Database Develop

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.

battery dying while in sleep

i just noticed this yesterday. i was playing a game on it for like 20 min and the battery was normal, lost like 1 or 2% during those 20 min. but the next day i took it off the charger with a full battery and then but it on my belt and 15 min later i turned the phone on and the battery was at 89%!!!! since then i have been messing with it and the battery only dies that quickly when the phone is off. any suggestions? im running nfinitefx45's rom(never did this till i tried fresh's new rom yesterday)OC to 710 with task killer set to auto

cp0020 said:
im running nfinitefx45's rom(never did this till i tried fresh's new rom yesterday)OC to 710 with task killer set to auto
Click to expand...
Click to collapse
guessing that could be why :l

kyouko said:
guessing that could be why :l
Click to expand...
Click to collapse
but i switched back to nfinites rom to see if that fixed the battery but it didnt

What widget are you using for overclocking and what are your settings? Also I believe with Fresh Hero you cant overclock, or at least shouldn't since its still using the stock kernel.
Anyway, the cpu should already autoscale up or down depending on what you're doing.
If nfinite's rom has the stock kernel you can always flash a newer one that you can overclock > Check out this page

kyouko said:
What widget are you using for overclocking and what are your settings? Also I believe with Fresh Hero you cant overclock, or at least shouldn't since its still using the stock kernel.
Anyway, the cpu should already autoscale up or down depending on what you're doing.
If nfinite's rom has the stock kernel you can always flash a newer one that you can overclock > Check out this page
Click to expand...
Click to collapse
im using darchkernel v4 for nfinite and using setcpu. 512 min and 710 max, have it set to ondemand

512 is almost the stock Mhz limit (576 is i think), your min should be closer to something like 245 Mhz so its not using a lot of power while sleeping.

HOT battery~!

OK...so MUCH THANKS to Mr. Carlisle for gettin me all squared away with rooting my Hero and upgrading to Froyo 2.2. All back ups complete, apps downloaded and only major bug thus far is the camera...SO....why is my battery running at 105 degrees on average? What should the normal range be? I turn it on @ 6 am after charging to 100% and wiping battery stats and ten hours later recharge it to 100% (Currently @ 50%) and all day the temp has been between 103 and 105. whycome? HELP!

Pauper7 said:
OK...so MUCH THANKS to Mr. Carlisle for gettin me all squared away with rooting my Hero and upgrading to Froyo 2.2. All back ups complete, apps downloaded and only major bug thus far is the camera...SO....why is my battery running at 105 degrees on average? What should the normal range be? I turn it on @ 6 am after charging to 100% and wiping battery stats and ten hours later recharge it to 100% (Currently @ 50%) and all day the temp has been between 103 and 105. whycome? HELP!
Click to expand...
Click to collapse
Because on FRF91 on Cyanogen mod (which i assume you are using) is overclocked to 710 mhz, where the hero's processor runs at 528 normally. My suggestion is to download an app called overclock widget from the market, (Obviously, it's a widget and you'll have to add it to your homescreen) and set the minimum and maximum clock (processor) speed to 240mhz(min) and 518mhz [or 534, if you want to, but it won't make much difference] (max).
You can set the max (or minimum) clock speed to be more or less. Lower clock(processor) speed=More lag but better battery life, and potential to freeze your hero because the processor can't operate the system fast enough. Higher clock(processor) speed= Faster and less lag but less battery life and can damage your touch screen (It's happened to me). if you leave it at too high a clock speed for too long, and can also freeze your phone because your processor can't operate at that speed and crashes your phone.
It's up to you if you want to overclock or not, but you should keep it resonable, and if you have heavy phone usage, don't go much further than 613 mhz for your max. There is also another program called set cpu that is avalible for free for xda members, but is a paid app on the market. Using that, you can set your frequencies to the default hero processor, or of other phones. But overclocking over 710mhz could do some harm to your phone, so be careful.
If you say, "I wonder if this will damage my phone," then don't take the chance without asking around first.

If you have any more questions about overclock, pm me, and I can help you out.

That temperature range, ~40C is completely normal when charging and using at the same time (with me, anyway). I'm OC'ed to 710 and using undervolt, too. The highest I've ever seen mine go is 43C, or about 109F. I don't really know where the "danger zone" is, but if I had to guess it would be around 48C or higher.
Edit: I reread your post, and do you mean it's at 40C always, even when it's sitting doing nothing? If that's the case then follow Ryoma Echizen's advice and fine-tune your CPU speed.

[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!

[Q] Damaged CPU?

Suckerpunch Kernel on Serendipity 6.2
I was playing around with OCing to 1.3 after achieving a stable 1.2 OC, and stupidly set to boot settings instead of applying on accident. Had to turn phone off for a bit to save power, fast forward an hour when I turn it on; get a kernel panic on boot, do a battery pull & reboot; get to homescreen, fiddle around a bit, freezes, batt pull again, eventually (after 2 more kernel panics) figure out that I had stupidly set the settings to boot instead of applying. Could this have caused any damage or added any sorts of instabilities to my phone?

No it should be fine. As long as you put the OC level down to 1200 or 1000 (and also the Undervolt (UV) settings if you messed around with those) and to save that as the new boot setting, it should be alright.

venomio said:
No it should be fine. As long as you put the OC level down to 1200 or 1000 (and also the Undervolt (UV) settings if you messed around with those) and to save that as the new boot setting, it should be alright.
Click to expand...
Click to collapse
Yep, done that. I do have a question about the active states, though; are those the frequencies which the phone will utilize?

Typically yes, getting to 1200Mhz should be easy and no problem... It's really a balancing act.
http://forum.xda-developers.com/showpost.php?p=10936691&postcount=1102
This guide helped me get started at first, and it will definitely help you optimize your OC/UV settings.

venomio said:
Typically yes, getting to 1200Mhz should be easy and no problem... It's really a balancing act.
http://forum.xda-developers.com/showpost.php?p=10936691&postcount=1102
This guide helped me get started at first, and it will definitely help you optimize your OC/UV settings.
Click to expand...
Click to collapse
I've read that, yes, that's where I got started as well. However, I don't understand fully what the States option in Voltage Control does.

snapplefish said:
I've read that, yes, that's where I got started as well. However, I don't understand fully what the States option in Voltage Control does.
Click to expand...
Click to collapse
Selecting states in VC is what allows the phone to use that state. So if you set your max clock to 1200, but 1000 is the max state you have checked, the phone will only ever use 1000 as the max. You need to set both options.