Database Info

Battery Tweak Epic Edition RC1

Plans for next revision:
*Add in Decad3nce's temperature control
*Bug nullghost till he gets init scripts running so we can have this startup at boot
This is really a tool for power users
If you don't consider yourself 'comfortable' with messing with your phone, then don't.
This is mostly the work of collin_ph, all the ideas are mostly his and I have only contributed in part to getting some things functioning correctly and some optimizations for the Epic.
What does it do?
This tweak creates a service that periodically checks the phone's power source.
If the power source changes, it reconfigures the device for maximum performace, battery and safety.
Tweaks memory settings for current power source
Re-clocks CPU based upon battery remaining or current power source
Reclocks for maximum performance if on AC power
Reclocks for maximum performance and charging safety if on USB
Reclocks for performance and battery if on Battery
As Battery life is diminished, Maximum CPU frequency is lowered
Tweaks scaling charactaristics depending on power sourcee
CPU Scales up less frequently on battery power
CPU Scales up more frequently on USB/AC power
The CPU is allowed to scale dynamically in all charging states based upon CPU usage
Includes a batt-cfg utility to configure the system
You may load 1 of 3 pre built profiles
Manually configure CPU Frequencies in all charging states
Determine the percentage of underclocking as the battery drains
Configure how often to poll the power state / battery statys
Disable batt.sh service from running at startup
Includes a batt-rm.sh uninstall utility
Includes a batt-diag diagnostic utility
Includes optional Disk performance tweaks (enabled by default)
The Tools
The entire 'application' is written in shell code and was first written just to give a performance and battery boost, but since has evolved more and more.
All the tools mentioned will be utilized either through the terminal, or in adb shell.
batt.sh
This is the core of the entire script. Don't mess with it.
The one thing you should do after installing the script:
Code:
Code:
pidof batt.sh
If theres any number showing up after it, then it's working fine.
batt-cfg
This is the 'main menu' of sorts, as it gives the user all the options and allows them to toggle tweaks/mods on the fly.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
batt-diag
It's a diagnostics utility, allowing you or someone knowledgeable to figure out any issues that you may be having with your device and be able to pinpoint exactly where the problem is.
batt-diag -v gives a more thorough output as you can see here; http://pastie.org/1162034
batt-rm.sh
It's a battery tweak removal script, follow the onscreen prompts and it should remove just about any trace of the battery tweak script.
The Presets
The presets are just default configurations that I have set up that can make your phone more efficient without you, the user, having to manually set everything.
The preset of 800 literally means that 800000 is the scaling_max_freq, or the max frequency, that your phone can achieve after you enable it.
Just typing 1, and then enter, you'll be ready and set to go. Same with 2 or 3.
Customize Settings
This is only for the experienced user, and it allows you to manipulate most/ifnotall the configurables on your device.
Note, you do not need to configure anything to enable this battery mod. Default settings will be assigned at 800MHz.
All the settings explain what each option does, so read them carefully.
Disk Boost
Remounts via noatime and nodiratime. Look up what that means on your own, and why it benefits performance the way it does.
Prerequisites needed to run this
Phoenix kernel 1.48 with Epic Experience should run this just fine
If you're running any other kind of rom, feel free to try it but i cannot guarantee that it will work.
This script will WORK even if you don't have the import call at boot, but it won't survive on the next reboot.
You can check via:
Code:
Code:
pidof batt.sh
NOTE: This script will also prompt you to try to run itself as root if you use it in terminal.
Contributors:
Collin_ph
Decad3nce
myn
onicrom
shabbypenguin
nullghost (aka tehdarkknight)
*make sure you are running these as root*
*disable setcpu while running this*
*been reported as rom manager fc's after batt tweak, simple fix reinstall rom manager* - thanks for the tip Raiderep

Finally got that working

This is perfect. As a former hero user, I was thinking to myself a couple days ago "I wonder if anyone is going to port the collin_ph battery tweak," and here it is.
Thanks!

I'm about to head into work and I got this downloaded. I'll put it to the test for the day. Thanx for the port or whatever you call it, I had this on hero and loved being able to get rid of setcpu(which I never really liked) but still have something governing battery use

