Related
Guys i have a problem with my LG g2 D802 with screen turning black often, then i messed around with the phone and ticked the option "always GUP overly" something like that in developer menu, anyways after that i didn't had any problem for 3 days, then again the blackout started,after restarting the phone more than 10 times i got the display back, then i checked if that overlay option is still ticked, is wasn't ticked , and i didnt touched it, anyways ..this should be an software problem right? anyone here know how to fix this ? Help me out please
Best Wishes
@Demitha some options in developer options resets after boot so they are getting unticked by the system itself. I don't know why your screen turns black after enabling that option, the onkly thing i can say to try is to wipe cache/dalvik-cache and even maybe an factory reset and if those things doesnt work then reflash stock.
We could also see maybe what caused an bsod when you logcat but since it appears often its hard to say when you need to start logging.
wulsic said:
@Demitha some options in developer options resets after boot so they are getting unticked by the system itself. I don't know why your screen turns black after enabling that option, the onkly thing i can say to try is to wipe cache/dalvik-cache and even maybe an factory reset and if those things doesnt work then reflash stock.
We could also see maybe what caused an bsod when you logcat but since it appears often its hard to say when you need to start logging.
Click to expand...
Click to collapse
the option name is "disable HW Overlays" screen dont turn black after enabling that option, i meant,screen didnt blackout after enabling it, but yet some times screen goes out, i did reset the phone once, didn't fix the issues, how do i reflash a stock? i never done it?is there a video guide or something? help me out please.
Best Wishes
@Demitha here is the guide if you didn't founded it yet: http://forum.xda-developers.com/showthread.php?t=2432476
Did you had this blackout also before enabling it?
wulsic said:
@Demitha here is the guide if you didn't founded it yet: http://forum.xda-developers.com/showthread.php?t=2432476
Did you had this blackout also before enabling it?
Click to expand...
Click to collapse
yeah it was worse before,after enabling that option blackout didnt happen fro o 3 days , i noticed even though i didnt restart the phone that HW overlay option gets unticked :/
@Demitha well if it was even worse before then i suggest you to charge your phone to 80-100% for safety because it may take a long time, maybe it can be lower but for safety I always have my battery around that percentage. And then you can try the guide. If your screen turns black can you touch it on random spots to see or it makes sound noises like if you click on anything.
wulsic said:
@Demitha well if it was even worse before then i suggest you to charge your phone to 80-100% for safety because it may take a long time, maybe it can be lower but for safety I always have my battery around that percentage. And then you can try the guide. If your screen turns black can you touch it on random spots to see or it makes sound noises like if you click on anything.
Click to expand...
Click to collapse
i hear sounds and vibrations, phone is totally working on the blackout
@wulsic you think reflashing will fix this issue?
@Demitha it could be but i am not sure, it could be also an hardware defect maybe, and also maybe an software so try to reflash it I am not sure or its hardware or software since it could be both.
wulsic said:
@Demitha here is the guide if you didn't founded it yet: http://forum.xda-developers.com/showthread.php?t=2432476
Did you had this blackout also before enabling it?
Click to expand...
Click to collapse
wulsic said:
@Demitha it could be but i am not sure, it could be also an hardware defect maybe, and also maybe an software so try to reflash it I am not sure or its hardware or software since it could be both.
Click to expand...
Click to collapse
if i flash the phone,i will get software updates like normally ?
@Demitha if you flash the phone to 4.4.2 then you will still get software updates for apps, system incremental updates etc so dont worry about it. You need to care first more to find out the black screen problem. Also if you have an blackscreen do you see like an backlight on ? That the black color gives light ?
wulsic said:
@Demitha if you flash the phone to 4.4.2 then you will still get software updates for apps, system incremental updates etc so dont worry about it. You need to care first more to find out the black screen problem. Also if you have an blackscreen do you see like an backlight on ? That the black color gives light ?
Click to expand...
Click to collapse
yes it does, it like a black light,not very bright but the light is there
@Demitha ahh okay so its not totally off, it could be an software problem since i also had something like that on custom roms when waking up my device (bsod) but i dont remember that my touchscreen still works that i hear those noises so it could be also an hardware problem. The only thing i cannsay is flash it to stock once again like it came out of the box and use it for a couple days to see or its coming back. If so can you reply again to this thread? I think that some g2 users could maybe say more about this subject since i dont have the g2. I also read about display graphics ram which saves battery by holding an image and displaying it like that instead of the gpu so i thought maybe that it got bugged or what, correct me if i'm wrong I read it today in the morning around 2 am.
wulsic said:
@Demitha ahh okay so its not totally off, it could be an software problem since i also had something like that on custom roms when waking up my device (bsod) but i dont remember that my touchscreen still works that i hear those noises so it could be also an hardware problem. The only thing i cannsay is flash it to stock once again like it came out of the box and use it for a couple days to see or its coming back. If so can you reply again to this thread? I think that some g2 users could maybe say more about this subject since i dont have the g2. I also read about display graphics ram which saves battery by holding an image and displaying it like that instead of the gpu so i thought maybe that it got bugged or what, correct me if i'm wrong I read it today in the morning around 2 am.
Click to expand...
Click to collapse
well, i never flashed a phone before, im afraid i might do it wrong
@Demitha i know that you are scared for the first time, when i flashed an android phone for the first time (Htc google nexus one, i miss the trackball xd) i read everything carefully and i did it good it was different then windows mobile since i was the first android user in my family. but i had it for some weeks and sold it again because i had touchscreen issues,power button didnt worked so yeah. But that was some hardware issue which wasn't caused by the flash but it was the previous owner.
So just read the guide carefully, backup all your files to be sure and charge your phone to 80% atleast thats what i am always doing. Or you need to know an geeky friend who also do these stuff
can you please point out what i need to download in order to flash the phone in this thread, there are different versions of g2 models there ,please check the screenshot below
https://copy.com/71RAumYBzgmI
here is the other screenshot, - https://copy.com/9oNye3tlH96z
@Demitha you said you have the d802 version and i also see in the build/software number the d802 so
You need to flash the d802 version which is the international one so just find the d802 files and flash it goodluck! Reply if you need help again
I have a Moto G4 Play, I believe it is XT1607, purchased straight from Motorola. I'm running Squid's CM with the stock kernel. Overall it works great, but I have a minor annoyance: when I first turn the phone on from being completely off, the time and date is always completely wrong. I mean off by MANY hours and minutes (like I don't even know where it gets this time from), as well as like 20-30 days. Obviously this isn't much of a problem since time syncs with my cellular network after the boot is complete, but this still bothers me slightly. Every other phone I've had kept the time accurate even when it was off. Is this a ROM issue or a G4 Play issue? Anyone else experiencing this?
*Note that I don't remove the battery when the phone gets turned off.
It's nothing tho. Connect to WiFi or use the latest ROM
I have the same problem in my Moto g4 play. Any suggestion?
It's tied to your Recovery. TWRP goes off whatever the hardware time is. My phone was initially in Mountain or Central time, but even with it set to Pacific Time it's off by several hours and minutes. The only way to fix it would be to modify whatever the heck smartphones use as BIOS/CMOS.
mkollersms said:
It's tied to your Recovery. TWRP goes off whatever the hardware time is. My phone was initially in Mountain or Central time, but even with it set to Pacific Time it's off by several hours and minutes. The only way to fix it would be to modify whatever the heck smartphones use as BIOS/CMOS.
Click to expand...
Click to collapse
Maybe this is something Moto removes as a result of unlocking bootloader. There's no possible way this glitch exists on stock firmware.
jasonmerc said:
Maybe this is something Moto removes as a result of unlocking bootloader. There's no possible way this glitch exists on stock firmware.
Click to expand...
Click to collapse
Well, I would gather that the clock applications (CM has two) would be storing that information either in the memory space directly or not at all. That's the only way I could see that file being recreated on boot. As far as I can tell, phones don't have button cell batteries in them, so don't ask me how the Recovery manages to keep time.
jasonmerc said:
I have a Moto G4 Play, I believe it is XT1607, purchased straight from Motorola. I'm running Squid's CM with the stock kernel. Overall it works great, but I have a minor annoyance: when I first turn the phone on from being completely off, the time and date is always completely wrong. I mean off by MANY hours and minutes (like I don't even know where it gets this time from), as well as like 20-30 days. Obviously this isn't much of a problem since time syncs with my cellular network after the boot is complete, but this still bothers me slightly. Every other phone I've had kept the time accurate even when it was off. Is this a ROM issue or a G4 Play issue? Anyone else experiencing this?
*Note that I don't remove the battery when the phone gets turned off.
Click to expand...
Click to collapse
Hey bro! I have this phone too!
triggerlord said:
Hey bro! I have this phone too!
Click to expand...
Click to collapse
Good to hear from you again. Is your internal clock being stupid as well (assuming you flashed TWRP/ROMs and such to it)? If so what exact model do you have?
jasonmerc said:
Good to hear from you again. Is your internal clock being stupid as well (assuming you flashed TWRP/ROMs and such to it)? If so what exact model do you have?
Click to expand...
Click to collapse
I have the XT1607. I bought it off Amazon. I flashed AOKP + Gapps and the clock seems to work fine on mine.
My phone seems to have developed a display driver issue where part of the screen ghosts images, turns 50 shades of gray, etc. Apparently this is a common problem at one time one if one searches "fix moto x pure display driver" on google but cant find a fix for it.
Does anyone know how to fix this? Did motorola address this issue with a fix? Perhaps reflash the driver? Ive already tried wiping the phone and flashing to Nougat ([7.1.2] AICP for clark). Neither made a difference. It shows in twrp as well btw.
running out of ideas here. Hate to have to retire the old girl.
any ideas on a replacement for verizon networks...i need an sd card slot for additional storage and of course the phone needs to be rootable. Maybe a moto G?
What makes you think this is a driver issue? If you do a screen shot when this is occuring does it look normal or messed up? If it is a software issue, the screen shot will look messed up, if it looks normal then the hardware is at fault. That would give you about a 80% accurate answer.
There are no "known issues" with the display drivers in the Moto X S/P, so if it's software, best would be to reflash stock via fastboot and retest. If the issue recurs it is likely hardware.
acejavelin said:
What makes you think this is a driver issue? If you do a screen shot when this is occuring does it look normal or messed up? If it is a software issue, the screen shot will look messed up, if it looks normal then the hardware is at fault. That would give you about a 80% accurate answer.
There are no "known issues" with the display drivers in the Moto X S/P, so if it's software, best would be to reflash stock via fastboot and retest. If the issue recurs it is likely hardware.
Click to expand...
Click to collapse
I thought it might be a driver issue by searching for "moto x pure display driver". My phone looks exactly like the one pictured in the first link in the search. Android authority is a pretty decent site and after reading through the comments section it does seem common enough.
Im going to try to reflash via fastboot as you suggested but im afraid i think youre right as it doesnt show on a screenshot. Its worth a try i suppose. Just dont have the $ for a phone right now.
thanks for the reply btw.
steveindajeep said:
I thought it might be a driver issue by searching for "moto x pure display driver". My phone looks exactly like the one pictured in the first link in the search. Android authority is a pretty decent site and after reading through the comments section it does seem common enough.
Im going to try to reflash via fastboot as you suggested but im afraid i think youre right as it doesnt show on a screenshot. Its worth a try i suppose. Just dont have the $ for a phone right now.
thanks for the reply btw.
Click to expand...
Click to collapse
I haven't heard of any display issues in this regard since the X's initial release, and that was fixed pretty quickly with an OTA. None sense then... The "display driver" is built into the kernel, and if this was an issue I'm sure we would have heard more about it.
Sorry to hear, but this sure sounds like a hardware problem.
Okay so my issue was similar just that instead of the bottom half, it was happening for the full screen and it seems to have fixed itself after having the screen on full brightness overnight. It was a mistake actually. It all started when I was replacing my old battery cus it got so weak. I had no heat gun or anything or that sort around so I figured I could heat the phone up internally. Started running clash royale as it got the phone hotter whenever I played and changed the sleep period to 30 minutes because those are the things that make my phone heat up. So I did that. Replaced the battery yada yada, it works perfectly now. So I forgot to set the sleep period back and went to bed with the screen on. Somehow it just continued to stay on all the way till morning (or I believe so). Woke up to the phone hot, screen brightness on full. It was under my pillow too so the heat just kept building up. Needles to say, when I realised I closed the apps running, turned the brightness all the way down and locked the screen. I put it aside to cool off because I had just gotten up, wasn't in the mood. But seeing as I can't keep my hands always from my phone I picked it up like 3 minutes later. I'm writing this an hour after and the brightness is on the lowest setting. No ghosting, no lines being drawn up anywhere, no lagging, nothing. It's currently working like brand new. I should mention that the phone was plugged in the whole time. And mobile network was on. WiFi was off.
I'll keep monitoring the issue and I'll post and changes if any. Hopefully there won't be any.
_arxn said:
Okay so my issue was similar just that instead of the bottom half, it was happening for the full screen and it seems to have fixed itself after having the screen on full brightness overnight. It was a mistake actually. It all started when I was replacing my old battery cus it got so weak. I had no heat gun or anything or that sort around so I figured I could heat the phone up internally. Started running clash royale as it got the phone hotter whenever I played and changed the sleep period to 30 minutes because those are the things that make my phone heat up. So I did that. Replaced the battery yada yada, it works perfectly now. So I forgot to set the sleep period back and went to bed with the screen on. Somehow it just continued to stay on all the way till morning (or I believe so). Woke up to the phone hot, screen brightness on full. It was under my pillow too so the heat just kept building up. Needles to say, when I realised I closed the apps running, turned the brightness all the way down and locked the screen. I put it aside to cool off because I had just gotten up, wasn't in the mood. But seeing as I can't keep my hands always from my phone I picked it up like 3 minutes later. I'm writing this an hour after and the brightness is on the lowest setting. No ghosting, no lines being drawn up anywhere, no lagging, nothing. It's currently working like brand new. I should mention that the phone was plugged in the whole time. And mobile network was on. WiFi was off.
I'll keep monitoring the issue and I'll post and changes if any. Hopefully there won't be any.
Click to expand...
Click to collapse
Later on the same day: So I fell asleep for about 4 hours with brightness on low. (damn I sleep a lot) woke up and the issue returned. But I had the brightness on full for a while and it seems to have resolved again when I put it back to low brightness.
That's all so far. Still monitoring
I'm glad someone else noticed that when you slide the brightness bar it effects the way this display issue behaves. I was starting to think I was alone on this. Now this is just my experience on my phone of course. It seems to be around 2/3 way to full bright that it starts to flash the white lines on and off and then 3/4 + it is pretty much acts as it should, they go away! So I took a screenshot as acejavelin suggested and the screenshot was clear. So this would explain why updates don't seem to change anything since it does seem to be a certain batch with bad hardware. Can this hardware be solder changed? Guess I will keep an eye out for sale of xpure with busted digitizer/good lcd to test and possible mb swap.
Yes 1575 definitely has a display driver issue, i've noticed this too. I don't think there is a way to fix this, unless it would be fixed in Nougat.
But how sure are you that it's a driver issue and not hardware? That's why I'm waiting for nougat. If it doesn't fix the issue then I'm just going to have to retire the phone.
Sorry bro
If you're encountering a display problem in aftermarket roms and even on the bootloader and recovery menus, then it's most definitely not a "display driver" issue. As @acejavelin already pointed out, it's not a known software problem unless you're running the shipped Lollipop software release.
Mine has the same issues now and then but a restart fixes it always.
Bill720 said:
If you're encountering a display problem in aftermarket roms and even on the bootloader and recovery menus, then it's most definitely not a "display driver" issue. As @acejavelin already pointed out, it's not a known software problem unless you're running the shipped Lollipop software release.
Click to expand...
Click to collapse
that's the point, problems are only in the stock rom. I've tried many custom roms and none of them have this issue, but unfortunately they have many other issues so i have to use the stock version.
But the Op!
onupirat said:
that's the point, problems are only in the stock rom. I've tried many custom roms and none of them have this issue, but unfortunately they have many other issues so i have to use the stock version.
Click to expand...
Click to collapse
steveindajeep said:
I've already tried wiping the phone and flashing to Nougat ([7.1.2] AICP for clark). Neither made a difference. It shows in twrp as well btw.
Click to expand...
Click to collapse
Oh. I just read this and assumed that we were all talking about the same thing. In your case, I'd perform some experimentation to make absolute certain that your findings aren't just coincidence.
Question re: hardware vs software
acejavelin said:
What makes you think this is a driver issue? If you do a screen shot when this is occuring does it look normal or messed up? If it is a software issue, the screen shot will look messed up, if it looks normal then the hardware is at fault. That would give you about a 80% accurate answer.
There are no "known issues" with the display drivers in the Moto X S/P, so if it's software, best would be to reflash stock via fastboot and retest. If the issue recurs it is likely hardware.
Click to expand...
Click to collapse
Hi ~ just read your msg, and tried your "screenshot test." The grayish area on my screen (which over time, comes & goes - haven't detected a pattern as to why/when) DOES show up on the screenshot.
If I understand correctly, that would tend to indicate that I am experiencing a software issue? (Not hardware)
I did do a Factory Data Reset, and am experiencing the same issue. I had not added any apps for an extended period of time, prior to this gray-area occuring. I did, however, drop the phone. I don't recall for certain, but I don't think the problem occurred immediately, rather, it started very shortly thereafter (1 -3 days).
And I am waiting for delivery of a battery, since that's shot (runs down very quickly, & shuts down with anywhere from 30% - 60%+ battery level).
Any suggestions for resolving this? I hope this post makes sense... And thank you for any ideas or assistance you can offer!
Hello everybody. I have the same problem.
And who ever changed the display? Do you want to understand this is the problem of the display, motherboard or drivers?
I think it's a software problem, a hardware will not stop glitches when you flash a different software until and unless you fix it. In my experience, after my phone break because of downgrade to marshmallow stock firmware, and with an unlock bootloader i update my phone using OTA update, suddenly it stop working. blank screen and i tried try to recovery it with xt1575 IMG file to boot it again, mine it was xt1572(India) then I start facing a lot of problem, glitches, can go back to marshmallow stock firmware so and so... Now I'm trying to find a solution !!!! Custom ROM, CM13 work better and no glitches till now... I will Report soon
Moto x style/pure display problem
steveindajeep said:
My phone seems to have developed a display driver issue where part of the screen ghosts images, turns 50 shades of gray, etc. Apparently this is a common problem at one time one if one searches "fix moto x pure display driver" on google but cant find a fix for it.
Does anyone know how to fix this? Did motorola address this issue with a fix? Perhaps reflash the driver? Ive already tried wiping the phone and flashing to Nougat ([7.1.2] AICP for clark). Neither made a difference. It shows in twrp as well btw.
running out of ideas here. Hate to have to retire the old girl.
any ideas on a replacement for verizon networks...i need an sd card slot for additional storage and of course the phone needs to be rootable. Maybe a moto G?
Click to expand...
Click to collapse
I think maybe due to brightness control problem, could be the software or hardware problem
Hey guys, Does anyone know how to fix the static screen during the boot animagion and once booted permanently? Its very annoying. I've looked around but can't find anything
Im sorry but you really didnt look... it has been said MANY times that using a custom kernel can fix it. either reStock or werewolf will fix it.
me2151 said:
Im sorry but you really didnt look... it has been said MANY times that using a custom kernel can fix it. either reStock or werewolf will fix it.
Click to expand...
Click to collapse
Neither of them work for me. Its still just static. So yes, I have looked around.
I assume you are rooted, what Rom and kernels are you running? If you have a stock based ROM you need a stock base kernel, werewolf has 2 of each. A werewolf 1.0 albatross.zip and ww 2.0 basilisk.zip for custom based rooms. (lineage-aosp rooms) And the same 2 kernels that have "stock" in the title. For stock based ROMS. Check red dragons kernel thread or try the 1.2 restock kernel. Turn off any screen lock b4 installing the zip in twrp?
I have stock rom and stock kernel.
In the settings, i have second screen to stay on and always show time.
As long as the second screen stays on, the static will not go away.
In my case, second screen stays on, so static does not go away.
What kernel do i need and where ?
tonycstech said:
I have stock rom and stock kernel.
In the settings, i have second screen to stay on and always show time.
As long as the second screen stays on, the static will not go away.
In my case, second screen stays on, so static does not go away.
What kernel do i need and where ?
Click to expand...
Click to collapse
They were mentioned above. You can also cover the proximity sensor and let both screens go off, then it should be fine.
bond32 said:
They were mentioned above. You can also cover the proximity sensor and let both screens go off, then it should be fine.
Click to expand...
Click to collapse
Covering the sensor does not turn of the screen. I dont know why.
Screen turn off ONLY during call, when i get it close to my ear but NOT when i cover it with my hand or flip the phone or what ever else you can think of.
My Moto G4 suddenly restarts at any time if I am using the phone, most of the time it happens when I receive a call.
I have tried various ROMS, even stock firmware, still facing the same issue.
I have the XT1643.
Anyone else facing such an issue?
[email protected] said:
My Moto G4 suddenly restarts at any time if I am using the phone, most of the time it happens when I receive a call.
I have tried various ROMS, even stock firmware, still facing the same issue.
I have the XT1643.
Anyone else facing such an issue?
Click to expand...
Click to collapse
Which baseband do you have? Do you tried without 3rd party apps on stock rom too?
strongst said:
Which baseband do you have? Do you tried without 3rd party apps on stock rom too?
Click to expand...
Click to collapse
I have the 'M8952_70030.25.03.62R' baseband.
I have tried without any third party apps installed, facing the same issue.
If in case it was a baseband issue, I would be interested in flashing the latest baseband.
Would you be kind enough to point me the right direction?
[email protected] said:
My Moto G4 suddenly restarts at any time if I am using the phone, most of the time it happens when I receive a call.
I have tried various ROMS, even stock firmware, still facing the same issue.
I have the XT1643.
Anyone else facing such an issue?
Click to expand...
Click to collapse
Same here.
I tried every rom. The problem still presists.
The problem is noticeable when battery is below 70 and while receiving calls.
Device XT1643
[email protected] said:
I have the 'M8952_70030.25.03.62R' baseband.
I have tried without any third party apps installed, facing the same issue.
If in case it was a baseband issue, I would be interested in flashing the latest baseband.
Would you be kind enough to point me the right direction?
Click to expand...
Click to collapse
You do have latest baseband version.
This issue happens when phone gets heats up and battery stops responding (power cut) to lower the heat radiated.
If im right according to your telling ill suggest you to take the phone to service centre. It is more a hardware problem then the roms itself.
How do i know?
Simple, experience.
My friends g4 plus suffers from same issue(not on calls but heat issue) and service centre guy told us this reason.
Well i may be wrong as information is incomplete.
Fill in this :
Battery temperature.
Background activities.
Mostly with calls and other than that (if happened).
You told all/most roms, may you name some with build date and what/how issue existed in all of then.
Also battery supply voltage(use my device app).
Try the same issue like this :
Plug in your phone charge it and play heavy games.
If device reboots you got your solution, if not then recreate the scenario and tell us exactly what happened.
Saksham Thapaliya said:
Same here.
I tried every rom. The problem still presists.
The problem is noticeable when battery is below 70 and while receiving calls.
Device XT1643
Click to expand...
Click to collapse
DgnrtnX said:
You do have latest baseband version.
This issue happens when phone gets heats up and battery stops responding (power cut) to lower the heat radiated.
If im right according to your telling ill suggest you to take the phone to service centre. It is more a hardware problem then the roms itself.
How do i know?
Simple, experience.
My friends g4 plus suffers from same issue(not on calls but heat issue) and service centre guy told us this reason.
Well i may be wrong as information is incomplete.
Fill in this :
Battery temperature.
Background activities.
Mostly with calls and other than that (if happened).
You told all/most roms, may you name some with build date and what/how issue existed in all of then.
Also battery supply voltage(use my device app).
Try the same issue like this :
Plug in your phone charge it and play heavy games.
If device reboots you got your solution, if not then recreate the scenario and tell us exactly what happened.
Click to expand...
Click to collapse
Thank you for the suggestion, I guess I will take it to the service centre, seems more of a hardware issue.
Anyways, my phone is still in the warranty period, but I have flashed it.
Will they service it for free if I flash stock firmware and relock the bootloader?
[email protected] said:
Thank you for the suggestion, I guess I will take it to the service centre, seems more of a hardware issue.
Anyways, my phone is still in the warranty period, but I have flashed it.
Will they service it for free if I flash stock firmware and relock the bootloader?
Click to expand...
Click to collapse
No,
Once you unlock your bootloader the warranty is compromised.
Saksham Thapaliya said:
No,
Once you unlock your bootloader the warranty is compromised.
Click to expand...
Click to collapse
Well, will they still service my phone if I pay them?
[email protected] said:
Well, will they still service my phone if I pay them?
Click to expand...
Click to collapse
Yes, they will take your phone and money from your pocket and will repair it.
If you can now, try to flash the stock rom with build no. NPJS25.93-14-8.
I also had similar issue(it shut down on receiving notifications) with build no. NPJS25.93-14-4 (even on custom roms I flashed over it) which got fixed in the NPJS25.93-14-8 update.
Now again the issue reappeared on NPJS25.93-14-10 version.
Hence I flashed the complete NPJS25.93-14-8 using fastboot and now it's working fine(both on stock and custom roms). Maybe it had something to do with modem version or bootloader(unlikely).
Tell me if it worked.
saranshkmr.in said:
If you can now, try to flash the stock rom with build no. NPJS25.93-14-8.
I also had similar issue(it shut down on receiving notifications) with build no. NPJS25.93-14-4 (even on custom roms I flashed over it) which got fixed in the NPJS25.93-14-8 update.
Now again the issue reappeared on NPJS25.93-14-10 version.
Hence I flashed the complete NPJS25.93-14-8 using fastboot and now it's working fine(both on stock and custom roms). Maybe it had something to do with modem version or bootloader(unlikely).
Tell me if it worked.
Click to expand...
Click to collapse
My phone shuts down while playing something through speakers( like while playing music, ringtones etc.).
It doesn't powet on itself but i have to turn on the device by myself. Is it a hardware issue?
Also my camera flash isn't working fine. While capturing only yellow led blinks. But while using torch both the led's are workung fine. What the crap this device is??
ADITYA_KUMAR said:
My phone shuts down while playing something through speakers( like while playing music, ringtones etc.).
It doesn't powet on itself but i have to turn on the device by myself. Is it a hardware issue?
Also my camera flash isn't working fine. While capturing only yellow led blinks. But while using torch both the led's are workung fine. What the crap this device is
Click to expand...
Click to collapse
If you haven't tried clean flash, do that. Flash the NPJS25.93-14-8 version.
Else it highly seems a Hardware issue.
And yes, this device is a crap. Heating issue, lag when recording video, random shutdowns, etc. But development work for this device is great.
I also have my earphone jack not working which apparently required to change the whole motherboard to fix as claimed by service center guy. And unlocked bootloader void my warranty so it's been this way for long time.
I had the same problem and I did everything. change rom, from kernel I did everything possible with software based speech and searching in forums I found that it is a battery failure, check if you still have the warranty. otherwise you need to buy a new battery only this way the problem is solved
I hope you solve your problem
I just solved it today and it goes great, greetings:good:
saranshkmr.in said:
If you haven't tried clean flash, do that. Flash the NPJS25.93-14-8 version.
Else it highly seems a Hardware issue.
And yes, this device is a crap. Heating issue, lag when recording video, random shutdowns, etc. But development work for this device is great.
I also have my earphone jack not working which apparently required to change the whole motherboard to fix as claimed by service center guy. And unlocked bootloader void my warranty so it's been this way for long time.
Click to expand...
Click to collapse
When i was on 14-8v , i started having these problems. Therefore i flashed lineage os 14.1. but problems are still.
While playing music it's not necessary that my device is going to be turned off, but sometimes it suddenly turns off by itself.
And my both leds are working fine while using torch, but at the time of capturing shots the white led does not blink, only yellow led blink. If anyone knows plzz let me know the solution.
Same here
I am using latest Android update provided by Moto. No root and nothing else..