Database Users

TouchScreen issue resolved in gingerbread?

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.

SGS2 sporadically enters car mode

Hi all,
I've used the phone for about six weeks and now it starts to act strangely. Since yesterday it keeps entering car mode sporadically and stars the voice recognition app. A minute ago, it even displayed that it was being charged, even though the charger was not plugged in.
I guess this behaviour us due to dirt in the micro USB jack that has accumulated while carrying the device in my pocket. Possibly, dust particles bridge some of the USB pins and trigger the described functions.
I will try to clean the USB jack and report back. Blowing air over the contacts from my mouth was not sufficient, though.
Has anyone of you experienced such symptoms on your device?
If I can't fix this issue myself, I think I'll have the phone exchanged. Hope, that dust will also reset the custom binary counter, then...
For the record: I'm on Villain Rom 1.4 with CF-Root kernel XKF1.
Greetings

Yeh car mode came on with me after installing villain 1.4
I had other issues also like gmail force closing etc... 1.3 was fine but 1.4 made my phone go a bit cuckoo.
I'm on cognition now but I'll be back on villain at 1.5
Sent from my GT-I9100 using XDA Premium App

So a software problem it is... Couldn't google anything about it. Well, I flashed a stock backup KE2+KF2 CF-Kernel and so far my device behaves as it should. No car mode. I really hope it was a software bug. But it looked so much like a hardware fault...

Not sure if its the same case, but sometimes when I answer calls my phoes goes into loud speaker mode on its own... its annoying.

I had the same problem, but it it resolved itself after a few days. Maybe it is some dirt behind the home button.

It's there again! This time on Darky Rom 2 R1.

Same here. Stock SGS2 KG2 rom. Anyone found a fix for this ?

Had my phone since launch and it started to do this a couple of days ago and also draining the battery within 4 or 5 hours because the cpu was in constant use. Also i couldnt turn the phone off, it would just reboot and wouldnt charge. I had the same theory about the usb jack but didnt seem to make any difference. I did a hard reset but the problem was still there, strangely the phone appears to have sorted itself out not and is running fine!
Sent from my GT-I9100 using XDA App

There is other thread
Read here
http://forum.xda-developers.com/showthread.php?t=1132588&page=2

thinks its charging....

so i've noticed multiple times today (just got it yesterday, rooted) that the charging indicator flashes on and off. this keeps bringing it out of standby. although sometimes the screen turns on without it saying charging but that seems to be a known issue.
but whats up with the charging flashing

full reset and its still doing it
actually i think it has to do something with rooting
i used this http://androidflip.com/how-to-root-acer-iconia-a500-with-stock-honeycomb-3-1/
but i unrooted and uninstalled and its not doing it now....
any other root method for 3.1?

Strange
Never had this issue on my a500 - but have the exact same issue on my Samsung Intercept with a slightly damaged charging port - after unplugging the system will still show as charging and offer to mount as an external storage device - even though it's not plugged into anything.
Had the random screen on when I was still on a 3.0 based rom - have you registered your tablet with Acer and upgraded ota to 3.1? Can also manually flash 3.1 update.
best of luck!

i just updated my last post,
but yeah im on the latest ota 3.1 in the US and registered

lbhocky19 said:
full reset and its still doing it
actually i think it has to do something with rooting
i used this http://androidflip.com/how-to-root-acer-iconia-a500-with-stock-honeycomb-3-1/
but i unrooted and uninstalled and its not doing it now....
any other root method for 3.1?
Click to expand...
Click to collapse
Yes! Easy as hell too.
Check this out, and good luck!
(How to root a500 3.1 stock)
http://forum.xda-developers.com/showthread.php?t=1138228
(Edit: the method you linked to looks like the same method described here at XDA. May not solve your problem)

well cancel my happiness. did a reboot and now it fully thinks its charging. no flickering.
even plugged it in and unplugged and still says charging.
this time i plugged it in and rebooted. at least the notification went away
edit: and its back.

really strange....
May want to just return it and snag a new one if that is easy/possible.
After your full reset did you do any Modding/install any apps? May be possible something you are running is causing the issue, but I am really stumped on this one.
Could always get cwm running and reset the battery cache, but I am pretty doubtful that is gonna do anything.

same problem for me here.though I did not root my device yet.it shows charging with no charger plugged in.also recognized that my battery indicator sometimes remains on a certain percentage and hangs.after a restart it shows the actual battery level.I am on stock rom 3.0.1...maybe I send it back tomorrow.because this is really enoying...

yup. mine just started doing the hanging at one percentage til reboot

don´t know if it´s software or even hardware related

the fact that we have identical problems makes me think software

earphone jack issue?

