Database Users

[Q] After booting in to android my phone just vibrats and shuts off?

I dont understand i have tried everything! I must be missing something
I have booted before with no problems aside from the robo voice
I come home in hopes to fix it and now no matter what build i use no matter what zimage i use the phone boots like normal in to Android and then just shuts down.... What am i missing here?

Spent all Morning Flashing rom and radio combos and still the same thing, Reformatted my sd card Nothing.
NO HELP?

this happened to me when i started using my extanded battery, no matter what i did it boots vibrates then shuts, im back to my normal battery all the builds work now, i figured out that the extended battery might need a driver or something.

here the same! with original battery is working
With extanded battery is shutting down! in one line by booting with haret
Chragin off (temp overheat)
battery working with
desirebuild_v5
battery dosent work with
mattcfroyorc1.4
mattcfroyorc1.3a

Wow never even thought about changing back to a stock battery. Or even mentioning that i again

This happened to me when I had a multi-boot program installed on the winmo side. Uninstalled it- booted just fine.

there have been a couple of threads with the same issue.. the devs have been asked about it.. nothing heard back as yet.. but it definitely it is an extended battery that is causing it

Yes the extended battery is it. I read it somewhere in the forums that it is not supported yet as there are no drivers and due to which while booting haret reads the battery temp to be 90 while it actually being ~30 and hence cant boot.
Replace it with stock and you are good to go

Mine is still the stock battery and still does the same thing for all versions of ROM and android too..

kingfisher1111 Mine is still the stock battery and still does the same thing for all versions of ROM and android too..
Click to expand...
Click to collapse
Are you using the stock HTC battery cuz im sure if the exteneded one dont work neither will cheap replacment batteries
Works great with my stock battery;
Never thought in a million years to try without extended battery lol
Only thing now i have to do is get over the robo voice.

nardone24 said:
Are you using the stock HTC battery cuz im sure if the exteneded one dont work neither will cheap replacment batteries
Works great with my stock battery;
Never thought in a million years to try without extended battery lol
Only thing now i have to do is get over the robo voice.
Click to expand...
Click to collapse
yes mine is original battery that came out of box with Tmobile..
Any one help me on this issue?

[POSSIBLE FIX] Random Rebooting! Grr

