Database Develop

Cpu Slow After Root

I just rooted my HTC Hero (Sprint) Stock 2.1 and now I notice my Cpu is running slow. If I install SetCpu it speeds it up right away...Upon opening SetCpu I notice my Cpu speed says 245 mhz max/min. When I the refresh it it says 480/528 but after my screen turns off and back on it slows down again and returns back to 245 mhz. I never had this problem until after I rooted the phone. Why does my phone keep reverting back to 245 mhz and slowing down after I turn my screen off? Also it seems like my Battery life has gone down drastically...
edit: I intalled overclock widget and when I open it it also says 245 mhz. When I then set it up to 528 it makes my phone run fast again. As soon as I turn my screen off and back on it automatically reverts back to 245...

What ROM are you running? If it is not a ROM running an overclockable kernel apps like setCpu and OC widget will actually slow your phone down. If you would like to see your clock speed without this side-effect, I suggest SystemPanel.

The 245 is what it goes too when sleeping, give it a minute or so and you would see that change on the apps, although your phone should be doing it right away. I suggest running a rom with overclock, and setting screen off settings to 245 min and 528 max, does wonders for my phone coming out of lock
-------------------------------------
Sent via the XDA Tapatalk App

danaff37 said:
The 245 is what it goes too when sleeping, give it a minute or so and you would see that change on the apps, although your phone should be doing it right away. I suggest running a rom with overclock, and setting screen off settings to 245 min and 528 max, does wonders for my phone coming out of lock
Click to expand...
Click to collapse
Depends on the ROM. Fresh Toast 2.1 has issues with setCpu and several people have reported issues with recieving calls if the screen off frequency is enabled in OC widget. I disagree with the screen off frequency for non-overclockable roms. Several users of Fresh ROM, not just myself have accidentally left OC widget or setCpu on when switching from toast to fresh and have noticed the same symptoms. Flipz himself has also said the same thing, if you try to overclock a non-OC ROM you will actually underclock it to the point it is unusable.

I did say to do it on an overclocked rom. If it's a stock kernel, then do not mess with the frequencies, it's a fight, and kernel beats app every time, effectively stopping everything
till they agree
-------------------------------------
Sent via the XDA Tapatalk App

Cpu Stuck at 245mhz after Rooting Hero CDMA

I just rooted my HTC Hero (Sprint) Stock 2.1 and now I notice my Cpu is running slow. If I install SetCpu it speeds it up right away...Upon opening SetCpu I notice my Cpu speed says 245 mhz max/min. When I the refresh it it says 480/528 but after my screen turns off and back on it slows down again and returns back to 245 mhz. I never had this problem until after I rooted the phone. Why does my phone keep reverting back to 245 mhz and slowing down after I turn my screen off? Also it seems like my Battery life has gone down drastically...
edit: I intalled overclock widget and when I open it it also says 245 mhz. When I then set it up to 528 it makes my phone run fast again. As soon as I turn my screen off and back on it automatically reverts back to 245...

fifedogg said:
I just rooted my HTC Hero (Sprint) Stock 2.1 and now I notice my Cpu is running slow. If I install SetCpu it speeds it up right away...Upon opening SetCpu I notice my Cpu speed says 245 mhz max/min. When I the refresh it it says 480/528 but after my screen turns off and back on it slows down again and returns back to 245 mhz. I never had this problem until after I rooted the phone. Why does my phone keep reverting back to 245 mhz and slowing down after I turn my screen off? Also it seems like my Battery life has gone down drastically...
edit: I intalled overclock widget and when I open it it also says 245 mhz. When I then set it up to 528 it makes my phone run fast again. As soon as I turn my screen off and back on it automatically reverts back to 245...
Click to expand...
Click to collapse
Your phone going to 245 is completely normal. It only gives your phone power when it needs it, and sitting on Setcpu screen isnt going to make it throttle up. You dont want your phone running at 528mhz at all times. It will KILL your battery. Our phones have a setting of "Ondemand", like gives the power on demand, if its not demanding a lot of power it will go back down saving battery life, CPU life and keeping temperatures down.
If you have problems with the phone running slow, i recommend checking out an overclocked kernel. You can run it at stock speeds, if you dont feel comfortable running OC. But if you want the extra power, the choice is always there.

Sounds like something to do with conserving battery by dropping the cpu speed.
-------------------------------------
Sent via the XDA Tapatalk App

Had thr same problem in the beginning way back idk how i guxed it i guess its the stock rom idk
-------------------------------------
Sent via the XDA Tapatalk App

Well on a stock rom setcpu cant do anything other then read the cpu and it will only update when it is force refresh. If you want setcpu to be able to control or change your cpu speeds this will require installing a rom that is overclock enabled. There are several located on this forum.

