Related
Is it just me or does the auto-brightness seem to only stay at a certain brightness and never change? On my previous phone, usually when I had auto-brightness enabled, whenever I walked into a dark room, my brightness would lower right away but on this phone, no matter where I go, the brightness seems to always be the same with auto-brightness on. The brightness does not change, even when I walk out with the sun out..
Can anybody confirm this please, I'm thinking of exchanging this unit as it might be defective...
Sent from my LG-P999
Might be your phone. In my moderately-lit office, I can definitely see the screen brightness change when I focus a flashlight on the sensor and then take it away. It's not a huge difference, but definitely observable.
Do you use a case? Is the case blocking the light sensor?
I do not use a case. I have also tried blocking the sensor with my fingers and the brightness just seems to always stay the same... also when I use the power control widget to change brightness and set it to auto-brightness it immediately jumps to that same particular brightness level that I've been stating
Sent from my LG-P999
I was noticing this as well. It seems to just go to medium brightness and stay there all day. I never notice any changing.
abowmedia said:
I was noticing this as well. It seems to just go to medium brightness and stay there all day. I never notice any changing.
Click to expand...
Click to collapse
That's exactly what I'm experiencing, glad to know I'm not the only one..
Sent from my LG-P999
The change is definitely less noticeable on this phone than my Nexus One, but is there.
I just got the G2x and it does the same for me. It's range of brightness seems to be 20-30% and that's it. I had this problem with stock gingerbread, so I tried rooting and installing CM7, but same problem. So I got it set to manual 10/40/100 on my power control.
My friend said his original droid did this for quite a while until a software update came along a few months later. Maybe we just have to wait till there's a software update to fix it?
Yes, it's borked, always has been.
Mine is broken too. Same happens to me.
Sent from my LG-P999 using XDA Premium App
Same here. It has never worked, as far as I can remember. Depending on where the setting happens to be left at, my battery runs out in just a few hours, or I cannot use it in the car.
Aside: I switched to an original Droid from an iPhone 3G, then onto a G2X. My next phone is going to be an iPhone -- and I'm not coming back to Android until Google figures things out. Android is nice, but I hate being out of date after a couple of months, and having to install unsupported, hacky, half-broken user-built ROMs to stay current with the state-of-the-art functionality.
1. The sensor reading often jumps to 30000lx momentarily, (measured using Lux Dash in Debug mode), and so the phone blinds you for while. This happens in a repeatable fashion when you hold the phone at certain angles. Try it yourself.
2. The N5 reads zero lux even in moderate/dim light, while my old N4 still reads around 10 lux. The N4 was much better as you could make a distinction between the dim light and no light at all.
On the new N5 you have to set the zero lux level so it's bright enought for moderate light, which means it's far too bright at night.
Why is the N5 sensor so poor? Or is the kernel? Really, this is pretty basic stuff. Come on Google, we want the autobrightness to work fine without having to download apps to try and fix the most basic settings.
(As per other threads, the N5 stock autobrightness is almost unusable!)
Same here. Only occurs in the kitchen under the spotlights. I've had 2 phones and the same has happened on both using lux.
Sent from my Nexus 5 using Tapatalk
Happy to see others having this issue as well. I always figured it was a Kitkat bug.
I had some dead pixels on my first N5, so I got a replacement. The replacement is now exhibiting this weird sensor issue (also spiking up to 30,000lux based on device orientation).
I have the same issue on my N5, sudden freak peaks of 15000 lux or more, then suddenly back to normal values of 50-80. Same behavior on stock kernel and Francos Kernel.
Hoping for a quick fix by Google.
Kusie
I'm having the same issue too, but it appears to be under certain lightbulbs that I have this issue. For example in 2 different situations, one I was in a restaurant and another while I was in my bathroom, and my phone would constantly pick up either 0 lux or 30000 lux (depending on the angle of the phone under the light). This is under halogen lighting.
When I get out of the restaurant and under regular lighting and when I'm in my bedroom (LED/CCFL lights), the light sensor would behave normally.
Anyone else have these issues?
Aria807 said:
Anyone else have these issues?
Click to expand...
Click to collapse
Yes, and it's not really reproduceable for me but it's very annoying and sometimes painful. This screen can get very bright and it's blinded me in the dark when this happens.
Is it the light sensor? Is it LUX? Does this happen without lux installed?
Can the sensor be calibrated or is it just bad hardware? This is a real annoyance. My S4 doesn't read 0 lux unless there is absolutely zero and it never jumps around. Even it's own screen reflecting on my face will cause it to read 1-10. That level of sensitivity is great for setting up lux to go subzero. Maybe the kernel is translating the sensor voltage output incorrectly?
Sent from my Nexus 5 using xda app-developers app
rabaker07 said:
Yes, and it's not really reproduceable for me but it's very annoying and sometimes painful. This screen can get very bright and it's blinded me in the dark when this happens.
Is it the light sensor? Is it LUX? Does this happen without lux installed?
Click to expand...
Click to collapse
Lux is a measurement of brightness.
I thought it was Lux causing it, but I have tried full wipe + reflashing a new rom, and my sensors still go a lil whack. This is flashing new rom + immediately downloading a sensor tool and checking the readings before installing Lux or any other apps.
However, Lux came out with a new version a week or so ago and it seems to have been waiving those spiked readings, so my phone atm isn't acting up super dim to super bright and back.
I still have this issue on 4.2.2.,very annoying. Is this a software issue or bad sensors?
Starts to piss me off so badly I think about sending my N5 back to google.
Happens both on stock auto brightness and yaab.
Help please?
Kusie
Yeah same here, very annoying, have to use Manuel britness very often
I have this same problem too. Using the Lux app debug mode I rotated the phone while in a room lit with incandescent bulbs and one lit with daylight. When rotating the phone I sometimes see a spike of 30000 lx but more importantly the sensor drops to 0 even though there is plenty of ambient light. During daylight I don't see the 30000 lx spikes but I still see the sensor dropping to 0 when there's plenty of ambient light.
I feel like the sensor is too far recessed into the phone and causing a tunnel effect. If the phone is looking at a dark shirt or surface that's a foot away from it, it will register 0 even though there's plenty of ambient light. This seems like a design flaw or a flaw in android's API.
Using the full version of Lux app might be able to fix it since it allows you to use the camera for ambient light detection but I haven't purchased the full app yet so I don't know.
Really wish android would have a solution for this because it's quite irritating.
Are you guys using the Lux app? I haven't had this problem with stock auto brightness.
clocinnorcal said:
Are you guys using the Lux app? I haven't had this problem with stock auto brightness.
Click to expand...
Click to collapse
With the stock auto brightness it was too bright in most cases and also in some cases the brightness would spike. Downloaded the free version of lux app in order to try to fix the problem and while it can adjust the brightness to be lower, the problem is that the light sensor gives low readings straight from the api.
I just installed Lux and I can't reproduce it on my Nexus. Mine always behaves correctly in automatic brightness, so I guess it's a hardware problem that only affects some devices?
I jump now in here as i have the same problem unfortunatley. I have no clue if its hardware related or software, but on my HTC One with kitkat running the same rom i dont have such issues s i guess its a HW fault. If anyone finds a solution or something that fixes this mess, would highly appreciate if wwe could keep this thread alive
I hope it's just a kernel issue where it's not translating the sensor output to the OS granularly enough. On my S4, it has to be truly zero light for it to see 0lx. Even in low low light, it's registering a value between 1 and 100. It makes it very easy to distinguish between no light (laying in bed) and low light (driving in the car, movie theater, etc). I hope they fix it because it's rather annoying that we're having this issue.
coolguy949 said:
I hope it's just a kernel issue where it's not translating the sensor output to the OS granularly enough. On my S4, it has to be truly zero light for it to see 0lx. Even in low low light, it's registering a value between 1 and 100. It makes it very easy to distinguish between no light (laying in bed) and low light (driving in the car, movie theater, etc). I hope they fix it because it's rather annoying that we're having this issue.
Click to expand...
Click to collapse
The next interesting thing is that it happens only in 1 out of 6 rooms at home. I hope I'm not totally crazy but could it be a bad combination between a sort of light bulb and the sensor?? I know this sounds totally stupid but I only can reproduce it with one light bulb. Or it is because that one light bulb is really low dimmed. I have to test that further tomorrow. Only have one dimmable light bulb atm to test so I will dim the others tomorrow that working atm.
noNeedforAsig
n3ocort3x said:
The next interesting thing is that it happens only in 1 out of 6 rooms at home. I hope I'm not totally crazy but could it be a bad combination between a sort of light bulb and the sensor?? I know this sounds totally stupid but I only can reproduce it with one light bulb. Or it is because that one light bulb is really low dimmed. I have to test that further tomorrow. Only have one dimmable light bulb atm to test so I will dim the others tomorrow that working atm.
noNeedforAsig
Click to expand...
Click to collapse
I remember reading something weeks ago that the sensor doesn't work well with certain bulbs. I can't seem to locate the thread though.
Hi,
i got my Zenfone 6 today, and i really like it, but there is one thing that probably makes me return it...
The display is flickering when it‘s set to really low brightness, i think its the backlight.
I‘m not sure if it's broken or not. So, am i the only one with a flickering display?
Thank you
07713 said:
Hi,
i got my Zenfone 6 today, and i really like it, but there is one thing that probably makes me return it...
The display is flickering when it‘s set to really low brightness, i think its the backlight.
I‘m not sure if it's broken or not. So, am i the only one with a flickering display?
Thank you
Click to expand...
Click to collapse
I had the same situation yesterday, it was on low brightness too.
But only for a few seconds, for now, everything seems fine, even in low brightness.
With adaptive brightness set on or off?
Do you have the latest firmware version WW-16.1210.1904.133?
It doesn‘t matterif adaptive brightness is on or off, it does it as soon as the display lowers its brightness to the 1st 1/4 of the brightness bar...
Ok. Do you have the latest firmware version WW-16.1210.1904.133?
_jis_ said:
Ok. Do you have the latest firmware version WW-16.1210.1904.133?
Click to expand...
Click to collapse
Hi, i have the same problem. Received the phone a week ago and trying to find a solution. I am on the last firmware, tried the dev option about overlay, hard reset and still the same. Going to send it back to Asus for a refund...
I wonder if this is software or hardware related. As of now i can't use it at night with low brightness.
It will probably be a problem for a particular phone, I would recommend that you replace it with a new one.
https://swedroid.se/forum/threads/snabba-fragor-snabba-svar-zenfone-6.165775/page-38#post-2443073
Thanks for the feedback. Called Asus this morning to replace it hopefully.
My Zenfone 6 does the same. If I set the adaptive brightness on the low brightness flickering disappears. I think it's a software related problem because others Zenfone have the same behaviour.
Tried it. No matter the settings it flickers. I found a video that match the problem, weird no one noticed : youtu.be/DN1La8AbZsI
Check at 1.16 min, on the right side, it flickers like that, when the luminosity is low. This is what i see on my screen.
Same here. White backgrounds flicker when brightness set to low. Tried disabling HW overlay, but it didn't help. Phone on the latest firmware WW_16.1210.1904.133.
Anybody letting the techs at Asus know about these problems? I would like to hear about a fix before I buy anything.
I am in touch with Asus France, i have to send back the phone for an exchange as they told me it MAY be a hardware problem.
I linked the thread to them if it can help.
Every zenfone I have had (2 and 3) have had this issue.
Skhio said:
I am in touch with Asus France, i have to send back the phone for an exchange as they told me it MAY be a hardware problem.
I linked the thread to them if it can help.
Click to expand...
Click to collapse
I think it's a software issue...if you let the brightness working in auto mode the problem disappears.
It is set in auto mode on my device and still the same. With or without doesn't help sadly.
Hmmm is this international version? The U.S is coming next month. Hopefully this get fix before I'm buying it.
Sent from my SM-G970U1 using Tapatalk
Wulff73 said:
I think it's a software issue...if you let the brightness working in auto mode the problem disappears.
Click to expand...
Click to collapse
Mine is flickering when brightness is set to low (about 1/4-th of the brightness slider and down) no matter auto or no auto.
Funny how we here in the US complain that so many phones are released in the EU, or India, or China long before they ever appear here....but in reality it could be that we benefit from this practice so that some of these issues can be resolved by others before we have to deal with them.
jaseman said:
Funny how we here in the US complain that so many phones are released in the EU, or India, or China long before they ever appear here....but in reality it could be that we benefit from this practice so that some of these issues can be resolved by others before we have to deal with them.
Click to expand...
Click to collapse
I hope that when this phone is released in your country, this issue will be solved definitively via software update. The way I see it, this problem isn't a huge problem, fortunately. Actually the screen flickering occours only if the brightness is set to a very low level (e.g. <20%) but, with this setting, the backlight is too dim as well for use even in a dark room (obviously for my taste). Since I use adaptive brightness with default settings, the minimum value the screen brightness reaches is 34% so I never get the problem....
guys anyone having an issue like mine? whenever my device gets hot my phone starts to dim the brightness! like even if im on max I notice an auto brightness lowering (and yes auto brightness is turned off)
this happens only when the device is hot! it used to happen only on 4k mod but now its always happening even after I went back to 1080... when I watch videos that require a lot of internet like 1080p or 4k content
or gaming, or whatever heavy duty, the device heats a quite enough and the brightness simply decides to lower it self...
Locking the phone to let it cool for a bit seems to make a difference but almost in a couple of seconds after continue using it dims back, until im in a cool environment or wait for the device to cool
is it only my device? or is it a software thing for all XZ premiums?
Id like to hear someone's perspective
thanks in advance
Hello, I've recently purchased a Oneplus 7 Pro and noticed it was using an OLED panel, the problem is that Burn-ins scare me a whole lot, as such, I have been wondering how others have been using their phones. I've tried using Google, but have found nothing truly satisfactory and as such, I have compilled a few questions i had about the display.
- Is screen burn-in still a real issue? and should I avoid using the phone over long periods of time?
- Do "True black" wallpapers help with this issue? what about dark gray? and a bright wallpaper?
- Do both the static navigation bar and status bar have issues? Same with the AOD, does the fingerprint icon cause issues?
- Should I take extra steps to prevent burn-in? (If so, please say which ones, eg. Any practices you have to prevent screen burn-ins)
(On a side note, does anyone approximatly know how long [in general] an OLED panel at medium brightness and daily moderate to heavy use has before it shows signs of burn-in?)
I'm sorry if this has already been addressed, but i have searched through the forums and have found nothing.
Thanks a lot!
CurlyApple said:
Hello, I've recently purchased a Oneplus 7 Pro and noticed it was using an OLED panel, the problem is that Burn-ins scare me a whole lot, as such, I have been wondering how others have been using their phones. I've tried using Google, but have found nothing truly satisfactory and as such, I have compilled a few questions i had about the display.
- Is screen burn-in still a real issue? and should I avoid using the phone over long periods of time?
- Do "True black" wallpapers help with this issue? what about dark gray? and a bright wallpaper?
- Do both the static navigation bar and status bar have issues? Same with the AOD, does the fingerprint icon cause issues?
- Should I take extra steps to prevent burn-in? (If so, please say which ones, eg. Any practices you have to prevent screen burn-ins)
(On a side note, does anyone approximatly know how long [in general] an OLED panel at medium brightness and daily moderate to heavy use has before it shows signs of burn-in?)
I'm sorry if this has already been addressed, but i have searched through the forums and have found nothing.
Thanks a lot!
Click to expand...
Click to collapse
I don't even think about it.
I share the same concerns.
The last OLED phone I had was a Galaxy Nexus and I told myself I'd never get an OLED screen again after that nightmare.
Dealing with the OLED issues has been better with improvements in the technology and overall quality control.
Android OS also has some changes that help prevent burn in. For example the navigation bar and status bar change colors based on the app.
With AOD I know Samsung for example slowly moves the elements around so it doesn't burn in. You can enable the Oneplus AOD with root but Always on Display isn't the same as the Ambient Display on stock Oneplus. Ambient display doesn't stay on screen long enough to really cause any burn in.
Best practices are to avoid high brightness, stay at half or less. If you have a game HUD or other static elements on screen for extended periods of time, rotate the phone when in landscape so it is less likely to burn in.
I'm not an expert on this so i'd like to hear others responses too. This is a more expensive flagship phone so I want to use it for games but avoid the burn in.
I've already read some reports of burn-in on Oneplus Chinese board. The culprits seem to be some Tencent games and its video streaming service. All have very high contrast UI elements, and users tend to turn the brightness very high.
This was the case with my plasma TV. Civ4 left some nasty burn-in in the first year but after so many years of heavy PC usage those remain the only true burn-ins on the TV. It depends on the app. Are there some ways to measure contrast of onscreen elements? In addition to phones I need to replace my plasma with OLED in the coming years.
I got burn in on my OnePlus 3 bc I keep it in my car and use it for a music player, there were times I left it on overnight on a static image multiple times, so if u plan keeping ur phone on all the time on a certain image then u don't have anything to worry about.
I used the Galaxy S3, Oneplus 3, Oneplus 5T all with OLEDs. No burn in. Never. Of course if you are and extrem case and you leave the screen static on for a lot of hours on several days there MIGHT be the risk. But with normal to "normal" heavy usage you shouldnt really be concerned.
CurlyApple said:
Hello, I've recently purchased a Oneplus 7 Pro and noticed it was using an OLED panel, the problem is that Burn-ins scare me a whole lot, as such, I have been wondering how others have been using their phones. I've tried using Google, but have found nothing truly satisfactory and as such, I have compilled a few questions i had about the display.
- Is screen burn-in still a real issue? and should I avoid using the phone over long periods of time?
- Do "True black" wallpapers help with this issue? what about dark gray? and a bright wallpaper?
- Do both the static navigation bar and status bar have issues? Same with the AOD, does the fingerprint icon cause issues?
- Should I take extra steps to prevent burn-in? (If so, please say which ones, eg. Any practices you have to prevent screen burn-ins)
(On a side note, does anyone approximatly know how long [in general] an OLED panel at medium brightness and daily moderate to heavy use has before it shows signs of burn-in?)
I'm sorry if this has already been addressed, but i have searched through the forums and have found nothing.
Thanks a lot!
Click to expand...
Click to collapse
Better u only turn it on for a few seconds, be carefull after 10 sec it gets critical..
Just don't leave the screen on at max brightness for long periods of time and you'll avoid burn in.
Because the pixels are self-illuminating and will eventually wear out/start dimming in an OLED display over time, this will probably be a concern with any phone that has such a display.
I had burn-in with my OnePlus 3T starting after a little over a year of use. I had my 6T for about 7 months and hadn't noticed any problems with it by that point.
I think the biggest culprit in long-term use is the notifications area of the status bar, unfortunately. The notification icons usually directly contrast with whatever is on the screen at the time, which ends up causing the pixels to wear out at different rates. While the burn-in on my 3T wasn't defined or crisp, there was a noticeable brightness difference where the icons usually display, and it was apparent any time there was a solid color in that area of the screen.
https://www.cnet.com/news/oled-screen-burn-in-what-you-need-to-know/
To fight this, keep up to date with swiping away notifications, and use gesture controls in OOS instead of the navigation bar.
Use Auto brightness and enjoy the phone...
Honestly, I would be concerned. I have noticed screen burn on my 7 Pro already. My specific case is that I use Waze while driving, and on long (> 1 hour) drives I get the UI lightly burned in. After I noticed it, I alternate the phone orientation 180 degrees to minimize its effects. I also have the "Colors" screen saver activate whenever plugged in, which has noticeably reduced & corrected the issue. Just be aware and adjust the phone orientation regularly and you should not see anything burn in.
My Galaxy S4 and 1+ 3T both had burn in, but after several years of use. (Same app was the culprit.) I think the reason it happened on my 7 Pro faster is because of the higher brightness and 90Hz refresh rate. Once I kicked it down to 60Hz it does not happen near as often .
thedr9669 said:
Honestly, I would be concerned. I have noticed screen burn on my 7 Pro already. My specific case is that I use Waze while driving, and on long (> 1 hour) drives I get the UI lightly burned in. After I noticed it, I alternate the phone orientation 180 degrees to minimize its effects. I also have the "Colors" screen saver activate whenever plugged in, which has noticeably reduced & corrected the issue. Just be aware and adjust the phone orientation regularly and you should not see anything burn in.
My Galaxy S4 and 1+ 3T both had burn in, but after several years of use. (Same app was the culprit.) I think the reason it happened on my 7 Pro faster is because of the higher brightness and 90Hz refresh rate. Once I kicked it down to 60Hz it does not happen near as often .
Click to expand...
Click to collapse
Do you have your screen turned to full brightness when using waze? I keep mine at about 40-50% brightness. I use maps for 2-3 hours a day 4 or 5 days a week and I have had my 7 Pro since launch and I have zero burn in. I have never had burn in going back to my note 3 days either. I/m actually looking at my OP6 right now as well and no burn in there either (bought that on launch day as well). I also activated forced 90hz all apps on my 7Pro as well and nothing yet. I'm guessing it's your screen brightness that is doing it. Nothing else makes any sense.
Tmobile demo both phone in my store have burn in.... But also does the note 9 and a few others.
Those have the same image on the screen 90% of the time and the screens are set to max brightness to show off the display. All AMOLED displays will burn in if you test your phone the same. When I use maps, I turn off auto brightness and just set it bright enough to see the screen which usually is about 40% brightness. I also change my wallpaper like once a week as well
Had burn in on both 6p and s9 and all in status bar and navigation bar. Now I've installed system tuner and switched on full immersive mode. You need to be rooted though. Using battery widget to look at battery life.
CurlyApple said:
Hello, I've recently purchased a Oneplus 7 Pro and noticed it was using an OLED panel, the problem is that Burn-ins scare me a whole lot, as such, I have been wondering how others have been using their phones. I've tried using Google, but have found nothing truly satisfactory and as such, I have compilled a few questions i had about the display.
- Is screen burn-in still a real issue? and should I avoid using the phone over long periods of time?
- Do "True black" wallpapers help with this issue? what about dark gray? and a bright wallpaper?
- Do both the static navigation bar and status bar have issues? Same with the AOD, does the fingerprint icon cause issues?
- Should I take extra steps to prevent burn-in? (If so, please say which ones, eg. Any practices you have to prevent screen burn-ins)
(On a side note, does anyone approximatly know how long [in general] an OLED panel at medium brightness and daily moderate to heavy use has before it shows signs of burn-in?)
I'm sorry if this has already been addressed, but i have searched through the forums and have found nothing.
Thanks a lot!
Click to expand...
Click to collapse
Used my OP3 for 3 years straight until I switched to the 7 pro. Never had to think about burn in. Just chill and enjoy the device
When using google maps or waze on long trips, keep the screen off till the next turn. That's what i do. I NEVER keep the screen on long enough with a static image. I don't think there is any tech that will not give a burn in with a static image over long periods of time. I will still pick OLED over LCD any day.
equlizer said:
When using google maps or waze on long trips, keep the screen off till the next turn. That's what i do. I NEVER keep the screen on long enough with a static image. I don't think there is any tech that will not give a burn in with a static image over long periods of time. I will still pick OLED over LCD any day.
Click to expand...
Click to collapse
Everyone should just have a spare lcd phone for navigation. I use an iphone 6s for navigation in my card. Tether data from my phone and dont have tk worry about burn in
I use mine for navigation ,i drive a convertible so the screen is always on high brightness.
Never had any issues with my galaxy s8 which i had for over a year and used it the same way. Poor thing had the maps on more than anything else.i broke the display before the any burn ins.
The display should not have any burn ins even after prolonged use.
However you might want to keep it at 90%max brightness.
I make the most of my oneplus 7 pro so if i notice any burn ins i'll just return it to warranty. I don't care ,i use the phone however i want to.
Also the colors are going to be visibly washed out after a few years of use compared to when it was new,that's why i always insure my phones and just get a brand new one before my contract expires.
In order to avoid getting burn-in you have to:
1. Avoid displaying images with static contents for more than one hour at a time. Many people get their keyboard burnt in because they text obsessively.
2. Avoid using a higher brightness than you need.
3. Maybe use the gesture based navigation.
Tipically burn in is a non-issue but displaying static content for more than an hour uninterrupted can get it to appear, depends on the panel, brightness and color being displayed.. Just pause what you're doing every once in a while and you should be fine.