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
Related
Earlier, my G2 shut off on me about 5 times. -_-
First, I had it sitting in the car ,tried to take a pic but the stupid voice recognition menu kept coming up so I gave up and set it down in the console. When I got home, the phone felt warm and was.. off.
Then, I turned it on.. stuffed it in my pocket. A moment later, I pulled it out and YET AGAIN when I pushed the button I was greeted by a quick vibe and the HTC screen -_-
Then a few minutes later I ran a speed test (checking HSPA+ out in Vegas).. put it down on the table.. come back.. PHONE IS *(@#% DEAD AGAIN.
I HATE YOU! *glares at phone*
It's killing me because it either happens several times in a row, or doesn't happen for days! I've tried replacing the sim card, replacing the SD card.. moving the battery... no dice.
Maybe it's my SIM card? Would that cause it? My last phone did that -_- And I'm silly to have not yet changed the SIM lol
Good thing I have a spare sitting in my bag.
What battery are you using? Aftermarket? Is so, did you remove the sticker around the battery? If you did then make sure you place a piece of tape on the battery to avoid making contact with the metal sd card holder. The metal on metal causes it to shut down.
Sent from my HTC Vision using XDA App
Interesting. I've also been having random shutdowns (not reboots, which I've seen mentioned elsewhere, due to a hardware fault) --
HTC Desire Z, using default battery, but I'll try isolating it anyway with a slip of paper or something.
OP you on a custom rom with overclock? maybe your clocking your phone too high or low?
Also if the phone for whatever reason gets too hot or cold it will turn itself off.
Please see this forum: Phone powers down and won't turn back on w/o pulling the battery
I strongly believe that this may be an issue with the GPS and/or Google Maps. Once I have the GPS off, this has not occurred. Can anyone else try this?
I have the Bell Desire Z NAM with stock HTC Sense 2.2 ROM.
It seems to be quite prevalent, see the bottom of this review: T-Mobile G2 is speedy sequel to original Android
I think you may be onto something with that GPS note, but my phone doesnt' need the battery pulled to restart.
Also, it's running the stock firmware, stock battery (just exchanged battery and got a new SIM card yesterday, and it shut off again today.. so those aren't the problem)... so any issues I'm having are 100% stock related...
This time it shut off after using Maps so....
i read somewhere (trying to find the source) that some G2's were experiencing random restarts / shutdowns due to low signal strength. Not sure how valid this is but you might want to look into this as well.
fablife said:
i read somewhere (trying to find the source) that some G2's were experiencing random restarts / shutdowns due to low signal strength. Not sure how valid this is but you might want to look into this as well.
Click to expand...
Click to collapse
This was true before we received the first OTA update. Since then though the problem has been fixed.
I think it was definitely the GPS, that said I just got done with a really long phone call about this and have a replacement on the way.. but that was way too much effort AND I have to pay shipping (it's not much, but seriously.) I'm not happy that T-Mobile was THAT big a pain in the butt about getting the phone replaced with a new one in the 30 day return period.
Going by the pointers one of my close friends on sprint (that used to be on AT&T) gave me, I'd say this could've been worse with another provider.. but it shouldn't have been. The reception isn't the best so the customer service should make up for that, and it sorta does.. but it sorta doesn't.
Oh well.
I have been experiencing almost the same thing for the past week or so. I have tried a few things such as lowering clock speeds, changing roms, and not using maps or GPS. Nothing has stopped the shutdowns. I cant seem to find a pattern in the things the phone is doing when it shuts off because it rarely does it when i have the screen on, also it never does it if music is playing or if i am watching a video. I will say that it seems to happen alot when i am in spots i know are dead spots for phone signal. I flash roms a fair amount so it is hard to say this has started after flashing a rom, but I will say it never did this before I flashed my first sensui 3.0 rom.
I am thinking its one of two things, something with the radio and/or its firmware or something with the sdcard because at least one senseui 3.0 rom said something about sdcard formatting.
I hope all this helps the smart people come up with idea on what wrong with our phones.
djrajir said:
I have been experiencing almost the same thing for the past week or so. I have tried a few things such as lowering clock speeds, changing roms, and not using maps or GPS. Nothing has stopped the shutdowns. I cant seem to find a pattern in the things the phone is doing when it shuts off because it rarely does it when i have the screen on, also it never does it if music is playing or if i am watching a video. I will say that it seems to happen alot when i am in spots i know are dead spots for phone signal. I flash roms a fair amount so it is hard to say this has started after flashing a rom, but I will say it never did this before I flashed my first sensui 3.0 rom.
I am thinking its one of two things, something with the radio and/or its firmware or something with the sdcard because at least one senseui 3.0 rom said something about sdcard formatting.
I hope all this helps the smart people come up with idea on what wrong with our phones.
Click to expand...
Click to collapse
My Desire Z had the same problem and I returned it to HTC Service for repair. They said they change some cables? and a new battery. It has been nearly 3 days and I haven't experienced a single shutdown but there was one time it restarted by itself.
Yeah my only problem with that is, I am close to my upgrade date. How much did it cost. I may still do it so I can give this phone to my kid brother.
Sent from my Htcclay's SuperCM7 G2 using Tapatalk
Just to update, I found that I can make it do it some times when playing with opening the hinge.
Sent from my Htcclay's SuperCM7 G2 using Tapatalk
Possible cause/fix found
I posted this in another thread here regarding the same problem but it appears it may have been overlooked so I'll post the info again in hopes of helping you and others having this problem.
A possible cause/fix has been found as posted on the T-mobile forums:
http://forums.t-mobile.com/t5/T-Mobile-G2/G2-Turning-off-by-itself/td-p/513575/page/4
There is a conductive metal strip along the back of the battery that looks like it may be shorting out. Check out the link for detailed fix with pics. I take no credit for this, just posting it since I'm experiencing this problem too.
Talked to tmobile CS today and was trying to get a replacement because my phone would randomly reboot and shut off. All he told me was go and pick up a new sim card. If that didn't help then they would be willing to give me a warranty replacement.
Sent from my T-Mobile G2 using XDA App
carquote said:
I posted this in another thread here regarding the same problem but it appears it may have been overlooked so I'll post the info again in hopes of helping you and others having this problem.
A possible cause/fix has been found as posted on the T-mobile forums:
http://forums.t-mobile.com/t5/T-Mobi.../513575/page/4
There is a conductive metal strip along the back of the battery that looks like it may be shorting out. Check out the link for detailed fix with pics. I take no credit for this, just posting it since I'm experiencing this problem too.
Click to expand...
Click to collapse
Clicking your link all I got was an empty T-Mobile page with the message "Page not found" and some some java script error message when closing the window.
Is this possible fix something else than lining the back of the battery with a strip of paper?
whpsnp said:
Clicking your link all I got was an empty T-Mobile page with the message "Page not found" and some some java script error message when closing the window.
Click to expand...
Click to collapse
Sorry about that, I fixed the link and it should be working now.
Cool, thanks!
Sent from my HTC Vision using XDA App
I'm pretty sure mine is not caused by the metal strip since my battery's all proofed. I didn't have anything wrong with it until about half a month ago, and it always happened after using GPS and left it on. If I turn it off after navigation or any other app that requires GPS the phone won't go into SOD.
I switched back to CM7 RC2 around that time and starting to get the GPS no fix problem, and it could't be fixed by the dd=/dev/.... script. So I switched into Nightly 88 or something that at least I was able to get a fix but the not-so-random freezing started.
This morning I flashed the new 7.1.0 RC1 and the phone would just turn itself off (it used to just freeze and become hot), and I got really tired of it... My old G1 was much more reliable than this.
I tried the dd=/dev script again, so far after 5 min the phone is still on with GPS on....
@carcuote
Thank you! I haven't had this issue for months now. But the solution is so easy to do that I will try our anyways.
I had this issue the first month our so when I got the new phone, but went away permanently after the second month. Maybe the contacts in the battery got a little rusted? Don't know but the solution is simple enough to try...
Sent from my T-Mobile G2
So before the gingerbread update i was experiencing the nexus one touch screen issue. This issue would happen mostly when the phone would be charging or warm, and the y coordinate of the touch screen would be off by about an inch. (I would post a link to youtube but i can't yet... new member =/ ) So if you try to answer your phone while the defect was active, you couldnt, because touching the slider would be recognized as trying to touch the 'menu' key on the phone.
Anyway, after gingerbread got pushed to my device, i have yet to experience this issue!! i havent been able to find anyone reporting this resolution. i'm extremely please about this because it was becoming a deal breaker after i missed an important call because i couldnt answer my phone due to the issue!!
anyone else experiencing this resolution!?
In my experiences it does still occur, although seemingly less frequently. It is a hardware problem though so probably won't disappear regardless of the OS
Hollow.Droid said:
In my experiences it does still occur, although seemingly less frequently. It is a hardware problem though so probably won't disappear regardless of the OS
Click to expand...
Click to collapse
Yup. For some reason I have worse now than before. Maybe I'm just using it more now. Lately it's driving me nuts, to the point of actually looking at a replacement.
Memnoch30 said:
Yup. For some reason I have worse now than before. Maybe I'm just using it more now. Lately it's driving me nuts, to the point of actually looking at a replacement.
Click to expand...
Click to collapse
this is where I was at before the push, i was seriously considering the incredible s, but for now it seems to have completely disappeared from my device...
I've also heard its a hardware issue (I do believe it to be true, not questioning that), so i found it extremely odd that its not happening now on my device.
Guess I'll just keep my mouth shut and enjoy
Observed no difference. The bug still appears every now and then. Doesn't bother me much because it usually occurs when the phone's charging. Not when I'm on the street using it. I heard that removing any kind of screen protectors can actually solve this problem.
NexusDro said:
Observed no difference. The bug still appears every now and then. Doesn't bother me much because it usually occurs when the phone's charging. Not when I'm on the street using it. I heard that removing any kind of screen protectors can actually solve this problem.
Click to expand...
Click to collapse
*gasp* not my invisible shield!?
Memnoch30 said:
Yup. For some reason I have worse now than before. Maybe I'm just using it more now. Lately it's driving me nuts, to the point of actually looking at a replacement.
Click to expand...
Click to collapse
I had it terribly after the GB OTA, I wiped cache & dalvik and it all but went away. One occurrence in a week and a half, and I've been using the crap out of the phone.
Slightly off topic question: On stock Android, is wiping cache the same as wiping the dalvik cache? The stock recovery doesn't have the "wipe dalvik" option, only "wipe cache".
No it's not, but if you have root you can wipe it manually by removing the contents /data/dalvik-cache/
Rusty! said:
No it's not, but if you have root you can wipe it manually by removing the contents /data/dalvik-cache/
Click to expand...
Click to collapse
Thanks. But every time you flash an official update, the cache gets wiped and rebuilt though, right? That's why after each update it takes a long time to boot.
I still have the touchscreen issue. i think it will never be solved because it's an hardware issue, not a software one.
So the problem still appears, maybe a little less frequently.
I still have the prob but it's different with 2.3
Before 2.3, the touchscreen problem was unpredictable and could happen at almost anytime, whether charging or not. I replaced the handset but the problem persisted.
Since upgrading to GB, I've noticed a very clear pattern. If I'm charging my device and unplug it before it is fully charged, the touchscreen becomes extremely erratic to the point I must reboot the phone. If it's allowed to charge completely it's okay.
It never happens when it's is not charging.
Still annoying as hell but I've moved to Africa and having the device replaced is a real challenge. So I guess I'm stuck with until I replace it.
Still has issue
Stock, no modification at all. Today when I was rearranging icons in ADW Launcher, it seems that the screen registered click below where my finger actually was, same as the problem I saw previous to updating to 2.3.3. The phone was not hooked to a charger at the time.
Stock GRI40 here on my Nexus One...same issues that i've already had with Froyo. As it was posted before, it's a hardware issue; and the Nexus S is the new kid on Google's block, so i'm not expecting anything to improve our screens.
filippogiad said:
I still have the touchscreen issue. i think it will never be solved because it's an hardware issue, not a software one.
So the problem still appears, maybe a little less frequently.
Click to expand...
Click to collapse
Theoretically, there is a chance they could fix a software workaround for the hardware problem. If the error happens in only specific circumstances, and ALWAYS happens in those circumstances, then just teach the phone to know when those circumstances are happening, and tell it what to do in those cases. However, I doubt anyone at Google is working too hard on this problem. I agree, it seems to be much less frequent than it ever was. Seems likely that they may have added a little something to help us out.
brettbellaire said:
Seems likely that they may have added a little something to help us out.
Click to expand...
Click to collapse
Or more likely, it could be unintentional.
So even with official OTA it's still here?
Remember me of the ''crazy'' screen problem we had before while charging,perhaps it's a hardware problem after all
This is a main reason why tomorrow i'm getting a new galaxy s.
I tried a lot of custom and stock roms, I sent my phone to HTC and they replaced hardware, but this issue still persist. And it cause me a lot of problems, especially while driving...
I also still get that glitch but not as frequently. I noticed that i didn't need to reboot the phone to fix it. All i need to do is tap the power button to shutoff the screen and then re-tap to turn it back on and it'll show the lock screen. Slide to unlock and the screen is precise once again.
The bug is still there for me also. However, I didn't seem to have it as bad as some did originally, and now I've noticed that it's happening even less frequently.
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'm on T-Mobile but I just got home and phoned up my co-worker who has the Verizon version. Says he noticed a slight improvement in overall touchscreen responsiveness. Biggest problem that he said was fixed was ghost touches (touching one portion of the screen caused a menu to pop up somewhere else for example) being completely gone. Idk, it's really starting to feel like a lot of these bugs should have gotten squashed in the product testing phase. Wonder if this is the same update as the mandatory one T-Mobile got way back. I wouldn't think so since the T-Mobile update did not fix touch screen issues for anyone.
Anybody notice the auto brightness isn't as dim anymore which is a good thing IMO.
slick_shoes said:
Anybody notice the auto brightness isn't as dim anymore which is a good thing IMO.
Click to expand...
Click to collapse
well that sucks because the lowest wasn't low enough for me.
Lock-N-Load said:
2. I do NOT see a difference in QC 2.0. I was about 8.94-9.0 volts draw on QC 2.0 before, and now I am at same. I call it as no change in QC 2.0 speed - so still not "true" QC 2.0.
Click to expand...
Click to collapse
Forgive me if I've misunderstood QC 2.0. But my understanding is it can charge at 9V or 12V. So just because it's still at 9V doesn't definitely mean that the phone isn't receiving more power, the amps could have also increased.
To provide 15W, for instance, you'd need 3A at 5V, 1.67A at 9V, and 1.33A at 12V.
It's possible to still get 9V from the charger, but draw more amps, for faster charging. Using something like Battery Monitor Widget, to monitor the current provided to the battery, would be a useful tool.
bobloadmire said:
well that sucks because the lowest wasn't low enough for me.
Click to expand...
Click to collapse
Try the paid version of Lux ... Can get the screen REAL dim!
G4'ed it!
After reading all of these posts, I'm really hoping for a similar update on T-Mobile coming soon. I'm glad this isn't just a placebo and an actual solution to a software problem that doesn't require getting my phone serviced.
SIdeloading apps problem???
UPDATE: Nevermind - issue not related to Verizon update... Had Twilight app kick on after sunset and that overlay app (reducing blue light) is what caused the touch issue. (Credit: brainwash1)
Enabled installing from "Unknown Sources" and installed an app yesterday no problem
I just did the Verizon system update and reboot, now on sideloading install I get the permissions list with CANCEL & INSTALL buttons at the bottom. Looks normal, but the INSTALL button doesn't respond to any tapping. Tried landscape mode also, just to move where the button was located on the screen, but no dice. CANCEL button works fine.
[Also, if there are many permissions, so I need to scroll, the INSTALL button starts as a NEXT button, then changes to INSTALL when done scrolling to bottom. Doesn't matter, neither NEXT not INSTALL buttons function]
Not sure what else would cause this. It seems like the Verizon system update broke something. Anyone else having new problem sideloading after the update???
Whats your carrier? I think the other guy is verizon. So am i, and i put no thanks
z500zag said:
Enabled installing from "Unknown Sources" and installed an app yesterday no problem
I just did the Verizon system update and reboot, now on sideloading install I get the permissions list with CANCEL & INSTALL buttons at the bottom. Looks normal, but the INSTALL button doesn't respond to any tapping. Tried landscape mode also, just to move where the button was located on the screen, but no dice. CANCEL button works fine.
[Also, if there are many permissions, so I need to scroll, the INSTALL button starts as a NEXT button, then changes to INSTALL when done scrolling to bottom. Doesn't matter, neither NEXT not INSTALL buttons function]
Not sure what else would cause this. It seems like the Verizon system update broke something. Anyone else having new problem sideloading after the update???
Click to expand...
Click to collapse
Do you have an app running that overlays something on the screen? I've had this in the past with a couple of different apps. Try turning off anything that's running.
Sent from my VS986 using Tapatalk
Ding ding ding!
brainwash1 said:
Do you have an app running that overlays something on the screen? I've had this in the past with a couple of different apps. Try turning off anything that's running.
Sent from my VS986 using Tapatalk
Click to expand...
Click to collapse
Twilight app kicked on after sunset, which is why I started having the problem. Paused it, and no more issue. Thanks!
Misterxtc said:
If you or anyone else don't want to be bothered by the OTA in fear of patching a exploit for root block LGDMSClient.apk with the debloater tool by @gatesjunior. If anyone downloaded it and do not want to install it just clear the cache from recovery mode. That should remove it from the phone.
EDIT: To enter recovery mode power down the phone and then hold the volume down and power buttons when powering back on.
Click to expand...
Click to collapse
Wiping the cache did nothing. It keeps popping up saying it is already downloaded and ready to install.
psycho_asylum said:
Wiping the cache did nothing. It keeps popping up saying it is already downloaded and ready to install.
Click to expand...
Click to collapse
OK, then the update isn't stored in the cache partition as other phones. It's a bit drastic but a factory data reset will do it. I ended up taking the update and then froze the updater. It did improve the touch response so I have no need for further updates. It updates the kernel because that is where the necessary changes are.
Misterxtc said:
OK, then the update isn't stored in the cache partition as other phones. It's a bit drastic but a factory data reset will do it. I ended up taking the update and then froze the updater. It did improve the touch response so I have no need for further updates. It updates the kernel because that is where the necessary changes are.
Click to expand...
Click to collapse
my touch response "seems" improved but I still get ghost touches..
I love pretty much every aspect of the phone, but the issues I have with the touchscreen are maddening at times, if I didn't see widespread reports of issues I would have Verizon replace the phone, but I am not sure it's worth the hassle..
lazarus2297 said:
my touch response "seems" improved but I still get ghost touches..
I love pretty much every aspect of the phone, but the issues I have with the touchscreen are maddening at times, if I didn't see widespread reports of issues I would have Verizon replace the phone, but I am not sure it's worth the hassle..
Click to expand...
Click to collapse
It might be worth replacing. I first had a black one that had the problem pretty bad. I returned the phone and went back to my S6 for a while but ended up picking up a blue one from Best Buy and this one works great. The touch wasn't that sensitive before the update but now it works really good. My battery is really good on the blue model too. Keep in mind I paid full retail for mine so when I returned the first one there was no restocking fee. I go to BestBuy just for that reason.
I was having some touch issues just as many are experiencing. Just today I installed the Google keyboard from the play store. I enabled the new keyboard and stopped using the LG keyboard. I have been using it this way for about an hour and I am much happier. I am hopeful this will take care of my issue. This is on a Verizon G4.
I took the update yesterday and threw my Verizon G4 on a Qi Wireless Charger last night and the bug where it has crashed in the AM is still there. Not sure about that.
Basically every time I wake up on a night of Qi Charging, the phone is crashed and freaks out.
Update:
My phone is now getting hot and doing the screen brightness bounce like it did out of the box. Going from 100 to 90 to 80 to 90 to 80 to 100 to 90.
bnick007 said:
I was having some touch issues just as many are experiencing. Just today I installed the Google keyboard from the play store. I enabled the new keyboard and stopped using the LG keyboard. I have been using it this way for about an hour and I am much happier. I am hopeful this will take care of my issue. This is on a Verizon G4.
Click to expand...
Click to collapse
I switched from the LG keyboard to the google keyboard day one so that was never a source of my issues.. Just today.. twice post update I have had ghost touches launch the app switcher icon while texting and caused me to switch apps on accident.. Doh.. It's frustrating to say the least.
Never had a problem with wireless charging besides it's slow.
No screen brightness fluctuations.
No ghosting on screen.
Sounds like there's an awful big batch of bad phones.
06stang said:
Never had a problem with wireless charging besides it's slow.
No screen brightness fluctuations.
No ghosting on screen.
Sounds like there's an awful big batch of bad phones.
Click to expand...
Click to collapse
There are definitely bad ones. I returned mine again a few hours ago because my outdoor pictures would come out either dark or overexposed real bad. I tried manual mode and auto and no matter what I did they were awful. So I'm back to my S6 again, it was fun while it lasted.
Hello everyone,
I've had my note 4 over two years now and out of nowhere problems started happening after second MM update, model SM-N910F was freezing and restarting and sometimes was not able to boot normally and got mmc read fail.
I'm reading a lot about this problem in other forums and here, so hope someone could help about this issue.
No Success:
I tried anything from removing sd card, removing sim card, changing the battery, resetting the device, cleaning the cache, flashing the room through odin, flashing the rom with pit file and doing a re partition (Didn't tried Nand erase).
Success:
The only way that I was able to fix the freeze issue was by installing app called Wake Lock and enabling PARTIAL_WAKE_LOCK.
But using Wake Lock has its disadvantages. First of all you need to run the app all times which its not practical and second it wipes your battery because it keeps device and processor awake.
Please join this thread anyone who has similar issues with the aim to fix or bring the phone to an usable state again.
I also purchased my GN4 about 2 years ago and just recently got this error. This is really fishy. Wouldn't be surprised if it was Samsung trying to screw over all the root users and get us to upgrade to newer models.
The Sponge said:
I also purchased my GN4 about 2 years ago and just recently got this error. This is really fishy. Wouldn't be surprised if it was Samsung trying to screw over all the root users and get us to upgrade to newer models.
Click to expand...
Click to collapse
Did you tried Wake Lock if it works? Which model of GN4 do you have ?
shpeendi said:
Did you tried Wake Lock if it works? Which model of GN4 do you have ?
Click to expand...
Click to collapse
Yes, I'm on the Canadian SM-N910W8 model of GN4.
I've been using the Wake Lock app for a few days now and it works perfectly, if you can get the phone to boot into homescreen that is.
For instance, when the phone shuts off due to low battery or an inevitable crash, sometimes getting the phone to boot up is a real pain in the ass because it doesn't boot up correctly most of the time.
However, one odd fix I've discovered is to put your phone and battery in the fridge for about 2-3 minutes and let it cool down completely. And then magically your phone will boot up properly to homescreen again. Activate Wake Lock and you're pretty much good until the next time your phone shuts off and can't boot. My phone will NEVER boot up to homescreen if it is even slightly hot in temperature. In order to boot, it needs to be cool.
I am highly confident that this is indeed a hardware issue, instead of a software issue. The mainboard fails to read memory properly which probably indicates that the mainboard needs to be replaced. I however cannot afford to do this so I hope that I can last atleast 2-3 years of my GN4 surviving through Wake Lock. :crying:
The Sponge said:
Yes, I'm on the Canadian SM-N910W8 model of GN4.
I've been using the Wake Lock app for a few days now and it works perfectly, if you can get the phone to boot into homescreen that is.
For instance, when the phone shuts off due to low battery or an inevitable crash, sometimes getting the phone to boot up is a real pain in the ass because it doesn't boot up correctly most of the time.
However, one odd fix I've discovered is to put your phone and battery in the fridge for about 2-3 minutes and let it cool down completely. And then magically your phone will boot up properly to homescreen again. Activate Wake Lock and you're pretty much good until the next time your phone shuts off and can't boot. My phone will NEVER boot up to homescreen if it is even slightly hot in temperature. In order to boot, it needs to be cool.
I am highly confident that this is indeed a hardware issue, instead of a software issue. The mainboard fails to read memory properly which probably indicates that the mainboard needs to be replaced. I however cannot afford to do this so I hope that I can last atleast 2-3 years of my GN4 surviving through Wake Lock. :crying:
Click to expand...
Click to collapse
I really don't think it's an hardware issue but even if so, why this started to happen immediately after the update and why it only happens when the device goes to sleep or when we power on the device.
I also noticed the change on bootloader fonts and interface after the update. I'm suspecting that the problem is there.
Does any one has any thoughts about this?
It's a hardware issue. It's a bad nand issue in fact. You can find Reddit posts a mile long about it.
Anyways it will slowly get worse over time. Had to replace the main-board in my SM-N910W myself.
ciscostud said:
It's a hardware issue. It's a bad nand issue in fact. You can find Reddit posts a mile long about it.
Anyways it will slowly get worse over time. Had to replace the main-board in my SM-N910W myself.
Click to expand...
Click to collapse
Is there any reason at all why it is happening I mean for the nand issue. I don't like the answer that is motherboard fault and we should replace it, which probably means replacing the phone. Is there anyone who can see deeper into the motherboard to find the issue. I also insist that this started to happen immediately after the second MM update.
I still have an IPhone 3G from 2008 and never changed anything on it. Isn't that ironic ?
shpeendi said:
Is there any reason at all why it is happening I mean for the nand issue. I don't like the answer that is motherboard fault and we should replace it, which probably means replacing the phone. Is there anyone who can see deeper into the motherboard to find the issue. I also insist that this started to happen immediately after the second MM update.
I still have an IPhone 3G from 2008 and never changed anything on it. Isn't that ironic ?
Click to expand...
Click to collapse
It was a Bad batch of nand chip that started to go bad after a year or two. Note 4s started to drop like flies before April.
I think your in the 1st stage of Loss and Grief. 1st stage is denial.
If thats so than Samsung should repair our phones under warranty and not tell us we have to pay for the repair coz we installed custom roms.
The Sponge said:
Yes, I'm on the Canadian SM-N910W8 model of GN4.
I've been using the Wake Lock app for a few days now and it works perfectly, if you can get the phone to boot into homescreen that is.
For instance, when the phone shuts off due to low battery or an inevitable crash, sometimes getting the phone to boot up is a real pain in the ass because it doesn't boot up correctly most of the time.
However, one odd fix I've discovered is to put your phone and battery in the fridge for about 2-3 minutes and let it cool down completely. And then magically your phone will boot up properly to homescreen again. Activate Wake Lock and you're pretty much good until the next time your phone shuts off and can't boot. My phone will NEVER boot up to homescreen if it is even slightly hot in temperature. In order to boot, it needs to be cool.
I am highly confident that this is indeed a hardware issue, instead of a software issue. The mainboard fails to read memory properly which probably indicates that the mainboard needs to be replaced. I however cannot afford to do this so I hope that I can last atleast 2-3 years of my GN4 surviving through Wake Lock. :crying:
Click to expand...
Click to collapse
same issue here, exactly as described above...
any way to push Samsung to admit bad batch and fix it for us with no charge?
golden_m said:
same issue here, exactly as described above...
any way to push Samsung to admit bad batch and fix it for us with no charge?
Click to expand...
Click to collapse
I've already swaped a few main-boards. Ive even put a international exynos n910c main-board in a broken canadian snapdragon note 4 and its works perfect.
If anyone needs help just pm me.
ciscostud said:
I've already swaped a few main-boards. Ive even put a international exynos n910c main-board in a broken canadian snapdragon note 4 and its works perfect.
If anyone needs help just pm me.
Click to expand...
Click to collapse
I would be more interested in understanding how come so many Note 4 devices started acting up around same time mark...
This is definitely a hardware problem with the motherboard. Mine started giving the same symptoms 2 weeks after the 6.01 upgrade. Wakelock made it stable but after Samsung replaced the motherboard it is so much faster and no issues at all. I wonder if this is a faulty NAND issue whether the 6.01 upgrade and the way it manages memory could have triggered it. Certainly strange but it need Samsung to fix it.
I am also having same problem.
I was using custom rom and it was working fine without any lag or freeze suddenly one day my Note fall from bed to ground and since then it is not working properly i thought its the ROM so i reverted back to stock MM rom flashed via odin.
Reset everything erased everything but the problem remains same.
At present i am on stock with hardly any apps just FB and whatsapp.
But my device is so slow and keep lagging and sometimes it becomes very hot and restart itself.
I dont know what to do now. i m on 910 G snapdragon.
anasrizvi said:
I am also having same problem.
I was using custom rom and it was working fine without any lag or freeze suddenly one day my Note fall from bed to ground and since then it is not working properly i thought its the ROM so i reverted back to stock MM rom flashed via odin.
Reset everything erased everything but the problem remains same.
At present i am on stock with hardly any apps just FB and whatsapp.
But my device is so slow and keep lagging and sometimes it becomes very hot and restart itself.
I dont know what to do now. i m on 910 G snapdragon.
Click to expand...
Click to collapse
Sorry to hear that, as for now jut install wake lock and enable partial_wake_lock so you can use your device until it fails completely
Mmm. I was thinking to root my phone (4month old still under warranty ) i think i changed my mind after reading this ?. Thank you guy's for the warning
Sent from my SM-N910G using Tapatalk
Same issues, I downloaded the wake lock and so far so good.
I have the same issue also guys and it started a week after updating to Marshmallow.
Phone worked perfectly fine for 2 years prior to this. So I highly doubt its a hardware issue and more likely a software/firmware problem.
Phone seems to have issues whenever the screen is asleep (hence why the wake lock app seems to help with this problem although not a proper solution)
I'm hoping Samsumg can release a patch fix for this as I truly love my Note 4 and would like to keep it for some time yet.
have anybody tried going back to Lollipop?
golden_m said:
have anybody tried going back to Lollipop?
Click to expand...
Click to collapse
I was thinking about that! but I saw on other threads people downgrading with no success.