So, i was having some issues with the earphone i had bought recently, but having a few problems with the same brand sometimes earlier (microsoft really put up a really interesting choice with the low price and really good bass and sound quality for its pricing, but damn, those things had caused me two replacements in earlier models) i was considering taking it to the warranty and getting a new one, fine.
Then i got the moto earphone (had never used it, was in that plastic thingy yet) to get me through the day and i put the ms one in the bag, but when i started walking, the same problems appeared. The volume would get lower, sound getting distorted, and the song started to cut to the point it would recognize as if the headphone has been unplugged and i have to start the music again. i'm no expert but i think we've got some issues here son
I went to master google in search for answers and i've found that people have been having these kinds of issues since the first generation moto g, some even got a replacement and the jack would still come faulty, there were a major "consent" that the fault was the pocket lint inside, and cleaning it would solve the problem, but my phone doesn't have even two goddamn weeks, it didn't even had time to get dirty. (and i tried it cleaning, only a lil hair came out) I am currently listening to music, and it's perfect, when the phone stays still. If i start moving it around or mess with the connector, the issues come back again.
Does someone had this problem here too? found some solution besides the pocket lint thing? i didn't found any post here on xda related to that, and i really don't wanna send it ro warranty 'cause i need it really bad for my work, and i know it's gonna take some time in there, the problem can even come back...
Please, show me a light.

I have a problem where moving the headphone jack a small amount would stop music playback its so annoying. I mostly use Bluetooth headphones though.

george241312 said:
I have a problem where moving the headphone jack a small amount would stop music playback its so annoying. I mostly use Bluetooth headphones though.
Click to expand...
Click to collapse
Moving it also distorts the sound to the point it stops. Normally this happens with detective earphones, but the jack is new to me.

I'm sure it's the jack, I just got new headphones too. What you can do is expand that contact strip in the jack inward, hence better contact? I haven't done this yet though

bestofrhcp said:
I'm sure it's the jack, I just got new headphones too. What you can do is expand that contact strip in the jack inward, hence better contact? I haven't done this yet though
Click to expand...
Click to collapse
yea, it is the jack indeed... are you facing this problem too?
i tried pulling it out a bit, but no results. Some random "solutions in the internet tell to put something behing that first metal contact strip... it that so?

So I kinda solved the problem these days... I bought a tpu case, and it has stopped. I guess that the phone is too slim, and it keeps banging in the pocket, making the jack loose and stopping the song. Now the phone is kinda bulky, fits right in the pocket, I can even run with it and the sound is still perfect. Sad that I gotta use this case, makes the phone Hella ugly, but yeah, I solved the problem
If anyone is facing it, try this, might work for you too.

Fixed my problem
I'd just like to add that I also suffered from this same issue (to the letter, volume decrease, distortion and all). It happened once a few weeks in but now, a few months later, it was happening so often that I had to give up using headphones.
Well, here's the thing: I contact Motorola and they give me the old crap about rebooting in safe mode and testing, or doing a factory reset.
As I KNOW this is a hardware issue, I just go ahead and reinstall the factory image (I was previously rooted) planning to send it in for repair/replacement: low and behold: it's fixed. So installing the original firmware and going through the setup (but choosing not to reinstall all my apps -new device option) fixed the problem. I have no idea how this can be. Maybe an app made the phone react too much to slight disturbances in the connection? When I have time, I'll be restoring my backup to see if the problem comes back, and uninstall apps one by one (starting with the xposed modules and other root apps).
I've been using the headphones a lot in the past 5 days with absolutely no issues.
tl:dr OP's exact problem, what seemed like a hardware fault, was fixed by a factory reset.

bv90andy said:
I'd just like to add that I also suffered from this same issue (to the letter, volume decrease, distortion and all). It happened once a few weeks in but now, a few months later, it was happening so often that I had to give up using headphones.
Well, here's the thing: I contact Motorola and they give me the old crap about rebooting in safe mode and testing, or doing a factory reset.
As I KNOW this is a hardware issue, I just go ahead and reinstall the factory image (I was previously rooted) planning to send it in for repair/replacement: low and behold: it's fixed. So installing the original firmware and going through the setup (but choosing not to reinstall all my apps -new device option) fixed the problem. I have no idea how this can be. Maybe an app made the phone react too much to slight disturbances in the connection? When I have time, I'll be restoring my backup to see if the problem comes back, and uninstall apps one by one (starting with the xposed modules and other root apps).
I've been using the headphones a lot in the past 5 days with absolutely no issues.
tl:dr OP's exact problem, what seemed like a hardware fault, was fixed by a factory reset.
Click to expand...
Click to collapse
Now that was unexpected lol. Anyways, thanks for the reply, i've seen much of this kinds of problems on the internet, but none of it came to a conclusion, the posts die after sometime. I hope someone finds the answer in your reply.
So, i bricked my phone sometime ago and installed the factory image. i've been using the tpu case since it came, as i stated before, it has solved my problems (i think mainly because the phone get bulkier, fits into the jeans pocket and stop moving, so the jack isn't affected by any kind of movement and it works perfectly), but after you said that i recalled, there was one day when i forgot the case at home, and unaware of that i went working with the headphone and it worked perfectly, i just noticed i had forgot the case in my way home. I'll do some further testing without the case, but your solution might just have hit the right spot.

