Develop Bugs

Decrease Screen Brightness -> save battery

Hi,
I found this:
chart
Short explanation for non german reader:
max brightness
iphone 4: 486 cd/m²
SGS: 311 cd/m²
Nexus 1: 217 cd/m²
min brightness
iphone 4: 3 cd/m²
Nexus 1: 24 cd/m²
SGS: 84 cd/m²
As you can see, the screen brightness is still very very high, even if you set it to the lowest value.
So i took a look into the settings.db and saw, that the value for screen_brightness was 30, not 0. (I had set the brightness to the lowest possible before).
Maybe the Samsung preferences don't let you set the lowest available brightness?
I set the value to 0, but I'm not sure the brightness changed. =/
Someone else wanna try this and measure if the brightness really decreases?
Could save some battery...

Nice one, because of the technology we generally use less power than iPhone 4 for display HOWEVER if you display a lot of whites the AMOLED screen has the *POTENTIAL* (note: potential) to use 30% more power than the iPhone 4's H-IPS Backlit LCD.
So, another power saver tip is to use dark backgrounds as white/light ones use a lot more display power. This is a side effect of the AMOLED technology.

This is probably the biggest quibble I've with this phone right now, so I was glad to find this post from supercurio's (creater of Voodoo) twitter: "Wow, minimum brightness on #GalaxyS can be tweaked to extremely low levels !"
I hope he'll share these findings with us soon.

Its pissing me off sooo much. Like at night even at min brightness its too bright, browsing market blinds me. Can't wait for supercurio's thing, he said he got the profiles figured out.
For now all i know is 18 is the lowest u can go, anything below just completely turns the backlight off.

You guys tried dimmer from market? Goes to 10.
Sent from my GT-I9000 using Tapatalk

I simply pay more attention to my brightness now and control it myself. It adds to the to do list BUT I have gained about 30% battery life per day by doing it.
I find unless I'm in the sun there is no need to go beyond 38%.

Battery temperature

Hello.
The battery reading is constant 36.8°C, im used to that. Anyway, yesterday i was observing the terminal while charging the battery to see whats going on with adjusting mAh and units, and noticed that aux0 value from ds2746 is getting lower as the battery gets warmer.
so i stuffed the digital thermometer probe under the battery and made a few notes while heating ans cooling the phone:
aux0....temp
268.....27,8
343.....20,2
365.....18,3
390.....15,5
then i played with the numbers a bit and got this:
546 - aux0 *0,1 = temp (close value)
it was a crappy cheap thermometer so the values could be wrong. should repeat the measurment with more acurate thermometer and make more than 4 notes....
Could the kernel be moded so the temperature reading would be from the upper formula?
Edit:
it's 596 - aux0 * 0,1, that should show the same as in WM

Thanks for the research! I've been meaning to do this for quite a while, but haven't. Out of curiosity, I have two questions:
a) What battery do you have?
b) What is aux1 reading for you?

aux1 jumps arround from 61 to 67 right after boot. After that its quite stable. 64 when charging, 62 when not charging.
Batteries are one 1350mAh and one dissassembled, using the controller with random battey packs, currently 750mAh

I'll update the kernel to use your data:
Temp C = (596 - aux0)/10.
I'll make the 596 a new kernel parameter: temp_calibration = 596.
If you come up with a better equation, please let me know.
The kernel will do integer math, not floating point, and it reports tenths of degrees, so with your equation it's simply C*10 = 596 - aux0, which is nice.
I wonder if perhaps the value HTC intended was 600?

It's a small difference, 596 just came from measuring, an the thermometer isn't pin point acurate. 600 should make less than 0.5C difference.

Okay, I just pushed the kernel change.
New kernel parameter, temp_calibration = 600.
Temp (C) * 10 = temp_calibration - aux0.
Coming soon to a kernel near you.
Thank you again V3rt!g(o) for the data.

[Battery saver] custom auto brightness

OK, so I'm testing out custom auto brightness settings to share with everyone to help improve battery life, its definitely a wip and I need testers to help find the perfect balance of darkness vs being able to see the screen clearly
Auto brightness settings can be found in "settings>display>custom backlight settings>edit other levels" in many custom roms just make sure screen dim level is set to 1 and use custom is checked

OK, so far I have the following settings which seem OK though might be a little dark, please test and report back
Only change values in the "screen" column
5
7
10
13
17
20
24
25
30
40
50
60
65
70
85
95
115
135
165
255
(Last value is just to ensure max brightness in very strong light)

