Related
ok i was under the impression that cynanogen mod autmatically over clocks the cpu to 528mhz. But someone told me it doesn't. Does it? and if i use setcpu will affect the stability?
Your not really Oc'ing because the CPU was made to run at a max of 528 and 384 is the stock(Offical OTAs) to save battery life. It will only go that high when needed, you dont drive at a 100MPH just to do it, you do that when no one else is around. It will reach that high under heavy load not if your dialing on just swiping on home.
ace is right from what ive been told and read. the cpu is underclocked so its not hitting its full potential.
also no cyanogen does not do this automatically. this is best done by the user anyway as they can get a prefered setup then on their phone as this does consume battery life.
Ok i downloaded setcpu but i dont see a big difference i selected 528 as max and the max stock as minumum and put set on boot and i rebooted. I dont know why im typing in upper case, im on my g1
to be honest i never really noticed too much of a difference myself.
I've been using SetCPU now for about 48 hours and am very impressed with it. See my sig for current system setup. As far as SetCPU settings: on-demand throttling, 528 MHz max, 245 Mhz min, no profile settings, scaling up setting 75%, and both "set on boot" options checked. The SetCPU settings definitely make the phone snappier compared to the normal CyanogenMod settings.
is there a difference between on demand governor or performance? whitch one is faster?
nahanee20 said:
is there a difference between on demand governor or performance? whitch one is faster?
Click to expand...
Click to collapse
http://www.pokedev.com/setcpu
On demand will scale CPU speed between the minimum and maximum settings, and performance runs it at maximum constantly.
Current CM rom fluctuates from 256Mhz/min to 528Mhz/max on demand. I suggest you leave it alone since it's an exceptional setup. Unless you prefer a constant max and have your battery die in 6 hours give or take.
BoomBoomPOW said:
Current CM rom fluctuates from 256Mhz/min to 528Mhz/max on demand. I suggest you leave it alone since it's an exceptional setup. Unless you prefer a constant max and have your battery die in 6 hours give or take.
Click to expand...
Click to collapse
It's not that exceptional, nor does modifying that setup drain your battery much faster. My G1 is much faster after using SetCPU to change the settings. My battery drain in standby is unchanged (because I'm using the same minimum setting as CM), and it is significantly faster under heavy usage. There's really no downside to it, so to assume that the default CM setup is optimal is a little short sighted in my opinion. Don't be offended...just my 2 cents.
TeeJay3800 said:
It's not that exceptional, nor does modifying that setup drain your battery much faster. My G1 is much faster after using SetCPU to change the settings. My battery drain in standby is unchanged (because I'm using the same minimum setting as CM), and it is significantly faster under heavy usage. There's really no downside to it, so to assume that the default CM setup is optimal is a little short sighted in my opinion. Don't be offended...just my 2 cents.
Click to expand...
Click to collapse
What you just stated is the exact performance the coded frequency default on CM does. On demand is the key word. When you go standby/sleep, frequencies goes minimum. When under heavy usage, frequencies goes maximum. So how is that short sighted? When everything you stated that SetCpu does better, is the exact thing that the default CM setup does. Plus having SetCpu process run constantly in background is a main factor that eats up RAM. While the default CM setup does not. The only benefit I see with SetCpu are the profiles.
The main thing that SetCPU does that CM does not is adjust the threshold at which the CPU begins to scale up. I have mine set to 50% which is far lower than CM's setting, and I believe that is the main reason my phone is so much faster.
Also, SetCPU does not stay running in the background. A script runs at boot to apply your settings, but the app doesn't actually run unless you start it yourself.
CM's default up threshold is at 40, so I have no clue where you got the idea that is far higher. Also, it does not affect speed. It's the percent cpu usage before going up a speed step. So actually the higher the threshold, the longer it stays on current/lower speed.
SetCpu does stay running in the background. Open your app drawer, open Dev Tools, Running Processes, and you will see SetCpu (com.mhuang.overclocking) running.
Well pal, all I can tell you is my phone is a LOT faster after using SetCPU to adjust settings. I don't mean only marginally, I mean significantly. In fact I can't overstate how much more snappy the phone is. If you can explain why that might be, I'd love to hear it.
Well pal, all I can tell you is my phone is a LOT faster after using SetCPU to adjust settings. I don't mean only marginally, I mean significantly. In fact I can't overstate how much more snappy the phone is. If you can explain why that might be, I'd love to hear it.
EDIT: That process is not running.
It boils down to user experience. If it feels cold, then it must be cold. Am I right? But these are all perceptions manufactured by our brain. That is why we have crazy people. I'm not calling you crazy, but crazy people see things that are not there. Perception is the word of the day.
I guess we'll have to agree to disagree. I could measure the before and after difference with a stopwatch, meaning it genuinely is faster. In my opinion, it is entirely possible that SetCPU allows for faster performance than CM does by default. Unfortunately, that is impossible for me to prove via an internet forum. Anyway, it was fun debating with you.
BoomBoomPOW said:
What you just stated is the exact performance the coded frequency default on CM does. On demand is the key word. When you go standby/sleep, frequencies goes minimum. When under heavy usage, frequencies goes maximum. So how is that short sighted? When everything you stated that SetCpu does better, is the exact thing that the default CM setup does. Plus having SetCpu process run constantly in background is a main factor that eats up RAM. While the default CM setup does not. The only benefit I see with SetCpu are the profiles.
Click to expand...
Click to collapse
I've been rooted and running SetCPU for a while but just recently switched to CM. I had CM running with SetCPU until today when I decided to remove SetCPU to see how CM does on it's own. My phone seems exactly the same from what I can tell... if not a tad faster. BUT I really liked the ability to have SetCPU clock the CPU waaaay down when the battery gets below a certain %. I had it set to run at 245max/128min when the battery dropped below 30%... yes it was sluggish but it would stretch that 30% for many hours if I needed it to.
Does CM do anything like this or have a provision somewhere for setting cpu speed based on battery level? I don't like having stuff installed if I don't need to, but missing this feature may have me reinstalling SetCPU.
I use System Panel pretty religiously to keep an eye on things, mostly in an effort to save battery life or figure out what apps are using battery. One thing I noticed right away, which may explain the complaints people are having with shorter battery life and warmer running.
On 2.1, if I leave System Panel open and just watch CPU clock speed, it will idle in the 200-300 MHz range. With the leaked Froyo OTA, it never goes below 600 while idle, and averages 700-800. I went ahead and closed down all third party apps and even some non essential built in processes just to make sure, but nothing got the CPU speed below 600. Now CPU *load* percentage was minimal, less than 10%. So why won't Froyo let the speed drop down at idle?
bast525 said:
I use System Panel pretty religiously to keep an eye on things, mostly in an effort to save battery life or figure out what apps are using battery. One thing I noticed right away, which may explain the complaints people are having with shorter battery life and warmer running.
On 2.1, if I leave System Panel open and just watch CPU clock speed, it will idle in the 200-300 MHz range. With the leaked Froyo OTA, it never goes below 600 while idle, and averages 700-800. I went ahead and closed down all third party apps and even some non essential built in processes just to make sure, but nothing got the CPU speed below 600. Now CPU *load* percentage was minimal, less than 10%. So why won't Froyo let the speed drop down at idle?
Click to expand...
Click to collapse
Good catch. I'm looking at it now, it gets down to 448mhz while downloading an APP from the market over the mobile network. Once downloaded and installed, it stays between 600-900mhz?? Rebooted and it still never goes below 6, and mostly stays in the 7-800's. Not good! I have a fresh install of Skyraider 2.01 with sense removed, using launcher pro.
I found this really interesting but I think systempanel is reading incorrectly. I say this because if you watch set CPU read the processor you can see that it drops down to 245mhz when idle even though systempanel reads 600-700mhz.
Sent from my ADR6300 using XDA App
What is this nonsense people are saying about 4 or 5 hours with screen on and their phone is still at 20%? GTFO.... Usually I would say about 3 hours of screen on and i'm dead. I can get like 18 hrs or so lightly, and by lightly, I mean only using it for a few text and check email, maybe some fb just to check inbox and such, lightly, using the phone (with my reception).
I know the Fascinate is better hardware, and I switched for the GPU among other reasons (2 of em for free...=P) but, on my nexus, I still find that the interactive governor ramped up to the max freq. (1113Mhz) less. Of course, I am using the 1150 nonvoodoo from geeknik, but I doubt I will make it 4 or 5 hours of screen on time.w
How can you use the phone, with the screen on, and not do anything that uses the battery. I mean, without cyanogen, it was cool that I can make it through my day, easy, close to out of box (getting to superclean dj05 is about 100 less flashes that I made it through with the n1/sense/cyan nightlys/test roms/etc.).
But now I want more, the price I have to pay I guess for the .3 inches of gained screen is not using the phone heavily in order to save battery!? That sucks. I used to hammer my iPhone and I rarely made it through the day, but I hammered it with atleast 4 or 5 hrs of screen on time sometimes, and it would make it atleast 8 hours... that thing would idle wayyyy better on GSM Edge than CDMA I guess, as with my T-Mobile N1, it idled wayy better, than this CDMA phone. Is there a way to put it on 1x instead of having it always on 3g? There isnt a setting to uncheck, and you cant get in *#*#4636#*#* on CDMA. I tried that immediately after unboxing to get off 3g when I wasnt using net apps, and usually that gave better signal on GSM, saving battery.
Check out my interactive battery test on my N1 that I did, the interactive setting eventually fell out of favor because it ramps up to the max... instead of ramping up accordingly like OnDemand, and not too slowly like Conservative. Again, why does Fascinate use conservative?
http://forum.xda-developers.com/showthread.php?p=7370179 thats my Interactive Governor Battery Test on my N1 I did in the summer time...
I just wanted to start this thread so we can get a consensus on what works best, and for charging this battery. I used to charge my N1 an extra 1.5 hrs with it off after android says it was at 100. That way it idled on 100 instead of immediate drain. An extra 3 or so hours of battery life if you use it right.
CPU governors control exactly how the CPU scales between your "max" and "min" set frequencies. Most kernels have "ondemand" and "performance." The availability
********I want to be able to choose between ondemand and powersave when my battery gets low. On this phone, as I did with the N1.
ondemand - Available in most kernels, and the default governor in most kernels. When the CPU load reaches a certain point (see "up threshold" in Advanced Settings), ondemand will rapidly scale the CPU up to meet demand, then gradually scale the CPU down when it isn't needed.
conservative - Available in some kernels. It is similar to the ondemand governor, but will scale the CPU up more gradually to better fit demand. Conservative provides a less responsive experience than ondemand, but can save battery.
performance - Available in most kernels. It will keep the CPU running at the "max" set value at all times. This is a bit more efficient than simply setting "max" and "min" to the same value and using ondemand because the system will not waste resources scanning for the CPU load. This governor is recommended for stable benchmarking.
powersave - Available in some kernels. It will keep the CPU running at the "min" set value at all times.
userspace- A method for controlling the CPU speed that isn't currently used by SetCPU. For best results, do not use the userspace governor.
akaine2001 said:
What is this nonsense people are saying about 4 or 5 hours with screen on and their phone is still at 20%? GTFO.... Usually I would say about 3 hours of screen on and i'm dead. I can get like 18 hrs or so lightly, and by lightly, I mean only using it for a few text and check email, maybe some fb just to check inbox and such, lightly, using the phone (with my reception).
I know the Fascinate is better hardware, and I switched for the GPU among other reasons (2 of em for free...=P) but, on my nexus, I still find that the interactive governor ramped up to the max freq. (1113Mhz) less. Of course, I am using the 1150 nonvoodoo from geeknik, but I doubt I will make it 4 or 5 hours of screen on time.w
How can you use the phone, with the screen on, and not do anything that uses the battery. I mean, without cyanogen, it was cool that I can make it through my day, easy, close to out of box (getting to superclean dj05 is about 100 less flashes that I made it through with the n1/sense/cyan nightlys/test roms/etc.).
But now I want more, the price I have to pay I guess for the .3 inches of gained screen is not using the phone heavily in order to save battery!? That sucks. I used to hammer my iPhone and I rarely made it through the day, but I hammered it with atleast 4 or 5 hrs of screen on time sometimes, and it would make it atleast 8 hours... that thing would idle wayyyy better on GSM Edge than CDMA I guess, as with my T-Mobile N1, it idled wayy better, than this CDMA phone. Is there a way to put it on 1x instead of having it always on 3g? There isnt a setting to uncheck, and you cant get in *#*#4636#*#* on CDMA. I tried that immediately after unboxing to get off 3g when I wasnt using net apps, and usually that gave better signal on GSM, saving battery.
Check out my interactive battery test on my N1 that I did, the interactive setting eventually fell out of favor because it ramps up to the max... instead of ramping up accordingly like OnDemand, and not too slowly like Conservative. Again, why does Fascinate use conservative?
http://forum.xda-developers.com/showthread.php?p=7370179 thats my Interactive Governor Battery Test on my N1 I did in the summer time...
I just wanted to start this thread so we can get a consensus on what works best, and for charging this battery. I used to charge my N1 an extra 1.5 hrs with it off after android says it was at 100. That way it idled on 100 instead of immediate drain. An extra 3 or so hours of battery life if you use it right.
CPU governors control exactly how the CPU scales between your "max" and "min" set frequencies. Most kernels have "ondemand" and "performance." The availability
********I want to be able to choose between ondemand and powersave when my battery gets low. On this phone, as I did with the N1.
ondemand - Available in most kernels, and the default governor in most kernels. When the CPU load reaches a certain point (see "up threshold" in Advanced Settings), ondemand will rapidly scale the CPU up to meet demand, then gradually scale the CPU down when it isn't needed.
conservative - Available in some kernels. It is similar to the ondemand governor, but will scale the CPU up more gradually to better fit demand. Conservative provides a less responsive experience than ondemand, but can save battery.
performance - Available in most kernels. It will keep the CPU running at the "max" set value at all times. This is a bit more efficient than simply setting "max" and "min" to the same value and using ondemand because the system will not waste resources scanning for the CPU load. This governor is recommended for stable benchmarking.
powersave - Available in some kernels. It will keep the CPU running at the "min" set value at all times.
userspace- A method for controlling the CPU speed that isn't currently used by SetCPU. For best results, do not use the userspace governor.
Click to expand...
Click to collapse
Thank Samsung for breaking ondemand on every sgs phone.
Sent from my SCH-I500 using XDA App
Well what else can you contribute to this thread? Thanks for letting me know that the ondemand is just broken on galaxy s phones. So basically its interactive ... or laggy UI experience. And if you've never used a ondemand kernel, you wouldn't notice the difference but i certainly do. It just takes too long sometimes for it to wake and other things. I have my screen off at 400 mhz but still that is higher than the 256 i was using on the nexus one and it used to wake immediately.
I was reading today and I found that ondemand is pretty much the way to go so i wonder if we could bounty up enough would somebody unbreak it...
akaine2001 said:
Well what else can you contribute to this thread? Thanks for letting me know that the ondemand is just broken on galaxy s phones. So basically its interactive ... or laggy UI experience. And if you've never used a ondemand kernel, you wouldn't notice the difference but i certainly do. It just takes too long sometimes for it to wake and other things. I have my screen off at 400 mhz but still that is higher than the 256 i was using on the nexus one and it used to wake immediately.
I was reading today and I found that ondemand is pretty much the way to go so i wonder if we could bounty up enough would somebody unbreak it...
Click to expand...
Click to collapse
You are doing something wrong. Conservative is not choppy on my device and the CPU will always ramp up faster than a human being can judge the response time.
Sent from my SCH-I500 using XDA App
My phone makes it the entire day with heavy use, this means about 20 - 10 min phone calls one or two lasting 30 min, texting my wife all day at work, checking emails, and angry birds for at least 1 hour a day i love that game but I suck at it lol. Something that I found is that the phone will last almost an hour of being on the phone after it hits 0%. In my pocket it lasted 4 hours at 0% the day before yesterday. I thought maybe this is on purpose so you have more then enough time to make it to a charger. When I first downloaded angry birds I played it for three hours straight with the screen at full brightness (i always keep it at full brightness, looks prettier that way) I know it was three hourse because it was while i was waiting at the hospital I got there a little before 7 and wasnt called until 10. Overall I am very pleased with the battery life of this phone not so much with other aspects but battery life and lag never came into my mind as a complaint for this phone, except with all the stock touchwiz stuff.
As adrynalyne said, CPU's scaling changes faster than human's perception. It's your phone or setting that's having an issue.
4 hours at 0%?
The little graphic samsung gives you in the stock battery is misleading.
In my brief experience with it, I got the following impression.
full battery graphic: you have between 100% and 75% left.
<full battery: 75%-50%
Half battery: 50%-25%
low battery: 25%-15%
empty: 15%-0%
This may not be quite right, but you get the idea. It has been a while, but stock battery is pretty misleading. Samsung reports [more than] half empty [always] as being half full!
Want a more trailer indicator? You can get an accurate battery mod (via a theme for instance) or you can download an app to check current battery % left (i use osmanager - do not leave this app running in the background! )
Assuming your phone lasts 27 hours or so unplugged with no use at all, I would say 4 hours at "zero" battery makes sense.
For my phone, the display uses an average of 3.5x as much power as the rest of its functionality (total of 1/4.5x lifespan in active use vs. pocket)
Swyped w/ XDA App. When in doubt, mumble.
I meant "reliable" not trailer.
I get about 5 hours of screen time with little voice calls on wifi.
I don't know if I am just one of the lucky ones but my phone gets between 30 and 36 hours on a single charge, having even made it to 44 hours on a very rare occasion and that's without setcpu profiles even set.
Wtf... my phone is brand spanking new and I get about 4ish hours of screen time on a full charge, with the lowest brightness + screen filter app set at 50.6% reduced light. I get like 3 hours without screen filter on.... wtf. This is running on conservative or interactive the whole time..... wtf!!! With wifi on and 0 extra screens or Widgets using launcher pro without animations... wtf!!!
Sent from my SCH-I500 using XDA App
+1... stock battery indicator is not accurate. Get the accurate battery mod.
soba49 said:
4 hours at 0%?
The little graphic samsung gives you in the stock battery is misleading.
In my brief experience with it, I got the following impression.
full battery graphic: you have between 100% and 75% left.
<full battery: 75%-50%
Half battery: 50%-25%
low battery: 25%-15%
empty: 15%-0%
This may not be quite right, but you get the idea. It has been a while, but stock battery is pretty misleading. Samsung reports [more than] half empty [always] as being half full!
Want a more trailer indicator? You can get an accurate battery mod (via a theme for instance) or you can download an app to check current battery % left (i use osmanager - do not leave this app running in the background! )
Assuming your phone lasts 27 hours or so unplugged with no use at all, I would say 4 hours at "zero" battery makes sense.
For my phone, the display uses an average of 3.5x as much power as the rest of its functionality (total of 1/4.5x lifespan in active use vs. pocket)
Swyped w/ XDA App. When in doubt, mumble.
Click to expand...
Click to collapse
Terror_1 said:
I don't know if I am just one of the lucky ones but my phone gets between 30 and 36 hours on a single charge...
Click to expand...
Click to collapse
That's because you don't use your phone.
Go play NFS for 3 hours and get back to us.
MoShiBa said:
...screen filter app set at 50.6% reduced light. I get like 3 hours without screen filter on...conservative or interactive the whole time...
Click to expand...
Click to collapse
What's the screen filter app? Conservative and interactive? That's SetCPU?
I wouldn't worry about these guys coming in here saying they're getting 2 days of use either. They're not using the phone anywhere near as much as you. I've had 3 of these things and know 2 guys with them. They all got the same battery life. You don't see anyone posting any screenshots, do you?
Me and my gfs fascinate gets about same battery life in our apt and hers is still DI01 and i'm on DJ05... she has jts 11/16 kernel and i have the 12/21 voodoo5 and we get about the same battery life... dependent on how much we use the phone. .... so just use your phone, and charge it as necessary... its better for the type of battery we use anyways in our phones... **************************************************************************************closed.**************************************************************************************
hy there,
im on latest sokp rom on my g2 (d802)
i want to get more juice from my battery, so I setup my core setings at 1036 mhz max and minimum 300 mhz.
wil this provide me a lot off battery in real life and will it also reduce heat ? even if i watch hd movie or play graphical games
In theory yes it should but not as much as you think cause it will be offset because it will have to keep a higher frequency for a higher period of time. Temperature should be reduced a lot but keep in mind games will lag if they need the extra power
drivenby said:
In theory yes it should but not as much as you think cause it will be offset because it will have to keep a higher frequency for a higher period of time. Temperature should be reduced a lot but keep in mind games will lag if they need the extra power
Click to expand...
Click to collapse
hmm, well after i underclocked i played asphalt 8 for like 20 mins and game performance did not changed significantly. and i feel that the phone is now cooler then before when multitasking stuff.
is there also another way that can realy increase battery life besides underclocking.
abati said:
hmm, well after i underclocked i played asphalt 8 for like 20 mins and game performance did not changed significantly. and i feel that the phone is now cooler then before when multitasking stuff.
is there also another way that can realy increase battery life besides underclocking.
Click to expand...
Click to collapse
you also can try custom governors
Hey there, you may be suffering a placebo effect, it can give you a little extra juice, but in my opinion you get most of your battery with these 4:
1. Reduce timeout to 15sec.
2. Adjust screen brightness to be as low as possible (lux helps with this)
3. Eliminate vibrations of any kind (haptic feedback, notications that make your phone vibrate ex. whatsapp) and so on...
4. Data (Use Wifi if possible, 2g when you are not using your phone and airplane mode in some cases extend your battery for a lot too)
Don't expect to get more than 30 min of extra use changing your kernel configurations. ALTHOUGH if you are a heavy user (let us say, in this case, a heavy gamer) there are some kernel configurations you should check.
Also remember, if a task takes you 30min but only consumes 1 % per 30 min compared to doing the exact same task in 30seconds consuming the same 1% which one is worth it?
Phones hardware is way above the software we have available at this time, underclocking and undervolting is an option and you won't feel the difference but, as I've stated before, those are not the main issues of the battery drain.
I hope I've helped you out!
Is it safe to change my CPU governor to "performance" to force max clock speed?
I don't want to overclock my Note 4, don't worry, not talking about that. But I am talking about MAX clocking it - forcing it to run at maximum rated speed. I've already tested out SetCPU and used it to change my governor to performance which forces the clock to max, and it nearly doubled my framerate in many games, especially the ones that struggled to play on this device like Xcom:EW.
But I quickly turned it off because I wasn't sure it was safe to do in the new era of smartphones, what with their DVFS and all. I'm worried that I'm going to overheat the CPU, and it's not going to be able to downclock because of temperature anymore. I'm only modifying the governor, but what if I actually used SetCPU to just change the CPU clock to max, without even touching the governor?
Can I hurt my phone by doing this? Can I safely start forcing my CPU to run faster while playing games, knowing that the only thing I risk is my battery draining faster, or am I actually risking damaging components by doing this?
Hello and thank you for using Q/A,
your CPU will not be damaged, but the battery life time will be shorted.
Regards
Trafalgar Square
RC
I personally have used Performance governor on Moto X 2013 for almost the whole 8 months I had it, 24x7 I mean. Never had a problem, yeah maybe battery life was little less than normal but I never did really care about it. Then I ran the same governor for a good period of time on my Note 3 too, same, no problem at all. Like you said, in games the frame rate difference is massive, but I don't play much games, I simply used that governor because it gets rid off all those micro lags and jitters which are Android's trademark, I simply can't them, with default Interactive the micro lags are very apparent.
However with Note 4 I am pretty happy with the BluActive governor, it makes most of the micro lags to go away, so sticking with it.
In any case unless you plan to use a mobile phone for maybe 5 years or so, I don't see any problem at all with it, other than a slightly increased heat, and maybe a little less battery backup, but you will find so many comments which might scare you, that chip burns off if you run it and all that, but those mainly are BS.