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
Related
Is there a good resource/thread for learning more about using SetCPU? I just flashed nerov3 and im wondering if it'd be beneficial to install it. Not sure if its neccesary or compatible... etc. How does one even know how much is safe to over and underclock?
Vibrant, NeroV3, JL5, Voodoo...
With having nero v3 installed, you can't OC it because we don't have vibrant's froyo source code yet but we do have I9000's. You could use one of those kernels to oc/uc. Nero is speedy w/ voodoo anyways so you don't REALLY need it, if u want to use setCPU to uc you can. Underclocking i would recommend min100 max800 set scaling to conservative, which will automatically clock cpu to compensate for usage. (Just my 2cents, listen or don't its your choice)
I would highly recommend SetCPU with Nero V3 or any Rom for that matter. I know for some, It is just personal preference. For me, I run my phone at 800mhz max and 200mhz min. Gives me awesome speed, with voodoo there isn't really any lag. I'm basically reiterating what ucantak3dis has said, So until there is an OC kernel. Which I'm not sure if som and/or viral have plans for. I would stick with what you've got in addition with SetCPU. You'll get great battery life out of it! Enjoy.
Thanks for the feedback guys. I installed it and im running at 200 min, 800 max (set on boot).
What exactly does that mean?
Also, I've read people talk about underclocking when the phone is asleep to save battery. Do I need to create a profile to do that?
Vibrant, NeroV3, JL5, Voodoo...
trunkstar1 said:
Thanks for the feedback guys. I installed it and im running at 200 min, 800 max (set on boot).
What exactly does that mean?
Also, I've read people talk about underclocking when the phone is asleep to save battery. Do I need to create a profile to do that?
Vibrant, NeroV3, JL5, Voodoo...
Click to expand...
Click to collapse
It means that those values are SET on boot of your device. Your phone will run anywhere between 200 mhz and 800 mhz and ramp up to a max of 800 mhz (conservatively) when necessary. Versus, Without SetCPU your phone would constantly be running at 1Ghz. You can create profiles for doing such things to save battery while the screen is locked, I have had issues with my phone NOT being able to wake though. So, try this at your own risk.
Personally, i wouldn't recommend having the set on boot checked because it caused problems w/ some ppl. I did that once and when i rebooted, it froze on the vibrant screen. idk if that's been fixed but just having setCPU set at the values you want is fine i think. Profiles aren't necessary unless your overclocking the cpu.
Hi everyone,
Like most people I've been trying to find that optimum balance between performance and battery life in my Aria. I'm running CM7.0.3 and the latest version of drowningchild's kernel. With that kernel I switched setCPU from ondemand to smartass, and I can already see the CPU spending most of it's time in either 400 or 480 MHz, but when playing a graphic intensive game it'll go up to 806 MHz and run great.
But, here's the problem. With things like less graphic intensive games, or playing videos, smartass doesn't want to scale up to a useful clock speed, and things get choppy. I switch back to ondemand and everything smoothes out again. I don't want to keep it in ondemand all the time though, because then it's spending half the time in 806 MHz and eating up battery unnecessarily.
So, is there a better governor option for me? Or maybe a way to "whitelist" apps within setCPU, to designate apps that always get the max clock speed?
tl;dr: smartass isn't that smart in certain situations. Is there a better way?
Check out the app "Tasker" in the market. It will allow you to reconfig the governors automatically based on a slew of complex conditions.
If you want smartass roll back to 7-5 of my kernel and it should be fixed as I tweaked it to jump around less in newer versions
I'm still messing around with the new kernel released & will add smartass very soon & hopefully optimized
drowningchild said:
If you want smartass roll back to 7-5 of my kernel and it should be fixed as I tweaked it to jump around less in newer versions
I'm still messing around with the new kernel released & will add smartass very soon & hopefully optimized
Click to expand...
Click to collapse
Hey yea you're right, I didn't notice you had a new kernel out. I'm running 7-5 still but I'll upgrade once smartass is working in the new version.
I've been using "conservative" setting. Although when it initial opens a resource intensive app, its stutters a little, and then compensates by clocking up. I haven't had an issue where a game didnt want to run smooth (also at 806mhz).
I run on demand at 320/768. This to me seems to be a very good combo. The 320 min makes a noticeable difference in responsiveness without much sacrifice to battery. I've found the Max cpu setting doesn't make too much of a difference in most situations.
Sent from my cm7 Aria.
I have mine set to On Demand - Min 200 - Max 800, ive noticed though the scaling only gives me the option of - conservative - On Demand - Performance, im wondering where the remaining Governors like Powersave,etc are?
He he, you are trapped by SetCPU now.
Anyway, if you select Powersave mode you have to manually reboot the device. So it is useless.
Do you think an additional software is needed to underclock I9100's CPU? And please don't get confused by them who claims they get huge battery improvement for this app. You will get the idea after using it anyway.
Regards.
Sent from GT-I9100
Having carried out some tests using SetCPU and then not using it on Cognition ROM i found battery life to be better when i was using it particularly if i had it set to On Demand - Min 200 - Max 800.
I cant see an option for other Governors but im sure ive seen them before in a previous version,or was it another similar app?
I thought SetCPU is just a program and governors come with kernels.
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.
Hi there to all!!! I've been flashing various Android Roms for a few yrs now & really enjoy trying out new custom roms etc... Now i have a weird problem, Most customs Roms I have tried for my S3 i9300 are great & most 4.3 Roms come with a Custom Kernel such as Beoffla, GoogyMax, devil kernel & so on.... Now the problem is when leaving the CPU at defualt governer & settings everything is fine eg: min 200 & max 1400 but games lag now & again, When setting the CPU min & Max settings to 1400MHz, the results are much better but not for long, The CPU always drops to 800MHz when gaming as i notice the lagg, I've noticed this same thing with just about every kernel & rom ive tried wether its set to 1400 or even overclocked to 1500 or 1600max, I've also tried every trick to make them settings stick , like trickster mod etc, none seem to work for long, its like another system service is interfering with the settings or so.....im pulling my hair out to figure out what this is, I just want the CPU min & max to stay firmly at 1400Mhz or 1500 etc....without changing at all!!!
Any help or suggestions would be really appreciated.... FlashJunkie83
Sent from my NeatRom'ed Galaxy S3
CPU/GPU can under-perform if they get too hot from playing resource-intensive games or apps. Maybe this is the issue.
~ RazorMC
RazorMC said:
CPU/GPU can under-perform if they get too hot from playing resource-intensive games or apps. Maybe this is the issue.
hey yea would make sense but when running rooted stock 4.1.2 with stock kernel, this doesnt happen at all, i can set performance governer in set cpu & it stays at 1400 Mhz throughout, also i would of thought a Cpu thats ment to run at 1400 would be fine to do so all the time as its ment to be able to... even with a little heat behind it... its still only doing what its ment to lol, i remember in the days of my s2, i could push the cpu to 1200mhz & it would happily stay there even tho it got hot lol, im really sure its a system thing that upsets the cpu frequency, other than that there must be a way to stop the cpu/gpu from under-performing with a little heat..... thanks for reply tho dude....
Sent from my NeatRom'ed S3 i-9300
Click to expand...
Click to collapse
@FlashJunkie83
- High temp will always cause freq throttling since this is how devices are designed. This over-rides whatever the max freq the cpu was designed to run on.
- try undervolting from the boefla config app (if you use the boefla kernel). I use -25mV with almost no difference to performance. Some users have gone on to -50mV but that gave me random freezes and massive lags sometimes.
- Test different governors. I mostly use the default pegasusq and it works well enough. Constantly high freq can affect the CPU in the long-term. So I use max freq of 800mhz and increase it to 1400mhz only when I play games.
- I'm not a fan of SetCPU. It's a great app but i find specific apps (like boeffla config) for kernels to be more precise.
- You can also try a different battery and borrow one from a friend to test it out. I had slight heating issues long ago and changing the battery reduced the heat for me somehow. It was not much, but it was enough for me to notice.
~ RazorMC
RazorMC said:
@FlashJunkie83
- High temp will always cause freq throttling since this is how devices are designed. This over-rides whatever the max freq the cpu was designed to run on.
- try undervolting from the boefla config app (if you use the boefla kernel). I use -25mV with almost no difference to performance. Some users have gone on to -50mV but that gave me random freezes and massive lags sometimes.
- Test different governors. I mostly use the default pegasusq and it works well enough. Constantly high freq can affect the CPU in the long-term. So I use max freq of 800mhz and increase it to 1400mhz only when I play games.
- I'm not a fan of SetCPU. It's a great app but i find specific apps (like boeffla config) for kernels to be more precise.
- You can also try a different battery and borrow one from a friend to test it out. I had slight heating issues long ago and changing the battery reduced the heat for me somehow. It was not much, but it was enough for me to notice.
~ RazorMC
Click to expand...
Click to collapse
thanks mate will give it a go
sent from my NeatRom'ed S3 i9300
finally fiqured it out, it seems that cynogenmod has a diffrent approach to thermal throttling as ive flashed CM10.2.0 Android 4.3.1 along with Boeffla 2.1 for CM & the issue seems to have gone completely, have been running a performance test on games for best part of the day at 1600MHz with 4 enabled cores & just going back to normal settings for normal daily use, & not 1 issue with throttling, so now im very happy with the smoothness in games although its gets warm, but most high performance CPU's do anyways,So ive come to the conclusion that thermal throttling must be handled more by sammy roms it seems, but got the result i wanted in the end, thanks for all replies tho guys
Sent from my blazing S3 i9300 now running CM10.2.0