Database Users

[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 )))

Slider unlock sometimes doesn't work with incoming call

Once in a while when trying to answer an incoming call the unlock slider won't respond. I will slide my thumb to unlock and ...nothing. When this happens the call will just go to voicemail . The workaround is to touch the power button to turn off screen , then touch it again to wake it up ,then the slider will work and I can answer the call. Sometimes this takes too long and I miss the call.
This is not a deal-breaker as it only happens 5% of the time , still it is annoying. I have tried different roms with no real difference. Anybody else have this problem? Any advice other than get a new phone under warranty?

Ditto. And I always act as you did to work around the issue, only difference is, I haven't missed a call due to this.
In any case, based on experience, the chance of this happening could be minimized (if not eliminated) by always locking the phone from the "desktop" (e.g. do not lock the phone when an app is running).
BACK STORY:
I remember this happening (more than once) when someone called me up after a train ride. And the last thing I could recall is that I have locked the phone while playing Angry Birds / Fruit Ninja / Zenonia 2, etc.
But it still sucks that it happens.

I guess my real question is , are all Nexus s doing this sporadically , even rarely , or is my phone defective?

question... are the phones plugged in to a wall charger when this happens?

Nope. Only happened to me when I under clocked the CPU with Setcpu using the powersave profile (I was just testing things out).

DKYang said:
Nope. Only happened to me when I under clocked the CPU with Setcpu using the powersave profile (I was just testing things out).
Click to expand...
Click to collapse
can happen any time any place

ransome7 said:
I guess my real question is , are all Nexus s doing this sporadically , even rarely , or is my phone defective?
Click to expand...
Click to collapse
I'm not sure if everyone's having this, but I'm with you on this. I'm on stock but rooted 2.3.3. Experienced this since 2.3.1.
EDIT: My wife has this problem too, since 2.3.1 until 2.3.3 (not rooted).

cygnum said:
I'm not sure if everyone's having this, but I'm with you on this. I'm on stock but rooted 2.3.3. Experienced this since 2.3.1.
EDIT: My wife has this problem too, since 2.3.1 until 2.3.3 (not rooted).
Click to expand...
Click to collapse
Mine did it stock , I rooted and loaded roms to see if that would fix the problem , lessened but still there

My nexus s (i9020T) has exactly the same problem. I've also tried to flash different ROMs, including CM-7rc2 and stock 2.3.3, and the problem remains.
I tried to bind Multi-touch Visualizer 2 to long pressing home button, and found the when screen is unresponsive, it can still detect press near edges very well, but not the center. While I press at the edge and drap across the center, it keeps tracking my finger correctly. In addition, Locking and unlocking the screen can solve the problem temporally. I connect my phone with adb, and tried to "cat /dev/input/event0" The behavior confirms what I see in Multitouch Visualizor 2: the when the center of screen is unresponsive, nothing can be read from the device node.
I read the mxt224 touch screen controller doc, and it seems the chip features self-calibration, and thus I believe the "lock & unlock" will trigger the chip to tune it self in some way. I've also read the driver code of nexus s, htc incredible and moto droid x, all using the same controlling chip. Both HTC and moto would send calibrate command to the chip during resume, but sumsang does not. I guess this might be the reason, but I'm not skilled enough to port the drivers

I experienced it twice so far i think, but only have the device for a little more than 2 weeks.
I am on stock 2.3.1 currently.

Beside the lock&unlock method, I discovered a new way of getting screen back to work: rub your hands a couple of times and touch again... Anyway it seem the screen is not well calibrated.

problem seems fixed with my customized kernel
Last night, I modified the touchscreen driver and mach settings a bit on the source of netarchy's nice kernel, and compiled a kernel of my own. The screen now seems working well with my new kernel

Never have experienced this on the nscollab rom which is cm7 and kernel together stable. I suggest give it a shot
Sent from my Nexus S using XDA App

swa2k4 said:
Never have experienced this on the nscollab rom which is cm7 and kernel together stable. I suggest give it a shot
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
May I know how to perform the suggested steps, i have been experience twice since i bought it on 2 weeks ago

I would like to bring this issue up again (after so long) as I am still randomly experiencing this exact issue even with Ice Cream Sandwich 4.0.3 (Stock & Custom ROMs). Any fix yet?

