I'm having a problem with my Asus Zenwatch 2 (Large). I understand the basic concept of screen burn in on OLED screens, but the burn in I'm getting is not normal. If an always on watch face is on for more than about half an hour, it gets burned into my screen. The problem seems to occur randomly, even occasionally burning in pixels I have displayed for less than a few minutes. I would really like to know what is going on here, as my watch screen has layers upon layers of screen burn-in.
Things I have tried:
Disabling the always on display
Forcing burn-in protection through developer options
Factory resetting the watch
Turning down my screen brightness
Erasing the system, boot, recovery, data, and cache partitions and reflashing (I thought there may be a corruption causing it)
None of these things worked. My watch is less than a year old, so I may send it back under warrenty.
Related
I just picked up my S3 and the whole screen had a hazy green tint on the lock screen and was the same when I unlocked, and I wasn't gonna mess about so rebooted quick and back to normal now, and I read another thread about it but isn't clear why it happens, but I checked the battery graph and there's just a huge gap as if no power was getting through at all, so has anyone else had this happen on S3 and what's causing it?
Michael_P said:
I just picked up my S3 and the whole screen had a hazy green tint on the lock screen and was the same when I unlocked, and I wasn't gonna mess about so rebooted quick and back to normal now, and I read another thread about it but isn't clear why it happens, but I checked the battery graph and there's just a huge gap as if no power was getting through at all, so has anyone else had this happen on S3 and what's causing it?
Click to expand...
Click to collapse
Just had this, I put my phone into my shoulder bag, cycled for 10 minutes, picked up the phone and the entire screen was green as if the red and blue pins from a monitor cable had disconnected.
I'm also having charging difficulties, although that may be the cables.
I'm on CM9, literally just updated to the newest nightly now to see if that sorts any issues. There's something just not quite right about this phone of mine. A quick reset was all it took to sort the screen out but it was scary to think such an issue could occur.
All I know is it's something to do with a sudden dip in power and I read about other phones doing it too very occasionally, and after it happened there was a gap on the battery chart as if the phone was getting no power at all.
Sounds like the OS or at least an important process crashed or got stuck (deadlock, livelock, ...).
Green color has something to do with the rendering process and/or screen calibration. All Galaxy S1 with Voodoo patches for the display color values show a green screen for a very short instant after screen-on.
That also explains the gap in the battery stats since a non-functional OS cannot collect any informations.
Did you run any particular apps which might be causing it?
Without any details I can only recommend the standard package: flash your OS again, factory-reset it.
Maybe wiping the cache is enough. Maybe it's a hardware fault, hard to say...
I just rebooted and I've already upgraded since then, and I wasn't doing anything really at the time except I think that was around the time I used G L to SD and it broke the Play Store, but when it Hulked on me I hadn't touched phone for 40 minutes and that's what I saw when I woke it up. but most people say it's a once in a lifetime thing so not really worried.
This may seem a bit strange, but I have an old i9300 that has run into a bit of an issue. The device itself runs fine, boots CM12.1 (Unofficial port, I know), but the issue is that sometimes the LCD Display goes to a point where it's unreadable. It'll look fine on a normal startup (Displays the Samsung Galaxy S3 GT-i9300 Logo), but then the display dims after that. While in Download Mode, it'll do the same thing. Attempting to reboot into recovery with this display dimmed causes a bootloop. I know that the AMOLEDs don't have backlights, but every so often, the backlight (I know that's not what it's called), will function properly. It's a very strange conundrum. Could it be that either something is loose, or the AMOLED is going out?
There is no backlight on AMOLED, each pixel illuminates individually so your problem is with the screen driver or connections. Water damage can cause the symptoms you describe, first step is to strip down the phone and check the connections.
boomboomer said:
There is no backlight on AMOLED, each pixel illuminates individually so your problem is with the screen driver or connections. Water damage can cause the symptoms you describe, first step is to strip down the phone and check the connections.
Click to expand...
Click to collapse
I gave it a thorough strip-down and checked for signs of water damage, but there wasn't any water damage to be found. I checked the strips that indicate water damage and they were still white. I also checked the connections, reseated them firmly and restarted. I haven't had the issue again since, but it's not a consistent issue, it pops up every so often.
(UPDATE: Here is a link to a short video of my issue: https://youtu.be/YqKW3tU4Fhw)
So I cant seem to find ANY info relating to this issue aside from results for the LG G4, but the solutions for said phone are all over the place. Some are bad screen, some are related to sim tray, some are related to water damage and battery etc. So basically, about a month after buying this phone (KIW-L24 US version), the screen started to artifact and flash in and out randomly. There is nothing that seems to trigger it. I have set the phone down on a table while on the homescreen and watched the lightshow. It is basically a mixture of the problems seen in these videos (Feat. LG G4).
https://youtu.be/gAUkXLR7eQI And https://youtu.be/QstOH66pfiU.
Symptoms:
Screen will randomly start to flicker and fade in and out. I will also get crazy artifacting lines. (Think de-gaussing an old CRT monitor or simillar to what is seen in the second video)
If i see the problems happening, locking the phone and unlocking again will sometimes fix it temporarily. Other times the problem continues after i turn the screen back on.
Sometimes the screen will refuse to come back on. The backlight turns on, and the digitizer responds, but the screen is still black. Making sure the screen really is off, I can come back to the phone a few minutes later and it will turn on. Other times ill have to hard reset the phone (hold power button 10 sec) and it usually brings the screen back to life.
Background:
I bought the phone "used - Like New" from amazon. It came with all the original accessories and even still had the film protector on the back of the phone. I may have noticed these problems after I received the phone, but they really only started to show about a month after purchase.
At first I though it could be software related as I was running CM13 and something could have been corrupted, so i did not just a factory restore, but a full reflash. This didn't solve the issue. Restarting my phone and the reflash did help, but the problem returned. The inability to turn the screen on persists through a reset and I have to wait till the phone boots again to get the screen back. Sometimes takes more than one reboot. This pretty much confirms a hardware issue right? If i put the phone on a black screen, i can see three small fuzzy "dots" in a triangle shape in the top left quadrant. Could the screen have been damaged by whoever owned it before returning it? They are not dead pixels per se, but seems more like areas where the backlight is showing through ever so slightly more. Not visible unless you are on a black screen in a dark room. Ill upload a video showing some of the issues. Any help is appreciated!
im afraid you need a new display brodar...
Seems to be hardware issue. You can visit the nearest service center to get it fixed for few bucks if you don't have warranty.
Yeah that's what i figured, i just needed conformation. I was able to get amazon to take the return even though I was out of the return period. So at least ill be able to get a refund. Ill just pay the extra for a new one this time haha.
One question : Do u have over heat problem with ur phone ?? If u feel ur phone is more than work from the back dont replace . U'll damage the new screen also . Some ppl erported over heat cpu issue with honor ! ;.
KobaltPanther said:
(UPDATE: Here is a link to a short video of my issue:
)
So I cant seem to find ANY info relating to this issue aside from results for the LG G4, but the solutions for said phone are all over the place. Some are bad screen, some are related to sim tray, some are related to water damage and battery etc. So basically, about a month after buying this phone (KIW-L24 US version), the screen started to artifact and flash in and out randomly. There is nothing that seems to trigger it. I have set the phone down on a table while on the homescreen and watched the lightshow. It is basically a mixture of the problems seen in these videos (Feat. LG G4).
And
.
Symptoms:
Screen will randomly start to flicker and fade in and out. I will also get crazy artifacting lines. (Think de-gaussing an old CRT monitor or simillar to what is seen in the second video)
If i see the problems happening, locking the phone and unlocking again will sometimes fix it temporarily. Other times the problem continues after i turn the screen back on.
Sometimes the screen will refuse to come back on. The backlight turns on, and the digitizer responds, but the screen is still black. Making sure the screen really is off, I can come back to the phone a few minutes later and it will turn on. Other times ill have to hard reset the phone (hold power button 10 sec) and it usually brings the screen back to life.
Background:
I bought the phone "used - Like New" from amazon. It came with all the original accessories and even still had the film protector on the back of the phone. I may have noticed these problems after I received the phone, but they really only started to show about a month after purchase.
At first I though it could be software related as I was running CM13 and something could have been corrupted, so i did not just a factory restore, but a full reflash. This didn't solve the issue. Restarting my phone and the reflash did help, but the problem returned. The inability to turn the screen on persists through a reset and I have to wait till the phone boots again to get the screen back. Sometimes takes more than one reboot. This pretty much confirms a hardware issue right? If i put the phone on a black screen, i can see three small fuzzy "dots" in a triangle shape in the top left quadrant. Could the screen have been damaged by whoever owned it before returning it? They are not dead pixels per se, but seems more like areas where the backlight is showing through ever so slightly more. Not visible unless you are on a black screen in a dark room. Ill upload a video showing some of the issues. Any help is appreciated!
Click to expand...
Click to collapse
Try moving to stock once , if it fixed stick to it for few days . 99% of possible cases for hardware issue .
So better request for a replacement from huawei . but don't mention them that u bought it used . tell them u bought it new
Seems that a lot of people complain about this bug/glitch. It mostly happens with this device, specific to some carrier like s5 t mobile etc. Mostly what people face is flickering with a green/yellow nuance that covers at least half of the screen, and that happens when you set screen brightness on minimum. Some other ( like me ) also get the flickering while turning the screen on or off. So I started doing some searches over the web, and tried all the 'fixes' possible. Sadly to me nothing worked. Some of these 'fixes' are :
Turning off auto brightness.
Turning off adaptive display.
Turning off screen overlay ( found on developer settings )
Also other strange ones like removing your sd card etc. Few people say that these worked for them, but for me it didn't.
I tried booting on safe mode, and the problem was still there. I also flashed official 5.0 and the same. So the only thing left was to blame the hardware. But I was sceptical about this since the problem is not persistive, sometimes it happens, sometimes not. Sometimes it happens on small scale, sometimes it is worse. Also a lot of people say that their devices were working fine and the problem started after marshmallow update. A certain person on an online forum claims that he/ she spoke with samsung officials and they are aware about this problem and working on an update to fix this. Does this mean it is not physical problem but just a software glitch ? Hard to say, I sent my phone to different local repair shop and they say it is screen physical problem. But maybe they just want to scam me and take money ( new screen costs too much )
After going through all these, I just got the idea to try and flash an older firmware, like kitkat. And to my surprise, on official kitkat rom it still does the problem, but FAR less.
So TLDR if you have this glitch and gave up on all the 'fixes' you found online, try flashing kitkat, it might work for you even if it's not a permanent fix.
I'm sorry to bump this topic being that it seems dead. However after my own research and now my second S5 from T-Mobile. I'm at the same point as you. My research states that it's more of an AMOLED screen issue, which after a factory reset and flash of older ROM and such does make sense. However, at the same time it could be an actual issue with the screen.
It's definitely a hardware issue in my case-cold temperatures exacerbate it ie-I have no flicker issues in the summer, but get flicker issues in the winter if my phone cool's down to the 60s. The flicker goes away if I heat the screen.
It seems the lower the temp, the more wattage (brightness) is required for the display matrix to function; insufficient wattage/heat when the screen is activated, and the matrix collapses. This is why it autobrightness tends causes issues when it provides power below threshold for matrix stability.
Easiest legitimate econimical fix is ordering a replacement screen, if you have reaervations about yiur shop doing it, it's a very easy/cheap/simple process to do yourself and plenty of how to YouTube videos.
okay, I will solve this issue for yall. I have an s5 g900t that had the screen flicker issue and also when temps are cold, the screen would blank out till I warmed the screen. I fixed this issue after a year of having the issue. a temp fix which can damage the device was found by accident when I went to change out a broken rear cam. heating the screen with a heat gun during surgery fixed the issue for a while then the symptoms came back. after much much research and testing, I found the amoled screen was the culprit. I ordered a new screen and replaced it. no more issues. I took the old screen and replaced it to my other s5 which is for testing only and the screen flickered under low light and would not come on when cold. so, if you have a screen that is flickering in low light and/or wont come on during cold, its your screen. replace it and fixed. how long the new screen will last? well 2 years later no problems, yet.
FYI, AMOLED screens are notorious for this issue and the manufacture is well aware.
My LG V30 VS996 will occasionally get stuck in what I've called the "Lock-Screen Loop", where it'll flash the lock screen, start to load things, and then immediately put itself to sleep and do it again. It looks like I'm turning the phone on and off without unlocking it. The fingerprint scanner doesn't work, Knock-On doesn't work, volume buttons don't work, the only thing that works is restarting the phone.
I have scoured all over the internet and tried toggling every possible setting that might be related to this issue, and still I've come up with something. It's so infuriating.
There's no easy way to recreate it, but it'll happen at least once a day, sometimes more than 4 or 5 times. The circumstances to make it occur change, too. Sometimes I'll go to turn it on with the fingerprint scanner and it'll happen, sometimes it's completely off and I'm not touching it and it happens, and other times I'll be scrolling through Twitter or whatever and it'll just happen.
Has anyone else on here ever experienced this or have an easy fix? I could try factory resetting it but I'd really rather not do that; my phone wasn't receiving the 8.0 update so I had to manually put it on and I'm afraid it'll revert itself and I'll have to go through all that hassle again. (Frankly, I don't remember how I did it, but the lock screen looping started long after I did that).
Any suggestions or help would be very much appreciated
Anthracite4 said:
I could try factory resetting it but I'd really rather not do that; my phone wasn't receiving the 8.0 update so I had to manually put it on and I'm afraid it'll revert itself and I'll have to go through all that hassle again.
Click to expand...
Click to collapse
Factory resetting will not wipe out Oreo.
The same problem comes up when in Pie. It seemed that the latest security update would have fixed it, but no.
I wonder if someone has a solution, other than factory reset.
From how you have explained it, it seems ghost touches on screen, either the digitizer is damaged (a hardware problem) that can happen from heat or dropping the phone. Ghost touches can also hang the phone in a state that fingerprint scanner or volume buttons may not work because cpu is too busy processing constant ghost touches. I had this happen to me when i dropped a phone where at random times the screen would light up as if i did 'knock on', lockscreen would come on for a sec and then phone would go back to sleep and at other times the phone would behave normally. If that's the case with your phone, there is no fix for that and even factory reset will not help.
It is also possible that your phone case or a new or worn out screen protector are interfering with the normal function of digitizer by producing ghost touches. Inspect the screen, especially the curved edges, if you have a piece of debris or phone case interfering with screen. If you use a case, try not use it for a day and see if it happens. If it still happens, remove the screen protector, put the case back on and see if it still happens.