Database Users

DK28, The Good And Bad

Even though its certain this isn't the official release, I thought we should condense the topics and just post the your thoughts about the good and bad features this update provides.
Ill start..dk28 isn't that awful for me like others. The only problems I've noted was samsung widgets disappearing sometimes, home screen rotation lag, and a few checkers showing up in the browser when zooming in and out.
However, on the bright side, flash is very smooth, and there are better icons
Sent from my SPH-D700 using XDA App

GPS fubared?

No notification when charging usb

Hey guys i recently started having a problem with the back button.it will pick up half the time and then its unresponsive the time any ideas on what i can do?

Probably just lag. Which way did you flash dk28?
Btw, I came up with some other things.
1. Notfications are delayed (ex. Handcents icons in the top bar are sometimes delayed)
2. Keyboard delayed (its actually a bit worse than before)
Sent from my SPH-D700 using XDA App

*Keyboard/touchscreen/captivate button lag/failure to register action/press
*Streaming music skips (last.fm) while doing anything else; like browsing the web.
*Slow orientation change
*No lineout on multimedia dock yet
*None of the unicorns and rainbows flying out of the screen that were promised by the legion of unrelenting froyo fanboys littering this forum for the past month.
Sent from my SPH-D700 using Tapatalk

acer1096xxx said:
Even though its certain this isn't the official release, I thought we should condense the topics and just post the your thoughts about the good and bad features this update provides.
Ill start..dk28 isn't that awful for me like others. The only problems I've noted was samsung widgets disappearing sometimes, home screen rotation lag, and a few checkers showing up in the browser when zooming in and out.
However, on the bright side, flash is very smooth, and there are better icons
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Same here, I guess a few of us got lucky. Just very small things such as checker boarding. I don't have homescreen lagg though, or widgets that disappear.
Sent from my SPH-D700 using XDA App

hardrock121 said:
GPS fubared?
Click to expand...
Click to collapse
GPS actually finally works for me with the update, I'm getting signal indoors in places I hadn't previously and it has yet to time out and require me to reflush the agps data or reboot the phone (used it all day today for work).
dannyzen said:
No notification when charging usb
Click to expand...
Click to collapse
Not seeing this one either, lets me know right away though the notification bar as per usual.
However I am experiencing one very odd piece of behavior, If I open the phone to show the keyboard, turn off the screen and leave it sitting ... the keyboard LED blinks constantly. I'm not sure if it's an app of mine conflicting or froyo itself but it's fairly annoying.

punzada said:
However I am experiencing one very odd piece of behavior, If I open the phone to show the keyboard, turn off the screen and leave it sitting ... the keyboard LED blinks constantly. I'm not sure if it's an app of mine conflicting or froyo itself but it's fairly annoying.
Click to expand...
Click to collapse
That's odd...maybe your phone is actually damaged then
Sent from my SPH-D700 using XDA App

I personally went back to 2.1, rock solid and stable.
On 2.2, Screen rotation is slow as molasses, GPS is stuck on my work location and would not work at all in updating. Browser was a bit slower compared to 2.1. Hated the scattered, non-alphabetical applications folder, wtf?!!
I enjoyed the 2.2 leak but the little niggles weren't enough to stay on it.
I did like the coloured menus, and the ability to turn off 3G when holding the power button for a few secs.

I keep getting errors when connecting to Wifi. I will look down at the phone and wifi will be off even though i never turned it off, and then the notification toggle wont do anything, and when I go into settings to enable it, it says "error" underneath the Wifi entry. Then it takes a few tries to get it connected again.
I do like where Froyo is headed, but this is absolutely no where near polished enough for final release.
Edit: Having a fully working GPS is awesome though. 2 meter accuracy = Awesome.

Does anyone else have lag when trying to adjust brightness on the notification bar?

LordLugard said:
Hated the scattered, non-alphabetical applications folder, wtf?!!
Click to expand...
Click to collapse
If you press menu > edit > menu again, there's an option for A-Z order.
Guess it doesn't matter now since you downgraded, but just thought id let you know.
Edit: lilxflip, yes. I'm getting the same problem but didn't notice that until now
Sent from my SPH-D700 using XDA App