***EDIT***
Well it would seem like my random reboots have gone away. Thanks to Tubgirl for the suggestion, but using Hastarin's 7.5R kernel with NO overclocking, AXI etc, it's finally stable once again.
In fact, I used that kernel with Darkstone's latest 3.2 build and the battery is crazy. I am getting approximately 7 hours of battery life for every 10% of the battery. That's with BT, data and all syncing turned on and basic use. That's around 3 days of life for a light user. Didn't even get that with winmo!
So for me - the moral of the story is stick to the clean, non overclocked kernels. As for speed, I cannot tell the difference (I don't play any games to be fair though).
***END***
For some strange reason, my phone randomly reboots at completely bizarre intervals when running Android. I can't put my finger on what it might be. So some questions!
- Does anyone else experience this?
- I'm running VBN RC3 Minimal WM ROM, might it be this?
- I'm running the 2.14 Radio is it this?
- I'm running mostly Mdeejay builds could it be them (happens with all of the one's I've tried)?
- Is it likely to be piece of android software?
- Is there any way I can find a log to see why it's rebooted?

Random Reboots
I have been experiencing this problem for about a month now. I have tried numerous roms and android combinations, as well as changed radios. The problem still returns no matter what combination I try. So I'm kind of

Could be a problem with your battery. Try replacing it.
Sent from my HD2 using XDA App

i had same problem.. what i did was fully drain my battery, than recharged it fully on off mode, with cable plugged in turned it on that charged again till i saw green LED light
since than it worked nicely no random boot
give it a shot id say
cheers

My HD2 has never done it, but my mates has.
He contacted HTC on Thursday and they are repairing it under warranty.
It is a well known issue that affected around 3000 handsets in the UK apparently. They call it the "heat related reboot", and it involves replacing the motherboard and another component.
His has gone back, they sent a courier to collect it..

Mine has been randomly rebooting for about 2 weeks now.
It usually happens once a day when running Winmo or Android. Sometimes when it reboots I get a rectangular box across the bottom of the screen for about a second. I dont know if this is caused by the Radio Rom update or it is just coincidence.
I have swapped the battery but it has made no difference.
It's driving me mad.

deadey3 said:
i had same problem.. what i did was fully drain my battery, than recharged it fully on off mode, with cable plugged in turned it on that charged again till i saw green LED light
since than it worked nicely no random boot
Click to expand...
Click to collapse
Thank you I will try this first!
stratplayer said:
My HD2 has never done it, but my mates has.
He contacted HTC on Thursday and they are repairing it under warranty.
It is a well known issue that affected around 3000 handsets in the UK apparently. They call it the "heat related reboot", and it involves replacing the motherboard and another component.
His has gone back, they sent a courier to collect it..
Click to expand...
Click to collapse
I have sent them an e-mail describing my issue, quoting you I will see what they say. Hopefully they will sort it soon because my first year of warranty expires in one month!

Oh also, if I send it back for warranty, I suppose I'll need to revert it back to the 02 defaults and remove all traces of HSPL! Is this possible?

i have this problem too, under android and wm. Still testing to find out hwats causing it but looks more and more a heat issue, eventhough it does not heat that much.
unfortunately dont have warranty so not sure what i can do.
when i have an audio or video stream, or navigator thats when it happens mostly. but i had random reboots as well for no reason.
is there something on WM we can use to find out whats making it reboot?

i get this issue every once in a while when i go to sleep and wake up and its booted up in windows? its happened about 2 or three times but doesn't happen every day.

Me too!
I'm also experiensing this. It started just when the whole android hd2 thing started. I have this problem no matter what radio/rom I'm using (except from stock). Reboots in win. Android gives SOD/reboots. I've tried some reasearching in to this and found out that when I flash back to original rom/radio it's stable. Between every flash i do Task29.
I've tried different memory cards and even swapped the battery with a collegue.
Still the same. Funny thing if it suddenly are many people experiensing this problem..
Could it have something to do with android experiments?
Bad thing is that it would be difficult to send it in for repair since it's working with original rom/radio.
You should all try to flash a stock radio and rom to see if it still reboots.. Mine don't..

jonboyuk said:
Oh also, if I send it back for warranty, I suppose I'll need to revert it back to the 02 defaults and remove all traces of HSPL! Is this possible?
Click to expand...
Click to collapse
Yea there is way, google "how to remove HSPL" eventually it will bring u to xda thread and if ur not sure YouTube it there is heaps of floating around

jonboyuk said:
For some strange reason, my phone randomly reboots at completely bizarre intervals when running Android. I can't put my finger on what it might be. So some questions!
- Does anyone else experience this?
- I'm running VBN RC3 Minimal WM ROM, might it be this?
- I'm running the 2.14 Radio is it this?
- I'm running mostly Mdeejay builds could it be them (happens with all of the one's I've tried)?
- Is it likely to be piece of android software?
- Is there any way I can find a log to see why it's rebooted?
Click to expand...
Click to collapse
I use the same VBN ROM but this build [build]20.09.10||JDMS 1.3|FRF91 Latest Stable Nightly||RC11 WITH AXIS! and Radio 2.12. I dont have any problem (reboot, sleep of dead, no robot voice...)

I switched to the latest hyperdroid v1.6 and have not had this problem yet although It did happen to me a lot when I was running different builds (cant remember which ones sry) Try switching builds and also make sure you turn everything off in WM like bsb tweaks and radio all that stuff. Its weird but it helps considering that everything gets turned off when u hit clrcad.exe anyways but it has helped the stability of my builds.

Alot of us seems to get these reebots in win also...

I wonder if it's got anything to do with the overclocking with setcpu? Hmmmm....

i had this exact same issue , bought phone of eBay so had no proof if purchase . phoned htc they said its 100% covered under warranty , they had it back for repair for 5 working days . they also replaced the external casing as it had a few chips from a drop , they pretty much returned a brand new phone apart from the serial number sticker tomtom no longer recognised the device id so i had to reactivate my maps , so they have at least replaced the mainboard . top customer service ! give them a ring its worth a try they can only say no

herukano said:
i had this exact same issue , bought phone of eBay so had no proof if purchase . phoned htc they said its 100% covered under warranty , they had it back for repair for 5 working days . they also replaced the external casing as it had a few chips from a drop , they pretty much returned a brand new phone apart from the serial number sticker tomtom no longer recognised the device id so i had to reactivate my maps , so they have at least replaced the mainboard . top customer service ! give them a ring its worth a try they can only say no
Click to expand...
Click to collapse
nice is there a way to check warranty online? i also bought it from ebay? where you located?

i'm also experiencing this random reboot phenomenon.. happened only after i started experimenting with Android on my HD2.. now the reboot issue happens with WinMo as well.. i've been using the same radio, ROM and same builds..
btw, since jonboyuk mentioned it, i did play around with "setcpu".. could this be the culprit??

Hello..
I've noticed that my HD2 also reboots sometimes in Android. I haven't used WM for a long, so I really don't know if it also reboots in WM. My question is though, is this a hardware issue? Never had this sorts of reboots before starting this Android @ HD2 game. An answer (or just a thought) to this question, will help me, since I have to send my HD2 for a repair tomorrow, cause the microUSB slot is broke. But if the reboot issue is a hardware fault, then I should also report that, to the repair center.
Thanks.

[Q] i9500 randomly reboots, wifi doesn't work and other problems

Hi, I bought my GS4 i9500 around 2 months ago, and few days ago while I was listening to music, someone called me and I noticed that the phone was a bit hot. I'm not exactly sure that that was the source of this problem.
Anyway, when I put the phone down, it didn't work, and after a few seconds it rebooted.
Ever since it rebooted it keeps doing problems - it reboots once in a while, the wi-fi doesn't work, and the touch is delayed sometimes (it doesn't respond for a while, and after a few seconds it suddenly responds to all the gestures I did over the last few seconds.).
I tried factory resting it, change frimware, clear cache and everything, and still nothing worked. It still does these problems.
I took it to the store where I bought it and they flashed it, and still it didn't solve it.
The problem is I rooted the phone, and I'm afraid the warranty won't be accepted if I send them the device.
Anyone knows what the problem might be?
Sorry for my bad English.
Thanks.

