Related
im running the extreme1.92x kernel oc'd at 1.4 but not sure about the best setup to save battery. i made one profile for charging i put in on max. not sure what to do with the advanced tab settings.
Profiles are really dependent on the user and their needs. The one piece of advice I can give you is to make sure you have a profile set up in case your phone starts to over heat. An OC'ed phone maxed during a charge may get quite toasty.
any suggestions?
Imo dont o/c. Let the kernel operate the way it is setup. O/c cause reboots, phone heating up, and freezes.
Sent from my ADR6400L using XDA App
I'm running Adrynalyne's 4.4.7 kernel and use the following and get really good battery life with no overheating and no lag. I don't do a screen of profile because the governor seems to handle that pretty well.
Normal 1024 max 245 min-Smartass governor
Profiles:
Battery < 25% 768 max 245 min-On demand Governor
Charging 1280 Max 245 min-Smartass governor
itsDollar said:
Profiles:
Battery < 25% 768 max 245 min-On demand Governor
Charging 1280 Max 245 min-Smartass governor
Click to expand...
Click to collapse
Does that actually work?
I thought you had to choose a default governor and setup profiles accordingly.
I didn't know you could setup profiles with a governor that wasn't active or chosen on boot.
the thunderbolt is so fast already theres really no need to over clock. i left it at stock for normal, toned down to 768 when <30% battery and down to 368 when screen off. its a little slow for about half a second when waking up but the battery life is amazing. i can make it through a whole day without charging with moderate use. also running ziggys bfs kernel on virusrom and that added a ton of speed. way better than overclocking that drains your battery
im not asking about overclocking or profiles, just want to know about advanced settings. everything is set to default -1.
qman66 said:
im running the extreme1.92x kernel oc'd at 1.4 but not sure about the best setup to save battery. i made one profile for charging i put in on max. not sure what to do with the advanced tab settings.
Click to expand...
Click to collapse
What Rom are you using?
Go to settings, menu, wireless networks, mobile networks and uncheck the third box. No need to have mobile data always on for most peeps . You'll still have 4G n everything, but gain a good 1-2 maybe more hrs (depending on use, kernels, governor settings, and I/O scheduling. I personally am running BAMF 1.6.2 with adryns 4.4.7 kernel, no set CPU, using tool box for that at 245mhz min - 1.024GHz max with ondemand governor and most importantly SIO Scheduler. Try these n you will have amazing performance and better battery life. Let me know you opinions
Sent from my ADR6400L using XDA Premium App
No matter how precise I click, I can't get SetCPU to set 1024mhz. Closest I can get is 1036. What gives? lol
sprodigy said:
No matter how precise I click, I can't get SetCPU to set 1024mhz. Closest I can get is 1036. What gives? lol
Click to expand...
Click to collapse
Haha, I couldn't tell if you were being serious or not but each kernel has speeds at different increments. 1036 will probably be as close as you can get to 1024.
dopediculous said:
What Rom are you using?
I personally am running BAMF 1.6.2 with adryns 4.4.7 kernel, no set CPU, using tool box for that at 245mhz min - 1.024GHz max with ondemand governor and most importantly SIO Scheduler. Try these n you will have amazing performance and better battery life. Let me know you opinions
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
My settings are identical except running 1.6.3, what does the SIO scheduler do or any of the schedulers for that matter?
mrsmith35sg said:
My settings are identical except running 1.6.3, what does the SIO scheduler do or any of the schedulers for that matter?
Click to expand...
Click to collapse
You can use Wikipedia for the scheduler info. Once you look into it you'll know why I didn't wanna type all those details in here from my phone. Lol, but yeah set that to SIO, Take off ENABLE data always on. N you should be better let me know.
Sent from my ADR6400L using XDA Premium App
rdompor said:
Haha, I couldn't tell if you were being serious or not but each kernel has speeds at different increments. 1036 will probably be as close as you can get to 1024.
Click to expand...
Click to collapse
Go to manage applications and clear data from set CPU and when u go back in to set CPU you will have to hit auto detect n if ur kernel has that frequency you'll be able to click it.
Sent from my ADR6400L using XDA Premium App
On a Samsung Vibrant (U.S.A.) with stock v2.2 what are the best settings, profiles, ect. for saving battery? Also please label the specifics like max/min, scaling, and your advanced settings. Thank you...
EDIT: I understand you can't overclock without a customized kernal, but if I recall correctly you can underclock without it. Am I correct?
If you underclock your phone, it might get better battery life, but it perfomance will go down too and will start lagging, i don't recommend it at all.
The vibrant doesn't like profiles with less than 800 Max, it tends to freeze on wake-up. The amount of savings from an 800 MHz screen off profile is almost immeasurable as well. Also, the default conservative governor is the only one that is reliable. Therefore unless you're overclocking to start with, setcpu doesn't do anything for battery life on our phones. Best to just use a UV kernel such as BALI.
Sent from my SGH-T959 using Tapatalk
Hey man, what you want is undervolt. Underclock will slow you down, and not make a huge difference. However I undervolt by 75mv through the spectrum and have seen great results.
can't hurt to underclock to 800 though, some kernels are ok at 400 but very laggy.
Vibrant - project v, bali 1.8.6UV
JettyLife said:
Hey man, what you want is undervolt. Underclock will slow you down, and not make a huge difference. However I undervolt by 75mv through the spectrum and have seen great results.
can't hurt to underclock to 800 though, some kernels are ok at 400 but very laggy.
Vibrant - project v, bali 1.8.6UV
Click to expand...
Click to collapse
Yes.
Don't underclock. It will make your phone hell.
UNDERVOLT.
thats good.
Ok, I'm posting here because after doing a search, this is the very latest SetCPU thread. Recently, we finally got a worthwhile Gingerbread JVP and several ROM's (Simply Honey 3.8 & Asgard 3.1 JUST AMAZING ROM's) have finally given us some 2.3's we can keep on our phones, well in my opinion anyway.
So, I'm using cmenard's latest Bullet GB Kernel v6.1 and have decided to finally put to use the profiles section on SetCPU. Below is what I'm thinking and would enjoy a friendly conversation of what/if any benefits can be had on Gingerbread and customs Kernels using SetCPU Profiles. I read somewhere that Android is getting much better in regards to battery/performance efficiency, but I noticed a slight fall in battery life on 2.3.4 over 2.2.1 by a few hours.
My Profiles at this time.
Main SetCPU screen
200 min - 1200 max - Conservative? Smartass? Interactive? Any particular Governor worth using other than stock Conservative? - Set on Boot = YES
I'm not quite sure how the priority works on the main screen, I mean let's say I'm at 21% battery life and its time for my battery profile to kick in, but I'm still using the phone for various reasons, wifi calling or benchmarking etc. Will the phone stay at 200-1200 or will it actually use my battery profiles?
Screen Off (Set at 10 minute timeout)
100 - 800 - Conservative - Priority 100
Battery <11%
100 - 400 - Conservative - Priority 75 (Really thinking I should delete this)
Battery <21%
100 - 800 - Conservative - Priority 50
Charging
100 - 800 - Conservative - Priority 25 (Trying to keep the phone cool)
I have read that the Vibrant does not like profiles of 400 or lower when the screen is off, and this must be true as I tried 100-400, 200-400, but they all gave me wake of death until I set the max to 800 (there was no in between a.k.a 500, 600 or 700), so now 100-800 seems to work great for Screen Off. I hate this since when the screen is off the phone does not need to be doing anything other then checking gmail via wifi and notifying me using BLN blinking. Also, I tried to set a profile for Battery temp, but for what ever reason it will NOT give me the save button, so I assume GB now controls that on its own, or cmenard has removed that option from his kernel (or setcpu is borked, lol).
Any tips or concerns with my settings above? Anyone here a guru with SetCPU profiles and can see I'm a noob with profiles? lol
Thanks
SkOrPn
Im trying to underclock the s2 when the phone's screen is off, but when i set it under profiles and put it into effect it will sometimes/most of the time, shut off when trying to awake! I've tried it at various Mhz. I had it at the lowest at first and it didnt' wake up ...so i thought not enough juice to remember all my stuff and it pooped... well i also tried it @ 800 Mhz and also had it set to powersave... im also running widget locker and about 3 widgets(twitter, beautiful widget, and notes), Does anyone know what is going on? Does anyone have any different settings that i should use instead...just trying to preserve battery life when in sleep mode.
Haven't used powersave mode at all yet, It's possible that profile has bugs on this phone.
I have my screen off profile set to 800 mhz and conservative and have had 0 issues so far.
as far as I'm aware powersave doesn't let it out of the minimum frequency (could be wrong). Use the conservative governor instead.
Don't use power save. I have done a lot of testing with this.
Here is the lowest that you can go.
Range: 200-500mhz
Mode: ondemand or conservative
If you go less than 500mhz or put it on powersaver, then it won't wake up from locking the phone.
Thanks
Thanks alot guys, have yall noticed increase battery life using the underclock?
and does widget lock take up alot of battery power? while in "sleep"?
geauxlsu83 said:
Thanks alot guys, have yall noticed increase battery life using the underclock?
and does widget lock take up alot of battery power? while in "sleep"?
Click to expand...
Click to collapse
I noticed that setting it to 200-500mhz increased my battery life by about 15-20%, but I did notice a significant performance drop. 200-800mhz is much less noticeable performance wise, but I didn't check to see what kind of battery life I got on that setting.
As for widgets...I'm not sure on that one either.
geauxlsu83 said:
Im trying to underclock the s2 when the phone's screen is off, but when i set it under profiles and put it into effect it will sometimes/most of the time, shut off when trying to awake! I've tried it at various Mhz. I had it at the lowest at first and it didnt' wake up ...so i thought not enough juice to remember all my stuff and it pooped... well i also tried it @ 800 Mhz and also had it set to powersave... im also running widget locker and about 3 widgets(twitter, beautiful widget, and notes), Does anyone know what is going on? Does anyone have any different settings that i should use instead...just trying to preserve battery life when in sleep mode.
Click to expand...
Click to collapse
Stock kernel or codeworkx's CWM kernel?
If either of those, your screen-off profile MUST include 800 MHz or you'll encounter a sleep of death. It's a common issue with Samsungs, and it is why SetCPU has such a bad reputation on Samsung CPUs, even though the SetCPU author has created kernel patches for nearly every Samsung Android device.
If my kernel or Cyanogenmod 7, screen-off profiles that do not include 800 MHz are OK, HOWEVER:
You must not set a screen-off profile of powersave. The governor mechanics of powersave are not compatible with the "sleep of death" fix. Conservative with min=max=200 SHOULD be OK.
The reason for this is that the CPU enters and exits suspend at 800 MHz (hardware limitation). If the regulator voltages aren't set high enough to support 800 MHz - the CPU crashes.
thanks
yeah im actually flashing your kernel as we speak i looked under a battery thread and they said your kernel is good for battery conservation thanks for your help
actually i flashed it from heimdall and it says it is kernel version is 2.6.35.7 is this yours?
All kernels except my Experimental series say 2.6.35.7 - you need to use CPUSpy to identify the [email protected] that built it.
Anything that comes from me will say [email protected] or, in rare cases, [email protected] until I build a completely new system with a different hostname.
Entropy512 said:
All kernels except my Experimental series say 2.6.35.7 - you need to use CPUSpy to identify the [email protected] that built it.
Anything that comes from me will say [email protected] or, in rare cases, [email protected] until I build a completely new system with a different hostname.
Click to expand...
Click to collapse
Your kernel is nice but can't oc. If I try to go to 1.4 soft reboot city.
Sent from my super modded phone.
Then your phone can't OC.
Not everyone's phone can run at 1.4 or 1.6. There's a reason it's only sold rated at 1.2... As frequency gets higher, the range of "stable" voltages (too low and you crash, too high and you overheat then crash) narrows, to the point where at a certain frequency that varies from device to device, there are no "stable" voltages.
Sent from my GT-P7510 using Tapatalk
Entropy512 said:
Then your phone can't OC.
Not everyone's phone can run at 1.4 or 1.6. There's a reason it's only sold rated at 1.2... As frequency gets higher, the range of "stable" voltages (too low and you crash, too high and you overheat then crash) narrows, to the point where at a certain frequency that varies from device to device, there are no "stable" voltages.
Sent from my GT-P7510 using Tapatalk
Click to expand...
Click to collapse
Well said.
Entropy512 said:
You must not set a screen-off profile of powersave. The governor mechanics of powersave are not compatible with the "sleep of death" fix. Conservative with min=max=200 SHOULD be OK.
Click to expand...
Click to collapse
I wonder is there any tasks or situations that might require freq above 200 while screen off? For example, while playing music or using apps like CardioTrainer (which captures gps, draws track on the map as you exercise).
Also, mine is set to 200..500 conservative for screen-off and CPUSpy shows it spends most time at 200 anyway (deep sleep taken out of consideration).
-- vlad
vladm7 said:
I wonder is there any tasks or situations that might require freq above 200 while screen off? For example, while playing music or using apps like CardioTrainer (which captures gps, draws track on the map as you exercise).
Also, mine is set to 200..500 conservative for screen-off and CPUSpy shows it spends most time at 200 anyway (deep sleep taken out of consideration).
-- vlad
Click to expand...
Click to collapse
This is why I also have my screen-off limited to 500. Once in a while, the phone needs to do a little extra work, and it's better to ramp to 500, get stuff done, then go back to deepsleep. As I said min=max=200 SHOULD be OK, but personally, I wouldn't recommend it.
I would love if SetCPU allowed for different governor tuning depending on profile. e.g. make up/down threshold more battery-biased with screen-off than screen-on. (Slower polling rate, higher up/down thresholds.)
SetCPU root access problem
Hi -
GSII AT&T Stock ROM
Rooted
Superuser v3.0.6
SetCPU 2.2.4 purchased form Market (support the devs!)
Screenshot attached
Cannot obtain root access
I have installed / uninstalled SetCPU a few times
Superuser logs show several apps already allowed but no success or even attempt from SetCPU
I've rebooted. I'm out of ideas
Anyone have any ideas on how to fix?
Thanks in advance
IshouldntbeHere said:
Your kernel is nice but can't oc. If I try to go to 1.4 soft reboot city.
Sent from my super modded phone.
Click to expand...
Click to collapse
Pretty sure it's your phone cause mine OC's to 1.6 with no problem.
BigBopper said:
Hi -
GSII AT&T Stock ROM
Rooted
Superuser v3.0.6
SetCPU 2.2.4 purchased form Market (support the devs!)
Screenshot attached
Cannot obtain root access
I have installed / uninstalled SetCPU a few times
Superuser logs show several apps already allowed but no success or even attempt from SetCPU
I've rebooted. I'm out of ideas
Anyone have any ideas on how to fix?
Thanks in advance
Click to expand...
Click to collapse
Have you tried updating the su binary in Superuser? (Even if you have the app updated, the app itself needs to update the binary.)
Beyond that I have no ideas.
Entropy512 said:
Stock kernel or codeworkx's CWM kernel?
If either of those, your screen-off profile MUST include 800 MHz or you'll encounter a sleep of death. It's a common issue with Samsungs, and it is why SetCPU has such a bad reputation on Samsung CPUs, even though the SetCPU author has created kernel patches for nearly every Samsung Android device.
If my kernel or Cyanogenmod 7, screen-off profiles that do not include 800 MHz are OK, HOWEVER:
You must not set a screen-off profile of powersave. The governor mechanics of powersave are not compatible with the "sleep of death" fix. Conservative with min=max=200 SHOULD be OK.
The reason for this is that the CPU enters and exits suspend at 800 MHz (hardware limitation). If the regulator voltages aren't set high enough to support 800 MHz - the CPU crashes.
Click to expand...
Click to collapse
Ahh, that was my problem. I was using powersave. Do you (or anyone else) see there being a benefit to having a screen off profile?
In theory, a screen-off profile shouldn't help - in reality, it's a line of defense for cases where something goes nuts in the background.
Can somebody please explain the SetCPU governors to me? Normally I would use Smartass V2, but we only have the stock kernel.
The main governors I am curious about are mot_hotplug and hotplug. My phone seems to use a lot of battery when these are enabled, even with underclocked minimum scaling values.
Last night I ran my phone on ondemand at 300 min -300max (screen off profile) and it didn't drop 10%, first increment on battery reading stock ROM). Today while in school, it dropped from about 80% - 20% (using the same profile but with mot_hotplug).
Do all of the other governors manage both processors and hotplug can not?
You might as well use hotplug m8
MattyOnXperiaX10 said:
You might as well use hotplug m8
Click to expand...
Click to collapse
Why? That doesn't make any sense based from the findings I posted.
I'm using mot-hotplug in a week I'll know
Was using ondemand but I read an article where it shows the descriptions. Apparently hotplug behaves very similarly to ondemand but has the capability to turn off the 2nd core if there isn't a lot of workload. I switched to hotplug and so far its shown a significant difference in battery life. However, it may be a placebo as well so i'll stick to it for a week or so and then compare.
*edit
heres a link with better explaination
http://icrontic.com/discussion/95140/android-cpu-governors-and-you-setcpu-system-tuner-tegrak
evonc said:
Was using ondemand but I read an article where it shows the descriptions. Apparently hotplug behaves very similarly to ondemand but has the capability to turn off the 2nd core if there isn't a lot of workload. I switched to hotplug and so far its shown a significant difference in battery life. However, it may be a placebo as well so i'll stick to it for a week or so and then compare.
*edit
heres a link with better explaination
http://icrontic.com/discussion/95140/android-cpu-governors-and-you-setcpu-system-tuner-tegrak
Click to expand...
Click to collapse
I use kholks custom CPU governor it seems to be a lot snappier and battery use is good.
There is info in the development forum on here about it and using it.
Sent from my XT910 using XDA
alright. ive been playing around and cant find some good governors for what i want.
for hardcore gaming, what governor have you found that works the best
for best batter saving, but still be able to watch videos, surf web, email and just general navigating without it being too slow.
which governors do you guys use for both of those? thanks
Quadrider10 said:
alright. ive been playing around and cant find some good governors for what i want.
for hardcore gaming, what governor have you found that works the best
for best batter saving, but still be able to watch videos, surf web, email and just general navigating without it being too slow.
which governors do you guys use for both of those? thanks
Click to expand...
Click to collapse
anyone?
Use the smartassV2 governor. It regulates the CPU frequency according to load (sorta like ondemand except it works better).
darkghost568 said:
Use the smartassV2 governor. It regulates the CPU frequency according to load (sorta like ondemand except it works better).
Click to expand...
Click to collapse
i tried and i liked it, but it like locked my cpu at 1.24ghz (thats the max i have it set to) and even if i changed it, it would lock to the max frequency????
Quadrider10 said:
i tried and i liked it, but it like locked my cpu at 1.24ghz (thats the max i have it set to) and even if i changed it, it would lock to the max frequency????
Click to expand...
Click to collapse
I'll have v1 of Funky kernel out soon if you want to try out wheatley.
I've been a fan of smartassV2 since the first time I used it on the Thunderbolt. It is as close to an ideal governor as I've ever used. SmartassV2, with a complete sysfs implementation, can be tweaked very nicely. It is a governor that you can really tune so that most of the time it's not running balls out, but it's not loafing along either, which is how a governor SHOULD function. (I like to see a nice bell curve peaking at an ideal frequency, and spiked way out at the bottom frequencies when I look at a bar chart of my time-in-state's.) From what I can tell, few if any devs tune their governors to their kernels. I'm thinking that's how we ended up with a dozen or so governors that are rather similar, yet rarely ideal.
Snuzzo said:
I'll have v1 of Funky kernel out soon if you want to try out wheatley.
Click to expand...
Click to collapse
Wheatley is epic.
Sent from my Rezound using Tapatalk 2
loonatik78 said:
I've been a fan of smartassV2 since the first time I used it on the Thunderbolt. It is as close to an ideal governor as I've ever used. SmartassV2, with a complete sysfs implementation, can be tweaked very nicely. It is a governor that you can really tune so that most of the time it's not running balls out, but it's not loafing along either, which is how a governor SHOULD function. (I like to see a nice bell curve peaking at an ideal frequency, and spiked way out at the bottom frequencies when I look at a bar chart of my time-in-state's.) From what I can tell, few if any devs tune their governors to their kernels. I'm thinking that's how we ended up with a dozen or so governors that are rather similar, yet rarely ideal.
Click to expand...
Click to collapse
Alright now my problem is that I set my CPU to 192mhz lowest and 1.24 max. And that's for normal use. I'm running smart ass2 Nd it's not licking my CPU at max anymore, but it keeps.moving the max to 1.51ghz.
any ideas on how to fix tht?
Quadrider10 said:
any ideas on how to fix tht?
Click to expand...
Click to collapse
No frills CPU in play store
Sent from my ADR6425LVW using Tapatalk 2
Quadrider10 said:
Alright now my problem is that I set my CPU to 192mhz lowest and 1.24 max. And that's for normal use. I'm running smart ass2 Nd it's not licking my CPU at max anymore, but it keeps.moving the max to 1.51ghz.
Click to expand...
Click to collapse
Quadrider10 said:
any ideas on how to fix tht?
Click to expand...
Click to collapse
Yeah. Don't use DSB's kernel. I spent DAYS trying to figure out what his kernel is trying to do as far as governors. I'm not going to talk smack about the guy's work, but I will tell you what I know.
I doesn't appear any of the governors have been tweaked for his kernel. It looks like code was just tossed in there and left however someone else wrote it. For instance, smartassV2 has a sleep_wakup_freq of .998GHz, which is much slower than it should be. It SHOULD be near or equal to scaling_max_freq. Likewise, the max_cpu_load (which determines when the cpu should scale up) is 70, a fairly aggressive number, while the awake_ideal_freq and sleep_ideal_freq are pointlessly high. If I had to guess, these look like parameters for a Snapdragon S1 SoC, not the dual core S3 the Rezound has. No matter what governor you choose, it's only active on "cpu0". "cpu1" runs ondemand no matter what. The reason you have trouble making settings for the governor stick is because the sysfs location disappears and reappears for no obvious reason. It appears when things pop in and out (presumably when cpu1 goes on and off line), things are reset.
Cold hard reality is this: You're NEVER going to optimize any kernel out there to it's fullest potential. Either the options aren't there to tweak, or they behave in inexplicable ways. I can't tell you why DSB's kernel (not to single out a dev or his work, but I'm certain that's the kernel you're talking about) does what it does, but it's so far divorced from optimized on such basic levels you're better off not wasting your time.
As an aside:
After getting a rough feel for what some of these kernels are doing, I'm not at all surprised some kernels have had significant heat and battery drain issues. There are things that simply do not work right or work consistently. The devs shouldn't be blamed for this. These are probably the issues they're trying to work around that they inherited from the sources they're starting from and what makes tweaking them so difficult.
I acutely got everything to work. I'm just trying to overclock the GPU.