Related
Hey all, recently rooted my Hero to CM7 RC4 and I've noticed that it doesn't actually sleep, even when the screen is off. If I turn the screen off (to "sleep" it) for a minute, the up-time (in Status) also goes up by a minute. My battery life is also very poor and is likely a result of the phone never spooling down. Poking around the web, some people thought this was from the default SMS app, but this happened before I had ever sent a text (only received one.) I even installed handcent and used it for a bit, but the phone still doesn't sleep properly. Any ideas?
Have you gone into Spare Parts and checked Partial Wake?
stayclean said:
Have you gone into Spare Parts and checked Partial Wake?
Click to expand...
Click to collapse
I did, but it said the only appreciable lock was 3m 25s for Android System (all time.) Dialer was 4s all time. There are no stats for 'time since last boot' or 'time since last unplugged'; I recently rebooted and have the phone currently plugged in.
Do you use wi-fi, or 3G? Bad or good phone service? Stuff auto-syncing on a regular basis? By the way, pretty sure up-time just displays how long the device has been on, nothing to do with sleep time or anything.
gaan kak said:
Hey all, recently rooted my Hero to CM7 RC4 and I've noticed that it doesn't actually sleep, even when the screen is off. If I turn the screen off (to "sleep" it) for a minute, the up-time (in Status) also goes up by a minute. My battery life is also very poor and is likely a result of the phone never spooling down. Poking around the web, some people thought this was from the default SMS app, but this happened before I had ever sent a text (only received one.) I even installed handcent and used it for a bit, but the phone still doesn't sleep properly. Any ideas?
Click to expand...
Click to collapse
You do have the End button Behaviour to sleep right?
its in sparepatrss?
stayclean said:
Do you use wi-fi, or 3G? Bad or good phone service? Stuff auto-syncing on a regular basis? By the way, pretty sure up-time just displays how long the device has been on, nothing to do with sleep time or anything.
Click to expand...
Click to collapse
Right now I have wi-fi off, with generally average phone service on 3G. Sometimes it dips down to 1 bar or reaches 4, but is usually 2-3.
I have the governor set to 'ondemand', with a min of ~176 and a max of ~714. The brightness is set to auto. I don't know if I have much stuff auto-syncing, is there a way to check if I do? I don't have very many apps installed - I just rooted this afternoon, and this is my first android phone so I'm trying to take it slow.
davidevan said:
You do have the End button Behaviour to sleep right?
its in sparepatrss?
Click to expand...
Click to collapse
Pretty sure in Android, the end button defaults to sleep anyway, so I don't think that really accomplishes much. Maybe try turning off 3G when not using the phone actively? That will drain the battery a bit.
stayclean said:
Do you use wi-fi, or 3G? Bad or good phone service? Stuff auto-syncing on a regular basis? By the way, pretty sure up-time just displays how long the device has been on, nothing to do with sleep time or anything.
Click to expand...
Click to collapse
Yeah, you're right...uptime has nothing to do with sleeping.
To the OP...reboot the phone then let the phone run for about 1.5 - 2 hours or so without using it. Then go to Menu - Settings - About phone - Battery use. Then tap the graph at the top where it shows your time and compare your Awake time bar to your screen on time bar. They should be similar, with a bit more in the awake time depending on wat is set to sync.
To be honest, there is no fix to be honest. I've had this problem on many occasions and it fixes itself automatically whenever it wants to.
Sent from my HERO200 using Tapatalk
What radio are you using??? What kernel are you using??? Also try unckecking auto brightness. Also I think I read the ondemad governor has no sleep frequency,so if your clocked at 748 then your still at 748 when you hit the end button to sleep. Also there's no need to have the end button set to sleep in spare parts the rom should sleep on its on. lm not sure but I don't think the phone will sleep being on that governor. Try smartass or conservative and see if it sleeps then. Also make sure you have compatibility unchecked in spare parts. Also in settings under accounts&sync uncheck mobile data. That will need to be rechecked again to use your data services. Having it on all the time drains big time. Hope some of this helps. If not just post here or pm me and if I can help I will good luck
Yea it's Me Again With the
Modified Hero
laie1472 said:
What radio are you using??? What kernel are you using??? Also try unckecking auto brightness. Also I think I read the ondemad governor has no sleep frequency,so if your clocked at 748 then your still at 748 when you hit the end button to sleep. Also there's no need to have the end button set to sleep in spare parts the rom should sleep on its on. lm not sure but I don't think the phone will sleep being on that governor. Try smartass or conservative and see if it sleeps then. Also make sure you have compatibility unchecked in spare parts. Also in settings under accounts&sync uncheck mobile data. That will need to be rechecked again to use your data services. Having it on all the time drains big time. Hope some of this helps. If not just post here or pm me and if I can help I will good luck
Yea it's Me Again With the
Modified Hero
Click to expand...
Click to collapse
I am merely speaking from experience with no programming or dev experience, but I think ondemand actually does sleep. I use it at 176/729 and my awake and screen on is always similar. See the screenie below and look at the broken blue line below the battery up time. If it wasn't sleeping that line would be solid. Again, this is just my personal experience using ondemand.
{
"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"
}
make it sleep=
just give it some nice warm hot cocoa with a dab of whisky, works like a charm
ranger61878 said:
I am merely speaking from experience with no programming or dev experience, but I think ondemand actually does sleep. I use it at 176/729 and my awake and screen on is always similar. See the screenie below and look at the broken blue line below the battery up time. If it wasn't sleeping that line would be solid. Again, this is just my personal experience using ondemand.
Click to expand...
Click to collapse
I mean you could be right, I'm no dev by far myself but
I'm using jm's kernel 806. Its based off of the same kernel as the aosp gb builds. If you check his kernel thread I asked this question and was given a different answer. Maybe I misunderstood him or didn't ask the question correctly. I'll send him a pm and see if he's in the mood to share some knowledge. I read that link you posted on aosp's thread, very helpful in understanding the kernels operations a bit better. But it didn't mention what those selected governors default to while sleeping. I mean how can I really know what frequency the kernel is currently at while its sleeping??? The min/max can be set with the default oc app. But not the off screen settings. Unless I'm missing something?? And that could be the case??
Yea it's Me Again With the
Modified Hero
I too am noticing lots of awake time on my battery graph with CM7 RC4. I rebooted about an hour ago, and haven't touched my phone until taking these screenshots. (Sorry for hosting them offsite, the network here blocks the xda uploader.)
http://img828.imageshack.us/slideshow/webplayer.php?id=sparepartspartialwakesil.png
One thing I found very interesting is that even though my phone shows nearly 50 minutes of 'awake' time, my battery still reads 100% even though it's been unplugged the entire time.
sleepy
laie1472 said:
I mean you could be right, I'm no dev by far myself but
I'm using jm's kernel 806. Its based off of the same kernel as the aosp gb builds. If you check his kernel thread I asked this question and was given a different answer. Maybe I misunderstood him or didn't ask the question correctly. I'll send him a pm and see if he's in the mood to share some knowledge. I read that link you posted on aosp's thread, very helpful in understanding the kernels operations a bit better. But it didn't mention what those selected governors default to while sleeping. I mean how can I really know what frequency the kernel is currently at while its sleeping??? The min/max can be set with the default oc app. But not the off screen settings. Unless I'm missing something?? And that could be the case??
Yea it's Me Again With the
Modified Hero
Click to expand...
Click to collapse
I haven't a clue...maybe JM can shed some light for us
the sleep would follow the governor design. Smartass caps at 352 and scales down to your min setting based on your input, interactive and ondemand scale differently... ondemand would scale down based on cpu load (app use) to your min, and interactive (input based) would scale down based on your input to your min. IMHO interactive and ondemand are the best. I use ondemand most of the time because I can set the min lower than interactive and still listen to music with the screen off, no choppiness. I do sometimes switch to 352 min interactive or 264 ondemand when I *think* my phone is being slow, lol.
il Duce said:
the sleep would follow the governor design. Smartass caps at 352 and scales down to your min setting based on your input, interactive and ondemand scale differently... ondemand would scale down based on cpu load (app use) to your min, and interactive (input based) would scale down based on your input to your min. IMHO interactive and ondemand are the best. I use ondemand most of the time because I can set the min lower than interactive and still listen to music with the screen off, no choppiness. I do sometimes switch to 352 min interactive or 264 ondemand when I *think* my phone is being slow, lol.
Click to expand...
Click to collapse
I have always used 176/729 ondemand and had no issues with music and get great battery life (and my phone sleeps ).
il Duce said:
the sleep would follow the governor design. Smartass caps at 352 and scales down to your min setting based on your input, interactive and ondemand scale differently... ondemand would scale down based on cpu load (app use) to your min, and interactive (input based) would scale down based on your input to your min. IMHO interactive and ondemand are the best. I use ondemand most of the time because I can set the min lower than interactive and still listen to music with the screen off, no choppiness. I do sometimes switch to 352 min interactive or 264 ondemand when I *think* my phone is being slow, lol.
Click to expand...
Click to collapse
But is there any way to accurately check or confirm the actual frequency??? Or follow the governor design???
Yea it's Me Again With the
Modified Hero
laie1472 said:
But is there any way to accurately check or confirm the actual frequency??? Or follow the governor design???
Yea it's Me Again With the
Modified Hero
Click to expand...
Click to collapse
I don't know that I understand you... The whole point is that they scale based on conditions, so the actual freq would be changing constantly (but only to your min setting). The smartass gov is the only one with screen off/on specific freq - it caps to 352 screen off, and min is 528 screen on... I suppose there's a way you could monitor it using adb, maybe ddms, but it would be changing based on your current load or input, so you wouldn't really get much from it. Does that help?
il Duce said:
I don't know that I understand you... The whole point is that they scale based on conditions, so the actual freq would be changing constantly (but only to your min setting). The smartass gov is the only one with screen off/on specific freq - it caps to 352 screen off, and min is 528 screen on... I suppose there's a way you could monitor it using adb, maybe ddms, but it would be changing based on your current load or input, so you wouldn't really get much from it. Does that help?
Click to expand...
Click to collapse
Here's what I'm getting at. If the frequency constantly changes due to the users demand or cpu load and maxes out at the selected frequency but doesn't go below the selected frequency either. Then lets say its in the middle of scaling up or down and the user hits the end button, then what frequency would the cpu be at??? Being that it's no way of telling if it hit the min or the max user defined choice. So if the user has a min of 352 and a max of 768 and this were to happen. Couldn't the kernel then be put to sleep at a frequency of 768 ??? After all its still in line with the user defined settings. With apps like over clock widget and set/cpu you could select the off screen clock settings but being as those apps conflict with the native app how can the user be sure of what the off screen frequency is set to if this were the case???
Yea it's Me Again With the
Modified Hero
[KERNEL] mOCk kernel v1.6.12 for MIUI
Credit:
llorn / mantera
originally made for the Triumph. Works on both CacingKalung's MIUI 2.2.3 and elol's Galnet MIUI mod for the Mi410 and supports 2 way call recording!
{
"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"
}
This is a first on MIUI for me
Undervolts great too and has no performance issues till now. Been using it for the last week
how to use undervolt settings ? i hope that will improve the battery life
Edit .: cant get the file ..says its not accessble or removed ??
ok i got it installed !!
used this link
could you tell me how to set the undervolt settings.. getting no frills now
Edit:got incredicontrol set up voltages
Got no frills set up governors n I/o scheduler
Lets see how it goes
apart from 2 way call recording, what extra advantages of this KERNEL. specially in terms of gaming......
how about incoming call valume?
undervolting now working ...its not getting saved !! gives the same default values once rebooted
Zailer. I reckon you haven't used Incredicontrol before
Everything is working fine for me.
So far I haven't encountered the call volume bug but it is indeed lower in volume than that on rc3.
Gaming performance is inferior to rc3 but better than MIUI 1.1.x but the phone is very responsive at even lower clocks.
No other advantage though.
You get 2 way call recording in rc3 too (infact better in the latter since amr recording and in call controls are not working in MIUI).
I haven't been successful with 2wcr in MIUI prior to this. Ymmv.
Sent from my Spice MI-410 on MIUI 2.2.3
thanks for the response.
but whats the big deal in using incredicontrol ? just set the undervolting as the developer told in his thread rite(675,700..). i did it . but when i reboot and check them its shows the default value (900 ,900.. )
should i believe from what you have just told ...that these incredicontrol will show the normal values even when the actual undervolt is working ??
i have tried voltage controll also .. its says undervolting is not allowed in this kernel
may be you can help me by sharing the right way to do things
First check in Settings -> about phone whether the kernel update has been applied or not.
Incredicontrol should remember the voltage values if the set on reboot option is checked.
I am using even more aggressive undervolt settings than the ones suggested by the kernel dev.
Shall post some screenshots later.
Hope this helps
Sent from my Spice MI-410 on MIUI 2.2.3
Testing this kernel now, using CacingKalung's Rom build.
I'm more interested in battery life so I'll be playing around with that, previously on the pure CacingKalung build, I managed to reach 13 hours with undervolting involved, but on the smartassv2 governor. I have Sync all running, Trillian running, I use Navigation, Whatsapp, Wifi and 3g nearly 24/7.
Will be trying to break that even further this time around with InteractiveX. For those interested, my device seems to be able to take much lower voltages, here's what they are.
61440: 600
122880: 600
245760: 600
368640: 600
460800: 600
576000: 850
652800: 850
768000: 850
806400: 900
921600: 925
1024000: 975
1113000: 1000
1209600: 1075
1305600: 1125
1401600: 1150
Will try to reach lower volts with this ROM and report back in.
Btw, IncrediControl works for me fine, saves my voltages FYI.
Remember to reset your battery stats after you flash the kernel. I noticed some significant battery drain before that.
Nice uv :thumbup:
Btw, I have been doing 1.4 ghz @ 1100mv, 1.5 @ 1150 and 1.6 @ 1200
Sent from my Spice MI-410 on MIUI 2.2.3
Guys this is killing me ...
@freerad
Thanks, I appreciate u helping me in detail.. but I have surely tried using "set on boot" and its showed in the about rom page as mock
Ok now am back to ck's rom and mock kernel. I hope the link I downloaded from is the same kenel
Sent from my CSL-MI410
I tried lower before on SpeedDemon Kernel, I haven't tried to see if it's possible on this one, will do soon.
The one thing i find though is that at the speed that I type, the powersaving governors don't work for me, they don't seem to be very able to keep up with my typing speed, so for now I'm back to SmartassV2.
Will try to try for lower volts, for now the results of this kernel will take a while, I usually do daily use testing.
hamsteyr said:
Testing this kernel now, using CacingKalung's Rom build.
I'm more interested in battery life so I'll be playing around with that, previously on the pure CacingKalung build, I managed to reach 13 hours with undervolting involved, but on the smartassv2 governor. I have Sync all running, Trillian running, I use Navigation, Whatsapp, Wifi and 3g nearly 24/7.
Will be trying to break that even further this time around with InteractiveX. For those interested, my device seems to be able to take much lower voltages, here's what they are.
61440: 600
122880: 600
245760: 600
368640: 600
460800: 600
576000: 850
652800: 850
768000: 850
806400: 900
921600: 925
1024000: 975
1113000: 1000
1209600: 1075
1305600: 1125
1401600: 1150
Will try to reach lower volts with this ROM and report back in.
Btw, IncrediControl works for me fine, saves my voltages FYI.
Click to expand...
Click to collapse
OMG ! it is so aggressive settings. installed the kernel and applied these voltage settings. working fine, no considerable lag or whatsoever. but I am still afraid of checking 'set on boot'
mi410 said:
OMG ! it is so aggressive settings. installed the kernel and applied these voltage settings. working fine, no considerable lag or whatsoever. but I am still afraid of checking 'set on boot'
Click to expand...
Click to collapse
no, when I opened Incredicontrl after sometimes, I found some default values, not that lower values that I set. though my phone did not reboot.
need to check with checking 'set on boot'
edit: no matter what I do, voltage settings get back to some default setting,
mi410 said:
no, when I opened Incredicontrl after sometimes, I found some default values, not that lower values that I set. though my phone did not reboot.
need to check with checking 'set on boot'
edit: no matter what I do, voltage settings get back to some default setting,
Click to expand...
Click to collapse
Yep + incredicontrol does not save the custom settings
That's odd then, my IncrediControl works just fine.
You should note that you should allow your IncrediControl to completely load before launching it. By this, I mean WAIT for the sign that says "Incredicontrol has been granted superuser permissions"
For me it seems that it takes a while but it happens, just not instantly. If you load IncrediControl too early, you'll see the default stock voltages.
Anyway, managed to pull 14 hours.
Reverted back to SmartAss v2, running on 1300 Mhz. My system doesn't seem to like lower volts, so these are the same volts as before. I seem to be able to work fine with even just 1200 so I may just clock it back down and try that instead.
hamsteyr said:
That's odd then, my IncrediControl works just fine.
You should note that you should allow your IncrediControl to completely load before launching it. By this, I mean WAIT for the sign that says "Incredicontrol has been granted superuser permissions"
For me it seems that it takes a while but it happens, just not instantly. If you load IncrediControl too early, you'll see the default stock voltages.
Click to expand...
Click to collapse
Exactly
I too believe this is what you guys were doing wrong.
I am using my phone successfully with slightly different clocks but in some ways more aggressive and am getting 30-40% better battery life!
i.e. I still have around 30% charge left when I return home from work.
Include 2 hours of very heavy usage during my commute
Prior to this, I could barely get home with 10% charge and often my battery would discharge completely.
I have set up Tasker to overclock and undervolt along with some handy shortcuts.
I abstained from using apps like SetCPU since I have Tasker running all the time and didn't want to add another background service.
I use the context to undervolt as soon as the display is off and to overclock as soon as the display is turned on. Seems to do the trick
My undervolt / Sleep settings : 61440-1024000 Hz on Interactive governor
My overclock / Wake / Boot settings: 1024000-1612800 Hz on smartass2 governor
My voltage chart:
61440: 600
122880: 700
245760: 750
368640: 800
460800: 850
576000: 850
652800: 850
768000: 850
806400: 900
921600: 950
1024000: 975
1113000: 1000
1209600: 1050
1305600: 1075
1401600: 1100
1516800: 1150
1612800: 1200
Most of the time with these settings, my phone is on 64MHz, 1024MHz and 1.6 Ghz and is quite responsive.
Shall do an overnight cpu-spy test
For games like Blood and Glory, I jack up to 1.6 GHz at performance mode using a Tasker shortcut.
Hope this helps
mi410 said:
OMG ! it is so aggressive settings. installed the kernel and applied these voltage settings. working fine, no considerable lag or whatsoever. but I am still afraid of checking 'set on boot'
Click to expand...
Click to collapse
If your phone doesn't not boot or messes up, just press down the menu button repeatedly while booting and you'll get into safe mode. Then you may clear data in application settings for IncrediControl
ok this time incredicontrol worked. but exactly how , I don't know. I just restarted the phone, charged to 100 % and then then applied these voltage settings but this time I didn't change all at a time. rather I did change one or three at the most at a time and press 'apply' each time until all settings were done. applied 'set on boot' also. need to check the battery backup now.
Trying to use that on mine, clocking 1.2 Ghz max on SmartAssV2, and 64 -> 768 Mhz Interactive X on screen off.
I'm getting some aftermarket 1600 Batteries as well, I'll see what I can get with them after this test.
Edit: It seems that the max that I'm able to reach is just 14 hours on a 1400 mAH battery, not too bad I suppose. Will post more when I get my 1600.
Our phones have become an increasingly more important part of our everyday lives. They have become more and more powerful and the batteries drain even more quicker. The nexus 5 is a powerful device it has a quad core CPU and 2 GB of ram and It can still keep up with most of the new flagships that have come out this year. However with great power come great battery drain. To follow this guide you will need a rooted Nexus 5, and a custom ROM installed I'm using Euphoria OS. (This guide has many useful tips it can be used for other devices not just the nexus 5)
1. Get rooted
You can find help on rooting the nexus 5 all over the Internet by doing a simple Google search, or even here on XDA
2. Install a Custom ROM
Although you don't really need to install one I recommend doing it because they offer extra features. That can help you save battery. I like Euphoria OS.
3. Install a custom kernel
There are many good ones out there I'm using elemental x. Although you could also use Franco or code-blue.
4. Get an app to manage your kernel.
You will need some kind of app to manage your kernel again there are many good ones out there like "kernel Tweaker", I'm using Elemental X which is a paid app but it is definitely worth it.
5. Change CPU settings
Go to the CPU section of the Kernel Manager app and set the governor to elemental x if you are not using the elemental x kernel set it to conservative.
Set the max CPU frequency to less than or equal to 1574MHz, and set the min CPU frequency to 300MHz. Set the max screen of frequency to 729MHz.
6. change the LCD display settings
Go to the graphics section and set the minimum brightness settings to 1. Don't go below one otherwise the display won't light up.
7. Undervolt
Under volt your CPU so it uses less juice and runs much cooler. If you undervolt too much than your phone might reboot randomly
8. Turn off the LTE
Other than your display LTE consumes the most battery. This is why I suggested flashing a custom rom. You can add a toggle to the quick settings menu for LTE so when you need LTE you can turn it on. Personally I can get by with 3G and HSPA+.
9. Edit wifi settings
Go to the settings menu and hit wifi, then hit the three dots to go into advanced wifi settings and turn off scanning always available and turn on avoid poor connections.
10. No animated wallpapers
Turn of all live , animated, or active wallpapers. Whatever it may be called on your device /rom.
Your done.
Now you can hopefully use your device for a couple for hours longer. Let me know your results.
I cannot be held responsible if damage is caused to your device.
Besides screen...3g is placed second...followed by lte...follwed by wifi..then 2g. In battery consumption
Cool little guide. Will help the lesser experienced users starting to learn the ropes of everything
doctor_droid said:
Besides screen...3g is placed second...followed by lte...follwed by wifi..then 2g. In battery consumption
Click to expand...
Click to collapse
I did some research on this and I tried it out myself for a few days before I posted this. And my research and my experience tell me that LTE does drain more battery than 3G or HSPA+. How good or bad your signal is can also impact the battery.
apatel321 said:
I did some research on this and I tried it out myself for a few days before I posted this. And my research and my experience tell me that LTE does drain more battery than 3G or HSPA+. How good or bad your signal is can also impact the battery.
Click to expand...
Click to collapse
Although controversial ...i still support my answer
http://www.electronics-eetimes.com/...phones.html?news_id=222920157&cmp_id=7&page=0
Do a more wiki abt envelop tracking..and nexus 5 has that chip
But nothing specific has been given...
apatel321 said:
I did some research on this and I tried it out myself for a few days before I posted this. And my research and my experience tell me that LTE does drain more battery than 3G or HSPA+. How good or bad your signal is can also impact the battery.
Click to expand...
Click to collapse
In the Anandtech review they showed that under identical circumstances LTE is slightly more efficient than 3G on this device. Close enough that in practice it should come down to whichever has the better signal.
{
"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"
}
bblzd said:
In the Anandtech review they showed that under identical circumstances LTE is slightly more efficient than 3G on this device. Close enough that in practice it should come down to whichever has the better signal.
Click to expand...
Click to collapse
OK I've been proven wrong however you could still set you preffered network mode to 2g and toggle LTE when you need it. (This might be a bit too slow for some people.)Didn't know that its that much more effient my last phone was a sgs2 skyrocket and turning of LTE made a difference of day and night I'm battery. So I continued to do the same with my nexus 5
apatel321 said:
OK I've been proven wrong however you could still set you preffered network mode to 2g and toggle LTE when you need it. (This might be a bit too slow for some people.)Didn't know that its that much more effient my last phone was a sgs2 skyrocket and turning of LTE made a difference of day and night I'm battery. So I continued to do the same with my nexus 5
Click to expand...
Click to collapse
Sgs2 skyrocket didnt had envelop tracking chip...the first qualcomm device to have it was sgs5 mini
i have samsung note right now , my previous device N5 is the worst compare to my note according to battery
apatel321 said:
Our phones have become an increasingly more important part of our everyday lives. They have become more and more powerful and the batteries drain even more quicker. The nexus 5 is a powerful device it has a quad core CPU and 2 GB of ram and It can still keep up with most of the new flagships that have come out this year. However with great power come great battery drain. To follow this guide you will need a rooted Nexus 5, and a custom ROM installed I'm using Euphoria OS. (This guide has many useful tips it can be used for other devices not just the nexus 5)
1. Get rooted
You can find help on rooting the nexus 5 all over the Internet by doing a simple Google search, or even here on XDA
2. Install a Custom ROM
Although you don't really need to install one I recommend doing it because they offer extra features. That can help you save battery. I like Euphoria OS.
3. Install a custom kernel
There are many good ones out there I'm using elemental x. Although you could also use Franco or code-blue.
4. Get an app to manage your kernel.
You will need some kind of app to manage your kernel again there are many good ones out there like "kernel Tweaker", I'm using Elemental X which is a paid app but it is definitely worth it.
5. Change CPU settings
Go to the CPU section of the Kernel Manager app and set the governor to elemental x if you are not using the elemental x kernel set it to conservative.
Set the max CPU frequency to less than or equal to 1574MHz, and set the min CPU frequency to 300MHz. Set the max screen of frequency to 729MHz.
6. change the LCD display settings
Go to the graphics section and set the minimum brightness settings to 1. Don't go below one otherwise the display won't light up.
7. Undervolt
Under volt your CPU so it uses less juice and runs much cooler. If you undervolt too much than your phone might reboot randomly
8. Turn off the LTE
Other than your display LTE consumes the most battery. This is why I suggested flashing a custom rom. You can add a toggle to the quick settings menu for LTE so when you need LTE you can turn it on. Personally I can get by with 3G and HSPA+.
9. Edit wifi settings
Go to the settings menu and hit wifi, then hit the three dots to go into advanced wifi settings and turn off scanning always available and turn on avoid poor connections.
10. No animated wallpapers
Turn of all live , animated, or active wallpapers. Whatever it may be called on your device /rom.
Your done.
Now you can hopefully use your device for a couple for hours longer. Let me know your results.
I cannot be held responsible if damage is caused to your device.
Click to expand...
Click to collapse
We already have two threads dedicated to battery stuff. Not sure why we would need another.
http://forum.xda-developers.com/google-nexus-5/general/nexus-5-battery-results-t2509132
http://forum.xda-developers.com/google-nexus-5/help/battery-life-help-troubleshoot-battery-t2785128
From that same AT article:
"Nexus 5 has ... QFE1100 envelope tracker for its cellular power amplifiers, which lowers power consumption by up to 20 percent"
Interestingly, that same article demonstrates close to 9 hours of wifi surfing time, presumably with screen on. I have yet to get anywhere close to that.
testinguser said:
From that same AT article:
"Nexus 5 has ... QFE1100 envelope tracker for its cellular power amplifiers, which lowers power consumption by up to 20 percent"
Interestingly, that same article demonstrates close to 9 hours of wifi surfing time, presumably with screen on. I have yet to get anywhere close to that.
Click to expand...
Click to collapse
It's not a real world usage test but one designed to put all phones on an equal footing so they can be accurately compared.
For instance their test is running a script that opens up new web pages every 30 seconds and has all background services disabled. This eliminates unpredictable drains and allows the test to be repeatable.
Intro
Over the past while I've finally decided to fix all minor annoyances on my Nexus 4. Here is a guide where I'll share all my modifications to make Mashmallow on the Mako as good as can be.
Kernel
Kernel Proper
The actual kernel included in this guide is HellSpawn kernel by @spezi77 which is based on hells-Core for Marshmallow, with all up-to-date Linux patches (3.4.112) and Google security patches (June 1). (Although I use, advocate, and absolutely recommend HellSpawn, feel free to use another custom kernel in the installer. You'll have to replace zImage and make your own changes to kernel/sema-boot.sh if your kernel doesn't include the same governors, hotplugs, etc.)
Here are a few highlights of HellSpawn itself:
- Includes the elementalx governor from @flar2 and lightweight mako_hotplug driver from @franciscofranco, which are much better than the stock ondemand governor and mpdecision hotplugs.
- Includes franciscofranco's gamma control, which is a much better default gamma for your screen and can be changed with franco's Nexus Display Control app or other Kernel Tweaker Apps.
- Includes a GPU overclock (400 -> 487 MHz) for when really demanding graphics operations require it.
- Includes BFQ, an optimized version of the default kernel's CFQ i/o scheduler. It helps when Play Store updates occur or when apps perform a lot of disk activity.
- Includes double tap to wake feature, which uses minimal extra battery and is much more convenient than the power key.
- When the screen is off, and not sleeping, only one CPU is active and it's limited to 1 GHz, which helps standby battery life with running background services.
Custom Kernel Installer
(original post with r1 was made on reddit)
I've adjusted many default kernel settings, based on a few years experience of running custom kernels. It uses the optimized elementalx governor from ElementalX kernel and lightweight mako_hotplug from franco kernel, with some of flar2's N5 settings, some of @hellsgod's N6 settings, and some of mine. There are other governors and hotplugs available, but from my experience, these offer the best balance of speed and battery life.
It includes a small, safe, -50 mV undervolt for a bit less heat from the CPU. - a user on reddit reported a reboot with r1, so I've removed voltage settings. It's probably useless to include such a small undervolt anyway. Change voltage settings in an init.d script or Kernel Tweaker app if you wish.
It activates double tap to wake by default, and also turns on power key suspend. If you press the power key with the screen on, double tap to wake will be turned off. Those on custom ROMs or Xposed's GravityBox can activate features to turn the screen off (double tap status bar, lock screen, nav bar, etc.) and keep double tap to wake on. Those without custom ROMs can perhaps use something like Greenify which can remap the home button long-press to turn the screen off.
It includes a patch to sepolicy which allows Viper4Android to work in selinux enforcing mode. You need to have SuperSU installed to have this work.
I've adjusted the io scheduler and page cache for better performance, tuned towards random reads.
It includes stock thermald and a tweaked thermald configuration that scales CPU frequencies up and down a little smoother when your temps get high. It should be noted that most custom kernels disable thermald for their own in-kernel thermal driver. I never liked doing this, as thermald does more than just adjust CPU frequencies - it also throttles GPU, screen brightness, and most importantly, battery charging. When your device gets too hot while charging, the worst thing to do is keep up the current and let the battery go over 45 degrees.
It includes a service to do 'Shared Cpufreq Policy', which lets thermald throttle all cores properly, and also lets the Battery Saver feature work correctly, by limiting all cores. This hasn't worked since KitKat and was one of my biggest annoyances. Many, if not all custom kernels just deleted the Power HAL libraries so battery saver feature doesn't work at all!
Includes Semaphore's 'mpdfake', a service to eat the touch boost spam that the Power HAL generates when not using mpdecision. If a custom kernel does not delete the Power HAL libraries, then your logcat is being spammed and logd process uses a lot of background CPU!
Includes a service to attempt to fix once and for all the location/GPS issues. I'm not going to state it works 100% yet, as I've only had max 24 hr uptime while making changes from the r1 release, but so far so good. Fingers crossed...
Includes a service to give SystemUI and Phone/Dialer higher priority. I haven't had a chance to really test it, as my device is sans-SIM at the moment, but it hopefully will lead to better responsiveness when you receive a call. (Under testing: giving some background processes lower priority, so they don't interrupt app usage.)
Move dalvik-cache to /cache partition and free 300-500 MB:
On each boot, it will check to see if you have a /cache/dalvik-cache folder, and will use it as the dalvik-cache if so.
If you are clean flashing a ROM and want to use /cache for dalvik-cache, create an empty dir in TWRP: /cache/dalvik-cache
If you just want to switch from /data to /cache, copy the /data/dalvik-cache to /cache/dalvik-cache and reboot.
Remember to be careful not to wipe /cache when 'dirty' flashing if you do this!
How to reset the mediaserver process quickly to get videos playing:
While your screen has been on for a few seconds or longer, double press the power key. You'll have to try it a few times to get the timing right, because a quick double press activates the camera in some ROMs. Also you're waiting for the screen to go off, not just dark. Practice a few times in low light, and you'll get the hang of the timing: each press should be followed by about half a second. You'll feel a short vibration when the service resets mediaserver to give some feedback that it's working. If it doesn't run the first time, keep cycling the screen off and on again until you get that vibration.
Remember: you have to start with the screen on, this allows you to quickly check on notifications from screen off without resetting mediaserver.
How to reset the sensors if ambient brightness, auto rotation, GPS, or any other sensors stop working:
Same as above, but this time you do the action twice. That is, screen on - double press power - vibrate once - double press power. You must do the two double presses within a second or two, so a little more practice may be needed. You'll feel two short vibrations when the service resets the sensors.
*** As of mod-r4, the new method to reset both mediaserver and sensors is Hold Volume Up and Power.
How to reset the touch screen if it becomes unresponsive:
If you happen to double tap to wake, the screen comes up, but no touches are being registered, tap on the screen with five fingers. If this doesn't reset it, turn the screen off and on again with the power key, and tap on the screen with both hands, all ten fingers. This will reset the driver and get it going again without a reboot.
Download & Installation
The installer is attached to this post. It's for AOSP ROMs, and uses the UberTC 5.4 toolchain. I'll post up CM versions on request.
Flash the zip with TWRP 3.0.2. If you have made any changes to your Marshmallow ROM (other custom kernels, etc.) you must remember to always flash custom kernels after (dirty) flashing custom ROMs! This is especially important, as if you are missing thermald you're going to have a bad time. FLASH YOUR ROM BEFORE THIS KERNEL INSTALLER UNLESS YOU HAVEN'T MADE ANY CHANGES. You can kill your device without thermal throttling!
Wiping dalvik-cache, and /cache is never necessary when flashing a custom kernel only.
ROM
Graphics Drivers
Audio
SuperSU - System or systemless?
Changelog: r14-mod-r3 - r13-mod4 - r16-mod-r5 - r04-mod-r6 - r05-mod-r7
Sorry, ran out of time for now but I'll continue the post soon...
If I want to customise the features, do I only comment out the features which I don't need in sema-boot.sh? Thx!
Hi @xenyz,
Thank you for your new kernel, I have to say that I missed using your projects.
Until now I'm testing it and the only cons I found is that with mako_hotplug when (temp increases) 1026 frequency makes mako very unresponsive.
Is there a way to change this frequency through a init.t script?
Thanks for keeping mako alive!
jer_ying_fd said:
If I want to customise the features, do I only comment out the features which I don't need in sema-boot.sh? Thx!
Click to expand...
Click to collapse
Sure, or another option is to put your overrides in /system/etc/init.d
jolas said:
Until now I'm testing it and the only cons I found is that with mako_hotplug when (temp increases) 1026 frequency makes mako very unresponsive.
Is there a way to change this frequency through a init.t script?
Click to expand...
Click to collapse
Carefully edit /system/etc/thermald.conf either in the installer before flashing, or on your device after flashing, and make your changes near the end of the file.
Can anyone comment on whether their location services are working better? I'm still undecided.
Sent from my Nexus 4 using Tapatalk
With the introduction of the new features of hellspawn r14, will it still work as it is?
jer_ying_fd said:
With the introduction of the new features of hellspawn r14, will it still work as it is?
Click to expand...
Click to collapse
I'm testing it out to make sure it's stable first. At least one change has to be made, turning off the new msm_hotplug which is enabled by default in r14.
Sent from my Nexus 4 using Tapatalk
xenyz said:
I'm testing it out to make sure it's stable first. At least one change has to be made, turning off the new msm_hotplug which is enabled by default in r14.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Ahh of course, I forgot to edit that out....
I've gotten strange behavior after installing the kernel on my Chroma ROM Nexus 4.
The touchscreen began to have bouts of unresponsiveness, when it never had it prior to installation
Extremely slow on wakeup after a long time in sleep mode. Once again, never had that issue before
Overall lag and slowdown that wasn't present on the stock kernel
I've enabled only D2TW, the new I/O scheduler, 1 core active on sleep, Schedule workqueues on awake cores, and ThermalId
Just now, it did a random reboot. Any idea on what the issue could be?
ArtOfSnaila said:
I've enabled only D2TW, the new I/O scheduler, 1 core active on sleep, Schedule workqueues on awake cores, and ThermalId
Just now, it did a random reboot. Any idea on what the issue could be?
Click to expand...
Click to collapse
Could you try it without changing any settings? Force stop the kernel app and reboot.
Do you use any Doze modification apps? Greenify aggressive doze?
Was it a reboot or a SystemUI restart? Did you see the Google bootloader logo? If so, send me last_kmsg
Sent from my Nexus 4 using Tapatalk
xenyz said:
Could you try it without changing any settings? Force stop the kernel app and reboot.
Do you use any Doze modification apps? Greenify aggressive doze?
Was it a reboot or a SystemUI restart? Did you see the Google bootloader logo? If so, send me last_kmsg
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Alright, I'll try it without any settings modified.
I do use Aggressive Doze, could that be conflicting with the kernel? It never seemed to affect the stock kernel besides making the wake take a bit longer, but no lag afterwards.
It was a complete reboot, with the Google logo and everything. Here's the last_kmsg.
ArtOfSnaila said:
I do use Aggressive Doze, could that be conflicting with the kernel? It never seemed to affect the stock kernel besides making the wake take a bit longer, but no lag afterwards.
Click to expand...
Click to collapse
I have noticed some erratic behaviour when modifying doze settings. My best guess is that there are certain assumptions made in Marshmallow as to when the device will be in Doze mode, and changing them can have unintended consequences.
ArtOfSnaila said:
It was a complete reboot, with the Google logo and everything. Here's the last_kmsg.
Click to expand...
Click to collapse
That is strange, the reboot was caused by a restart to recovery request. If it happens again, grab another last_kmsg?
Sent from my Nexus 4 using Tapatalk
xenyz said:
I have noticed some erratic behaviour when modifying doze settings. My best guess is that there are certain assumptions made in Marshmallow as to when the device will be in Doze mode, and changing them can have unintended consequences.
That is strange, the reboot was caused by a restart to recovery request. If it happens again, grab another last_kmsg?
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Ah crap, about the last.kmsg, I think I know what happened. To pull the .txt file I had to reboot into recovery and use terminal to mount /system and then pull it. It might've pulled data off of that restart.
Currently using the phone with no kernel app active, and it's doing fine. I'll keep you posted if weird stuff happens.
Another thing I noticed is that when I plugged in the charger, the phone would slow down a lot.
ArtOfSnaila said:
...
Another thing I noticed is that when I plugged in the charger, the phone would slow down a lot.
Click to expand...
Click to collapse
Maybe it had to do with hotplug settings (I used to have similar problems until I modified thermald.conf settings)
Sent from my Nexus 4 using Tapatalk
ArtOfSnaila said:
Another thing I noticed is that when I plugged in the charger, the phone would slow down a lot.
Click to expand...
Click to collapse
That's likely because of the thermal throttle when the battery gets warm. Keep in mind this is actually good for your battery, although annoying when it slows down.
I'm thinking about raising the threshold just a bit in the next release.
Sent from my Nexus 4 using Tapatalk
xenyz said:
That's likely because of the thermal throttle when the battery gets warm. Keep in mind this is actually good for your battery, although annoying when it slows down.
I'm thinking about raising the threshold just a bit in the next release.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
I found the following changes to accomplish best my needs (snappier phone with average temp)
jolas said:
I found the following changes to accomplish best my needs (snappier phone with average temp)
Click to expand...
Click to collapse
Cool. Er, warm. Eh, whatever.
What's your battery temps whilst charging? This is my main concern and where throttle is necessary.
All batteries achieve optimum service life if used at 20°C (68°F) or slightly below. If, for example, a battery operates at 30°C (86°F) instead of a more moderate lower room temperature, the cycle life is reduced by 20 percent. At 40°C (104°F), the loss jumps to a whopping 40 percent, and if charged and discharged at 45°C (113°F), the cycle life is only half of what can be expected if used at 20°C (68°F).
Click to expand...
Click to collapse
source
I know it's likely not that useful for those of us with original batteries on older devices, but I try to treat it as best I can.
Sent from my Nexus 4 using Tapatalk
xenyz said:
Cool. Er, warm. Eh, whatever.
What's your battery temps whilst charging? This is my main concern and where throttle is necessary.
source
I know it's likely not that useful for those of us with original batteries on older devices, but I try to treat it as best I can.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Charging with screen on, battery temp around 40°C
Sent from my Nexus 4 using Tapatalk
After more than 24 hours of usage without kernel manager, it ran fine, until it started throttling for some reason. Turns out somehow, the max clock speed was locked to 1000 or so Mhz. I don't know if that was the kernel or the app misbehaving, but I ended up having to reactivate the kernel app to set the clock speed back to normal
There was another spontaneous reboot, here's the last.kmsg.
ArtOfSnaila said:
There was another spontaneous reboot, here's the last.kmsg.
Click to expand...
Click to collapse
Thanks for the log. I had a similar reboot but with r14, something in the wakeup_reasons code. I'll have a look through spezi77s commits in kernel/power and see if I can spot something.
I haven't had one reboot in a month or so of using r13, so it's quite strange that you had one so soon, after 24h.
As for the throttle, keep an eye on your battery temperature in Kernel Auditor or whatever and see if it's higher than 40 degrees when you get the 1 GHz max freq.
Edit: I discovered at least one bug in r2 wrt the PowerHal touch boost spam. I'm thinking of posting r14mod3 but I'm not certain r14 is stable yet (see main kernel thread)...
Sent from my Nexus 4 using Tapatalk
I was struggling with my Nexus 6 performance very badly. It was almost unusable. First, its battery used to drain fast. I felt the low performance was due to battery. So I replaced the battery. I also factory reset the phone. After factory resetting the phone was at least smooth. But as soon as I install some apps (not a lot of them), it started to slow down. I used to run 200+ apps without any lag on my Nexus 6. But now it was struggling with 50+ apps. So I felt it must be stock Naugat. So I went to flash lineageOS 15.1 (my first successful experience with MODing android, earlier I bricked one phone and after that never thought of trying it out again). The performance is a bit improved. But its definitely not smooth. Also this is the case with no extra apps installed. Only basic gapps are their. So I am getting fishy about whats going on. So I googled and found this thread.
Someone their said that its working on only two cores!!! And something immediately clicked to me what I have seen but never observed well. Recently I bought poco f1. Just to do performance comparison, I installed antutu on both Nexus 6 and poco. Also whenever I opened Antutu CPU monitor, it always showed two cores are sleeping. That was not the case with poco. All cores are always working. For example, I just charged my Nexus 6 battery to 100%. Also its not in battery saver. Still it says two cores sleeping and only two cores active:
{
"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"
}
People at reddit said installing custom kernel fixes this issue. There are some recommendations on reddit page: Franco, b14ckb1rd and elementalX. I googled and found that there is elementalX app in play store which says to automate whole process. I bought it for ₹250 and installed, backed up current kernel and installed elmentalX. It went into TWRP and installed elementalX successfully. But now my lineageOS is not booting up. It is animating its icon for last 15 minutes? Is it bootloop. I didnt read much earlier about kernels. I felt as offical app installs it, it must be working one. But now reading this thread, it seems that my lineageOS got screwed again. So I have some questions:
1. Is my lineageOS screwed now?
2. If yes what should I do? Flash backed up kernel through TWRP. If yes, how? I never done. Is the procedure same as installing custom ROM? Putting kernel zip in phone and then installing ZIP from TWRP?
3. Is their any custom kernel out their compatible with lineageOS 15.1 which can enable my CPUs two sleeping cores?
Just installed backed up kernel from TWRP. Got my NExus 6 alive. Now point is which custom kernel is compatible with lineageOS 15.1 that will awake my two sleeping cores. My Nexus 6;s two core's are still inactive at 80% battery . Overall performance not smooth.
After watching some videos and some googling, I realized that its not about the kernel actually which turns off cores but its hotplug mpdecision. I installed kernel audiutor,
hotplug mpdecision, I enabled all cores of my Nexus 6. Also I realized that max frequency of my active cores were something 1958 MHz. I just increase it to max 2649 MHz and rebooted. My Nexus 6 is going super smooth now. Also ran geekbench4 benchmarks.
These are the benchmarks.
Before changing CPU stuff
================================================
Benchmarks 1
-----------------------------------------------------------------------------------------------
Single core: 593
Multicore: 997
After changing CPU stuff
================================================
Benchmarks 2
-----------------------------------------------------------------------------------------------
Single core: 818
Multicore: 1009
Benchmarks 3
-----------------------------------------------------------------------------------------------
Single core: 1069
Multicore: 3029
I feel that two cores were still offline during benchmark 2. When I checked after benchmark 2, they were off in kernel adiutor CPU monitor. I re-enabled them and I reran the geekbench. I ended up getting benchmark-3 which are quite good and in fact above average for Nexus 6. For 5-10 minutes now, all cores are active.
I then googled and realized that mpdecision restarts after every reboot. So I have to disable mpdecision on every reboot to enable all cores. Initially I was not getting meaning of two ON/OFF switches on kernel adiutor's interface. They were "Apply on boot" and "mpdecision". Now I have "Apply on boot" switched ON and "mpdecision" switched off. That means on every reboot, all my cores will be up at full frequency right?
Also that means more power consumption. So I have done certain things to compensate. Enabled dark mode so that Nexus's quad HD AMOLED will consume less power. Also installed Franco kernel's Servicely app which allows app and services to put on sleep when screen is off. I am also planning to use Nexis 6's always in battery saver mode. I am ok as long as it performs fast (with two core off, battery saver mode was useless, now it seems like very normal). Its just that only top and bottom orange bars/strips in battery saver mode annoys me.
One more thing I will love to have to save battery. In MIUI, there is per app setting for what to allow when app is in background as can be seen here: http://nine-faq.9folders.com/articl...-background-restriction-on-the-xiaomi-devices On my poco f1, I keep almost all apps "No background activity mode". Only handful have "No restriction". This is letting me extend battery to days straight. Is similar possible on lineageOS say through some apps or setting.
Also can all feel my config all fine? Latest lineageOS + All cores running at full speed + Power saving settings explained above? Is this perfect for performance and battery life?
(Will be testing battery life soon for few days.)
Mahesha999 said:
One more thing I will love to have to save battery. In MIUI, there is per app setting for what to allow when app is in background as can be seen here: http://nine-faq.9folders.com/articl...-background-restriction-on-the-xiaomi-devices On my poco f1, I keep almost all apps "No background activity mode". Only handful have "No restriction". This is letting me extend battery to days straight. Is similar possible on lineageOS say through some apps or setting.)
Click to expand...
Click to collapse
I don't know much about LOS and how close it is to AOSP but in ABC ROM you can go to Settings --> Battery --> click three dots in upper right corner --> select Battery Optimization to set what apps run in the background.
Mahesha999 said:
Just installed backed up kernel from TWRP. Got my NExus 6 alive. Now point is which custom kernel is compatible with lineageOS 15.1 that will awake my two sleeping cores. My Nexus 6;s two core's are still inactive at 80% battery . Overall performance not smooth.
Click to expand...
Click to collapse
- Install the latest LOS nightly 20180926
- in battery management, set the performance profile to fast
- with a kernel manager, disable mpdecision
if that still isn't fast enough, install this custom kernel:
https://forum.xda-developers.com/nexus-6/development/testers-oreo-8-1-custom-kernel-t3798205
- in battery management, set the performance profile to fast
- with a kernel manager, disable mpdecision and CPU hot plugging