Related
Is there a way to tweak the behaviour of the auto-brightness backlight? At the moment it correctly goes up to full brightness in sunlight, but it doesn't go as dim as I would like under artificial light. At home, after dark, under electric light, I can manually turn the screen brightness down to the minimum level, and it's still bright enough - the auto setting is much brighter than that(although clearly much dimmer than it is in sunlight, so it is doing something).
Can this be tweaked? Failing that, is there an easier way to control the brightness manually - something I can keep running all the time, and which doesn't require the stylus to change the setting?
Try GLight
http://www.ageye.de/index.php?s=glight/about
JustBored said:
Try GLight
http://www.ageye.de/index.php?s=glight/about
Click to expand...
Click to collapse
Thanks, I'll give that a try.
I find Lumos to be more stable and reliable
http://forum.xda-developers.com/showthread.php?t=450318
Ok I havn't tried either of them before but I just installed G-Light.
After a bit of config. it's ok. You need to give each backlight number a wider setting.
Otherwise it'll just flip back and forward in brightness.
So far G-Light is proving rather dissapointing. The phone's built-in "Auto" setting works well, apart from the fact that the brightness doesn't go low enough in dim light - in particular, it manages to choose a good level and then stick to it. G-Light, by contrast, keeps changing the brightness up and down all the time.
I think the notion of having absolute brightness bands may be the wrong way to go. You really want a set-up where the threshold values are in different places depending on whether the light is getting brighter or dimmer. So, as the light fades, you cross a threshold and dim the screen - but when the light goes slightly back up over that threshold, you don't brighten the screen again until it gets significantly higher than that. That way, regardless of the light level, the screen brightness will be steady unless the ambient light level is changing a lot. If you use single threshold values then whenever the ambient light happens to be very close to a threshold value you will always get the brightness going constantly up and down.
Edit: some of the things Lumos does (like averaging across multiple readings) sound hopeful, though. I'll give that a try.
Shasarak said:
So far G-Light is proving rather dissapointing. The phone's built-in "Auto" setting works well, apart from the fact that the brightness doesn't go low enough in dim light - in particular, it manages to choose a good level and then stick to it. G-Light, by contrast, keeps changing the brightness up and down all the time.
I think the notion of having absolute brightness bands may be the wrong way to go. You really want a set-up where the threshold values are in different places depending on whether the light is getting brighter or dimmer. So, as the light fades, you cross a threshold and dim the screen - but when the light goes slightly back up over that threshold, you don't brighten the screen again until it gets significantly higher than that. That way, regardless of the light level, the screen brightness will be steady unless the ambient light level is changing a lot. If you use single threshold values then whenever the ambient light happens to be very close to a threshold value you will always get the brightness going constantly up and down.
Edit: some of the things Lumos does (like averaging across multiple readings) sound hopeful, though. I'll give that a try.
Click to expand...
Click to collapse
Let me know how Lumos is.
Yes as I said earlier you need to widen those settings.
For now I have 5 set to 0-81
6 set to 82-200
8 set to 201-600
10 set to 601-1000
All the rest are disabled by setting the values to -1 to -1
HeavyComponent said:
Let me know how Lumos is.
Click to expand...
Click to collapse
Lumos is also proving dissapointing. It's partly the fault of the hardware - the sensor seems to read 0 even in surprisingly bright light, so the app has no way of telling whether you're at a light level where backlight 1 is appropriate or a light level where backlight 3 is appropriate - both read 0 on the sensor. (This is probably why the default auto option doesn't go below 3 in the first place).
As for Lumos, the author needs to realise that perception of brightness is actually based on an exponential curve. That means that all of the values between level 1 and level 5 are somewhere between 0 and 80 sensor reading. The graph interface is useless for editing custom values with that level of precision - it's trying to squeeze over 2000 values into less than 800 pixels of screen space, and the pixels are tiny! I think you can edit the values directly in the settings.txt file, but that's fiddly - there should be spinboxes, really (as with G-Light).
In any case, you don't want to be editing the values directly! What you want to be doing is taking the phone out of your pocket, looking at it, and thinking "hmm, the screen is too bright at the moment" then adjusting the brightness to whatever level is comfortable for the current ambient light level. The programme should then interpolate the curve that you want, and progressively refine it each time you decide it isn't quite right and tweak the brightness.
I haven't tried to Lumos program yet, but I've been using Glight for a few days. At first I had some issues with it but then I realized that you have to turn the auto light adjustment off in settings first. If not, they'll both be fighting against one another.
Also, you have to set your thresholds pretty carefully as has been already stated. Mine is set to go bright only in bright outside and lowest in a dark room with no light at all.
1 0 to 5
3 10 to 799
8 800 to 2500
I've got mine set low for better battery life and the screen is always readable to me no matter what anyway.
Also, if you're using a the snap on rubber protector (I got a T-Mobile one) it will interfere with the light sensor. I just got one and the lighting is all over the place now. Time to order a full body screen protector.
GLight doesn't seem to work for me. keeps crashing, and the settings don't seem to save at all.
I don't want a sliding scale that Lumos has since i don't think the light sensor is all that accurate (sometimes thinks it's too bright and sometimes thinks its too dark). would rather just have a few settings (pitch black setting, super bright setting, and in the middle) as shawndh suggested.
i have the verizon tp2 - not sure if this might be causing some of the glight probs.
I miss the option for this...
The widget only makes the brightest or darkest setting... :-(
Sent from my LT15i using XDA App
when you use the standard "Power Control" widget you can toggle min/user/max
with user being the setting that you set in the display settings.
and if you have a user setting somewhere in the middle, then it will adjust to the ambient light.
If you install widgetsoid (a massively enhanced version of the powercontrol widget mentioned above) the brightness control has an auto option, which works fine.
For ARC, you can enable and disable by executing the following command in a terminal. You can write it in a script file and make it one-button action with the help of "gscript lite".
echo 1 > /sys/devices/i2c-0/0-0040/leds/lcd-backlight/als/enable
1 to enable, 0 to disable
In addition, by adjusting cutoff frequency of low pass filter of ALS output, you can adjust the changing speed of brightness relative to ambient lighting. The command is listed below:
echo 2,4,2,0 > /sys/devices/i2c-0/0-0040/leds/lcd-backlight/als/params
2nd figure "4" is to define cuf-off frequency to 4Hz for
increasing brightness. Range 0~7, larger value for faster change
3rd figure is for decreasing brightness. This example, 2, is to define 2Hz for cut-off frequency.
cruxlin said:
For ARC, you can enable and disable by executing the following command in a terminal. You can write it in a script file and make it one-button action with the help of "gscript lite".
echo 1 > /sys/devices/i2c-0/0-0040/leds/lcd-backlight/als/enable
1 to enable, 0 to disable
In addition, by adjusting cutoff frequency of low pass filter of ALS output, you can adjust the changing speed of brightness relative to ambient lighting. The command is listed below:
echo 2,4,2,0 > /sys/devices/i2c-0/0-0040/leds/lcd-backlight/als/params
2nd figure "4" is to define cuf-off frequency to 4Hz for
increasing brightness. Range 0~7, larger value for faster change
3rd figure is for decreasing brightness. This example, 2, is to define 2Hz for cut-off frequency.
Click to expand...
Click to collapse
I think I just fell in love. Thanks a lot!
daveybaby said:
If you install widgetsoid (a massively enhanced version of the powercontrol widget mentioned above) the brightness control has an auto option, which works fine.
Click to expand...
Click to collapse
I have widgetsoid installed and the auto brightness control just sets my brightness to the minimum..
DemonicHawk said:
I have widgetsoid installed and the auto brightness control just sets my brightness to the minimum..
Click to expand...
Click to collapse
Are you sure? Works here just fine.
Try holding your thumb over the light sensor, see what happens.
Yeah, i've tried covering it and putting a flashlight to it, neither do anything when on auto. I even went into the service menu to make sure it was working properly.
I guess i'll just have to stick with a fixed brightness and let it "auto adjust" as needed. Maybe its the generic .181 build im using?
Hmm, i don´t know who is wrong but i was thinking that the arc only has an automatic brightness that can not be disabled. I have a german arc (unbranded, .181 FW) and it doesn´t matter to which level the brightness is set the automatic is always active and permanently regulates the brightness. Woul be very gald if SE would integrate an automatic brightness on/off setting with the next firmware
cruxlin said:
For ARC, you can enable and disable by executing the following command in a terminal. You can write it in a script file and make it one-button action with the help of "gscript lite".
echo 1 > /sys/devices/i2c-0/0-0040/leds/lcd-backlight/als/enable
1 to enable, 0 to disable
In addition, by adjusting cutoff frequency of low pass filter of ALS output, you can adjust the changing speed of brightness relative to ambient lighting. The command is listed below:
echo 2,4,2,0 > /sys/devices/i2c-0/0-0040/leds/lcd-backlight/als/params
2nd figure "4" is to define cuf-off frequency to 4Hz for
increasing brightness. Range 0~7, larger value for faster change
3rd figure is for decreasing brightness. This example, 2, is to define 2Hz for cut-off frequency.
Click to expand...
Click to collapse
Genius!! Many thanks
Strange! with the update to 2.3.3 it stopped auto-dimming (not sure if it was due to the update or due to me installing juice defender)
And i can not get turn it on with the Power Widget.
cruxlin said:
echo 1 > /sys/devices/i2c-0/0-0040/leds/lcd-backlight/als/enable
1 to enable, 0 to disable
Click to expand...
Click to collapse
I get "permission denied" trying to do that
but "cat" ing the vqalue gives me a 0
do I have to root?
cruxlin said:
echo 2,4,2,0 > /sys/devices/i2c-0/0-0040/leds/lcd-backlight/als/params
2nd figure "4" is to define cuf-off frequency to 4Hz for
increasing brightness. Range 0~7, larger value for faster change
3rd figure is for decreasing brightness. This example, 2, is to define 2Hz for cut-off frequency.
Click to expand...
Click to collapse
cat /sys/devices/i2c-0/0-0040/leds/lcd-backlight/als/params
gain,filter_up,filter_down,offset
2,0,0,0
any clues what gain and offset are used for?
this works brilliantly
Thank you so much
And yes you need ROOT
cruxlin said:
For ARC, you can enable and disable by executing the following command in a terminal. You can write it in a script file and make it one-button action with the help of "gscript lite".
echo 1 > /sys/devices/i2c-0/0-0040/leds/lcd-backlight/als/enable
1 to enable, 0 to disable
In addition, by adjusting cutoff frequency of low pass filter of ALS output, you can adjust the changing speed of brightness relative to ambient lighting. The command is listed below:
echo 2,4,2,0 > /sys/devices/i2c-0/0-0040/leds/lcd-backlight/als/params
2nd figure "4" is to define cuf-off frequency to 4Hz for
increasing brightness. Range 0~7, larger value for faster change
3rd figure is for decreasing brightness. This example, 2, is to define 2Hz for cut-off frequency.
Click to expand...
Click to collapse
Hi cruxlin
Thanks allot for your information on how to change this. I have found on my ARC with 2.3.3 that als/enable is allways configured to "1". Doing echo "0" > als/enable will not change this value. It is working fine for als/params where I managed to change how fast the brightness are changing.
I also discovered an odd way of manually disabling/enabling the light sensor by using the default sony ericsson brightness toggle widget. Setting this to "dim" will disable the auto brightness and you can set the brightness manual to whatever level you wish. When you toggle the widget to enable brightness it will both enable auto brightness and change brightness to the value you previosly used as minimum.
I had for testing added echo 2,6,6,0 > als/params for fast brightness change and using a flashlight. This made the brightness update the same second I moved the flashlight over the light sensor.
I actually very much like the sony ericsson way of controlling this as it enables me to define minimum brightness with auto brightness enabled and very quickly use the dim toggle to quickly change to some other preffered value.
So with that second script you can also get rid of the backlight stuttering higher and lower in some situations?
Ambroos said:
So with that second script you can also get rid of the backlight stuttering higher and lower in some situations?
Click to expand...
Click to collapse
I do not think I have experienced this backlight stuttering, how do you notice this?
I have just yesterday managed to get my auto brightness working, my SE brightness widget had been set to dim shortly after I got the phone and I had not touched it until yesterday unknowing that this also controls the auto brightness
hygge said:
I do not think I have experienced this backlight stuttering, how do you notice this?
I have just yesterday managed to get my auto brightness working, my SE brightness widget had been set to dim shortly after I got the phone and I had not touched it until yesterday unknowing that this also controls the auto brightness
Click to expand...
Click to collapse
It's just that in some low-light situations the automatic brightness flips out, and switches between two settings at an extremely fast speed, creating a flickering effect. Doesn't happen a lot, but it is pretty annoying when it happens.
Ambroos said:
It's just that in some low-light situations the automatic brightness flips out, and switches between two settings at an extremely fast speed, creating a flickering effect. Doesn't happen a lot, but it is pretty annoying when it happens.
Click to expand...
Click to collapse
I do experience that on my Neo too, try to move your phone a bit, or hold your thumb over the light sensor and release it. Works sometimes.
I ran the script in glite and it makes no difference for me any pointers thx
hygge said:
I also discovered an odd way of manually disabling/enabling the light sensor by using the default sony ericsson brightness toggle widget. Setting this to "dim" will disable the auto brightness and you can set the brightness manual to whatever level you wish. When you toggle the widget to enable brightness it will both enable auto brightness and change brightness to the value you previosly used as minimum.
I had for testing added echo 2,6,6,0 > als/params for fast brightness change and using a flashlight. This made the brightness update the same second I moved the flashlight over the light sensor.
I actually very much like the sony ericsson way of controlling this as it enables me to define minimum brightness with auto brightness enabled and very quickly use the dim toggle to quickly change to some other preffered value.
Click to expand...
Click to collapse
It works perfectly for me, thank you.
After upgrading to 2.3.4 where power control widget is missing (I dont know why), I was not able to set auto-mode.
With this solution I recovered it and, more ahead, I have now something I was looking for, the way to set the low brightness intensity, that was very high when dark night.
I cannot set the other paramethers, since I lost root while updating (I'll need to fix this), but for the moment, it works fine.
Again, thanks a lot.
daveybaby said:
If you install widgetsoid (a massively enhanced version of the powercontrol widget mentioned above) the brightness control has an auto option, which works fine.
Click to expand...
Click to collapse
Even if you uncheck auto, it will use the light sensor to set the brightness, the input you give is just the minimal brightness. Try putting the brightness on ~8% in a place with light, then hold you hand above the light sensor. Screen will still become darker.
Hi everybody, I recently updated my Eonon Androud HU to 5.1.1 using the first 5.1.1 custom ROM listed here. The DSA Prerooted ROM. Thus far it's been functional and fits my needs over the Malaysk ROM. However this ROM has some sort issue with it automatically dimming the screen to low, even though it's been set to 100%. When sliding the brightness slider to 100, the screen will still dim on its own, regardless of the adjustment still being set at 100%. I have gone through all the settings and found nothing that can help me. The display submenu only displays the option "Brightness". Which is just the standard slider to adjust the brightness. There is no option for Auto, Low, Bright, etc.
I've downloaded some apps to control the brightness to see if that would help, but something on this ROM is overriding any brightness apps from working. I even tried installing an xposedMTC module as it had an automatic dimming option, hoping to deactivate it completely but no luck. The way my car works is my headlights have an automatic DRL. When I turn my DRL's off, the headunit seems to activate it's full brightness, until I turn the automatic light control back on which turns on my DRL's, then the screen goes dim again. It's as if the headunit is going by the whole "Oh your headlights are on, it must be dark outside. Let me adjust the brightness to low for you".
Any help would be appreciated. I hope it's a simple fix. Thank you!
brian117 said:
Hi everybody, I recently updated my Eonon Androud HU to 5.1.1 using the first 5.1.1 custom ROM listed here. The DSA Prerooted ROM. Thus far it's been functional and fits my needs over the Malaysk ROM. However this ROM has some sort issue with it automatically dimming the screen to low, even though it's been set to 100%. When sliding the brightness slider to 100, the screen will still dim on its own, regardless of the adjustment still being set at 100%. I have gone through all the settings and found nothing that can help me. The display submenu only displays the option "Brightness". Which is just the standard slider to adjust the brightness. There is no option for Auto, Low, Bright, etc.
I've downloaded some apps to control the brightness to see if that would help, but something on this ROM is overriding any brightness apps from working. I even tried installing an xposedMTC module as it had an automatic dimming option, hoping to deactivate it completely but no luck. The way my car works is my headlights have an automatic DRL. When I turn my DRL's off, the headunit seems to activate it's full brightness, until I turn the automatic light control back on which turns on my DRL's, then the screen goes dim again. It's as if the headunit is going by the whole "Oh your headlights are on, it must be dark outside. Let me adjust the brightness to low for you".
Any help would be appreciated. I hope it's a simple fix. Thank you!
Click to expand...
Click to collapse
That's one of the main differences between Malaysk and DSA. DSA told me look out the window and figure it's night time. Secondly he told me to go to max at least two or even three times in a row. It will then STAY 100% bright till you reboot.
halloj said:
That's one of the main differences between Malaysk and DSA. DSA told me look out the window and figure it's night time. Secondly he told me to go to max at least two or even three times in a row. It will then STAY 100% bright till you reboot.
Click to expand...
Click to collapse
Whoa, thanks for the quick reply and useful information. Is there absolutely no way to bypass having to do that method? As that would be a chore doing it multiple times after exiting and entering my car multiple times a day. Maybe a simple build.prop edit possibly? Just naming ideas.
There is... Mtc manager has settings in it for brightness settings due to time. You can turn it off there. This didn't work for me so I went another route with changing some file. Its all detailed in the thread as to how.
miffymiffy said:
There is... Mtc manager has settings in it for brightness settings due to time. You can turn it off there. This didn't work for me so I went another route with changing some file. Its all detailed in the thread as to how.
Click to expand...
Click to collapse
You could disable brightness control entirely or just alter the brightness levels.
It's in file /system/etc/install-recovery.sh - at its end, comment out all 14 lines after comment line reading "#Brightness control (last, always)", in order to disable the algorithm.
OR, change line reading "nb=5 ### Night Brightness ###" to a different value for the night brightness (nb), eventually equal to day brightness (db, on next line).
Use a root explorer, or edit a copy of file on PC (with notepad+ if on Windows) and copy it back - with a root explorer or manually, if you can. File mode: 0755, owner & group: root:root.
If script /system/etc/install-recovery.sh gets "damaged", you must reinstall the firmware, but with NO wipe all, so fairly quickly and no loss of settings and apps.
Editing of script could also be done with @devilsoft app (with a name I can't recall).
brian117 said:
Hi everybody, I recently updated my Eonon Androud HU to 5.1.1 using the first 5.1.1 custom ROM listed here. The DSA Prerooted ROM. Thus far it's been functional and fits my needs over the Malaysk ROM. However this ROM has some sort issue with it automatically dimming the screen to low, even though it's been set to 100%. When sliding the brightness slider to 100, the screen will still dim on its own, regardless of the adjustment still being set at 100%. I have gone through all the settings and found nothing that can help me. The display submenu only displays the option "Brightness". Which is just the standard slider to adjust the brightness. There is no option for Auto, Low, Bright, etc.
I've downloaded some apps to control the brightness to see if that would help, but something on this ROM is overriding any brightness apps from working. I even tried installing an xposedMTC module as it had an automatic dimming option, hoping to deactivate it completely but no luck. The way my car works is my headlights have an automatic DRL. When I turn my DRL's off, the headunit seems to activate it's full brightness, until I turn the automatic light control back on which turns on my DRL's, then the screen goes dim again. It's as if the headunit is going by the whole "Oh your headlights are on, it must be dark outside. Let me adjust the brightness to low for you".
Any help would be appreciated. I hope it's a simple fix. Thank you!
Click to expand...
Click to collapse
Hi @brian117 !
In fact, there is a simple fix I found lately.
You need to enter factory settings first.
Go to SETTINGS -> Factory settings -> enter code: m123456
When you're there, go to last page, and tick the "Key light" option.
Now press "Apply" and "Exit". Confirm reboot.
It worked with me - now the screen has full brightness regardless of the car lights on or off (in Poland we need to have the lights on whole day, as well). Now you can use a software dimming, like MTC to auto dimm the screen according to actual day time. I did this. Works like a charm! (I set dimming after sunset to 75% brightness)
If you're as annoyed as I am by the fact that the minimal auto-brightness level is set even in fairly bright rooms and you would like to adjust it, then I have a simple tool for you. Just start it, enter your desired adjustment level (0-255) and click OK. My app will set the brightness immediately, and also every time the screen turns on (this is required because the adjustment does not seem to stick for very long).
You can download the latest version along with the source code here: My GitHub
Works great. Any effect on battery that you can speak of?
Sent from my OnePlus 5
It shouldn't have any effect on battery life. It shows 0% used on my phone in the last 48h.
Hey... Thanks for your app. It's definitely working. I'm not 100% sure what it does though... Does it set the lowest possible autobrightness level, and then the automatic adjustment takes over from there? Can you explain a bit more?
saccentekennedy said:
Hey... Thanks for your app. It's definitely working. I'm not 100% sure what it does though... Does it set the lowest possible autobrightness level, and then the automatic adjustment takes over from there? Can you explain a bit more?
Click to expand...
Click to collapse
Let's say the auto brightness sets a brightness level "x" normally. If you adjust the auto brightness in my tool then the brightness will be set to "x + whatever you put in my tool" instead.
mooop12 said:
Let's say the auto brightness sets a brightness level "x" normally. If you adjust the auto brightness in my tool then the brightness will be set to "x + whatever you put in my tool" instead.
Click to expand...
Click to collapse
Thanks for that explanation.
So, then something funny is going on. At the moment, it's full sunshine out and using your app is making the screen dimmer. I've set the app to '50', and when I turn the phone on, the screen dims and I have to toggle autobrightness off and on again to reset it to full brightness. I'm not sure whether I'm using it wrong, or it's a bug?
---------- Post added at 09:56 AM ---------- Previous post was at 09:51 AM ----------
saccentekennedy said:
Thanks for that explanation.
So, then something funny is going on. At the moment, it's full sunshine out and using your app is making the screen dimmer. I've set the app to '50', and when I turn the phone on, the screen dims and I have to toggle autobrightness off and on again to reset it to full brightness. I'm not sure whether I'm using it wrong, or it's a bug?
Click to expand...
Click to collapse
Edit... Further observations:
When conditions would mean full brightness on autobrightness, it feels like the screen is SUBTRACTING the amount I put into the app. Does that make sense?
Not sure what's causing it for you, it's working fine on my phone. Sometimes it gets bugged and it goes from full brightness to zero again, but that's because the setting does not seem to stick for very long, I just have to lock and unlock the phone and it works fine. It shouldn't be subtracting from the brightness though.
mooop12 said:
Not sure what's causing it for you, it's working fine on my phone. Sometimes it gets bugged and it goes from full brightness to zero again, but that's because the setting does not seem to stick for very long, I just have to lock and unlock the phone and it works fine. It shouldn't be subtracting from the brightness though.
Click to expand...
Click to collapse
I'll try a very high number to make it really obvious if it's working or not
I've posted an update. I noticed the brightness adjustment resets very often so I've added a functionality to set the adjustment every 2 seconds while the screen is on. It shouldn't have any effect on the battery as it barely uses any CPU (less than 20 second in the course of a whole day).
mooop12 said:
I've posted an update. I noticed the brightness adjustment resets very often so I've added a functionality to set the adjustment every 2 seconds while the screen is on. It shouldn't have any effect on the battery as it barely uses any CPU (less than 20 second in the course of a whole day).
Click to expand...
Click to collapse
Or user can disable optimization battery for your app ?
Envoyé de mon ONEPLUS A5000 en utilisant Tapatalk
Works fine except when you want the maximum brightness, for me it won't let me use max brightness unless there's much light and it activates itself
In the changelog for 4.5.11 is says they improved autobrightness. Has any of you noticed this? Do you still need this mod, or do you just need the update...?
In the 4.5.11 seems works a lot better than before, but still far froms iOS perfection, anyway give it a try!
Tried it on OOS5. It stops working afther I change the brightness manually. Brighness goes to 0 afther unlock.
Good Solution
Thanks for providing this minimal app, I just discovered it & it works great. Better than Lux Lite shall I say (my previous solution)
Does this work with Android in general or is it just for the OnePlus?
I have the same problem with a user in a previous post.
It does work as the minimum brightness according to the value I set, but also limits the maximum brightness.
For some reason I never get it.
Only if I set 255 in the app.
hey guys,
im having trouble with adaptive brightness since some time and i am pretty sure sth has changed there.
my screen is just to dark for the most time.
some time ago i could just increase the brightness value and the adaptive brightness would work with that (higher) value, like an anchor value.
now, by doing that, i just change the overall brightness and it will jump back after some time.
is this the same for you guys? it gets obviously when being in a dark room and ramping up the brightness (with adaptive brightness enabled) to 100 percent. now when i disable adaptive brightness, exactly nothing changes in terms of brightness, however former times, there would be still an increase in brightness since 100 percent with adaptive brightness does not equal 100 percent on manual brightness (at least in a dark place). now it does.
is this the same for you? was this an update or sth?
latest stock pie, with caesium kernel.
Something in kernel settings?
siggey said:
Something in kernel settings?
Click to expand...
Click to collapse
nothing set in settings.
also just tried another one, kikasura or how it is callled. same thing.
just that we are on the same page here: you still can increase the anchor value in brightness settings. or will it, too, just increase your overall brightness for a short time and as soon as lights change or you lock the screen it will be back to previous values?
I stop using auto brightness because some times he is crazy.
I prefer manual mod, like this I have the hand on it and i consum lot less battery (It's my feeling)
Adaptive Brightness is still working fine for me. The way I like to "calibrate" it is when in pitch dark, I set it all the way down to 0. From there it'll always go maximum when in sunlight and indoors it's somewhere in between and does fine. If that's not enough, try resetting adaptive brightness:
https://www.androidpolice.com/2019/...thout-clearing-all-battery-data-apk-download/
Sent from my Pixel 2 XL using Tapatalk
It is happening the same to me on very low light scenarios, auto brightness will go to the lower value, setting the screen without almost no bright, besides I put it manually higher. Maybe this happened after a update I dont know.
FedericoUY said:
It is happening the same to me on very low light scenarios, auto brightness will go to the lower value, setting the screen without almost no bright, besides I put it manually higher. Maybe this happened after a update I dont know.
Click to expand...
Click to collapse
https://www.theverge.com/2019/4/26/18516417/how-to-adjust-android-pie-adaptive-brightness-feature
Sent from my Pixel 2 XL using Tapatalk