Is this compatible or even needed with the mix up kernel?

compatible? maybe as i said this is known working on phoenix kernel as for others i cannot say. needed? well that depends are you happy with your current battery life?

Using Phoenix kernel 1.48 with Epic Experience bogged down my phone after installing, im only at 76% battery life, i cant imagine how slow it would be at 20%
edit:
its fine now, i guess it had to load initially?

Whats the best settings you think we should run..for the best battery life

800mhz or you can use configure to keep that even lower... obviously the lower the cpu freq the less voltage it uses = better battery life

I just set this up to the 800mhz defaults. I will come back with results

How does this govern cpu clocking and usage? I'm assuming there's no live governer such as ondemand or interactive at play here?

phoenix 1.48 has a working interactive governor

shabbypenguin said:
compatible? maybe as i said this is known working on phoenix kernel as for others i cannot say. needed? well that depends are you happy with your current battery life?
Click to expand...
Click to collapse
I don't think anybody is That being said, great work shabby, can't wait til nullghost gets his init scripts working.

shabbypenguin said:
phoenix 1.48 has a working interactive governor
Click to expand...
Click to collapse
So how does this affect setcpu? I'm runnin baked 1.3 ghz kernel..does this mean after I install I won't be at 1.3?
Sent from my SPH-D700 using Tapatalk

this is set for 800/1ghz/1.2ghz i included the configure option so people can make teh .conf however they see fit.. if batt.sh runs on it then it will scale from 1.3ghz after you configure it. witht he beta versions i dont believe anyone got it working on baked snack but if you try please let me know if it works what doesnt etc etc

when i try to run batt.sh i get this message...Mount: cant find /mnt/sdcard in /proc/mounts..what does this mean

its an issue im trying to figure out, batt.sh works fine without it, thats part of the disk speedups, in batt-cfg you can disable it

new feature will update tomorrow

not sure why but shootme is screwy for me recently as you can see. i have 0% tws, 37% voice calls at 30 mins 29s display is on for over an hour. screen is at auto, 3g, drm services RUNNING. oh yea im at 1.2ghz