guile50 said:
Now that was unexpected lol. Anyways, thanks for the reply, i've seen much of this kinds of problems on the internet, but none of it came to a conclusion, the posts die after sometime. I hope someone finds the answer in your reply.
So, i bricked my phone sometime ago and installed the factory image. i've been using the tpu case since it came, as i stated before, it has solved my problems (i think mainly because the phone get bulkier, fits into the jeans pocket and stop moving, so the jack isn't affected by any kind of movement and it works perfectly), but after you said that i recalled, there was one day when i forgot the case at home, and unaware of that i went working with the headphone and it worked perfectly, i just noticed i had forgot the case in my way home. I'll do some further testing without the case, but your solution might just have hit the right spot.
Click to expand...
Click to collapse
Did you, by any chance, have GravityBox installed on your phone when it was playing up? Also/or, where you using an unmodified ROM, as that's what I'm using usually (deodexed but stock) I've just restored my backup (that's rooted and has a few xposed modules on) and sure enough first time I touch the jack with music playing, it plays up (this time it triggered the voice command, which it did do some times). So I think to start by disabling GravityBox as that modifies a lot of stuff... Reboot, and the damn thing seems to work perfectly, I'm tugging and pulling at the jack right now and it's working perfectly.
I find it a bit too much to believe, and I don't want to lose GravityBox as that's a big reason I root.
One explanation I can come up with is that Motorola saw there was a problem and they fixed it in software, and installing AOSP or GravityBox that changes system files, gets rid of that software "fix".

bv90andy said:
Did you, by any chance, have GravityBox installed on your phone when it was playing up? Also/or, where you using an unmodified ROM, as that's what I'm using usually (deodexed but stock) I've just restored my backup (that's rooted and has a few xposed modules on) and sure enough first time I touch the jack with music playing, it plays up (this time it triggered the voice command, which it did do some times). So I think to start by disabling GravityBox as that modifies a lot of stuff... Reboot, and the damn thing seems to work perfectly, I'm tugging and pulling at the jack right now and it's working perfectly.
I find it a bit too much to believe, and I don't want to lose GravityBox as that's a big reason I root.
One explanation I can come up with is that Motorola saw there was a problem and they fixed it in software, and installing AOSP or GravityBox that changes system files, gets rid of that software "fix".
Click to expand...
Click to collapse
Well, try to trigger the problem a couple of times with gravity box installed. I don't have it, installed xposed once and had major lag, stuttering and FC problems, then i took the ting off. Didn't test the jack thing, but i've never been a hard xposed user.
I really think my problem is hardware-related, but tonight i'll head home without the case and report back here.

If I am on a stock Moto ROM, I have the problem. When I moved to AOSP/CM based ROM's, I can manipulate my headphones without causing it to stop.. I think maybe the stock kernel is a bit too sensitive and stops it with just a little bit of disconnection vs a more lax implementation in AOSP/CM...

So I've ran my tests: climbed stairs, climbed down stairs, run a Lil bit, shake my hips (they don't lie) and messed around my pocket: no sign of Jack problems. I guess that flashing stock firmware again did the job, as you have stated earlier. I'm going to stop using the case and go jogging, or going more often to work listening to music without it, but after today field tests, I'm sure the issue is gone.

guile50 said:
Well, try to trigger the problem a couple of times with gravity box installed. I don't have it, installed xposed once and had major lag, stuttering and FC problems, then i took the ting off. Didn't test the jack thing, but i've never been a hard xposed user.
I really think my problem is hardware-related, but tonight i'll head home without the case and report back here.
Click to expand...
Click to collapse
Just an update: I give up. I've tried multiple things, including almost bricking my device. I cannot find something definite at all. Installing a clean factory image (or a rom that has not been changed much) will get rid of the problem, even with root. However after restoring my TitaniumBackup of about 140 apps, the problem came back for a while. I noticed it after enabling MotoVoice, so I disabled moto voice and it disappeared, but then re-enabling moto voice didn't make the problem come back... And that is why I give up. I've ordered a pair of Bluetooth headphones.

I think that flashing the stock firmware again is the ultimate solution to solve the problem. After some tests I really couldn't trigger it again, so I guess that's the end of it
The problem is that the issue is so random I can't seem to find a proper way to trigger or to say it is 100% solved. I've read about it happening since the first generation moto g, seems like a hardware issue, but...

My headphone jack wont work properly when i insert the headphones into the jack completely but it works fine when i pull out a lil of the pin of headphones out of the headphone jack whats the deal its too annoying
Moto x 2013 verizon

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