For some reason SetCpu was doing this. I just set it back to 480/528 and rebooted it and then uninstalled SetCpu and now everything is fine. For some reason SetCpu was the cause of this. I reinstalled to make sure and sure enough it was happenening again. I'm glad I figured it all out

Yeah, apparently you decided to create a new thread instead of utilizing the response I gave to your thread last night:
If it is not a ROM running an overclockable kernel apps like setCpu and OC widget will actually slow your phone down. If you would like to see your clock speed without this side-effect, I suggest SystemPanel.
Click to expand...
Click to collapse
For future reference, anyone not using a ROM based on Toast's kernel DO NOT install an OC program. This is the typical behavior and it is not fun to deal with because you will have to be patient waiting for the phone to start up and open the OC program to set it back and uninstall. I believe that just uninstalling and rebooting is sufficient, but am not 100%.

lineman78 said:
Yeah, apparently you decided to create a new thread instead of utilizing the response I gave to your thread last night:
Click to expand...
Click to collapse
I actually made that thread at the same time last night. I didnt know where to put it exactly...

fifedogg said:
I actually made that thread at the same time last night. I didnt know where to put it exactly...
Click to expand...
Click to collapse
Aw, this must be the one from the Dev section and got moved over here. I noticed it over there, but had already posted on the one in Q&A... So now there are 2 in Q&A.

[Q] SetCPU unstable on Galaxy S?

I've done numerous tests with and without OC and on different kernels (both normal and custom). So far SetCPU have only given me headaches. Random crashes, unable to wakeup, kernel panics... The list goes on.
According to these tests I've come to the conclusion that SetCPU is very unstable on Galaxy S and should not be considered supported at all.
What's your experience with SetCPU on Galaxy S? Is it conclusive with mine? Do you experience the same problems with Overclock Widget, or is it more stable?

after using setcpu for a few weeks and getting similar problems, i removed it.
There is pretty much no use in it for this phone, they allready scale from 100mhz - max speed (even oc if you have one) automatically

mekwall said:
I've done numerous tests with and without OC and on different kernels (both normal and custom). So far SetCPU have only given me headaches. Random crashes, unable to wakeup, kernel panics... The list goes on.
According to these tests I've come to the conclusion that SetCPU is very unstable on Galaxy S and should not be considered supported at all.
What's your experience with SetCPU on Galaxy S? Is it conclusive with mine? Do you experience the same problems with Overclock Widget, or is it more stable?
Click to expand...
Click to collapse
Are you using a task manager? I had the same problem as you until I removed the auto task killer I had previously installed. Now I can set setcpu to 100000 min 1000000 max ondemand for main with a profile of screen off 100000 min 1000000 max conservative.

mekwall said:
I've done numerous tests with and without OC and on different kernels (both normal and custom). So far SetCPU have only given me headaches. Random crashes, unable to wakeup, kernel panics... The list goes on.
According to these tests I've come to the conclusion that SetCPU is very unstable on Galaxy S and should not be considered supported at all.
What's your experience with SetCPU on Galaxy S? Is it conclusive with mine? Do you experience the same problems with Overclock Widget, or is it more stable?
Click to expand...
Click to collapse
Yes. I have the same problem on my stock SGS.

Setcpu is not working good on sgs. Try to remove it, and you'll get better battery life.
Sent from my GT-I9000 using Tapatalk

I don't know of anyone who has tested it on the I9000 (and there may even be alternatives or the same thing floating around the development subforum), but they claim to have a 1.2ghz overclocked kernel here for the I9000. Maybe best to be avoided, but a 100% use at your own risk alternative, especially if you're a bit unsure on any of the translated steps, is available here.
http://translate.google.com/transla.../matpclub.com/board/index.html?id=tipn&no=144

been using it on a vibrant for about 10 days and had my first issue last nite - it froze the phone - had to remove battery to reboot, tried again, froze it again
i thought it was the last two apps i'd installed so i removed them, then there was an update, downloaded and installed, so i did a number of settngs changes, closing setcpu, running benchmark quad, reopening & changing settings etc
about half dozen times
and it's been fine so far -

I had the same issue. I would pull my phone out of my pocket and it wouldn't wake up. I could call my phone and it would ring but my phone would do nothing until I removed the battery and re-booted. This happened numerous times until I uninstalled SETCPU and it stopped doing that so I knew I found the culprit and haven't tried it again since (I need to receive calls as priority 1)

doesnt anyone search anymore i posted this issue over a month ago. setting cpu mode to anything on than conservative can cause freezes as the system doesnt get enough cpu to wake up.. it is even mentioned in set cpu to use conservative.