Backlight going down/up...

I don't even know if my eyes are cheating me, or the tablet is indeed have a problem.
(If you followed my previous topic, this is the second tablet I got, brand new.)
Noticed the issue in Hangouts first, with AI keyboard and dynamic screen mode.
Disabling dynamic seemed to fix the issue.
But yesterday I saw it again... at least I think.
It was only a Chrome window, and I was reading news.
The screen went from lighter to darker while I did nothing with the tablet.
Anyone else seeing/having the same issue?
It's so damn annoying.
I mean, I never had such issue on my displays on any device. That's why I think it's not my eyes...

h8Aramex said:
I don't even know if my eyes are cheating me, or the tablet is indeed have a problem.
(If you followed my previous topic, this is the second tablet I got, brand new.)
Noticed the issue in Hangouts first, with AI keyboard and dynamic screen mode.
Disabling dynamic seemed to fix the issue.
But yesterday I saw it again... at least I think.
It was only a Chrome window, and I was reading news.
The screen went from lighter to darker while I did nothing with the tablet.
Anyone else seeing/having the same issue?
It's so damn annoying.
I mean, I never had such issue on my displays on any device. That's why I think it's not my eyes...
Click to expand...
Click to collapse
Try turning off "Reading Mode": [Settings] -> [Device] -> [Display] -> [Reading Mode = Off]
Just a thought.
This may be a silly question, but, is your brightness set to auto?

HumanCaviar said:
Try turning off "Reading Mode": [Settings] -> [Device] -> [Display] -> [Reading Mode = Off]
Just a thought.
Click to expand...
Click to collapse
Yeah, did that yesterday night as a last resort. Didn't notice the issue happening since then, but I will keep an eye on it.
By the way, now I have a working tablet, I'm quite satisfied. (Except this.)
Thanks for the tip!

h8Aramex said:
Yeah, did that yesterday night as a last resort. Didn't notice the issue happening since then, but I will keep an eye on it.
By the way, now I have a working tablet, I'm quite satisfied. (Except this.)
Thanks for the tip!
Click to expand...
Click to collapse
I believe it happens whenever an image is shown. So you will probs notice it when text takes up the entire screen and as you scroll down the page and an image comes into view the screen will change brightness.
Just have to get used it a guess. I kinda am lol.
Sent from Galaxy Note 10.1 2014 Edition via Tapatalk.

the tablet has dynamic backlighting that i haven't seen anywhere to turn off (it's not the screen mode, i have that set to movie). there was a thread about it earlier and i think only the OP and i were able to see it. it's a lot subtler than other devices but when you have a dark scene the screen dims a bit, then when you have a "bright" scene the screen increases the backlight a bit.

I have this issue and its especially noticeable with gifs on screen.

Zerogamer100 said:
I have this issue and its especially noticeable with gifs on screen.
Click to expand...
Click to collapse
Thanks fellas!
Back to Samsung it goes!
Well, at the moment I contacted the local consumer rights service and will try to use the law against the carrier.
Which basically means that they will have to refund me for both the tablet and mobile data fees.
Yeah, this provider got the best prices. And the worst customer service.
And yeah I waited YEARS for this tablet to arrive (I missed the original 10.1 bandwagon)... and it's riddled with bugs. Don't even know what to do if they do refund.
Should I buy an iPad? But that's dumb as a rock. A normal tablet? What's the point in that?
So yeah. Wait for the Note Pro? But who knows if it won't have the same... or even more issues?
Yeah, #firstworldproblems, I know.
But I had a Latitude XT2 laptop with a pen. Most magical thing ever.
I just wanted to write again. ;_;
pls sammy why u do dis to us...
@madsquabbles: Nah. I disabled dynamic, set it to normal or what. Auto backlight is off ... I checked everything.
This is not a feature, but some stupid power management or firmware issue. Not that Sammy would address either. (See the lack of 4.4 or multi-seat support. The tablet is far from brand new.)
ps.: I don't think it's that two of you could see it. You two had the same panel issue as I do. (Remember, Apple also loves to mess up things like this. Like their latest problem with the Retina MBPs had the burn in problem. It was the same machine, but two companies were shipping the LCD panels. One was faulty, other one was perfect. I suspect the same.)
@Geordie Affy: I found this issue happening on news sites. But now it happened on a wall of text (it was a news site again, but without any images.) And today, even in LectureNotes. Not that it's bad, BUT it's annoying as hell.
Baaah. Sorry guys for "mentioning", I just tend to use this stupid mail symbol to refer to people.
Silly internet. There are no symbols left that would cause no harm. ;_;

