Related
Hi all,
I'm running OzDROID 2.0 for my rom, 2.10.50.26 for my radio, and Hyperdroid1.6 for Android. Also TMOUS. I just recently updated my rom from an energy build to this one (wanted a lighter, faster loading WinMo). I've been having a nasty problem with the screen not coming back on when it goes to sleep. The buttons light up when i press them, but the screen stays black. Just today alone, i've had to pull the battery FOUR times. Some days it's ok, some days it's a nightmare. I checked the hyperdroid post for a radio recomendation but couldn't see any. I've tried using SetCPU to adjust clock speeds using profiles for sleeping, etc in hopes that some obscure thing will work. no good. I mean, what if i see bigfoot and want to snap a pic but the screen doesn't turn on?
My only ideas left include:
-Formatting my 16gb SD card. (would like to avoid, but will do if people think it would help. I hate setting stuff back up)
-Getting Hyperdroid1.7. (Havent yet cause 1.6 w/ Cyanogen is pretty F'n awesome, and minus this problem, i LOVE it)
-Updating my radio. (Going to do this anyways as i randomly get the "robot voice" problem. I plan on upgrading to 2.12.50.02_2 unless anyone has better suggestions)
I just wanted to check here to see if anyone has one of those "Ohh, enable <enableable option>, dumbass!" fixes. I'm not that experienced with this phone stuff. If anyone could help I would greatly appreciate it.
Thanks!
Searching is your friend. App tray->Settings->Display->Auto-Rotate to OFF/Auto brightness to OFF. This has been covered bajillions of times, the HD2 builds of Android have problems with rotation and the light sensor causeing the kernel to wig out and BSOD.
Sorry for inconveniencing you. If you had any idea how much time i've spent on here trying to figure it out, you'd understand why I decided to just ask this myself. I've had this problem for a month and am finally just now posting. If I found that anywhere I would have gladly done it. The funny thing is - those two ARE disabled, and have been. I dont like auto-rotate and auto-adjust brightness has always been off.
I even took the time to read the "similar posts" that are recommended after typing in the subject.
Since those two are off and my problem persists, I suppose I should format my SD card and try other stuff. So while that problem may have been covered "a bajillion times" it appears your solution is not the miracle cure and is probably a good reason as to why it's been asked "a bajillion times."
Why is it then when I tell people to search, they instantly peg me as some jackass just trying to pawn them off. This issue, the "black screen of death" or, "my phone wont wake from sleep under android" HAS INDEED been covered many, many times. It's cause by either what I just told you, or the particular kernel that you are running is one that tends to get stuck in the sleep mode and won't let the screen come back on. Seriously 9 times out of 10 the problem is caused by auto rotate or auto brightness.
Ashasaur is right but also none of the android versions are very stable anyway and eventually you will face this problem on all of them some sooner than others but they will eventually crash in one way or another
Sent from my PC36100 using XDA App
ashasaur said:
Why is it then when I tell people to search, they instantly peg me as some jackass just trying to pawn them off. This issue, the "black screen of death" or, "my phone wont wake from sleep under android" HAS INDEED been covered many, many times. It's cause by either what I just told you, or the particular kernel that you are running is one that tends to get stuck in the sleep mode and won't let the screen come back on. Seriously 9 times out of 10 the problem is caused by auto rotate or auto brightness.
Click to expand...
Click to collapse
I don't doubt that, but when you reply to someone asking for help with a tone as if they are retarded, don't expect them to buy you flowers. Sorry this has been asked so many times but I feel i put good time into researching this problem and didn't see a problem asking a Question on a QUESTION and answer forum. Like i said, sorry i inconvenienced you and I do appreciate your response, however you did come across as a jackass. I understand you probably deal with a lot of crap as a forum mod, but I didn't post this intending to ruin your day. You can see my post count and gather from it that I don't spend days posting pointless questions. If I came across a solution that worked, this post wouldn't exist.
Try a different radio(2.11.50.20) seems to be doing good for me, also try copying your files to a better SD card. And there is a tab under Setting>Home>>Items that says Home Timeout: 4 Hrs... try unchecking that box. I am new to the HD2 also and trying to tweak it just right so it stops turning off in the middle of the night and making me late for work cause no alarm lol
I've had my G2 for almost a month now and the knock on/off always worked flawlessly. Then today it just stopped working, my knock off works but knock ON will not work, at ALL! I've restarted, turned the feature off/on, nothing is getting it to work again. Any ideas? What exactly triggers the knock on feature? Surely it can be the touch of the lcd if the screen is off...is it somehow the proximity sensor or gyro sensor? If I can figure out how it works maybe I can start there..Thanks for any help you can give me.
GHII said:
I've had my G2 for almost a month now and the knock on/off always worked flawlessly. Then today it just stopped working, my knock off works but knock ON will not work, at ALL! I've restarted, turned the feature off/on, nothing is getting it to work again. Any ideas? What exactly triggers the knock on feature? Surely it can be the touch of the lcd if the screen is off...is it somehow the proximity sensor or gyro sensor? If I can figure out how it works maybe I can start there..Thanks for any help you can give me.
Click to expand...
Click to collapse
Backup first...then Factory reset
Should fix whatever file or resource that got screwed up. Install your apps 1by1 until you find what app caused your issue & delete it
tiguy99 said:
Backup first...then Factory reset
Should fix whatever file or resource that got screwed up. Install your apps 1by1 until you find what app caused your issue & delete it
Click to expand...
Click to collapse
Well I havent installed anything new recently but maybe I'll take the opportunity to try one of the new CM/ASOP roms...Thanks for the reply
I'm having the same issue with knock on not working. i've wiped a few times and have flashed diferent roms but it wont turn the phone back on. i'm also having this strange issue where i cant pull the notification bar down.
EDIT: I figured it out. did you install TWRP Recovery? i did and mine was messed up. i flashed back to stock and re-rooted and everything works again. I'm not sure if TWRP is the reason since im on a t-mobile G2 but reflashing to stock definitely worked. also i think you have to do a reset after flashing rom because the changes wont take effect unless you do
GHII said:
Well I havent installed anything new recently but maybe I'll take the opportunity to try one of the new CM/ASOP roms...Thanks for the reply
Click to expand...
Click to collapse
Wow that's a relief, I'm having the same pull down issue too.. Even scrolling here is a dead spot on the screen if I'm scrolling a page or list as I get in that area it "slows". I thought my digitizer was going bad. I found my knock on works but I have to do it extremely slow... Tap... Pause 1-2...tap.
Edit yes to twrp.
Sent from my VS980 4G using xda app-developers app
well i re-rooted and it doesnt work anymore. i deleted stuff so i need to see if its something that is being removed that causes it to not work
I just flashed the stock rom back..shows unrooted again, and it is still doing the same thing. Im still under my 30 days, Im going to return it, hope for the Nexus 5 on verizon by the weekend and if not I guess buy a new G2.
mine still says rooted so i'm kinda screwed right now
Same issue
Same thing with my T Mo G2. Using Nova launcher. Knock on worked flawlessly since new, about 2 months,use Nova gesture for knock off. Suddenly knock on stopped working. Too bad, because I like the feature, got used to using it. Did a restore and wipe using TWRP, kept root access, but still no knock on. Next I'll try going back to stock ROM, but I'd rather go an easier route. Has anyone successfully restored knock on?
Hi i have a dead spot somewhere app in the screen and when i pull down the notification bar it doesnt goind down.Also i tryed to draw with quick memo and i can see that it is a dead spot somewhere near the top of the screen
Does anyone has the probleme and have you fixed it
The only solution is returning the phone
ankurcshah said:
The only solution is returning the phone
Click to expand...
Click to collapse
No...first try this.
Open phone app and go to dialer
Dial 3845#*XXX# where XXX is your phone model i.e. 800/1/2/3.. You will come accross a menu.
Select settings
Select touchscreen firmware update...
Wait for couple of minutes...screen will become unresponsive...
when it responds reboot....
Go to settings gestures...ensure knock on is selected.
It should work then,
Let me know...Best of Luck....
---prs thx if helped
rastigo said:
No...first try this.
Open phone app and go to dialer
Dial 3845#*XXX# where XXX is your phone model i.e. 800/1/2/3.. You will come accross a menu.
Select settings
Select touchscreen firmware update...
Wait for couple of minutes...screen will become unresponsive...
when it responds reboot....
Go to settings gestures...ensure knock on is selected.
It should work then,
Let me know...Best of Luck....
---prs thx if helped
Click to expand...
Click to collapse
It is a ls 980 model so the code is 5689#*980# and i did that and after doing that also its the same. no reponse ! So tired of this
ankurcshah said:
The only solution is returning the phone
Click to expand...
Click to collapse
ankurcshah said:
It is a ls 980 model so the code is 5689#*980# and i did that and after doing that also its the same. no reponse ! So tired of this
Click to expand...
Click to collapse
I read the following posts on some other forum...so essentially its a hardware issue....try stock jb rom kdz, then factory reset and reboot. If this helps solve the problem you are lucky. If not, try getting your phone replaced with 802 model. That is practically most stable with a lot of devlopment and tons of ROMS stable and working.
I will still keep looking for a solution and let you know consulting a few senior xda devs I know... sorry man, it hurts to see a fellow indian in distress.....:crying:
Tons of lg users are experiencing this issue. Its a design flaw with a hardware component that easily breaks. Wonderful build quality -_-...right. So only option is replacing the phone. But to how soon, until the other one breaks. So its kinda like. Well. This blows. I suppose Ill install a custom kernel and enable screen wake features that way.
Sent from my LG-LS980 using xda app-developers app
That's odd, I have not seen much on this... if running stock
Quote:
Originally Posted by Burkettacb View Post
Okay. So after hours of tapping. Which might i add. My fingers hurt, I am now able to activate the screen. Pausing after each tap, using my finger print area to tap "not to be confused with finger tip". The screen will activate. Also note, the standard two taps works sometimes, but with four presses, i seem to get the best results. Give it a try people. I have a theory the hardware has not failed. But yet, the activation area pixel size value changed. Either due to a conflicting app install. A intermittent system glitch etc
Sent from my LG-LS980 using xda app-developers app
Or againg, a ROM you may be using.
More detail would be helpful
ankurcshah said:
The only solution is returning the phone
Click to expand...
Click to collapse
Good luck with that if the phone is a D800. I took my G2 to the local AT&T store just a couple of hours ago with the same "no knock on" bug. But the sales person (who had bad breath) told me that because there was another way to get the phone to function (the back button), they won't even look at it. The fact that the knock off/on feature was a MAJOR selling point when the phone was released is apparently irrelevant.
He has a ls980 so it might not be the same for him. He can ask for a replacement
Sent from my LG-D802 using XDA Premium 4 mobile app
This happened to me this week as well, unfortunately in Canada none of the carriers will replace my device for me, LG says its user damage and are gonna charge me 125 dollars to fix it. I'm gonna see what the local repair shop says and hopefully theyll just fix it for me. It seems like this is an increasingly common issue, it's a shame that LG don't recognize that we didn't damage our phones, they sold us defective units. I'm very unhappy with LG's customer service, we should raise awareness of this and hopefully LG will come up with a solution for us
Andrew_han said:
This happened to me this week as well, unfortunately in Canada none of the carriers will replace my device for me, LG says its user damage and are gonna charge me 125 dollars to fix it. I'm gonna see what the local repair shop says and hopefully theyll just fix it for me. It seems like this is an increasingly common issue, it's a shame that LG don't recognize that we didn't damage our phones, they sold us defective units. I'm very unhappy with LG's customer service, we should raise awareness of this and hopefully LG will come up with a solution for us
Click to expand...
Click to collapse
Did you try the "Hidden Menu" "Touch firmware update" option? I had this issue and it got fixed with it.
try 3845#*modelnumber# eg: 3845#*800# change model number 800 with your phones model number, then tap on "Settings" and scroll down to "Update Touch Firmware"
I have a few more suggestions to make it work, let me know how it goes.
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.
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
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