So. Recently got my second transformer. After a few hours use it switched off and refused to turn on at full brightness - in the dark i could just just see icons on the homescreen. After a while it seemed to tun on again. Crazy. So i updated to and used latest 4.4.2 stock for a day, the screen was working perfectly at all brightness levels, uniform, no light bleed. Then i flashed a few of the available CM based roms. This morning, a few days in, i notice that the backlight is much much stronger on the right.
At low brightness it was completely ridiculous. Its like one of the rows of leds wasnt on at all. So i reflashed a backup i had from install day and now everything is just fine - uniform brightness, working perfectly. It seems to be a driver bug. But how did it survive me going from kernel to kernel?
So now im wondering if its a hardware issue... any thoughts?
Ive now noticed this happening on a number of occasions to different rows of the backlight - sometimes at bootom, sometimes at bottom and right. Anyone else seeing something like this?
Sounds like hardware to me...
berndblb said:
Sounds like hardware to me...
Click to expand...
Click to collapse
I flashed the latest cm and this seems to have stopped happening so looks like driver issues. However, the screen continues turn off sometimes, and when it does it needs two presses of the power button to turn back on. Its a crazy thing asus - i had the last infinity too, sold it after a few months because it just wasnt as good as my nexus 10. And now this... pretty amusing.
Dunno why i keep buying asus. Must be my good experience with their motherboards or something... usually they also have excellent support and firmware updates.
Related
Hello programmers, love this forum since i know it 3 years ago...
the BIG question i have is;
i switched a broken s3mini screen to a new one.
everything working fine till i slide the brightness tab down.
every click it slides down, the screen turns into a color, as if absence of color calibration, or intense of certain colors making the only brightness option i can choose to see accurate colors is on max.
i updated the firmware to latest, still no results. its an original never rooted 8190.
thanks in advance and great work!
Is your new screen a Samsung genuine? Or is it 3rd party? It could be incompatibility. If you never changed the firmware and it was working before the new screen, but not now, it's probably the new screen.
Good luck!
What is everyone experiencing? I have a T-Mobile Nexus 6. I am running stock and not rooted. Apologies if this has already been covered, but I searched a couple of different ways and did not see anything.
Not sure what others are experiencing, but my Nexus 6 display will randomly wake into ambient mode even when I just have it sitting still on my desk or couch. There are no alerts that are driving it, so I am just wondering if others are seeing the same thing or if they have done anything with the settings to clear this issue.
I can't imagine that ambient display is a huge drain on the battery or anything, but it's not nothing. Plus it's distracting when it happens.
I've noticed mine coming on due to vibrations. I had it sitting on a minifridge next to my desk. I thought it was random too, but it turns out I was either knocking the side of my desk with my knee, or the fridge was kicking on/off.
Mine does it all the time. No movement to the phone or even around the phone. Hands no where near it. Just decides to wake up. I find the whole ambient display to be pretty annoying altogether honestly. Hoping devs can disable it and find a way to use the LED.
I saw a weird error message from LightFlow (which I installed and enabled to see what it would do). I wonder if this or other apps that are running in the background and potentially causing the screen wakes.
I will try uninstalling LighFlow to see if it improves the situation and report back with any news.
I think you might be right. I have the same problem but I didn't notice it when I first got the phone. I have installed lightflow and now that you mention it, this problem started soon after. So I just uninstalled lightflow and it already seems better.
When I installed that double tap to wake app it messed with ambient display and would turn it on, especially when the battery was low. I removed that app.
Since then I have also turned off ambient display because I found it fairly useless and feel it is using battery for very little benefit. If it flashed faster or kept flashing until I checked it I think I'd use it.
I turned it off because I had it sitting on a table with nobody touching the table and it kept coming on. I couldn't get light flow to get the light working unfortunately, hopefully there is a fix coming.
Moostafa29 said:
Mine does it all the time. No movement to the phone or even around the phone. Hands no where near it. Just decides to wake up. I find the whole ambient display to be pretty annoying altogether honestly. Hoping devs can disable it and find a way to use the LED.
Click to expand...
Click to collapse
root phone, install light flow, disable ambient display.
it's already been done.
i use light flow and it works perfectly, sans flashing LED but that seems hardware/kernel blocked.
It seems that LightFlow is what was causing the issue as I haven't noticed the screen waking since uninstalling it yesterday.
Sent from my Nexus 6 using XDA Premium HD app
I'm definitely looking forward to getting the LED indicator working.
Sent from my Nexus 6 using XDA Premium HD app
Seems like my phone has forgotten it's amoled. It lights up the entire screen even if it's just black. The screen is overly bright and looks washed out and I can see tons of imperfections on it that seem to move with whats on the screen. This leads me to believe it's software, (happened a few days after a cm12.1 install) .
I've tried flashing stock images and it still persists. Anyone experience something like this? Not sure the best solution.
lower your brightness? what brightness do you keep it at?
Regardless of whether brightness is 100% or 0% the screen is overly washed out. It's as though the backlight is being turned on even if there are dark pixels on the screen. Everything is just way brighter and hard to read. Not sure if it's a hardware problem or software problem. Any way for me to determine this? Only thought would be a nandroid backup from my phone being restored on another to see if it recreates the problem but i don't have access to a second nexus 6.
Noxey said:
Regardless of whether brightness is 100% or 0% the screen is overly washed out. It's as though the backlight is being turned on even if there are dark pixels on the screen. Everything is just way brighter and hard to read. Not sure if it's a hardware problem or software problem. Any way for me to determine this? Only thought would be a nandroid backup from my phone being restored on another to see if it recreates the problem but i don't have access to a second nexus 6.
Click to expand...
Click to collapse
Can` t you go to store where they sell the Nexus 6 to compare? I reccon you`re on stock and don`t use a custom kernel for color control, my screen is beautiful imo. But also its possible that maybe you have a faulty device, it can happen ....
My screen was great. It's a recent issue that came up. It has happened in the last few days.
Hi everyone,
Got my Pixel 4 XL on the 23rd and been playing around with it since then. I am now settling into a rhythm and noticed a very concerning glitch with the display when the phone is in dark mode. Basically, when the phone is in dark mode I noticed that typing in Gboard or tapping anywhere on screen in apps that are not pure black (such as Messages, Phone, etc.) will shift the screen colour from blueish-black to greenish-black. This happens every time, even after rebooting the device. There is no visible colour shifting in apps that use pure-black such as Settings (however, parts of Settings like the search bar that are the "gray" dark colour also shift). Once I noticed this happening now I cannot stop noticing it everywhere. I am looking to find out from you whether you are seeing the same thing or whether this may be a device problem. Note that the same issue shows up in dark apps even if dark mode is not enabled. It also has nothing to do with Ambient EQ, Automatic Brightness, or anything else of similar nature. Occasionally the problem stops, but if I pull up Gboard and start typing (say to search in the Recent section of the phone app) the problem immediately comes back.
I am looking for serious feedback here from those willing to look closely. This does seem like a software glitch to me, rather than hardware, especially since I am not seeing this behaviour with any other colours and so far it definitely has something to do with physical interaction with the screen when tapping on it. As I said, it also seems to be universally triggered by Gboard when in apps running in dark mode.
I appreciate any feedback you can provide.
Edit: Looks like what I'm observing is related to the switching colour profiles when the display is going back and forth between 60Hz and 90Hz. Turning off the smooth display function or forcing the display into permanent 90Hz mode appears to stop the problem from happening. Google really messed this one up. I hope their 90Hz fix they promised clears up this issue. Very annoyed ?
Thanks,
Dejan
Btw, since you are using forced 90hz display make sure to have always on display on. If you don't your greys will be purple and lower brightness as well as lots of black smear/crush. I don't know how turning on always on display solved that issue (someone posted this fix in another thread). So it indeed doesn't seem to be hardware but software related and hopefully they will tune this over time.
zetsumeikuro said:
Btw, since you are using forced 90hz display make sure to have always on display on. If you don't your greys will be purple and lower brightness as well as lots of black smear/crush. I don't know how turning on always on display solved that issue (someone posted this fix in another thread). So it indeed doesn't seem to be hardware but software related and hopefully they will tune this over time.
Click to expand...
Click to collapse
Yeah, I saw that thread. Some funky stuff going on with display calibration and 90Hz. Since I know that the HW is not defective and the SW is the source of the issue I am less bothered now (I cannot stand exchanging HW). I haven't specifically observed that effect on my phone and while I did try forcing 90Hz, I actually went back to the stock setting since I noticed that forced 90Hz further sucked down the battery that already is not particularly stellar despite this being the XL version. I presume Google will refine the 90Hz calibration and function over the next few months. I will say though that I am a bit confused why they need to have different calibration at different refresh rates. I calibrate all of my desktop monitors and despite the fact that I have a 100Hz monitor I never have to change calibration with refresh rate. Maybe an OLED thing :shrug:
dhorgas said:
Hi everyone,
Got my Pixel 4 XL on the 23rd and been playing around with it since then. I am now settling into a rhythm and noticed a very concerning glitch with the display when the phone is in dark mode. Basically, when the phone is in dark mode I noticed that typing in Gboard or tapping anywhere on screen in apps that are not pure black (such as Messages, Phone, etc.) will shift the screen colour from blueish-black to greenish-black. This happens every time, even after rebooting the device. There is no visible colour shifting in apps that use pure-black such as Settings (however, parts of Settings like the search bar that are the "gray" dark colour also shift). Once I noticed this happening now I cannot stop noticing it everywhere. I am looking to find out from you whether you are seeing the same thing or whether this may be a device problem. Note that the same issue shows up in dark apps even if dark mode is not enabled. It also has nothing to do with Ambient EQ, Automatic Brightness, or anything else of similar nature. Occasionally the problem stops, but if I pull up Gboard and start typing (say to search in the Recent section of the phone app) the problem immediately comes back.
I am looking for serious feedback here from those willing to look closely. This does seem like a software glitch to me, rather than hardware, especially since I am not seeing this behaviour with any other colours and so far it definitely has something to do with physical interaction with the screen when tapping on it. As I said, it also seems to be universally triggered by Gboard when in apps running in dark mode.
I appreciate any feedback you can provide.
Edit: Looks like what I'm observing is related to the switching colour profiles when the display is going back and forth between 60Hz and 90Hz. Turning off the smooth display function or forcing the display into permanent 90Hz mode appears to stop the problem from happening. Google really messed this one up. I hope their 90Hz fix they promised clears up this issue. Very annoyed ?
Thanks,
Dejan
Click to expand...
Click to collapse
I just noticed this on my pixel 4 xl tonight. But It only happens when the proximity sensor is triggered. Ex: like after making a phone call except it made everything on the screen seem over saturated on the screen and well as the same color shift you had stated. It seems to go away once I lock the device and unlock it again. It did it with smooth display on and off as well as force 90hz on and off.
There are a couple threads discussing this. Here's one of them:
https://forum.xda-developers.com/pixel-4-xl/how-to/smooth-display-colour-issues-t4000087
And another:
https://forum.xda-developers.com/showthread.php?t=3998907
Sent from my Pixel 4 XL using Tapatalk
Hi, sorry if this was posted before, but with XDA moving to XenForo, search seems messed up, i did several searches and nothing comes up for "flicker" in this whole Pixel 4 XL Forum...
Has anyone else dealt with the low brightness screen flicker? I know it can't be just a bad phone, since i just bought three pixel 4 XL phones and they all exhibit this same behavior.
They are all running LineageOS (Official builds) so I don't know if this just affects the ROM or stock as well (although I've read it might affect stock phones too elsewhere).
It makes the phone pretty difficult to use in very low light situations, the screen will constantly flicker (more noticeable on darker backgrounds).
At first I thought it was just the Opera browser (as that's what I prefer), but it's operating system wide... Apps like "Darker" help.... because you can crank up the phone brightness and use a filter to dim the screen.... but it doesn't get the top & bottom menu/buttons, so those remain like spotlights in your eyes with that workaround.
Just curious if anyone knows whats up with this... it's the only phone I've ever seen this behavior on (and i've used Pixel 1,2,3 XL phones all with Lineage, and a myriad of other devices back in the Cyanogenmod days.... I've never seen a screen flicker issue like this).
Thanks for any help
edit / update-
the pro version of "darker" app works to fix this.... you crank the phones brightness to 100% and with the pro version you can dim the rest of the interface.
hopefully this helps anyone else suffering from this HUGE flaw (again i don't know if its just LineageOS or not, i didn't run stock on these except to unlock bootloader etc)
Hi,
I've seen it once and solved it by switching off smooth display. Not a real solution of course, but I never really noticed the difference between 90Hz and 60Hz anyway.
edwinek said:
Hi,
I've seen it once and solved it by switching off smooth display. Not a real solution of course, but I never really noticed the difference between 90Hz and 60Hz anyway.
Click to expand...
Click to collapse
hmm.... you running stock i guess? i don't see smooth display option in lineage