I've noticed since 2.2 that when a caller hangs up, I get a single beep in my bluetooth earpiece confirming that the call has ended, which I like...didn't have any sound before that.

Anyone else having trouble hanging up during a phone call? I hit the damn End button at least 3-4 times before it decides to hang up.

I must be one of the lucky few, everything works great, and not only that it fixed all the issues I had with the previous 2.1 build. I've tried out just about everything I can think of wifi, gps, 4g, pandora, etc.
edit: Should add, I did a factory reset after I installed it, wiped everything the only bit I loaded back in was contacts.

muyoso said:
Anyone else having trouble hanging up during a phone call? I hit the damn End button at least 3-4 times before it decides to hang up.
Click to expand...
Click to collapse
Give the phone a few secs after the screen comes back on then press it. Works fine; if you immediately press it.. it doesn't hangup. Seems intentional..
Umm.. aside from no GPS now which I plan to fix by reflashing di18 then 2.2... I don't find any major problems. The keyboard does have a bit of a registration flaw but not too major..
The leds do light up whenever the screen is off.
And I don't think the brightness sensor likes my room light because it enjoys changing itself a bit.
Sent from my SPH-D700 using XDA App

I'm always weary about doing wipes, so to test if this is true, mid anyone else testing out this also to see if he's right? =P

punzada said:
However I am experiencing one very odd piece of behavior, If I open the phone to show the keyboard, turn off the screen and leave it sitting ... the keyboard LED blinks constantly. I'm not sure if it's an app of mine conflicting or froyo itself but it's fairly annoying.
Click to expand...
Click to collapse
I have noticed the Sammy widget thing and the slow screen rotations but I was intrigued by your bug. So I tried it. Definitely happened. I wouldn't say 'blinks constantly' though. At least not in my case. It flashed on for about 2-3 seconds every 30 or so seconds. Maybe even as long as a minute. Caught me off guard. I watched it for a bit then went back to reading this thread only to have it happen out of the corner of my eye.

kenvan19 said:
I have noticed the Sammy widget thing and the slow screen rotations but I was intrigued by your bug. So I tried it. Definitely happened. I wouldn't say 'blinks constantly' though. At least not in my case. It flashed on for about 2-3 seconds every 30 or so seconds. Maybe even as long as a minute. Caught me off guard. I watched it for a bit then went back to reading this thread only to have it happen out of the corner of my eye.
Click to expand...
Click to collapse
Woah, just tried it. I had similar results. However, I opened the keyboard, let the flash disappear, then 2-3 seconds later it came back. And stayed there too, for about a minute or so!
Not really a big deal in my opinion; I honestly don't use the keyboard often due to its laginess..

[Q] Burned LED flash light?

I've looked around to see if there was a post about this and didn't see it. This is my problem, I was using my phone yesterday as a flashlight for like about 5 minutes when my light just started to dim little by little until it turned off. So, did I just burned my led flash? If so, is there a way to fix or do I just call it in to insurance? Thanks.

Not sure..leds generally flicker before the burn out. They are also rated to handle long cycles....so five minutes should be easy. Bt the circuitry could be burned out. Sounds like this might be a warranty issue.
I did it all from my Nookie...

This same thing just happened to me last night. What happened in your situation?

You arent supposed to leave the app on for over a minute or so. it can burn it out, and/or mess up your whole phone. it can overheat your phone. i would see if there are any other problems with it, and get it returned.

stratax said:
You arent supposed to leave the app on for over a minute or so. it can burn it out, and/or mess up your whole phone. it can overheat your phone. i would see if there are any other problems with it, and get it returned.
Click to expand...
Click to collapse
Wait hold on just one min... so the flashlight app is not safe to use? i think that not right... you're telling me i can't record a Five min video with the LED light on?
level 3 brightness(flashlight app) is what the Recording Cam use

Zephyr757 said:
This same thing just happened to me last night. What happened in your situation?
Click to expand...
Click to collapse
Nothing, I just called it in for warranty. Will be receiving it in just a few days!!!