Good to see someone already started this thread. I have some settings I collected from xda and android forums that have been working well so far for my needs...
Window Length: 5 seconds
Reset Threshold: 400Lux
Sample Interval: 2sec
Screen Dim Level: 5
Allow Light Decrease : Yes
Lower Upper Screen
0 199 10
200 399 20
400 599 25
600 799 30
800 999 40
1000 1249 50
1250 1499 60
1500 1999 70
2000 2999 80
3000 3999 90
4000 5999 100
6000 9999 125
10000 ∞ 255
If anyone can tweak these and get better results by all means do share!

retareq said:
Good to see someone already started this thread. I have some settings I collected from xda and android forums that have been working well so far for my needs...
Window Length: 5 seconds
Reset Threshold: 400Lux
Sample Interval: 2sec
Screen Dim Level: 5
Allow Light Decrease : Yes
Lower Upper Screen
0 199 10
200 399 20
400 599 25
600 799 30
800 999 40
1000 1249 50
1250 1499 60
1500 1999 70
2000 2999 80
3000 3999 90
4000 5999 100
6000 9999 125
10000 ∞ 255
If anyone can tweak these and get better results by all means do share!
Click to expand...
Click to collapse
Hi, i just tried these values, and for me its way to dark. I think that the display of the galaxy looks realy bad, if the value is under 1/4 of max.

retareq said:
Good to see someone already started this thread. I have some settings I collected from xda and android forums that have been working well so far for my needs...
Window Length: 5 seconds
Reset Threshold: 400Lux
Sample Interval: 2sec
Screen Dim Level: 5
Allow Light Decrease : Yes
Lower Upper Screen
0 199 10
200 399 20
400 599 25
600 799 30
800 999 40
1000 1249 50
1250 1499 60
1500 1999 70
2000 2999 80
3000 3999 90
4000 5999 100
6000 9999 125
10000 ∞ 255
If anyone can tweak these and get better results by all means do share!
Click to expand...
Click to collapse
I think most slots should be raised by 5-10 for best visibility but I would suggest adding a slot or 2 at the beginning of it for best low light (mainly nighttime) settings

beama said:
Hi, i just tried these values, and for me its way to dark. I think that the display of the galaxy looks realy bad, if the value is under 1/4 of max.
Click to expand...
Click to collapse
Did you try my values? I think its a little easier to tweak some different light levels just to your liking, also the only thing that really doesn't look all that great are dark backgrounds on the home screen and launcher background but by raising some of the brightness levels by 5 or so at a time, its easily correctable... this is mainly to be a baseline guide since the stock values are wayyy to high in most cases
Fyi, before doing this I considered 2.5 hours on extended battery good, now I easily get 3+ even 4 hours on screen time with overclocking (1344 MHz) and interactive governor

I get 4 hours easy. I agree its a bit dark but I have no idea on what to modify because I don't really understand how its set up. To the guys who tried it already can you post your modified values that might be brighter ?

