SetCpu - Hero CDMA Q&A, Help & Troubleshooting

Hi, installed Setcpu but cant get the option to boost it faster than 528, is there a setting on it for getting it close to 600+?
Thanks

You'll have to be running a custom kernal to take advantage of over clocking. The stock kernal will be limited to stock speeds.
Hey... I think this thing makes phone calls too!

If SETCPU>menu>auto-detect does not list speeds greater than 528, then that is the highest that your ROM/Kernel supports. What ROM are you running?

Unfortunately Im on the stock 2.1

Deltatristar500 said:
Unfortunately Im on the stock 2.1
Click to expand...
Click to collapse
Root then and get a deca kernel on there!
-----
Sent from my CDMA Hero. I got some hot Froyo-on-Hero action here!

user7618 said:
Root then and get a deca kernel on there!
-----
Sent from my CDMA Hero. I got some hot Froyo-on-Hero action here!
Click to expand...
Click to collapse
so drop the kernel on my rooted stock 2.1 and then I can crack the speed on it?

Deltatristar500 said:
so drop the kernel on my rooted stock 2.1 and then I can crack the speed on it?
Click to expand...
Click to collapse
You'll have to save it in the root of your SD card, boot to recovery, wipe dalvik and flash it there. More info here

I don't know if deca's kernels work with sense or not. Beezy420 on AC has an oc kernel posted in his honey bun thread, I believe.
-----
Sent from my CDMA Hero. I got some hot Froyo-on-Hero action here!

when I go to revcovery mode, I get a black screen with a triangle and an exclamation
nvm, got into recovery

You need to flash a custom recovery. I'm assuming you didn't search or read the wiki.

Yes Deca's kernels work on 2.1 & 2.2 sense roms . Just to let u know
user7618 said:
I don't know if deca's kernels work with sense or not. Beezy420 on AC has an oc kernel posted in his honey bun thread, I believe.
-----
Sent from my CDMA Hero. I got some hot Froyo-on-Hero action here!
Click to expand...
Click to collapse
Sent from my DROIDX using XDA App

FdxRider said:
Yes Deca's kernels work on 2.1 & 2.2 sense roms . Just to let u know
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Good call. I wasn't sure.
-----
Sent from my CDMA Hero. I got some hot Froyo-on-Hero action here!

MrCoolHand said:
You'll have to save it in the root of your SD card, boot to recovery, wipe dalvik and flash it there. More info here
Click to expand...
Click to collapse
hmm, I only have a couple options on recovery
1 reboot
2 apply sdcard:updatezip
3 wipe data
4 wipe cache
thanks it

Deltatristar500 said:
hmm, I only have a couple options on recovery
1 reboot
2 apply sdcard:updatezip
3 wipe data
4 wipe cache
thanks it
Click to expand...
Click to collapse
Have you flashed a custom recovery image like clockwork or amon ra? That sounds like the stock one.

MrCoolHand said:
Have you flashed a custom recovery image like clockwork or amon ra? That sounds like the stock one.
Click to expand...
Click to collapse
thanks, no I have not...will look at getting one of those..Im really new at all this so bare with me.

From a new to this standpoint the easiest thing to do is search the market for "Rom Manager" download the free version and there should be an option to flash Clockwork to your phone. It will do all of the work for you.
Then reboot into recovery, and you will have the option to Flash/Apply Zip.
For a Sense rom the best kernal I have found is still Zen's no perf lock kernal, a quick search should pull it up. It eliminates the screen lag in Sense that typically occurs when the screen is off, answering calls, and typing. No other kernal has ever come close to it when I run sense roms.
It will let you overclock and undervolt with a wide range of speeds. I get great performance out of 345 low 729 high with on demand while the screen is on, then set a profile in set cpu for the screen off to be 245 to 480 (allows music/pandora to play without issue while conserving battery).
Just some helpful stuff for you.