It worked for me to go fully back to stock. Maybe give that a shot,

Tunestwo said:
It worked for me to go fully back to stock. Maybe give that a shot,
Click to expand...
Click to collapse
If you mean by that to flash the original frimware, i've already tried that..
Any other ideas?

Danieliko said:
If you mean by that to flash the original frimware, i've already tried that..
Any other ideas?
Click to expand...
Click to collapse
Noop, sorry man. when i did go fully back to stock it went off... i think its a warranty problem here.

well, i'm currently dealing with the problem too, it automatically boots itself, my reception goes off, eventough im not in a dead spot. but: it only happens if im on ~20% battery. i think its a softwaresided problem. im running on the normal stock touchwiz with android 4.2.2.
im gonna send it to the operator, maybe it really is a warranty-sided problem.

irot3k said:
well, i'm currently dealing with the problem too, it automatically boots itself, my reception goes off, eventough im not in a dead spot. but: it only happens if im on ~20% battery. i think its a softwaresided problem. im running on the normal stock touchwiz with android 4.2.2.
im gonna send it to the operator, maybe it really is a warranty-sided problem.
Click to expand...
Click to collapse
Sent to operator, unfortunately the warranty has been expired (probably because I rooted), and they want ~450$ to repair it..
Hopefully ill find some solution.

Danieliko said:
Sent to operator, unfortunately the warranty has been expired (probably because I rooted), and they want ~450$ to repair it..
Hopefully ill find some solution.
Click to expand...
Click to collapse
~450$ suggest to get new one , when device reboot see if the battery temperature maybe the wrong with battery I was have the reboot problem and fixed with replace battery and reinstall full rom.
my rom is UBMG9

d34dlym4n said:
~450$ suggest to get new one , when device reboot see if the battery temperature maybe the wrong with battery I was have the reboot problem and fixed with replace battery and reinstall full rom.
my rom is UBMG9
Click to expand...
Click to collapse
I'll try that, thanks

[Q] Fast battery discharge

