[Tips & Tricks][Poll] SetCPU Advanced Configs [NS & NS4G]- Share Yours! - Nexus S General

Ok so it is very hard to find dedicated threads to this and I think the more of us trying this and reporting back to one thread, the more successful we will be in achieving great battery life or performance (i do it for battery life)
Here's what i have found to work well today, just some simple adjustments but my battery didn't drop a single percent for about 1.5 hours of very light use(still great tho).
MAIN TAB
Setting the Scaling to: Conservative
Max: 1000MHz
Min: 100MHz
PROFILES TAB (i only have one profile set):
Screen off - Max: 400 (don't go lower, your phone wont wakeup)- Min: 100- conservative - Priority 50
ADVANCED TAB(minimal changes, but i feel they have helped a bit):
Sampling Rate: 20000
Up Thresh: 80
Down Thresh: 25
Ignore Nice: 0
Freq Step: 20
{
"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"
}
These may not be the best settings as we will play guess n check, but thats the reason of this thread, lets figure these things out.

You need root permission's for this, correct?

driftnut56 said:
You need root permission's for this, correct?
Click to expand...
Click to collapse
yessir you do

You should look into the smartass governor if you want to look for screen off frequencies. SetCPU only wastes CPU cycles for you to do this when a kernel can do it. Of course, I believe the end result is that you're still saving more battery, so at least it's a step forward

I'm overclocking 1.2 ghz. Switching between interactive and conservative.
Conservative has better battery life, but interactive is a bit snappier.
I'm new to the setcpu thing; gathered bits and pieces here and there to try and find the perfect settings.
Great thread though, hopefully people will post so we can take full advantage of this beast!
BTW, Tried to post screenshots, but I need more forum activity.

Had no success with conservative myself it allows the clock to step down to 100 eventhough I have the minimum at 200. The smart ass works like a charm no more lock screen lag
Sent from my Nexus S 4G using Tapatalk

teddybrukshut said:
I'm overclocking 1.2 ghz. Switching between interactive and conservative.
Conservative has better battery life, but interactive is a bit snappier.
I'm new to the setcpu thing; gathered bits and pieces here and there to try and find the perfect settings.
Great thread though, hopefully people will post so we can take full advantage of this beast!
BTW, Tried to post screenshots, but I need more forum activity.
Click to expand...
Click to collapse
Hi. I am new to over clocking with SetCPU. How did you get it to go over the 1000 max? I don't understand all of the other settings enough to feel brave enough to change them other than the first tab.
Thanks

ArizonaLoco said:
Hi. I am new to over clocking with SetCPU. How did you get it to go over the 1000 max? I don't understand all of the other settings enough to feel brave enough to change them other than the first tab.
Thanks
Click to expand...
Click to collapse
You have to flash a custom kernel (i recommend netarchy's kernel), then when you open setcpu, you can "autodetected recommended settings". You will then see the ability to overclock.

itsallsubliminal said:
Ok so it is very hard to find dedicated threads to this and I think the more of us trying this and reporting back to one thread, the more successful we will be in achieving great battery life or performance (i do it for battery life)
Here's what i have found to work well today, just some simple adjustments but my battery didn't drop a single percent for about 1.5 hours of very light use(still great tho).
MAIN TAB
Setting the Scaling to: Conservative
Max: 1000MHz
Min: 100MHz
PROFILES TAB (i only have one profile set):
Screen off - Max: 400 (don't go lower, your phone wont wakeup)- Min: 100- conservative - Priority 50
ADVANCED TAB(minimal changes, but i feel they have helped a bit):
Sampling Rate: 20000
Up Thresh: 80
Down Thresh: 25
Ignore Nice: 0
Freq Step: 20
These may not be the best settings as we will play guess n check, but thats the reason of this thread, lets figure these things out.
Click to expand...
Click to collapse
i used following profiles and UV settings...
still looking into it though...
http://caleb1783.tistory.com/196

I'm not using setcpu. It causes launcher pro to freak out for me. Installed CPU master and all is perfect. Running matr1x 7.5 @1.3 jiggawatts with the smartass v2 governer. Also I'm on gpa17 at the moment.
sent from my Touchwiz'd Nexus S 4g

Related

Utilizing SetCPU

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.

Overclock widget = placebo

The system already dynamically clocks the CPU
Don't believe? Install OSMonitor and look at the "Misc" tab
Notice the "ondemand" governor scaling the processor from 245000 - 998400 hZ
Leads me to believe CPU governing is already in the kernel
You might be right.
The only difference I can think of is with the widget people are using (I have not tried it) the under clocking happens the instant the screen turns off. Where as we have no idea when/how the standard under clocking happens, if it does at all.
I am waiting it out. If the under clocking widget is true, it will eventually become common knowledge on these forums. For now I have not seen anything that has convinced me and I fear if i tried it I would suffer from the placebo effect. The last thing I want is another app running in the background for no reason.
strung said:
The system already dynamically clocks the CPU
Don't believe? Install OSMonitor and look at the "Misc" tab
Notice the "ondemand" governor scaling the processor from 245000 - 998400 hZ
Leads me to believe CPU governing is already in the kernel
Click to expand...
Click to collapse
I've noticed this as well. System Panel measures my CPU speed at around 245 Mhz when I'm just swiping through the home screen, but cranks up to 1 Ghz when the CPU usage approaches 100%.
Mecha2142 said:
I've noticed this as well. System Panel measures my CPU speed at around 245 Mhz when I'm just swiping through the home screen, but cranks up to 1 Ghz when the CPU usage approaches 100%.
Click to expand...
Click to collapse
Really? I wonder if that could explain some of the choppiness while scrolling around and general phone use.
I can confirm this with SetCPU's real time monitor. drops to 245 when not in use, and 1ghz when scrolling around
I think oc widget is better. I can choose a 5sec interval in which it checks to see if there are processes that need more CPU power.
I wonder what the intervals are in the stock unrooted OS
Oc widget def works for me, and I'm not just letting my phone sit as a paperweight, I'm using moderate to heavy everyday and the results for me are better.
Also, does the unrooted OS allow other frequencies besides 245 and 1ghz?
Oc widget runs mine in the 300s 500s 700s and 800s when needed
1ghz is not needed all he time when the screen is on. And I don't notice extra lag anywhere
And with 5sec intervals, the screen does not have be off to see 245. Just let it idle for 5 secs
I don't even think the OCwidget works. I mean it tries to set new values, and it thinks they succeed, but I think the new values are ignored by the kernel. For example, I tried to set min and max to 250 mHz and it still shot up to 1 GHz.
My apologies for being a debbie downer.
Here you go... can someone produce something similar with the stock OS unrooted
it does help.. even tho you see my battery between 81 and 79 lol... for me, the top 25% of battery life (from 100-75) goes by fast no matter what, but then it really holds good life afterwards.
{
"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"
}
strung said:
I don't even think the OCwidget works. I mean it tries to set new values, and it thinks they succeed, but I think the new values are ignored by the kernel. For example, I tried to set min and max to 250 mHz and it still shot up to 1 GHz.
My apologies for being a debbie downer.
Click to expand...
Click to collapse
The problem is we are all in the "i think" stage, so its pure speculation. Maybe the oc widget developer could help us out here.
I Do think the op should put a ? In the thread title to get more discussion on this, cuz there are some brilliant minds here at xda
Edit: I emailed the dev w this thread asking for his insite, hopefully he jumps in
Faith is a powerful force
if overclock widget really controlled the clock
1) Linpack scores would reflect that
2) mHz readings would reflect that
But... they don't
strung said:
The system already dynamically clocks the CPU
Don't believe? Install OSMonitor and look at the "Misc" tab
Notice the "ondemand" governor scaling the processor from 245000 - 998400 hZ
Leads me to believe CPU governing is already in the kernel
Click to expand...
Click to collapse
Sounds like you have a problem if your Evo is only running from 245 kHz to 998 kHz.
Minjin said:
Sounds like you have a problem if your Evo is only running from 245 kHz to 998 kHz.
Click to expand...
Click to collapse
How do you figure a problem? 998mhz is max.. u just poking fun at "hz"? lol
So with OSMonitor, do you see any current values besides 245 and 998?
here's mine with OC Widget and some of my defined frequencies... If it truly fluctuates to differents clocks like mine on the stock OS with NO root (please show screenies), i will resign as the OC Widget evo underclock believer until an overclock kernel is released and camera works .
I'm on stock OS with root
It indeed goes to all the freq's
sorry too lazy to screenshot
EDIT: oh and I uninstalled OC widget!
strung said:
I'm on stock OS with root
It indeed goes to all the freq's
sorry too lazy to screenshot
Click to expand...
Click to collapse
and no oc widget? thought i was headed somewhere lol
itsallsubliminal said:
How do you figure a problem? 998mhz is max.. u just poking fun at "hz"? lol
Click to expand...
Click to collapse
That would be 998 millihertz which would be even slower.
I may seem like I'm being pedantic and I wouldn't even mention it if this forum was for arguing about American Idol winners but this forum is by definition populated by geeks and otherwise smart individuals.
Regardless of what the app displays, the phone is operating at 245MHz to 998MHz. The capitalization of the H is official but I'm not that anal. Capitalizing the M means mega (1000000). Lower case means milli (1/1000).
Minjin said:
That would be 998 millihertz which would be even slower.
I may seem like I'm being pedantic and I wouldn't even mention it if this forum was for arguing about American Idol winners but this forum is by definition populated by geeks and otherwise smart individuals.
Regardless of what the app displays, the phone is operating at 245MHz to 998MHz. The capitalization of the H is official but I'm not that anal. Capitalizing the M means mega (1000000). Lower case means milli (1/1000).
Click to expand...
Click to collapse
ROFL!
email from OC Widget dev
here is what the dev (Billy Cui) wrote back to me about OC Widget and the Evo...
"Yes, most system support dynamically clocking, but you will still
benefit on using OCW, especially for save battery. And some system do
not running cpu full speed, and with OCW, you can force it run faster."
Makes sense, like i said about the update interval being adjusted with OCWidget.
comments?

[Q] OC/UV Beater2v1.7 makes my phone unstable with default values, help!

Ok I need to narrow down if I'm doing something wrong, or if my phone is actually faulty.
I have the latest Virtuous Affinity Rom, and installed OC/UV Beater, and I cannot seem to find a stable setting, and after using the VDD/OC reset .zip's that are supposed to reset everything to normal, I still have the issues.
I'm new to the whole OC the phone thing, can someone tell me if my voltages are far off what they should be for my phone.
ALSO could anyone supply me with their virgin (or stable working) files from their MT4G found in the sys/devices/system/cpu/cpu0/cpufreq/ folder so I can double check mine?
It seems below the 537600mhz is where I'm unstable. I stress tested 3 freq at a time and went down the list, that's where I would get the issues.
My OC settings in OC/UV Beater are:
Wake Gov: ondemand
Wake Min: 122000
Wake Max: 1459200
Sleep Gov: conservative
Sleep Min: 122000
Sleep Max: 460800
VDD:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I can think of 2 things.
1) Your wake min is WAY too low. That alone could be the issue.
2) Try bumping the voltage on higher frequencies up a notch.
Asking us if your voltages are ok is asking us a question we can't answer. Always start with default voltages. If that gives you stability VERY slowly adjust your voltage down a notch at a time, allowing time and testing between each setting. Never set on boot until you're SURE it's stable.
Sent from my HTC Glacier using xda app-developers app
estallings15 said:
I can think of 2 things.
1) Your wake min is WAY too low. That alone could be the issue.
2) Try bumping the voltage on higher frequencies up a notch.
Asking us if your voltages are ok is asking us a question we can't answer. Always start with default voltages. If that gives you stability VERY slowly adjust your voltage down a notch at a time, allowing time and testing between each setting. Never set on boot until you're SURE it's stable.
Sent from my HTC Glacier using xda app-developers app
Click to expand...
Click to collapse
Thanks for that. I understand what you are saying as I have been overclocking my PC for years, however, what I don't understand is why does OC/UV Beater2 seem to not be stable at all stock clocks and voltages when I stress test.
I have now gotten 1.5Ghz through 537600mhz stable, however, I cannot get 460mhz through 122mhz stable at stock volts, but it is stable with the voltage boost I have added. I'm curious to see if maybe my default voltage settings have gotten corrupted or misconfigured, that's why I am looking for someone to fill me in on the stock VDD and Freq for my cpu.
Also looking for advice as to what I have set there is normal voltage for the frequencies there?
Just looked at mine on cm 7.2. Your voltages look a little low across rhe board. Clear the data on oc/uv beater and reflash your kernel.
Sent from my HTC Glacier using xda app-developers app
Awesome, when you get a chance could you give me some screen shots of your voltages or tell me how much more yours are boosted?
Well, I'm on a different ROM now, but maybe this will help you. The voltages on this kernel are pretty low.
Sent from my HTC Glacier using xda app-developers app

