Screen on time

blade35 said:

Ohh you got me wrong there. You've posted your screenshots above, I saw them and I trust you. What screenshots I am asking for are the tweaks that you've done in your governor settings and boost scheduling.

Click to expand...

Click to collapse

I run this script on start up in FKM:

#!/system/bin/sh

sysctl -w kernel.sched_upmigrate="80 80"

sysctl -w kernel.sched_tunable_scaling="2"

sysctl -w kernel.sched_downmigrate="60 60"

sysctl -w kernel.sched_latency_ns="800000"

sysctl -w kernel.sched_schedstats="0"

sysctl -w kernel.sched_min_task_util_for_boost="70"

sysctl -w kernel.sched_min_granularity_ns="200000"

sysctl -w kernel.sched_wakeup_granularity_ns="0"

sysctl -w kernel.sched_autogroup_enabled="0"

sysctl -w kernel.sched_upmigrate="80 80"

I need to set sched_upmigrate twice because it doesn't set when ran just once in the script. I also set the schedutil governor down_migrate_ns to 40000 and up_migrate_ns to 10000 on little, big and prime cores, I change vfs pressure to 20, entropy write wake up threshold to 128 and swappiness to 1, under i/o scheduler tunables I edit nr_requests to 32 and turn off i/o stats. That's all I change. And that's how I get 12-13 hour SOT times, I also charge my phone powered off when I notice unusual drain from 100%, like sometimes in the morning I'll notice that the phone drops from 100% to like 97% within minutes, when I drain it down to about 5% I'll power it off and let it charge fully powered off, then turn it on and let it settle while plugged in and then unplug and use as normal, for about 3-4 charge cycles it'll be fine and then start losing charge abnormally fast after unplugging so I do a powered off charge to fix it. I should mention also that I haven't upgraded the Google app, I have its and YouTube's (I used YouTube Vanced magisk module) auto update ticked off under the settings (3 dots) menu for those apps in the play store. They sometimes do still update, I'll notice that YouTube Vanced becomes normal YouTube app and I know Google got updated too so I go to the play store and uninstall from there which reverts them back to the original versions. I don't let Google app update because some new features they come up with raise the idle drain, and since I don't use it or the assistant that much I don't care to have the latest Google app version. All other social media apps are updated to their latest version. If you have Instagram I would recommend you deny it location access because it wakes the phone up quite often to check location, even if you set it to "only while using this app" somehow it has permission to start a foreground service and it uses that to check location with the stricter permission applied when you're not using it, it can't get around the deny permission.
If you're worried about lag, you can either turn on the prefer.idle option in stune boost for top-app (better response but more power drain), or set top-app stune boost to 5 (acceptable response with less battery drain). If you are gonna use a custom kernel and tweak these settings go and check that cpu sets under /dev/stune/audio-app etc have schedtune.prefer_idle set to 0, this is by far the biggest battery drainer, it tells the task scheduler to prefer to run tasks on idle cores for whatever group those tasks are in, in many custom kernels this is usually turned on for foreground tasks, top-app tasks and sometimes background tasks. An article I read when researching this said that in the tests that the developers performed turning off prefer.idle and enabling stune.boost for those groups yelded same response latency with a 15% reduction in power use. Good luck with your tweaking!

Consistent 10 hour screen on time!

I'm on Android 10, OOS 10.3.0.GM57AA rooted with tweaked stock kernel and I get consistent 10 hr screen on time (12 was my personal best) with full overnight charging every other night, I can definitely get 5 hrs sot before 50% battery drain, I'm not running any mods that force gms battery optimization, or apps that force hibernate stuff or modify doze settings, my usage is moderate with mixed WiFi and mobile data usage. According to fk kernel manager's battery monitor my active use is between 6.50% and 7.50% per hour (down from above 10% per hour before tweaks) and my idle use is between 0.35% and 0.55% per hour (down from over 1.50% per hour). I know everyone's usage is different but I think my tweaks should help most people. I'm a car mechanic by trade and love solving problems, and while this phone's battery life is a huge improvement over my essential ph-1 I still thought it could be better. I began my journey with custom kernels like most of you, then I began to note down differences between settings that each kernel had and from there deduced which ones affected power efficiency, I studied what settings the Lspeed magisk modeule made. After all this I began researching what those settings actually did, I poured over Google's device git, I read Linux kernel case studies about the schedutil scheduler and its settings and that's how I came up with my tweaks. I think where people get lost is in the timer settings, the processor's time dialation is different from ours and maybe that's where people get confused with the different nanosecond timers and what effect they have on our perception. I used the time of the average blink of an eye, 100 ms, as my reference point for modifying the scheduler timers, I think that for most use case scenarios google has grossly reduced timers to reduce latency which is supposed to battle lag, in my opinion this creates a lot of overhead that eats into power consumption, calculations are done way too many times before we even see a change on our screen. That's when I set out to reach a balance in timer settings that will let the CPU do what it needs to do in our perceived time instead of its perceived time, I based my settings around milliseconds instead of nanoseconds and it really made a difference. I hope someone with more understanding reads this and can further improve on this concept or prove it wrong. I really would like to share my settings and screenshots and my reasoning, but it's a lot of work with my already busy day to day life. I will do it if there is enough interest especially from someone who has a more intimate knowledge of the Linux EAS kernel.

blade35 said:

Thanks a lot man really!!
I can't comment on the overnight drain cause I had a fresh oos install yesterday from a custom rom with the latest Google app and the overnight idle drain was surprisingly low at about 2% for around 8 hours.
I'm using blue spark kernel and not stock.

Click to expand...

Click to collapse

That's great!

I'm gonna add one last note about the task scheduler kernel.sched_tunable_scaling. There are three values available, but FKM only allows two for enable and disable. That's why I use a script. The three values are 0 for off, 1 for logarithmic scaling of scheduler values based on load, and 2 for linear tuning of values based on number of cores. With my settings that I have I noticed that 1 improves performance quite a bit with a penalty to power consumption, but even with severe underclocking of the cpu cores with 1 apps launch faster than I've ever experienced on any device, and the overall response of the device is super fast. With sched_tunable_scaling set to 2 is where I noticed the power savings, the device behaves normal, but my active use usually hovers at around 6.5% to 7.5% per hour.

chandanthakurit said:

Can you please help me..by sharing steps to optimise the battery..please send it on chandanthakurit@gmail.com.

I will be very thankful to you.

Regards,
Chandan

Click to expand...

Click to collapse

Why should anybody sent you a mail when you can search and learn from the forum?
XDA is for knowledge sharing, it's not a personal help desk

The last 1% died after further 19 mins...

Oh!mazing