Long time lurker, but 1st time poster.
I've noticed on my Revolution that the CPU always runs at 1ghz. I thought CPU throttling was a standard feature in android?
Anyhow I installed CPU tuner and I get much better standby battery life now (~2% drain/hr when not using phone vs. ~5% drain/hr on standby). The phone runs mostly at 124mhz w the screen off. My problem is my revolution reboots pretty frequently and sometimes even just completely shuts down w CPU tuner on. I still get reboots once in awhile w CPU tuner turned off, but much less frequently.
Anyone else having this problem? I also have green power running in the background to turn off the data connection w the screen off. Are you guys who use setCPU not getting reboots? If so I'll spend the $2 and give that a try.
hadookee said:
Long time lurker, but 1st time poster.
I've noticed on my Revolution that the CPU always runs at 1ghz. I thought CPU throttling was a standard feature in android?
Anyhow I installed CPU tuner and I get much better standby battery life now (~2% drain/hr when not using phone vs. ~5% drain/hr on standby). The phone runs mostly at 124mhz w the screen off. My problem is my revolution reboots pretty frequently and sometimes even just completely shuts down w CPU tuner on. I still get reboots once in awhile w CPU tuner turned off, but much less frequently.
Anyone else having this problem? I also have green power running in the background to turn off the data connection w the screen off. Are you guys who use setCPU not getting reboots? If so I'll spend the $2 and give that a try.
Click to expand...
Click to collapse
I honestly don't think anyone has been messing with the CPU until the CM ROM is released.
hadookee said:
Long time lurker, but 1st time poster.
I've noticed on my Revolution that the CPU always runs at 1ghz. I thought CPU throttling was a standard feature in android?
Anyhow I installed CPU tuner and I get much better standby battery life now (~2% drain/hr when not using phone vs. ~5% drain/hr on standby). The phone runs mostly at 124mhz w the screen off. My problem is my revolution reboots pretty frequently and sometimes even just completely shuts down w CPU tuner on. I still get reboots once in awhile w CPU tuner turned off, but much less frequently.
Anyone else having this problem? I also have green power running in the background to turn off the data connection w the screen off. Are you guys who use setCPU not getting reboots? If so I'll spend the $2 and give that a try.
Click to expand...
Click to collapse
As far as I've seen, the Revo's CPU does automatically speed scale to the necessary load.
If you're running lots of apps in the background, with the screen on Android will keep the cpu at full throttle to provide a smooth experience for you.
As soon as you turn off the screen, it will throttle it down as much as it can.
If the phone's rebooting on you, that's because whatever cpu tuner is doing may be keeping the cpu speed too low for the demand of the OS, then the watchdog kicks in when it thinks the cpu is stuck in a loop. (watchdog wants to be petted every 30 seconds, if the cpu misses that, the watchdog reboots the phone)
I use setcpu and have no reboot issues.
Sent from my VS910 4G using XDA App
throttle
I use android system info to show the CPU speed. It shows the % of time my revolution is running at each speed. W/o using a 3rd party app it always shows 100% at 1Ghz. W CPU tuner running it shows 50% at 122Mhz, 25% at 1Ghz, and 25% in between.
I don't think I'm running any apps thats sucking up a lot of CPU. I'm rooted w most of bloat removed.
Am I the only one not seeing any CPU throttle on stock?
i'm not seeing any throttling on stock.
setcpu drastically improved battery life when the phone's off, and no reboot issues.
some issues initially with the phone not throttling back up quickly enough when i got a call, making me unable to answer the call, but played with the settings and made it so it automatically throttles back up to 1024 when i get a call, and now it's fine.
Exactly Im much happier with my phone now. I had the same issue when I received a call but set up the profile as u did and have no problems at all
newkick said:
i'm not seeing any throttling on stock.
setcpu drastically improved battery life when the phone's off, and no reboot issues.
some issues initially with the phone not throttling back up quickly enough when i got a call, making me unable to answer the call, but played with the settings and made it so it automatically throttles back up to 1024 when i get a call, and now it's fine.
Click to expand...
Click to collapse
Sent from my VS910 4G using XDA App
I am using setCPU as well with no issues. I have mine set were the screen is off it goes to 124 and clocks back up to full 1GHz when it is on. Helps greatly improve my battery.
So what settings do you use? I get really bad lag when waking my Revo. Sometimes it will reboot after waking too.
Sent from my VS910 4G using XDA App
I don't know if this is a CPU throttling issue, or a general REVO issue, but I get horrible horrible lag sometimes trying to get any programs to respond. Like press the home key, or click send, or anything like that. I'm running Decrap 1.1, I don't know if I have too many processes running or what.
Interesting. The Thunderbolt has the same issue. Is it the same CPU in that phone?
Related
748/245
Temp < 50C 245/245 100
Screen Off 245/245 90
Charging/Full 719/245 80
Battery <40% 604/245 70
All ondemand
Temp > 42.1 528/245
Screen Off 528/160
Charging/Full 768/768
Battery <100% 768/245
that's listed by priority
Hungry Man said:
Temp > 42.1 528/245
Screen Off 528/160
Charging/Full 768/768
Battery
Click to expand...
Click to collapse
Screen Off: 245-480
**Stock is 245-245. 160 as a minimum seems to produce a LOT of wait time from when the call is coming in to when the phone lights up. More than 245 seems to whack the battery.
Keep in mind, when you wake up your phone, this Screen Off SetCPU Profile is active for at least a SECOND or two. The problem is that if you have your maximum at 245, you experience BAD lag trying to pull the lock bar down. At 245-480, the maximum is high enough that a) the lock bar pulls down as smoothly as a stock Eris, and b) even if SetCPU takes a couple of seconds to change the profile, at least you're at 480mhz for the first scrolling of the screen left/right (so you don't embarass yourself in front of iphone users). Anything higher than 480mhz is a different voltage. Almost the whole time your phone is 'Screen Off', it will be operating at 245 anyway. So 480 is a good setup for it to jump up when a call comes in (to play the ringtone and show the picture a little faster, and for the lock screen bar to pull down smoothly, and the first second of SenseUI to be smooth enough, until your phone changes the profile to your <100% profile.
Battery <100% 245-806
** Zanfur's take on how this processor clocks up/down its speeds will lend itself to a general wisdom that 768mhz isn't really slower than 806mhz, and that in instances of high variability of clock speed (aka you have some Power Save bias in SetCPU keeping it lower/higher at random, or you're doing very intermittent tasks), the processor rests at 768mhz more quickly, and wastes less time/'effort' changing speeds. Changing to 806 is another 'step' altogether, where 245 to 528 is one 'step', and that to 768 is another 'step'. Going to 806 is absolutely another step yet after that (which means your phone responds a LITTLE slower because it has one more step to 'throttle' up to). BUT, if you're doing a dedicated task, such as running a Linpack benchmark (which is a terrible benchmark anyway) your phone will move faster at 806, or if you're playing a game, or playing a video... generally the processor will stick at one speed (and not have to 'step' up or down), so 806 is faster. I clock friends' phones at 768 to avoid problems, keep it clean, etc etc. Some people put the minimum here at 160mhz, but I feel that this is too low (and another 'step', just like 806 is over 768, 160 is another step down from 245).
Charing (any) 480-806
** I keep the minimum here HIGHER than when the phone is on battery, because I'm less concerned about how much energy it's consuming, and having a minimum of 480 makes the phone very snappy no matter what, from the second you touch it
Overheating > 48C 122-528
** Clock speed here matters a LOT less than just getting your phone out of the heat. This phone doesn't overheat because it's overclocked, it overheats because you run it at an overclocked speed for a long time. MOST overheating instances are from wireless tethering and from broken charging systems (that keep trying to charge the battery and generate a lot of heat). The 'Failsafe' profile here provides a 'notification' option which I HIGHLY recommend.
My ex-gf's Eris actually CAUGHT FIRE, as in it looked like it was a zippo, right above the volume buttons. It used to overheat EVERY NIGHT that it was on the charger, excessively, so hot that you couldn't touch it. For a month or two it did this, actually, and caused no real damage to the phone. Since the night of the Flame (you can actually see the melted plastic and even on the outer case - she has a blue snap shell case on it that is melted as well), the phone has NOT overheated even one time on the charger. (Sorry for the story, it was a waste of time).
The point is that, the first time it happened, her phone System sound was on Silent, and she DIDN'T hear the notification that her phone was overheating. Apparently it doesn't matter (or she's very lucky her phone isn't damaged in terms of its operation!) how much it overheats for some people, but I like to have it warn me it's getting close to 50C. The notification's the important part there (so u can cool your eris), not the clock speed.
@pkopalek I like your settings you posted with a full description of each. I changed my settings to yours and give it a day or so and will report a status update as to performance quality
I've never lagged at 160mhz =p but that could just be my phones/ roms.
Hungry Man said:
I've never lagged at 160mhz =p but that could just be my phones/ roms.
Click to expand...
Click to collapse
my audio skips and it won't wake up when in a call at 160mhz. I keep mine at 245mhz minimum to keep phone working smoothly.
What does the different prioritys mean? Is that like what one its.focused on more?
Sent from my FroShedYo.V5 using XDA App
How do you guys clock your CPU so high? Whenever I try anything over 729 bad stuff happens. If I put it on 748 it lags and if i try 768 it freezes up. You guys are all using the droid eris right? What ROMs and kernels are you running? I'm on Kaosfroyo
sgbenton said:
How do you guys clock your CPU so high? Whenever I try anything over 729 bad stuff happens. If I put it on 748 it lags and if i try 768 it freezes up. You guys are all using the droid eris right? What ROMs and kernels are you running? I'm on Kaosfroyo
Click to expand...
Click to collapse
When a processor is made at the factory, it will always have flaws in it. The chip is tested to see what frequency it is stable at. So that is the speed that is stamped on the chip and the frequency that it is set at to operate for the consumer and not have any problems. When you overclock a processor, you are bypassing the frequency that the chip as been deemed to be stable at. After that, there is no set speed that your processor can handle, because each one is different according to the flaws it might have.
So in short (what I'm trying to say), the processor in your phone just can't handle those without causing problems. That's why when you overclock it, it's kind of a trial-and-error process to see what speed you can get out of it, but be careful, because too high can cause permanent damage.
Using Interactive governor
Main: 787/710
Temp > 42.1 C: 480/245 Priority: 100
Screen Off: 480/245 Priority: 95
Charging/Full: 480/245 Priority: 90
Took me 2 hours to figure out why my phone was lagging out even more than it was prior to root. Slow dialing, lagged texting, lagged screen on, etc. Once I reverted back to "moto_hotplug" governor in SetCPU, everything is perfect.
Sent from my DROID3 using Tapatalk
That's strange my default setting in setcpu was ondemand and all is well
I was experiencing the same issue every time I turned my screen off, except my phone would completely freeze and my only option was pulling the battery. Finally I discovered it was the one profile in SetCpu that was set to clock down and scale to ondemand when the screen was off.
Can anyone confirm that clocking down with profiles works as long as the scaling is ondemand?
djdmbrwsk said:
Can anyone confirm that clocking down with profiles works as long as the scaling is ondemand?
Click to expand...
Click to collapse
I tried that out and it doesn't seem to work even if I leave the scaling as moto_hotplug. It takes a few minutes, but it definitely completely freezes up.
djdmbrwsk said:
I tried that out and it doesn't seem to work even if I leave the scaling as moto_hotplug. It takes a few minutes, but it definitely completely freezes up.
Click to expand...
Click to collapse
Same here, but others are still reporting that they are underclocking with SetCPU just fine. I'm leaving it alone for now, since I'd rather overclock to be completely honest with you. My battery life isn't a problem at all. 17-21 hours on average unplugged before 10%. Perfectly fine for me.
Lyxdeslic said:
Took me 2 hours to figure out why my phone was lagging out even more than it was prior to root. Slow dialing, lagged texting, lagged screen on, etc. Once I reverted back to "moto_hotplug" governor in SetCPU, everything is perfect.
Sent from my DROID3 using Tapatalk
Click to expand...
Click to collapse
I can second this issue. I played around with a bunch of different settings and found it was most stable when the max was no lower than 800, but it still froze on occasion even with hotplug selected. Overall it seems SetCPU is not really compatible with the Droid 3.
I switched mine to Ondemand as well and it was quickly obvious the phone didn't like it. Quadrant scores dropped to 1000-1500 range. Setting back to moto_hotplug and Quadrant scores back over 2200 and everything is running smooth.
I learned this the hard way as well. I had it changed to the settings I used on my thunderbolt back then, using ondemand screen off 300 max 300 min. When Handcent received a message, texting would lag, etc and once I changed back to moto_hotplug everything was great again!
Sent from my DROID3 using Tapatalk
So just inherited my dads OG Droid. Currently rooted and runs Steel Droid (Mod Version 9000) and 2.6.32.9_RZ Kernel.
Phone is overclocked to 1GHz (125/1000 ONDEMAND).
Like the title says, the phone gets about 5 hours and then hit's 5% and keeps asking me to charge. If I charge it overnight and unplug it when it's 100%, it'll hit 90% idling (while I sleep) about 3 hours later.
Running Programs:
DSPManager
Words Free
Facebook
3D Digital Weather Cloc
News & Weather
3G Watchdog
Videos
SoundHound
Pandora
Temp+CPU V2
Now out of all the running apps, Pandora, Soundhound, News & Weather, 3G Watchdog, Temp+CPU, 3D Digital Clock are all widgets. Temp+CPU and 3D Digital clock are the only ones that actually run, the rest are just there in case I want to use them.
These stats today are from using Pandora for about an hour over Wifi.
Any ideas? Phone runs fine most of the time but I have seen the occasional lag where you have to click something 10 times before it opens.
I used to have a pretty big problem with battery life too, but even though I think they are somewhat silly and annoying the Easy Battery Saver app helped me quite a bit.
Wifi and using the speakers are heavy on battery life. Not sure how much difference it will make but try consolidating your widgets and app shortcuts to as few screens as possible.
Also your CPU governor might be set to something that lets the phone hog through anything at the sacrifice of battery. When i set my CPU to Performance my phone runs like a boss, while setting it to battery saver I get a little more lag but more battery, obviously. Not sure how/if your ROM will let you change that but it's something to look into.
I got it set to On Demand which might be the issue. The kernel is a low voltage kernel. How do ultra low voltage kernels run?
I did a battery calibration, downloaded Advanced Task Killer (Battery saver didn't work well, I'd always have an issue with 3G not activating) and got rid of all my widgets. Currently charging it up completely, I'll check it out tomorrow.
So the title is incorrect, it says 5 hours and 5% left. I checked the battery info at 5%. It said 4hr 4x min. About 10 minutes later it shut off so I didn't even get 5 hours to a full charge.
I don't have high expectations but coming from an Alias 2 that had the extended battery (I'd get a week of battery with my use), this is pretty disappointing.
Well I can tell you now, ondemand is NOT good for battery, what that governor does is make it so the CPU will go from MIN to MAX speed slots depending on what the phone needs, AFAIK it doesn't scale with need, it just goes to max. So your phones CPU was running at max most the time which kills battery.
Can't say anything about your ROM, but I use simply stunning 5.6 http://www.droidforums.net/forum/chevyno1/177728-ss-5-6-2-3-7-incl-1-battery-other-goodies.html Which, with his low voltage 1ghz kernel set to the smartass governor, I get anywhere from 8-14 hours of battery life depending on use. Using ultra low voltage kernels depend on your phone, some phones have trouble overclocking to 800mhz mid-voltage (mid-voltage is considered to be the most stable, but use the most battery), others can overclock to 1.25ghz ultra-low voltage, which is very rare. I would say try out all the different voltage kernels and see which one works best with your phone.
Also task killer = MAJOR MAJOR No no! The task killer will kill the apps, and the android OS will restart them, using more CPU time and making the battery actually not last as long, I would recommend learning how to use the supercharger script http://forum.xda-developers.com/showthread.php?t=991276
Can't say much about the majority of programs you have running, but I've found facebook does not like to play nice with the Droid, also, why use the 3D clock when the Droid comes with a built in-clock app? Pandora uses a lot of battery, so running it w/ the ondemand governor is probably what hurt your battery there.
Not many Droid users left out there, but I was and still am an extremely avid Droid user, so if you have any more questions just shoot me a PM and I'll help as much as I can.
Thanks! I got rid of all my widgets and installed Chevy's ultra low voltage 1.1GHz kernel on smartass. I lost 20% battery pretty fast but let's see how long it runs. I've had no force close issues so far. I'm a bit tempted to go to 1.2GHz ulv.
How much does the ROM have to do with battery life? I really love this ROM and it's interface. I thought the battery life really only had to do with kernels.
I also got rid of the clock widget and put a default clock widget. What's the built in Android one? Is that the "Analog Clock"?
Sorry for all these questions, I'm pretty new to Android. Only had this for 2 days (~8-10 recharges...)
Its fine, better to question and learn then to just get mad and over it, and Roms have everything to do with battery, they are just like kernels, some work AMAZING on some phones, while others can destroy battery life.
Like my rom, I found the perfect one for my phone, I get 8- (been thinking about it more) 20 hours of battery life on mine and it has pretty amazing performance too with the occasional hiccup.
And I thought you had the clock app installed for an alarm, not for a widget, my bad. I don't use a clock widget so I wouldn't know.. Also, I've found its not very good to run many widgets on the Droid, as it has limited memory and can only handle so much.
Well I got sick of it and reflashed the entire ROM. CPU governer is set to ONDEMAND 125/1000. Only*widgets I have are a simple clock (like the iPhone lock screen) and power control. Gonna see how it goes. So far so good but I'm saying that because I didn't loose 20% overnight. If I can clear the day, I'm good.
googlelover, what CPU Governer did you find to work the best with your phone?
I have been an Android owner for a while now, with the Droid being my first. Until recently battery life had always been an issue for me. Undervolting has never had an effect over a 20% improvement. And this is only when it's in deep sleep. Otherwise, in very general terms, undervolting can require a higher current aka worse battery life if you use your phone a lot. With undervolting comes the risk of data corruption in your phones memory and SD Card. What really kills your phone is screen on time, wakelocks, CPU overclock, and signal quality.
The last you have no control of. But if you're overclocking 1GHz or higher you have to realize that's almost twice the manufactured clock speed. As far as wakelocks, this is when something keeps your phone from going into a low power state. This can happen because of a rogue app, a buggy ROM, or having too many widgets. I ran into a ROM a while ago on my Fascinate that would stay awake if you had GPS enabled. The best you can do with your display power usage is to keep your brightness down. Hope this explains a few things
have the same issue
core2kid said:
Well I got sick of it and reflashed the entire ROM. CPU governer is set to ONDEMAND 125/1000. Only*widgets I have are a simple clock (like the iPhone lock screen) and power control. Gonna see how it goes. So far so good but I'm saying that because I didn't loose 20% overnight. If I can clear the day, I'm good.
googlelover, what CPU Governer did you find to work the best with your phone?
Click to expand...
Click to collapse
I already told you, the smartass governor, and like I said before, ondemand is not a good governor in my opinion. There are way to many factors in battery life to have anyone else be able to truly help you with it, all our phones are different and it really just takes time switching kernels, switching ROMs, etc to find what works with your phone
Sorry googlelover, I forgot you already said that.
So update guys. I've been going a day (so like 18 hours) of use after which it finally hits the 15% warning.
What I did:
Basically I reflashed the ROM and started from scratch. Before reflashing, I wiped the user data/cache/davick cache etc at least twice just to make sure it was really wiped.
I reflashed SteelDroid 9.0 with the default chevyno1 lv 1ghz kernel and gave it a go with just a simple clock widget. Worked well. One by one, I'm starting to install applications until I can figure out what was draining the battery fast. So far, so good. If I can get 18 hours on a 2 year old battery, I'm going to be doing fine with my extended battery.
One thing I did notice was that the phone back by the camera (where CPU is) isn't getting as hot as it used to. Makes me think that the phone was at a high clock speed in sleep. Another issue may have been my CPU temp/speed monitor. It was probably poling the CPU stats every second which made the phone increase the CPU speed because it sensed activity.
Try out the ROM I'm using. I absolutely love it. The interface is phenomenal and it runs very well.
htp://w w w . d r o i d f o r u m s . n e t /forum/steel-droid/148060-release-steel-droid-9-0-gingerbread-11-17-2011-a.html
(remove the spaces to see it, I wasn't able to post links normally because I don't have enough overall posts).
There's probably other ROMS that run better like the one googlelover is using, but I can't use the default Android interface anymore after using this.
core2kid said:
Sorry googlelover, I forgot you already said that.
So update guys. I've been going a day (so like 18 hours) of use after which it finally hits the 15% warning.
What I did:
Basically I reflashed the ROM and started from scratch. Before reflashing, I wiped the user data/cache/davick cache etc at least twice just to make sure it was really wiped.
I reflashed SteelDroid 9.0 with the default chevyno1 lv 1ghz kernel and gave it a go with just a simple clock widget. Worked well. One by one, I'm starting to install applications until I can figure out what was draining the battery fast. So far, so good. If I can get 18 hours on a 2 year old battery, I'm going to be doing fine with my extended battery.
One thing I did notice was that the phone back by the camera (where CPU is) isn't getting as hot as it used to. Makes me think that the phone was at a high clock speed in sleep. Another issue may have been my CPU temp/speed monitor. It was probably poling the CPU stats every second which made the phone increase the CPU speed because it sensed activity.
Try out the ROM I'm using. I absolutely love it. The interface is phenomenal and it runs very well.
htp://w w w . d r o i d f o r u m s . n e t /forum/steel-droid/148060-release-steel-droid-9-0-gingerbread-11-17-2011-a.html
(remove the spaces to see it, I wasn't able to post links normally because I don't have enough overall posts).
There's probably other ROMS that run better like the one googlelover is using, but I can't use the default Android interface anymore after using this.
Click to expand...
Click to collapse
Don't forget not many roms have the default android interface, many have themes to completely change the look, if your happy where your phone is, great! But if you ever feel like your phone is slowing down again, I'd still recommend looking around and flashing some different roms.
Thanks, I'll keep that in mind. I'm only using this phone for another couple months. I'll be getting the Droid 4 when it comes out. Looks like a really nice phone.
I've been running CM11 (feb 14 build) now for about 2 weeks with terrible battery drain during use. The phone gets really hot when i'm just browsing facebook or reading a news app.
I looked at the CPU usage and it seems it's either at max cpu, min cpu or deep sleep. That is strange first of all, it never or rarely uses the frequenceis in between. Then i took a look at the battery graph. When the phone is sleeping, the battery is holding really steady, but as soon as I start using it all hell breaks loose and the graph looks like an olympic downhill slope. The strange thing is that the main battery source is the screen which is odd beause on stock (With better battery life compared to this) Android System was the main battery killer.
I then took a look at BetteryBatteryStats. First thing i noticed: 50-50 deepsleep and awake which is pretty astounding.
The wakelocks are msm_hsic_host and PowerManagerService.Wakelocks. But this is strange because it's still pretty much a clean install.
So my theory is that the CPU governor is not functioning propperly and blasts to max cpu as soon as a wakelock is requested and when the phone is in use it also blasts max cpu. I don't know.. that's just what I think is happening with the data i have.
Any ideas?
Updated section:
After clearing cache through recovery and doing a hard reset, the uAh has gone back to 3142000. Standby time seems good with the battery losing 7% overnight. It does charge quite quickly from 0-100 in about 2h. The previous heating issue remains with cpu monitors showing that the cpu jumps to high clock when I touch the screen. I don't see any change in which apps use the most battery with the screen taking up the most as before the problem started.
The heat appears to be what is draining the battery but I can't find any single app that causes it to ramp to max.
Pictures:
No-frills is set to stock settings to see how the phone handles the actions
2nd picture is when phone is idle
3rd picture is immediately after swiping through a few tabs and scrolling through some pages in the app which causes cpu clock and load to increase
Old sectionFor when battery uAh was low)
I've had this Z1 for about 11 months. I can only get around 2.5h on screen time with regular usage. The battery uAh was only 1848000 Recently it fell to the 1700s. Calibration appears to reduce the value further. The phone seems to heat up in about a minute or two no matter what app is running.
The phone is rooted on stock 4.4.2
I have tried updating to Lollipop before but received an error due to rooting, so I don't think anything changed.
bump
alantay11 said:
bump
Click to expand...
Click to collapse
sounds like it's time for you to replace your battery.
You may try to disable the "input boost frequency"
By default when you toch the screen, cpu frequency of two cores instantly jumps to around 1400 to preventing any lag but it seems to use more power and causing heat
I have disables this and since then I'm no longer have any heat issue and also the battery life is so much better now but you may exprience a little lag while scrolling on heavy web pages but thats all
Btw i'm on .157 and using Kernel Adiutor for cpu tweaks
You may disable this by the app mentioned above or by editing sys.somc.touch_perf_kick=1 from 1 to 0 in buid.prop or adding this line