Hey guys. I'm looking for an app that is similar to SetCPU, but I can set my CPU overclock/underclock settings specifically for different applications. Meaning, I could have my Mantano Reader always at 300MHz but have Modern Combat 3 always at 1300MHz.
Anyone know of how to do this? I'm trying to maximize my battery. I'm on CM7.2 (Mirage Kang) and I have V6 but I'm still seeing some depressing battery loss just browsing with Wi-Fi on.
That's what your governor is for, it up clocks and/or down clocks the CPU according to what type of task is being performed.
joenathane said:
That's what your governor is for, it up clocks and/or down clocks the CPU according to what type of task is being performed.
Click to expand...
Click to collapse
Ah, I see. I just got my Nook Color around a week ago and I've installed Mirage Kang so I am extremely new to all this.
Could you point me in the right direction? What app for this would you suggest, SetCPU or something like Tasker?
Its under cyanogen mod settings in the settings menu.
Setcpu won't work with CM7.
gallahad2000 said:
Its under cyanogen mod settings in the settings menu.
Setcpu won't work with CM7.
Click to expand...
Click to collapse
I know of those settings (along with Nook Tweaks). What I was looking for was setting specific CPU settings for different apps. Like,
Mantano Reader : Always 300MHz
Andy-83 Calculator : Always 300MHz
Modern Combat 3 : Always 1300MHz
etc, etc, etc.
Specific settings for each app, not just generalized overclock/underclock settings for all apps.
(I hope I am explaining this well enough.)
I think you can set up rules such as those with Tasker.
tjw345 said:
I know of those settings (along with Nook Tweaks). What I was looking for was setting specific CPU settings for different apps. Like,
Mantano Reader : Always 300MHz
Andy-83 Calculator : Always 300MHz
Modern Combat 3 : Always 1300MHz
etc, etc, etc.
Specific settings for each app, not just generalized overclock/underclock settings for all apps.
(I hope I am explaining this well enough.)
Click to expand...
Click to collapse
There is no need to set it for each app. Just set it to on demand and the governor will automatically adjust the clock speed as it is needed.
Sent from space
Related
I'm getting used to my NC - and tweaking performance to get the best bang for the buck with this thing.
I'm running CM7 - and Dhalinger's, OC kernal clocked @ 1100mhz max - On Demand with very good performance. I started with Conservative - but web browsing is much better with On Demand setting.
Performance < particularly on Web > is much better than standard 800 mhz setting. But the device gets much warmer with Overclock around speaker -- and -- the battery drop is quite a bit faster with the overclock. Is this something I should concern myself with - re: the life of the device. I know with PC's you use aftermarket coolers for overclock - not so sure about Android devices and heat.
Is there a way to tweak the CPU overclock settings using a standalone app - like SETCPU to maintain better performance - while allowing your device to keep it's battery life maximized as much as possible.
Right now, I'm limited to Amazon App store - so not looking at Dhalinger's ( sorry if I got spelling wrong ) app from Android Market. But Would consider SETCPU if it's something that will help out.
The things that I use that seem to work the processor the most - seems to be EZpdf - with scaling / web use / and any games I've played. Kindle not so much. I don't do much video watching right now.
Is SETCPU worth a buy - and what should I expect from it.
Thanks
I'm pretty sure your supposed to set overclock within the CM7 settings menu. SETCPU should not be used. As far as browsing goes try Opera mobile. Much faster than any of the others I've tried.
yeah the other poster was right, donot use secpu with cm7 just goto settings, cyanogenmod settings, performance then set it from there
Hi,
at once, my english is very bad.
I have a problem with the Elelinux-7.1.0-RC1-Hero-v3.0.
The Status bar is very laggy and the launcher pro app drawer too :'( What can i Do.? thanks.!
wipe and clear everything, flash again!
Tried to overclock? I've used this app https://market.android.com/details?id=com.jrummy.droidx.overclock&feature=search_result and set the CPU to min 264 / max 672 governor: smartass for profile: screen on.
Be careful with overclocking, as with a computer electronic components doesn't like it
Don't use separate app to overclock Ele Rom. Go to Settings - Cyanogenmod Settings - Performance and adjust CPU clock there. Do it incrementally, though, for safety. I'm running 164/710 quite happily.
I should add: Smartass governor. Seems the cleverest, therefore saving a little battery...
flyxer said:
Hi,
at once, my english is very bad.
I have a problem with the Elelinux-7.1.0-RC1-Hero-v3.0.
The Status bar is very laggy and the launcher pro app drawer too :'( What can i Do.? thanks.!
Click to expand...
Click to collapse
For information v3.1 (based on Android 2.3.5) has been released, maybe it will fix your problem
Update to Eli's latest release and overclock is your best bet. I have my processor clocked at 264/748 SmartAss at the minute and it runs smooth as very smooth.
Also, as a note, I use SetCPU and have no problems.
Is there an app that will let you overclock depending on the app?
I think i've tried most of the popular progs, but they seem to be global overclocks
Right you are. Most programs use global overclocks, like SetCPU, but it allows you to only set profile parameters to certain items like Battery, Screen, etc.
xdadooder said:
Is there an app that will let you overclock depending on the app?
Click to expand...
Click to collapse
If you have root and a kernel that support it, you can effect this with Tasker - I bump the speed up and change governors when I stream audio on my little Aria to prevent choppy playback, overwise I run underclocked for better battery life.
Im having the same issue with every launcher that Ive tried based on 4.0+, terrible, terrible stability.
Some days I will have no issues, but more often then the launcher will frezee up, and sometimes FC. Usually after after I force stop the app from settings, the problems continues soon there after. This has been happening on the stock launcher, Nova launcher, Trebuchet and Apex launcher, but never on Go launcher or ADW Ex. I thought it may be the widgets I use, but removal of the all my widgets doesnt change a thing.
Is anyone else having similar issues or know of a fix?
Have yet to have my first launcher crash... 3 screens with various widgets. Stable as hell here.
SteveCheeseman said:
Im having the same issue with every launcher that Ive tried based on 4.0+, terrible, terrible stability.
Some days I will have no issues, but more often then the launcher will frezee up, and sometimes FC. Usually after after I force stop the app from settings, the problems continues soon there after. This has been happening on the stock launcher, Nova launcher, Trebuchet and Apex launcher, but never on Go launcher or ADW Ex. I thought it may be the widgets I use, but removal of the all my widgets doesnt change a thing.
Is anyone else having similar issues or know of a fix?
Click to expand...
Click to collapse
Thats quite strange - I haven't come across any prime that shows this symptom.
Have you done any customisation or removed any system apps?
Is "Force GPU Rendering" turned on? (in settings > developer options)
Is the CPU scheduler set to CFQ ? (you can check it with antutu cpu free version)
You may want to do a fresh install of the 11.1 firmware and see if it fixes your issue.
If it doesn't try installing the ATP tweak from development thread and switch between different scheduler to see if it fixes the issue. (noop is the most stable).
Hope you resolve this issue and enjoy your prime.
Don't have any issues w/ ADW except for scrolling widgets.
a Mandroid said:
Thats quite strange - I haven't come across any prime that shows this symptom.
Have you done any customisation or removed any system apps?
Is "Force GPU Rendering" turned on? (in settings > developer options)
Is the CPU scheduler set to CFQ ? (you can check it with antutu cpu free version)
You may want to do a fresh install of the 11.1 firmware and see if it fixes your issue.
If it doesn't try installing the ATP tweak from development thread and switch between different scheduler to see if it fixes the issue. (noop is the most stable).
Hope you resolve this issue and enjoy your prime.
Click to expand...
Click to collapse
Changing the I/O scheduler to CFQ is not needed. My prime stock launcher is very stable on stock noop I/O scheduler. That CFQ mode doesn't make as much a difference as some make it to seem. I've tried them all in ATP tweaks. Stock noop does the best for "Me".
OK..edit..nvm...I thought you was saying to put it on CFQ. You right, noop is the most stable. Which is the stock, out the box method, noop.
a Mandroid said:
Thats quite strange - I haven't come across any prime that shows this symptom.
Have you done any customisation or removed any system apps?
Is "Force GPU Rendering" turned on? (in settings > developer options)
Is the CPU scheduler set to CFQ ? (you can check it with antutu cpu free version)
You may want to do a fresh install of the 11.1 firmware and see if it fixes your issue.
If it doesn't try installing the ATP tweak from development thread and switch between different scheduler to see if it fixes the issue. (noop is the most stable).
Hope you resolve this issue and enjoy your prime.
Click to expand...
Click to collapse
I am currently using ATP tweak with my scheduler set to cfq, but I did have the issue before on noop. I havent removed/modified any system apps. Only thing Ive done with system apps is install in the launchers as such. and yes i do have force gpu rendering
Had the same Problem
My Launcher also crashed very frequently, in the end it was nearly unusable. But after a factory reset everything is fine now and it seems to be fixed. My Prime was rooted but I never messed with any Schedulers or anything else!
So far the Stock Launcher never crashed and was never unresponsive! I think the HC to ICS upgrade somehow messed it up.
SteveCheeseman said:
I am currently using ATP tweak with my scheduler set to cfq, but I did have the issue before on noop. I havent removed/modified any system apps. Only thing Ive done with system apps is install in the launchers as such. and yes i do have force gpu rendering
Click to expand...
Click to collapse
Ehm, I actually think force gpu rendering should be turned off...
changing force gpu rendering doesnt seem to change anything, so a factory reset it lookin to be my best shot.. i was hoping i didnt have to do that though
haven't had a single hiccup with spb shell, and it seems like it would be pretty taxing on the cpu/gpu. I think you're going to have to just bite the bullet and factory reset.
Force GPU Rendering yields mixed results for some. In some apps you get better performance, and some apps become unstable (e.g. random crash or start showing random drawing artificats) - as they were not designed to work with GPU rendering.
Any apps targeted for Android ICS will have GPU turned on by default, regardless of this setting. As app developers update their apps for Android 4.0, that option should not be needed anymore. Most games use GPU regardless of this setting.
Also note that, GPU rendering can have adverse affect on memory and battery usage. GPU consumes way more memory than CPU for certain types of operation, that is why Android has disabled GPU rendering for the different parts of launcher (e.g. System bar) as it would need to wake the GPU each time and it will use more power and memory.
So I highly recommend turning it off for consistency and reliability - and wait for app developers to update their apps for ICS. That option is really meant for developers to test their apps. Forcing Android to use GPU rendering for everything may produce unpredictable behavior and higher battery usage.
If you do change it, please do a cold boot (shutdown and then volume down+power button together to boot), and clear the data for launcher (Settings > Apps > All > Launcher) [Note you will lose your shortcuts and widget layouts]
Hi everyone,
This is the first time owning a Samsung device, so the pegasusq governor is a new thing to me, I read about what it actually is on a thread but I wanted to ask to fellow S3 owners what are they using for great battery life - performance ratio?
I'm running Omega 6.0, slipstreamed loads of crap that is not needed (from the "safe to remove" thread) with Apex Launcher. I'm only using 2 homescreens, dark wallpaper, etc, the typical works to try and improve battery life.
Now the thing is, with SetCPU I'm running the default pegasusq governor ranging from 200mhz -1400mhz. Is the pegasusq governor the right choice here? Isn't it basically a variant of the OnDemand governor but Samsung proprietary for quadcore CPUs? I also recall reading a mention of S3's freezing or not waking up when it's set from the lowest underclocking point (200mhz), is that right? I've been using this for a few hours and no problems yet, but just wanted to know what are everyone elses experiences and what's the best configuration that has worked individually for you!
Cheers! Hope I complied with the rules, I did do a search but didn't find anything of this nature apart from a few separate questions!
I use the same governor, 100Mhz - 1704Mhz. No issues. Works great.
Siyah kernel is using pegasusq so i think it is the best governer there is. if you're on stock kernel or lowest underclocking is 200mhz but in custom kernels you can use 100mhz.
I have set my SetCPU to 100mhz - 1200mhz and undervolting all 18-steps to -50mv. I seldom reboot my phone but not encounter any freeze on boot
You should try tweaks for improving the battery life and peformance. Like supercharger, zipalling , random build.prop tweaks.... Etc xD but yeah use the samsungs "for quad core"
Thank you for the prompt replies everyone!
I remember with my Desire the whole development community was pretty much "set in stone" if you will, so it was really easy to choose a kernel etc.
Is there a kernel that you recommend? Is anyone using a "Screen Off" profile without any problems? If so what's the range you have it set at? That's what I was mostly scared as I remember on my Desire the lockscreen or taking calls would lag quite a bit but obviously this is a different beast altogether!
I'm also using AutoKiller Memory with Extreme Settings and some tweaks applied as well.
I use Siyah clocked 100-1704 screen on. 100-300 screen off. No issues.
Sptz said:
Is there a kernel that you recommend? Is anyone using a "Screen Off" profile without any problems? If so what's the range you have it set at? That's what I was mostly scared as I remember on my Desire the lockscreen or taking calls would lag quite a bit but obviously this is a different beast altogether!
Click to expand...
Click to collapse
I set mine to 100-600 not having any issues, when reiveng notification/phone calls doesn't lag at all. Just don't use "power saving" option.
Sptz said:
I'm also using AutoKiller Memory with Extreme Settings and some tweaks applied as well.
Click to expand...
Click to collapse
3rd party apps don't to any good to battery life it only consumes more(for me) cause it's always running in your background which consumes memory and also battery life.
stock task manager is pretty good, been use it always. Closing all apps and clearing memory
bordikun said:
I set mine to 100-600 not having any issues, when reiveng notification/phone calls doesn't lag at all. Just don't use "power saving" option.
3rd party apps don't to any good to battery life it only consumes more(for me) cause it's always running in your background which consumes memory and also battery life.
stock task manager is pretty good, been use it always. Closing all apps and clearing memory
Click to expand...
Click to collapse
Nah, Autokiller isnt a task manager.
Basically, Android automatically kills empty processes (etc) at specified RAM levels. It does this anyway. But on High end RAM packed devices, these values are too low to be of any use as the phone will seldom hit that low a level of free RAM.
Autokiller simply adjusts these values to be more useful for high end devices.
Actually, you don't need autokiller to do this. You can do it in an init.d script although I've not tested this on the SGS3 as I haven't seen a need.
Here is an example I wrote for my Desire AOSP ROM:
Code:
#!/system/bin/sh
echo "8192,16384,19200,23040,25600,30720" > /sys/module/lowmemorykiller/parameters/minfree
Default SGS3 is:
Code:
8192, 10240, 12288, 14336, 16387, 25600
These are for:
Foreground App, Visible App, Secondary Server, Hidden App, Content Provider, Empty App