Off late I'm noticing that whenever I turn on the display, it goes completely bright for maybe 5 seconds before adaptive brightness kicks in. Today I completely reset my phone and reflashed the latest factory image (MRA58R, I was on MRA58N previously). It was fine for a while (for a few hours) and now it has started behaving the same way. It works fine if I turn off adaptive display. This happens 90% of the time.
Has anyone else faced this?
---
I have filed a bug report, please star it.
https://code.google.com/p/android/issues/detail?id=196048
I've got the same issue on 6.0 stock not rooted. I've been fiddling around with lux trying to get it to stop going to max bright in low light settings... And it seems that the light sensor is getting incorrect readings in low light and it takes a few seconds for the sensor to start showing accurate levels for the light conditions. I would love to have adaptive brightness work as it used to - don't know what changed.
Same issue here.
Woah. I'm not alone. So for all you guys, it started just recently?
yeah. I noticed it a little less than a week ago
Do you use Gravity Box?
Issue came with that mod for me and even after removing it my Adaptive Brightness still doesn't work properly.
foxnutz said:
yeah. I noticed it a little less than a week ago
Click to expand...
Click to collapse
Hmm. Same here. Started last week. Will have to dig out what the root cause is.
altimax98 said:
Do you use Gravity Box?
Issue came with that mod for me and even after removing it my Adaptive Brightness still doesn't work properly.
Click to expand...
Click to collapse
Nope. I'm running completely stock, no root, even locked bootloader (for device protection feature).
I am running completely stock marshmallow no root, boot loader is locked, no gravity box. Same problem.
Is there any program we can use to monitor the readings at the light sensor is receiving?
I have tried two apps but that doesn't seem to gather data while running in background; only works when the app is opened. Still trying to find one that does background logging.
I have the same issue.
And I thought it was Gravity Box.... now I wonder if it's the November patch? Since there is report from people who never root and using stock?
Ok, so I found an app that can log data while in background. It's called Androsensor. It also has a companion app (Androsensor Keep Awake) which helps to hold a wakelock to gather more data. I tried it and I feel it's definitely not the sensor or it's driver/binary malfunctioning, it seems to be reporting proper values. Maybe more people can try it and report back.
i just bought my phone (brand new) update it right away to 6.0 and used it and having thesame issue!
that means this is google firmware problem!
The reason I believed it to be the sensor was because I used lux to try and fix this and noticed when the bug was occurring, as the screen just turned on and went to max brightness, lux showed the values from the sensor above 20000. Oddly enough if I had lux update every 3 sec it would sometimes capture the actual light levels on the second update and adjust accordingly. I'll check out the app you mentioned and see what shakes out.
I'm having it too, also completely stock and unrooted, first noticed it a few days ago. A friend of mine also has it. He is also stock, I'm not sure about his root status though.
Ok got some interesting results this morning using androsensor. First of all I was unable to recreate the bug while using the keep awake helper app... Which leads me to believe that there may be some issue with the sensor values being calculated/averaged by the autobrightness code/program as the device wakes up from sleep. perhaps android is shutting off the light sensor when the device goes to sleep and this causes a reset? So it appears that it's not getting wrong values rather, that the data being drawn from the sensor is reset or perhaps recalculated as the device wakes back up. Almost as if it can't remember the last light level that was observed. I uninstalled the wake lock helper and was able to recreate the bug by letting the device "sleep" (leaving the screen off for maybe 5 seconds). So while the sensor showed readings of 2 lux the screen brightness was increased erroneously until the auto brightness refreshed and then after a few updates on the sensor the correct brightness was applied to the screen. Curious results. Can anyone else try to recreate the bug using androsensor and the wakelock helper program? I'm hoping I didn't run into some user error there.
I too tried without the wakelock helper and got the same result which made me believe it's not the sensor that's causing it. Will try the same with the helper app and report back.
Just tried Androsensor with the helper and I was unable to reproduce the bug, exactly what foxnutz faced.
Alright so we got some results! Just for the sake of being thorough, can anyone else replicate these results that andr0idfreak and myself saw? It seems holding a wakelock on the sensor stops this bug.
Now where do we go from here? It's been an awfully long time since I've done anything with logcat... But I think that may be our best bet to find out what's really going on here. I'll have to do some homework before proceeding. Will report back.
I think we should file a bug report here.
https://code.google.com/p/android/issues/list
I think a bug report is probably worthwhile. I thought it was some combo of xposed and gravitybox as well but I flashed my stock system back and it's doing the same thing.
So after this much anticipated Oreo release, my display has been left faded looking. It's as though you have the brightness turned all the way up which washes out the color, but even when it's turned down. It's rather frustrating & sRGB is not ticked. Please tell me this isn't the new display & what I could possibly do to change it.
Edit: Also just realized when I change my screen mode in display settings, nothing happens. I can even turn the red, green and blue all the way down with no effect. Anyone else experiencing this issue with Oreo?
Have to say no, that has not happened for me. Display looks the same and changing display settings changes the screen for me. Perhaps a reboot might help...
Do a Full reset, sounds like the ota bugged your settings out.
I've been on Oreo since the release and haven't had any issues with screen color or resolution.
Did you proceed to do the above posted steps? I myself would also say to factory reset the system.
If so, would you mind letting us know how it went and if it fixed the issue at hand.
The only place I've noticed something like this, is when using Google Maps through Android Auto, with my Vehicles display. I get the faded or Ghosting on the display. If I change from maps, to phone and back to maps it's fine again. But it's only temporary. This all started after I got the Oreo update. I'm still actively troubleshooting to find out if the cable is the problem or if it's related to the phone.
after 2 resets im good. started device as new and bo restoration of apps/go from there
So I was appreciating the beautiful display on the Note 8 and it's abilities again today by watching a HDR video from YouTube on it, but I noticed something weird. Whenever I went from a bright to a dark environment, (lit bedroom to dark living room) the screen would drop to a lower brightness, then realize it's in HDR mode and go all the way back up, and it would alternate multiple times as I moved around in the dark environment. It would drop to a low brightness, pick back up to full, drop, repeat. Can anyone else test to see if this is happening with theirs too?
Settings: WQHD+ resolution, Auto Brightness enabled, Video Enhancer enabled
Video:https://youtu.be/tO01J-M3g0U
This will help me confirm whether it is indeed a software bug introduced in Oreo/April Patch or if it's my own hardware that's having issues. Thanks for the help!
I would say it is a software bug.
This was happening to me after the Oreo update, unsure what I done that resolved it though but, after flashing a custom rom and going back to stock it has worked fine for me. Using the same Oreo package that I used to update to Oreo the first time also.
I am really sad to hear about all these bugs due to OREO updating, they make me think that it has far more cons than pros over nougat, in my country no Oreo ota yet, I will stay this way until a really good oreo comes out...
After my Mi A2 was updated from Android 8 O to Android 9 P, I have to face lots of bugs and some serious issues. Although I already tried factory resetting, it doesn’t help. Many A2 users also face these issues.
1. Portrait Mode – Unable to focus on any other subjects, except a subject in the middle of the frame. That means whenever you touch on the screen to focus, focusing does not work for you at all. This is one of most serious issues for users who love photography.
2. Fingerprint Scan – Significantly slower scanning speed. Very annoying.
3. Screen Brightness Dropping – When I was on Android 8 O, I always adjusted the brightness scale to 30-40% and it’s bright enough. But now, for Android 9 P, I have to slide the scale to 70-80% so I can see the screen clearly. (Adaptive Brightness already turned off)
+++ There's an explanation that this screen brightness change is not a bug. Find out more here: https://forums.androidcentral.com/g...ubt-about-display-brightness-android-pie.html
Thanks @Varun.Shanbhag for the information. +++
4. Heating Issue – I’ve noticed that while charging the phone, when it was on Android 8 O, the temperature never got more than 39°C, but now, on Android 9 P, it sometimes gets to 41°C. (Refer to the app ‘Ampere’)
Moreover, when using camera, it gets hot too quickly.
However, I am not sure if there’s only me facing this overheating issue.
It is likely to be caused by CPU freq. issue stated in the following thread: https://forum.xda-developers.com/mi-a2/help/little-cpu-stucks-1401-mhz-min-freq-t3851184
5. Touch Screen – Touch screen seems to be less responsive than before. I can notice its latency. Sometimes I have to double tap the screen to get something done, because the first tap does not respond. (It can be easily noticed this issue with back button)
6. Lower Audio Volume – Some users say that they're facing lower audio volume issue when using earphones or headphones.
7. Face ID - Face ID doesn't work stably, it sometimes works and sometimes does not.
8. Front Flash Issue - front flash doesn't work when I turn it on in camera app. (But it works when set it as 'Auto')
9. Black Banding on Camera Screen - There're black bandings appear on the screen while using camera app, they look like signal noise appears on TV.
10. Camera App Crashes - Camera sometimes crashes, for example, the camera app says "Camera Error - Can't connect to camera" when I switch the camera from back to front in Portrait Mode.
11. Whole system seems to be less stable than it was in Android Oreo.
[List last updated: Jan 3, 2019]
----------------------------------
I hope all issues will be fixed in the next update.
Are you facing any other issues else?
TheGuyBelow said:
After my Mi A2 was updated from Android 8 O to Android 9 P, I have to face lots of bugs and some serious issues. Although I already tried factory resetting, it doesn’t help. Many A2 users also face these issues.
1. Portrait Mode – Unable to focus on any other subjects, except a subject in the middle of the frame. That means whenever you touch on the screen to focus, focusing does not work for you at all. This is one of most serious issues for users who love photography.
2. Fingerprint Scan – Significantly slower scanning speed. Very annoying.
3. Screen Brightness Dropping – When I was on Android 8 O, I always adjusted the brightness scale to 30-40% and it’s bright enough. But now, for Android 9 P, I have to slide the scale to 70-80% so I can see the screen clearly. (Adaptive Brightness already turned off)
4. Heating Issue – I’ve noticed that while charging the phone, when it was on Android 8 O, the temperature never got more than 39°C, but now, on Android 9 P, it sometimes gets to 41°C. (Refer to the app ‘Ampere’)
Moreover, when using camera, it gets hot too quickly.
However, I am not sure if there’s only me facing this overheating issue.
5. Touch Screen – Touch screen seems to be less responsive than before. I can notice its latency. Sometimes I have to double tap the screen to get something done, because the first tap does not respond. (It can be easily noticed this issue with back button)
6. Lower Audio Volume – Some users say that they're facing lower audio volume issue when using earphones or headphones.
I hope all issues will be fixed in the next update.
Are you facing any other issues else?
Click to expand...
Click to collapse
I have a little issue with after ending a call, after some time device make some sound like I ended a call (beep like) and screen randomly wake up, it happens only after ending a call, and notification led pulse is laggy. . .it was laggy even I was on Oreo.
razor17 said:
I have a little issue with after ending a call, after some time device make some sound like I ended a call (beep like) and screen randomly wake up, it happens only after ending a call, and notification led pulse is laggy. . .it was laggy even I was on Oreo.
Click to expand...
Click to collapse
I'm not sure about beep and screen randomly wake up, but the laggy LED pulse happens to me, that makes me annoyed sometimes ?
I also found that the LED issue has appeared since Android 8 O.
yeah the laggy led looks so cheap and retro like it was used in the last century ???
Hey guys, i just updated to pie December update, and the wifi tethering band locked to 2,4Ghz, any way to enable the 5ghz?
Really considering flashing the custom Pixel Experience ROM. Having a lot of bugs on Pie. Did the factory reset. None of them gone.
Any suggestions ? Should I just go for Custom. Or should I wait for next update ?
TheGuyBelow said:
After my Mi A2 was updated from Android 8 O to Android 9 P, I have to face lots of bugs and some serious issues. Although I already tried factory resetting, it doesn’t help. Many A2 users also face these issues.
1. Portrait Mode – Unable to focus on any other subjects, except a subject in the middle of the frame. That means whenever you touch on the screen to focus, focusing does not work for you at all. This is one of most serious issues for users who love photography.
2. Fingerprint Scan – Significantly slower scanning speed. Very annoying.
3. Screen Brightness Dropping – When I was on Android 8 O, I always adjusted the brightness scale to 30-40% and it’s bright enough. But now, for Android 9 P, I have to slide the scale to 70-80% so I can see the screen clearly. (Adaptive Brightness already turned off)
4. Heating Issue – I’ve noticed that while charging the phone, when it was on Android 8 O, the temperature never got more than 39°C, but now, on Android 9 P, it sometimes gets to 41°C. (Refer to the app ‘Ampere’)
Moreover, when using camera, it gets hot too quickly.
However, I am not sure if there’s only me facing this overheating issue.
5. Touch Screen – Touch screen seems to be less responsive than before. I can notice its latency. Sometimes I have to double tap the screen to get something done, because the first tap does not respond. (It can be easily noticed this issue with back button)
6. Lower Audio Volume – Some users say that they're facing lower audio volume issue when using earphones or headphones.
I hope all issues will be fixed in the next update.
Are you facing any other issues else?
Click to expand...
Click to collapse
U didn't miss anyone of them ... same here except I don't have any heating problems
add to them that face ID is not working always anymore ... sometimes need to restart phone othertimes it works on it own ... hope Xiaomi fix this ASAP
TheGuyBelow said:
After my Mi A2 was updated from Android 8 O to Android 9 P, I have to face lots of bugs and some serious issues. Although I already tried factory resetting, it doesn’t help. Many A2 users also face these issues.
1. Portrait Mode – Unable to focus on any other subjects, except a subject in the middle of the frame. That means whenever you touch on the screen to focus, focusing does not work for you at all. This is one of most serious issues for users who love photography.
2. Fingerprint Scan – Significantly slower scanning speed. Very annoying.
3. Screen Brightness Dropping – When I was on Android 8 O, I always adjusted the brightness scale to 30-40% and it’s bright enough. But now, for Android 9 P, I have to slide the scale to 70-80% so I can see the screen clearly. (Adaptive Brightness already turned off)
4. Heating Issue – I’ve noticed that while charging the phone, when it was on Android 8 O, the temperature never got more than 39°C, but now, on Android 9 P, it sometimes gets to 41°C. (Refer to the app ‘Ampere’)
Moreover, when using camera, it gets hot too quickly.
However, I am not sure if there’s only me facing this overheating issue.
5. Touch Screen – Touch screen seems to be less responsive than before. I can notice its latency. Sometimes I have to double tap the screen to get something done, because the first tap does not respond. (It can be easily noticed this issue with back button)
6. Lower Audio Volume – Some users say that they're facing lower audio volume issue when using earphones or headphones.
I hope all issues will be fixed in the next update.
Are you facing any other issues else?
Click to expand...
Click to collapse
About the heating problem probably your cpu stacks at 1401 mhz when charging. Check it with cpu spy. This was happened to me with pie.
jerryshaw12 said:
Hey guys, i just updated to pie December update, and the wifi tethering band locked to 2,4Ghz, any way to enable the 5ghz?
Click to expand...
Click to collapse
There's no this issue happens to me, I can switch between 2.4 and 5 normally.
BTW, try finding out this, in case it can help.
https://forum.xda-developers.com/mi-a2/help/5ghz-wifi-t3827425
vagsvag said:
About the heating problem probably your cpu stacks at 1401 mhz when charging. Check it with cpu spy. This was happened to me with pie.
Click to expand...
Click to collapse
Is that the same issue people talking about in this thread? https://forum.xda-developers.com/mi-a2/help/little-cpu-stucks-1401-mhz-min-freq-t3851184
I think Xiaomi should fix these bugs ASAP, seems there're too much troubles here, as if we are using extremely unstable buggy custom rom LOL.
Mem_0 said:
U didn't miss anyone of them ... same here except I don't have any heating problems
add to them that face ID is not working always anymore ... sometimes need to restart phone othertimes it works on it own ... hope Xiaomi fix this ASAP
Click to expand...
Click to collapse
Thanks for your information, I've added it to the list. I also hear about Face ID issue on Pie, so you can be sure that there's not only you are facing haha.
I feel kinda sad with this update. We should report all the problems to Xiaomi as much as we can, just hope the dev can hear our voices.
TheGuyBelow said:
Is that the same issue people talking about in this thread? https://forum.xda-developers.com/mi-a2/help/little-cpu-stucks-1401-mhz-min-freq-t3851184
I think Xiaomi should fix these bugs ASAP, seems there're too much troubles here, as if we are using extremely unstable buggy custom rom LOL.
Click to expand...
Click to collapse
Oreo is ok, i have downgrade my phone after some hours using pie. Pie for me it is in early beta.
How can we report about this ?
Gps problems
I'm also having issue with lags. Fingerprint scanner is lagging from time to time.. Overall daily task from switching apps to bring back to home screen also lags.
Disabling adaptive brightness seems to help improve the lag so far...
Sent from my Mi A2 using Tapatalk
TheGuyBelow said:
After my Mi A2 was updated from Android 8 O to Android 9 P, I have to face lots of bugs and some serious issues. Although I already tried factory resetting, it doesn’t help. Many A2 users also face these issues.
1. Portrait Mode – Unable to focus on any other subjects, except a subject in the middle of the frame. That means whenever you touch on the screen to focus, focusing does not work for you at all. This is one of most serious issues for users who love photography.
2. Fingerprint Scan – Significantly slower scanning speed. Very annoying.
3. Screen Brightness Dropping – When I was on Android 8 O, I always adjusted the brightness scale to 30-40% and it’s bright enough. But now, for Android 9 P, I have to slide the scale to 70-80% so I can see the screen clearly. (Adaptive Brightness already turned off)
4. Heating Issue – I’ve noticed that while charging the phone, when it was on Android 8 O, the temperature never got more than 39°C, but now, on Android 9 P, it sometimes gets to 41°C. (Refer to the app ‘Ampere’)
Moreover, when using camera, it gets hot too quickly.
However, I am not sure if there’s only me facing this overheating issue.
5. Touch Screen – Touch screen seems to be less responsive than before. I can notice its latency. Sometimes I have to double tap the screen to get something done, because the first tap does not respond. (It can be easily noticed this issue with back button)
6. Lower Audio Volume – Some users say that they're facing lower audio volume issue when using earphones or headphones.
7. Face ID - Face ID doesn't work stably, it sometimes works and sometimes does not.
I hope all issues will be fixed in the next update.
Are you facing any other issues else?
Click to expand...
Click to collapse
I just got my Global A2, 4/64 two days ago. Updated to Pie and have Dec Patch.
1) Portrait works fine. I can focus on any part of the scene and that subject will be in focus. Works quickly and reliably.
2) Fingerprint scan is quick with zero issues holding my finger at any angle. No lag whatsoever.
3) I went straight to Pie, so had zero experience with Oreo on the A2, but screen brightness behaves similar to the Moto G5+ that I had before. Adaptive brightness also behaves the same.
4) I never checked the phone with Oreo, but when charging on Pie, the phone feels cool to the touch. Cooler than my Moto G5+. BTW, I am using the OEM Moto QC 3.0 charger with the A2.
5) Touch screen is as responsive as my Moto G5+ and my Wife's Moto G6.
6 and 7) I don't use headphones or Face ID.
Hemicrusher said:
I just got my Global A2, 4/64 two days ago. Updated to Pie and have Dec Patch.
1) Portrait works fine. I can focus on any part of the scene and that subject will be in focus. Works quickly and reliably.
2) Fingerprint scan is quick with zero issues holding my finger at any angle. No lag whatsoever.
3) I went straight to Pie, so had zero experience with Oreo on the A2, but screen brightness behaves similar to the Moto G5+ that I had before. Adaptive brightness also behaves the same.
4) I never checked the phone with Oreo, but when charging on Pie, the phone feels cool to the touch. Cooler than my Moto G5+. BTW, I am using the OEM Moto QC 3.0 charger with the A2.
5) Touch screen is as responsive as my Moto G5+ and my Wife's Moto G6.
6 and 7) I don't use headphones or Face ID.
Click to expand...
Click to collapse
If u used Oreo before u upgraded pie u would saw the difference
I can't connect phone to my PC after update, i get 'USB Device Not Recognized' notification when I try to connect. Anybody else has this issue?
Mem_0 said:
If u used Oreo before u upgraded pie u would saw the difference
Click to expand...
Click to collapse
Everything is working perfectly. No lag choosing focus points in portrait, no lag using the finger print sensor, no lag using the screen, adaptive brightness, heat issues etc.? That all the behavior I am seeing would be better with Oreo?
Mem_0 said:
If u used Oreo before u upgraded pie u would saw the difference
Click to expand...
Click to collapse
Hello
I was on Oréo before and I did not notice any difference in the use with Pie, I am very fond of this version (sorry for English).