indiscriminant said:
From a new to this standpoint the easiest thing to do is search the market for "Rom Manager" download the free version and there should be an option to flash Clockwork to your phone. It will do all of the work for you.
Then reboot into recovery, and you will have the option to Flash/Apply Zip.
For a Sense rom the best kernal I have found is still Zen's no perf lock kernal, a quick search should pull it up. It eliminates the screen lag in Sense that typically occurs when the screen is off, answering calls, and typing. No other kernal has ever come close to it when I run sense roms.
It will let you overclock and undervolt with a wide range of speeds. I get great performance out of 345 low 729 high with on demand while the screen is on, then set a profile in set cpu for the screen off to be 245 to 480 (allows music/pandora to play without issue while conserving battery).
Just some helpful stuff for you.
Click to expand...
Click to collapse
thanks for the reply

thanks, worked like a charm with the Zen kernel, and with set cpu set at 345 low 729 high, yet Restaurant story seem to still lag a but at 729, most be all the folks at me restaurant. Oh well.

How do I minimize the lag from turning on the screen and useing the device on the home screen. I turn it on, there looks like there is a bit of a pause for the CPU to relize the screen is turned on and to switch to the 345 low 729 high setting (on demand) instead of the lowest setting to 345 for (screen off). The dely is a bit annoying since I can move to the other screens left or right from the home screen. Its like the phone freezes for a few seconds

Deltatristar500 said:
How do I minimize the lag from turning on the screen and useing the device on the home screen. I turn it on, there looks like there is a bit of a pause for the CPU to relize the screen is turned on and to switch to the 345 low 729 high setting (on demand) instead of the lowest setting to 345 for (screen off). The dely is a bit annoying since I can move to the other screens left or right from the home screen. Its like the phone freezes for a few seconds
Click to expand...
Click to collapse
Go into your display settings and turn off Screen animations. (I have mine on some and it seems fine though)
Also, take the stock android clock/weather widget and remove it.
Then re-apply the widget again and when it gives you the option to keep its animation on turn it off as well, by default when the Rom is loaded it is on. For some reason that seems to always cause me lag when first getting the screen on. I think it is due to whenever it loads it checks the weather, the last time it showed, and then decides if it wants to do the animation or not. Unfortunately our Hero's just don't process that too fast.
Also as a new person go to this link, about half way down http://wecravegames.com/forums/gadg...sion/34-~~~official-android-thread~~~-67.html
It is a gaming forum I am also on and I answered a basic question on terms for rooting etc that may be of help to you.

Related

overclock widget