Still have problems with this tweak...this is wat iam getting when I do batt-cfg I hit number one and I get this....
Loading 800mhz default
[: Bad number
Save settings...
Settings saved
Starting batt.sh
Note: when you exit ADB or terminal, you may have to hit
CTRL-C
Then my phone freezes and I have to pull the battery
Sent from my SPH-D700 using Tapatalk

Music player CPU usage?

So i was playing music today (first time in a while) and not doing much else. I noticed the battery was draining rapidly so here is CPU spy:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I suspect most of that 1200 is the music. How can i keep it down? I am using the stock music player btw
Sent from my pocket-sized, Linux-based computer using electromagnetic radiation... and Tapatalk.

I've found if you go into the market and type in android music you will get the stock froyo music player. It sounds the same and uses about 1/4 as much ram as the stock player
Sent from my SCH-I510 using XDA App

Go to you're about phone in settings and look at battery use. If music is what's causing the battery loss, you can stop overclocking and undervolt at 800 and 1000 aggressively and that should help while you're listening to music.

What CPU governor are you using?

HTCluva said:
I've found if you go into the market and type in android music you will get the stock froyo music player. It sounds the same and uses about 1/4 as much ram as the stock player
Sent from my SCH-I510 using XDA App
Click to expand...
Click to collapse
Thanks; I'll try this.
hazard209 said:
Go to you're about phone in settings and look at battery use. If music is what's causing the battery loss, you can stop overclocking and undervolt at 800 and 1000 aggressively and that should help while you're listening to music.
Click to expand...
Click to collapse
I don't know why, but UV has never worked properly for me. The phone always restarts itself when the CPU enters a UV'd state. Maybe i just need specifics on how to do it.
imnuts said:
What CPU governor are you using?
Click to expand...
Click to collapse
I am using smartassv2. Would conservative help?

Well start simple and test UV values. Just do -50 across the board to start.
Here's what I use: IO Scheduler - noop, CPU Governor - smartassV2, 1200/-50, 1000/-50, 800/-100, 400/-100, 200/-125, 100/-125
But those are pretty aggressive UV settings.

Firstly, I suggest trying the free Mortplayer or the non-free Poweramp. I like them both.
I have the stock music player frozen and I didn't test it. I did test Poweramp and Mortplayer with 160kbps MP3 as well as uncompressed WAV while virtually nothing was running on my phone.
I found the results with OS Monitor. I stared at OS Monitor for quite a while without music playback first to make sure stuff doesn't jack the CPU. Android System jumps from 0 - 1% every now and then. System jumps from 0 - 2 % every now and then. All EQ and Tone filters were disabled.
Each of the following OS Monitor values were averaged in my mind while playing music for a few minutes for each playback type.
Poweramp 160kbps MP3: System and Poweramp processes together averaged 12% (each process was roughly the same average, so the load was split)
Poweramp 44.1 kHz 16bit stereo WAV: System and Poweramp processes together averaged about 9% (Poweramp process was between 1 and 2%- System took most of the load.)
Mortplayer 160kbps MP3: Mortplayer process 0% with System taking the load at 12% average.
Mortplayer 44.1 kHz 16bit stereo WAV: Mortplayer process 0% with System taking the load at 9% average.
In conclusion, Mortplayer and Poweramp use the same overall CPU resources during playback. Playback of MP3 uses more CPU resources than uncompressed WAV files. Mortplayer uses the System process while Poweramp shares the load with the System process.
My setup.
IMO 4.0 kernel with Tegrak Overclock with Interactive X governor. Overclocked to 1.252Ghz. Minimum scaling frequency is at 200Mhz.
CPU Spy shows that I use multiple CPU states (mostly 200, my minimum scaling frequency) during playback, as evidenced by resetting the timers in CPU Spy and refreshing after some time has lapsed while playing music. Is there a way to see the active state? My guess is that the state changes in microseconds, so the existing state status would be pointless (just a guess.)
Does anybody know if OS Monitor is calculating the CPU usage with respect to the maximum frequency all the time? I suspect this is the case.
Sorry for the derailing action.

[GUIDE] Make da Phone run FASTER. Settings optimilization, Barebones, Modding CM11

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Settings Optimilization
(Requirements: being literate, at least half a brain, common sense. If you don't meet these, listen to da song
and go away)​Processor Tweaks
CPU Governor
A CPU governor in Android controls how the CPU raises and lowers its frequency in response to the demands the user is placing on their device
1: OnDemand Governor:
Main goal of the ondemand governor is to switch to max frequency as soon as there is a CPU activity detected to ensure the responsiveness of the system. Ondemand jumps to maximum frequency and decreases the frequency gradually when CPU is less loaded/apporaching idle.
2: Userspace Governor:
This governor, exceptionally rare for the world of mobile devices, allows any program executed by the user to set the CPU's operating frequency.
3: Interactive Governor:
Can be considered a faster ondemand. Snappier with similar battery life.
4: Performance Governor:
This locks the phone's CPU at maximum frequency. Not very power efficient but God, it's fast.
Minimum and Maximum CPU Frequency
These are the values between which your cpu will scale it's clockspeed. The lower is Min value the less battery your phone should consume when not bothered. Max value is the border of how high you will let you CPU go.
The higher it goes the more battery it eats. Many people say it improves the performance, some that it doesn't. Too high values can cause freezes so don't be surprised when that happens
HTC Desire S values:
Min 245-368
Max 1024-1516
Experimental 1612-1804
I/O scheduler
I/O scheduler basically determines the order in which things get written to or read from storage. It will prioritize each block of data based on which process is requesting the operation or how much time it takes to complete each operation
1: Noop:
Inserts all the incoming I/O requests to a First In, First Out queue and implements request merging.
Advantages:
Serves I/O requests with least number of cpu cycles. (Battery friendly?)
Best for flash drives since there is no seeking penalty.
Good throughput on db systems.
Disadvantages:
Reduction in number of cpu cycles used is proportional to drop in performance.
2: Deadline:
Goal is to minimize I/O latency or starvation of a request. The same is achieved by round robin policy to be fair among multiple I/O requests. Five queues are aggressively used to reorder incoming requests.
Advantages:
Nearly a real time scheduler.
Excels in reducing latency of any given single I/O.
Best scheduler for database access and queries.
Bandwidth requirement of a process - what percentage of CPU it needs, is easily calculated.
Like noop, a good scheduler for solid state/flash drives.
Disadvantages:
When system is overloaded, set of processes that may miss deadline is largely unpredictable.
3: ROW
The ROW IO scheduler was developed with the mobile devices needs in
mind. Favoring READ requests over WRITEs decreases the READ latency greatly.
Advantages:
Best READ values so very fast user experience
Disadvantages:
Not so good at WRITEing
4: CFQ:
Completely Fair Queuing scheduler maintains a scalable per-process I/O queue and attempts to distribute the available I/O bandwidth equally among all I/O requests.
Advantages:
Considered to deliver a balanced i/o performance.
Easiest to tune.
Excels on multiprocessor systems.
Best database system performance after deadline.
Disadvantages:
Some users report media scanning takes longest to complete using CFQ.
5: BFQ
Instead of time slices allocation by CFQ, BFQ assigns budgets. Disk is granted to an active process until it's budget (number of sectors) expires.
Advantages:
Believed to be very good for usb data transfer rate.
Believed to be the best scheduler for HD video recording and video streaming. (because of less jitter as compared to CFQ and others)
Considered an accurate i/o scheduler.
Achieves about 30% more throughput than CFQ on most workloads.
Disadvantages:
Not the best scheduler for benchmarking.
Higher budget assigned to a process can affect interactivity and increased latency.
Set on boot
This option sets your CPU values on boot. It's good to let your phone run on your settings for a while before doing that.
Memory management and miscellaneous
zRAM
zRam is a virtual memory, also known as swap space, which lives in the ram. Virtual memory is the part where the system stores memory fragments which are not accessed, making more room for apps to store information in the ram. From my experience makes phone faster.
Advantages:
More memory for you.
Disadvantages:
It uses CPU to compress/decompress so battery dies faster/might cause some lags.
Allow purging of assets
Purging of bitmap memory assets. Think of it as allowing stale items in RAM to be tossed out when you need more RAM.
Kernel samepege merging
Let's say that we have processes called "A" and "B". "A" needs "Y" data to be loaded in memory to run and "B" needs "Z" data. Assuming that "Y" and "Z" are identical kernel samepege merging merges those identical processes into "X" thus increasing available RAM.
16bit transparency & Surface iprovement
Some users claim better performence/smaller battery usage after enabling 16bit and disabling Surface improvement

Barebones
Some of the apps that come with your phone can be safely removed without causing stability issues. They take up space and use resources that could be used for other things. Removing unwanted apps will theoretically make your phone run faster and smoother, plus, you can configure your phone just the way you want it.
WE WANT YOU​to help developing Barebones​
How do I do that?
1. Click on the link.
2. Login to cyanogenmod wiki.
3. Click edit
4. You will see a list of templates. Click (edit) next to Template:Barebones cm10.1
How do I add an app?
You will see something like this:
! <apk name>
! <package name>
! Remove
! Description
! Version
|-
|Android keyboard
|com.android.inputmethod.latin
|{{yes}}
|Stock android keyboard. Safe to remove if replaced with something else for eg. Swype,Swift
|4.2.2
|-
Click to expand...
Click to collapse
These are columns:
! <apk name>
! <package name>
! Remove
! Description
! Version
Click to expand...
Click to collapse
This is how you start and end your row:
|-
Click to expand...
Click to collapse
Behind this you have to write your column content
|
Click to expand...
Click to collapse
Warning! You always have to make all columns even if you want to leave them empty.

Modding
Modding​
So, Google IT guys are the best, they know everything better and magic rainbow is flowing out of their arses... Yet still some people find ways to improve Android:
V6 Supercharger:
Turbo Boost:
RTMixManager™
Looking for a real functioning game booster? Get one here!
CrossBreeder
Lag Reduce/Entropy/DNS+/Tether+/Adblock/Censor Bypass
Direct Injection Turbo

The end
What do you want from us?​
1. Post your settings/OC/ideas on how to make Phone run Faster.
2. Help updating Barebones.
3. Post Mods you're using
Credits: droidphile, mj.vikram, http://androidforums.com/, http://rootzwiki.com/, http://wiki.cyanogenmod.org/, and others...

not bad.... here are some suggestions for post 3
http://forum.xda-developers.com/showthread.php?t=2076101
http://forum.xda-developers.com/showthread.php?t=2113150
http://forum.xda-developers.com/showthread.php?t=2158329
Sent from my GT-I9505 using Tapatalk 2

hisname said:
not bad.... here are some suggestions for post 3
http://forum.xda-developers.com/showthread.php?t=2076101
http://forum.xda-developers.com/showthread.php?t=2113150
http://forum.xda-developers.com/showthread.php?t=2158329
Sent from my GT-I9505 using Tapatalk 2
Click to expand...
Click to collapse
Thanks! Updated.

Hi there is like this new setting in cm11, force high end setting. Anyone care to share their thoughts about that?

[TESTING] Control Swappiness tendency

Hello guys, we have another new option in L Speed.
We are now able to control a swappiness tendency, how much aggressive we want to swap the memory.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You can find this option under virtual memory section as you can see on this image. If there is any issue, please report.
Governor tuner doesn't work on this build.
Thanks for testing

Paget96 said:
Hello guys, we have another new option in L Speed.
We are now able to control a swappiness tendency, how much aggressive we want to swap the memory.
You can find this option under virtual memory section as you can see on this image. If there is any issue, please report.
Thanks for testing
Click to expand...
Click to collapse
Question: does this just change the swappiness percentage, that also can be changed in KA, or are other perimeters changed as well?
Thanks

martyfender said:
Question: does this just change the swappiness percentage, that also can be changed in KA, or are other perimeters changed as well?
Thanks
Click to expand...
Click to collapse
As you can see in L Speed logs, just swappiness.
Sent from my Nexus 5 using Tapatalk

Paget96 said:
As you can see in L Speed logs, just swappiness.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
My 1GB device uses zram by default with a 400mb swap file and swapiness set to 100%. I have overcommit ratio set to zero. I have played with these settings in the past, but I'm not sure if I noticed any difference. Does lowering swapiness improve battery and cpu useage. Also what about lowering the amount of zram space? The only memory intensive app I have is GT Racing 2 Real Racing, but I rarely ever play it. Based on an xda guide, I have dirty_ratio set to 40 and dirty_background_ratio set to 10.
https://forum.xda-developers.com/android/general/guide-comprehensive-guide-to-kernels-t3121088
Thanks

martyfender said:
My 1GB device uses zram by default with a 400mb swap file and swapiness set to 100%. I have overcommit ratio set to zero. I have played with these settings in the past, but I'm not sure if I noticed any difference. Does lowering swapiness improve battery and cpu useage. Also what about lowering the amount of zram space? The only memory intensive app I have is GT Racing 2 Real Racing, but I rarely ever play it. Based on an xda guide, I have dirty_ratio set to 40 and dirty_background_ratio set to 10.
https://forum.xda-developers.com/android/general/guide-comprehensive-guide-to-kernels-t3121088
Thanks
Click to expand...
Click to collapse
It depends on whether you use swap/zram or no, lowering swappiness will reduce a "aggression" of how often kernel swap the memory. If it's lower, it's less, so less frequent CPU usage.

Paget96 said:
It depends on whether you use swap/zram or no, lowering swappiness will reduce a "aggression" of how often kernel swap the memory. If it's lower, it's less, so less frequent CPU usage.
Click to expand...
Click to collapse
I hadn't investigating vm changes much on this newer rom until yesterday. My device uses zram only, by default. Size 400mb, swapiness 100%. About 24 hrs ago I changed them to: size 250, swapiness, 40%. So far, my device appears to have less lag. Other settings I changed recently are dirty_ratio, 40, dirty_background_ratio,10, overcommit_ratio, 0, vfs_cache_ pressure remains at the system default of 100%
Do your cache reclaiming and cache allocation settings in lspeed, tune these parameters?
I/O tweak related: I had also enabled I/O boost and I/O extended que. I was experiencing some system lag, especially after wakeup, device unused overnight. Is it possible these two settings were the cause of the lag? I have them disabled now to test.
Thanks

martyfender said:
I hadn't investigating vm changes much on this newer rom until yesterday. My device uses zram only, by default. Size 400mb, swapiness 100%. About 24 hrs ago I changed them to: size 250, swapiness, 40%. So far, my device appears to have less lag. Other settings I changed recently are dirty_ratio, 40, dirty_background_ratio,10, overcommit_ratio, 0, vfs_cache_ pressure remains at the system default of 100%
Do your cache reclaiming and cache allocation settings in lspeed, tune these parameters?
I/O tweak related: I had also enabled I/O boost and I/O extended que. I was experiencing some system lag, especially after wakeup, device unused overnight. Is it possible these two settings were the cause of the lag? I have them disabled now to test.
Thanks
Click to expand...
Click to collapse
Yes, L Speed tune those parameters. And yeah, those can result a lag, test it and report to me.

Since we don't have anything to complain about this option, I assume we don't have to test it anymore. You are pleasured with those parameters, so I'll close this thread.

Thread re-opened, waiting for some reports about this option and potential improvements.
Thanks for support

We are also fine with this option, nothing much to test here.
If you have any problems with this option, please write to this thread.
Thanks for support

How To Guide Optimise Stock Kernel Scheduler & Governor Setting

So, after months of using Pixel 7 family, surely we all know that Tensor 2 is not exactly the best flagship SOC in term of raw power or energy usage, probably due to it's "Exynos Genetics Trait"
that being said, doesnt mean it's down bad. And with some optimisation, we can always try to make it run better. One of the example is by seeing how much better it run on custom kernel. But what about other stock kernel user ?
Well, fortunately, as long as we have root access, the stock kernel still allow us to play with some parameter. And here are some tunables parameters that i use to balance the energy usage and responsiveness of the device. (my aim is 10% battery for 1 Hour of SoT and ±0-1% decrease during 6-10hrs idle)
If you want to know more about each parameters, you can google a lot of linux kernel documentation (like here for example : https://access.redhat.com/solutions/177953)
but for now i'll just write down the change and my configurations. (I used EX Kernel Manager to change the parameters) :
CPU Section :
Switch governors for all CPU clusters from 'sched_pixel' to 'shedutil'
Open "Governor Options" and change the 'rate_limit_us' for all clusters from '10000' to '0'
Open "CPU scheduler options" and use bellow value for respected parameters :
sched_wakeup_granularity_ns : 10000000
sched_tunable_scaling : 1
sched_min_granulatity_ns : 2000000
sched_latency_ns : 12000000
Memory Section :
Disable "ZRAM"
That's it for now. Try and feedback if you find any improvement in your energy usage.
I've been using it for weeks, and pretty happy especially with idle drain. As for SoT, normally i end up with 5-6 Hrs screen time when i down to bed with ±30% battery remaining.

otonieru said:
So, after months of using Pixel 7 family, surely we all know that Tensor 2 is not exactly the best flagship SOC in term of raw power or energy usage, probably due to it's "Exynos Genetics Trait"
that being said, doesnt mean it's down bad. And with some optimisation, we can always try to make it run better. One of the example is by seeing how much better it run on custom kernel. But what about other stock kernel user ?
Well, fortunately, as long as we have root access, the stock kernel still allow us to play with some parameter. And here are some tunables parameters that i use to balance the energy usage and responsiveness of the device. (my aim is 10% battery for 1 Hour of SoT and ±0-1% decrease during 6-10hrs idle)
If you want to know more about each parameters, you can google a lot of linux kernel documentation (like here for example : https://access.redhat.com/solutions/177953)
but for now i'll just write down the change and my configurations. (I used EX Kernel Manager to change the parameters) :
CPU Section :
Switch governors for all CPU clusters from 'sched_pixel' to 'shedutil'
Open "Governor Options" and change the 'rate_limit_us' for all clusters from '10000' to '0'
Open "CPU scheduler options" and use bellow value for respected parameters :
sched_wakeup_granularity_ns : 10000000
sched_tunable_scaling : 1
sched_min_granulatity_ns : 2000000
sched_latency_ns : 12000000
Memory Section :
Disable "ZRAM"
That's it for now. Try and feedback if you find any improvement in your energy usage.
I've been using it for weeks, and pretty happy especially with idle drain. As for SoT, normally i end up with 5-6 Hrs screen time when i down to bed with ±30% battery remaining.
Click to expand...
Click to collapse
Someone said that it reverts back once you reboot?

elong7681 said:
Someone said that it reverts back once you reboot?
Click to expand...
Click to collapse
In the Franco Kernel Manager, there's an option to "keep" the new settings on a reboot. (Not sure about the EX Kernel Manager.)

elong7681 said:
Someone said that it reverts back once you reboot?
Click to expand...
Click to collapse
Right, it reverts back for CPU Governor (Cluster 3) after a reboot. (with EXKM)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then I tried with FKM and problem is the same.
I will see after the night how is my battery drain.
But i can't complain because i loose only 2 or 3% during night (8h)
(Bluetooth and 5G on) No wifi because 5G signal is good.
No custom rom, rooted, january update.

Plathoon said:
Right, it reverts back for CPU Governor (Cluster 3) after a reboot. (with EXKM)
View attachment 5817379
Then I tried with FKM and problem is the same.
I will see after the night how is my battery drain.
But i can't complain because i loose only 2 or 3% during night (8h)
(Bluetooth and 5G on) No wifi because 5G signal is good.
No custom rom, rooted, january update.
Click to expand...
Click to collapse
It's expected that it reverts back to default because it's controlled by multiple things. People shouldn't change the governor. There is a write-up on this in Freak's kernel thread.

ekin_strops said:
It's expected that it reverts back to default because it's controlled by multiple things. People shouldn't change the governor. There is a write-up on this in Freak's kernel thread.
Click to expand...
Click to collapse
Can you provide a link to the write-up please?

Pixel86 said:
Can you provide a link to the write-up please?
Click to expand...
Click to collapse
Post

Mrcactuseater what's your deal always laughing at genuine posts?

ekin_strops said:
It's expected that it reverts back to default because it's controlled by multiple things. People shouldn't change the governor. There is a write-up on this in Freak's kernel thread.
Click to expand...
Click to collapse
Actually you can change the CPU governor from the default one to one of the additional existing alternatives.
The issue is just that the frequency scaling driver for the affected CPU cluster(s) will break if the PowerHAL detects that the Sched_Pixel governor isn't "there" anymore for doing the job that it is supposed to do.

Plathoon said:
But i can't complain because i loose only 2 or 3% during night (8h)
(Bluetooth and 5G on) No wifi because 5G signal is good.
No custom rom, rooted, january update.
Click to expand...
Click to collapse
Damn that's less than half of mine...

Not_Purgatory said:
Actually you can change the CPU governor from the default one to one of the additional existing alternatives.
The issue is just that the frequency scaling driver for the affected CPU cluster(s) will break if the PowerHAL detects that the Sched_Pixel governor isn't "there" anymore for doing the job that it is supposed to do.
Click to expand...
Click to collapse
I never wrote you can't change it, I wrote people SHOULDN'T change it to avoid the issues you mentioned.

You say to try to deactivate zram. Is there any real benefit? Zram is useful?

Techboyz97 said:
You say to try to deactivate zram. Is there any real benefit? Zram is useful?
Click to expand...
Click to collapse
You save CPU cycles at the expense of additional vRAM.

If you use smartpack kernel manager there's an option to apply all changes with a script on boot. That's the way I've always worked with kernels that won't allow changes to stick on boot

Pixel86 said:
You save CPU cycles at the expense of additional vRAM.
Click to expand...
Click to collapse
WUT? lol