Related
Is there a way to lower the brightness beyond the default minimal setting? I've noticed that even on the lowest setting, I can still use the thing like a flashlight.
Sent from my Nexus One using XDA App
Too bright? Haven't heard that one. Mainly complaints about not bright enough in the sunlight and such.
I'm no programmer or anything, but as far as I know the android system has a brightness value of 0-100%, and the user (or apps) can change the value to anywhere in between. There might be a hack to undervolt the screen, but as far as I know one doesn't exist.
I'm guessing he has an AMOLED... in which case, I understand. The screen is bloody bright, even on the lowest setting.
My only idea would be to install one of the CM roms that lets you use the surface flinger mod to change your display to a monochrome red.
download 'screen filter' or 'total screen control' from the market. they allow you to apply a dark layer dim your phones screen to however much you want. hope this helps
Only time I really notice mine is too bright is reading if I use white on black, so I use a grey on black.. Fixed.
Although yeah, if i poke into the market first thing in the morning or such, it's pretty bright.
Problem with the screen overlays with surface flinger and such is you have to manually enable/disable them. It would be nice if the screen would go lower in some cases.
050820121030:
I have use the search button to see how i can lower screen brightness on galaxy note.
i found everywhere mentioning screen filter, it is not i don't like screen filter, but when i take screenshot it will be tinted gray.
so i decide to go to a more elegant way like what atrix 4g user did.
http://forum.xda-developers.com/showthread.php?t=1245332
i tried with my note, i cant find sys/bus/i2c/drivers/lm3532, i decided to check folder with the nearest name, but i can't find it.
so i decided to download linux, mind you i have no idea how to use linux.
i downloaded samsung ics opensource update 4, inside i can't find leds-lm3532.c,leds-lm3532.h,board-mot-lights.c.
so futhur dig found leds-lm3530c, the file structure is different with leds-lm3532.c, but i think it works the same.
any good suggestion from experts?
edit1 050820121203:
I decided to check what AdjBrightness do.
it is modifying the following files
/sys/class/leds/lcd-backlight/brightness
/sys/class/leds/amber/blink
/sys/class/leds/amber/brightness
/sys/class/leds/green/blink
/sys/class/leds/green/brightness
all return errors in note.
further investigation leads to Rootdim:
/sys/class/leds/leds-sec/trigger
/sys/class/leds/leds-sec/brightness
/sys/class/leds/leds-sec/mmc1::/trigger
/sys/class/leds/leds-sec/mmc1::/brightness
/sys/class/leds/leds-sec/mmc2::/trigger
/sys/class/leds/leds-sec/mmc2::/brightness
here all the triggers return error.
next thing i check /sys/class/
i see backlight/panel in it.
i also see lcd, leds and lightsensor.
have no idea, keep digging.
100820120935:
Found s6*aa*.c files inside driver folder.
There will be some info about 5.3inch screen.
Deeper search found that it only suplort 24 stages of brightness
From 0,1 to 30 is 0
Conclusion minimum brightness for galaxy note is 1(more than 30)
Keep digging.
100820121808:
s3cfb_s6e39a0.c contain brightness level from 1 to 24.
100820121815:
AMS529HA01 is samsung 5.3 inch galaxy note panel
s3cfb_s6e8aa0 -- the one we are using.
the following files also related to the above file.
s3cfb_s6e39a0
s3cfb_s6e63m0
s6d6aa1
s6dr171
s6e8aa1
smart_dimming
midas-lcd
setup-fb-s5p
the whole thing means samsung have tried other lcd before hd super amoled 5.3 inch?
keep digging for the brightness
150820121820:
End of research, the brightness for amoled devices only have 24 levels.
lower than that you will need to adjust contrast for better battery consumption.
if you use filter it wont decrease battery consumption, and it will affect your screenshot images clarity.
1609120512:
https://sites.google.com/site/androidnothize/no-dock/input-device-and-backlight
this shows you minimum brightness level is 30
http://forum.xda-developers.com/showthread.php?t=1709686
search for min_bl
http://forum.xda-developers.com/showthread.php?t=1154278&page=617
curve?
http://forum.xda-developers.com/showthread.php?t=1576355&page=222
N.E.A.K
So, what's the verdict? Are we stuck with "too bright in the dark" screens on our Note's?
d210 said:
So, what's the verdict? Are we stuck with "too bright in the dark" screens on our Note's?
Click to expand...
Click to collapse
For that purpose a screen filter works just fine for me.
Frankly it's not doing it for me, it looks like I'm looking through a grey plastic bag.
Andrew0811 said:
150820121820:
End of research, the brightness for amoled devices only have 24 levels.
lower than that you will need to adjust contrast for better battery consumption.
if you use filter it wont decrease battery consumption, and it will affect your screenshot images clarity.
Click to expand...
Click to collapse
So what is conclusion bro?
We can't use brightness below the SYSTEM-MINIMUM?
I also want more battery by reducing brightness to below 10.
AND yes you did well.
Good research.
anyone know of a way to get the HTCONE/sprint non-rooted phone to go lower in display brightness?
if i use it as an alarm clock on my nightstand it lights up the entire room on lowest brightness.
thanks!
Oo.et.oO said:
anyone know of a way to get the HTCONE/sprint non-rooted phone to go lower in display brightness?
if i use it as an alarm clock on my nightstand it lights up the entire room on lowest brightness.
thanks!
Click to expand...
Click to collapse
Look for an app called "Lux Auto Brightness" on the Play Store. There is a lite version that you can try out. It's allowed me to go in the negative brightness and it works pretty well.
N0wy0ud1e said:
Look for an app called "Lux Auto Brightness" on the Play Store. There is a lite version that you can try out. It's allowed me to go in the negative brightness and it works pretty well.
Click to expand...
Click to collapse
thanks. don't suppose this will work with locale...
maybe i'll have to write my own pluggin
I haven't used Lux but I really like Screen Filter for the same job: it has a huge range of dimming up to total blackness and can turn off the capacitative button backlight (requires turning the screen off and back on) which is a big deal when viewing a dimmed screen in a dark room. And the full version is free and ad-free as well.
thanks again for your replies. looks like Lux works with locale.
but... it's not quite working for me yet (setting to negative values of brighness at certain times, etc doesn't seem to work)
i'll keep trying. thankfully there is a trial version
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....
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 ???