worked great for a while then kept force closeing anyone haveing problems??
It seems to be working fine for me. One thing is that when I set the clock to 128 or something, the status displayed on the widget still shows 527. The performance is significantly slowed so I assume it's doing it's job.
Overall I think it's a nice little widget. Great for maxing out performance, and maxing battery life by limiting performance.
Phone:
Black G1
JF 1.51
Yup...me too
I will make the change but it sometimes does not refresh the gui. It will also not work if you reboot. (if i remember correctly) also tons of force closes. I am on 6.01 and have tried JF1.5 and am curently on HERO but have not had success with the widgets on the build yet so I dont have a confirmation.
Could someone post the previous version of this app please? The updated version on the market shows "problem loading gadget" on the Hero rom when you add it to the screen..previous versions worked without any problems. Thanks in advance.
edit: nm..fixed it..just had to run the odex optimization script and all is good again
just use SETCPU from market...its more stable thank open overclock......at least it doesnt unclock back to 384mhz
what is a good configeration for over clock..i dotn want to mess up my phone??
I was thinking the same and should I have it on always max. Or what?
I've got mine set to 128Mhz min and 527Mhz max, it has drastically increased my battery life. Batter life barely drops 1% overnight.
Anyone have the Version before the 1.7 update. The new update doesnt seem to work on hero w/ Rosie.
You can grab the 1.6 apk from the Dev's Google Site (check the Files section).
1.7 doesn't work with Ion for me either
zgmf-x322a said:
just use SETCPU from market...its more stable thank open overclock......at least it doesnt unclock back to 384mhz
Click to expand...
Click to collapse
Did setcpu support choosing a different freq. when the screen is off? Setting that to 128 - 245 has helped my battery greatly. One question for anyone using OC apps, does your phones at any time run at a lower freq than what's specified as the maximum? I just set my phone to (with the screen on) to 128 - 384 because if I put it all the way to 527 it won't come down (unless I turn the screen off).
masr1979 said:
Did setcpu support choosing a different freq. when the screen is off? Setting that to 128 - 245 has helped my battery greatly. One question for anyone using OC apps, does your phones at any time run at a lower freq than what's specified as the maximum? I just set my phone to (with the screen on) to 128 - 384 because if I put it all the way to 527 it won't come down (unless I turn the screen off).
Click to expand...
Click to collapse
1.2.0 does not currently.
I swear, the next version will (I swear!). I'll also add some basic battery profiles (if battery is less than 50%, set the speed to something) and a profile for charging. Of course, it'll always be free here (link in my sig).
does your phones at any time run at a lower freq than what's specified as the maximum? I just set my phone to (with the screen on) to 128 - 384 because if I put it all the way to 527 it won't come down (unless I turn the screen off).
Click to expand...
Click to collapse
Yes. You can usually catch it by doing cat proc/cpuinfo in ADB. It depends on what the phone is doing at that moment.
That's strange it doesn't work well with hero. Since I'm using haykuros adp1.5hr3 it workd beautifully, but the regular overclocker app doesn't even budge and I uninstalled that..idk tho, probably a build issue as far as I'm guessing.
IronCross1788 said:
That's strange it doesn't work well with hero. Since I'm using haykuros adp1.5hr3 it workd beautifully, but the regular overclocker app doesn't even budge and I uninstalled that..idk tho, probably a build issue as far as I'm guessing.
Click to expand...
Click to collapse
The creator of the original Overclock app hasn't updated his application for even Cupcake build support yet. I thought he removed it from the market.
masr1979 said:
Did setcpu support choosing a different freq. when the screen is off? Setting that to 128 - 245 has helped my battery greatly. One question for anyone using OC apps, does your phones at any time run at a lower freq than what's specified as the maximum? I just set my phone to (with the screen on) to 128 - 384 because if I put it all the way to 527 it won't come down (unless I turn the screen off).
Click to expand...
Click to collapse
Yeah NeoBlade (thanks!) gave me the tip on that one yesterday. Seems to be helping a ton.
Min384Max527
Screen off Min128Max245
I can't find Overclock Widget in Market, was it removed?
I have the Overclock Widget and my question is, is it bad for my phone that while my screen is on i have it a min 527 max 527 then while screen off min 128 max 245... I've noticed that phone charges last longer but the useage of going back and forth determental to the phone? Thanks
coolbho3000 said:
1.2.0 does not currently.
I swear, the next version will (I swear!). I'll also add some basic battery profiles (if battery is less than 50%, set the speed to something) and a profile for charging. Of course, it'll always be free here (link in my sig).
Yes. You can usually catch it by doing cat proc/cpuinfo in ADB. It depends on what the phone is doing at that moment.
Click to expand...
Click to collapse
Thanks, that would be of great help. Specially the battery profile settings. If you could also put a monitor, be it a widget or something on the notification bar it would be beyond awesome, or maybe a just notification of when the speed is changed and to what it was changed to.
Does anyobdy know if this SETCPU works on Hero ?
And must the app be on after i set the clock or can i close the app after ?
*bump* need to know

JAC kernel bug: using audio randomly kills phone

