I bought this used s9 for quite affordable price. Everything looked fine during testing except a greenish shade which happens only when unlocked and happens for like a second.
On searching internet, i found threads, yt videos by a number of people, almost all claiming that it is an update consequence. My questions are
1. Is it a software issue? If yes, can I expect some wayto solve - official ota or root and custom or old rom (if possible at all)?
2. If not software issue, is it a software induced hardware issue? Any way to repair without paying full for display?
2.1 If i get it replaced somehow, will itcome back again?
3. In any case, if I don't get it repaired, how long can I expect the deviceto be functional; ie before this green shade becomes permanent instead of being intermittent making device unusable?
Thank you
If it only happens for a second the only thing I be concerned about by the possibility of a rootkit or virus.
If running on Android 9 or higher and you did a factory reset already, that should have killed any unwanted critters.
Do a display check with ScreenTest. If it passes it should be good to go and just a transient glitch.
You've heard of The Matrix, right?
blackhawk said:
If it only happens for a second the only thing I be concerned about by the possibility of a rootkit or virus.
If running on Android 9 or higher and you did a factory reset already, that should have killed any unwanted critters.
Do a display check with ScreenTest. If it passes it should be good to go and just a transient glitch.
You've heard of The Matrix, right?
Click to expand...
Click to collapse
Hahah
This is something different. I asked a reseller and he said that such displays may last anywhere from 1 hour to 1 year.
Internet is filled with such questions.
Can you please help answering other questions if not this one, like if downgrading to older android possible or not?
The green only lasts for a second or so when opening the lock screen?
Never any other time?
Then it's not hardware.
AMOLED displays can last for many years. ScreenTest gives you a good idea of it's condition. Generally failure is gradual with the blue pixels failing first, red last.
The boot loader version dictates if you can downgrade or not.
...
blackhawk said:
The green only lasts for a second or so when opening the lock screen?
Never any other time?
Then it's not hardware.
AMOLED displays can last for many years. ScreenTest gives you a good idea of it's condition. Generally failure is gradual with the blue pixels failing first, red last.
The boot loader version dictates if you can downgrade or not.
Click to expand...
Click to collapse
So far, only immediately after unlocking. Haven't used much tho.
People say temp fix to all such issues is to Enable Always On display and double tap to wake screen instead of using Power button.
Can you ease tell which ScreenTest app it is? Playstore shows several with similar names.
tarun0 said:
So far, only immediately after unlocking. Haven't used much tho.
People say temp fix to all such issues is to Enable Always On display and double tap to wake screen instead of using Power button.
Can you ease tell which ScreenTest app it is? Playstore shows several with similar names.
Click to expand...
Click to collapse
Like I said if it's transient it's no issue.
This is the one I use:
Hi.
My s9 has this problem which everything turns green or worst, depending on the brightness level.
I can repeat the bug 100% of the time: just use the power button to turn off the phone two times: one to put into black screen and again to turn on. Then the screen misses some horizontal lines and is all buggy.
I shall record a video to share my problem but again, this can only be avoided by using aways on display to turn on the phone and then all goes back to normal.
spamtoaster said:
Hi.
My s9 has this problem which everything turns green or worst, depending on the brightness level.
I can repeat the bug 100% of the time: just use the power button to turn off the phone two times: one to put into black screen and again to turn on. Then the screen misses some horizontal lines and is all buggy.
I shall record a video to share my problem but again, this can only be avoided by using aways on display to turn on the phone and then all goes back to normal.
Click to expand...
Click to collapse
Try clearing the system cache.
A hard reboot.
Try in safe mode.
A factory reset may help but if that fails try flashing to the same version. If Android 8 or lower it could be caused by a rootkit that a factory reset won't purged. However this isn't a typical symptom nonetheless the firmware maybe corrupted.
If none of the above works it's a hardware failure, likely the display.
Related
I've been reading through the previous threads and I'm still confused if the issue is hardware or software related. I have the AUO panel and have broken swipes, and times where I can't scroll properly. This has been going on a couple months now and it's getting on my last nerve since it's frequently happening when I need my phone to work properly. All this time I assumed it was software but a couple threads mentioned it was hardware. Trouble is, some people with the JDI screen also have issues so I don't understand. My question is, has anyone ruled out software by flashing an AOSP rom? I'd rather not send this to Sony if at all possible since they don't cross ship and I'd be without a phone.
I have rarely an issue with the touch screen, when swipe up or down, it doesn't swipe it acts like I've just touched (clicked) once the display. I think it is a software issue, because in my case, if I turn off the display wait for 2-3 seconds and turn it on, it works with no problems.
Can you point me please to other threads that have this issue in discuss?
Thank you!
Have you removed the asf from the screen and placed an actual screen protector on it? I found that this really helped with the weird screen issues.
I have a screen protector over the ASF. But that has nothing to do with my issue, because, like I said, when I turn the display off, wait 3 seconds, and on again everything is working normally.
vibecatalin said:
I have a screen protector over the ASF. But that has nothing to do with my issue, because, like I said, when I turn the display off, wait 3 seconds, and on again everything is working normally.
Click to expand...
Click to collapse
Yeah, I reboot usually and the issue temporarily goes away. Then it will come back a day or two later. I'm afraid to remove the ASF because I've read some issues with goes touches even with a screen protector. I just want the issue to be fixed... I was thinking of flashing a AOSP rom but wanted to see if anyone with that ROM had any trouble or not. Maybe the L update in January will fix things.
Here are the resources I've read on this issue:
http://talk.sonymobile.com/t5/Xperia-Z1-Compact/Touchscreen-loosing-touch-issue/td-p/580111
http://johnhaller.com/blog/2014-03-06--sony-xperia-z1-z1s-touch-screen-issue
http://forum.xda-developers.com/showthread.php?t=2770293
I have rarely that issue, like I said I just turn off the screen, and after 2-3 seconds turn it on and it's gone. I'm sure this is a software related issue.
If it helps at all, I never had the issue in the two weeks I tried an aosp rom. However the camera and battery life were a bit lacking so I'm back on a stock rom.
I haven't have the issue too in the past weeks, I've wiping cache and dalvik cache pretty often , because I've installed some system apps. Anyway I will really want to know the cause of this
L.E. I'm still on stock firmware.
L.E. 2 : The Glove mode function, in the Settings-Display menu has an application or something? Has a file redirected to it? Is there in the phone's system a file than can be edited or deleted or something for the glove mode function? Maybe we will find answers there.
I'm not sure that I've made myself understood with the question.
So I've gotten Redmi Note 8t half a month ago or so.. and about the time I updated to MIUI 11 I've started experiencing this weird bug.. Any app or screen or page or icons from the home screen or buttons from apps that remain turned on for some time (literally anything longer than 15 seconds) kind of stay "etched" on my screen for some time (relatively equivalent to the time the relevant app/screen/page was turned on).
I have no idea why this is happening so any help would be massively appreciated. A photo of the problem attached.
Ps this bug appears on every darker screen, not just on home screen.
novak.vujacic97 said:
So I've gotten Redmi Note 8t half a month ago or so.. and about the time I updated to MIUI 11 I've started experiencing this weird bug.. Any app or screen or page or icons from the home screen or buttons from apps that remain turned on for some time (literally anything longer than 15 seconds) kind of stay "etched" on my screen for some time (relatively equivalent to the time the relevant app/screen/page was turned on).
I have no idea why this is happening so any help would be massively appreciated. A photo of the problem attached.
Ps this bug appears on every darker screen, not just on home screen.
Click to expand...
Click to collapse
the images don't seem to be loading for me, but looking at your description it appears to be a burn-in problem.
I'd suggest you bring it to a service center to have it checked.
jc9896 said:
the images don't seem to be loading for me, but looking at your description it appears to be a burn-in problem.
I'd suggest you bring it to a service center to have it checked.
Click to expand...
Click to collapse
Thanks for your reply. Try opening them by clicking on the link and then tapping on "view full image" - it's the only way they'll load I've no idea why, today the whole xda website behaved very unresponsive for me, maybe they didn't upload properly.
Anyway I've just now googled "burn-in" (yep I'd never heard about this before) and from whar I've seen it seems pretty similar to my problem.
Although, in my case, the icons/buttons/keyboard letters that "etch" themselves into the screen after being used for some time do disappear after some time (usually dependant on the time those apps/icons/letters were shown/used on the main screen.
PS The thing is new, I've no idea how this could have happened.
jc9896 said:
the images don't seem to be loading for me, but looking at your description it appears to be a burn-in problem.
I'd suggest you bring it to a service center to have it checked.
Click to expand...
Click to collapse
I had this issue with a Moto G5, apparently it is not permanent, wich is nice, because when its permanent like in the case of amoled displays, the only real solucion is to replace the display. In this case to minimize it I downloaded a blue screen filter app and lowered the screen brightness to around 70 or less, btw this usually happens when you are watching bright stuff or when the phone is hot, also try to use dark mode whenever you can.
FOUND A SOLUTION
After tampering with many a setting, I found out that setting the colour temperature of the display in the stock settings of the phone to cool renders the burn-in almost completely invisible.
novak.vujacic97 said:
FOUND A SOLUTION
After tampering with many a setting, I found out that setting the colour temperature of the display in the stock settings of the phone to cool renders the burn-in almost completely invisible.
Click to expand...
Click to collapse
nice to see your problem has been solved!
some LCDs have screen retention when displaying certain colour temperatures.
also, seems like your attached photos are working again
Been using the phone for the last 12 hours and I noticed something towards the end of my use last night.
The screen seemed to become unresponsive. And when it would work it would start to make its own input when scrolling and opening any app or link my finger would drag over while scrolling.
Changed refresh rates, changed resolutions, even seen if the blue light filter was the issue. Nothing.
Almost seems like the screen drops frames when scrolling, like it gets caught on something.
New development. Fingerprint sensor doesn't respond at all and inputting a pattern is damn near impossible. Going to try removing the screen protector to see if that could also be the issue
Did a factory reset
Issue seems to be where the finger print scanner is
It's almost like a dead or unresponsive zone.
Sounds like a factory defect, better have it replaced if resetting didn't worked.
Small video showing when scrolling over the fingerprint reader, the screen almost loses input
Defect.
Samsung has been little help lol. They want me to send it in for repair instead of an exchange. They also said to just order a whole new one and return the one I have now except the black 128 is sold out
imtjnotu said:
Samsung has been little help lol. They want me to send it in for repair instead of an exchange. They also said to just order a whole new one and return the one I have now except the black 128 is sold out
Click to expand...
Click to collapse
Sounds like Samsung support LOL...sorry you're having issues
Did you remove the factory installed screen protector? Maybe it's the cause of the issue
Return that pal, that doesn't sound good at all.
lovers74 said:
Did you remove the factory installed screen protector? Maybe it's the cause of the issue
Click to expand...
Click to collapse
one of the first things i did to trouble shoot. still having the issue. sometimes the screen completely loses all touch registration and it doesnt even know im trying to swipe or push on things. just realized it did this also after tmobiles new software update.
im still waiting here to hear back from samsung on how they are going to fix this issue
The same thing happens to me. Pulling down the notification shade seems to be the only thing that still works. It seems to goose the phone and it starts working again.
Test using the *#0*# diagnostic menu and use the Touch test.
Hi everyone.
I have a note 10 + 256 go exynos from france.
SInce about last update one ui2.5, I have seen 3 issues which I think are related.
- AOD tap to show not working
- Double tap to wake not working
- When I remove the phone from the ear during a call the screen does not light up anymore whereas before yes.
I almost returned the phone in warranty a short time ago because my screen only registered two fingers,a few days later I received an update that fixed this problem.
For these 3 problems I tried 3 things :
- Update touch screen firmware via *#2663#
- Factory reset
- Reflash the stock firmware with odin and frija
I also have another problem a few times a day the screen freezes, I have to lock unlock the screen and it works again..
Do you think it's a software problem or a hardware problem (damaged screen, damaged sensor or other)?
Please help me thanks.
Lol, firmware and/or software; maybe a settings or permissions issue as there are many. Hardware rarely fails unless it receives severe abuse. You can perform some of the builtin hardware tests just to be sure.
Try using the factory load if the apk in question has been updated or wait for an update that fixes it. Be sure to check the Gallaxy Store for updates.
I'm still running on Pie because it's fast, stable and functional. No scope storage that I don't want or need.
Once you get an OS optimized and running well there's little advantage to upgrading many times unless the new OS is really worth it.
Many times it's not... I'm still running W7 too.
You invariably end up with new issues, hunting down all new glitches and worse, since it's new there not many online solutions.
Thank you for your help.
I mentioned the 3 main methods of fix but of course before that I had already tried the basic things like clearing the system cache, checking the permissions of the AOD application as well as deleting this data.
I also checked the sensors with * # 0 * # but I did not find anything problematic
I even tried to flash the november update with odin and frija and I got a soft brick, so I don't even dare to try a downgrade firmware, I don't have the knowledge, I read that I had to keep the same bootloader and I get lost in the different firmwares
Those are all system apks that run in the background.
Is Android System configured correctly?
Try clearing it's data and of course the system cache.
A hard reboot as well.
It's interesting you lost the proximity sensor.
Thanks.
Yes I have cleared the system cache several times, android system too. I even did a hard reset. I think more and more of a hardware problem, because all these functions are linked to the fact that the screen does not wake up by touch when it is turned off.
the proximity sensor still works at least partially because it flashes well during a call and turns off the screen when I put the phone to my ear, but no wake up when I take it off my ear.
cyroko said:
Thank you for your help.
I mentioned the 3 main methods of fix but of course before that I had already tried the basic things like clearing the system cache, checking the permissions of the AOD application as well as deleting this data.
I also checked the sensors with * # 0 * # but I did not find anything problematic
I even tried to flash the november update with odin and frija and I got a soft brick, so I don't even dare to try a downgrade firmware, I don't have the knowledge, I read that I had to keep the same bootloader and I get lost in the different firmwares
Click to expand...
Click to collapse
cyroko said:
Thanks.
Yes I have cleared the system cache several times, android system too. I even did a hard reset. I think more and more of a hardware problem, because all these functions are linked to the fact that the screen does not wake up by touch when it is turned off.
the proximity sensor still works at least partially because it flashes well during a call and turns off the screen when I put the phone to my ear, but no wake up when I take it off my ear.
Click to expand...
Click to collapse
If it happened after the firmware update... it's in the firmware or software.
Bad firmware can sometimes blowout a cpu but doubt it damaged the hardware controlling just that one feature of the touchscreen.
If that was the case the touchscreen wouldn't work at all.
Maybe the firmware is ok but got corrupted during the download or flash.
A defective memory module could corrupt the load but again that rarely happens.
So back to the firmware/software/settings...
Maybe someone here has seen this before or has a better idea to sort it out.
Honestly I'm not sure it's exactly after an update.
It's just that it's not functions that I use very often. I don't call a lot of people and most of the time I use very little Aod and double tap2wake.
Usually when I grab my phone to use it I unlock it directly with the fingerprint.
when i mentioned the problem where my screen only recognized two fingers at this time , aod and dt2w were already weird as it only worked on the top half of the screen not on the bottom half ..the update solved the problem for the 2 fingers but not for the fact that aod and dt2w only works on the upper half.
Now for some time aod and dt2w no longer work at all no matter where I touch the screen.
I want to clarify that I use a screen protector with loca glue but that it is from the beginning and that it has never been a problem before.
I know this is a weird problem thanks for your patience
I never use a lock screen or the fingerprint sensor.
There may be a conflict because that... disable and see if that helps.
The screen could goof up the proximity sensor. Probably not but next time it's off, check it out.
No worries; these devices fascinate me.
Hope you sort it out; eventually one usually does
I never use a lock screen or the fingerprint sensor.
There may be a conflict because that... disable and see if that helps.
The screen could goof up the proximity sensor. Probably not but next time it's off, check it out.
No worries; these devices fascinate me.
Hope you sort it out; eventually one usually does
2x post
when i did the factory reset it was the first thing i tried before even resetting a password but it didn't work anyway.
For the screen protector I use the same brand from the beginning and it has never caused me a problem of this kind, but maybe this one is defective ..
I would have to remove it to try but I have lazy to change it again because I had to change it twice in a little while.
Hoping that by dint of applying the loca glue I haven't damaged anything.
Thanks
Nah the glue didn't hurt anything; it's well sealed.
The tap on AOD I never use but I double tap to turn the screen on/off. If I lost that I be witch hunting.
Try increasing the touch sensitivity if you haven't already... and make sure no other apps have accessibility permissions that could conflict. Same for device administrator permissions.
Try it in safe mode as well.
My 1 month old Pixel 6 Pro suddenly began to display screen flashing and flickering.
It starts a few seconds after the phone is unlocked or about a minute after the phone is turned on. If you leave the screen alone, so no touching, everything is normal. But once this issue appears, it won't go away until you turn off the phone or lock the screen.
Video here:
File upload and sharing. Large file transfers. Free online cloud storage.
Visit this link to download: VID_20221027_095933.mp4
files.fm
Any ideas if this could be SW related or it is for sure a HW defect? Thanks!
Seller said they managed to fix it by factory resetting the phone and installing updates. Which I find weird since I did this multiple times before sending it back. Google seems to agree with seller.
I guess I just have to wait to get it back and hope for the best, but this in no way seems a SW issue to me.
But is it even possible that software could cause such issues?
I'm also starting to have this issue on the right side of my Pixel 7 Pro. It's not a severe as the video above but it's still noticeable
penguinello said:
But is it even possible that software could cause such issues?
Click to expand...
Click to collapse
It really doesn't seem like it's a software issue but I hope it is
samuelg900 said:
It really doesn't seem like it's a software issue but I hope it is
Click to expand...
Click to collapse
I expect to get my phone back this week or early next week. I will let you know if they really solved the issue and so if it really was a SW glitch as they said.
Got it back today with the issue "solved" but...it's still there, just manifesting in a slightly different way.
File upload and sharing. Large file transfers. Free online cloud storage.
Visit this link to download: VID_20221118_133213.mp4
files.fm
Phone is now back from Google assistance and the problem is solved. I don't know what they did but I suspect the screen was replaced in warranty since it had the protective foil on.
I forgot to update my story but, I made a claim to Google and went to a UBreakiFix store and got it checked out the same day. They replaced the screen for free and that fixed the issue.
samuelg900 said:
I forgot to update my story but, I made a claim to Google and went to a UBreakiFix store and got it checked out the same day. They replaced the screen for free and that fixed the issue.
Click to expand...
Click to collapse
Thanks, my phone suddenly had this issue while I was sitting on the couch and turned my screen on during a call.
Jon8RFC said:
Thanks, my phone suddenly had this issue while I was sitting on the couch and turned my screen on during a call.
Click to expand...
Click to collapse
This problem started on my phone several months ago and hasn't gone away.
Apparently when the p6p was released it was a fairly common occurrence - solved by software.
I tested various screen setups and found a way to use my phone ; I can't set the screen resolution over 51% , turn off Adaptive brightness, turn on Dark theme. Smooth display doesn't seem to have any bearing and if the phone is cold it is more prone to flickering.
Once it starts to flicker I use the slider to bring the level to its lowest and back to about 45%. Pita but workable (can't return phone for a screen replacement).
Managed to eliminate the flickering by installing magisk module AOSP Mods
(changed screen brightness in Miscellaneous/Screen resolution - set the slider to 50%) . Back to full brightness with no flicker.
Link
My Green tint problem fixed by Lock/Unlocking several times fastly. Check this video if you have pixel display issue-
(seems like a software bug, google should fix this ! )