Develop Bugs

Optimal battery life w Liquid Smooth [guide]

My current recommendations for optimal battery life are as follows: 3.8.0 exp 1 (Lean Kernel)(imoseyon)
this started as an IRC question & i decided i'd like to have something as a reference for those who'd like to maximize battery life with their respective setups. Feel free to post some screen shots of your battery life to show others your sucess!
battery 101 - cut the services (not in use) off !
How to configure Lean Kernel for optimal battery and secondly performance
Please download / flash your mods ROM / kernel / also flash lean tweaks (jakebites)
inside Lean Tweaks:
`enable 'File system speedup' (aka mount disc noatime)
`enable zram
`enable SD card speedup (set to base 2048)
this will all take effect once you reboot (it uses init.d scripts which require a reboot)
`Go to kernel menu > set customer vibration value > set vibration (/haptic) to 1000
install franco.kernel.apk
https://play.google....m.franco.kernel
go straight to system settings > more > *tick* NFC on [off]
next, disable logcats: liquid control > prop modder > *tick* disable logcats (also within franco.kernel.apk *tick* turn off logger)
liquid control > general > *tick* boot animation on [off] ; android bugmailer *tick* on [off] ; Check in service on [off] *tick*
best to manually toggle 3G / SYNC / LTE / GPS / bluetooth (obviously) as they are not in use - these are some of the biggest battery thieves unless you wantto use powersaver;
Power saver optimal settings:
~powermode: power saver / default
~by request (thanks terryrook) here are some preferred powersaver settings (top to bottom)
*tick* enable powersaver [on] off
Screen off action: *tick* [data off]
data action delay: [10 mins] (should be tailored to your preference (this is a great baseline)
Sync action:[ Autosync Off (delayed)]
Time Interval: [12 hrs] (i prefer this / + syncing each time i want my mail etc)
Screen-off Wifi action: [untouched]
Sync data usage: [Prefer Wifi]
Sync mobile data preferences: Prefer 3G
Not only do I use franco.Kernel apk for access to Franco's latest releases, I also use it for functionalities:
Sqlite defrag on boot,
Disable logger
Set max freq for s/o
Etc!
set your brightness with the slider to your liking - i stay in the area of 50%. Display = #1 battery hog
~Governor InteractiveX (interactive for additional stability)
~Max freq: 1650 (highest stable freq for your device) ( my thinking is the quicker the info is processed, the less processing time)(works for me) (you may want to experiment with this!)
~Min freq: 350 (as franco once said, less disatance between min / max = less time spent switching frequencies)
default IO sechduler
lastly for now, remmeber that your GPU settings will greatly affect batery life! i keep my gpu at 307 unless i dgaf about battery at time (for LK inside terminal simply type $su [enter]; $oc gpu 0 [enter]
if you're using set on boot, make certain that you have (lets say feature A) feature A set on boot for instance within either franco.Kernel.apk OR leantweaks. if you have feature A set on boot in both franco.Kernel & leantweaks, you will end up negating any battery benefits.. bc the system expending energy uselessly
Sent from my Galaxy Nexus using xda premium

First off I'd like to say ur rom is sick fast and i haven't had 1 reboot or issue since applying it on my verizon nexus. I also get great battery life now. 4-5 hrs screen time and 15 hrs total. Here's kind of a noob question though. I've rooted my android phones in the past.... g1, my touch my touch 3g, and my touch slide. All I really did was flash roms backup tweaks n stuff like that. What and how exactly do u mess with the kernal? Isn't the Franco kernal in liquid 1.4 already? Or are you saying buy the app on the market to keep it updated? Thanks for your help
Sent from my Galaxy Nexus using Tapatalk 2

[FIX] Optimum Color Control Values for Purple Screen/Grain Issue [JB]

Well, after 5 months of looking out for the best values, I've experimented and all and found out these to be the best. Even at lowest brightness, the screen is crisp and clear just like it's supposed to be.
People who have the Purple Screen issue, I highly recommend you use these values.
Requirements -
1. Franco Kernel Updater (TKT wouldn't give that much brightness/crispyness to the screen)
2. ICS Gradient Fix (Check Signature)
3. Franco Kernel
First up, flash Franco's latest kernel.
Secondly, make sure you don't have any 2 or more applications which have Color Control options (Like, Franco Kernel Updater and TKT - Remove TKT and stay with Franco). If you do have 2 or more installed, please set all values to default on all applications including Franco's. (In TKT, click on menu and select reset preferences and reboot).
Third, fire up Franco Kernel Updater and get to the CC options and set these :
Color Multipliers -
Red - 280
Green - 292
Blue - 350
Gamma -
Red - 4
Green - 0
Blue - 9
Disable Contrast Adaptive Brightness - Yes (Tick)
Contrast Control : -24
OMAP Gamma - 1.2
These values work BEST with MoDaCo's JB Build. Tested on Jr1, Jr.1.1, Jr2.
Please note : This is simply a band aid, not a total fix. The purple screen and grain issue is probably a hardware issue. This settings are extremely crisp on my device. You need to get adapted to them.
Thanks to -
1. Franco for his amazing kernel and application.
2. Morfic for introducing contrast control into the kernel world and of course for his kindness. (You're the sweetest developer I've talked to).
Best of luck with these settings guys!
Please, don't forget to click "Thanks"!

It made everything look over-saturated for me.. plus, is it safe to jack up the settings like this?
It did improve the grainy screen on low brightness problem, though.

Well, i think the best values i've EVER Seen.
Oh dear, so f****ng awesome.
via Google Galaxy Nexus

Made my eyes hurt.. Too cold.. I'm trying to get my screen as close to 6500k as possible.
Sent from my Galaxy Nexus using Tapatalk 2

Thank you for this! By far the best optimization of colors I've ever seen. Maybe colors are a bit over-saturated but thats how Super AMOLED should produce.

Doesn't lacking the values up that high create burn in???
Sent from my Galaxy Nexus using xda premium

craigbailey1986 said:
Doesn't lacking the values up that high create burn in???
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Try reducing every multiplier value by 40. 280 to 240, 292 to 252 and 300 to 260.

This can never be an all-in-one "fix" because of the way screen technology works. Everyone's screen will have different degrees of the problem itself (purple tint & grain), on top of that they will all have a slightly different color temperature, contrast level, saturation etc. By providing the values that worked for you, you're just going to have a thread where half the people think it looks great, half think it looks awful, and everyone thinks everyone else is crazy.
A better idea might be to describe the steps you took to arrive at your own numbers, things you looked for, how you tweaked them to get to the best values.

Look Excellent to me - Screen absolutely Pops, so vivid and the gradient issues are not visible.
Thanks so much!

Those high values are gonna kill your screen

OP settings work well for me (similar to my 200 215 280, -2 0 10, -23, CAB off), but OMAP always makes things worse IMO. With OMAP at 1.2 I instantly see banding again where with it off the gradients are smooth. OP settings with OMAP 1.0 are excellent however, reducing the magenta and yellowing I was seeing with my others. I am worried about the burn-in though..

What's this about burn in? Do these settings cause it?

I sort-of mispoke. Burn-in is possible, but high multipliers are more worried to wear out those pixels/degrade them faster.
Edit: I'm going for more of a "Trinity Blue" sort of solution now: 215 235 280, -2 0 15, -24, CAD off, OMAP unset. Still trying to find that balance that gets rid of the magenta/yellow at all points.

Okay guys try out 180,192 and 250 as the color multipliers. No burn issues then. I'm on it right now. Its great!

I'm using Trinity kernel, TKT, and Display Tester Pro for calibration. The gamma test shows that my particular settings should be red=2, green=3, blue=2. The color gamma settings are not relative to one another and are not "mixed together" for adjusting color. Each one is a separate adjustment for that color's correct level of brightness for midtones, relative to darkest and lightest levels. Together, the three settings add up to correct gray brightness levels, not to correct gray colorlessness.
If you look at a chart containing only black, 50% gray, and white, the color multipliers should be adjusted to remove any trace of color tint from the gray. The easiest way to do it is set the weakest color to 200 and reduce the other two colors until the gray has no color tint at all. The properly set color gamma settings, on the other hand, should make the 50% gray have the correct lightness level.
If you have yellow tint, there's not enough blue. Magenta tint means not enough green. Cyan tint, not enough red.
The color multipliers, unlike the gamma settings, are relative to one another. Once you have them set correctly relative to one another, moving them all up or all down together pnly changes the overall brightness of the display. The wrong overall brightness level will remove detail from either the black end or the white end. Too much brightness is also bad for the screen, not to mention battery drain.
So anyway I'll shut up now and I hope everyone gets their screens looking perfect.
gsm gnex / cm9 / trinity / 1420 MHz

for whatever reason trinity seems to be giving me better screen color, but im sure I could do the same with franco, anyways, my gamma settings are untouched, I found that modifying the color to these values makes the purple tint go away for me:
Red:135
Green:135
Blue:190
Trinity Contrast -15 to -25

Have you tried adjusting it for 18% gray? I can nail it pretty close with 180,150,190 and 8,0,8 but gamma is a complete ***** on this display...
strumcat said:
I'm using Trinity kernel, TKT, and Display Tester Pro for calibration. The gamma test shows that my particular settings should be red=2, green=3, blue=2. The color gamma settings are not relative to one another and are not "mixed together" for adjusting color. Each one is a separate adjustment for that color's correct level of brightness for midtones, relative to darkest and lightest levels. Together, the three settings add up to correct gray brightness levels, not to correct gray colorlessness.
If you look at a chart containing only black, 50% gray, and white, the color multipliers should be adjusted to remove any trace of color tint from the gray. The easiest way to do it is set the weakest color to 200 and reduce the other two colors until the gray has no color tint at all. The properly set color gamma settings, on the other hand, should make the 50% gray have the correct lightness level.
If you have yellow tint, there's not enough blue. Magenta tint means not enough green. Cyan tint, not enough red.
The color multipliers, unlike the gamma settings, are relative to one another. Once you have them set correctly relative to one another, moving them all up or all down together pnly changes the overall brightness of the display. The wrong overall brightness level will remove detail from either the black end or the white end. Too much brightness is also bad for the screen, not to mention battery drain.
So anyway I'll shut up now and I hope everyone gets their screens looking perfect.
gsm gnex / cm9 / trinity / 1420 MHz
Click to expand...
Click to collapse

arzbhatia said:
Okay guys try out 180,192 and 250 as the color multipliers. No burn issues then. I'm on it right now. Its great!
Click to expand...
Click to collapse
It's been discussed few times already - going above 200 can lead to screen burn in. On SAMOLED screens blue color wear out first and peeps really shouldn't touch this setting. Better set lower red/green values. Screen will look a bit darker so don't cranck up contrast too much, -10 should be good enough.

herzzreh said:
Made my eyes hurt.. Too cold.. I'm trying to get my screen as close to 6500k as possible.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
look at the graphs.
http://forum.xda-developers.com/showpost.php?p=29037317&postcount=1

herzzreh said:
Have you tried adjusting it for 18% gray? I can nail it pretty close with 180,150,190 and 8,0,8 but gamma is a complete ***** on this display...
Click to expand...
Click to collapse
You can see where your gamma should by by installing the free version of Display Tester from the Play Store. Go to Color, Gamma, and slide the gray screen to the left to see the red page. Find the vertical bar that most closely matches the red bacground. The number on that bar is where your gamma should be set for that color. Mine is spot on at 2.3. Then slide to green page and do the same. Then the blue page. My green gamma reading is 2.8, meaning it isn't quite as bright as the red or blue, so I have to turn it up a hair. My blue is good at 2.3. The adjustment sliders in TKT only give me whole-number choices, so I get as close as possible with 2, 3, 2. I'm just guessing there, since TKT doesn't have normal gamma increments. Anyway good luck taming your gamma.
galaxy nexus (gsm) / cm9 / trinity @ 1.4GHz

[MOD]Auto Brightness Setting - Sense 5.5 - 3.62.401.1

**Updated for Sense 5.5 - 3.62.401.1**
I made this for myself because I wanted to use the auto-brightness feature but the stock values are almost blinding. I thought I'd share it since I'm sure many others think so too. I also modified the button leds to only come on in darkest setting.
Flash in recovery, wipe cache and dalvik cache. You may need to flash more than once because sometimes it doesn't stick. The led buttons should only light up in near darkness.
These are the values I used.
Code:
<integer-array name="config_autoBrightnessLevels">
<item>11</item>
<item>41</item>
<item>91</item>
<item>161</item>
<item>226</item>
<item>321</item>
<item>641</item>
<item>1281</item>
<item>2601</item>
</integer-array>
<integer-array name="config_autoBrightnessLcdBacklightValues">
<item>30</item>
<item>50</item>
<item>65</item>
<item>85</item>
<item>100</item>
<item>115</item>
<item>135</item>
<item>165</item>
<item>195</item>
<item>255</item>
</integer-array>

Thanks i try it with maximusHD
Edit: works on maximus. Can you set brightness some lower?
Sent from my Maximus One Beast in Stealth Black

MaximN97 said:
Thanks i try it with maximusHD
Edit: works on maximus. Can you set brightness some lower?
Sent from my Maximus One Beast in Stealth Black
Click to expand...
Click to collapse
Can you download Rex Light Meter https://play.google.com/store/apps/details?id=com.rex.lightmeter
and tell me at which lux values you want the brightness to be lower.

About how much lower are the auto brightness settings compared to standard auto brightness settings? Thanks
Sent from my HTC One using Tapatalk 2

Thanks.
I've downloaded and been running for last hour or so.
To be honest I can't tell much difference.
How much lower have you set it?
The HTC One has way too bright settings, so you should be able to lower it a lot more and it still look great.
The One is an excellent phone with great battery life, but the biggest drained is the screen brightness. Fix that and you'll make a lot of people happy.
Thanks

Looks promissing!
Is there a way to get the current brightness value [1-255] to get an idea of what is used?
Is it possible to only dimm the ButtonLeds, they are always way to bright, or do we only have 0/1?

I'll give it a try on ViperRom...

Hi ! What file in framework-res.apk should be modified, since I have some mods in framework-res, I don't wanna loose ?
Tnx for info.
Sent from my HTC One using xda premium

nenadr said:
Hi ! What file in framework-res.apk should be modified, since I have some mods in framework-res, I don't wanna loose ?
Tnx for info.
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
/res/values/arrays.xml
line 551
You want to edit these
<integer-array name="config_autoBrightnessLcdBacklightValues">
<integer-array name="config_autoBrightnessLcdBacklightValuesUp">
<integer-array name="config_autoBrightnessLcdBacklightValuesDown">

xfish said:
Looks promissing!
Is there a way to get the current brightness value [1-255] to get an idea of what is used?
Is it possible to only dimm the ButtonLeds, they are always way to bright, or do we only have 0/1?
Click to expand...
Click to collapse
I don't know of any easy way to get the current screen brightness value. If you use the app I mentioned above, you can get the live lux value from the light sensors.
I believe the led buttons is either on or off, but I haven't tried. I have set them to only come on in the darkest setting since my buttons are purplish and look pretty bad.

Stock Values
lux - brightness - percentage
0 - 30 - 12
11 - 50 - 20
41 -50 - 20
91 - 81 - 32
161 - 111 - 44
226 - 142 - 56
321 - 170 - 67
641 - 190 - 75
1281 - 227 - 89
2601 - 255 - 100
New Values
lux - brightness - percentage
0 - 30 - 12
11 - 50 - 20
41 - 65 - 26
91 - 85 - 33
161 - 100 - 39
226 - 115 - 45
321 - 135 - 52
641 - 165 - 65
1281 - 195 - 77
2601 - 255 - 100
Between 91 and 321 lux is pretty tricky. Sometimes I feel its too dark and sometime too bright depending on the where I am. After several days of testing I settle for the settings above.
If you guys have feedback on where you'd like the brightness to be lower, I can make another mod.

krysdafur said:
/res/values/arrays.xml
line 551
You want to edit these
<integer-array name="config_autoBrightnessLcdBacklightValues">
<integer-array name="config_autoBrightnessLcdBacklightValuesUp">
<integer-array name="config_autoBrightnessLcdBacklightValuesDown">
Click to expand...
Click to collapse
This is awesome! Thank you for sharing! I like the bright screen, but its way too bright, don't understand why the defaults are so high!!

Any confirm whether this works on any of the new custom rims based on 2.23.401 roms. I'm tempted to try it.
Sent from my HTC One using Tapatalk 4 Beta

Appears to be working on arhd 12.1
Sent from my HTC One using xda premium

Can you make an up to date version of this?

updated for 3.57.401.500

Does it work in odexed stock rooted rom?

coelhooliveirar said:
Does it work in odexed stock rooted rom?
Click to expand...
Click to collapse
Yes.
updated for 3.62.401.1

I want to flash/try the AutoBrightness.3.62.401.1.zip but how to reverse it without full backup??

Still to flash many times on the latest version?
Sent from my HTC One using XDA Premium 4 mobile app

Tweaked brightness settings - battery saving and readable (edit through CM settings)

I've come up with some great (I think so..) brightness settings for the Razr M. I worked on this to make sure of battery savings while remaining comfortably readable under any light conditions. So here they are if you are interested in having a go:
0 lux - 4% screen brightness
2 lux - 4%
3 lux - 6%
7 lux - 8%
22 lux - 10%
63 lux - 14%
180 lux - 22%
511 lux - 31%
1447 lux - 43%
4095 lux - 57%
11585 lux - 74%
32768 to infinity - 95%
You have to edit them in manually through CM settings, attached is the smooth graph of the outcome (from CM itself):
One thing that has annoyed me on any phone I've had is the auto brightness settings, so I did a bit a research into how the human eye perceives light increase, and its based roughly on log(lux), increasing screen brightness by ^2.5 each step. Result is that I wrote an excel sheet (also attached) with some cool maths where you can adjust some variables to tailor an auto-brightness curve to your taste.
I made a few assumptions specific to the Razr M for the above settings:
- It has a minimum light reading of 2 lux even in the darkest of darks (my defy did the same thing - might be a motorola thing)
- The lux reading is approximately accurate (my galaxy note 8 and Razr M give VERY similar readings under the same light sources)
- I topped the lux reading out at 32k (it does read up to 65k) because its around the starting value of direct sunlight, and it also happens to be a nice round number
Just thought I'd share because I think I nailed the auto brightness settings on this device.
Cheers

How did you get that many step points? I only see 0, 15, 100, 3000 and 8000-infinity.
I am running CM11.2 (4.4.3).
---------- Post added at 10:26 AM ---------- Previous post was at 10:14 AM ----------
Nevermind. Found it by long pressing a segment and choosing "split". Not real intuitive but it works.

Yeah you have to add in a few extra points with my setup. You could probably skip say every second point and it would work almost as well. But the built in brightness points ramped up to quickly for my liking - far brighter then necessary.

Where exactly do you go to in CM to modify these settings? I can't find them...

Display&Lights -- Brightness -- click on the settings icon next to the slider

I didn't mention in the first post, but the excel sheet is very customisable...
If you want to lower brightness there are several ways:
1. lower the maximum brightness
2. Increase the curve value (this affects the middle range of the curve mostly)
3. Increase the maximum lux value
Or if you want to increase brightness, just do the opposite of the points above. You know you have good settings when it looks the same always (ie doesn't suddently appear dim or bright). I think my default value are pretty close. I spent some time fine tuning, but like anything, there is always room for improvement
I also did this calculator so I didn't have to run another app in the background to control auto brightness.. save on a few MB of ram anyway.

Rufus said:
I didn't mention in the first post, but the excel sheet is very customisable...
If you want to lower brightness there are several ways:
1. lower the maximum brightness
2. Increase the curve value (this affects the middle range of the curve mostly)
3. Increase the maximum lux value
Or if you want to increase brightness, just do the opposite of the points above. You know you have good settings when it looks the same always (ie doesn't suddently appear dim or bright). I think my default value are pretty close. I spent some time fine tuning, but like anything, there is always room for improvement
I also did this calculator so I didn't have to run another app in the background to control auto brightness.. save on a few MB of ram anyway.
Click to expand...
Click to collapse
hello can u tell me more about the curve value? which range can be set? and whats the behave on mobile?

Share your KCAL Colour Settings

Hi All!
Kindly share your KCAL settings here
Like this:
Kernel - my kernel - IceMan ( not for public )
OS - LineageOS build myself
My settings:
Red 216
Green 222
Blue 256
Saturation 65
Value 129
Contrast 129
Hue 0
Thank you!

250
240
255
40
132 (140)
132 (140)
10

Red 235
Green 248
Blue 256
Saturation 52
Value 132
Contrast 138
Hue 0
Tianma Panel

Excellent idea to open a thread like this. If anyone has a Kcal profile which makes blacks blacker, whites whiter and colors more vivid, please share your profile. :3. I'm on an LOS based rom by the way.

What app are you using to control the KCal?

techlogik said:
What app are you using to control the KCal?
Click to expand...
Click to collapse
Elementalx app its fine, but also required custom kernel for kcal.

240,240,256,50,130,132,0
Whiter screens
Sent from my HTC 10 using XDA-Developers Legacy app

Hmm, I think I found a profile which I like. I used the DarkDroid profile as the base and changed one value.I only changed saturation.
Red: 250
Blue: 250
Green: 256
Saturation: Default is 45 but I changed it to 65
Value: 120
Contrast: 145
Hue: 0

As different type of panel is available and implemented on our beloved HTC10, shouldn't we share what type of panel too ? it's easily available using DevCheck app
I don't think applying settings from a panel to a different brand is really productive.
It's like calibrating a Sony TV and applying the resulted calibrating profile to a Samsung one, just because models share the same IPS panel ? Hmmmm no !
Btw this topic is an excellent idea !)

Fre$h said:
As different type of panel is available and implemented on our beloved HTC10, shouldn't we share what type of panel too ? it's easily available using DevCheck app
I don't think applying settings from a panel to a different brand is really productive.
It's like calibrating a Sony TV and applying the resulted calibrating profile to a Samsung one, just because models share the same IPS panel ? Hmmmm no !
Btw this topic is an excellent idea !)
Click to expand...
Click to collapse
You are right; I have updated my post