stratax said:
You arent supposed to leave the app on for over a minute or so. it can burn it out, and/or mess up your whole phone. it can overheat your phone. i would see if there are any other problems with it, and get it returned.
Click to expand...
Click to collapse
Hmmmm.. I don't think this is right. With my myTouch slide, I have successfully had it on for slightly over 15 mins with no damage what so ever. Maybe this one was defective. Otherwise, even on stock rom, the flashlight app wouldn't be there. But I don't know. Maybe like I said, it was defective. Thanks anyways.

Just came from the Zinx CM7 thread where he is warning the torch mode can burn out your LEDs.

dragon4000 said:
I've looked around to see if there was a post about this and didn't see it. This is my problem, I was using my phone yesterday as a flashlight for like about 5 minutes when my light just started to dim little by little until it turned off. So, did I just burned my led flash? If so, is there a way to fix or do I just call it in to insurance? Thanks.
Click to expand...
Click to collapse
i am also facing the same problem. When i try to take a picture, the flash light only works for the first 2 or 3 pictures for the rest it wont flash until i leave it to lie for some time before it comes back and when i try using the torch it turns on bright then as some seconds go by it begins to dim and when i try to use brightlight feature it just flashes and goes offf
Can anyone help me out????

mickeyasamoah said:
i am also facing the same problem. When i try to take a picture, the flash light only works for the first 2 or 3 pictures for the rest it wont flash until i leave it to lie for some time before it comes back and when i try using the torch it turns on bright then as some seconds go by it begins to dim and when i try to use brightlight feature it just flashes and goes offf
Can anyone help me out????
Click to expand...
Click to collapse
Yes your flash is slowing and painfully dying out.
Sent from my HTC One S using Tapatalk 2

dragon4000 said:
I've looked around to see if there was a post about this and didn't see it. This is my problem, I was using my phone yesterday as a flashlight for like about 5 minutes when my light just started to dim little by little until it turned off. So, did I just burned my led flash? If so, is there a way to fix or do I just call it in to insurance? Thanks.
Click to expand...
Click to collapse
I had this problem on my Google Nexus 5X (on stock rom) and I changed it, to bunch of different ROMs and the flash worked on everyone, currently I've got it on some *android 12 AOSP without gapps something like that, maybe you could try to (unlock the bootloader) and then (flash TWRP *custom recovery*) and then go into TWRP and wipe your operating system then flash your choosen custom ROM then see if it works. Also I see that you have gotten one from warranty, that's great! I hope this helps other people, and you also get some new features with those custom ROMs! Or just update your outdated device upto 4 or more version ahead of when it got discontinued, * I'm sending from my LG G8 currently, that I got to try to mod, but cant figure out how to unlock the bootloader, but that's fine its my main device rn, I have a Google pixel 6 pro for that and the Google Nexus 5X )))

LED notifications not working....

Hey all. New Vzw G2 here. I have clean rom on this right now and just loaded up aicp as well and neither rom has working led notifications. The led works it charges red, blinks green on boot up, and flashes white on waking up the screen with double tap.
I have tried multiple notification programs from the play store and tried to test out the led but nothing is working...
Am I just missing something obvious here??
Any help would be appreciated.
Mario
Sent from my VS980 4G using Tapatalk

I know that this sounds like a no-brainer, but we sometimes forget to check the simple things. Check your settings under display and make sure you have the notification switch "on" and then download and try light manager from the play store.

The only thing I could figure out to get LED notifications to work was to use a 4.3 based rom which has the proper API's for notification apps. IMO I traded the IR functionality for one which lets me setup my phone to actually have notifications. No idea what the AICP rom is since I have a D801 and the VSW G2 is all different for whatever silly reason but Light Flow works great on PA.

Thanks all still no such luck. So weird. Enabled and disabled the notification in display tried light manager and light flow still no go. For real I don't get it. I know the light works but only for system notifications like charging battery low knock on etc. SO weird. Grr
Sent from my VS980 4G using Tapatalk

Can you test a different rom?