(I figured to post this in Android Development as it wasn't really a fit for any other forum; and made its own thread since multiple ROMs and threads use non-stock kernels.)
I ran into an issue running JAC's OC/UV kernel, as detailed at http://forum.xda-developers.com/showthread.php?t=806116 . Essentially, whenever any kind of audio was playing, whether through headphones or the speaker, local media (i.e. mp3 player) or remote (i.e., Pandora), at some point the phone would just.. die. Capacitive buttons wouldn't light up, no unlock; music would die; and basically a battery pull was required to turn the phone back on. adb logcat reports nothing - you can see the audio streaming, then the logcat shut off with the phone.
Based on the thread above (and searching the Bionix thread), it seems that a non-stock kernel does this. (There are only a couple of posts out of the thousands on Bionix's thread.) I have not tested KingKlick's kernel, only JAC's; perhaps KK doesn't suffer from this. This issue is independent of overclocking/underclocking the phone (verified by setting JAC kernel to 1000/200, then uninstalling setcpu); Voodoo lagfix (verified by disabling lagfix and running audio for about an hour); and ROM (tested using multiple versions of Franken-Twiz and Hybrid - maybe there's an inherent issue with eugene's mods, but I haven't seen any other posts.)
I suppose this thread serves as a warning/bug report for anyone that might encounter this issue if running a non-stock kernel. The best way to resolve AFAIK is to revert to a stock kernel.
Thank you for posting this! My phone had suffered from this at random times since I started using JAC's kernel. I asked about it in a couple of threads but never got a single reply. Glad to know it's not only me
I'm running the same kernal and about 20 minutes ago running pandora my phone just turned off too and had to pull the battery to restart
Sent from bionix 1.9.1 jacs oc/uv kernel
Had that issue at the Gym the other day, not even on Bionix.
I had similar issues, also with the KK Kernel, its not just JAC's kernel. You don't have to pull the battery either to get out of the freeze, you can hold the power button for several seconds and it does a hard reset.
I have found though that the KK Kernel is less likely to do it if you set your setcpu to 400 min and 1000 max before using pandora. Those settings seems to have worked for me every time..also after setting up pandora make sure to fix permissions with rom manager.
Just a little work around, try it to see if it works for you.
Sent from my SGH-T959 using XDA App
Actually this is a known problem since even the G1.
If you have anything like setCPU, which I do, and you set the idle or lowest speed lower then 400 Mhz the phone will more then likely freeze up when playing music or when going to idle.
I don't remember off the top of my head what causes it to do this when it goes below that certain Mhz, but Im sure I or someone here can dig the old thread up.
Man without this thread I could never get pandora to work with a custom kernal. I setcpu at 400 min and 1000 max and not a single freeze. Thanks so much for posting that tip, you made my day.
Sent from my SGH-T959 using XDA App
Ive had this problem to.... but it was ONLY with Jacs 1.1, I revert every ROM back to his 1.0 and have no problems. Everytime I dont, I get a phone freeze.
I was having this problem with jac's newest kernel so I went back to his first OC/UV, it is a known problem and he's working on it according to his twitter. how I got around this is I used his OC script and got rid of setcpu, from what Quadrant says I'm still running 100/1200. Hope that helps you guys
jmercil said:
I have found though that the KK Kernel is less likely to do it if you set your setcpu to 400 min and 1000 max before using pandora. Those settings seems to have worked for me every time..also after setting up pandora make sure to fix permissions with rom manager.
Click to expand...
Click to collapse
Interesting. I'll try installing JAC OC/UV/Voodoo again and see if this observation is consistent.
r6kid said:
I was having this problem with jac's newest kernel so I went back to his first OC/UV, it is a known problem and he's working on it according to his twitter. how I got around this is I used his OC script and got rid of setcpu, from what Quadrant says I'm still running 100/1200. Hope that helps you guys
Click to expand...
Click to collapse
Yeah, I think the problem only exists when you use the OC kernel with setCPU, and setup setCPU under 400Mhz, other wise the kernel with out setCPU works just fine when it goes below 400Mhz.
Once again I don't remember why it does that but it has something to do with setCPU not being able to initialize properly after the phone goes idle and falls below 400Mhz.
Would have to agree. There's a bug somewhere. Not sure if its limited to jacs though.
Currently on masters rom kk. Only problem is pandora.
i had this problem too. kinda disappointed cause the kernels make everything run so much better. so i had to go back to using stock cause i listen to music a lot :/
There's definitely some hardware variability, because I can't recreate this bug. I listen to music all day long (MixZing, Slacker, Pandora) running 1.8 w/ JAC's OC/UV Voodoo. Never seen this.
Likewise with Jacs 1.1, had a couple other weird issues running that specific kernel too, not a single problem when I flashed back to 1.0
Sent from my T959 running Bionix1.9 with Jacs OC/UV and Voodoo
i get this same thing. ive had it happen with SetCPU both installed and not. right in the middle of a good song bam phone just shuts up. walk over to my toolbox and sure enough the phone is in a state of being divided by zero and only a battery pull lets it return to the world of the living. not greally a good thing when i have sevearl iphone dorks in the shop and they pop on over to my speakers and they say out of the way lets plug in a REAL phone. makes me want to scream LOL. ****ing iphone >_<
i retort with soooo when you get it out of the box....thats it right? nothing can be changed right? oh look that program sucks....what you cant make your own? ...yea...i thought so. hey look im making a call in the scrap room surrounded by 4ft thick concrete walls.... i got full bars lol. they got nothing in the empty parking lot cuz there holding it wrong LOL
Blkegk said:
Man without this thread I could never get pandora to work with a custom kernal. I setcpu at 400 min and 1000 max and not a single freeze. Thanks so much for posting that tip, you made my day.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Glad it worked for ya!
Sent from SGSV Bionix 1.9.1 KK OC/UV with the quickness!
sxfx said:
Yeah, I think the problem only exists when you use the OC kernel with setCPU, and setup setCPU under 400Mhz, other wise the kernel with out setCPU works just fine when it goes below 400Mhz.
Once again I don't remember why it does that but it has something to do with setCPU not being able to initialize properly after the phone goes idle and falls below 400Mhz.
Click to expand...
Click to collapse
I tried that though, as you can see in the thread I linked to above. Uninstalling SetCPU didn't help..
I think it's hardware.... One of the unlucky ones....
Try with a stock kernel. Jac and kk kernels do uv by default, which is like overclocking in reverse. It has the same possible stability issues.

[Q] Why does my hero keep restarting? (Gingerbread 2.3.2 aosp)

It always restarts automatically, when i make a call, the call just freezes and when i turn the phone on from standby to see what happen, well you guessed it, it restarts! its pretty annoying i went through 2 batteries today in 8 hours, because of the restarts. please help!
If your using the stock kernel I think its overclocked to 768 not sure though. Try one of dec's 691 kernel the #589 is my recommendation. Hope it helps good luck.
Root-Hack-Mod-Always™
jlopez512 said:
It always restarts automatically, when i make a call, the call just freezes and when i turn the phone on from standby to see what happen, well you guessed it, it restarts! its pretty annoying i went through 2 batteries today in 8 hours, because of the restarts. please help!
Click to expand...
Click to collapse
There could be a lot of things happening. The most common is that your running a clock speed higher than that which your phone can handle. Not all heros are created equal, mine for instance starts rebooting at anything higher than 691. Try a different kernel or if using setcpu or over clocking widget to lower your upper end clock speed. Your phone freezing when coming out of standby can mean your lower clock speed is too low. ASOPGB has JIT enabled by default as well. Go into the settings and turn it off, then reboot. You will just have to play until you find out what works for you. Good luck!
runngwlf said:
There could be a lot of things happening. The most common is that your running a clock speed higher than that which your phone can handle. Not all heros are created equal, mine for instance starts rebooting at anything higher than 691. Try a different kernel or if using setcpu or over clocking widget to lower your upper end clock speed. Your phone freezing when coming out of standby can mean your lower clock speed is too low. ASOPGB has JIT enabled by default as well. Go into the settings and turn it off, then reboot. You will just have to play until you find out what works for you. Good luck!
Click to expand...
Click to collapse
Set cpu or similar will not fix the issue, laie was right a capped 691 kernel is needed and probably a capped recovery as well. Btw jit is no longer default in gb, and jit would not cause reboots anyway.
sent from my hero, which no longer sucks ass
il Duce said:
Set cpu or similar will not fix the issue, laie was right a capped 691 kernel is needed and probably a capped recovery as well. Btw jit is no longer default in gb, and jit would not cause reboots anyway.
sent from my hero, which no longer sucks ass
Click to expand...
Click to collapse
Ahh thanks for the info, I had not gotten through all the new posts on the other ASOP GB threads. Good to know though. I have no tried out the rom, I plan to this weekend and my phone does NOT like kernels that clock above 691.

[Kernel] Dragon TEST... SetCPU profiles support...

http://www.tabbal.net/files/Dragon-Kernel-Voodoo-OC-v3.3-T1.zip
Dragon 3.2 w/ a fix that seems to work for setCPU screen off profiles setting the CPU to low values. Please note: The max freq in setCPU for that profile is what will be used, no scaling. I set it to 200Mhz and it's working fine every time I fire it back up.
The original patch is from here: https://review.source.android.com//#change,20804
Created by coolbho3k for the Nexus S, I backported it to Froyo. If we get good test reports from others, I'll push the changes to github tomorrow so other devs can use it.
When testing, please either use known good OC/UV settings, or don't OC/UV at all. Phantom OC/UV crashes won't help us know if this is working well for others. I've tested it with and without, turning my phone on/off like a madman... working fine so far.
Hmmm... early reports aren't looking good. Perhaps something isn't quite right. lol... Be warned if you try it, read all the comments. Might have to declare this one a fail. Too bad the NS cpu-freq driver is so different.. maybe I'll try pulling the whole thing over..
Downloading now report back tomorrow! This sounds promising.
Sent from my SGH-T959 using XDA App
Will test as soon as i get mine back to stock! Its just what I felt like doing today.
I did have a question..
Do we need to adjust it to say.. performance,on demand powersave? or will it just default?
just flashed it on my phone its been running warm hot even then after about 10 15mins of running it reboots
coolkid893 said:
just flashed it on my phone its been running warm hot even then after about 10 15mins of running it reboots
Click to expand...
Click to collapse
wow that can't be good. Sounds like the phone is overheating..
PaiPiePia said:
wow that can't be good. Sounds like the phone is overheating..
Click to expand...
Click to collapse
ya i know an its not even o/c its set to only max at 800mhz lol i think im gonna reflash to 3.2 to be safe but its a step in the right direction good try
Ok Im gunna have to try and install setcpu first.. otherwise my phone loads and restarts a few minutes into being on the desktop.
Testing now, Just UV'ed my clocks, and now setting profiles.
Observation so far:
SetCPU, and Uvolting seems to lock up my phone, and cause a reboot, and phone is pretty warm/hot.
Confirmed I can not run this either.
Couldn't use it. Phone would shut off as soon as scanning started. Kept happening everytime I tried to start phone :¬( going back to 3.2 has been stable at 1.4 ghz.
Sent from my SGH-T959 using XDA App
junxracr said:
Couldn't use it. Phone would shut off as soon as scanning started. Kept happening everytime I tried to start phone :¬( going back to 3.2 has been stable at 1.4 ghz.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Im having better luck using profiles with 3.2 than with this one. I've been using set cpu since 3.2 came out with no problems @1.4 and on powersave when screen is off. I have made no changes to the UV settings.
yikes ! i smell quadrant score in few min lemme install it
Has anyone got a "kernel panic" on this before? I'm not sure what I could have done wrong.. had to Odin back to stock. Forgot to back up before I flashed, shame on me. lol.
kernel panic wipes your data ? everytime kernel panicked on me i just restarted =D
bartek25 said:
kernel panic wipes your data ? everytime kernel panicked on me i just restarted =D
Click to expand...
Click to collapse
Nah, it didn't wipe my data. I had to Odin back to stock because I couldn't go into Clockwork Mod Recovery Mode. It would go into Kernel Panic and it reset all my launcher settings....
Was running hot for me also. Back to stock and then to bionix .
I think that when you get things fine tuned you will have a great Kernal.

[Q] Pandora streaming is choppy on my HTC hero CDMA (CM7 flashed)

I recently flashed the aospCMod-20110123 (gingerbread) on my sprint HTC hero. The upgrade has been awesome so far except for one really annoying issue. My pandora app hasn't been playing properly (I uninstalled and reinstalled the app). The music becomes choppy when the screen turns off. Reactivating the screen fixes the sound most of the time but it's really annoying. I haven't had this issue before with CM6.1 (froyo). Did anyone else see this issue ? I would greatly appreciate for any possible solution to this problem.
Thanks.
prashm said:
I recently flashed the aospCMod-20110123 (gingerbread) on my sprint HTC hero. The upgrade has been awesome so far except for one really annoying issue. My pandora app hasn't been playing properly (I uninstalled and reinstalled the app). The music becomes choppy when the screen turns off. Reactivating the screen fixes the sound most of the time but it's really annoying. I haven't had this issue before with CM6.1 (froyo). Did anyone else see this issue ? I would greatly appreciate for any possible solution to this problem.
Thanks.
Click to expand...
Click to collapse
If you are using the kernel that comes with the ROM:
Go into CM Settings and then performance.
Within CPU Settings, change the governor to ONDEMAND.
You'll have to reboot. If that alone doesn't fix your problem then bump you MIN CPU setting to 256.
What is your min set to? Probably needs to be bumped up to 264 or whatever.
poashll said:
If you are using the kernel that comes with the ROM:
Go into CM Settings and then performance.
Within CPU Settings, change the governor to ONDEMAND.
You'll have to reboot. If that alone doesn't fix your problem then bump you MIN CPU setting to 256.
Click to expand...
Click to collapse
Thanks for quick reply. However, I don't find the CPU settings option under Settings->CyanogenMod settings -> Performance. Is that enabled by a separate app that I may be missing ?
prashm said:
Thanks for quick reply. However, I don't find the CPU settings option under Settings->CyanogenMod settings -> Performance. Is that enabled by a separate app that I may be missing ?
Click to expand...
Click to collapse
If you flashed a different kernel, you will not see the option. If that is the case, you will need to use Setcpu or Deca's battery tweak.
Sent from my HTC Hero CDMA using XDA App
poashll said:
If you flashed a different kernel, you will not see the option. If that is the case, you will need to use Setcpu or Deca's battery tweak.
Sent from my HTC Hero CDMA using XDA App
Click to expand...
Click to collapse
Thanks poashll. I installed cputuner free app and restarted ph. That completely jacked my ph. I kept on getting "The process com.android.phone has stopped unexpectedly.." error. Nothing seemed to fix it. So I restored my cm6 backed up rom. Thank God that I had backed up my prev ROM. Then I downloaded and flashed the latest CM7 nightly build. This one had the CPU Settings option. Before I mess with it, I backed up my current configurations (it's a real pain in the butt to re-install all the lost apps and configurations). And then changed the governor to ONDEMAND. Now my pandora works great and battery life is still good!
Thanks a ton for all the help! I appreciate that.
hmmmm... I have been having the same problem since I installed ASOP gingerbread. and still have it with CM 7. adjusting the cpu settings work fine for me as long as I don't let the phone's screen go to sleep. but if the screen stays awake it's fine....
any other setting you suggest? kind of a waste of battery to be running pandora AND have the screen awake all the time.
noriyori said:
hmmmm... I have been having the same problem since I installed ASOP gingerbread. and still have it with CM 7. adjusting the cpu settings work fine for me as long as I don't let the phone's screen go to sleep. but if the screen stays awake it's fine....
any other setting you suggest? kind of a waste of battery to be running pandora AND have the screen awake all the time.
Click to expand...
Click to collapse
What settings are you using?
Sent from my HTC Hero CDMA using XDA App
poashll said:
What settings are you using?
Sent from my HTC Hero CDMA using XDA App
Click to expand...
Click to collapse
I set the governor to ONDEMAND and the MIN to 264. But like a dummy, I didn't set the 'Set on boot' option so my settings reverted when I rebooted...
How is the ondemand governor different than the standard interactive governor?
Mine is still on interactive, but the min is on 352. Anything lower than that for my phone, and it will skip when the screen turns off.

Categories

Resources