h8Aramex said:
Thanks fellas!
Back to Samsung it goes!
Well, at the moment I contacted the local consumer rights service and will try to use the law against the carrier.
Which basically means that they will have to refund me for both the tablet and mobile data fees.
pls sammy why u do dis to us...
Click to expand...
Click to collapse
Use the law against carrier? Good luck.
If everything else works, as you said, then why don't you fix this issue (not sure if it's a bug, as you call it).
Turn the auto brightness off, control it yourself.
Or install lux, if you're rooted, and you have much better control.

ddavtian said:
Use the law against carrier? Good luck.
If everything else works, as you said, then why don't you fix this issue (not sure if it's a bug, as you call it).
Turn the auto brightness off, control it yourself.
Or install lux, if you're rooted, and you have much better control.
Click to expand...
Click to collapse
This is different. It's not auto, it's not scene mode, it's not what you think it is.
Uhm... okay how can I explain this.
If you don't have it, you can't guess what we mean.
It's like... you are reading some text, and it goes darker, then brigher, then darker. At the very same screen, even if you stop scrolling.
Then if you got images, it can become worse.
It's terrible because you spend like 10 seconds each time to check if you eyes are bad or there is something fishy going on.
As I said it's possible a faulty panel provider or something.
Now I'm on the carrier-war. If I lose that, I'll send the tablet back to Sammy for LCD replacement/repairs.

I have seen this exact issue and have been able to reproduce it on my friends unit as well. Open up snote.. Start recording a voice memo and watch.. The screen flashes dim and bright. Dim and bright.. It drove me nuts.. Then I noticed.. It was actually doing it in unison with the red blinking dot of the voice memo. So I think it's something where there is an animated gif/pic on screen. I will test turning off reading mode to see if that fixes it and report back. I think I also have mine set to dynamic
Sent from my HTC One using Tapatalk

it's more of a gimic than anything. it's a way to boost contrast numbers without any real benefit to the end user, imoh.

[Q] LG G2 D802 Black Screen

Guys i have a problem with my LG g2 D802 with screen turning black often, then i messed around with the phone and ticked the option "always GUP overly" something like that in developer menu, anyways after that i didn't had any problem for 3 days, then again the blackout started,after restarting the phone more than 10 times i got the display back, then i checked if that overlay option is still ticked, is wasn't ticked , and i didnt touched it, anyways ..this should be an software problem right? anyone here know how to fix this ? Help me out please
Best Wishes

@Demitha some options in developer options resets after boot so they are getting unticked by the system itself. I don't know why your screen turns black after enabling that option, the onkly thing i can say to try is to wipe cache/dalvik-cache and even maybe an factory reset and if those things doesnt work then reflash stock.
We could also see maybe what caused an bsod when you logcat but since it appears often its hard to say when you need to start logging.

wulsic said:
@Demitha some options in developer options resets after boot so they are getting unticked by the system itself. I don't know why your screen turns black after enabling that option, the onkly thing i can say to try is to wipe cache/dalvik-cache and even maybe an factory reset and if those things doesnt work then reflash stock.
We could also see maybe what caused an bsod when you logcat but since it appears often its hard to say when you need to start logging.
Click to expand...
Click to collapse
the option name is "disable HW Overlays" screen dont turn black after enabling that option, i meant,screen didnt blackout after enabling it, but yet some times screen goes out, i did reset the phone once, didn't fix the issues, how do i reflash a stock? i never done it?is there a video guide or something? help me out please.
Best Wishes

@Demitha here is the guide if you didn't founded it yet: http://forum.xda-developers.com/showthread.php?t=2432476
Did you had this blackout also before enabling it?

wulsic said:
@Demitha here is the guide if you didn't founded it yet: http://forum.xda-developers.com/showthread.php?t=2432476
Did you had this blackout also before enabling it?
Click to expand...
Click to collapse
yeah it was worse before,after enabling that option blackout didnt happen fro o 3 days , i noticed even though i didnt restart the phone that HW overlay option gets unticked :/

