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
Related
I'm not sure the time refresh but no matter what I overclock the device to it will reset back to default (180mhz) within an hour or less. This happens in both manually in omap software and the startup smartkey.ini. Either way the device will hold the overclock temporarly while the device zips by, but sooner or later it clocks back to 180!
I'm running pdaviet4, how are your experiences?!
The same! CRAP!!!
you guys need to make sure to use omapclockplus for this functionality. When i used it i never had a problem
nottoosmart said:
you guys need to make sure to use omapclockplus for this functionality. When i used it i never had a problem
Click to expand...
Click to collapse
Using underground edition with omapclockplus occasionally drops the overclock and I need to reset it. But for the most part sticks with it.
The only annoying part is you don't know when it drops untill you need to do something that uses some juice and your device hangs forever
I use battery status to overclock
And it works fine
For some reason smartskey does not work well for overclocking on the wm6 and wm5 AKU3 roms
jocool said:
And it works fine
For some reason smartskey does not work well for overclocking on the wm6 and wm5 AKU3 roms
Click to expand...
Click to collapse
I agree. I have now disabled OmapClock via SmartsKey and use Battery Status. Seems to work flawlessly.
Andy
yeah same used both and battery status is the best choice for me
This sounds strange to me ! I never had problems with omapclock and smartskey. And I ran it on every rom, including several wm6.
I often use my pda for short periods, but i usually play very long times (call of duty 2 for instance, which needs a lot of ressources to be playable) with no problems. Also tomtom is fluent each time i use it (if i try to use it not OC'd then I can feel the difference)
so for me, so far, no problem with omapclock v.2 and smartskey in wm6
nottoosmart said:
you guys need to make sure to use omapclockplus for this functionality. When i used it i never had a problem
Click to expand...
Click to collapse
Both Omapclock+Omapclockplus or Omapclock+Smartskey make me default frequency after manual suspend and wakeup (by key press) and overclocked frequency after automatic suspend (by timeout).
Now trying Batterystatus, it seems is able to keep the device overclocked forever. Checking for battery drain.....
Vladimyr said:
Both Omapclock+Omapclockplus or Omapclock+Smartskey make me default frequency after manual suspend and wakeup (by key press) and overclocked frequency after automatic suspend (by timeout).
Now trying Batterystatus, it seems is able to keep the device overclocked forever. Checking for battery drain.....
Click to expand...
Click to collapse
same Batterystatus FTW
I want to thank you guys for the battery status tip! its been running rock solid and the battery info is good to know too
As for the overclock i turned off the string in smartskey.ini and let battery status take over. WM6 still seems to reset the clock when the device is in standby (you can notice this real quick when waking the device and notice the Mhz change) but battery status has the option to re-set the clock to the overclock specificed on wakeup. Great little app!
I suppose its a little savior WM6 defaulting the clock in standby... in the end, it saves juice!
First of all, for anyone who has not yet tried the new Manhattan Project 1.6ghz kernel by Team Whiskey, i suggest you do so (http://ip208-100-42-21.static.xda-developers.com/showthread.php?t=821514). It is currently in alpha but so far has gotten outstanding feedback. Ive personally been running it and I'm not looking back.
Up until now its been well known that SetCPU profiles not only dont work on our phone, but also causes crashes and severe instability. However, SINCE I FLASHED THIS NEW KERNEL (and running Bionix Fusion 1.1), I have successfully profiled my phone. Here is what I've been running all day with absolutely no issues, and my phone running like LIGHTNING:
Main: 1600-200 Conserv.
Screen Off: 200-200 Conserv.
Temp > 50: 800-200 Conserv.
I posted these results in the kernel forum, but I also wanted to post them here for everyone to see because i know that the lack of SetCPU profiles has been a major complaint around here. If anyone would like to try this out and verify that it works for them also with this kernel, please post here, so everyone can finally enjoy the beauty of overclocking AND underclocking.
Once again, I'm running Manhattan Project Kernel and Bionix Fusion 1.1
Outstanding!
Appreciate the profiles. Should be a great help. I personally lowered my Temp to 40c but thats just my opinion
Excited to get the running will tell results soon!
So had my phone sitting for a bit, it became unresponsive and i think it had something to do with the sleep profile. I went ahead and changed it to 400/200 conserv for testing.
Awesome. But is the set on boot option still not working?
Oh and just an educated guess bit I would figure no Voodoo on this kernel. So disabling just in case before I update
YatimaMeiji said:
Awesome. But is the set on boot option still not working?
Click to expand...
Click to collapse
i dont even bother, its not really needed....even if its unchecked yoru settings are preserbed upon reboot
----------------
UPDATE #2: after 5 hours of no problems my phone finally started crashing, so i have may have spoken prematurely. But I'm stubborn, so Im still gonna try every damn combination possible until my phone tells me to go f*ck myself haha
I will post my feedback as well...
OP, are you running any lag fixes?
drizze99 said:
I will post my feedback as well...
OP, are you running any lag fixes?
Click to expand...
Click to collapse
OCLF Ext2 v2.2
--------
I'm also trying "Overclock Widget" to see if i get better results
As much as I love Overclocking to 1600ghz, my it is beautiful....id also feel much more comfortable being able to underclock when its sleeping.........this is probably a wild goose chase, but i dont care, im bored at work
With screen off 200/200, phone does not wake up, changed to 400/200, still no wake up. Both set to conservative. Disabling profiles for now.
EDIT: Found the problem, if you enable Performance scaling on the main tab, and switch it back to conservative, it really doesn't switch. This is what was causing my Vibrant to not wake up! I had to set it to on-demand, leave setCPU and switch it to conservative, before it would stick. Re-testing 200/200 screen off.
TopShelf10 said:
OCLF Ext2 v2.2
--------
I'm also trying "Overclock Widget" to see if i get better results
As much as I love Overclocking to 1600ghz, my it is beautiful....id also feel much more comfortable being able to underclock when its sleeping.........this is probably a wild goose chase, but i dont care, im bored at work
Click to expand...
Click to collapse
you realize that the phone does this automatically, right?
turn on set cpu with nothing going on in the background and just let the phone sit. it will drop down to 200mhz and stay there.
the profile setting for temp is a good idea, but screen off is just going to cause lag issues. if the screen is off and the phone isnt doing a sync or something else, you can bet its probably chilling out at 200mhz
jnp1974 said:
With screen off 200/200, phone does not wake up, changed to 400/200, still no wake up. Both set to conservative. Disabling profiles for now.
EDIT: Found the problem, if you enable Performance scaling on the main tab, and switch it back to conservative, it really doesn't switch. This is what was causing my Vibrant to not wake up! I had to set it to on-demand, leave setCPU and switch it to conservative, before it would stick. Re-testing 200/200 screen off.
Click to expand...
Click to collapse
probably not going to help, but i certainly hope it does!!!
TopShelf10 said:
probably not going to help, but i certainly hope it does!!!
Click to expand...
Click to collapse
Thanks for the hope, it worked. YEAH! It now wakes when it should, and profiles appear to be working just fine.
EDIT: I was testing different benchmarks with scaling on conservative, on-demand and performance to see if they altered my benchmark results. The difference was minimal, but I forgot to change scaling back to conservative and it wouldn't wake. When I pulled the battery, rebooted and checked SetCPU, it said conservative, but was stuck on performance. Changed to on-demand, left SetCPU, back in and changed to Conservative. It worked.
jnp1974 said:
Thanks for the hope, it worked. YEAH! It now wakes when it should, and profiles appear to be working just fine.
Click to expand...
Click to collapse
dont be fooled, it can often work for a while before it shows its ugly side, be patient
I've never had any problems with profiles? The only thing that needs to be kept in mind is that if you check "set on boot" you'll get errors. Anything but "conservative" for scaling will give you errors.
edit: for screen off don't be so stingy trying to set it to 200/200, if you need more battery life then get a bigger battery or spare batteries or Juice Defender , I usually set it to 200/800 and I have no issues.
TopShelf10 said:
dont be fooled, it can often work for a while before it shows its ugly side, be patient
Click to expand...
Click to collapse
I was fooled, ditching profiles altogether, boo
Can conferm that both profiles and set on boot work.
Sent from my Vibrant.
Mouahmong said:
I've never had any problems with profiles? The only thing that needs to be kept in mind is that if you check "set on boot" you'll get errors. Anything but "conservative" for scaling will give you errors.
Click to expand...
Click to collapse
i never check set on boot....what are your profile settings and what ROM/kernel are you running?
OK, I don't have mine OCLF yet but so far so good.
I have run Sleep profiles of 200/200 and 400/200 and the phone wakes up every time. I have gotten a txt message as well during my test and the screen lit up just like Bionix should! Will continue to kep messing with it....
turbosix said:
you realize that the phone does this automatically, right?
turn on set cpu with nothing going on in the background and just let the phone sit. it will drop down to 200mhz and stay there.
the profile setting for temp is a good idea, but screen off is just going to cause lag issues. if the screen is off and the phone isnt doing a sync or something else, you can bet its probably chilling out at 200mhz
Click to expand...
Click to collapse
if it does so automatically then why is there an option to adjust "screen off" values?
Setcpu automatically scales between the high/low you set. SO if you let the main value stay at 1600-100..when the screen is off it will scale at a lower value of course cus you're not using the phone..but it wont stay at 200, because it has a Max of 1600! So depending on background processes it could scale back up to 4 or even 600 while screen is off
MY suggestions:
Download superpower battery saver from market, tweak to turn data on/off with screen and force ondemand cpu scaling
Download Autokiller--donate to get extra functions-- and set the value to Extreme or Ultimate when screen is off and Moderate or Optimal when it is on
I did that without setcpu profiles and it took 4 1/2 hrs to go from 81 % to 70
Im running Fusion 1.1 w/ Manhattan Project
im using serendipity 4.0.1, and rGB-v.4-Voodoo #10, im new to UV the phone, but i search in the post and found a template, i applied it and save it as boot setting, when i pressed the back button and open the app again, the values reseted, how do i maintain them?
The values reset because you didn't hit "Apply for now".
"Apply for now" applies the values until you reboot the phone and "Save as boot setting" saves your settings for everytime the phone boots up.
So, either put everything back in and hit "Apply for now" or restart the phone. I recommend erasing your bootup settings and hitting "Apply for now" so you don't end up in a boot loop if your settings are not stable.
how do i erase my bootup settings?
i dont know how to set up my voltage control app, it keep crashing on me
also consider the battery life for normal usage when oc ...
im not trying to over clock, i just want to save on battery but i cant seem to set up Voltage Control without crashing, i dont know what to do anymore, i cant set it up!!
hernan078 said:
im not trying to over clock, i just want to save on battery but i cant seem to set up Voltage Control without crashing, i dont know what to do anymore, i cant set it up!!
Click to expand...
Click to collapse
Try going to adb shell and removing it, and then reinstalling it. If that doesn't work you might just need to reflash Serendipity.
Auridran said:
Try going to adb shell and removing it, and then reinstalling it. If that doesn't work you might just need to reflash Serendipity.
Click to expand...
Click to collapse
i think the problem is not the app, is the values im using, i dont know what to do, i was pumped to using voltage control to save battery!
hernan078 said:
i think the problem is not the app, is the values im using, i dont know what to do, i was pumped to using voltage control to save battery!
Click to expand...
Click to collapse
Have you tried lower values? Does it do the same thing?
I lower the values and it works, for a while, when i press the lock button i wait 2 minute or less and the phone crashes and i have to do a battery pull out!
hernan078 said:
I lower the values and it works, for a while, when i press the lock button i wait 2 minute or less and the phone crashes and i have to do a battery pull out!
Click to expand...
Click to collapse
What values are you using? Not all the processors in the phones are created equal, and some don't like to be run very far out of spec.
I would recommend to start conservatively.
Note: If u r using OC based kernels, try not to reduce much voltage from any step over 1200. I think I read in some post there (probably glitterballs' kernel related one) that 1200 and 1280 both use same voltage levels. So its best to be conservative on that end.
Values I regarded as safe are 100, 100, 75, 50, 50, 50 (bottom to top), and the ones I am currently using are 125, 125, 100, 75, 75, 50 (bottom to top), and I have my speed capped at 1000 (since this is sufficient for my needs).
diablo009 said:
I would recommend to start conservatively.
Note: If u r using OC based kernels, try not to reduce much voltage from any step over 1200. I think I read in some post there (probably glitterballs' kernel related one) that 1200 and 1280 both use same voltage levels. So its best to be conservative on that end.
Values I regarded as safe are 100, 100, 75, 50, 50, 50 (bottom to top), and the ones I am currently using are 125, 125, 100, 75, 75, 50 (bottom to top), and I have my speed capped at 1000 (since this is sufficient for my needs).
Click to expand...
Click to collapse
Im using rGB-v.4-Voodoo #10 Kernel, and i put the values you posted, but it crashes on me, do i need to change my kernel or something like that?
hernan078 said:
Im using rGB-v.4-Voodoo #10 Kernel, and i put the values you posted, but it crashes on me, do i need to change my kernel or something like that?
Click to expand...
Click to collapse
Your phone may just not be quite capable of those undervoltages. It might not be capable of any undervolting at all. Remember, undervolting is running the processor out of spec. It's all luck of the draw if you get a processor that is from the top of the bin or a processor that is from the bottom of the bin.
Auridran said:
Your phone may just not be quite capable of those undervoltages. It might not be capable of any undervolting at all. Remember, undervolting is running the processor out of spec. It's all luck of the draw if you get a processor that is from the top of the bin or a processor that is from the bottom of the bin.
Click to expand...
Click to collapse
but it doesnt matter what kernel im running? if i use a kernal that dont support UV, i cant UV? The kernel im using, support undervolt?
hernan078 said:
but it doesnt matter what kernel im running? if i use a kernal that dont support UV, i cant UV? The kernel im using, support undervolt?
Click to expand...
Click to collapse
As far as I know, every kernel that supports overclocking for the Captivate supports undervolting. I know for a fact the kernel you're using does.
Auridran said:
As far as I know, every kernel that supports overclocking for the Captivate supports undervolting. I know for a fact the kernel you're using does.
Click to expand...
Click to collapse
And what you suggest is the problem? :S
hernan078 said:
And what you suggest is the problem? :S
Click to expand...
Click to collapse
Like I said, your CPU probably can't handle the level of undervolting you're trying to give it. Also, some peoples' phones can't even reach 1.28GHz (the stock clock of the kernel you're using) without undervolting at all, so your problem could easily lie there, unless you've limited the clock to 1GHz in Voltage Control.
hernan078 said:
Im using rGB-v.4-Voodoo #10 Kernel, and i put the values you posted, but it crashes on me, do i need to change my kernel or something like that?
Click to expand...
Click to collapse
Is it crashing for the values in green too? They were supposed to be very conservative, and the ones I regard as "safe".
And like "Auridran" quoted, try limiting speed to 1000.
Edit: I would recommend u starting with 25 for lower speeds, and try not reducing voltage at speeds over 800.
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.
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.