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
Related
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%.
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.
Just curious, what's your lowest vsel?
Mine are currently set as: 18/300 - 33/600 - 39/800.
Sent from my MB525
On 2.1 my 300mhz waz 14 but now im on 2.2 i av to use 16 but heres mine 300/16 600/28 800/39
Sent from my MB525 using XDA App
Running eclair 2.1 blur version 2.21 & my settings are:
300/18
700/32
1100/56
Could probably get the 300 & 700 lower (1100 is at the lowest stable I could set) but I'm happy with what they are.
Up_threshold set to 75%.
Very snappy & good battery life - only uses 4% battery when sleeping over night for 8 hours.
My threshold iz on 99% and i get 3days owt of mine
Sent from my MB525 using XDA App
I have used this for the first time tonight and I'm running the following without any issue
300 / 18
600 / 32
1100 / 56
Mine is 1000/50. I did some testings and it is stable.
sp8y said:
Running eclair 2.1 blur version 2.21 & my settings are:
300/18
700/32
1100/56
Could probably get the 300 & 700 lower (1100 is at the lowest stable I could set) but I'm happy with what they are.
Up_threshold set to 75%.
Very snappy & good battery life - only uses 4% battery when sleeping over night for 8 hours.
Click to expand...
Click to collapse
Now running the leaked UK 2.2 froyo 3.4.2-117 & I've kept my vsel the same but now have the up_threshold set to 70%.
if i set the lowest vsel, will my battery live longer?
albertocalle said:
if i set the lowest vsel, will my battery live longer?
Click to expand...
Click to collapse
Less voltage consumption = more use time without needing to charge.
Less charges = Increased lifespan of battery (ussually batteries are rated at 1000 charge cicles)
Less voltage also means less temperature, which may increase lifespan in the long term too.
In climates of 32ºC+ for stores who sell it, its very recommended to store them in refrigerators not in the coolest compartment but next to the drinks.
One battery stored at 10º vs 30º for a few months could mean a lot.
btw my battery lasts at least 12/24 hours more per charge, thanks to setvsel
My settings are
19 300 30 600 40 800
Aply at boot + Limit to vsel1 while screen is off.
In my case:
300/24
600/34
1000/50
At the above voltages, the stability test can run at least 30 minutes with interruptions, like pulling the status menu, showing the instructions etc, from time to time.
Something that's been bugging me with the HOX is the light sensor and auto brightness. I've been trying apps to customise the levels but outdoors has been causing me issues.
On a bright day, when I'm in the shade, a level of 50% brightness is about right for me and in direct sunlight I need it at 100%. However, both of these conditions have the same light sensor value of 10240 lux (ie maximum) from the light sensor, despite being a big change in ambient light.
Below are the available steps with the stock sensor and as you can see there's a massive gap between the last 2. I appreciate the levels are logarithmic but there's a very perceivable difference between those values and I would estimate that over half my use falls between them.
Is there anyway devs could unlock extra values or are we stuck with these? I'm sure my previous phones had more than these.
10
40
90
160
225
320
640
1280
2600
10240
I believe these are the available steps with a desire hd. There's more throughout but in particular an additional 5 in the upper level
0
10
117
225
272
320
480
640
960
1280
1940
2600
4200
5800
6900
8000
9120
10240
Try this app: Custom Auto Brightness
terence0320 said:
Try this app: Custom Auto Brightness
Click to expand...
Click to collapse
You can add extra steps within this app but they won't get utilised because the light sensor doesn't report any intermediate values between 2600 & 10240
Probably going to have to be a kernel source code deal.
Hunt3r.j2 said:
Probably going to have to be a kernel source code deal.
Click to expand...
Click to collapse
I hope you're right and it can be done.
The sensor is a CM3602, the same as many devices including the Desire HD so it doesn't appear to be a hardware limitation as that has much better resolution.
may be it's on rom side too and not only on kernel side. libs for sensors are compiled into roms, too. and as of my knowledge these values are given in rom libs. but i may be wrong
going to have a closer look into this... it's enerving, you're right. starting this earliest coming monday -> [email protected]
it's onkernel side; messed around a bit with it but wasn't succesful so far will search a little bit more, found this http://forum.xda-developers.com/showthread.php?t=1277700 so far, first point to start with but tegra has completely different code...
Hi guys!
I got my SXS on 24 December and i try to play games (etc. Dead Space NFS Most Wanted) but my phone gets a bit hot (not very, but its a bit uncomfortable for my hands) but the bigger problem is: it drops the CPU clocks to 805 (?) MHz and its make games unplayable. All stock on my phone and I try to play nonpirate games. The worst is, sometimes the games pause automatically.
The phone do that too when I start playing. (So thats isn't hot and still lags, and pauses...)
Any suggestions?
only pauses, lags, and heats? man you are lucky..
my xperia ion is nowhere better. after 1st time playing dead space, it doesn't get hot or get lags. it simply rage quit and not letting me play every time i start the game.. all stock no pirate as well.
btw, xperia ion will be my last android phone, yes, no more android, but still other sony devices. i so hate the way android works, even though you can really enjoy the customization and apps integration, but seriously nothing else. i have lost all the faith on android and sony mobile. i don't wanna struggle just to get something i want to work. i want something reliable, and that's definitely not android.
asdf2222 said:
Hi guys!
I got my SXS on 24 December and i try to play games (etc. Dead Space NFS Most Wanted) but my phone gets a bit hot (not very, but its a bit uncomfortable for my hands) but the bigger problem is: it drops the CPU clocks to 805 (?) MHz and its make games unplayable. All stock on my phone and I try to play nonpirate games. The worst is, sometimes the games pause automatically.
The phone do that too when I start playing. (So thats isn't hot and still lags, and pauses...)
Any suggestions?
Click to expand...
Click to collapse
Go to system/etc and find thermal-send.conf
Edit with root explorer!
you'll see these lines:
[MSM_THERM]
sampling 10000
thresholds 49 52 55 58 70
thresholds_clr 45 50 53 56 68
actions lcd lcd cpu lcd shutdown
action_info 192 128 810000 64 0
Change to:
[MSM_THERM]
sampling 10000
thresholds 49 52 65 58 70
thresholds_clr 45 50 63 56 68
actions lcd lcd cpu lcd shutdown
action_info 192 128 810000 64 0
Reboot your phone will no longer lag during heavy game! Before if u reach 53 degree u'll lose performance. Now It will not clocked down until 63 Degree.
Thank me, if I deserved it.
Send from my stupid lt26i
Also, check you're on the latest firmware
Sent from my Jellybean Xperia S
Welcome to the forum. Please post all your questions here in Q&A in future.
Thanks
AvRS
Ben36 said:
Also, check you're on the latest firmware
Sent from my Jellybean Xperia S
Click to expand...
Click to collapse
Yeah im on the latest firmware, and i tried older firmwares too.
monivan said:
Go to system/etc and find thermal-send.conf
Edit with root explorer!
you'll see these lines:
[MSM_THERM]
sampling 10000
thresholds 49 52 55 58 70
thresholds_clr 45 50 53 56 68
actions lcd lcd cpu lcd shutdown
action_info 192 128 810000 64 0
Change to:
[MSM_THERM]
sampling 10000
thresholds 49 52 65 58 70
thresholds_clr 45 50 63 56 68
actions lcd lcd cpu lcd shutdown
action_info 192 128 810000 64 0
Reboot your phone will no longer lag during heavy game! Before if u reach 53 degree u'll lose performance. Now It will not clocked down until 63 Degree.
Thank me, if I deserved it.
Send from my stupid lt26i
Click to expand...
Click to collapse
May this will help, I changed this values i will test soon!
(sry for my english)
0000alex0000 said:
only pauses, lags, and heats? man you are lucky..
my xperia ion is nowhere better. after 1st time playing dead space, it doesn't get hot or get lags. it simply rage quit and not letting me play every time i start the game.. all stock no pirate as well.
Click to expand...
Click to collapse
I didnt had those problems on stock or by now. I play a lot on my Ion and everything runs great.
monivan said:
Go to system/etc and find thermal-send.conf
Edit with root explorer!
you'll see these lines:
[MSM_THERM]
sampling 10000
thresholds 49 52 55 58 70
thresholds_clr 45 50 53 56 68
actions lcd lcd cpu lcd shutdown
action_info 192 128 810000 64 0
Change to:
[MSM_THERM]
sampling 10000
thresholds 49 52 65 58 70
thresholds_clr 45 50 63 56 68
actions lcd lcd cpu lcd shutdown
action_info 192 128 810000 64 0
Reboot your phone will no longer lag during heavy game! Before if u reach 53 degree u'll lose performance. Now It will not clocked down until 63 Degree.
Thank me, if I deserved it.
Send from my stupid lt26i
Click to expand...
Click to collapse
I dont know but i changed the values and the game is auto pause... :S sry for my english :crying:
monivan said:
Go to system/etc and find thermal-send.conf
Edit with root explorer!
you'll see these lines:
[MSM_THERM]
sampling 10000
thresholds 49 52 55 58 70
thresholds_clr 45 50 53 56 68
actions lcd lcd cpu lcd shutdown
action_info 192 128 810000 64 0
Change to:
[MSM_THERM]
sampling 10000
thresholds 49 52 65 58 70
thresholds_clr 45 50 63 56 68
actions lcd lcd cpu lcd shutdown
action_info 192 128 810000 64 0
Reboot your phone will no longer lag during heavy game! Before if u reach 53 degree u'll lose performance. Now It will not clocked down until 63 Degree.
Thank me, if I deserved it.
Send from my stupid lt26i
Click to expand...
Click to collapse
will this work on Samsung galaxy music duos ? iam facing the same problem-i mean Auto pausing of games and also force stop sometimes..if this dont work then please post some working method for the device if any..