lgkahn said:
doesnt anyone search anymore i posted this issue over a month ago. setting cpu mode to anything on than conservative can cause freezes as the system doesnt get enough cpu to wake up.. it is even mentioned in set cpu to use conservative.
Click to expand...
Click to collapse
I have it set to Conservative on my Vibrant, and I'm having the same issues as the OP.
Edit: When I go into SetCPU after pulling the battery and resetting, it shows it's limiting my CPU to 19.2 MHz. Yes, 19.2. Insane.

tt4079 said:
Are you using a task manager? I had the same problem as you until I removed the auto task killer I had previously installed. Now I can set setcpu to 100000 min 1000000 max ondemand for main with a profile of screen off 100000 min 1000000 max conservative.
Click to expand...
Click to collapse
I killed my task manager service, and it didn't freeze up! I'm going to uninstall the task manager and see if I have any more freezing issues in the future.
Edit: Nope, didn't work. Removing SetCPU.

mekwall said:
What's your experience with SetCPU on Galaxy S?
Click to expand...
Click to collapse
I have the Vibrant version with T-Mo. After rooting, Titanium, Barnacle and Root Explorer all seem to be working fine.
After a few minutes of installing SetCPU, my phone wouldn't wake up. Rebooted twice, same results.
Removed SetCPU and the phone's working fine again. Maybe the minimum speed should be set at 250 or so?
George

To begin with, you don't even need SetCPU
SGS phone automatically regulates the speed of the CPU depending on your usage.
most of the time in Stock ROM it hover around 200 Mhz, very few times it uses the max 1000 Mhz
only when there are lots of background apps running
when you runt he CPU at 1000 Mhz it gets hot fast, and it consumes more battery
good thing is it drops back down to 100~200 Mhz as soon as it's done with the heavy tasks
so having the SetCPU installed will defeat the whole purpose of power saving and CPU cycle on demand
mekwall said:
I've done numerous tests with and without OC and on different kernels (both normal and custom). So far SetCPU have only given me headaches. Random crashes, unable to wakeup, kernel panics... The list goes on.
According to these tests I've come to the conclusion that SetCPU is very unstable on Galaxy S and should not be considered supported at all.
What's your experience with SetCPU on Galaxy S? Is it conclusive with mine? Do you experience the same problems with Overclock Widget, or is it more stable?
Click to expand...
Click to collapse

I don't even remember the last time where we had a fixed clock on a cpu Allgamer. The point of setcpu is to either downclock or overclock your cpu. You might want to limit your clock to 0.6GHz just to save some juice.
Anyway, after a few hours of head scratching and 2 reboots, I uninstalled and refunded it.

I agree. Setcpu is rather unstable. I have feeling lots of the kernel overclockers have problems but blame the kernel while they should blame setcpu

i have just installed setcpu. it's probably been about a day or so now and i have not experienced any problems?
i have an Australian model (I9000) just flashed to the canadian firmware for the 3br fix.
Is it just generally not recommended to use setcpu on my SGS?
please advise. Thanks

toansta said:
i have just installed setcpu. it's probably been about a day or so now and i have not experienced any problems?
i have an Australian model (I9000) just flashed to the canadian firmware for the 3br fix.
Is it just generally not recommended to use setcpu on my SGS?
please advise. Thanks
Click to expand...
Click to collapse
It depends on what you're using it for. If you know what you're doing, it can be a useful tool. If you want to overclock, you'll want setcpu. If you want to underclock (lets say you're out and about, with 40% battery), then you can set the maximum cpu speed lower so that the battery will last longer.
You don't need setcpu if you're simply going to tell it that you want your max speed to be 1ghz, with a min of 100mhz and you want it to be "conservative". Your phone does that by default, and frankly the SGS is pretty good on its own when it comes to battery management.

thanks reuthermonkey, i will keep that in mind.

What are the perfect setcpu 2.0.3 settings for froyo JP6 I9000 rooted? Thanx in advance

Telanis said:
I have it set to Conservative on my Vibrant, and I'm having the same issues as the OP.
Edit: When I go into SetCPU after pulling the battery and resetting, it shows it's limiting my CPU to 19.2 MHz. Yes, 19.2. Insane.
Click to expand...
Click to collapse
Menu and rescan the device should restore the normal values. those values are not the ones actually used!

[mod] Avoid random freezing w/ OC kernels

