Related
I have just installed setcpu on my Nexus One. Does it have to be open all the time in order to work? Do I have to ignore it in TasKiller? Is it still underclock my CPU even if I kill it?
tasomaniac said:
I have just installed setcpu on my Nexus One. Does it have to be open all the time in order to work? Do I have to ignore it in TasKiller? Is it still underclock my CPU even if I kill it?
Click to expand...
Click to collapse
I ignore it because I use it ondemand, not for performance, I would advise you ignore it seeing it has to run in the background for profiles and for on demand.
As android builds are getting more and more closer to being daily builds, one of the standing issues that remains is battery life.
This thread is where posts concerning How to Save battery should go. NOT Questions, but suggestions. If your suggestion is one to look into, it will be added to the OP.
UPDATE: You can now use ALL GOVERNORS For the CPU! (Read more to find out how) --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
SetCPU
SetCPU, is an app more commonly used for over/under clocking devices.
This short tutorial will show you how you get the app,
get it running, and of course save battery!
*YOU NEED A ROOTFS.IMG THAT GRANTS YOU ROOT ACCESS!*
1. Get SetCPU
A. Download it from *HERE*. (The only XDA thread I could find for it)
OR
B. Support this great application and get it from the Android market by searching for SetCPU.
-----------------------------------------------------------------------------
2. Getting the App working
1. Once you have the application installed, launch it from your drawer and either grant it Root Permissions or it may auto-configure.
2. Hit Auto Detect Speeds.
3. It should show you the speeds your device it currently running at, now move over to [Profiles] and click Enable and if you want click on Notification.
-----------------------------------------------------------------------------
3. Make your profiles
1. Sleep Profile - 384 Max/245 Min- Interactive setting
(It may seem high, but this keeps it so that your device wakes up quickly)
2. Battery < 30
Max 614/460 Min- Interactive/Conservative Setting
*Try out the SetCPU Widget!*
If you have any personal settings that you think might be better than these please do post!
-----------------------------------------------------------------------------
UPDATE 9/15 ALL CPU Governors!
To use the modules use this kernel built from the GIT, and hit auto detect speeds on SetCPU again. Under the main tab choose Your preferred setting..
You can find what all the the kernels differ in in the further pages of this thread, I will update OP later.
-----------------------------------------------------------------------------
Advanced Tab
20000 Sampling Rate
30-50 Up Threshold (THIS IS THE KEY: This means when your CPU load hits 30%, it will scale up the mhz. If the phone still responds too slow for your taste, set this lower)
http://forum.xda-developers.com/showthread.php?t=777921
Check Set on Boot (And Apply)
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Turning off Background Services and Adjusting Brightness
Things like Bluetooth, WiFi, Sync, GPS, and excessive brightness can really kill your battery.
A quick way to manage these settings is to hold down to add a widget on your home screen and choose [Power Widget].
This stock widget allows you to quickly see the service's your using, and the farthest one to your right allows you to switch between four brightness settings.
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Using that new kernel link provided, you'll get a nice boost in standby time too! Enjoy!
Additional battery saving tips:
* Don't use a live wallpapers
* Turn off 3G connectivity (Eclair-based ROMS need apps like APNDroid to do so)
* Turn off Background-enabled data transfers in the Sync page.
the app screebl is a battery saver for whenever you have your screen on.
MOD EDIT:
Screebl Pro is a PAID FOR APP..
Link deleted and warning given please do not post warez in the future.
Mark.
Is that a Paid application from the Market? If so it is warez. (Big No-No)
Shatterv2 said:
Is that a Paid application from the Market? If so it is warez. (Big No-No)
Click to expand...
Click to collapse
no it's donation-ware. You can find SetCPU in the G1 device section of the XDA forums for free...
http://forum.xda-developers.com/showthread.php?t=505419
Can we have on our hd2 a folder with Android Sdk ? Like in a rooted one ?
aussiebum said:
no it's donation-ware. You can find SetCPU in the G1 device section of the XDA forums for free...
http://forum.xda-developers.com/showthread.php?t=505419
Click to expand...
Click to collapse
Yes that was already stated in the OP
Shatterv2 said:
*YOU NEED A ROOTFS.IMG THAT GRANTS YOU ROOT ACCESS!*
Click to expand...
Click to collapse
Can you post one?
Ultimaex said:
Can you post one?
Click to expand...
Click to collapse
read here: http://forum.xda-developers.com/showpost.php?p=7088391&postcount=4
Thanks for the tips!
Ultimaex said:
Can you post one?
Click to expand...
Click to collapse
Rooted RootFS.img files by michyprima can be found *HERE* in the Installation Instructions section.
Mark.
SetCPU forcecloses on me with dan's froyo without sense. Anybody get this combo to work for them? Also, I did replace the rootfs file.
Strange, try the new froyo build by Darkstone.
reocej said:
SetCPU forcecloses on me with dan's froyo without sense. Anybody get this combo to work for them? Also, I did replace the rootfs file.
Click to expand...
Click to collapse
Yeah, I'm using SetCPU 2.01 with Dan's v1 vanilla froyo fine. When set to use "ondemand" CPU Governor and Autodetect speeds, getting much better battery life - it's only dropping ~1% every hour now EDIT: when idle, of course
aussiebum said:
Yeah, I'm using SetCPU 2.01 with Dan's v1 vanilla froyo fine. When set to use "ondemand" CPU Governor and Autodetect speeds, getting much better battery life - it's only dropping ~1% every hour now EDIT: when idle, of course
Click to expand...
Click to collapse
Happy to help!
Next thing (when I get around to it) is probably to try out the Conservative CPU Governor module... that will correctly scale CPU power according to load (ie. 245mhz => 384, etc) instead of like On Demand, where it jumps from 245mhz => 998mhz => lower....
ATK
My favorite Ap Right now: Advanced Task Killer - you can find it on market for free. With this you can kill tasks who run in backround etc.
RuffRap said:
My favorite Ap Right now: Advanced Task Killer - you can find it on market for free. With this you can kill tasks who run in backround etc.
Click to expand...
Click to collapse
Use Taskiller. Red Icon in the market. Free App is the exact same as the paid one. Kills tasks as well but detects tasks that ATK cant. Includes features like End apps once screen turns off and kill all apps 10sec's after boot. Great App IMO.
I've found out that JuiceDefender does a good job as well. If you buy the extension (UltraDefender?) it also has a CPU governer module which regulates your CPU speed based on usage.
maseo said:
I've found out that JuiceDefender does a good job as well. If you buy the extension (UltraDefender?) it also has a CPU governer module which regulates your CPU speed based on usage.
Click to expand...
Click to collapse
No need to pay - as I mentioned before, the "conservative" cpu governor module that is freely available (do a search!) will do exactly what you mentioned when used with SetCPU.
Hey all,
Sorry if this has been answered/asked already, but is there a way you can prevent SetCPU from getting killed by AutoKiller? I have the autokill-profile in AutoKiller set to "Default", but the system assigns SetCPU an OOM value of 11-14, which is the highest value for getting killed (essentially regarding it as extremely non-important). How does one PERMANENTLY set SetCPU on the "Do-Not-Kill List"?
Thanks in advance.
PS: I'm running KaosFroyo v35-1 and so I can't uninstall Autokiller.
Short answer: No
Long answer: Noooooooooooooooooooooooooooooooo
Hungry Man said:
Short answer: No
Long answer: Noooooooooooooooooooooooooooooooo
Click to expand...
Click to collapse
Lol...funny stuff
As for OP you can uninstall autokiller if you want too...just look up how to remove apps through adb or terminal on phone.
Hungry Man said:
Short answer: No
Long answer: Noooooooooooooooooooooooooooooooo
Click to expand...
Click to collapse
why cant you just lower the oom value by clicking and holding setcpu under the processed tab and select lower oom value, it will drop it to -17, which practically means it is being ignored.
"Practically" is not what he asked for. What he asked for is a permanent solution.
tyler1524 said:
why cant you just lower the oom value by clicking and holding setcpu under the processed tab and select lower oom value, it will drop it to -17, which practically means it is being ignored.
Click to expand...
Click to collapse
That only works for about 3 minutes, until the system automatically increases the OOM value back to like 12 or 13.
I don't understand... even when I have it set to system default, after a while, it still kills it. So that means, even if I were to uninstall Autokiller, the SetCPU would still be killed after a while?
Doesnt matter if its killed. Its android, itll come right back
Nikolai2.1 said:
Doesnt matter if its killed. Its android, itll come right back
Click to expand...
Click to collapse
That's the problem. SetCPU doesn't.
Acrono said:
That's the problem. SetCPU doesn't.
Click to expand...
Click to collapse
I check my processes constanly and i dont see it going away. Maybe im wrong
Maybe Autokiller is correctly determining that SetCPU is consuming more power and Country cycles than its providing. I've certainly found that to be the case with Kaos Froyo
-------------------------------------
Sent via the XDA Tapatalk App
I'm joking about Autokiller's intuition but serious about the dubious benefits of SetCPU on an already overclocked ROM
-------------------------------------
Sent via the XDA Tapatalk App
Nikolai2.1 said:
I check my processes constanly and i dont see it going away. Maybe im wrong
Click to expand...
Click to collapse
It's always killed after 10-15 minutes, even on the default setting. If I set it to aggressive, immediately after it goes into the background, it's killed within a matter of seconds.
paulbonner said:
I'm joking about Autokiller's intuition but serious about the dubious benefits of SetCPU on an already overclocked ROM
Click to expand...
Click to collapse
KaosFroyo is already overclocked? I notice a huge performance gain when I enable SetCPU and OC it to 710mhz. If KaosFroyo is indeed overclocked already, then it must be set pretty low, or at least, very close to stock settings....
Acrono said:
KaosFroyo is already overclocked? I notice a huge performance gain when I enable SetCPU and OC it to 710mhz. If KaosFroyo is indeed overclocked already, then it must be set pretty low, or at least, very close to stock settings....
Click to expand...
Click to collapse
Ocd to 710 by default
Edit: I've had the best results ditching setcpu and using the collin_ph script, just btw
I see that setcpu is at a constant 2 ooms. Now im using Zen express but idk if that makes a difference. And im set to strict
The real and best answer I have for the first post (and what I do, and advise everyone I am around to do)
Stop using Autokiller.
Android does a great job killing processes.
Most users use 4-5 apps constantly throughout the day, and if the few most commonly used ones stay in memory more often than not, the phone is FASTER, as a result of calling up apps instead of having to completely relaunch them every time.
YES, using autokiller to adjust your memory settings can help if you are normally running process-intense apps in the background (like I sometimes run a VNC for work that will chew up some processor time if I just hit 'home' when I'm done instead of killing the task, or sometimes a small game that you figured was not in memory anymore, is still chewing up processor time).
BUT
That is what, and only what, I use a task killer for. I open up Free Advanced Task Manager, kill my background process that I don't want running, and move on with life.
9 days out of 10, I don't use a task killer, and I NEVER use auto killer.
If you want to keep your phone faster than not, use 'back' to get out of apps instead of pushing 'home'. Unless 'back' is mapped to something in the app (like for some apps), back will end the process rather than leave it running.
I could write ten pages on why to not use autokiller, but a lot of guys who are a lot smarter than me will swear by it. I just find it slowing down my phone by forcing me to re-launch things like Handcent SMS, my Web Browser, and Google Voice, when I'd rather have those things stay running in the background. They don't chew up much processor time just sitting in the 'background', and my phone is WAY faster if it takes 1 second to open up each app instead of 3-6 seconds (because autokiller made my phone already automatically kill the task).
Good luck with your decision, sir.
And if you're using xtrSense, you can just set up your GScript to overclock how you want (mine's at 806800), and if you're using Froyo ROMs, you can use the battery tweak. SetCPU isn't that useful for most of these ROMs, since the methods of overclocking by collin_ph's battery tweak and xtrSense's GScript are faster and more efficient, and don't require a background process like SetCPU to be running.
But that's just my opinion. I hope it helps.
I use System Panel to basically monitor my memory instead of just relying on Autokiller to manage them for me. I also found that the way I use my phone, similar to the way pkopelek mentions, a few select apps a day, my free memory stays fairly close to what it did with autokiller installed. Average around 40-60 and if I kill a few off, up to 90-100.
One thing I have noticed is that System Panel comes with a cpu scale and shows your clock speed. With no SetCPU installed my CPU will drop down to 245 and then bounce around and finally settling back to 245 then the cycle starts again. With Collins tweak I get the same response. However, with SetCPU installed my CPU will clock down to 245 and sit there until I touch the screen. I have to believe that SetCPU is doing something that collin's isn't. Now the only way I can get it to behave this way is if I change the advanced parameters.
just my 2 cents.....
When I used AutoKiller and SetCPU (I used both between May and August) before I started using xtrSENSE v4.x, I never had a problem with SetCPU quitting working under any ROM, including any Froyo that was out at the time.
I only mean that perhaps the problem isn't between SetCPU and AutoKiller. Maybe it is the ROM??? Just guessing here.
Nikolai2.1 said:
I see that setcpu is at a constant 2 ooms. Now im using Zen express but idk if that makes a difference. And im set to strict
Click to expand...
Click to collapse
I'm using this: http://forum.xda-developers.com/showthread.php?t=685594 and the value is ALWAYS above 9. I've never had it down that low except when I temporarily add it to the ignore list (it falls out after about 5 minutes).
I am using cm 6.1 nightly and would like to know how to tune my mobile for long battery life. Wish setcpu could look into my usage and suggest presets for long battery life or performance.
my main is: Min: 245, Max: 710
Screen off: Min: 245, Max: 352
even without the screen off profiles or anything i still get 1-2 days + depending on my usage, and since i like to play with my phone and abuse the wifi/3g it lasts like a day anyway.
With screen on, max 633, min 480. create a profile so when screen is off, max 352 & min 160.
Mine is atm at 10% battery and it's been on for 51h & 30m and in that time it's been awake for 9h & 38m.
When i'm home, wifi is always on.
Gps is only on when needed, and so is bluetooth.
A suggestion for setcpu, it can collect the settings from users and provide the average as an option. This will really help new users. Integration with cm parts will be kickass.
kevin2516 and fusk.
i like yours max and min settings, but what type of scalling u guys use?
ondemand
userspace
performance
interactive (how does it work? couldnt find it on setcpu site)
thanks!
Vecaly said:
kevin2516 and fusk.
i like yours max and min settings, but what type of scalling u guys use?
ondemand
userspace
performance
interactive (how does it work? couldnt find it on setcpu site)
thanks!
Click to expand...
Click to collapse
"couldnt find it on setcpu site"
Oh really? http://www.pokedev.com/setcpu/#7
nemuro said:
"couldnt find it on setcpu site"
Oh really? http://www.pokedev.com/setcpu/#7
Click to expand...
Click to collapse
yeah i saw it before, but i didnt find interactive.
interactive = conservative?
http://forum.cyanogenmod.com/topic/4434-froyo-kernels-by-slayher/
Look for the small text in the signature of the OP.
nemuro said:
http://forum.cyanogenmod.com/topic/4434-froyo-kernels-by-slayher/
Look for the small text in the signature of the OP.
Click to expand...
Click to collapse
thanks.
kept "ondemand".
By having different profiles, we end up changing the CPU frequency limits frequently. Could this harm the CPU? This question was asked elsewhere but am not able to track it (iirc, it was not answered)
I think it will harm CPU. i have been using few profiles for a week. Yesterday it froze for 6 times. . So yeah....
Sent from my HTC Wildfire using XDA App
Vecaly said:
kevin2516 and fusk.
i like yours max and min settings, but what type of scalling u guys use?
ondemand
userspace
performance
interactive (how does it work? couldnt find it on setcpu site)
thanks!
Click to expand...
Click to collapse
I use ondemand and i've set threshold at 90%
works for me.
hackworks said:
By having different profiles, we end up changing the CPU frequency limits frequently. Could this harm the CPU? This question was asked elsewhere but am not able to track it (iirc, it was not answered)
Click to expand...
Click to collapse
No it does not harm the cpu.
think of other cpu's like intel or amd, they also can be throttled either through the hardware or software, to lower power consumption when not used, and visa versa.
I just use the main profile, the phone tends to freeze when switching profiles so i removed all the ones i had.
Running 160-672mhz. Running fine and doesn't freeze anymore.
When i use a profile for screen off, it sometimes takes a second or two to switch cpu speeds. It's kind of annoying as if i don't wait for it to change to the main speed, it may freeze.
Anyone else experiencing this ?
As the title says. No governor, be it on-demand or performance, doesn't stay after a reboot. I've tried Adam, Perseus, issue persists on both of them! Is this because of this new 4.3? If I remember correctly this wasn't a problem on 4.2! I've tried with SetCPU, No Frills, nothing...I always used performance, now I can't set it and it bothers me very much....
Anyone?
Sent from my GT-I9500 using Tapatalk
Have you got more than one app actively trying to set the governor ? You've said you're using SetCPU, but make sure the rom (Performance Control for example) or kernel doesn't have an app that's also trying to set the governor on boot for example. If they are, disable those & then try with SetCPU.
MistahBungle said:
Have you got more than one app actively trying to set the governor ? You've said you're using SetCPU, but make sure the rom (Performance Control for example) or kernel doesn't have an app that's also trying to set the governor on boot for example. If they are, disable those & then try with SetCPU.
Click to expand...
Click to collapse
Well I have tried with either Adam or Perseus, and in that case S-Tweaks and Synapse are automatically installed respectively. And I don't see there's any setting under those apps to change Governor! So I am forced to use SetCPU, are you saying I should uninstall S-Tweaks or Synapse in order to get SetCPU working properly? Because there's no visible settings under S-Tweaks or Synapse to change governor but there could/must be a hidden setting there which changes Governor at each reboot! and probably conflicts with SetCPU?
Actually, first up, try clearing cache/data on SetCPU, reboot, apply settings you want, reboot & see if they stick.
Then try uninstalling those other apps which might be conflicting. Also, check in rom settings to see if you have anything like Performance Control which might be setting something at boot. Also check to see if you have an init.d folder/if there's any scripts lurking in there which might be causing problems.
MistahBungle said:
Actually, first up, try clearing cache/data on SetCPU, reboot, apply settings you want, reboot & see if they stick.
Then try uninstalling those other apps which might be conflicting. Also, check in rom settings to see if you have anything like Performance Control which might be setting something at boot. Also check to see if you have an init.d folder/if there's any scripts lurking in there which might be causing problems.
Click to expand...
Click to collapse
Nah, tried everything, no profile sticks, even master wiped the device with full stock ROM and kernel, nothing. It's not actually a reboot needed for the default governor/settings to take place, if I just turn the screen off and turn it back on after a minute or so the set governor by me doesn't stick.
I am quite sure this is how it is suppose to be, but whatever, I don't like it. The fluidity I have seen with performance, well nothing could beat it. Maybe the CPU architecture of i9500 is the thing to blame here. Damn...
That's really weird. Maybe try another app other than SetCPU (or a bunch of them) ? Some kernels have variables that can't be set by the user or you can set them but they immediately go back to whatever setting the dev who made the kernel wants them to be at (some individual governor settings like sampling rates/etc), but setting the actual governor shouldn't be one of those. If the governor is available in the kernel, you should be able to both set it 'on the fly' and set it on boot.
MistahBungle said:
That's really weird. Maybe try another app other than SetCPU (or a bunch of them) ? Some kernels have variables that can't be set by the user or you can set them but they immediately go back to whatever setting the dev who made the kernel wants them to be at (some individual governor settings like sampling rates/etc), but setting the actual governor shouldn't be one of those. If the governor is available in the kernel, you should be able to both set it 'on the fly' and set it on boot.
Click to expand...
Click to collapse
Nah, not really weird as I understand it now. CPU hits throttle temp at 1.6 GHz and automatically defaults out at a lower clock rate, in this case 800 MHz. That's just too bad for me anyway, I have never used anything besides performance, now I am forced to use something else! I wonder how come no one has mentioned this yet!