Related
If you are using one of the Over-Clocked Undervolted Kernels please uninstall set-cpu and observe your battery life for 3 days and compare it to what you got when you used set-cpu. Then report as to if it is better, worse, or the same.
Just compare to what how long your battery lasts with your normal usage. Please do not give replies like "I only used 30% in two days with normal use."
Just reply with either better, worse, or same. Because usage is relative and that is not the purpose of this.
I think that set-cpu is interfering with the built in govenor and its ability to scale the freq of the phone. I think that it is staying on what-ever freq you set in set-cpu and scaling properly and thus reducing the battery life, and making the undervolting useless.
IF YOU BELIEVE YOU HAVE BETTER BATTERY LIFE WITHOUT SETCPU, THEN GET LOGS WHILE IT IS RUNNING AND SEND THEM TO THE DEV.
I have also noticed lag on the home screen with setcpu, I started using Overclock Widget to detect the values and to diff freq screen off 245-576 and put the phone on sleep while charging so will stay cool. Battery life has been great so far! I'm using 2.6.33.4 [email protected] #1 about to upgrade to his newest 2.6.34...I think SetCpu has flaws!
Will let you know my results.
this thread may be of some help. im currently trying pershoots 5.12vfp release without setcpu at all.
i do, however, remember getting 37 hours with moderate use with setcpu and profiles set, but i cant remember which kernal it was exactly. i think it may have been IRs 4.29 release..
Just uninstalled SetCPU and I'm running Pershoot's newest 2.6.33.4 925 Kernel. I will report back my findings in a couple of days...
Been curious about this for a while, but does the Nexus automatically throttle CPU speed by itself when SetCPU is not installed?
paulk_ said:
Been curious about this for a while, but does the Nexus automatically throttle CPU speed by itself when SetCPU is not installed?
Click to expand...
Click to collapse
Nope, incredible and onwards only.
Did this Quite a bit ago... ran with and without for over a week and i have better battery life without setcpu
When you don't have setcpu, you're not running at 1113ghz..
persiansown said:
When you don't have setcpu, you're not running at 1113ghz..
Click to expand...
Click to collapse
Perhaps...However, Linpack is proportional (I think) to the device's performance. My little experiment was testing different frequency kernels and measuring that against Linpacl
998: 7.4
1.13: 8.2
1.19: 8.9
So it would appear that performance increases with each kernel which wouldn't be the case if SetCPU was required.
I have some reasons to believe that SetCPU would interfere with the actual design of the Nexus One. I mean after all, i'm sure it was programmed to manage itself. So why have another app that does the same thing, twice? Just a thought, but for one thing, my phone is definitely cooler when charging compared to having SetCPU with profiles.
dogiedogie said:
Nope, incredible and onwards only.
Click to expand...
Click to collapse
You mean that the Incredible features CPU throttling?
jlevy73 said:
Perhaps...However, Linpack is proportional (I think) to the device's performance. My little experiment was testing different frequency kernels and measuring that against Linpacl
998: 7.4
1.13: 8.2
1.19: 8.9
So it would appear that performance increases with each kernel which wouldn't be the case if SetCPU was required.
Click to expand...
Click to collapse
There are dozens of potential optimizations that can be done to improve performance without touching the cpu speed. Different kernels, especially if they're from different people, will have different flags set in the build and so will perform differently even at the same clock speed.
Casao said:
There are dozens of potential optimizations that can be done to improve performance without touching the cpu speed. Different kernels, especially if they're from different people, will have different flags set in the build and so will perform differently even at the same clock speed.
Click to expand...
Click to collapse
I completely agree however all the kernels I use are from the same person and the optimizations at the different clocks speeds are identical. Therefore the spread in my linpack scores indicate that setcpu is not required. At least, that's my theory
this and other threads have made me question why we need setcpu anyways. I have it running and its great but can't we just integrate what setcpu is doing from the get go instead of having an external app running a separate process?'seems a little inefficient to me. The reason I say this is that I noticed most people are using the same settings for set cpu.
anyways, I dunno how relevant all this is since froyo's just around the corner and that may alleviate some problems but bring more problems
Yeah, start bashing my app, knowing I was the one who came up with the ideas behind the 1113MHz/uv hack in the first place (in fact, I came up with the 21MB hack as well, so prominently displayed in the OP's kernel thread title). Thanks, nexus one community.
I can explain that setcpu does not run any code in the background if your profiles are disabled, I can explain how cpufreq works, I can explain what lengths I went to to optimize the profiles, and I can explain that the profiles are very passive (except sometimes on the Droid, but there's an option for tweaking that) but I probably won't bother. Grab 1.5.3a and use it, or don't use it. I don't care either way.
I think that set-cpu is interfering with the built in govenor and its ability to scale the freq of the phone. I think that it is staying on what-ever freq you set in set-cpu and scaling properly and thus reducing the battery life, and making the undervolting useless.
Click to expand...
Click to collapse
You obviously do not know how cpufreq works. Setcpu does not touch the values after it sets a profile. Profiles actually run code only when it receives broadcast intents. It sets the max and min bounds and the governor if necessary within a fraction of a second. The service is completely idle otherwise. It can't "interfere with the built in governor." Okay, then. What is your big theory? What exactly is setcpu doing wrong?
SetCPU is advantageous because it allows you to tweak speeds on the fly and based on certain conditions. You can have solely kernel based overclocking and undervolting, sure, and that is perfectly fine. SetCPU is a convenient tool for controlling that without having to compile and flash a new kernel. If you do not like profiles, do not use them. They were only introduced in 1.3.0 But don't uninstall SetCPU because it does nothing with profiles disabled.
dogiedogie said:
Nope, incredible and onwards only.
Click to expand...
Click to collapse
HTC implements a rather awkward driver in nearly all of their Sense UI devices (and I think the Magic 32A) that throttles based on certain conditions. I am not entirely sure how it works, as I have not looked into the specifics, but it seems to max out the CPU under some conditions.
chowlala said:
I have some reasons to believe that SetCPU would interfere with the actual design of the Nexus One. I mean after all, i'm sure it was programmed to manage itself. So why have another app that does the same thing, twice? Just a thought, but for one thing, my phone is definitely cooler when charging compared to having SetCPU with profiles.
Click to expand...
Click to collapse
I am 100% sure this is placebo effect. Setcpu can't make your phone run hotter just because it's there. If you had a charging profile set for 1113/1113, sure, but that is not setcpu itself. Linux does not control the CPU scaling any further than what ondemand does - there is nothing preventing the CPU from going up to your max during sleep (or rather, when the screen is off), for example, or when your battery is low.
Oh, and using the active widget is a bad idea if you care about battery life. I tried to optimize it as much as possible, but realize that it's updating a lot more things than other apps are (the frequency, the bounds, and two temperature readings) at a relatively fast interval. The home screen does pause a bit while it is updating. That is a fact of life. Longer intervals are essentially useless because the update interval for cpufreq itself is on the order of thousands of microseconds. The current appwidget refreshes if the screen is on, regardless of whether it's visible or not (there is currently no way to tell if it is visible). A live wallpaper would be a much better idea than a constantly updating appwidget, and I'll look into that.
Let me explain this bit better. Cpufreq will scale your CPU between the max and min values automatically. Once the CPU load hits the "up threshold," it takes your CPU frequency from the min to the max, then gradually eases it down. SetCPU lets you easily change the max and min values on the fly. If you want, it can also prevent the system from scaling the CPU up that high during times you don't want it to (with profiles, of course). It does not and cannot interfere with the actual governor.
Well there you have it, straight from the source
TL;DR - setCPU doesn't run code in background unless you use profiles, it doesn't make your phone hotter unless you use a 1113/1113 profile, & if you value battery life don't use setCPU Active widget.
SetCPU
coolbho3000 said:
...
Click to expand...
Click to collapse
Props dude. Keep up the good work.
To be honest I'm a user, donator and supporter of SetCPU. I've never had cause to complain.
Not bashing your app dude, in fact I have the paid version. I am only wondering why people are noticing better battery life without it than with it. Want to see if it really is setcpu or something else. To do that something has to be isolated.
And I believe that if the freq are set in the kernel then the phone will scale up an down on its own.
coolbho3000 said:
Yeah, start bashing my app, knowing I was the one who came up with the ideas behind the 1113MHz/uv hack in the first place (in fact, I came up with the 21MB hack as well, so prominently displayed in the OP's kernel thread title). Thanks, nexus one community.
I can explain that setcpu does not run any code in the background if your profiles are disabled, I can explain how cpufreq works, I can explain what lengths I went to to optimize the profiles, and I can explain that the profiles are very passive (except sometimes on the Droid, but there's an option for tweaking that) but I probably won't bother. Grab 1.5.3a and use it, or don't use it. I don't care either way.
You obviously do not know how cpufreq works. Setcpu does not touch the values after it sets a profile. Profiles actually run code only when it receives broadcast intents. It sets the max and min bounds and the governor if necessary within a fraction of a second. The service is completely idle otherwise. It can't "interfere with the built in governor." Okay, then. What is your big theory? What exactly is setcpu doing wrong?
SetCPU is advantageous because it allows you to tweak speeds on the fly and based on certain conditions. You can have solely kernel based overclocking and undervolting, sure, and that is perfectly fine. SetCPU is a convenient tool for controlling that without having to compile and flash a new kernel. If you do not like profiles, do not use them. They were only introduced in 1.3.0 But don't uninstall SetCPU because it does nothing with profiles disabled.
HTC implements a rather awkward driver in nearly all of their Sense UI devices (and I think the Magic 32A) that throttles based on certain conditions. I am not entirely sure how it works, as I have not looked into the specifics, but it seems to max out the CPU under some conditions.
I am 100% sure this is placebo effect. Setcpu can't make your phone run hotter just because it's there. If you had a charging profile set for 1113/1113, sure, but that is not setcpu itself. Linux does not control the CPU scaling any further than what ondemand does - there is nothing preventing the CPU from going up to your max during sleep (or rather, when the screen is off), for example, or when your battery is low.
Oh, and using the active widget is a bad idea if you care about battery life. I tried to optimize it as much as possible, but realize that it's updating a lot more things than other apps are (the frequency, the bounds, and two temperature readings) at a relatively fast interval. The home screen does pause a bit while it is updating. That is a fact of life. Longer intervals are essentially useless because the update interval for cpufreq itself is on the order of thousands of microseconds. The current appwidget refreshes if the screen is on, regardless of whether it's visible or not (there is currently no way to tell if it is visible). A live wallpaper would be a much better idea than a constantly updating appwidget, and I'll look into that.
Let me explain this bit better. Cpufreq will scale your CPU between the max and min values automatically. Once the CPU load hits the "up threshold," it takes your CPU frequency from the min to the max, then gradually eases it down. SetCPU lets you easily change the max and min values on the fly. If you want, it can also prevent the system from scaling the CPU up that high during times you don't want it to (with profiles, of course). It does not and cannot interfere with the actual governor.
Click to expand...
Click to collapse
I too am a fan of setcpu, and over the last week I did get curious due to this this thread. I found my battery ran down quite significantly faster without setcpu, maybe because I didn't have my sleep profile of lowest freq min/max, or my battery profile of max 756, or my low battery profiles scaling down my cpu max. Either way, stop bashing the app, it's awesome, and if you had concerns, take them to the dev rather than start a witch hunt in the forums trying to make a posse.
People that report better battery, may not have had setcpu set up correctly in the first place. A friend of mine at work installed it, ran for a day and uninstalled it, citing it didn't do anything and infact drained his battery. He had the widget running, and had upped the minimum cpu freq to 500 and something, max to the 1.13ghx. He didn't run profiles. But as such, he wasn't letting his phone scale down to the lowest freq when it wanted to, and had the widget drain. I got him to set t up as I have mine, and he was blown away with the change.
"My car wont go over 20km/h"
"Are you putting your foot on the accelerator?"
"Whats an accelerator?"
Things have to be used correctly to get the best out of them, and unless someone saying it's far worse than without actually comes in and puts up their values they have it set to, we have no idea why they are having the fault. My experience (I have worked tech call centres for years) is that 99/100 issues people experience are due to not using things as they are set out to be, or just have no idea how to do what they are trying to do. My work mates thing was that he thought all apps would go faster if he increased the minimum freq, so therefore use less battery because the processes are completed faster. In a way it's logical, but the result is that even when nothings running the cpu wont fall below that value, so the battery drained much faster than he expected.
So I love Set CPU and it was working for a bit, but now for some reason my profiles refuse to work. I have them enabled, but it always has "Main Profile" activated, which kills my batter. Below are my set profiles:
Screen Off 245/245
Priority: 100 Ondemand
Charging/Full 806/806
Priority: 85 Ondemand
Battery < 50 748/710
Priority: 75 Ondemand
Battery < 1 710/604
Priority: 65 Ondemand
I'm using KaosFroyo v23, but I haven't seen anything about bugs with SetCPU in it.. so anyone have any other ideas? It seems the problem is the 'Main Profile' over riding my profiles.
those are some pretty high profiles......... what are you OC to?
copestag said:
those are some pretty high profiles......... what are you OC to?
Click to expand...
Click to collapse
You mean how high can I OC to? Umm, 824 is the highest I've gone too.
Holy **** 824, lucky bastard.
Anyway, I have the same exact problem. If you want it to work you have to go into set cpu and tap the "enable" button under profiles and disable and re-enable and then hit the back button to exit. This'll keep it working on your profiles until you reboot, so just do this once as soon as you reboot.
Hungry Man said:
Holy **** 824, lucky bastard.
Anyway, I have the same exact problem. If you want it to work you have to go into set cpu and tap the "enable" button under profiles and disable and re-enable and then hit the back button to exit. This'll keep it working on your profiles until you reboot, so just do this once as soon as you reboot.
Click to expand...
Click to collapse
Yeah, guess I lucked out on my phone. It's kind of a beast lol. Anyway, I tried that but it still doesn't seem to work. In the notification in the status bar, it always says "Main Profile" rather than "Charging/Full" or whatever. My "screen off" one out does work, though. The widget will show my screen off settings for a sec when I unlock the phone.
It may just be an issue with the notification bar updating.
Oh and does that say battery < 1% ? or is it supposed to be 100%?
Just so you know here's an example of how profile priority should be done
When under 50% battery, 90 priority
when under 100% battery, 80 priority
You see how lower battery needs a higher priority? This is because when you're under 50, you're also under 100. This may be your problem. Make sure that lower battery gets HIGHER priority.
I also suggest you set a temperature priority, especially with your killer speeds.
*dies of jealousy*
Hungry Man said:
It may just be an issue with the notification bar updating.
Oh and does that say battery < 1% ? or is it supposed to be 100%?
Just so you know here's an example of how profile priority should be done
When under 50% battery, 90 priority
when under 100% battery, 80 priority
You see how lower battery needs a higher priority? This is because when you're under 50, you're also under 100. This may be your problem. Make sure that lower battery gets HIGHER priority.
I also suggest you set a temperature priority, especially with your killer speeds.
*dies of jealousy*
Click to expand...
Click to collapse
I think this was the problem. I messed up the priorities, it's a tad confusing.. oh well, this should fix it. When I did the fix in your last post, I realized that both my screen off AND my charging one did. Just not my battery.
Thanks for the help man. And for the tip about the temperature, I didn't take that into account, being that I wasn't aware my OCing was that crazy!
EDIT: Yep, that fixed it! One more question, I'm assuming that my screen off/charging/temperature profile should be set at 100% Priority? Or should it go temp profile > screen off > charging > lower battery > higher battery?
EDIT AGAIN: Okay, I think the proper set up is: temp profile > charging/full > screen off > 25% battery > 50% battery. Correct? The temp should be the highest priority so it can override the others, then charging should be able screen off, since it's pointless to lower the overclock while charging, then screen off since it is important to battery life, then lower battery, followed by higher battery for the reason you explained.
Wewf. It's worth the set up, I suppose.. and btw I CAN overclock to 844, but it's not stable in the slightest.
824? nice....... thats why I was mentioning the high profiles......... most people cap out at about 768 on this phone......I just initially set mine there and havent really tried for more
as for the profile priority goes...... IMO the temp needs highest priority.... this is the one that does the damage if not obeyed ........
I personally have all my profiles (other than main of course) set to 480/245 so priority doesnt really matter
in your last post you mentioned it being pointless to lower OC while charging..... depending on your temp profile and charging method, this theory doesnt much matter..... since on wall charger I always exceed my temp profile anyhow (which I have set to the specs in the manual 40°C/104°F)
copestag said:
824? nice....... thats why I was mentioning the high profiles......... most people cap out at about 768 on this phone......I just initially set mine there and havent really tried for more
as for the profile priority goes...... IMO the temp needs highest priority.... this is the one that does the damage if not obeyed ........
I personally have all my profiles (other than main of course) set to 480/245 so priority doesnt really matter
in your last post you mentioned it being pointless to lower OC while charging..... depending on your temp profile and charging method, this theory doesnt much matter..... since on wall charger I always exceed my temp profile anyhow (which I have set to the specs in the manual 40°C/104°F)
Click to expand...
Click to collapse
Yeah, I just realized something pretty bad when I charged it over night.. being that charging (the 824 one) was set to a high priority that the screen off, it was literally on 824 ALL night long.. I woke up and the battery tempt was 145 D: It was fine, my temp profile saved it from going too high, thank God.
Any ideas for a good temp to set that profile at, though? It's at like 130 now, but I think that's a bit too high as well.
specs list an upper limit of 40C/104F....
specs are usually conservative (my profile is set to spec).....but I wouldnt go too far over if I were you
Sent from my Eris using XDA App
copestag said:
specs list an upper limit of 40C/104F....
specs are usually conservative (my profile is set to spec).....but I wouldnt go too far over if I were you
Sent from my Eris using XDA App
Click to expand...
Click to collapse
Alright, I kicked it down a notch to 40C.
Thanks for the help guys.
I have mine at 41.7 degrees since I can hit 40 easy.
Quick Question -
Running Kaos v23 now - since upgrading from v21, I have lost the icon at the top of the menu home screen. Also, when I go into task killer, it is not shown as an active application. Any ideas???
Thanks
bl4scott said:
Running Kaos v23 now - since upgrading from v21, I have lost the icon at the top of the menu home screen. Also, when I go into task killer, it is not shown as an active application. Any ideas???
Thanks
Click to expand...
Click to collapse
Um, have you tried OPENING the app? Go to your app drawer, click on it, then check mark "Notifications" under "Profiles."
And yeah I changed the temp profile, cause it overheated during a phonecall..
Make sure it's installed. If none of your superuser permissions are working reflash an old superuser.
Does anybody have ANY good info on the Advanced settings for setcpu
sampling rate
power save bias and what not for our phones
or where we can find them ?
Hi all,
Was just wondering what was preferred by everyone for Froyo ROMs..
setCPU or Collins Battery Tweak?
Which works best for you and at what settings?
Thanks very much!!! And hope to see some good responses
tcrappa2 said:
Hi all,
Was just wondering what was preferred by everyone for Froyo ROMs..
setCPU or Collins Battery Tweak?
Which works best for you and at what settings?
Thanks very much!!! And hope to see some good responses
Click to expand...
Click to collapse
Don't forget CPUBoost. I feel like a groupie
I'm kinda sixes on it, setCPU tends to run constantly in the background and uses more battery power, so I prefer it for just overclocking, but I think it's interfacing is kind or a pain. It does allow one to set customized profiles variable priorities, when i had an eris that I could OC to 844 I had three different temp profiles set to lower the clock as the phone heated up
Collins Tweak is specifically engineered for battery life, which I really don't care about, and, if I correctly recall, the lowest percent underclock it allows is 10% as the battery drains. Aside from that, it's flexibility is great, is command prompt, which may bother some, but you set it once and can forget about it, it allows you to even define how often it starts to check the battery to adjust CPU limits, so you can to a degree define how little it runs in the background, I've set mine as long a 3600 seconds, it does have temp threshold settings, but only one set. I listen to Pandora all the time (maybe only 90%) and therefore hate the smartass governor, not in principle, but definitely in practice, and Collins Tweak allowed me to shut that down with certainty.
I've been using CPUBoost since Conap integrated into CELB3.8, I'm actually a little behind I haven't gone to 3.9 yet or installed the latest CPUBoost, so my one real complaint may be addressed by now, but occasionally the phone seems to just reset the settings, so I sometimes have to change the governor back. It's very simple interfacing and right to the point, governor, max and min. Unless support has been added there are no temp options, but my current eris ****s out at 768, so it's no longer a big deal for me.
+1 CPUBoost.
I'm running gingertazz on my eris and have heard a lot about people using setCPU to overclock and their recommendations on how to do so. However, I want to use it to underclock when my screen is off but I have no idea what to set it to. I've heard that it's possible to underclock too much and screw things up so is anyone else underclocking when the screen is off? what settings do you use and have you seen any issues or battery improvements? Thanks!
terps9lax said:
I'm running gingertazz on my eris and have heard a lot about people using setCPU to overclock and their recommendations on how to do so. However, I want to use it to underclock when my screen is off but I have no idea what to set it to. I've heard that it's possible to underclock too much and screw things up so is anyone else underclocking when the screen is off? what settings do you use and have you seen any issues or battery improvements? Thanks!
Click to expand...
Click to collapse
No, you can't actually screw up your phone by underclocking. The worst is your phone might lag coming out of sleep when you receive a new notification or phone call. I've underclocked all the way down to 19MHz before, although I usually do experience some lag at some times. I would say that the best performance while still underclocking is at 245MHz, although you can experiment yourself and find out if 160 or 128, or even 19 might work fine enough for you.
awesome, I'll have to mess with it and see what works for, thanks for the help!
roirraW "edor" ehT said:
No, you can't actually screw up your phone by underclocking. The worst is your phone might lag coming out of sleep when you receive a new notification or phone call. I've underclocked all the way down to 19MHz before, although I usually do experience some lag at some times. I would say that the best performance while still underclocking is at 245MHz, although you can experiment yourself and find out if 160 or 128, or even 19 might work fine enough for you.
Click to expand...
Click to collapse
I totally agree with you. ALTHOUGH, if I may make a suggestion. The smartass setting is very effective at automatically scaling down the CPU for screen off and also allows for pretty descent recovery upon wake up. Honestly, I would just rock smartass until you actually needed to scale up for a certain app or whatever. Most off the times even on my DINC I'll just let smartass have full control. But then again this DINC is pretty powerful and never has problems waking up.
[DINC]¦[2.15.00.11.19]¦[INCREDIKERNEL]
wildstang83 said:
I totally agree with you. ALTHOUGH, if I may make a suggestion. The smartass setting is very effective at automatically scaling down the CPU for screen off and also allows for pretty descent recovery upon wake up. Honestly, I would just rock smartass until you actually needed to scale up for a certain app or whatever. Most off the times even on my DINC I'll just let smartass have full control. But then again this DINC is pretty powerful and never has problems waking up.
[DINC]¦[2.15.00.11.19]¦[INCREDIKERNEL]
Click to expand...
Click to collapse
Every once and a while, even very recently, I try Smartass again and I almost always end up having lag more often. I'm sure that's because of our underpowered phones, but....just my opinion.
Send me your Dinc and then I'll try it longer!
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?