Hi, I want to reduce the light brightness of my TX lower than that of manual. My rom is rooted LT29i 9.2.A.1.205 4.3.
I tweaked framework-res.apk
framework-res \res\values\integers.xml
<integername="config_screenBrightnessSettingMinimum">1</integer>
<integername="config_screenBrightnessSettingMaximum">245</integer>
<integername="config_screenBrightnessSettingDefault">60</integer>
<integername="config_screenBrightnessDim">1</integer>
But It doesn't seem to work. What can I do? If I need to tweak another system APPs?
The last line is what dims your screen before it turns off automatically. I suggest leaving this one the way it was.
Also, most likely these lines only work for manual brightness, not the automatic one.
Sent from my Xperia V using Tapatalk.
WhiteNeo said:
The last line is what dims your screen before it turns off automatically. I suggest leaving this one the way it was.
Also, most likely these lines only work for manual brightness, not the automatic one.
Sent from my Xperia V using Tapatalk.
Click to expand...
Click to collapse
Thanks for your answer:good: I just want to know how to reduce the minimum of manual brightness. I tweaked those values, but it didn't seem to work. I didn't change the values of auto brightness, however, The minimun of manual brightness is always brighter than that of auto brightess.
I think the drivers of display brightness are in the kernel
So your changes had no effect
Hi
The "Adapt to lighting conditions" is checked, but it doesn't really adapt. I have to manually change the slider to adjust brightness.
Looks like a bug. Not sure if there are any other settings to make.
Is this a known issue? Any workarounds?
Thanks.
Farhad.
The slider sets the maximum brightness of the screen, not the minimum. Hence, in order for the auto adjust to work, set it to the max and tick the check-box.
sxtester said:
The slider sets the maximum brightness of the screen, not the minimum. Hence, in order for the auto adjust to work, set it to the max and tick the check-box.
Click to expand...
Click to collapse
Source?
sxtester said:
The slider sets the maximum brightness of the screen, not the minimum. Hence, in order for the auto adjust to work, set it to the max and tick the check-box.
Click to expand...
Click to collapse
seems to work more like a brightness scale kind of thing. not only sets max, but minimum as well.
it'll always adjust when the box is ticked, but the slider determines how bright or dark biased it is.
It's a sliding window of brightness ranges, which should be good news to anyone who's felt that autobrightness on other phones swings too far in either direction. Now you can customize to your own taste.
Personally the sweet spot for me with good compromise between use in low light indoors, daylight and office lights is about 25% - the slider button just above the second "g" in "lighting conditions"
Remember though that changing White Balance settings will darken the display, and you'll need to boost brightness to get decent contrast again.
Use Lux Lite from the playstore. It lets you individually "link" a specific brightness level to a specific lighting condition, which the app then remembers and automates.
phositadc said:
Source?
Click to expand...
Click to collapse
What do you mean "Source"?
That's how it work[s|ed] on my Xperia U, Xperia M, Xperia SP and now on Xperia Z3C.
Not proof enough?
It works, but doesn't work well. When I wake up at night the brightness level goes lower but not nearly low enough. I have to manually reduce the brightness to the lowest level. When the day starts, I have to manually increase the brightness. Not ideal, not a deal breaker either. Hopefully Sony addresses in the next update.
garment69 said:
It works, but doesn't work well. When I wake up at night the brightness level goes lower but not nearly low enough. I have to manually reduce the brightness to the lowest level. When the day starts, I have to manually increase the brightness. Not ideal, not a deal breaker either. Hopefully Sony addresses in the next update.
Click to expand...
Click to collapse
Totally agree, Im using lux to improve the brightess auto adjust....
I use my Z3C at night quite often and find that the backlighting is too bright even turned all the way down. The adaptive lighting option does not bring it bright enough durring daylight use if left un the low setting. Is there any way to adjust the backlight other than a 3rd party app?
Sent from my D5803 using XDA Free mobile app
Do you mean other than the brightness slider?
Install lux and set it to adjust brightness automatically depending on ambiant light.
Set it to -10 or 5% with 1 lux and 100% with 100. Etc. It take time to adjust it but will save your eyes and battery.
Donation isn't necessary but bring some good options.
Works like default adaptive brightness but with more steps (if you desire), darker or lighter...
Mazzeru said:
Install lux and set it to adjust brightness automatically depending on ambiant light.
Set it to -10 or 5% with 1 lux and 100% with 100. Etc. It take time to adjust it but will save your eyes and battery.
Donation isn't necessary but bring some good options.
Works like default adaptive brightness but with more steps (if you desire), darker or lighter...
Click to expand...
Click to collapse
Thanks man, will look into that! using Twilight now, it is waaaay to complicated for what i want.
Sent from my D5803 using XDA Free mobile app
After a few days with Lux, it is much better. It allows the screen to dim and brighten way past stock settings. I really like the night filter mode. When i am outside and check my phone i am no longer getting blasted by a spotlight bright screen!
This app is a life saver for anyone who suffers from "invisible" screen flickering caused by PWM backlight control. Most AMOLED displays control lower than 100% display brightness by PWM. This method is extremely easy to implement, but can cause eye strain and headaches for sensitive people. DC dimming is rare as it is hard to implement without sacrificing color accuracy. This is where OLED Saver comes in handy.
How to use:
- turn off system adaptive brightness
- install the app, allow permissions it requests and enable the service
- set minimum screen brightness to 255 if you want to have the safest value (guaranteed to have zero flickering). After further testing, values as low as 96 seems to be still safe - but test it with your phone to be sure.
- minimise the ongoing notification to hide it from lockscreen
- turn on automatic brightness change from the notification ("A")
- remove OLED Saver from battery optimizations
In some rare cases you will need to suspend the service from notification (while taking screenshots for example, app installer might need it disabled too).
If you have Tasker and root access, you can toggle the service to force 100% brightness automatically. I'm using 100% while viewing videos/pictures and taking photos.
Start service
Code:
am startservice org.js.oledsaver/.MainService
Stop service (this will remove also notification)
Code:
am stopservice org.js.oledsaver/.MainService
So far I haven't found any negative point while using this app, just wish it was included in the AOSP code so we could still use adaptive brightness. Anyway, give it a try and share your experience.
I used to have some trouble watching text on this display under certain light conditions.
I don't know if it is just a placebo effect, but since I've installed this app, I don't feel any discomfort anymore.
I also can't see any difference in picture quality.
pecholino said:
I used to have some trouble watching text on this display under certain light conditions.
I don't know if it is just a placebo effect, but since I've installed this app, I don't feel any discomfort anymore.
I also can't see any difference in picture quality.
Click to expand...
Click to collapse
You can easily check if it's working with another phone's camera. People have different sensitivity to PWM flickering, from none to watering eyes. You are probably somewhere in between. Without the app, I had a slight feeling like something was pulling my eyes. As soon as I enabled the app, this sensation has been gone. My wife doesn't see/feel any difference, but I left it enabled for her anyway, just to be on the safe side.
Thanks a lot for introducing this app. It works.
However I encountered a problem. With this OLED Saver activated and using GCAM to take photos, it boosts the brightness to maximum. Then I went elsewhere like home screen or other app, the auto brightness seemed not working and kept the max. brightness.
Then I tried locking the screen and unlocking, the brightness went up or down randomly, or it worked in some particular patterns I don't know. Anyway, it can't keep the brightness I set previously.
Does anyone has any idea to remedy this? Thanks a lot.
CLS_phone said:
Thanks a lot for introducing this app. It works.
However I encountered a problem. With this OLED Saver activated and using GCAM to take photos, it boosts the brightness to maximum. Then I went elsewhere like home screen or other app, the auto brightness seemed not working and kept the max. brightness.
Then I tried locking the screen and unlocking, the brightness went up or down randomly, or it worked in some particular patterns I don't know. Anyway, it can't keep the brightness I set previously.
Does anyone has any idea to remedy this? Thanks a lot.
Click to expand...
Click to collapse
Which GCAM app do you use? I'll try it. In stock camera it doesn't behave this way.
Btw. I tried to contact the developer if he could add global intents so we could control OLED Saver with Tasker and without root, this should help in preventing this kind of behavior. No response so far though. If you are rooted you could use method mentioned in the first post.
Also I'm in touch with Velis Auto Brightness developer - this app offers much more features (customizable automatic brightness levels, apps exclusion and more) and has similar feature for OLED displays, but sadly it doesn't work on status/nav bar as of now. If he manages to use the same method as OLED Saver, we could switch to VAB app.
The GCAM version is 7.0.009.259843690.
Phone model is M1906F9SH (64G global version) with OE ROM.
Thank you.
CLS_phone said:
The GCAM version is 7.0.009.259843690.
Phone model is M1906F9SH (64G global version) with OE ROM.
Thank you.
Click to expand...
Click to collapse
Could you send me the link to the particular GCAM apk pls? Different authors might give slightly different results.
I'm not allowed to post link here, yet.
Please search this file name: PMGC_7.0.009_FinalBuild_V14.apk
It's what I've saved and installed.
CLS_phone said:
I'm not allowed to post link here, yet.
Please search this file name: PMGC_7.0.009_FinalBuild_V14.apk
It's what I've saved and installed.
Click to expand...
Click to collapse
Hm, I can't replicate this. I've installed GCAM, enabled max brightness for pictures (but it does nothing, as system brightness is at max already and real dimming is done with OLED Saver, which is not being controlled by GCAM). Moving to/from GCAM doesn't change anything. If I manually suspend OLED Saver from notification, GCAM shows max brightness correctly. On resume it returns to the expected behavior and dimmer display.
Yeah, sometimes I got what you described. Sometimes it rushes to very very bright, but sometimes it can be very dim...
I'll try reset it again and see how it goes. Thanks for your time.
CLS_phone said:
Yeah, sometimes I got what you described. Sometimes it rushes to very very bright, but sometimes it can be very dim...
I'll try reset it again and see how it goes. Thanks for your time.
Click to expand...
Click to collapse
I think that I saw OLED Saver "crash" once while using the phone - brightness suddenly went to max and was controlled by system. Since I removed this app from battery optimizations, it seems to be stable. Though this does not explain rapid bright/dim changes.
This looks very useful but what is it doing exactly? Is it running the screen at max brightness at all time and using some kind of overlay to dim the screen? Isn't that bad for battery life?
Sent from my G6 using Tapatalk
barth2 said:
This looks very useful but what is it doing exactly? Is it running the screen at max brightness at all time and using some kind of overlay to dim the screen? Isn't that bad for battery life?
Sent from my G6 using Tapatalk
Click to expand...
Click to collapse
Yes, as you said, running HW brightness at max and putting a translucent overlay over the screen. It's basically SW implementation of DC dimming. It has a small artifacts with very low brightness, especially on grey colors, but otherwise no issues. Impact on battery should be negligible (OLED displays work different than LCD). Here is a nice article with links to more information at the end https://blog.elcomsoft.com/2019/11/...e-11-pro-and-pro-max-google-pixel-4-and-4-xl/
_mysiak_ said:
Yes, as you said, running HW brightness at max and putting a translucent overlay over the screen. It's basically SW implementation of DC dimming. It has a small artifacts with very low brightness, especially on grey colors, but otherwise no issues. Impact on battery should be negligible (OLED displays work different than LCD). Here is a nice article with links to more information at the end https://blog.elcomsoft.com/2019/11/...e-11-pro-and-pro-max-google-pixel-4-and-4-xl/
Click to expand...
Click to collapse
Has anyone used a high speed cam to determine at which brightness level the a3 flickers, or is it all level below 100%
Sent from my G6 using Tapatalk
barth2 said:
Has anyone used a high speed cam to determine at which brightness level the a3 flickers, or is it all level below 100%
Sent from my G6 using Tapatalk
Click to expand...
Click to collapse
I̶ ̶u̶s̶e̶d̶ ̶o̶n̶l̶y̶ ̶c̶a̶m̶e̶r̶a̶ ̶o̶f̶ ̶a̶n̶o̶t̶h̶e̶r̶ ̶p̶h̶o̶n̶e̶ ̶a̶n̶d̶ ̶i̶t̶ ̶s̶e̶e̶m̶s̶ ̶t̶h̶a̶t̶ ̶f̶l̶i̶c̶k̶e̶r̶ ̶s̶t̶o̶p̶s̶ ̶t̶o̶ ̶b̶e̶ ̶v̶i̶s̶i̶b̶l̶e̶ ̶a̶t̶ ̶a̶b̶o̶u̶t̶ ̶l̶e̶v̶e̶l̶ ̶2̶2̶0̶ ̶f̶r̶o̶m̶ ̶2̶5̶5̶,̶ ̶b̶u̶t̶ ̶a̶s̶ ̶f̶a̶r̶ ̶a̶s̶ ̶I̶ ̶k̶n̶o̶w̶,̶ ̶p̶r̶e̶t̶t̶y̶ ̶m̶u̶c̶h̶ ̶a̶l̶l̶ ̶S̶a̶m̶s̶u̶n̶g̶ ̶A̶M̶O̶L̶E̶D̶ ̶d̶i̶s̶p̶l̶a̶y̶s̶ ̶u̶s̶e̶ ̶P̶W̶M̶ ̶a̶t̶ ̶a̶n̶y̶ ̶l̶e̶v̶e̶l̶ ̶b̶e̶l̶o̶w̶ ̶1̶0̶0̶%̶,̶ ̶s̶o̶ ̶i̶t̶'̶s̶ ̶s̶a̶f̶e̶ ̶t̶o̶ ̶a̶s̶s̶u̶m̶e̶ ̶t̶h̶a̶t̶ ̶M̶i̶ ̶A̶3̶ ̶i̶s̶ ̶n̶o̶ ̶d̶i̶f̶f̶e̶r̶e̶n̶t̶.̶
Edit: actually PWM seems to kick in at 80% brightness and below.
Hi _mysiak_,
I changed to some other version of GCAM (without the max brightness view finder) and then this OLED Saver App is working fine afterwards. Thank you.
Then I found, when in very dim setting, occasionally, the white color (now it's actually gray) seems not stable. It could be fluctuating from neutral gray to warmer. Not intrusive, though. Do you see that?
CLS_phone said:
Hi _mysiak_,
I changed to some other version of GCAM (without the max brightness view finder) and then this OLED Saver App is working fine afterwards. Thank you.
Then I found, when in very dim setting, occasionally, the white color (now it's actually gray) seems not stable. It could be fluctuating from neutral gray to warmer. Not intrusive, though. Do you see that?
Click to expand...
Click to collapse
Yes, I noticed that "slow flickering/artifacts" as well. I believe it's the side effect of DC dimming method and probably one of the reasons why it's not so widely used. From what I read, Samsung AMOLED panels are designed to be used with PWM dimming, so we probably can't avoid it with very low brightness. If it's too disturbing, I just move the OLED Saver brightness slider a bit higher (it stops completely at roughly 40% brightness). Using pitch black themes in apps helps too. Not a perfect solution but definitely better than PWM
Btw. it's the same for any app using translucent overlays, I tried a couple of them and at similar brightness, all behave the same.
barth2 said:
Has anyone used a high speed cam to determine at which brightness level the a3 flickers, or is it all level below 100%
Sent from my G6 using Tapatalk
Click to expand...
Click to collapse
It seems to be at 80% and below. 81-82% and above should be safe.
CLS_phone said:
Hi _mysiak_,
I changed to some other version of GCAM (without the max brightness view finder) and then this OLED Saver App is working fine afterwards. Thank you.
Then I found, when in very dim setting, occasionally, the white color (now it's actually gray) seems not stable. It could be fluctuating from neutral gray to warmer. Not intrusive, though. Do you see that?
Click to expand...
Click to collapse
Try to change the "basic physical brightness" to value 96, artifacts don't disappear completely, but I don't notice them so often.
Level 96 in OLED Saver corresponds to HW brightness level 82%, which seems to be still free of PWM.
Thanks for the tip.
It's really works. Thanks for the tip ???