retareq said:
I get 4 hours easy. I agree its a bit dark but I have no idea on what to modify because I don't really understand how its set up. To the guys who tried it already can you post your modified values that might be brighter ?
Click to expand...
Click to collapse
Just try upping the values in the "screen" column by 5-10...even with increasing by 10 its still far lower than stock (stock setting has 50 as lowest value when even 15-25 should be plenty bright
To determine what level you are currently on look at the very top for filtered/raw values and see which level they fit between the first 2 columns (lower and upper)

Ok I tried metalspring way and this is what I have now :
Window Length: 10 seconds
Reset Threshold: 400Lux
Sample Interval: 10 seconds
Screen Dim Level: 10
Allow Light Decrease : Yes
Lower Upper Screen
0 199 20
200 399 25
400 599 35
600 799 45
800 999 55
1000 1249 65
1250 1499 75
1500 1999 85
2000 2999 95
3000 3999 105
4000 5999 115
6000 9999 125
10000 ∞ 255
Oh I also have the color calibrated from franco kernel app using the values suggested in app so I'm REALLY liking this now. No gradient banding or grain, looks sweeet.
updated: after todays field test I modified the values to allow for gradual dimming as much as possible. I will keep tweaking and posting results here.

Hi, how can I get gradual change like stock does? More values? Less? I hate the pop high/low u get with this
Sent from my Galaxy Nexus

does it happen to anyone else that changing the number of levels/steps for custom auto brightness from the stock 20 to anything less causes the screen go go MAX (255) brightness?

miguel.b said:
does it happen to anyone else that changing the number of levels/steps for custom auto brightness from the stock 20 to anything less causes the screen go go MAX (255) brightness?
Click to expand...
Click to collapse
Not to bring back this thread, but this is the exact issue that has shown up in CM10 ROMs and reported by quite a few users. If you use any number of levels other than 20, brightness is locked to 255 no matter what your thresholds or sensor is registering. Have you found any workaround or fix for this?

AuraspeeD said:
Not to bring back this thread, but this is the exact issue that has shown up in CM10 ROMs and reported by quite a few users. If you use any number of levels other than 20, brightness is locked to 255 no matter what your thresholds or sensor is registering. Have you found any workaround or fix for this?
Click to expand...
Click to collapse
I really thought I was the only one. I have NOT found a work around unfortunately. Rather, I've just stayed with the stock steps/levels all the while. the behaviour is still present, and I've not found any other resource or posts on the issue.

I have brought this up in another thread over at rootzwiki and others have chimed in. Perhaps I'll create a brand new thread to acknowledge it (as opposed to responding to relevant threads already created) since it doesn't appear to be getting traction in finding a solution.
Sent from my Galaxy Nexus using xda premium

Possible to run lower resolution, for longer battery life?

Especially with root now becoming available, I started giving this more thought:
If someone wanted to do that, would running a lower resolution be an option, to perhaps extend your battery life?
The screen is QHD, 1440x2560. To minimize scaling issues with a fixed-pixel-location screen like an LCD, you could go down to HD, 720x1280. Now the graphics hardware is dealing with 1/4 as many pixels. It won't look as good, granted, but lets say the user accepts that trade-off.
Is this even possible? If so, do you think it could help battery life?
I don't have experience with this on phones. But on a computer, you can certainly lower your display resolution, even if using an LCD. It will look fuzzy at a non-native resolution, but perhaps that's less of an issue here, with the pixels being so small by comparison. And if you were gaming on the PC, lowering the resolution would allow higher framerates, assuming you were limited by your graphics card, not your CPU. I've admittedly never thought about it from a power-use perspective, but it seems reasonable that, if keeping the framerate the same, running a lower resolution would require less power for the PC.
My Galaxy S3 was 720x1280, admittedly on a smaller 4.8" screen, but I thought it looked fine. If using a lower screen resolution could, say, add 20% to my G4's SOT, I would be interested in that.

I believe this is what changing the DPI is for. This can be done via apps, or changing the value in the build.prop I think. Pushing less pixels on to the screen will definitely increase battery life. There's a threshold though, and depending on which G4 variant you have (whether it's branded by a carrier, etc.) you may want to research on what a safe number might be. I think some AT&T G4 user reported bootloops after changing the DPI to <530 or something. It looks like the camera doesn't get affected by the DPI change too, which is a definite good sign.
I'm waiting to see how the battery life holds up right now with root mode now being enabled in Greenify. If I can't squeeze more than 5 hours SoT while at a certain brightness and using BT, I'll consider changing the DPI.

This is not going to improve battery life in the slightest. You might be running a lower resolution but all the pixels are stilled turned on. The lower tax on the GPU is negligible.

kyle1867 said:
This is not going to improve battery life in the slightest. You might be running a lower resolution but all the pixels are stilled turned on. The lower tax on the GPU is negligible.
Click to expand...
Click to collapse
Agreed. This was done on the G3 and batter life was not changed, only game performance improved as you are pushing graphics at 1080p instead of 1440p.

AhsanU said:
I believe this is what changing the DPI is for. This can be done via apps, or changing the value in the build.prop I think. Pushing less pixels on to the screen will definitely increase battery life. There's a threshold though, and depending on which G4 variant you have (whether it's branded by a carrier, etc.) you may want to research on what a safe number might be. I think some AT&T G4 user reported bootloops after changing the DPI to <530 or something. It looks like the camera doesn't get affected by the DPI change too, which is a definite good sign.
I'm waiting to see how the battery life holds up right now with root mode now being enabled in Greenify. If I can't squeeze more than 5 hours SoT while at a certain brightness and using BT, I'll consider changing the DPI.
Click to expand...
Click to collapse
I believe that that's wrong, specially if you set it to numbers lower than stock.

I found a way to change the resolution
https://forum.xda-developers.com/galaxy-s5/general/tool-change-phone-resolution-dpi-root-t3582863
Follow this thread, it's so simple and works perfectly!! on LG G4 818p