[Q] What are the default CPU frequencies and governor?

What is the default CPU min/max frequencies and the governor being used? (on stock kernel)
My guess is that the max is 1512 and min is 384. But I'm really not sure what governor is used by default.
Anyone know?
Ondemand
Sent from my Nexus 4 using XDA Premium HD app
Defaults are as follows:
MIN: 1026MHz
MAX: 1512MHz
CPU govenor: ONDEMAND
xandr00 said:
Defaults are as follows:
MIN: 1026MHz
MAX: 1512MHz
CPU govenor: ONDEMAND
Click to expand...
Click to collapse
The default minimum is 1026??? Are you sure? Why would it be set to keep running so high? I heard that it doesn't fall from 1026 to 384 easily until 5-6 seconds have passed...but if 1026 is the minimum..then, smh
Is the default I/O CFQ?
Max - 1512
Min - 384 (CPU Apps don't show it correctly)
Govenor - Ondemand
I/O - Noop
Harry GT-S5830 said:
Max - 1512
Min - 384 (CPU Apps don't show it correctly)
Govenor - Ondemand
I/O - Noop
Click to expand...
Click to collapse
The fact that CPU apps don't show the minimum frequency properly, and the fact that it hangs on 1026 for a few seconds before dropping to 384...do you think that indicates a problem?
I don't know if the minimum is actually 1026 or not but I know for a fact that when you TOUCH the screen, it does ramp up to 1026. So that can be a explanation why battery life isn't as good in reviews.
{
"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"
}
zephiK said:
I don't know if the minimum is actually 1026 or not but I know for a fact that when you TOUCH the screen, it does ramp up to 1026. So that can be a explanation why battery life isn't as good in reviews.
Click to expand...
Click to collapse
I remember with my i9300, as soon as you touched the screen, it would ramp up to 800mhz. It has to do with project butter. It does keep everything running smooth, at the cost of battery life.
K Rich said:
I remember with my i9300, as soon as you touched the screen, it would ramp up to 800mhz. It has to do with project butter. It does keep everything running smooth, at the cost of battery life.
Click to expand...
Click to collapse
never heard such of a thing on the galaxy nexus (might of been present but no one ever mentioned it so im not sure how GN reacts to that). first time ive heard of it.
battery life has been nothing but exceptional for me on N4 and GN. didnt notice a difference between 4.1 and 4.0.x for battery life. it stayed the same or slightly gotten better.
i recommend using franco kernel though
zephiK said:
never heard such of a thing on the galaxy nexus (might of been present but no one ever mentioned it so im not sure how GN reacts to that). first time ive heard of it.
battery life has been nothing but exceptional for me on N4 and GN. didnt notice a difference between 4.1 and 4.0.x for battery life. it stayed the same or slightly gotten better.
i recommend using franco kernel though
Click to expand...
Click to collapse
I agree completely, battery life has been great. Just letting others know what might be the cause for "bad" battery life from past experiences

[GUIDE] OnePlus One Uber Battery Savings Guide by oscarandjo

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!

Categories

Resources