this is for those who have been discouraged from OC kernels due to random freezing. Some vibrants (like mine) dont OC well and randomly freeze, also the heat up to 100+ degrees Fahrenheit quickly. ive tested this w/ kingklick's kernel and been running freeze free for a couple days and staying under 92 degrees and i get really good Bat life....(FB, Push Exchange Email & Twitter running in background, ESPN scoreboard widget, LWP, texting all day, plus wifi on w/ pandora running------60% battery on a class/workout day which is 9am-6pm)
Im running this w/ a stock Vibrant firmware thats rooted... (No i aint running a deodexed Stock ROM)
No u cant have a OC Kernel w/ leaked Firmware
Dwnload SetCPU (if you dont have it already)
OC to 1200MHz
- Create Profile in SetCPU for Temp > 50.0C and make it 800/200 w/ a Conservative Cpu governor.. (if u use OnDemand or make it the bottom number 100MHz, u will still freeze up.)
- Create Profile in SetCPU for Screen Off and and make it 600/200 w/ a conservative CPU governor..(if u use OnDemand or make it the bottom number 100MHz, u will still freeze up.)
Remember: Doing anything to ur phone is at ur discretion....u will b a sad panda if u blame me for u messing up ur phone

Cool thanks for this. I'm one of the unlucky ones my phone gets super hot when OCing. Going to try this out and report back if it successful.

boimarc89 said:
this is for those who have been discouraged from OC kernels due to random freezing. Some vibrants (like mine) dont OC well and randomly freeze, also the heat up to 100+ degrees Fahrenheit quickly. ive tested this w/ kingklick's kernel and been running freeze free for a couple days and staying under 92 degrees and i get really good Bat life....(FB, Push Exchange Email & Twitter running in background, ESPN scoreboard widget, LWP, texting all day, plus wifi on w/ pandora running------60% battery on a class/workout day which is 9am-6pm)
Im running this w/ a stock Vibrant firmware thats rooted... (No i aint running a deodexed Stock ROM)
No u cant have a OC Kernel w/ leaked Firmware
Dwnload SetCPU (if you dont have it already)
OC to 1200MHz
- Create Profile in SetCPU for Temp > 50.0C and make it 800/200 w/ a Conservative Cpu governor.. (if u use OnDemand or make it the bottom number 100MHz, u will still freeze up.)
- Create Profile in SetCPU for Screen Off and and make it 600/200 w/ a conservative CPU governor..(if u use OnDemand or make it the bottom number 100MHz, u will still freeze up.)
Remember: Doing anything to ur phone is at ur discretion....u will b a sad panda if u blame me for u messing up ur phone
Click to expand...
Click to collapse
im going to try these settings, hopefully they will improve my battery life...

I'm gonna try this on my cappy. Heat wasn't an issue, but it would freak out and hardfreeze on me constantly, especially under 3d testing.

just a quick question, what is an unsafe temperature to be running the phone at? mine is typically in the high 90s but it gets to 102 when charging

normally it should get around 95 w/ heavy use

Just pulled it off the charger and since it slowed to 800mhz it seems to be doing fine. As soon as it cools i'll run a quadrant/stresstest and report back.

speedysilwady said:
just a quick question, what is an unsafe temperature to be running the phone at? mine is typically in the high 90s but it gets to 102 when charging
Click to expand...
Click to collapse
boimarc89 said:
normally it should get around 95 w/ heavy use
Click to expand...
Click to collapse
Mine got up to 108 on stock everything when I first got it and everything seemed fine...

Phone got quite upset again. Hardfroze on quadrant.But i am also using a completely different kernel than you guys, so i wouldn't count my opinion for much.

Thanks for the settings. I just set it up, will let it run throughout the night and will repost status report tomorrow.

Seems to work here. Nice find.
EDIT: I take it back. it hard freezes on my vibrant. Running euge's touchwiz3

Your phone does not support overclock even though it has the same everything . Mine froze at 1.2ghz

gravis86 said:
Mine got up to 108 on stock everything when I first got it and everything seemed fine...
Click to expand...
Click to collapse
Mine gets to 122° running @ 1.4ghz been running this way since nov 2010. Had no problem thus far .116° is what samsung says to not let it get past

Some phones are just not going to allow oc. But this may help some ppl be able to oc.

Setcpu Profiles

Hey guys, I want to know what should I set my profiles to in order to save battery but at the same time keep the device running fast?

I use 648 max 192 min on ondemand, and I have no problem running anything at all, including Sense 3.6.

But how is your battery life and what rom are you using?

phil15_92 said:
But how is your battery life and what rom are you using?
Click to expand...
Click to collapse
End the day roughly at 60% battery. Just on a rooted version of Telstra's stock ICS, fully odex'd.

any of you guys see that setcpu always asks for permission from su
i remember from my inspire days that it didnt do that...

I have mine max 1026000 min 594
Profiles-- screen off max 540 min 486
Conservative

randong said:
any of you guys see that setcpu always asks for permission from su
i remember from my inspire days that it didnt do that...
Click to expand...
Click to collapse
I see it. Every so often it pops up at the bottom of the screen that it has acquired root permission. I'm concerned that something is causing setcpu to restart unnecessarily.