My Nexus 4 is just over a year old. It has been performing really well throughout this period. A month back, the soft buttons on the screen stopped working and I got the screen replaced. The phone was working very well even after this. I am running only the stock Android. I haven't rooted the phone yet.
Over the last few days, the battery discharge has been fast and unpredictable. I have attached the Battery screenshot. I shall explain the sequence of events to describe the screenshot.
The battery goes from 40-50 to 0 in one go! (the first downward steep drop). Phone had already switched off. I connected it to a charging point and restarted the phone.
While the phone was being charged (the slow upward red slope), I did some research on this. Since, Google Play Services was consuming most of the battery, the following solution seemed to be good to follow.
(Disable Hangouts, sign out of Google+, turn ON Location Reporting, reboot, then reenable Hangouts and sign back into G+),
I tried this. Once I rebooted, the battery power was 56% !! (The steep upward climb)
I used it for some time. And kept it on charge to charge it completely. But after some time, the battery charge dropped to 19% (the second drop in the screenshot). I rebooted the phone again. And this resulted in the next battery charge spike upto 45%!!
I tried searching for Hangouts app or Google+ app on the phone. But they no longer exist in the app drawer.
Is this a battery issue? Or some software issue? Should I try a factory reset?
Edit1: Added a larger image of the battery stats.
------
An avid Nexus 4 fan !!

That is some really strange behavior. It either can be a software or a hardware issue.
You may do a factory reset and install a factory image. Be sure that you charge your batterie to maximum first before doing the reset. If there is still this drops than it mostly is a hardware issue. Replacing the batterie could help.
Also a huge N4 fan. High five for that! ;D

CCody said:
That is some really strange behavior. It either can be a software or a hardware issue.
You may do a factory reset and install a factory image. Be sure that you charge your batterie to maximum first before doing the reset. If there is still this drops than it mostly is a hardware issue. Replacing the batterie could help.
Also a huge N4 fan. High five for that! ;D
Click to expand...
Click to collapse
Yes. Concerned about the battery
I havent rooted the phone. Would I need to do that for installing a factory image?
P.S. I have added another image with a better depiction of the battery behavior.

harishvr9 said:
Yes. Concerned about the battery
I havent rooted the phone. Would I need to do that for installing a factory image?
P.S. I have added another image with a better depiction of the battery behavior.
Click to expand...
Click to collapse
You just need an open bootloader. Root is not required.

CCody said:
You just need an open bootloader. Root is not required.
Click to expand...
Click to collapse
Wouldn't a simple factory reset from the phone's menu suffice? What is the difference?

Like I said before, try a normal factory reset first and if this does not work then flash a factory image. In the most case a normal factory reset will do.
The difference between a reset and a factory image is like a white shirt you are washing. A reset is like putting this shirt in the washing machine if it has stains. It will be white and clean again. But after some time those stains wouldn't go away completely and your white shirt isn't that white like before anymore. Flashing a factory image will be like buying a new white shirt.

@harishvr9: If you want to be 100 sure it is not a software issue, you should flash the latest factory image on your phone with fastboot. For this, you will need a working fastboot or (Android SDK) on your computer, the N4 factory image from HERE and being able to boot into bootloader mode (VolDown+Power).

Erovia said:
@harishvr9: If you want to be 100 sure it is not a software issue, you should flash the latest factory image on your phone with fastboot. For this, you will need a working fastboot or (Android SDK) on your computer, the N4 factory image from HERE and being able to boot into bootloader mode (VolDown+Power).
Click to expand...
Click to collapse
Thanks !! I am sure there would be a thread on XDA to guide me on this!

harishvr9 said:
My Nexus 4 is just over a year old. It has been performing really well throughout this period. A month back, the soft buttons on the screen stopped working and I got the screen replaced. The phone was working very well even after this. I am running only the stock Android. I haven't rooted the phone yet.
Over the last few days, the battery discharge has been fast and unpredictable. I have attached the Battery screenshot. I shall explain the sequence of events to describe the screenshot.
The battery goes from 40-50 to 0 in one go! (the first downward steep drop). Phone had already switched off. I connected it to a charging point and restarted the phone.
While the phone was being charged (the slow upward red slope), I did some research on this. Since, Google Play Services was consuming most of the battery, the following solution seemed to be good to follow.
(Disable Hangouts, sign out of Google+, turn ON Location Reporting, reboot, then reenable Hangouts and sign back into G+),
I tried this. Once I rebooted, the battery power was 56% !! (The steep upward climb)
I used it for some time. And kept it on charge to charge it completely. But after some time, the battery charge dropped to 19% (the second drop in the screenshot). I rebooted the phone again. And this resulted in the next battery charge spike upto 45%!!
I tried searching for Hangouts app or Google+ app on the phone. But they no longer exist in the app drawer.
Is this a battery issue? Or some software issue? Should I try a factory reset?
Edit1: Added a larger image of the battery stats.
------
An avid Nexus 4 fan !!
Click to expand...
Click to collapse
Same symptoms.
http://forum.xda-developers.com/nexus-4/help/nexus-4-sudden-signal-loss-battery-t2797981

