Related
I was curious... does SetCpu work for this phone like Milestone Overclock? What's the difference, aside from SetCPU having more options?
They are both free (well SetCPU only free for XDA), but everyone uses milestone OC here and I'm wondering if there's a reason for that.
syrenz said:
I was curious... does SetCpu work for this phone like Milestone Overclock? What's the difference, aside from SetCPU having more options?
They are both free (well SetCPU only free for XDA), but everyone uses milestone OC here and I'm wondering if there's a reason for that.
Click to expand...
Click to collapse
There is difference between two applications. Milestone overclock actually overclocks the processor while setcpu doesn't. Setcpu just changes clock frequency of CPU ranging from minimum to maximum. It allows you to make user profiles depending on which frequency of processor will be controlled. It actually helps battery last battery longer. BTW setcpu is paid application
SetCPU is used for setting CPU parameters. Like the range of mhz your CPU works at. Also setting profiles (CPU mhz when the phone is charging, reach temperature, battery lower than... etc.). But it cannot be used for overcharging, that's why we use Milestone overclock...
Sent from my XT720 using XDA App
jackfrost3821 said:
There is difference between two applications. Milestone overclock actually overclocks the processor while setcpu doesn't. Setcpu just changes clock frequency of CPU ranging from minimum to maximum. It allows you to make user profiles depending on which frequency of processor will be controlled. It actually helps battery last battery longer. BTW setcpu is paid application
Click to expand...
Click to collapse
Setcpu is free for XDA members bud, find it here
how should i adjust my advanced settings? im overclocked at 850mhz
LibertyMonger said:
Setcpu is free for XDA members bud, find it here
Click to expand...
Click to collapse
Thank you I wasn't knowing it is free for xda members!
I personally think Setcpu creates glitches in phone routine. Say when I play music and turn off the display, after I turn it on it pauses music a bit. I uninstalled it, problem seems to be no more. Still I can't confirm if the bug was created because of setcpu plus the battery life is not increased exponentially with setcpu.
Thanks for the answers
jackfrost3821 said:
I personally think Setcpu creates glitches in phone routine. Say when I play music and turn off the display, after I turn it on it pauses music a bit. I uninstalled it, problem seems to be no more. Still I can't confirm if the bug was created because of setcpu plus the battery life is not increased exponentially with setcpu.
Click to expand...
Click to collapse
I think I agree, lol. Android has it's own built in "Setcpu" it's supposed to do a good job on it's own. I have been using it lately and not really sure it is much of an advantage. I'm gonna go a few days without I think and see. Same with battery calibration, I use 3 backup batteries so if it works it really can't work properly when switching batteries but they all always seem calibrated the same whether I use it or not.
SetCPU works with msoc but it is more of a parameter setting app. Imagine if you were oc to 1200 all the time. That would be foolish bc your processor would burn up that is to say if you battery stayed charged long enough to do it. Im set at 1100/74 but I don't need it like that all the time. When my screen is off, why do I need it that high. I do bc I listen to alot of online media, MLB, Jango, Pandora, and if the screen is on it makes temp go up. I do, you may not need it that high. SetCPU allows me to set that parameter to adjust the CPU down and underclock it if I need to. Also if my battery is too hot, I don't need it to be fast as lightning compounding heat, so I set it for a specific temp and it underclocks when I hit it. Here is a screen shots to show my settings.
LibertyMonger said:
I think I agree, lol. Android has it's own built in "Setcpu" it's supposed to do a good job on it's own. I have been using it lately and not really sure it is much of an advantage. I'm gonna go a few days without I think and see. Same with battery calibration, I use 3 backup batteries so if it works it really can't work properly when switching batteries but they all always seem calibrated the same whether I use it or not.
Click to expand...
Click to collapse
Exactly that is what I've tried, uninstalled SetCPU to see the battery performance. It was really unnoticeable the battery drain with and without Setcpu. I use Autokill Memory Optimizer which seems to be providing good results as well as performance enhancement.
Nah that pause has nothing to do with setcpu. I get that all the time.
Sent from my Milestone XT720 using XDA App
exist2resist said:
Nah that pause has nothing to do with setcpu. I get that all the time.
Sent from my Milestone XT720 using XDA App
Click to expand...
Click to collapse
Yes it has to do with SetCPU if your minimum frequency is less. In screen lock profile select min frequency to 550Mhz instead of 250Mhz. Music won't pause while waking up your device. It works!
jackfrost3821 said:
Yes it has to do with SetCPU if your minimum frequency is less. In screen lock profile select min frequency to 550Mhz instead of 250Mhz. Music won't pause while waking up your device. It works!
Click to expand...
Click to collapse
I guess you are correct.
But currently I removed the SetCPU. And I see much better performance now. I was min at 250MHz. Even the quadrant score is much better now.
Thanks for your insight
I remove setcpu and do a comparison too. I'm using CM 7.1.0 of fjfalcon and it lasts 1.5-2 days with minimal usage on setcpu. Now let's see if it's barely unnoticable.
but I think set cpu to 250mhz during the night when you don't use your phone may prolong battery life.
Woodrube said:
SetCPU works with msoc but it is more of a parameter setting app. Imagine if you were oc to 1200 all the time. That would be foolish bc your processor would burn up that is to say if you battery stayed charged long enough to do it. Im set at 1100/74 but I don't need it like that all the time. When my screen is off, why do I need it that high. I do bc I listen to alot of online media, MLB, Jango, Pandora, and if the screen is on it makes temp go up. I do, you may not need it that high. SetCPU allows me to set that parameter to adjust the CPU down and underclock it if I need to. Also if my battery is too hot, I don't need it to be fast as lightning compounding heat, so I set it for a specific temp and it underclocks when I hit it. Here is a screen shots to show my settings.
Click to expand...
Click to collapse
Dude! with those settings what is your battery life like?
my minimum is at 125mhz and max at 250mhz (when screen off) and I lose 30% over night! and it barely lasts 8hours D:
what ROM are you on?
Do you guys know how the smartass governor works?
As I understand solution for "998 MHz with screen on" bug is found: http://forum.xda-developers.com/showthread.php?t=1225411&page=17#post16944722
We need to replace only one governor.
I don't want to play with different ROMs and kernels and I'm looking for simplest solution.
Is it possible to compile it as a module ("ondemand_mod" for ex.) and add it to stock ROM?
Or any other (simple) way?
Wrong section ...
Sent from my X10i using Tapatalk
Why wrong Section, this is Development to get the CPU Governor working correctly
Wolfbreak said:
Why wrong Section, this is Development to get the CPU Governor working correctly
Click to expand...
Click to collapse
Exactly, this is the right section for such request.
However, I can't help but wonder: is this really a "problem"?
No offence to anyone, but I find that the phone is very snappy
when on max frequency... The big problem for me, would be if it
didn't go into Deep Sleep immediately after turning the screen off
and stayed at min frequency for an extended period.
When the screen is on (aka using the phone) I'd like it to be as FAST
as possible. That's the reason I use the minmax governor.
Anyway, again, I don't mean to argue with anyone, I am just
presenting my point of view.
My_Immortal said:
However, I can't help but wonder: is this really a "problem"?
No offence to anyone, but I find that the phone is very snappy
when on max frequency... The big problem for me, would be if it
didn't go into Deep Sleep immediately after turning the screen off
and stayed at min frequency for an extended period.
When the screen is on (aka using the phone) I'd like it to be as FAST
as possible. That's the reason I use the minmax governor.
Anyway, again, I don't mean to argue with anyone, I am just
presenting my point of view.
Click to expand...
Click to collapse
Yes, it's really problem.
Higher frequency - higher power consumption. Moreover - with higher frequency CPU used with higher voltage so consumption is even more higher. So at 998 MHz CPU eats about 5 times more battery than on 246MHz.
With properly tuned governor I don't feel any real lags or slowdowns.
And, when screen is on CPU load is usually is lower than 20% at full frequency. So I don't want to waste my battery.
As I see it's possible to compile and use governor as module.
Could someone compile it? And assemble as xRecovery package?
Or point me where to read about compiling for arm, where to get tools and so on...
Karlson2k said:
Yes, it's really problem.
Higher frequency - higher power consumption. Moreover - with higher frequency CPU used with higher voltage so consumption is even more higher. So at 998 MHz CPU eats about 5 times more battery than on 246MHz.
With properly tuned governor I don't feel any real lags or slowdowns.
And, when screen is on CPU load is usually is lower than 20% at full frequency. So I don't want to waste my battery.
Click to expand...
Click to collapse
The thing is, on 245 MHz, you can't get any kind of decent performance.
Try this: set the minimum and maximum CPU frequency with SetCPU to 245 and attempt to use the phone normally.
Also, you might be right about voltage, but if the CPU is forced to work on lower freqs when it actually needs higher, there's definitely stress and increased battery consumption.
My phone lasts for more than 24 hours and it's always at max frequency when the screen is on. No lag, no freezes, no drain.
I do agree that the ondemand governor might not function as expected but I fail to experience the actual problem. That might be just me though.
Xperia X10i via Tapatalk
My_Immortal said:
The thing is, on 245 MHz with high load, you can't get any kind of decent performance.
Try this: set the minimum and maximum CPU frequency with SetCPU to 245 and attempt to use the phone normally.
Also, you might be right about voltage, but if the CPU is forced to work on lower freqs when it actually needs higher, there's definitely stress and increased battery consumption.
My phone lasts for more than 24 hours and it's always at max frequency when the screen is on. No lag, no freezes, no drain.
I do agree that the ondemand governor might not function as expected but I fail to experience the actual problem. That might be just me though.
Click to expand...
Click to collapse
There is no need to work on 245MHz as proper governor rise frequency automatically when it's necessary.
And really no stress for CPU to work an low frequency at full load. Moreover - CPU will consume more power at 500Mhz with 45% load than at 250Mhz with 95% load.
Sometime I use phone for navigation - long time with screen on and very low load. In this scenario battery drains very fast.
And last one - I like to have everything working properly. In case that I'll really need high frequency all the time I'll use other governor. I just want to have a choice.
I need a simple solotion for this too..I use z kernel and I found that Thego2s kernel fixed this problem..I was going to flash that kernel but think that has a bug and stoucks on logo ..can some one sayas a simple way?
Yes, I think a lot of people would prefer to use just small and simple fixes rather than replacing the whole kernel with a lot of nice but (personally) unnecessary features.
I am waiting for developers to release a fix for this problam
What are the best settings to have you phone's CPU speed set at? I'm looking for both good performance and good battery. Also I am using the default overclocker, what is the best one? Thank you guys for your time.
Sent from my LG-VM670 using XDA Premium App
I use SMARTASS as my CPU speed governor and I set my CPU to 480-748 MHz, seems pretty stable for me.
Sent from my LG-VM670 using xda premium
thaunknownartist said:
What are the best settings to have you phone's CPU speed set at? I'm looking for both good performance and good battery. Also I am using the default overclocker, what is the best one? Thank you guys for your time.
Sent from my LG-VM670 using XDA Premium App
Click to expand...
Click to collapse
Overclocking values differ from phone to phone. Test it out with different values and use the one which is stable for you.
This was just discussed in the IHO technical-discussion thread, as a matter of fact.
My phone is stable for most stuff at 806 MHz, but sometimes the camera will cause a freeze/reboot. So I run at a 786 MHz max. Your phone will be different; this has to do with minute physical differences between individual chips.
The thing to keep in mind when overclocking is that the processor in our phone (unlike those of many other phones) does not make use of dynamic voltage scaling. There are only two voltage levels: a lower one if the phone is running at or below (or is it just below? correct me if I'm wrong, guys) 480 MHz, and a higher one if the phone is running above. So below 480 MHz, the system will give the processor a certain amount of voltage (period), and above, the processor will get a certain higher amount of voltage (period).
Because of that, the tests that have been done indicate that 806 MHz is the sweet spot for battery efficiency when the phone is in use--and the closer you get to 806, the better. Thus, I've had the following settings for quite some time:
786 MHz min
786 MHz max
Performance governor
which has treated me pretty well. On a day of light to moderate use, I'd end up with 65-75% battery left (occasionally more like 80%), depending on cell signal where I am et al. And it gives me probably the best performance I'm gonna get out of this phone.
However, I very recently decided to change the minimum to below that 480 MHz threshold and see what a lower voltage when idling would do for my battery life. My current settings are:
320 MHz min (may change to 480)
786 MHz max
Smart*** governor
There is actually a noticeable performance decrease when I first wake the phone up, so I may switch governors as well. In any case, I've had those settings for only one full day now, but for that one day the battery life was noticeably better. I'll post an update when I've had a few more days to test.
As always, it's difficult to quantify battery life in a reliable/rigorous manner (much less a universally applicable one), so YMMV.
Ive been running the "cm7-1.4highpro-test-rev3" kernel and it runs great. I've been bumping up my undervolting slowly, and im at -475 at 216 mhz, which (in theory) should be the undervolt clock speed that will save me most battery becasue i have phone set to go between 216 mhz and 312 mhz when screens off. Ive got both 216 and 312 mhz undervolted extremely heavily and i haven't seen ANY issues. The rest of clock speeds are at -100 or so, and if i push much further than that the phone locks up and does weird stuff. This would lead me to believe that the undervolting IS indeed working. But can the processor really run at -475 @216mhz and [email protected] without any side affects?? I haven't once had it get stuck in sleep mode with screen off or ANYTHING, so im a bit unsure if it is actually undervolting or not.. Myrt undervolt shows that my phone is undervolted to the specific settings i set within SetCpu. I also havent seen much, if any, difference with battery life. With 10 hours of idle time, straight idle screen off whole time, wifi, gps, mobile data, 4g, bluetooth, all that stuff off and after 10 hours my battery is down to 85%.
I limited uv clocks, so there is a low limit. One day ill add more low end clocks but it won't matter because the photon uses a separate clock for suspend. I knew people would try to uv to 500 with it set on boot and screw there phone up. So this way I didn't have thousands of user error related uv issues. Uv does works but its more for high end than low end. Low end uv causes sleep of death.
w0lf215 said:
Ive been running the "cm7-1.4highpro-test-rev3" kernel and it runs great. I've been bumping up my undervolting slowly, and im at -475 at 216 mhz, which (in theory) should be the undervolt clock speed that will save me most battery becasue i have phone set to go between 216 mhz and 312 mhz when screens off. Ive got both 216 and 312 mhz undervolted extremely heavily and i haven't seen ANY issues. The rest of clock speeds are at -100 or so, and if i push much further than that the phone locks up and does weird stuff. This would lead me to believe that the undervolting IS indeed working. But can the processor really run at -475 @216mhz and [email protected] without any side affects?? I haven't once had it get stuck in sleep mode with screen off or ANYTHING, so im a bit unsure if it is actually undervolting or not.. Myrt undervolt shows that my phone is undervolted to the specific settings i set within SetCpu. I also havent seen much, if any, difference with battery life. With 10 hours of idle time, straight idle screen off whole time, wifi, gps, mobile data, 4g, bluetooth, all that stuff off and after 10 hours my battery is down to 85%.
Click to expand...
Click to collapse
Sent from my MB855 using XDA App
haha ok I understand, just thought I was going crazy there for a bit, or had the most amazing tegra 2 known to man. is there a way to UV the suspend mode then or no? And is my battery life at idle about average or low considering the UV. do you have any kernels for CM7 that aren't limited for UV? Thanks for reply, and all your hard work on the photon!!
Sent from my MB855 using XDA App
Changing suspend voltage can only be done in source. I havnt played with it yet because i need to test it on a stable kernel that way i know any issues would come from it. As far as extra uv steps its planned after wifi fix. I wont add 500 new steps probably 2 steps at a time(-25 steps). Im also planning on changing my clock table(multiples of 216 only). I might make a half step 1.0 kernel underclocked to 108~192. It will be mem underclocked and gpu/avp underclocked. With lower voltage tables on everything. Default scheduling will be powersave. Which you can check out with cpu master right now. That kernel will also have a tweaked 2 core start/stop.
w0lf215 said:
haha ok I understand, just thought I was going crazy there for a bit, or had the most amazing tegra 2 known to man. is there a way to UV the suspend mode then or no? And is my battery life at idle about average or low considering the UV. do you have any kernels for CM7 that aren't limited for UV? Thanks for reply, and all your hard work on the photon!!
Sent from my MB855 using XDA App
Click to expand...
Click to collapse
Sent from my MB855 using XDA App
"That kernel will also have a tweaked 2 core start/stop. "
Holy ****!
That would be the best thing
All new ones this week have tweaked 2nd core
DethMetalz69 said:
"That kernel will also have a tweaked 2 core start/stop. "
Holy ****!
That would be the best thing
Click to expand...
Click to collapse
Sent from my MB855 using XDA App
Im building a battery version of top secret now
Sent from my MB855 using XDA App
has anyone else tried using setcpu with ics roms? does it actually do anything?? I'm trying now, and i set my lowest frequency to 192 and like max at 894...thing is I don't notice the phone being any slower... is it actually doing anything? it says it is.. system panel shows it maxing out at 894..but I'm still dropping battery like crazy lol clearly it doesn't help enough if it even works.
Sent from my ADR6425LVW using XDA App
Known bug with ics roms, will not work at all until source is released and we get someone to to build a kernel without HTC perflock built in
Sent from my aokpcb_tenderloin using xda premium
don't use any apps that control the CPU. that goes for frequency,governors,etc. it messes with perflock which causes the CPU to run at only the min/max frequency and no proper scaling. stick with this advice until custom ics kernels come
It works for me. Tell me I'm stupid if you want but my battery doesn't drain as fast with it. If I set CPU to 500mhz it runs slower so it does something. It does bounce around due to perflock. But it helps me
Sent from my ADR6425LVW using Tapatalk 2
Evocm7 said:
It works for me. Tell me I'm stupid if you want but my battery doesn't drain as fast with it. If I set CPU to 500mhz it runs slower so it does something. It does bounce around due to perflock. But it helps me
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Ehhh far to many times I'd have the phone go 1.5Ghz full blast non stop even with the screen off. Be at work and wonder why my leg was on fire.
Sent from my ADR6425LVW using XDA
It works great for me, and was just updated recently and fixed all the little minor problems and occasional crashes that I used to have.
None of the stock kernels should ever be govern with a CPU app. I have no idea why people say it only applies to ICS. In fact this applies to BOTH GB and ICS kernels. GB and ICS kernels have the same battery life on stock roms.
If the kernel does not allow you to disable perflock, it won't scale right, stock kernels cannot have it disabled. I say again, BOTH ICS and GB because people like to give out FALSE INFORMATION.
Sent from my ADR6425LVW using XDA
nosympathy said:
Ehhh far to many times I'd have the phone go 1.5Ghz full blast non stop even with the screen off. Be at work and wonder why my leg was on fire.
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
That has happened to me once. But not since last update. It does bounce around sometimes but never goes above the max I specify so I'm happy with it. Keeps temps down under heavy use as well even though temps aren't much of an issue with latest leak
Sent from my ADR6425LVW using Tapatalk 2
Works fine after the latest update on conservative governor, scales throughout the range given. Cleanrom 4.4 stock kernel.
richii0207 said:
I say again, BOTH ICS and GB because people like to give out FALSE INFORMATION.
Click to expand...
Click to collapse
exactly...
lol so people are saying it works, and people are saying it doesn't.
doesn't really answer my question lol
Sent from my ADR6425LVW using XDA App
Quadrant only shows my CPUas being single core . I'm on CleanRom Standard Edition 4.5. Wasn't sure if that had been addressed in a thread yet or not . So I wasn't sure where to address this, but this seemed like a good place . I took a screenshot of it .
Sent from my ADR6425LVW using xda premium
jayochs said:
lol so people are saying it works, and people are saying it doesn't.
doesn't really answer my question lol
Sent from my ADR6425LVW using XDA App
Click to expand...
Click to collapse
If it works its doing something, it works. It works on cleanrom ics pro 4.4 on conservative governor since the last update before that it wasn't working right for me it would jump to Max all the time now it scales right.
Kane5581 said:
If it works its doing something, it works. It works on cleanrom ics pro 4.4 on conservative governor since the last update before that it wasn't working right for me it would jump to Max all the time now it scales right.
Click to expand...
Click to collapse
i'm running cleanrom 4.5 right now. when i set to conservative, it jumps all over, but it still maxes ouat at 1512 often.
i just stopped touching it because i didn't feel like breaking anything lol but again, some people are saying due to perflock it won't work, while others say they have experience of it working. so confusing.
Perflock being the pain it is, I'm staying away from it right now.
When I had it installed, my battery life was complete fail.
Sent from my ADR6425LVW using Tapatalk 2
jayochs said:
lol so people are saying it works, and people are saying it doesn't.
doesn't really answer my question lol
Sent from my ADR6425LVW using XDA App
Click to expand...
Click to collapse
All you can do is try it. Worst case scenario your battery drains too fast. Then uninstall it. Why it helps some and not others, I don't know. It helped me get 16 hrs of battery life with 4hr screen time with 4g on stock battery (ics) yesterday. No way in hell I could get that without setcpu
Sent from my ADR6425LVW using Tapatalk 2
Well at the risk of posting terrible "FALSE INFORMATION!", I'll let you know my experience with setCPU so far and you can make your own decisions from there.
First, here's my current config:
Android 4.0.1, SebastianFM's 1.20 OC Kernel, CFQ IO scheduler, interactive or on-demand governor depending on situation (cpu profiles enabled).
Profiles enabled, listed lowest to highest priority:
bat <=100% -- min=384, max=1566, interactive, CFQ
bat < 90% -- min=384, max=1350, interactive, CFQ
bat < 75% -- min=192, max=1188, interactive, CFQ
bat < 50% -- min=192, max=1026, interactive, CFQ
temp > 105*F -- min=192, max864, interactive, CFQ
bat < 34% -- min=192, max=864, conservative, CFQ
bat < 25% -- min=192, max=648, conservative, CFQ
SCREEN OFF -- min=192, max=540, interactive, CFQ
temp > 120*F -- min=192, max=540, conservative, CFQ
bat < 15% -- min=192, max=540, conservative, CFQ
So, I realize Perflock is enabled, so frequencies do tend to jump around. However, when you set and enable profiles, setCPU does seem to control the frequencies still, even though you can watch the min/max frequencies move around.
I use the setCPU widget on my homescreen too. So lets assume for example my battery is between 90-100% charge, in which case my min=384 and my max=1566. With profiles enabled, I can watch my minimum frequency occasionally go as high as my max, or 1566. Generally, this happens when my phone is actually using the 1566 frequency at the present moment, which is indicated by the current frequency display on the widget. However, if my current CPU speed happens to be anywhere in between the range i selected, lets just say its at 864mhz currently. In this situation, my current frequency will show 864mhz, but my min frequency might also show 864mhz and my max might show 1188mhz, at that particular time.
OK so now my battery has depleted to 49%, and so my profile kicks in and sets the minimum frequency at 192 and the maximum frequency at 1026. In this case, I'll NEVER see a current CPU speed over 1026mhz. I might see both the minimum and maximum at 1026mhz for a period of time, or I may see the current frequency say 648mhz while the minimum is at 192mhz and the maximum reports 648mhz also.
The point is, YES, I can watch perflock doing its thing and changing my min/max frequencies around constantly. However, by simple observation I can confirm it does actually scale within my specified parameters.
There was a bug with setCPU up to about a month ago where it would occasionally crash and your CPU would just go to its normal default (384-1512mhz, deadline scheduler, on-demand governor), however the recent updates have fixed the crashes! SetCPU now continually runs without crashing, and when you use profiles, it DOES seem to scale exactly how you tell it to.
a.mcdear said:
Well at the risk of posting terrible "FALSE INFORMATION!", I'll let you know my experience with setCPU so far and you can make your own decisions from there.
First, here's my current config:
Android 4.0.1, SebastianFM's 1.20 OC Kernel, CFQ IO scheduler, interactive or on-demand governor depending on situation (cpu profiles enabled).
Profiles enabled, listed lowest to highest priority:
bat <=100% -- min=384, max=1566, interactive, CFQ
bat < 90% -- min=384, max=1350, interactive, CFQ
bat < 75% -- min=192, max=1188, interactive, CFQ
bat < 50% -- min=192, max=1026, interactive, CFQ
temp > 105*F -- min=192, max864, interactive, CFQ
bat < 34% -- min=192, max=864, conservative, CFQ
bat < 25% -- min=192, max=648, conservative, CFQ
SCREEN OFF -- min=192, max=540, interactive, CFQ
temp > 120*F -- min=192, max=540, conservative, CFQ
bat < 15% -- min=192, max=540, conservative, CFQ
So, I realize Perflock is enabled, so frequencies do tend to jump around. However, when you set and enable profiles, setCPU does seem to control the frequencies still, even though you can watch the min/max frequencies move around.
I use the setCPU widget on my homescreen too. So lets assume for example my battery is between 90-100% charge, in which case my min=384 and my max=1566. With profiles enabled, I can watch my minimum frequency occasionally go as high as my max, or 1566. Generally, this happens when my phone is actually using the 1566 frequency at the present moment, which is indicated by the current frequency display on the widget. However, if my current CPU speed happens to be anywhere in between the range i selected, lets just say its at 864mhz currently. In this situation, my current frequency will show 864mhz, but my min frequency might also show 864mhz and my max might show 1188mhz, at that particular time.
OK so now my battery has depleted to 49%, and so my profile kicks in and sets the minimum frequency at 192 and the maximum frequency at 1026. In this case, I'll NEVER see a current CPU speed over 1026mhz. I might see both the minimum and maximum at 1026mhz for a period of time, or I may see the current frequency say 648mhz while the minimum is at 192mhz and the maximum reports 648mhz also.
The point is, YES, I can watch perflock doing its thing and changing my min/max frequencies around constantly. However, by simple observation I can confirm it does actually scale within my specified parameters.
There was a bug with setCPU up to about a month ago where it would occasionally crash and your CPU would just go to its normal default (384-1512mhz, deadline scheduler, on-demand governor), however the recent updates have fixed the crashes! SetCPU now continually runs without crashing, and when you use profiles, it DOES seem to scale exactly how you tell it to.
Click to expand...
Click to collapse
awesome analysis. ...so what's your battery life like?
I've gottent it to work a couple of times, other times it seems to do nothing at all, and i have also had it almost burn a hole in my pocket due to heat. I would say dont try to OC for now and wait until we have something more stable as they have previously stated. To be honest its a hit or miss type of mod for now.
jayochs said:
awesome analysis. ...so what's your battery life like?
Click to expand...
Click to collapse
My battery life is pretty good. I'm very surprised by how little i actually notice the difference in responsiveness and performance as my CPU throttles lower as my battery drains throughout the day.. However, I will admit that the only reason I have it scaling so low like that was to match the same battery life that I was getting on totally de-sensed GB builds...