Related
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 )))
Hi Nexus 10 owners,
Love my Nexus 10 but I have an issue with the notification light under the screen.
It was working fine when I first got it on Friday, with it dimming on and off when an email is received.
But since yesterday, it hasn't light up at all, for any notifications, and I do have the "Pulse Notification Light" checked in setting.
So I was wondering if anyone else have any problems with the notification light? Could it be a bug, or perhaps my light broke after the first day?
Thanks in advance for any response.
I might suggest trying https://play.google.com/store/apps/details?id=com.coolbeans.ledtester&hl=en to see if your light still works
espionage724 said:
I might suggest trying to see if your light still works
Click to expand...
Click to collapse
Thanks for the suggestion.
Just tried the app and there's no light.
However, could it be that this app doesn't work on the Nexus 10 yet?
imistw said:
Thanks for the suggestion.
Just tried the app and there's no light.
However, could it be that this app doesn't work on the Nexus 10 yet?
Click to expand...
Click to collapse
Yea it might be possible that app doesn't work; may want to see what an actual N10 owner has to report though
Works fine on my N10, only flashes white though, regardless what colour I pick.
Sent from my Nexus 10 using Tapatalk 2
alias_neo said:
Works fine on my N10, only flashes white though, regardless what colour I pick.
Sent from my Nexus 10 using Tapatalk 2
Click to expand...
Click to collapse
So I guess it's really just my N10 then.
Thanks though.
No problem, try reflash with stock images and you might get lucky. My Nexus 10 is buggy as sh** and I put it down to 4.2. It'll all get sorted out soon enough, hopefully yours is just a bug too. Hope you solve it.
Sent from my Nexus 10 using Tapatalk 2
UPDATE
Just reset my N10 and now the notification light works again.:victory:
Guess it must have been one of the app interfering with the light.
BTW, when I tested it with a LED tester app, it can actually show green, red, blue and purple lights.:good:
alias_neo said:
No problem, try reflash with stock images and you might get lucky. My Nexus 10 is buggy as sh** and I put it down to 4.2. It'll all get sorted out soon enough, hopefully yours is just a bug too. Hope you solve it.
Sent from my Nexus 10 using Tapatalk 2
Click to expand...
Click to collapse
Thanks, I actually just solved it so now I am happy. haha
BTW, what do you mean by reflash with stock image and put it down to 4.2?
imistw said:
Thanks, I actually just solved it so now I am happy. haha
BTW, what do you mean by reflash with stock image and put it down to 4.2?
Click to expand...
Click to collapse
If I understand right, he just flashed a factory 4.2 image from Google, without any OTA updates.
You can get the factory software from the Google developer site and you can download it to your nexus device in case anything gets messed up.
By "put it down to", I mean I blame 4.2 (Android version on the Nexus 10) for all the bugs I'm having. It's a new OS, and this multiuser stuff amongst others means some pretty major changes so I expect it to be a little unstable for a while. Still a better state than honeycomb was when I bought my XOOM on launch day, boy was that a mess.
You're right about the lights, I just got it to work with all the different colours, cyan and then purple look nice
Sent from my Nexus 10 using Tapatalk 2
alias_neo said:
You can get the factory software from the Google developer site and you can download it to your nexus device in case anything gets messed up.
By "put it down to", I mean I blame 4.2 (Android version on the Nexus 10) for all the bugs I'm having. It's a new OS, and this multiuser stuff amongst others means some pretty major changes so I expect it to be a little unstable for a while. Still a better state than honeycomb was when I bought my XOOM on launch day, boy was that a mess.
You're right about the lights, I just got it to work with all the different colours, cyan and then purple look nice
Sent from my Nexus 10 using Tapatalk 2
Click to expand...
Click to collapse
Wow, I did not know about the factory software from the Google developer site. Guess i learned something new today. :laugh:
UPDATE #2
The notification light is not working again
Reset my N10 again, then performed a LED light test each time I install a new app.
Until the last app installed, the notification light was working, then after a few minutes it stops working again.
So I guess it's not really caused by 3rd party apps.
So I ask again, has anyone had problem with their N10's notification light?
Still hoping that it's a bug instead of just me having a defective unit.
Thanks again!
I'm having the same issues. Sometimes the LED seems to be working, others it's not. I installed LED tester and again, sometimes it works fine and others not at all. I have tried to spot a pattern to see what causes it to stop and start and have drawn a blank - no idea. I have since installed light flow but this has not helped. Seems to me that there is either a software bug and we haven't yet figured what the trigger is, or there is a dodgy hardware batch (I hope it's the former!)
hefferman said:
I'm having the same issues. Sometimes the LED seems to be working, others it's not. I installed LED tester and again, sometimes it works fine and others not at all. I have tried to spot a pattern to see what causes it to stop and start and have drawn a blank - no idea. I have since installed light flow but this has not helped. Seems to me that there is either a software bug and we haven't yet figured what the trigger is, or there is a dodgy hardware batch (I hope it's the former!)
Click to expand...
Click to collapse
I think I've found the trigger. If I turn the device completely off, and turn it back on with the charger plugged in, notifications work. If I turn it back on with the charger unplugged, notifications do not work.
Other things I have tried which made no difference included factory reset and factory reflash.
Can some other folks see if their behavior matches mine? I have a replacement device being shipped to me, but if this is a software problem I'd rather not swap hardware. I'm very curious to hear if there are any devices that have a working LED under both boot up scenarios.
I think you are right. LED notifications were working ok when I had a freeze in google now. I restarted (on battery) and tested the notifications - no LED. I plugged in the charger, restarted the system and retested - LED working again. Looks like we have a workaround and a confirmed software bug rather than a hardware fault.
I'll test when I get home, but, I've only ever noticed the light when my tablet is plugged in, so it could be the same for me too. Shouldn't be a major problem, will get fixed in the next update as long as Google are aware.
alias_neo said:
I'll test when I get home, but, I've only ever noticed the light when my tablet is plugged in, so it could be the same for me too. Shouldn't be a major problem, will get fixed in the next update as long as Google are aware.
Click to expand...
Click to collapse
I'm not entirely sure, there are people who are claiming that their LED works 100%.
kftrav said:
I think I've found the trigger. If I turn the device completely off, and turn it back on with the charger plugged in, notifications work. If I turn it back on with the charger unplugged, notifications do not work.
Other things I have tried which made no difference included factory reset and factory reflash.
Can some other folks see if their behavior matches mine? I have a replacement device being shipped to me, but if this is a software problem I'd rather not swap hardware. I'm very curious to hear if there are any devices that have a working LED under both boot up scenarios.
Click to expand...
Click to collapse
Just tried this but still nothing.
Called Google today and they are sending me a replacement.
Ok, this is ridiculous.
Just unplugged my N10 and now the notification light is working.
So apparently it's working randomly.
Hopefully my replacement device works 100% of the time.
BTW, are replacement devices new, or refurbished?
ok so i bought Galaxy S4 i9500.. like a week ago.. then i updated my firmware using keis like 2 days ago.. n now my camera crashes.. when not used after a very long time. im not sure is it either the samsung fault or android fault.. my current version is 4.2.2. if u need anymore details.. i will love to provide them!!
obaid_rock said:
ok so i bought Galaxy S4 i9500.. like a week ago.. then i updated my firmware using keis like 2 days ago.. n now my camera crashes.. when not used after a very long time. im not sure is it either the samsung fault or android fault.. my current version is 4.2.2. if u need anymore details.. i will love to provide them!!
Click to expand...
Click to collapse
Does it say "warning;camera failed" ? And are you loading the camera from the lock screen or home screen?
obaid_rock said:
ok so i bought Galaxy S4 i9500.. like a week ago.. then i updated my firmware using keis like 2 days ago.. n now my camera crashes.. when not used after a very long time. im not sure is it either the samsung fault or android fault.. my current version is 4.2.2. if u need anymore details.. i will love to provide them!!
Click to expand...
Click to collapse
the easiest way is to flash another firmware (Stock*) by Odin
download anther firmware from sammobile.com
ur setting and data will remain but problem will fix
:good:
I bought a new samsung galaxy 4s and the camera failed
obaid_rock said:
ok so i bought Galaxy S4 i9500.. like a week ago.. then i updated my firmware using keis like 2 days ago.. n now my camera crashes.. when not used after a very long time. im not sure is it either the samsung fault or android fault.. my current version is 4.2.2. if u need anymore details.. i will love to provide them!!
Click to expand...
Click to collapse
I had the same problem with my new Galaxy S4 that I bought on 8 of may in 2013.
In the beginning, the camera work fine, but after several minutes, on each time that I tried to open the camera aplication it had black screen with an error message.
I tried to exit the battery and return it, it didn't help.
I tried to rebot to manufacturer settings, at the first couple of minutes the camera work fine, but later the black screen appear again at each time I open the camera application.
Here is a link to youtube that show the same problem that I had :
Search on youtube "samsung galaxy s4 camera fail"
What can I do ?
I am having the same problem with my s4; tried system update, factory reset... maybe i need to try to flash my firmware. so disappointed with Samsung. a flagship phone shouldn't have this problem!
to be safe, getting it exchanged... i never bought insurance before but it looks like i might need to if i am sticking with the s4.
It's a known problem. Loads of people have it. You'll just have to wait for Samsung to fix it.
gili1234 said:
I had the same problem with my new Galaxy S4 that I bought on 8 of may in 2013.
In the beginning, the camera work fine, but after several minutes, on each time that I tried to open the camera aplication it had black screen with an error message.
I tried to exit the battery and return it, it didn't help.
I tried to rebot to manufacturer settings, at the first couple of minutes the camera work fine, but later the black screen appear again at each time I open the camera application.
Here is a link to youtube that show the same problem that I had :
Search on youtube "samsung galaxy s4 camera fail"
What can I do ?
Click to expand...
Click to collapse
From today speaking to a guy who repairs samsungs this is a hardware issue. Reboots and factory resets seem to fix the issue but the root of the problem is the the camera module either not correctly attached/or soldered to the connection so when rebooting or resetting the phone the movement of the device in your hand or laying the phone face up briefly re-connects the module to the device. I'm awaiting my new device as my carrier told me a few people have had this issue also.
Hope that helps
cameracartwright said:
Does it say "warning;camera failed" ? And are you loading the camera from the lock screen or home screen?
Click to expand...
Click to collapse
no it dosent.. it just crashes.. with a black screen!
I have taken several pictures with my 2 days old GS4 but in one occasion when I opened the camera and switched from the front camera to the main, the phone froze and reboot it self :/
I hope i only was a one time failure and not hardware or software relate.
Cheers
There are several other topics created for this issue Slow or reboot when opening camera apps and [Q] Galaxy S4 - reboot launching camera from lockscreen
So far, temporary fixes are limiting the background processes to 4 from the developer options in the settings menu and disabling air view options and smart screen options. This has worked for me, I haven't experienced any other reboots but the lag is still present and sometimes when enabling both cameras feature the app would freeze.
I'm not sure whether this is a hardware or a software issue but nevertheless most GS4s experience lag with the camera app, especially those on the octa version, the GT-I9500. I bought the phone internationally, not using a carrier and switching mine will be a pain; therefore i really hope it's a solvable software issue.
This happened to me yesterday. I tried factory resets, going back to stock with Kies, clearing data, but nothing works. I thought it was because of something
I flashed yesterday, but that wasnt it. Sad it happened so quickly and hopefully it can be fixed.
Sent from my SGH-M919 using xda app-developers app
cameracartwright said:
From today speaking to a guy who repairs samsungs this is a hardware issue. Reboots and factory resets seem to fix the issue but the root of the problem is the the camera module either not correctly attached/or soldered to the connection so when rebooting or resetting the phone the movement of the device in your hand or laying the phone face up briefly re-connects the module to the device. I'm awaiting my new device as my carrier told me a few people have had this issue also.
Hope that helps
Click to expand...
Click to collapse
how reliable is your source? will they fix it in the future.. like in the next batch.. n will they take the first batch back and give us the new models? can u confirm this with him?
obaid_rock said:
how reliable is your source? will they fix it in the future.. like in the next batch.. n will they take the first batch back and give us the new models? can u confirm this with him?
Click to expand...
Click to collapse
He doesn't work for Samsung he just repairs them independently so he is speaking from experience. But I have since asked another independent business and the toldme the same. My problem has now stopped buti believe could be fixed due to my new case on the phone pushing the camera module slightly in place? Who knows but I am replacing incase it happens again (really don't wanna be lumbered with an s4 with a broken camera)
cameracartwright said:
He doesn't work for Samsung he just repairs them independently so he is speaking from experience. But I have since asked another independent business and the toldme the same. My problem has now stopped buti believe could be fixed due to my new case on the phone pushing the camera module slightly in place? Who knows but I am replacing incase it happens again (really don't wanna be lumbered with an s4 with a broken camera)
Click to expand...
Click to collapse
Were you receiving any warning messages?. As I dug into this problem I've found there are 2 error types. In the 1st scenario the camera would crash and a message would be displayed. The 2nd one, would just turn the screen black after accessing the camera app and after a few seconds the phone would reboot.
If a message is displayed then it's most likely a hardware issue. If the phone restarts without warnings then disabling air gesture options and smart screen options along with disabling a few samsung apps temporary solved the matter, therefore being a software misbehave. It's not a permanent solution but until sammy releases a patch this could be a small fix.
G-XtremE said:
Were you receiving any warning messages?. As I dug into this problem I've found there are 2 error types. In the 1st scenario the camera would crash and a message would be displayed. The 2nd one, would just turn the screen black after accessing the camera app and after a few seconds the phone would reboot.
If a message is displayed then it's most likely a hardware issue. If the phone restarts without warnings then disabling air gesture options and smart screen options along with disabling a few samsung apps temporary solved the matter, therefore being a software misbehave. It's not a permanent solution but until sammy releases a patch this could be a small fix.
Click to expand...
Click to collapse
No error message for me.. It justs reboots for me.. Btw what's the expected battery life?
obaid_rock said:
No error message for me.. It justs reboots for me.. Btw what's the expected battery life?
Click to expand...
Click to collapse
Slightly less than 10% / hour with medium use. Coming from a Note 2 this is really frustrating.
G-XtremE said:
Slightly less than 10% / hour with medium use. Coming from a Note 2 this is really frustrating.
Click to expand...
Click to collapse
yea i was expecting much better battery life than this... this sucks! my frnd has a note 2.. n thats awesome!
G-XtremE said:
Were you receiving any warning messages?. As I dug into this problem I've found there are 2 error types. In the 1st scenario the camera would crash and a message would be displayed. The 2nd one, would just turn the screen black after accessing the camera app and after a few seconds the phone would reboot.
If a message is displayed then it's most likely a hardware issue. If the phone restarts without warnings then disabling air gesture options and smart screen options along with disabling a few samsung apps temporary solved the matter, therefore being a software misbehave. It's not a permanent solution but until sammy releases a patch this could be a small fix.
Click to expand...
Click to collapse
I have the first scenario. What would actually cause this? Flashing wouldn't cause it, would it?
G-XtremE said:
Were you receiving any warning messages?. As I dug into this problem I've found there are 2 error types. In the 1st scenario the camera would crash and a message would be displayed. The 2nd one, would just turn the screen black after accessing the camera app and after a few seconds the phone would reboot.
If a message is displayed then it's most likely a hardware issue. If the phone restarts without warnings then disabling air gesture options and smart screen options along with disabling a few samsung apps temporary solved the matter, therefore being a software misbehave. It's not a permanent solution but until sammy releases a patch this could be a small fix.
Click to expand...
Click to collapse
Mine did both loaded camera app then black screen with message after a few seconds "warning:camera failed" then one time the phone didn't reboot it simply froze until I force restarted it. I'm getting replacement tomorrow evening as I use my camera a lot when I don't have a dedicated camera with me
cameracartwright said:
Mine did both loaded camera app then black screen with message after a few seconds "warning:camera failed" then one time the phone didn't reboot it simply froze until I force restarted it. I'm getting replacement tomorrow evening as I use my camera a lot when I don't have a dedicated camera with me
Click to expand...
Click to collapse
Yup, I have that exact thing. Unfortunately, T-Mobile US doesn't have the S4 as part of their replacement "plan" yet. I'll have to check back later.
Hi, so I got my Moto G4 about 2 days ago and I noticed today when I was swiping on my home screen from left to right the app Icons release a blurry trail like some sort Motion Blur , and In the Notifications too the Wi-Fi and Cellular toggle leave a blurry trail of the icon when swiping up or down. Is this a software problem? I just Factory reseted my phone and the problem is gone but reapeared later again. I think that it's because I had too many app icons on my home screen (I had only 2 pages)?
MayoVitalis said:
Hi, so I got my Moto G4 about 2 days ago and I noticed today when I was swiping on my home screen from left to right the app Icons release a blurry trail like some sort Motion Blur , and In the Notifications too the Wi-Fi and Cellular toggle leave a blurry trail of the icon when swiping up or down. Is this a software problem? I just Factory reseted my phone and the problem is gone but reapeared later again. I think that it's because I had too many app icons on my home screen (I had only 2 pages)?
Click to expand...
Click to collapse
Well i had seen having this problem just put this question in the motorala forum of g4.They fixed that issue.
anhoxhrs said:
Well i had seen having this problem just put this question in the motorala forum of g4.They fixed that issue.
Click to expand...
Click to collapse
Okay I'll post it there and see if I get any help from them. Thanks thought!
anhoxhrs said:
Well i had seen having this problem just put this question in the motorala forum of g4.They fixed that issue.
Click to expand...
Click to collapse
Posted there still no solutions thought. I noticed when my phone gets hot the blur is almost gone (It wasn't noticable) What is going on? Also I flashed a older version of the firmware and still had that blur. It got heavy again after I installed like 12 apps and then I updated again to the latest build and still the blur is there.
MayoVitalis said:
Posted there still no solutions thought. I noticed when my phone gets hot the blur is almost gone (It wasn't noticable) What is going on? Also I flashed a older version of the firmware and still had that blur. It got heavy again after I installed like 12 apps and then I updated again to the latest build and still the blur is there.
Click to expand...
Click to collapse
Try to go to service center.Make sure you have locked the bootloader.
I also have this problem. The support advised me to send the phone to a service center.
For information, this usually occurs when the screen is hot, about 10 minutes of use. Particularly visible when used as GPS (waze or google maps).
This is a hardware problem. Not software, it remains after a quick restart.
anhoxhrs said:
Try to go to service center.Make sure you have locked the bootloader.
Click to expand...
Click to collapse
Thanks I'll lock the bootloader and go in to the service center and let them check it out. Altrought in EU it doesn't matter if it's unlocked I think but I'll lock it again.
Tiwy57 said:
I also have this problem. The support advised me to send the phone to a service center.
For information, this usually occurs when the screen is hot, about 10 minutes of use. Particularly visible when used as GPS (waze or google maps).
This is a hardware problem. Not software, it remains after a quick restart.
Click to expand...
Click to collapse
Thanks for the info! For me it's the opposite when my phone is cold (To be exact, the battery when it's at 22,0°C in CPU-Z) the blur is there and really noticable. When I use my phone and the battery hits 35-37°C the blur is almost gone everywhere but an app named "Discord" that has really small text has the blur and it's really noticable. I'll send it and see what they can do.
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