Erovia said:
@harishvr9: If you want to be 100 sure it is not a software issue, you should flash the latest factory image on your phone with fastboot. For this, you will need a working fastboot or (Android SDK) on your computer, the N4 factory image from HERE and being able to boot into bootloader mode (VolDown+Power).
Click to expand...
Click to collapse
@CCody and @Erovia .. pls Help ..
I unlocked the bootloader. But when I am trying to flash the factory image via flash command i get this response.
""flash is not recognized as an internal or external command, operable program or batch file".
What did I do wrong? Fastboot.exe is there in the sdk/platform-tools folder.
Now I am stuck on the "Lock State - Unlocked " screen
Edit - Got it working !! Thanks a ton! Will report whether it worked or not

@harishvr9: The easiest way is to run the flash-all.bat (on Windows) or the flash-all.sh (Linux/OSX). It will flash the bootloader, the radio, reformat your partitions and copy the files on them.

Erovia said:
@harishvr9: The easiest way is to run the flash-all.bat (on Windows) or the flash-all.sh (Linux/OSX). It will flash the bootloader, the radio, reformat your partitions and copy the files on them.
Click to expand...
Click to collapse
Thanks!! Got it working somehow. Will update about the performance by tomorrow.

Damn, I am a bit late. I am sorry for that.
Let us stay updated in any cases!

CCody said:
Damn, I am a bit late. I am sorry for that.
Let us stay updated in any cases!
Click to expand...
Click to collapse
@Erovia and @CCody
I am back with an update. I had installed the factory image of 4.4.3 stock android. The system notified me about an update and the notification was lingering on the screen. So I ran the update. The weird thing was that the battery was at 85% before it restarted. After it updated and rebooted, the battery was at 36%!
Now what does this infer? Battery issue? Or 4.4.4 update issue?
Thanks in advance for the support !!

Why didn't you flash the 4.4.4?
Anyway, charge it to 100% and see what happens.

harishvr9 said:
@Erovia and @CCody
I am back with an update. I had installed the factory image of 4.4.3 stock android. The system notified me about an update and the notification was lingering on the screen. So I ran the update. The weird thing was that the battery was at 85% before it restarted. After it updated and rebooted, the battery was at 36%!
Now what does this infer? Battery issue? Or 4.4.4 update issue?
Thanks in advance for the support !!
Click to expand...
Click to collapse
I would suggest to try this ROM out for a few days and if this issue still occurs, than it is no doubt this is a hardware issue.
Have you already charge your batterie to maximum once?

CCody said:
I would suggest to try this ROM out for a few days and if this issue still occurs, than it is no doubt this is a hardware issue.
Have you already charge your batterie to maximum once?
Click to expand...
Click to collapse
Doing it now. Will leave it without charge overnight to see how it fares. Tomorrow is gonna be a long day. The battery better stay with me !

harishvr9 said:
Doing it now. Will leave it without charge overnight to see how it fares. Tomorrow is gonna be a long day. The battery better stay with me !
Click to expand...
Click to collapse
May the amp will be with you, mate. :good:

harishvr9 said:
@Erovia and @CCody
I am back with an update. I had installed the factory image of 4.4.3 stock android. The system notified me about an update and the notification was lingering on the screen. So I ran the update. The weird thing was that the battery was at 85% before it restarted. After it updated and rebooted, the battery was at 36%!
Now what does this infer? Battery issue? Or 4.4.4 update issue?
Thanks in advance for the support !!
Click to expand...
Click to collapse
Why didn't you flash to 4.2.2 and waited for couple days. All of us that have same problem like you got it after 4.4.3
Sent from mobile

Rajnus said:
Why didn't you flash to 4.2.2 and waited for couple days. All of us that have same problem like you got it after 4.4.3
Sent from mobile
Click to expand...
Click to collapse
Did you mean to say 4.4.2 or 4.2.2 ? Guess 4.4.2 ran well on my device.

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