I've tried aicp and clean and I'll try another here soon. 4.2.2 hasn't worked and an AOSP 4.3.1 hasn't worked I can't figure it out.
Sent from my LG-VS980 using Tapatalk

Could my issues be anything to do with still being on the most recent stock firmware baseband? I have a rule now to never accept OTA updates after my S4 screwed me over. I thought I read there was an OTA for Verizon at some point....
Sent from my LG-VS980 using Tapatalk

Have you tried backing up your data and trying the stock rom? I've also noticed that some things don't function properly on some custom roms, especially if it's not stock. I know you said you've tried other roms, but at this point, it just has to be checked through trial and error.

Make sure Pulse Notification Light is enabled, Use custom values is disabled and Battery Light is disabled. I have Root Mode and Reset color before change enabled on Light Flow and anything else significant disabled.

For the stock rom, Google backup was screwing up with the led notification. I had that problem.
I disabled Google backup and wiped the phone.
During initial boot when it says to back up with Google I deselected it and the led notification worked.
Not sure for custom rom.
Good luck
Sent from my LG-D802 using xda app-developers app

adzam3 said:
For the stock rom, Google backup was screwing up with the led notification. I had that problem.
I disabled Google backup and wiped the phone.
During initial boot when it says to back up with Google I deselected it and the led notification worked.
Not sure for custom rom.
Good luck
Sent from my LG-D802 using xda app-developers app
Click to expand...
Click to collapse
Hmm! Well, I am going to try this. I have plenty of TWRP backups, I'll run a fresh install and see if not using google restore fixes the issue. If it doesn't, I'm STUMPED!
I sure hope it works, this is the ONLY issue I have, I LOVE this phone otherwise, but this is a pretty big issue, I never know when I have messages waiting!
Mario

adzam3 said:
For the stock rom, Google backup was screwing up with the led notification. I had that problem.
I disabled Google backup and wiped the phone.
During initial boot when it says to back up with Google I deselected it and the led notification worked.
Not sure for custom rom.
Good luck
Sent from my LG-D802 using xda app-developers app
Click to expand...
Click to collapse
HOLY CRAP - If I could THANK you a million times I would. Deselecting restore from google WORKED. Booted CleanROM up as a fresh install and tried out the lite version of LightFlow, and BAM, LEDs worked. Must have brought some setting over from all my Samsung devices I owned previous. Never had an issue going from the S3 to Note2 to S4, but going to an LG, must have had issues.
THANK YOU !!!!

desantim said:
HOLY CRAP - If I could THANK you a million times I would. Deselecting restore from google WORKED. Booted CleanROM up as a fresh install and tried out the lite version of LightFlow, and BAM, LEDs worked. Must have brought some setting over from all my Samsung devices I owned previous. Never had an issue going from the S3 to Note2 to S4, but going to an LG, must have had issues.
THANK YOU !!!!
Click to expand...
Click to collapse
Glad that it worked.
Read it somewhere that the backup was the culprit. So the credit goes to the first person that discovered it.
Thank god for xda community and all the sharing .
Sent from my LG-D802 using xda app-developers app

adzam3 said:
Glad that it worked.
Read it somewhere that the backup was the culprit. So the credit goes to the first person that discovered it.
Thank god for xda community and all the sharing .
Sent from my LG-D802 using xda app-developers app
Click to expand...
Click to collapse
Seriously! I was about to try to return my phone, that would have been a hassle and a half. I LOVE my G2, Best phone I've had, I wish there were more cases for it for the Verizon version, I'm a minimalist guy and there is like one case on ebay that fits that bill. Oh I digress!

I switched from GS3 to G2 and let Google restore my settings and apps. My Light Flow (and Light Manager and every other LED app under the sun) just would not work. I just couldn't figure it out... it worked just fine on the GS3.
Finally, after disabling the auto restore of settings and apps, I did a factory restore; and now Light Flow works. Well, my email insists on green rather than the colour I set for it, and I can't seem to get the calendar notification LED working but everything else LED related now seems to work (mostly all 3rd party IM apps) including charging, charged, sms, etc.

Incoming Verizon Update

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.

Display driver issue? fixes?

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