After reading this:
http://forum.xda-developers.com/showthread.php?t=2052496
I found I got the "faster" type. As I understand it, this means my cpu has less power/frequency needs, and so, because the stock kernel is configured to manage any of the possible cpu binnings, the settings are probably not the optimal ones for my particular unit. So, does this mean my phone is running at a higher voltage than it needs? Should I undervolt it? How?
While faster CPU binning does mean that you CPU can run more stable at a lower voltage, UV doesn't save you that much of battery.
Most of the battery goes to the screen. The least I have seen around is 50%. Then the next culprit is the radio. And you also have RAM, storage, etc. UV might give you around 1% more battery or so.
You can try UV if you want, but I don't think you need, or should do it.
Sent from my Nexus 4 using xda app-developers app
KyraOfFire said:
While faster CPU binning does mean that you CPU can run more stable at a lower voltage, UV doesn't save you that much of battery.
Most of the battery goes to the screen. The least I have seen around is 50%. Then the next culprit is the radio. And you also have RAM, storage, etc. UV might give you around 1% more battery or so.
You can try UV if you want, but I don't think you need, or should do it.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Actually that's not the in my phone. I don't know what I'm doing wrong but AndroidOS, Google Services or MediaServer usually show up as the battery top drains. I have to say I'm on wifi most of the time and the screen time is usually around 1 hour per day. I'm using all the sync features, google now etc, so I I thought reducing the 384Mhz voltage would have some impact
hallucynogenyc said:
Actually that's not the in my phone. I don't know what I'm doing wrong but AndroidOS, Google Services or MediaServer usually show up as the battery top drains. I have to say I'm on wifi most of the time and the screen time is usually around 1 hour per day. I'm using all the sync features, google now etc, so I I thought reducing the 384Mhz voltage would have some impact
Click to expand...
Click to collapse
Presumably you're not talking about under volting, but under clocking?
Sent from my Nexus 4 using xda premium
No, I'm not. Looking at my cpu modes graph, it makes sense to me that reducing the voltage at which the cpu runs at 384mhz would reduce the consumption:
{
"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"
}
Sent from my Nexus 4 using Tapatalk 2
While it is debatable whether you will save any noticeable amount of battery by undervolting, I have found it to significantly reduce the heat produced by the CPU. Our SOC's are great undervolters, so I don't see any reason NOT to undervolt.
Sent from my Nexus 4 using Tapatalk 2
heat = energy, I highly doubt you can feel a difference in temperature but not in battery lol. How are you guys undervolting? I tried setCPU but it doesn't work, is a custom kernel needed?
KyraOfFire said:
While faster CPU binning does mean that you CPU can run more stable at a lower voltage, UV doesn't save you that much of battery.
Most of the battery goes to the screen. The least I have seen around is 50%. Then the next culprit is the radio. And you also have RAM, storage, etc. UV might give you around 1% more battery or so.
You can try UV if you want, but I don't think you need, or should do it.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I think the battery usage by the screen that is being reported includes more than just the amount of battery used to power the screen. Due to project butter, touching the screen ramps up the CPU to high frequencies, like 1026 - 1512 GHz, making the phone buttery smooth yet sucking the life out of it's battery. In other words, the screen usage includes its touch boost processing usage as well, which in its self is allot of usage. Basically, UV should improve battery life significantly.
Still noone tells me how to do it xD
hallucynogenyc said:
Still noone tells me how to do it xD
Click to expand...
Click to collapse
You need to install a custom kernel that allows undervolting then use an app such as system tuner to undervolt.
Mine shows as a nominal CPU and I could under volt quite a bit. Makes a nice difference to heat and battery life is noticeably better.
Sent from my Nexus 7 using Tapatalk 2
Okay, I thought rooting would be enough Honestly, I'm liking the stock kernel overall, what's the closest to stock kernel that allows undervolting I can find? If there's no such thing, what do you recommend me?
Thanks in advance
The easiest way, with the minimun amount of work, would be flashing motley kernel. UV by default and you faster binning CPU is fully accounted for.
http://forum.xda-developers.com/showthread.php?t=2021437
Trinity kernel also UV by default. He has his own website here
http://forums.derkernel.com/index.php/topic,47.0.html
Download the zip file, flash it in recovery, wipe cache/dalvik and you're good to go.
You can also try other kernel/ROM that support UV. Most likely you will need a control app.
Sent from my Nexus 4 using xda app-developers app
What's a good level to undervolt to I'm on faux's 001 have a nominal cpu and right now I'm -100 MV should I UV more? My phone is still completely stable at this level
mbucks911 said:
What's a good level to undervolt to I'm on faux's 001 have a nominal cpu and right now I'm -100 MV should I UV more? My phone is still completely stable at this level
Click to expand...
Click to collapse
Every phone can handle different uv levels, mine seems to be -150, and I have "fast" cpu. You can try higher but don't set the voltage to be "on boot" or else you'll get the bootloop or freeze.
Related
Anyone have any clue how to set up SetCPU to maximize battery life on a Nexus one with A11 of the Sapphire ROM? There are so many settings and profiles and on demand/conservative/etc. and the profiles and advanced, etc.
Any ideas?
On-demand is way to go for battery life. It basically means it only uses the amount it needs to. So 245-998 means it cuold run less then 998 at low stress times.
I use profiles.
Charging, I turn max down to like 615 or so to keep heat down
Under 40% Battery, I go down to 615 to save battery
OVer 40C, I go down to 576 to get it back under 40C.
Also, some people underclock the CPU to maximize battery life. Just realize there is a give and take because a slower CPU = longer process time. A happy medium is probably the most efficient.
how do you know when the cpu runs faster? like can i open certain apps and see that it goes up? i always see mine at 384
One thing you need to know is that your CPU settings aren't what you think. Setting a "Screen Off" profile is pointless. Your phone idles at 386mhz already. When you set a MAX CPU speed you're telling your phone that it is not allowed to use more than that setting.
The only real thing you're going to get from SetCPU is a "Screen on" MAX.
I set mine at 800 and I got a significant battery life increase.
Cheeze[iT] said:
how do you know when the cpu runs faster? like can i open certain apps and see that it goes up? i always see mine at 384
Click to expand...
Click to collapse
Your CPU goes up when it's being used more. If you're on Ubuntu on your PC you can add a CPU monitor to the task bar. When you open something you can see the usage go up. You can do it on windows too but you have to have task manager open.
It's the same as any computer. Usage = battery loss.
just an FYI...
i have this set between 768-998MHz an i get exceptional battery life and its snappy as well. set on 'performance' and i unplugged the phone this morning at about ~7:30 ans i have 69% battery left under moderately-heavy usage
=] my phone just came back as a replacement NEW on monday. i unlocked the bootloader so i ad to pay them $55.. oh well
dumbestcrayon said:
One thing you need to know is that your CPU settings aren't what you think. Setting a "Screen Off" profile is pointless. Your phone idles at 386mhz already. When you set a MAX CPU speed you're telling your phone that it is not allowed to use more than that setting.
The only real thing you're going to get from SetCPU is a "Screen on" MAX.
I set mine at 800 and I got a significant battery life increase.
Click to expand...
Click to collapse
Can you elaborate? You are saying I should just set the overall max to 800 on my N1? Do I set it to ondemand and set on boot? Won't that slow the device down?
hah2110 said:
Can you elaborate? You are saying I should just set the overall max to 800 on my N1? Do I set it to ondemand and set on boot? Won't that slow the device down?
Click to expand...
Click to collapse
I've been playing with the overall speed as well. i turned mine down to the 600 range and it still feels fine. I'm still confused about the 3 options, the ondemand, userspace or performace... whats the difference? I don't ever feel like it clocks down?
Cheeze[iT] said:
I've been playing with the overall speed as well. i turned mine down to the 600 range and it still feels fine. I'm still confused about the 3 options, the ondemand, userspace or performace... whats the difference? I don't ever feel like it clocks down?
Click to expand...
Click to collapse
http://en.m.wikipedia.org/wiki/Dynamic_frequency_scaling
So my battery life pretty much sucks and i've been looking for a way to improve it a bit, which is how i found this thread.
I downloaded SetCPU already but which settings do i choose to maximize my battery life?
This is how i have it now:
{
"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"
}
Dumbestcrayon said setting max to 800 worked well so i tried but i cant get it exactly on 800. Also, profiles are blank right now since i dont want to choose anything that could stress my phone.
Any help would be awesome
PhantomRampage said:
So my battery life pretty much sucks and i've been looking for a way to improve it a bit, which is how i found this thread.
I downloaded SetCPU already but which settings do i choose to maximize my battery life?
This is how i have it now:
Dumbestcrayon said setting max to 800 worked well so i tried but i cant get it exactly on 800. Also, profiles are blank right now since i dont want to choose anything that could stress my phone.
Any help would be awesome
Click to expand...
Click to collapse
There's not much you can do with SetCPU to improve battery life. I have mine set to 768 at all times and it helps a little. Understand that you're not going to change much. The only way to improve battery life is to not use your phone. Other than that you're pretty much going to get the same results. A lot of people will argue but common CPU knowledge shows other wise.
dumbestcrayon said:
There's not much you can do with SetCPU to improve battery life. I have mine set to 768 at all times and it helps a little. Understand that you're not going to change much. The only way to improve battery life is to not use your phone. Other than that you're pretty much going to get the same results. A lot of people will argue but common CPU knowledge shows other wise.
Click to expand...
Click to collapse
While he may call himself/herself the dumbest crayon, it isn't much so.... Set cpu was made to kill your battery while trying to scavange whatever is left.. it is more intended, now, for overclocked usage. Not stock. Cause as noted.. this is not really for regular use as it only improves a little. What matters is the kernal being used. This is where the engine for everything that you is kept, to work with the processor.
After this, set cpu is a show item...
So just to be clear. I was reading that the HTC Incredible will be underclocked to 768. Is it possible to underclock to 768mhz with just SetCPU, or does a modified kernel have to be flashed to see any battery performance benefit?
thanks.
ghostrida said:
So just to be clear. I was reading that the HTC Incredible will be underclocked to 768. Is it possible to underclock to 768mhz with just SetCPU, or does a modified kernel have to be flashed to see any battery performance benefit?
thanks.
Click to expand...
Click to collapse
yes you can underclock you would set your Max speed to that speed and don't use profiles.
Using Faux123's kernel, I've undervolted significantly. I went from the stock voltages and reduced all the voltages around the table by 150mv.
I can do GL Benchmark @ 1.35GHz and 487MHz (GPU) without the phone thermal throttling, which gets me better results than anandtech's freezer tests (39.6fps), mine being 42 fps on GL Benchmark Egypt HD On-Screen.
So, anyone else UV'ing?
qwahchees said:
Using Faux123's kernel, I've undervolted significantly. I went from the stock voltages and reduced all the voltages around the table by 150mv.
I can do GL Benchmark @ 1.35GHz and 487MHz (GPU) without the phone thermal throttling, which gets me better results than anandtech's freezer tests (39.6fps), mine being 42 fps on GL Benchmark Egypt HD On-Screen.
So, anyone else UV'ing?
Click to expand...
Click to collapse
damn, 150mV is a lot!
I'll def UV my nexus, but probably the same values as my s2: -25 or 50mV
No reboots ?
Nope , no reboots. I'm daring to try -175, or -182.5 ish :S
how has this impacted your battery life?
When i was using faux i got to about -150mv as well. Phone never really got warm as well and battery seems to be abit better. I didn't have it on for more then 1 or 2 days. But i was 100% sable. I ran GLbench as well in a loop for about 2 hours with no lockups or reboots. Makes me think that the reason the voltage is so high is because there is a very limited number of the chips that needed more voltage so they just pumped more voltage into all the chips.
Damn! So lowering the voltages that much made it not throttle at all ???! . what was your temp after bench
Sent from my Nexus 4 using Tapatalk 2
---------- Post added at 05:12 PM ---------- Previous post was at 04:47 PM ----------
qwahchees said:
Using Faux123's kernel, I've undervolted significantly. I went from the stock voltages and reduced all the voltages around the table by 150mv.
I can do GL Benchmark @ 1.35GHz and 487MHz (GPU) without the phone thermal throttling, which gets me better results than anandtech's freezer tests (39.6fps), mine being 42 fps on GL Benchmark Egypt HD On-Screen.
So, anyone else UV'ing?
Click to expand...
Click to collapse
Btw can I ask what governor your using ? . and just to be clear . you under clock and undervolted the cpu. But oced the GPU?
Sent from my Nexus 4 using Tapatalk 2
I'm trying it right now. -150mv seems perfectly stable but I can't judge battery yet.
wow. sounds good. would you be able to run quadrant test as well, and see what you get please?
4470 for me: http://imgur.com/a/FiLC1
Quadrant lasts for a really short time though, < 1 minute. There can't be thermal throttling. The phone gets just barely warm to touch.
Edit: 5518 with performance governor and everything else the same.
Completely forgot about this thread.
Battery life = superb. 3 hr screen time on average, and if lucky almost 4.
No throttling at 1.35GHz, but I haven't tested 1.51GHz. I also managed to get to -187.5 uv undervolt, which is superb. I run all my clockspeeds under 1 volt.
@ italia0101
Yup. OC'd the GPU, undervolted and underclocked the CPU to 1.35GHz. Temp I didn't check. I'll run one later
qwahchees said:
Completely forgot about this thread.
Battery life = superb. 3 hr screen time on average, and if lucky almost 4.
No throttling at 1.35GHz, but I haven't tested 1.51GHz. I also managed to get to -187.5 uv undervolt, which is superb. I run all my clockspeeds under 1 volt.
@ italia0101
Yup. OC'd the GPU, undervolted and underclocked the CPU to 1.35GHz. Temp I didn't check. I'll run one later
Click to expand...
Click to collapse
Can you possibly post a screenshot of the brightness setting that you are using to get the 3 hours? and do you keep mobile connection on or not?
Sent from my Nexus 4
From 1%-35%
So -150mv ended up not being perfectly stable. I thought it was good but it crashed about once a day. Now I'm trying -125. Yesterday I managed to do 12 hrs with 4h screen on. (wifi on and airplane mode 24/7, since I have wifi and gvoice all day).
Raikyure said:
So -150mv ended up not being perfectly stable. I thought it was good but it crashed about once a day. Now I'm trying -125. Yesterday I managed to do 12 hrs with 4h screen on. (wifi on and airplane mode 24/7, since I have wifi and gvoice all day).
Click to expand...
Click to collapse
Has under volting helped at all with the heat issues? Really annoying how it gets so warm after browsing for like 15 min.
I assume this voids the warranty?
I was on faux and i could under volt to a maximum of 125 stable, but honestly, i haven't found any improvement on battery life and overheating.
I'm using Franco now, that doesn't have uv, and my battery life is much much better than on faux...
{
"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"
}
Sent from my Nexus 4 using Tapatalk 2
any update on this?
kaiowas82 said:
I was on faux and i could under volt to a maximum of 125 stable, but honestly, i haven't found any improvement on battery life and overheating.
I'm using Franco now, that doesn't have uv, and my battery life is much much better than on faux...
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Could I ask what settings you are using on Franco's kernel or is it just stock because those results look impressive!
Sent from my Nexus 4 using xda app-developers app
Hello!
I'm interested in undervolting my nexus 4.
My primary cause is to get better battery life and reduce heat.
I use Franco Kernel.
Is undervolting -25 will be useful for my cause?
Undervolting -25 can cause problems?
I heard that if you undervolt too much your device can be damaged.
Thanks in advance to all the helpers!
Wassupdog said:
Hello!
I'm interested in undervolting my nexus 4.
My primary cause is to get better battery life and reduce heat.
I use Franco Kernel.
Is undervolting -25 will be useful for my cause?
Undervolting -25 can cause problems?
I heard that if you undervolt too much your device can be damaged.
Thanks in advance to all the helpers!
Click to expand...
Click to collapse
You won't even notice -25, people usually undervolt -100 or more. I don't think it can damage your phone, it can only get unstable in which case you need to find stable voltages for your device (CPU).
Dark Emotion said:
You won't even notice -25, people usually undervolt -100 or more. I don't think it can damage your phone, it can only get unstable in which case you need to find stable voltages for your device (CPU).
Click to expand...
Click to collapse
Thanks.
Did you ubdervolted ur phone?
Wassupdog said:
Thanks.
Did you ubdervolted ur phone?
Click to expand...
Click to collapse
Yes, my chip is "FAST" and I use these voltages:
{
"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"
}
Dark Emotion said:
Yes, my chip is "FAST" and I use these voltages:
The phone is stable?
Do you feel the difference?
It slows the phone?
It reduce heat?
My chip is slow, what does it means?
Click to expand...
Click to collapse
I answerd with a few questions xD in the qoute ( im from the phone and it is a little bit hard to edit )
Wassupdog said:
I answerd with a few questions xD in the qoute ( im from the phone and it is a little bit hard to edit )
Click to expand...
Click to collapse
These voltages are stable on my phone. Some users use even lower voltages on their "FAST" chip.
On stock ROM I did felt that phone is not as smooth as with default voltages but on Purity ROM which I use now I don't feel huge difference.
It does reduce heat if you undervolt enough.
About chips: Basically, when Qualcomm makes the APQ8064 chip that you see in our Nexus 4, there are 4 different "types" based on how it meets their quality standards. These are Slow, Nominal, Fast, and Faster. The main difference IIRC between these types is how stable each can handle undervolting. CPUs that are "Fast" for example come pre-configured at a lower nominal voltage than a "Nominal" type CPU, and more so than a "Slow" type. (Does this account for how some people's phones generate less heat? Maybe, maybe not. IIRC, there's like only a -100mV difference between Faster and Slow out of the box, however Faster CPUs should be able to handle lower voltages than Slow-type.)
Dark Emotion said:
These voltages are stable on my phone. Some users use even lower voltages on their "FAST" chip.
On stock ROM I did felt that phone is not as smooth as with default voltages but on Purity ROM which I use now I don't feel huge difference.
It does reduce heat if you undervolt enough.
About chips: Basically, when Qualcomm makes the APQ8064 chip that you see in our Nexus 4, there are 4 different "types" based on how it meets their quality standards. These are Slow, Nominal, Fast, and Faster. The main difference IIRC between these types is how stable each can handle undervolting. CPUs that are "Fast" for example come pre-configured at a lower nominal voltage than a "Nominal" type CPU, and more so than a "Slow" type. (Does this account for how some people's phones generate less heat? Maybe, maybe not. IIRC, there's like only a -100mV difference between Faster and Slow out of the box, however Faster CPUs should be able to handle lower voltages than Slow-type.)
Click to expand...
Click to collapse
Do you recommned to me to undervolt?
I have a "Slow" cpu.
What voltages should I set (if you recommend to undervolt)?
Iwant to reduce heat and save battery.
Im using franco kernel and PA 3.99.
Wassupdog said:
Do you recommned to me to undervolt?
I have a "Slow" cpu.
What voltages should I set (if you recommend to undervolt)?
Iwant to reduce heat and save battery.
Im using franco kernel and PA 3.99.
Click to expand...
Click to collapse
If you want to reduce heat and save battery than undervolt your cpu.
Set -50 or -75 and use your phone (test it) for stability.
You can always set the stock voltages if you see that your phone becomes slower and you don't like it.
Dark Emotion said:
If you want to reduce heat and save battery than undervolt your cpu.
Set -50 or -75 and use your phone (test it) for stability.
You can always set the stock voltages if you see that your phone becomes slower and you don't like it.
Click to expand...
Click to collapse
Thanks!
Last question, how can i test stablity?
Wassupdog said:
Thanks!
Last question, how can i test stablity?
Click to expand...
Click to collapse
Just use your phone, play games, run some benchmarks, run StabilityTest app, take some pictures and or videos as well to see if there are any artifacts etc
Check some other threads about undervolting like this one: http://forum.xda-developers.com/showthread.php?t=2155495&highlight=undervolt
Read what users report.
Dark Emotion said:
Just use your phone, play games, run some benchmarks, run StabilityTest app, take some pictures and or videos as well to see if there are any artifacts etc
Check some other threads about undervolting like this one: http://forum.xda-developers.com/showthread.php?t=2155495&highlight=undervolt
Read what users report.
Click to expand...
Click to collapse
Thanks!
Wassupdog said:
Thanks!
Click to expand...
Click to collapse
What app are people using to undervolt?
I'm currently using SetCPU, but somehow i don't trust it to not mess with anything else, like the governor, ect; (any chance of that happening if i don't change anything?).
boomam said:
What app are people using to undervolt?
I'm currently using SetCPU, but somehow i don't trust it to not mess with anything else, like the governor, ect; (any chance of that happening if i don't change anything?).
Click to expand...
Click to collapse
I'm using Trickster mod with neo kernel.
Sent from my Nexus 10 using Tapatalk 4
Targaeryan said:
I'm using Trickster mod with neo kernel.
Sent from my Nexus 10 using Tapatalk 4
Click to expand...
Click to collapse
Trickster looks interesting.
As a question, how come you yourself use it over a more "common" app like SetCPU?
We all know that OnePlus One's 3100 mAh battery and ROM optimizations clearly has given the flagship killer the edge in battery life over its competitors.(puny yureka)
But there is always room for improvement.
Reddit user oscarandjo has published a great guide on various battery saving techniques.
The OnePlus One has a brilliant battery, it's a large battery combined with an efficient processor and that leads to great standby and screen on times. This is why the OnePlus One has one of the best battery lives of all of the current flagships.
There are of course many things you can do to make the battery better, most of these things involve turning useful features off. This guide isn't one where you disable all things that make a smartphone smart, instead it makes small changes that make a big difference.
Many of these methods require root, if you aren't rooted yet and are a technical person get it done ASAP using this guide
This guide doesn't include any basic methods like turning aeroplane mode on in poor signal areas, it's more technical methods.
Click to expand...
Click to collapse
First method is to cut down wakelocks
Second method is to block unnecessary apps location services
Third method is to undervolt your CPU
Fourth method is to use Greenify to auto hibernate apps
Fifth method takes some time, but makes a difference
Sixth method is Amplify
Final method is to hide adverts
Click to expand...
Click to collapse
Visit the thread on Reddit to get the step by step procedures.
Do give oscarandjo's thread an upvote.
{
"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"
}
All of these I already know but it seems like a good guide for people who are new to android.
Some more important things to consider are hotplugging and under clocking.
Underclocking obviously saves battery by reducing the max CPU clock speed and is much more effective than undervolting.
Hotplugging takes up the most battery depending on the type of hotplugging used.
MPDecision is Qualcomm's method of hotplugging and is aggressive but does not respect the max freq when its under clocked. You need MSMLimiter for it to work properly.
Intelliplug has multiple variants in which some allow you to set the min and max number of cores and others which have predefined profiles. Its fast but lags with dt2w.
Alucard hotplug seems the most efficient because stock settings allow for smoothness and battery savings.
My favorite is MSM MPDecision because it allows you to set the number of cores online at any time while respecting other parameters. I find that if you set a max and min of 2 cores online at any time and use the slim CPU governor with gboost disabled, under clocked to 1.5ghz, you get amazing screen on time with zero lag. Approximately an hour every ten percent while being smooth as butter.
Edit: hey @llcooljerry! Nice to see you here on xda for a change!
sent from my amazingly awesome OnePlus One with Stereo Mod
Don't forget to hit thanks!
abhi08638 said:
All of these I already know but it seems like a good guide for people who are new to android.
Some more important things to consider are hotplugging and under clocking.
Underclocking obviously saves battery by reducing the max CPU clock speed and is much more effective than undervolting.
Hotplugging takes up the most battery depending on the type of hotplugging used.
MPDecision is Qualcomm's method of hotplugging and is aggressive but does not respect the max freq when its under clocked. You need MSMLimiter for it to work properly.
Intelliplug has multiple variants in which some allow you to set the min and max number of cores and others which have predefined profiles. Its fast but lags with dt2w.
Alucard hotplug seems the most efficient because stock settings allow for smoothness and battery savings.
My favorite is MSM MPDecision because it allows you to set the number of cores online at any time while respecting other parameters. I find that if you set a max and min of 2 cores online at any time and use the slim CPU governor with gboost disabled, under clocked to 1.5ghz, you get amazing screen on time with zero lag. Approximately an hour every ten percent while being smooth as butter.
Edit: hey @llcooljerry! Nice to see you here on xda for a change!
sent from my amazingly awesome OnePlus One with Stereo Mod
Don't forget to hit thanks!
Click to expand...
Click to collapse
Many thanks, what did you do with cpu boost driver? What are your settings if you have it enabled and which io scheduler?
abhi08638 said:
Edit: hey @llcooljerry! Nice to see you here on xda for a change!
sent from my amazingly awesome OnePlus One with Stereo Mod
Don't forget to hit thanks!
Click to expand...
Click to collapse
Hey buddy I'm glad to be here. But i still lack the technical know how in most parts. I thought i will be able to learn and get the facts from experienced users in here.
The guide is kinda meant for all the new users who wants more out of the battery without much tinkering.
Thanks mate. I seriously will look more into under-clocking my one.
Well i did overclock my M14x laptop a few years back.
Cheers.
eefieboy12 said:
Many thanks, what did you do with cpu boost driver? What are your settings if you have it enabled and which io scheduler?
Click to expand...
Click to collapse
disabled CPU Boost driver because it'll cause lags with slim governor since its basically an on demand governor
sent from my amazingly awesome OnePlus One with Stereo Mod
Don't forget to hit thanks!
Hello, I was recently playing around with the CPU settings in 3C CPU manager, and I noticed the default powersaver configuration isn't that good, compared to mine.
I am using the stock kernel.
Firstly, I noticed that the interactive governor is too sensitive for the A53 cores and it would cause the CPU frequency to jump up to the maximum very easily.
Secondly, I felt that based on my general day-to-day usage (heavy web browsing + some gaming), 4 cores are more than sufficient.
I played around with the ondemand governor and just set its powersave bias to 185, then took all the cores except cores 0, 1 and 4 offline (2x A53 + 1x A57).
I set the A53 cluster to run on the ondemand governor and the A57 core to run on the default interactive governor.
If you want, you can downclock the A53 cluster to 1.34 ghz after you disable pnpmgr, and you should be able to get 6.5 hours of heavy-usage SOT on the stock kernel with little to no lag at all, on a ROM that has Force GPU rendering on.
Do try it out and let me know of the results! :good: (don't forget to disable wakelocks for Google Play Services too)
this is reeeeally high powersaver, too much compromise, and there are people who reach that SOT without any mod
throcker said:
this is reeeeally high powersaver, too much compromise, and there are people who reach that SOT without any mod
Click to expand...
Click to collapse
Hmm... compared to the stock powersaver this actually gives higher scores in both single core and multi core benchmarks. I also have auto-brightness on. However, I get absolutely no lag and my usage is very heavy, almost all my SOT is web browsing on HSPA, with some gaming here and there. I'm open to suggestions though.
For comparison purposes, on the stock powersaver configuration (A53 only), I get 4 hours and 14 minutes of SOT at 1%.
Without downclocking on this configuration, I got 7h 6min of total time and 5h SOT from 98%.
{
"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"
}
throcker said:
this is reeeeally high powersaver, too much compromise, and there are people who reach that SOT without any mod
Click to expand...
Click to collapse
only way i could get that amount of SOT without any mods is if i disabled any and all data/signal and just sat at a picture all day
Which core is a53 cluster and which is a57?
acidspider said:
Which core is a53 cluster and which is a57?
Click to expand...
Click to collapse
0,1,2,3 are the little(A53) and 4,5,6,7 are the big one(a57)
Sorry but these setting were pretty much worthless here. the default settings in the LeeDroid Kernel are much better. Freezing Google Play Services just screwed up my contact list and didn't do much else.
applied your settings (phone was at 97%) went to thanksgiving dinner at my sisters never picked up the phone but about 3 times and made 2 phone calls less than 10min each and used almost 57% of the battery in 4 hours. I typically use about 40% battery in a full 9 hour day at work.
clsA said:
Sorry but these setting were pretty much worthless here. the default settings in the LeeDroid Kernel are much better. Freezing Google Play Services just screwed up my contact list and didn't do much else.
applied your settings (phone was at 97%) went to thanksgiving dinner at my sisters never picked up the phone but about 3 times and made 2 phone calls less than 10min each and used almost 57% of the battery in 4 hours. I typically use about 40% battery in a full 9 hour day at work.
Click to expand...
Click to collapse
freezing google play service breaks more then helps.. also stock settings are much better then any of these "powersaving " settings...actually amplify and greenify with donate app and xposed do help also a lot and using high accuracy mode for location.
but keeping the kernel settings at nearly stock, maybe just lower clocks for both clusters helps a lot.
the problem is, that in 5.x.x LITTLE.big SoCs aren't really optimized...so it will do much better with MM...and maybe when kernel devs are getting more knowledge about LITTLE.big so they could together tweak it more.
clsA said:
Sorry but these setting were pretty much worthless here. the default settings in the LeeDroid Kernel are much better. Freezing Google Play Services just screwed up my contact list and didn't do much else.
applied your settings (phone was at 97%) went to thanksgiving dinner at my sisters never picked up the phone but about 3 times and made 2 phone calls less than 10min each and used almost 57% of the battery in 4 hours. I typically use about 40% battery in a full 9 hour day at work.
Click to expand...
Click to collapse
DeeZZ_NuuZZ said:
freezing google play service breaks more then helps.. also stock settings are much better then any of these "powersaving " settings...actually amplify and greenify with donate app and xposed do help also a lot and using high accuracy mode for location.
but keeping the kernel settings at nearly stock, maybe just lower clocks for both clusters helps a lot.
the problem is, that in 5.x.x LITTLE.big SoCs aren't really optimized...so it will do much better with MM...and maybe when kernel devs are getting more knowledge about LITTLE.big so they could together tweak it more.
Click to expand...
Click to collapse
Oops... I meant disabling wakelocks for google play services :silly:
This has only been tested on the stock kernel...