Overclocking and phone calls

[hydrogenman]

I get great battery life on my overclocked droid unless I'm on a phone call.

I'm running SM 2.0.3 and an overclock at 800 mhz


I have about 30 minutes of call time, my battery's at 40% (was at 100 when I took it off charger), and the battery monitor says about 68% of the battery use is from the phone call.

30 minutes of phone time shouldn't drain 50% of a full battery charge (roughly based on math).

Perhaps I have a profile set incorrectly...any ideas?

[bizzshow]

thats probably your problem try dont know ive never had that issue but i know my phone keels over when using some apps

[phenley]

Originally Posted by hydrogenman I get great battery life on my overclocked droid unless I'm on a phone call. I'm running SM 2.0.3 and an overclock at 800 mhz I have about 30 minutes of call time, my battery's at 40% (was at 100 when I took it off charger), and the battery monitor says about 68% of the battery use is from the phone call. 30 minutes of phone time shouldn't drain 50% of a full battery charge (roughly based on math). Perhaps I have a profile set incorrectly...any ideas?

Just use SetCPU to set to like 500mHz max/250mHz min on sleep/standby, and that should fix the problem (as you know screen turns off when you are on the phone). At least it did for me. I only set the profile that high because when it was lower I was getting pretty slow wake up times when receiving a call when the phone was asleep

[hydrogenman]

Originally Posted by phenley Originally Posted by hydrogenman I get great battery life on my overclocked droid unless I'm on a phone call. I'm running SM 2.0.3 and an overclock at 800 mhz I have about 30 minutes of call time, my battery's at 40% (was at 100 when I took it off charger), and the battery monitor says about 68% of the battery use is from the phone call. 30 minutes of phone time shouldn't drain 50% of a full battery charge (roughly based on math). Perhaps I have a profile set incorrectly...any ideas? Just use SetCPU to set to like 500mHz max/250mHz min on sleep/standby, and that should fix the problem (as you know screen turns off when you are on the phone). At least it did for me. I only set the profile that high because when it was lower I was getting pretty slow wake up times when receiving a call when the phone was asleep

My profiles are as follows

Charging
550 max
550 min

Sleep/Standby
250 max
250 min

Power < 50%
550 Max
250 Min


Normal settings on main page

800 Mhz max
550 Mhz min


I'm using the ondemand CPU governor with set on boot


Thoughts?

what CPU governor should I use?

[jasonb]

Originally Posted by hydrogenman Originally Posted by phenley Originally Posted by hydrogenman I get great battery life on my overclocked droid unless I'm on a phone call. I'm running SM 2.0.3 and an overclock at 800 mhz I have about 30 minutes of call time, my battery's at 40% (was at 100 when I took it off charger), and the battery monitor says about 68% of the battery use is from the phone call. 30 minutes of phone time shouldn't drain 50% of a full battery charge (roughly based on math). Perhaps I have a profile set incorrectly...any ideas? Just use SetCPU to set to like 500mHz max/250mHz min on sleep/standby, and that should fix the problem (as you know screen turns off when you are on the phone). At least it did for me. I only set the profile that high because when it was lower I was getting pretty slow wake up times when receiving a call when the phone was asleep My profiles are as follows Charging 550 max 550 min Sleep/Standby 250 max 250 min Power < 50% 550 Max 250 Min Normal settings on main page 800 Mhz max 550 Mhz min I'm using the ondemand CPU governor with set on boot Thoughts? what CPU governor should I use?

ondemand is the governor we should be using. it is meant to respond to cpu demands and ramp up speed when needed and will slow down when not needed.

[Shad0w325]

Lower your min on normal settings. There is no reason for the CPU to always run at 550MHz+. This is my setup and I have great battery life.

Normal
1000 Max
250 Min

Charging
1000 Max
250 Min

Sleep/Standby
550 Max
250 Min

Power < 40%
550 Max
125 Min

Battery > 45.5C
550 Max
125 Min

CPU Governor: On Demand

[dbutters]

Can anyone offer an explanation of the advanced settings? Also, what do the 'set on boot' options do? Should I add SetCPU to my task manager's ignore list?

[thrashtrash]

Originally Posted by dbutters Can anyone offer an explanation of the advanced settings? Also, what do the 'set on boot' options do? Should I add SetCPU to my task manager's ignore list?

absolutely otherwise you will keep killing the process and returning to the normal clock of 550 i believe, but im not sure thats exactly what happens but i always add it just to be safe and i havent had any problems

[BayouFlyFisher]

Originally Posted by dbutters Can anyone offer an explanation of the advanced settings? Also, what do the 'set on boot' options do? Should I add SetCPU to my task manager's ignore list?

I can't answer your question, but there is a website under the About button. I went to it once, but don't really remember much as I setup Setcpu a long time ago.

[LrdElderon]

advanced settings let you customize the ondemand govenor. if you change the powerbias option or the upthreshold % you can change how much load before the cpu ramps up speed to save power by not having it run 100% just because an email came in.