Related
This module aims to fix Nexus 5 ambient light sensor issues leading to random auto-brightness spikes under certain lighting.
The issue
Sometimes the light sensor goes crazy and reports 30000 lux even in a dim light because of what auto-brightness attempts to blind you in a moment. These random spikes happen when you hold a phone at certain angles and depend on light bulbs used in a room.
The solution
The fix is implemented as an Xposed module.
Basically, it is a filter inserted near a point where native HAL communicates to Android framework. It intercepts all sensor readings and replaces abnormal 30000 lux (and 0 lux following 30000) with an averaged value from a sliding window. This affects any process that use Android sensors API including system_process, so that default Android auto-brightness works fine too (no need to use apps like Lux Dash to workaround the issue).
Installation
Download and install Xposed framework
Then install Nexus 5 Light Sensor fix module and activate it
Reboot
Usage
The module provides no user interface, nor it runs any services in a background. It only injects a proxy method to the implementation of Android sensors API. You won't be able to notice it in the main menu or in a task manager. Think of it as a patch that can be turned on and off through Xposed installer.
Source
The mod is open source (with permissive MIT licence), the source code is available on my GitHub.
Thanks
@rovo89 for his Xposed framework
@n3ocort3x and @wantabe for the initial attention and for kicking me up to finally create a new thread
and you (the community) for your feedback
More on the issue
Two major issues with the Nexus 5 ambient light sensor (original module announcement)
Palmadores said:
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.
Click to expand...
Click to collapse
exorz said:
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.
Click to expand...
Click to collapse
Is the Auto-Brightness Functionality wonky on the Nexus5?
Aria807 said:
I think it may be bugged with Halogen lighting (correct me if I'm wrong). My home is ~ 18 years old, and we have some bulbs that have not been changed yet (yellow). Sometimes when I use my N5 under those lighting, the sensors go whack and don't register properly picking up 0lx, then spike up to 30000lx. Once I move to areas in the house with newer bulbs, the sensors work normal, picking up the right readings.
Click to expand...
Click to collapse
Well done! Auto-brightness accuracy is much improved indoors! Appreciate your work on this!
Do I need to disable the modules if I dirty flash a new Carbon nightly? Or is that not necessary
augoza said:
Do I need to disable the modules if I dirty flash a new Carbon nightly? Or is that not necessary
Click to expand...
Click to collapse
I'm not sure, cause I use stock ROM, but I guess there is no need to disable it. As I can see from Carbon sources, related parts of code was not modified at all. To be sure, please ask ROM developers or other Xposed guys.
1.1 update won't install on nexus 5 signature mismatch
Sent from my Nexus 5 using Tapatalk
ddloco said:
1.1 update won't install on nexus 5 signature mismatch
Click to expand...
Click to collapse
I know, this is my fault and this is actually stated in the module description. Please remove version 1.0 and install 1.1 from scratch.
Still coming up very bright compared to Lux. Battery drain WILL be an issue.
mcnob said:
Still coming up very bright compared to Lux. Battery drain WILL be an issue.
Click to expand...
Click to collapse
The mod only removes random spikes reported by sensors. It does not affect an algo used by stock auto-brightness (any auto-broghtness is basically a function that maps a given input value from the sensors to the screen brightness; the mod just removes some trash from the input).
AFAIK the stock auto-brightness is configured through framework-res (google: config_autoBrightnessLcdBacklightValues, e.g. http://forum.xda-developers.com/showthread.php?t=2616914). Probably there is some app/mod for tweaking these options.
Wonder if custom ROMs like Omni and CM already have the fix baked in?
Anyone tries this on something other than an N5?
Motorola perhaps?
Sent from my DROID RAZR M using Tapatalk
FirePsych said:
Anyone tries this on something other than an N5?
Motorola perhaps?
Click to expand...
Click to collapse
I'm pretty sure this wouldn't make any sense, at least with current implementation, which compares each input value against hardcoded 30000 lux.
bland.life said:
Wonder if custom ROMs like Omni and CM already have the fix baked in?
Click to expand...
Click to collapse
The problem is that a code to be patched is located in a device-independent part of Android, but only Nexus 5 build should be modified. However, I didn't research well whether there is a way to build some piece of base framework only for a particular device. Probably Omni/CM guys know better.
mcnob said:
Still coming up very bright compared to Lux. Battery drain WILL be an issue.
Click to expand...
Click to collapse
Must be a variance between different devices because on my N5 auto-brightness indoors at night looks just a little on the dim side. In brighter light it looks good to me but I can't tell you what percentages it's using. I would probably like it 2 or 3 percentage points higher indoors but I'm fine with the way it is now. At least on my device I haven't seen any noticeable effect on battery life with auto-brightness on most of the time. Still getting 5-9 hrs of screen on time with my use. I made a comment in a previous post about auto-brightness being more accurate, I was referring to the way it would constantly adjust the brightness level and the changes would be big ones. Personally I think auto-brightness is much better with the module installed and in my case useable now. No, it's not as accurate as the auto-brightness is on my One X, which is amazingly accurate, for that kind of accuracy I would use something like Lux, maybe in conjunction with the module. I would give it a shot myself but I've purchased enough apps to modify the display brightness as it is. Running stock 4.4.2.
Edit:
Forgot to mention I'm using the dimmer backlight setting in the config file for the ElementalX kernel. I don't think that makes much of a difference in accuracy, if any, just how dark the display can potentially go. I also completely forgot that the dimmer backlight and auto-brightness levels are options available in the GravityBox module. As effing long as I've used GB I've never used those two options!
abusalimov said:
I'm pretty sure this wouldn't make any sense, at least with current implementation, which compares each input value against hardcoded 30000 lux.
Click to expand...
Click to collapse
Yup. Didn't work on my Razr M.
Sent from my DROID RAZR M using Tapatalk
I don't know what the issue is lol, but I have Franco kernel so I assume I'm immune to this right?
Sent from my Nexus 5 using Tapatalk
Deeco7 said:
I don't know what the issue is lol, but I have Franco kernel so I assume I'm immune to this right?
Click to expand...
Click to collapse
It doesn't matter, which kernel do you run, ALS is a user space driver. BTW I use franco kernel too.
10000 lux
My N5 reports 10000 lux instead of 30000, very annoying
Running CM11.0 m5
zbloh said:
My N5 reports 10000 lux instead of 30000, very annoying
Running CM11.0 m5
Click to expand...
Click to collapse
Thanks for reporting. Is it reproduced on CM11.0 M5 only, did you try other ROMs? Does it show exactly 10000.0 lux? If so, I could catch this value as well.
New version 1.2 is available now:
- Always replace 0 lux with 1 lux to prevent auto-brightness changing hither and thither in a very low light environment
- Do not feed replaced values back to EMA filter (makes it more responsive to newly coming proper readings)
- Filter out 10000 lux as well (reported by zbloh)
Hi guys, I'm currently on on the last Existent MM rom, and I find the led brightness too low for me, so that I can barely notice it when it is not night time.
I remember that on some KK roms or Aosp based roms the brightness was far more efficient.
Is it kernel related? Or is there a way to tweak some files to make it brighter?
Thanks
TheLonelyCyborg said:
Hi guys, I'm currently on on the last Existent MM rom, and I find the led brightness too low for me, so that I can barely notice it when it is not night time.
I remember that on some KK roms or Aosp based roms the brightness was far more efficient.
Is it kernel related? Or is there a way to tweak some files to make it brighter?
Thanks
Click to expand...
Click to collapse
IDK for me it is bright enough also am on latest existenz rom
Try cleaning the speaker grills
I am having a bit of issues lately with youtube, which is the main use of my MiPad.
Youtube started lagging few weeks ago for me. Like missing frames every now and then.
If I clean install a ROM the YT will work awhile normally but after few days and after installing some other apps the lagging starts again.
First I thought it was just the new F1xy kernel and reverted back to old fixy but problem remained. Then I tried Smoke kernel and problem remained.
Then I clean installed cDroid (new blobs) and everything was fine, for awhile. After installing Chrome, the lagging came back and I thought that Chrome was the problem and uninstalled it and videos worked awhile okey but then the lagging came again.
I've now tried several kernels and LOS14 (new blobs) and crDroid and installing and uninstalling YT and clearing its cache and whatnot rebooting and lagging always comes back sooner or later.
I used to run LOS14 with fixy or foxy and had no major issues with YT but now I just can't seem to shake this problem away.
I now run crDroid and SmokeR21.5 and with gaming or video-profile I might be able to watch some YT without lagging, but eventually it starts to jerk.
Does anyone else have this kind of lagging/jerking with YT and does anyone know how to get rid of it?
Now I haven't had any serious lagging for awhile and I have no idea why. I still run crDroid and SmokeR kernel. Bloody magic if you ask me...
And lags are back yet again. Every 10ish seconds roughly there is a slight jerk [emoji21]
I am using SmokeR kernel with gaming profile. Cpu freq doesn't dip under 696Mhz but still lags happen. Damn!
This might be a 1080p60 issue. At least yesterday I had no hiccups with normal 1080 video but 60fps one had occasional lags. Gonna try the new Smoke LOS14 next to see how that handles videos.
Have you tried Smoke LOS 14.1? Seems that YouTube issue is fixed there.
RushArt said:
Have you tried Smoke LOS 14.1? Seems that YouTube issue is fixed there.
Click to expand...
Click to collapse
I am actually in the middle of flashing it atm.
Tautologica said:
I am actually in the middle of flashing it atm.
Click to expand...
Click to collapse
Great. Finally after so long, we might have ROM that YouTube don't sucks
Some results;
With Smoke LOS 14.1 I was able to watch 1080p60 videos without a hitch and without the performance app for few days iirc but after that videos started jerking so I installed the performance app and tried the with different profiles. Only with the Gaming profile I was able to watch 1080p60 videos without problems. So the Smoke LOS 14.1 is one solution for me.
Unfortunately that ROM is still too beta. Battery consumption and deep sleep behaviour is just bad and I would estimate that I could only get 4ish hours of SOT during few days cos of the battery drain.
So I decided to give crDroid 3.6 and F1xy 9.3 beta a go.
It seems that Youtube is having some mobile issues with 1080p60 videos and those are not available atm, 720p60 is the highest atm. I suppose they will fix that soon.
Anyway, crDroid + 9.3 worked like a charm for roughly 6 hours (minus the artifacts ofc). Then the jerks came back and Spectrum app didn't help at all. No matter what profile I used, I still got at least mild frame drops.
So I played with Kernel Auditor a bit and noticed that only settings that helped was if I set max and min CPU freq to the same value, e.g. 1800Mhz, all the YT videos play nicely. Even with 1000Mhz there was no huge frame drops. I am going to do some more testing but at this moment I speculate that the frame drops occur when CPU frequency fluctuates.
Has anyone else noticed anything like this? Am I the only one with these frame drops (lags, jerks, hitches) in 60FPS YT videos?
And after writing that message above 720p60 videos played just fine with Balanced profile without tinkering with frequencies. Idk what is going on with this tablet...
I think I found it what is causing the lags on youtube. I think it is the bloody Live Display setting and particularly its Night setting that is doing this.
I tried it few time to switch between Night and Off settings and with Night setting 720p60 videos lagged always and with Day or Off videos ran just fine with F1xy and Balanced profile.
I don't get it why changing a color temperature would cause something like this but at least I found a way to reproduce the issue.
So could someone else try and reproduce this issue:
1. Go to Settings --> Display --> LiveDisplay --> Display Mode --> Choose Night
2. Try some 1080p60 or 720p60 Youtube video.
3. If you get lags, change the LiveDisplay to Off or Day and try again.
Cheers.
Tautologica said:
I think I found it what is causing the lags on youtube. I think it is the bloody Live Display setting and particularly its Night setting that is doing this.
I tried it few time to switch between Night and Off settings and with Night setting 720p60 videos lagged always and with Day or Off videos ran just fine with F1xy and Balanced profile.
I don't get it why changing a color temperature would cause something like this but at least I found a way to reproduce the issue.
So could someone else try and reproduce this issue:
1. Go to Settings --> Display --> LiveDisplay --> Display Mode --> Choose Night
2. Try some 1080p60 or 720p60 Youtube video.
3. If you get lags, change the LiveDisplay to Off or Day and try again.
Cheers.
Click to expand...
Click to collapse
What kind of lag you are getting? I've used LiveDisplay since day 1 and there is no lag annoying enough to me. I am using F2FS file system though. And horrible battery drain when screen off (1% per hour) with ForceDoze and Wi-Fi off.
RushArt said:
What kind of lag you are getting? I've used LiveDisplay since day 1 and there is no lag annoying enough to me. I am using F2FS file system though. And horrible battery drain when screen off (1% per hour) with ForceDoze and Wi-Fi off.
Click to expand...
Click to collapse
Missing frames. Video jerks/skips. This can happen every 2 secs or every 10ish secs. Forcing CPU min and max freq to the same value fixed this as well when I tested.
I suppose it could be something else causing this but definitely LiveDisplay settings activate this (for me) when I tested my hypothesis few times yesterday.
There are different revisions of Mipad so this might not be issue for everyone.
And this also explains why usually after few days this always started happening to me when I flashed a new rom. I probably activated LiveDisplay after few days of use...
Tautologica said:
Missing frames. Video jerks/skips. This can happen every 2 secs or every 10ish secs. Forcing CPU min and max freq to the same value fixed this as well when I tested.
I suppose it could be something else causing this but definitely LiveDisplay settings activate this (for me) when I tested my hypothesis few times yesterday.
There are different revisions of Mipad so this might not be issue for everyone.
And this also explains why usually after few days this always started happening to me when I flashed a new rom. I probably activated LiveDisplay after few days of use...
Click to expand...
Click to collapse
Yeah, it could be something specific for your MiPad or software set up.
Out of topic question, but do you experience same battery drain too when screen is off (around 1% per hour?)
I think this has to be a LOS14 issue cos I have had the same jerking in all highwaystar based roms and the new smoke LOS14. I just can't confirm now that if the LiveDisplay was the issue in those roms. But I bet it was cos I started using it not so long ago.
RushArt said:
Yeah, it could be something specific for your MiPad or software set up.
Out of topic question, but do you experience same battery drain too when screen is off (around 1% per hour?)
Click to expand...
Click to collapse
Naah mate. Atm I have pretty decent deep sleep behaviour. I am running crDroid 3.6 and Fixy 0.93beta iirc.
Tautologica said:
I think this has to be a LOS14 issue cos I have had the same jerking in all highwaystar based roms and the new smoke LOS14. I just can't confirm now that if the LiveDisplay was the issue in those roms. But I bet it was cos I started using it not so long ago.
Naah mate. Atm I have pretty decent deep sleep behaviour. I am running crDroid 3.6 and Fixy 0.93beta iirc.
Click to expand...
Click to collapse
Ah, shoot. So we are talking about totally different thing. I had the impression that you are using LOS 14.1 Smoke, my bad. Personally I had no issue with LOS 14.1 for YouTube even using LiveDisplay. Just that annoying battery drain.
Btw, is there any bug for CrDroid (other than non working camera)? Because if turning LiveDisplay will give no lag YouTube, plus great sleep behavior I'd rather flash that instead.
RushArt said:
Ah, shoot. So we are talking about totally different thing. I had the impression that you are using LOS 14.1 Smoke, my bad. Personally I had no issue with LOS 14.1 for YouTube even using LiveDisplay. Just that annoying battery drain.
Btw, is there any bug for CrDroid (other than non working camera)? Because if turning LiveDisplay will give no lag YouTube, plus great sleep behavior I'd rather flash that instead.
Click to expand...
Click to collapse
I was using LOS14 Smoke just awhile ago but the nagging youtube lag appeared ( I presume cos I started using LiveDisplay) and yeah there was some weird deep sleep issues with that rom. Check pic.
crDroid is pretty much like any other off-shoot of highwaystars los14, so it has artifacts and no camera and you probably need to use custom kernel at some point. Atm i am going to stay on it until something with better battery optimization comes along.
And I am still not 100% sure that LiveDisplay is the ultimate cause of my YT lag. But I bet it has something to do with it cos it was so clear yesterday when changing to night mode --> YT lagged, turning it off --> YT no lags. But for now I'll keep using the mipad without the night mode and see what comes in my way...
Some phones are great to take camping because if you play Asphalt 8 long enough, the back warms up to the ideal temperature that can bake bread. Rate this thread to express the extent to which the OnePlus 8 Pro stays cool under extended heavy use. A higher rating indicates that even when playing strenuous games for long periods of time, the phone doesn't get uncomfortably warm.
Then, drop a comment if you have anything to add!
No complaints really here but noticed it running warmer than my Exynos Notebultra 20. By a Celsius under my regular usage patterns.
Here's my GSAM temp charts.
We've recently entered Spring here in Australia. Using the phone outdoors on the weekend in 34 degree temperature and full sun, my phone would overheat and prompt me to shut down services after about 5 minutes of casual use (web browsing and background services only). I removed the genuine cover which helped a little, but still frequently overheating. This phone is useless if it can't be used outside...
According to the Health and Safety guide accessible within the phone itself.
Cool as a cucumber
rodbacon said:
We've recently entered Spring here in Australia. Using the phone outdoors on the weekend in 34 degree temperature and full sun, my phone would overheat and prompt me to shut down services after about 5 minutes of casual use (web browsing and background services only). I removed the genuine cover which helped a little, but still frequently overheating. This phone is useless if it can't be used outside...
Click to expand...
Click to collapse
Yeah, I've got same issues. Left couple of times in UTE and every single time it switched off due to high temperature. I did not have issues with another brands. Top dollar useless phone.
When I experienced the temperature issue I was running OB2. I'm now running the stable build, and it seems a little better (though I need to do more testing). What version of the OS are you running?
rodbacon said:
When I experienced the temperature issue I was running OB2. I'm now running the stable build, and it seems a little better (though I need to do more testing). What version of the OS are you running?
Click to expand...
Click to collapse
Hi,
Thanks for replay. I am on latest Android 11 (Oxygen OS 11.0.1.1.IN11BA) and for me there is no any improvements. For me it is frustrating because I need often use it as hotspot.
Regards
dladz said:
Cool as a cucumber
Click to expand...
Click to collapse
which app is this ?
manojkumarn said:
which app is this ?
Click to expand...
Click to collapse
Ex kernel manager
Gonna have to chime in on this one. Coming from the 7 pro I was expecting better.
Have had some quirks with this phone still working on one being it likes to not wake the screen up now and then right away. Annoying but the only real gripe is that when I record a video... Jesus that overheats it.
4k @30fps screen brightness half, 120hz, qhd. Overheats around 930 to 11 on the dot.
Brightness down does nothing
60hz and fhd allows me to keep recording after it overheated (meaning it will stay under the line of what's the redline for overheating with the screen turned down even if I just bounced the flash off)
For kickers I threw it into 1080 p mode @30 and she **** flash down around 5!!!!!
Honestly the main gripe I have with this thing is the overheat issue when recording and the camera on the 7pro beats the 8 pro
Smittyzz said:
Gonna have to chime in on this one. Coming from the 7 pro I was expecting better.
Have had some quirks with this phone still working on one being it likes to not wake the screen up now and then right away. Annoying but the only real gripe is that when I record a video... Jesus that overheats it.
4k @30fps screen brightness half, 120hz, qhd. Overheats around 930 to 11 on the dot.
Brightness down does nothing
60hz and fhd allows me to keep recording after it overheated (meaning it will stay under the line of what's the redline for overheating with the screen turned down even if I just bounced the flash off)
For kickers I threw it into 1080 p mode @30 and she **** flash down around 5!!!!!
Honestly the main gripe I have with this thing is the overheat issue when recording and the camera on the 7pro beats the 8 pro
Click to expand...
Click to collapse
Reporting back....
Gcam has fixed all issues. Am mad happy with the phone now
Smittyzz said:
Reporting back....
Gcam has fixed all issues. Am mad happy with the phone now
Click to expand...
Click to collapse
Glad the OnePlus 8 Pro now beats the 7 Pro...
After my msm full reflash I can now use stock camera without overheat issues! But I'm still cycling between the 2. After the msm restore and a new kernal I'm now as cool as my 7pro and am finally happy last report back
Anyone else having problems with automatic brightness changes?
Every evening when it gets dark the brightness level goes to the lowest level, which is much to dark to read anything. Every evening I have to adjust the ''automatic'' level to halfway the level-slider, multiple times.
Do you have night mode enabled ?
I have this feature enabled from 9pm to 7am and indeed the auto brightness goes lower than normal value during this time slot .
Pouic said:
Do you have night mode enabled ?
I have this feature enabled from 9pm to 7am and indeed the auto brightness goes lower than normal value during this time slot .
Click to expand...
Click to collapse
No eye comfort modus
No Adaptive sleep modus
Only 'dark modus' enabled day and night
The same is happening to me. The brightness of the screen in darker lights is too low. Every time I move the slider to upper brightness but next time I open the screen is lower again.
marselcj said:
The same is happening to me. The brightness of the screen in darker lights is too low. Every time I move the slider to upper brightness but next time I open the screen is lower again.
Click to expand...
Click to collapse
I tried to wipe the system settings but the problem persists. I hope they can fix this in an update
BartKey said:
I tried to wipe the system settings but the problem persists. I hope they can fix this in an update
Click to expand...
Click to collapse
I might state the obvious, but the sensor is a bit high up on the device and it might be covered by your phone case, u sure it's not just a goof with an off brand cover?
The sensor is not covered. I use an original OnePlus cover.
Strange thing ... Everybody or at least majority of Oneplus Nord 2 owners had complained about automatic brightness . It's true in my case as well but now problem is solved with a 3-d party apk . Velis Auto Brightness from G.Play . Calibrating autobrightness is very accurate but the app remain active in background all the time and I didn't know how this affect battery drain . I read all OnePlus latest phones have this annoying bug and it's pitty none of latest updates solved it , worst here on XDA or OnePlus forum no one offer any solutions to calibrate automatic brightness .
Some smart guys said there is not "automatic brightness" but "adaptive brightness" so we had to learn phone AI how to adjust brightness a few days and then restart the phone . This are childish thoughts of those which are nothing to do else .
So , what do you think about this ? There are solutions to calibrate or fix this issue ?
I noticed that when the phone is on below 15% or lower and the battery saver is on ( for me it's 10%) the phone brightness goes to automatic mode and it becomes even less bright. I think it has to be a certain feature which is connected to battery saving IMO.
I'm using Velis for 3 months as well. This solves the problem. But OnePlus definitely should solve this.
Even latest update v11.3 EU, doesn't solve it. I even did a factory reset. 3 hours work to reset everything back as is was, for nothing...
Look at a possible solution (for me didn't work) :
"
stevendumondCupcake
stevendumond , Sep 25, 2021 :
stevendumond said: ↑
FYI: I did this a few minutes ago. I think that may be it. Before I did this, the screen brightness did not work at all. I could slide that slider up and down and nothing ever changed on screen brightness, auto or manual. Now it works! On auto and manual!
Hopefully this is the "fix"! But disabling a feature is NOT a fix, it's a workaround. Luckily I don't need that feature
Click to expand...
Click to collapse
So far the screen brightness has not faded into darkness. Phone is working fine now. This is a workaround that works.
Settings> Battery> Battery Optimization> Advanced Optimization (3 dots in upper right)> Sleep Standby Optimization: OFF
Click to expand...
Click to collapse
Since A.14 OTA , Adaptive Brightness is better but not entirely satisfying . It seems they solve bugs by little steps ... which is quite annoying !
muppetz said:
Since A.14 OTA , Adaptive Brightness is better but not entirely satisfying . It seems they solve bugs by little steps ... which quite annoying !
Click to expand...
Click to collapse
Not better here with a.14. Same problem as before... Indeed very annoying
BartKey said:
Not better here with a.14. Same problem as before... Indeed very annoying
Click to expand...
Click to collapse
Minimum level (especially in low light) is a little bit higher , sensitivity is more accurate and transition between levels is also a little bit faster . I'm pretty sure there are some improvements , that's a fact not a feeling .
muppetz said:
Minimum level (especially in low light) is a little bit higher , sensitivity is more accurate and transition between levels is also a little bit faster . I'm pretty sure there are some improvements , that's a fact not a feeling .
Click to expand...
Click to collapse
Let's hope it improves a lot more. My previous devices, Moto g, Moto G5 plus, never had such problem, even on any custom ROM...
BartKey said:
Let's hope it improves a lot more. My previous devices, Moto g, Moto G5 plus, never had such problem, even on any custom ROM...
Click to expand...
Click to collapse
Oh , yes I still have Motorola One Vision and automatic brightness is flawless ...