I stumbled upon these apps by dumb luck and decided to post this for anyone that doesn't know they exist. The dev is Chinese I am guessing based on a lot of his apps being in Chinese. He soes have these 3 apps in full English though and I am glad he does! For anyone that is looking for a SetCPU alternative, look no further. I will be the first to admit that I am not crazy about SetCPU. The app and I don't get along because of stability issues. CPU Master can do everything SetCPU can do but with better stability. I have been using it on both of my Vibrants. I have one Vibrant with the MIUI Rom (1.7.29) with the Bali 1.1.1 kernel and the other Vibrant is running CM7 Trigger Redux #17 with the Bali 1.1.1 kernel. I have had ZERO issues with the phones. Set on boot work flawlessly and overclocking is a breeze. The will give you every scaler that is included with the kernel you are running along with whatever overclock speed is set in the kernel. The Bali kernel supports up to 1.4Ghz and thats what the slider is maxed at. I loaded the Glitch kernel that supports 1.7Ghz overclock to see if the slider adjusts to that speed and as expected, I got 1.7. The only difference between the Free version and the paid version is that you can set and edit profiles in the paid version. For 1.99, its well worth the investment!
The Benchmark app ties directly into CPU Master. It tests everything that Quadrant Advanced (paid version) does PLUS it tests the speed of your SD cards! All of this and it's Free. If you are playing with overclocking speeds on your phone to see where the threshold is on your device, this benchmark will tell you. Through its rigorous testing you will see right away if your phones CPU can handle the speed you are testing. If you lock up during the test, its time to slow it down! On my MIUI Vibrant, I can only go up to 1.3Ghz and beyond that it freaks out. On my CM7 Trigger Vibrant, I can run 1.4Ghz with no problems.
Smart Profiles Free is a great app for people who spend part of their day in places where being quite is important. You can create all kinds of different profiles throughout your day to keep your phone running like the way YOU want it and not worry about turing on and off features. Just make your profiles and you are done! For example, from Monday to Friday I am at work 8 - 4:30 and I want my phone on Vibrate only. During those times I also want my WiFi on to use the company's internet and not my data plan and I also want my GPS off. As you can see you have A LOT of control of the various functions of your phone!
These apps are definitely worth the time to take a look at and try out. For any end user that wants even more control of their phone, they are certainly a fantastic addition!!
Free Apps:
CPU Master (Free): https://market.android.com/details?id=com.antutu.CpuMasterFree
AnTuTu Benchmark: https://market.android.com/details?id=com.antutu.ABenchMark
Smart Profiles (Free): https://market.android.com/details?id=com.antutu.phoneprofilefree
Paid App:
CPU Master for ROOT Users: https://market.android.com/details?id=com.antutu.CpuMaster
Excellent over / underclocking utility!
Yes, sure Antutu CPU Master is really a very good and powerful utility. I bought the pro version and it is worth the money. I am using it in my Samsung Infuse 4G, this allow the device to be underclocked till 100 MHz and overclock up to 1800 MHz, of course with the required Kernel and root access. It can be configured by the readymade profiles that can automatically change the clock settings based on conditions.
The widget which is just two column wide and 1 row height shows CPU Speed, Battery Status and Temperature.It has profiles, default, Charging, Screen off, In Call, Low battery, Temperature over-heat.
For stable clock setting set the minimum to 800 MHz as below this the device goes unresponsive particularly when the screen is off. I am using the range between 800 - 1800 and so far no issues, and it works great!
As mentioned, the benchmark, CPU setting and profile are great features of Antutu collection of software. Thanks to them!
Related
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.
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
I finally quit over-thinking the sucky battery drain on the new Miui. Originally, I thought using the Bali Kernel would solve this (it did in the older versions) but on the new version 9.23 Miui, the Bali 2.21 would not flash.
Well, went back to my old way of thinking and doing, and just changed the voltage settings on the current kernel
The result was dramatic, went from 10 hours (100% to 5%) on my phone to 15 hrs (100% to 35%) This makes it good enough for me to work all day use my phone ( Phone, camera, text, video, etc) without having to do an interim recharge.
For those who need more on how to, here is a link along with the app you can use:
http://forum.xda-developers.com/showthread.php?t=829731
There is another link inside this posting that explains voltage settings you should read it will help you get the gist of UV settings
I set to 1.2 = -75mv, 1.0 = -50mv 800 = -50mv and 400 =-25mv
This worked well for me but you need to check to make sure it is stable.
Go to the Apps store and D/L "stability test" app. Very useful.
If you want a different app for voltage settings take a look at setVsel app it will also work well.
Either way, an easy fix with a very acceptable outcome.
Hope this helps some of you...
you may want to do some stability testing, because if you're not on Glitch ML or LL, -75uv on 1.2 tends to be unstable, at least in my experience. You have more leeway on the low end than the high. For instance, -50uv at 1ghz and above is typical for most users, but for 800 and below you can easily go to -100uv, or even -150uv or -200uv for 200mhz and 100mhz.
kaintfm said:
you may want to do some stability testing, because if you're not on Glitch ML or LL, -75uv on 1.2 tends to be unstable, at least in my experience. You have more leeway on the low end than the high. For instance, -50uv at 1ghz and above is typical for most users, but for 800 and below you can easily go to -100uv, or even -150uv or -200uv for 200mhz and 100mhz.
Click to expand...
Click to collapse
Not Raining at all Like I said I used what worked for me, phones are all different and in my case my phone is a business tool so my approach has to more conservative and this works perfectly as configured for this phone.
I agree it does not resolve some of the bigger issues that Stockish Kernels possess, but under-volting did resolve the extreme battery drain I was experiencing.
I would prefer using Bali kernel by DrHonk but the new 9.23 Miui build had a few things added to it which will require a change of code and a re-syncing of the revised Bali kernel. DrHonk is aware and is working on this already. Until then, this fix will suffice until there is a update kernel release
BTW, thank you for the lower setting recommendations, I ll play around with that on the weekend.
Just updated the settings in my signature after a bit more testing with the Glitch Medium Leak (ML) Kernel. Was a little surprised that the settings were stable, but after 12hrs, they are rock solid, and battery life is noticeably better.
Did the same thing for my Samsung Fascinate (wifi only, as a poor-man's iPad) and while I couldn't get the settings above 1000mhz stable, the 1000mhz and under settings I used on my Vibrant were stable on the Fascinate as well.
Did you keep the other UV settings for example like 1.3 = -0mv or did you disable them (in SetCPU this is done by unchecking them)?
Hello there, I'm here to ask how some people overclock their xperia x10 so high example to 1190 mhz, my one is instantly booting when i switch to that frequency, how do they do it ? Im on jb rom by scritch 007 and jb ferakernel . Any advices ?
loockzye said:
Hello there, I'm here to ask how some people overclock their xperia x10 so high example to 1190 mhz, my one is instantly booting when i switch to that frequency, how do they do it ? Im on jb rom by scritch 007 and jb ferakernel . Any advices ?
Click to expand...
Click to collapse
To start with, no two XPERIA X10i are the same when it comes to the silicon in them.
The odd one or two may be able to sustain 1128MHz for benchmarking, but highly unlikely to be able to sustain that frequency for an extended time with a 'standard' load of user installed apps.
The XPERIA X10i is spec'd to be run stable and conservatively at 998MHz and there was no consideration for any frequency changes above that when designed.
However that does not stop most of us attempting to find the limits.
I tend to favour 1113MHz for my max daily frequency using SmartAssv2 governor, others may select something different.
I use SetCPU to change CPU frequencies, others prefer AnTuTu cpu master or some other overclocking application.
I use Link2SD on a secondary partition with a 32GB SanDisk UHS-I SDcard which gets away from the slow read/write of internal data storage.
build.prop 'tweaking' for optimisation goes a long way too.
The smart money is not overclocking, but on how low you can maintain the CPU (and thus battery life) when the screen is off and still be able to come out of deep sleep without 'hanging' the phone.
I have a screen-off CPU profile clocked at 576MHz-192MHz using SmartAssv2 to do that (work in progress).
Limiting applications that wake your phone when the screen is off it also a bonus.
CPU Governors and I/O scheduler information is a good start to understand what the CPU is attempting to do with different settings.
I have installed and run scritch007 CM10 JB ROM v5.0 (think it was at the time) with Amin Kernel and I seem to remember 1190Mhz was the raged edge of stability with AnTuTu v3 on my phone, so it doesn't surprise me a phone may not be able to clock at that speed using a CM10 JB ROM. See my AnTuTu v3 benchmark below used SmartAssV2 and noop I/O scheduler.
One should consider with the JB ROMs, the phone is doing a lot more (albeit a lot smarter) with the same amount of HW resources and even if you set the clock at 1190MHz and benchmark it, even before installing your own apps, there is still a lot of processes all completing for resources.
To get a better idea of the abilities of your phone, you may want to installed generic GB 2.3.3 and root it with an Overclocked Kernel to see if high clock rates of 1190MHz+ can be maintained without crashing the phone (WLOD - White light of death).
I can set 1128MHz on my phone without crashing it, but it always crashes on AnTuTu benchmark test at that frequency which is only about bragging rights at the end of the day anyway. I can't do anything constructive at these clock rates.
Installing JB ROMs and Kernels under rapid development with their own quirks on an X10i is probably not the most ideal why to gauge the stability of your phone when overclocked.
At the end of the day, it's more likely just luck of the draw if an XPERIA X10i can maintain 1190MHz+ clock frequencies and I'd say that 1190MHz+ is the exception and not the rule.
Dr Goodvibes said:
To start with, no two XPERIA X10i are the same when it comes to the silicon in them.
The odd one or two may be able to sustain 1128MHz for benchmarking, but highly unlikely to be able to sustain that frequency for an extended time with a 'standard' load of user installed apps.
The XPERIA X10i is spec'd to be run stable and conservatively at 998MHz and there was no consideration for any frequency changes above that when designed.
However that does not stop most of us attempting to find the limits.
I tend to favour 1113MHz for my max daily frequency using SmartAssv2 governor, others may select something different.
I use SetCPU to change CPU frequencies, others prefer AnTuTu cpu master or some other overclocking application.
I use Link2SD on a secondary partition with a 32GB SanDisk UHS-I SDcard which gets away from the slow read/write of internal data storage.
build.prop 'tweaking' for optimisation goes a long way too.
The smart money is not overclocking, but on how low you can maintain the CPU (and thus battery life) when the screen is off and still be able to come out of deep sleep without 'hanging' the phone.
I have a screen-off CPU profile clocked at 576MHz-192MHz using SmartAssv2 to do that (work in progress).
Limiting applications that wake your phone when the screen is off it also a bonus.
CPU Governors and I/O scheduler information is a good start to understand what the CPU is attempting to do with different settings.
I have installed and run scritch007 CM10 JB ROM v5.0 (think it was at the time) with Amin Kernel and I seem to remember 1190Mhz was the raged edge of stability with AnTuTu v3 on my phone, so it doesn't surprise me a phone may not be able to clock at that speed using a CM10 JB ROM. See my AnTuTu v3 benchmark below used SmartAssV2 and noop I/O scheduler.
One should consider with the JB ROMs, the phone is doing a lot more (albeit a lot smarter) with the same amount of HW resources and even if you set the clock at 1190MHz and benchmark it, even before installing your own apps, there is still a lot of processes all completing for resources.
To get a better idea of the abilities of your phone, you may want to installed generic GB 2.3.3 and root it with an Overclocked Kernel to see if high clock rates of 1190MHz+ can be maintained without crashing the phone (WLOD - White light of death).
I can set 1128MHz on my phone without crashing it, but it always crashes on AnTuTu benchmark test at that frequency which is only about bragging rights at the end of the day anyway. I can't do anything constructive at these clock rates.
Installing JB ROMs and Kernels under rapid development with their own quirks on an X10i is probably not the most ideal why to gauge the stability of your phone when overclocked.
At the end of the day, it's more likely just luck of the draw if an XPERIA X10i can maintain 1190MHz+ clock frequencies and I'd say that 1190MHz+ is the exception and not the rule.
Click to expand...
Click to collapse
Thanks for your answer.
Hello. I have been running CyanogenMod 10.1-10.2 since I got my device back in July, everything has been working great. Bugfixes have been lovely and all that good stuff; however one thing continues to annoy me. I cannot underclock my device properly. Let's say I go into the normal CyanogenMod Performance settings. Then I put my CPU to something like 1024MHz, then I see how the results went over with PerfMon from Chainfire, it will underclock only on Core 0, the rest of the cores still run up to the standard limit, 1890MHz. The only way I can somewhat successfully underclock is by setting my CPU to 594MHz or lower, at which point it will disable all cores except Core 0.
This has been annoying me for a while, I am running the standard CyanogenMod kernel, and recently I tried the Elite Kernel. The only thing the Elite Kernel did was remove the ability to disable the other 3 cores when below 594MHz. (And add the ability to go up to 2.2GHz, but who wants to overclock the Galaxy S4 yet?)
It may be worth mentioning if I try to tweak individual core settings with Tasker, on Core 0 it will let me set a CPU frequency, then if I go in and try to set something on Core 1, it won't have any of the default values for anything, and I enter them manually, then it will give me some errors about not finding the governor I said and stuff like that.
Anyone who knows any way to fix this (Custom kernels, different ROMs (Only for curiosity, I would stick to CyanogenMod anyway), etc) would be greatly appreciated.
Anyone who questions my motives for underclocking, question away. I don't like how my battery life is next to junk when I'm not even touching my phone all day, and the GS4 hardly needs the CPU it has, so I plan to use Tasker to set up a bunch of power saving mechanisms.
I suppose I do have one other question. Will underclocking even benefit me if I can't modify the voltage settings? Are they modified automatically when you're running at lower frequencies? (You would hope so, considering it's kinda a mobile device with a power source that isn't infinite). But if it won't help me without lowering my voltage (and if it isn't modified automatically) is there any good way to do that with a Tasker based setup, so it can be switched instantly whenever I do something? For example, launching a music player. All 4 cores shoot up to 1890MHz (I know they eventually settle down to lower frequencies, but for example's sake), I would rather have it so when I launched the app, Tasker would come in and set my CPU to ~800MHz with only a single core. Everything might slightly lag, but it would work and I would potentially get better battery life while listening to music.
Also, I never tested this on TouchWiz, as I didn't stay on it for more than 30 minutes after I got my device.
I am running the latest CyanogenMod nightly in case it matters (20131002, and it'll be 20131003 tomorrow unless it breaks something)
Thanks in advance to anyone who can possibly help with this. I'm sorry if the post is unorganized, but I hope it's understandable.
[bump]
Forgive me for my ignorance since I'm on ME7 and unable to flash CM10.x yet, but couldn't you just try different governors instead? On my old phone I was using lulzactive and it gave me great battery life, and you could tweak all the values any way you want for more performance or battery life.
I also remember when I experimented with undervolting and much to my dismay it turns out it made my battery life WORSE because of all the error correcting it was doing.
I get at least a days worth of moderate/heavy use on mine and with how fast it charges I don't really care about battery life but I'm curious how much actual gain you'll get for your efforts