@Demitha well if it was even worse before then i suggest you to charge your phone to 80-100% for safety because it may take a long time, maybe it can be lower but for safety I always have my battery around that percentage. And then you can try the guide. If your screen turns black can you touch it on random spots to see or it makes sound noises like if you click on anything.

wulsic said:
@Demitha well if it was even worse before then i suggest you to charge your phone to 80-100% for safety because it may take a long time, maybe it can be lower but for safety I always have my battery around that percentage. And then you can try the guide. If your screen turns black can you touch it on random spots to see or it makes sound noises like if you click on anything.
Click to expand...
Click to collapse
i hear sounds and vibrations, phone is totally working on the blackout

@wulsic you think reflashing will fix this issue?

@Demitha it could be but i am not sure, it could be also an hardware defect maybe, and also maybe an software so try to reflash it I am not sure or its hardware or software since it could be both.

wulsic said:
@Demitha here is the guide if you didn't founded it yet: http://forum.xda-developers.com/showthread.php?t=2432476
Did you had this blackout also before enabling it?
Click to expand...
Click to collapse
wulsic said:
@Demitha it could be but i am not sure, it could be also an hardware defect maybe, and also maybe an software so try to reflash it I am not sure or its hardware or software since it could be both.
Click to expand...
Click to collapse
if i flash the phone,i will get software updates like normally ?

@Demitha if you flash the phone to 4.4.2 then you will still get software updates for apps, system incremental updates etc so dont worry about it. You need to care first more to find out the black screen problem. Also if you have an blackscreen do you see like an backlight on ? That the black color gives light ?

wulsic said:
@Demitha if you flash the phone to 4.4.2 then you will still get software updates for apps, system incremental updates etc so dont worry about it. You need to care first more to find out the black screen problem. Also if you have an blackscreen do you see like an backlight on ? That the black color gives light ?
Click to expand...
Click to collapse
yes it does, it like a black light,not very bright but the light is there

@Demitha ahh okay so its not totally off, it could be an software problem since i also had something like that on custom roms when waking up my device (bsod) but i dont remember that my touchscreen still works that i hear those noises so it could be also an hardware problem. The only thing i cannsay is flash it to stock once again like it came out of the box and use it for a couple days to see or its coming back. If so can you reply again to this thread? I think that some g2 users could maybe say more about this subject since i dont have the g2. I also read about display graphics ram which saves battery by holding an image and displaying it like that instead of the gpu so i thought maybe that it got bugged or what, correct me if i'm wrong I read it today in the morning around 2 am.

wulsic said:
@Demitha ahh okay so its not totally off, it could be an software problem since i also had something like that on custom roms when waking up my device (bsod) but i dont remember that my touchscreen still works that i hear those noises so it could be also an hardware problem. The only thing i cannsay is flash it to stock once again like it came out of the box and use it for a couple days to see or its coming back. If so can you reply again to this thread? I think that some g2 users could maybe say more about this subject since i dont have the g2. I also read about display graphics ram which saves battery by holding an image and displaying it like that instead of the gpu so i thought maybe that it got bugged or what, correct me if i'm wrong I read it today in the morning around 2 am.
Click to expand...
Click to collapse
well, i never flashed a phone before, im afraid i might do it wrong

@Demitha i know that you are scared for the first time, when i flashed an android phone for the first time (Htc google nexus one, i miss the trackball xd) i read everything carefully and i did it good it was different then windows mobile since i was the first android user in my family. but i had it for some weeks and sold it again because i had touchscreen issues,power button didnt worked so yeah. But that was some hardware issue which wasn't caused by the flash but it was the previous owner.
So just read the guide carefully, backup all your files to be sure and charge your phone to 80% atleast thats what i am always doing. Or you need to know an geeky friend who also do these stuff

can you please point out what i need to download in order to flash the phone in this thread, there are different versions of g2 models there ,please check the screenshot below
https://copy.com/71RAumYBzgmI

here is the other screenshot, - https://copy.com/9oNye3tlH96z

@Demitha you said you have the d802 version and i also see in the build/software number the d802 so
You need to flash the d802 version which is the international one so just find the d802 files and flash it goodluck! Reply if you need help again

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