[Q] Android Pie Display Dimmer than Oreo?

I just upgraded from 8.1 to 9.0 on my XL 2 over the weekend. I am stock rooted.
Is it just me or is the overall display brightness much less on Pie than it was on Oreo? In the same daytime environment, I feel like Pie needs to be around 70% brightness whereas on Oreo, I feel like the display was set on about 35%. I rarely had Oreo brightness above 50%. Now with Pie, I feel like I can barely see the screen when it's under 50%.
On Oreo, my display was set to Saturated and of course, white theme since that's all we had.
On Pie, I used the same settings and it looks much dimmer. I adjusted display to Boosted and have toogled back and forth between light and dark themes and I don't notice any difference with how much dimmer the overall display feels.

The display can still get just as bright. They've just changed the way the values are displayed from the slider is all.

angus242 said:
I just upgraded from 8.1 to 9.0 on my XL 2 over the weekend. I am stock rooted.
Is it just me or is the overall display brightness much less on Pie than it was on Oreo? In the same daytime environment, I feel like Pie needs to be around 70% brightness whereas on Oreo, I feel like the display was set on about 35%. I rarely had Oreo brightness above 50%. Now with Pie, I feel like I can barely see the screen when it's under 50%.
On Oreo, my display was set to Saturated and of course, white theme since that's all we had.
On Pie, I used the same settings and it looks much dimmer. I adjusted display to Boosted and have toogled back and forth between light and dark themes and I don't notice any difference with how much dimmer the overall display feels.
Click to expand...
Click to collapse
Google changed the algorithm on the brightness slider. Therefore, 70% is the new 30% So, no, it's not you. Another brilliant improvement for the sake of supposed progress! ?

Badger50 said:
Google changed the algorithm on the brightness slider. Therefore, 70% is the new 30% So, no, it's not you. Another brilliant improvement for the sake of supposed progress! ?
Click to expand...
Click to collapse
Lol, not sure what they're Smoken at Google headquarters...

galaxys said:
Lol, not sure what they're Smoken at Google headquarters...
Click to expand...
Click to collapse
Probably hanging out with this guy! ???

I agree with everyone else. 100% on 9 is still as bright as 100% was on 8.1 but 50% on 9 is NOT what 50% was on 8.1, no doubt about it. On 8x I usually kept my brightness around 65%... now on 9, to get something similar I am around 70-75%... If the same energy is being used to illuminate the display at the different values, batt life should remain about the same... But WHY?
Why change what 50% was on 8 to be different on 9? Isn't HALF the available illumination HALF the available illumination regardless of the OS version? What is the effect, or end game Google was looking for with this?

The max brightness is the same. The difference is the slider is no using a logarithmic algorithm instead of the old linear algorithm.
Here is the explanation of why it was done:
The first noteworthy feature is a changed brightness slider behavior: It now changes the brightness logarithmically instead of linearly. Before this preview when it was linear, about 90% of the brightness was controlled by the lower 20% of the left of the slider. The old 50% brightness was almost identical to 100% max brightness, and the old 5% brightness was significantly brighter than 0% brightness. Now, the change in perceptual brightness is more uniform as you increase or decrease the slider.

Exactly. 50% before was definitely not 50% nits output for the screen which, with a rated max 403 by anandtech, would be only 201.5 nits. And that was before the November update that lowered the max by 50 nits.
jimv1983 said:
The max brightness is the same. The difference is the slider is no using a logarithmic algorithm instead of the old linear algorithm.
Here is the explanation of why it was done:
The first noteworthy feature is a changed brightness slider behavior: It now changes the brightness logarithmically instead of linearly. Before this preview when it was linear, about 90% of the brightness was controlled by the lower 20% of the left of the slider. The old 50% brightness was almost identical to 100% max brightness, and the old 5% brightness was significantly brighter than 0% brightness. Now, the change in perceptual brightness is more uniform as you increase or decrease the slider.
Click to expand...
Click to collapse
Sent from my Pixel 2 XL using Tapatalk

EeZeEpEe said:
Exactly. 50% before was definitely not 50% nits output for the screen which, with a rated max 403 by anandtech, would be only 201.5 nits. And that was before the November update that lowered the max by 50 nits.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Doesn't really bother me. My normal brightness is now just like 60% instead of around 20%. Not sure why some freaked out about it.

galaxys said:
Lol, not sure what they're Smoken at Google headquarters...
Click to expand...
Click to collapse
The same shìt as the retards who designed the P3XL.