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.

[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] dynamic overclocking

.
..

I use setcpu to do this.
Look into the governors, choose one.
Then choose the appropriate thresholds (in the advanced menu) for what you do.
It doesn't allow you to tweak per app, but tells the cpu governor at what %of cpu to move to the next cpu speed (up or down).
I set mine very low, as i care more about battery than performance. So my up threshold is like 95% or something.
But my down threshold is a lot more agressive.
But you do the opposite.
MuF123 said:
Hello,
my question is regarding dynamic overclocking. I've used the ones that raise the speed when under a load - but my question is -
Is there a way to return to stock clocks after certain time?
Explanation:
situation1: I want to check new single mail or open new single IM or check university's website for some news, I want the device to be FAST as possible, nevermind the battery.
situation2: I want to use maps/navigation/IM/games/web browsing for longer period of time (hours?) with the screen on. I don't need all the power when I play solitaire, text on IM or browse not-so-important news websites.
I think when I've seen the realtime clock displayed on my phone it jumped to max clock right after I've clicked almost anything on the screen. I want the speed-up, but after certain period of time to stop doing this in favor of the battery life-time.
Any ideas how to do this? Thanks!
Click to expand...
Click to collapse
Sent from my Milestone using Tapatalk

Yes, just throttle the cpu to give you more power when you are sluggish. That could work for you.
Me? I have my droid do 110 when screen is off (works quite well!), and then I FORCE the unit to 1000 when plugged in. Besides that i throttle the cpu based on battery power: more cpu power with more battery life. Makes my droid last longer.
I might want to add a throttle up when sluggish and not in my personal battery red zone and a throttle down when the cpu gets too hot period.
Any cpu frequencies that you all would suggest?

..

MuF123 said:
Thanks for the reply, but - think about this, I will start a 3D game, it will use 100% of the cpu so it would always stay at the highest possible frequency (+highest voltage). I don't want that.
Click to expand...
Click to collapse
I dont get it?
You dont want max speed in game? Why do you overclock?
If the game requires 100%, the it will (and should) clock up.
As soon as the game doesnt, it will clock down (depends on your threshold).
The only other i could see, is to change the max clock rate in setcpu before you play the game. This will ensure it doesnt clock higher than your choice, but requires a manual step.
But seriously, if your cpu is pegged at 100, why would you not want it to step up the higher speed?
Sent from my Milestone using Tapatalk

..

MuF123 said:
exactly - I don't want minimum battery in game, that's why I don't want to overclock.
actually from the nature of 3d rendering I think every game will run at 100%, but the situation when the game hits the frame limiter (not likely on milestone).
I want snappy performance while doing few quick tasks:
e.g.: new IM comes, I want to unlock, load the application, get to the IM, reply, lock. (40seconds)
or
taking phone from cradle - I want the phone to load homescreen fast, rotate the screen, open phone app, to look at last missed call and call back (20seconds).
Battery life won't be affected by 40 or 20seconds of ~1100mhz, okay.
And then I start a game for a prolonged time. It will run smoothly even on 550MHz, the additional frames I see are just waste of battery = I don't want that.
So now I have two options - either run at max speed and it will be always fast and it will drain my battery when I decide to play for an hour.
OR
I can use default speeds for longer battery life for everything and I will wait an hour to rotate the screen in browser or IM app.
Click to expand...
Click to collapse
You could compromise and find a max speed that you could undervolt to make it drain battery like stock. My 800mhz vsel is less than the default vsel @550. So the battery drain is less...
It requires some trial and error, but most "slight" overclocks (700,800; depends on the phone) can be configured to drain less than stock.
Of course, if you feel you need 1000 or 1100, this wont work as it requires increasing the vsel (or at least not decreasing it).
Sent from my Milestone using Tapatalk

Clocking problems

Hi,
first, I want to apologize for my bad english.
I have a problem with the clockingspeed of my HTC One.
I was impressed by how bad the battery life of the One is.
I found out, that the CPU is always clocking at 1,7Ghz, both values (Min AND Max) are set to 1.7 Ghz.
If I turn on the battery-safe option, it clocks at 1Ghz, but again on both values.
So, I have downloaded some CPU apps, which should let me change the clocking speed of the CPU.
Well, it works, but if I turn on "Set on boot", and reboot, the values are gone.
I thought, this would be caused by the stock ROM, so I have flashed the "InsertCoin" ROM, but no changes.
Has someone the same problem, or does someone has a solution for me?
regards.

The clock speed is dynamically controlled. When the phone is not in use, it should reduce the clock speed.
It sounds like you have an app that is preventing it from sleeping.
Install betterbatterystats and look for partial wakelocks. Feel free to leave a screenshot here.

Hi,
even if there is an app which would prevent my phone from clocking down, the MIN-value should be at 300/400mhz, and not be the same as the max-value ..
regards.

No idea..?

what hes saying is theres a rogue app mostly likely in the background thats pushing your phone that it thinks it should ramp up the speed of your phone. so even if you have it set to 384/1.7 the phone is detecting "oh **** *so and so* app is beastly bump the speed to max 1.7. bad analogy but you get the idea. i would start by wiping the phone install a brand new rom and DONT install anything just the mhz reader. then check. if your on a fully clean flash and still holding at max value all the time. then next is to check the CPU governor. it may have been set to performance at some point "accidentally" the performance governor forces the phone to hold at max speed. mostly only used for synthetic benchmarks.

Nope nope nope.
Nope.
I just had to S-Off my phone ..

Crazy overheating problems with Stock Kernel and even more with Stellar Kernel. Help?

Hello, I'm using Titan Stock ROM and it was working quite OK, but I noticed that with high CPU usage during longer periods of time (Like when you are calling on Skype with both webcams on) after like 5 minutes (depending on ambient temperature) the CPU throtling kicks in and you can barely end the call because the whole GUI of Android gets completely unresponsive.
Quick questions:
- What is the maximum "safe temperature" for the CPU to not break? 60ºC is way too less.. as it gets easily to that temperatures.
Now in hope of getting this a bit fixed I recently installed the "Stellar Kernel". I set the CPU settings as recomended on its kernel page (Undervolted to Min Freq. 98MHz and Max Freq. to 1190MHz). Now its just a nightmare. It overheats even quicker.. and when it throttles you can just pray to do anything.. (I changed finally to Min Freq to 385MHz but that doesn't helps much).
And on the other hand thanks to the underclocking the phone doesn't wants to wake up during minutes.. which is quite unpractical when somebody is calling you.. you can hear the phone ringing but you cannot accept the call because the phone doesn't want's to wake up. But that got somehow fixed putting it back to the Min Freq. +300Mhz.
Just want to know if somebody knows about some magic setting which allows the phone to function properly during longer time.. as far as I'm aware 1190MHz is the original maximum Freq. of this phone so no overclicking is done here. So it looks that the only way to have it working somehow decently is to underclock the maximum frequency and leave the minimum frequency high enough to work properly. I don't really care about battery anymore, as I just need the phone to be functional, and as it is now it's just not. Any advices? Thanks for any reply.

You probably have a hardware problem

rhp07 said:
Hello, I'm using Titan Stock ROM and it was working quite OK, but I noticed that with high CPU usage during longer periods of time (Like when you are calling on Skype with both webcams on) after like 5 minutes (depending on ambient temperature) the CPU throtling kicks in and you can barely end the call because the whole GUI of Android gets completely unresponsive.
Quick questions:
- What is the maximum "safe temperature" for the CPU to not break? 60ºC is way too less.. as it gets easily to that temperatures.
Now in hope of getting this a bit fixed I recently installed the "Stellar Kernel". I set the CPU settings as recomended on its kernel page (Undervolted to Min Freq. 98MHz and Max Freq. to 1190MHz). Now its just a nightmare. It overheats even quicker.. and when it throttles you can just pray to do anything.. (I changed finally to Min Freq to 385MHz but that doesn't helps much).
And on the other hand thanks to the underclocking the phone doesn't wants to wake up during minutes.. which is quite unpractical when somebody is calling you.. you can hear the phone ringing but you cannot accept the call because the phone doesn't want's to wake up. But that got somehow fixed putting it back to the Min Freq. +300Mhz.
Just want to know if somebody knows about some magic setting which allows the phone to function properly during longer time.. as far as I'm aware 1190MHz is the original maximum Freq. of this phone so no overclicking is done here. So it looks that the only way to have it working somehow decently is to underclock the maximum frequency and leave the minimum frequency high enough to work properly. I don't really care about battery anymore, as I just need the phone to be functional, and as it is now it's just not. Any advices? Thanks for any reply.
Click to expand...
Click to collapse
acquire kernels and other que rooms have different governors Study on them and the Best That was enough pro you and your needs .
I think this will help you , give will take this need to manually change the clock all, the governor will operate according to its governor preferably .
Read
http://androidforums.com/threads/android-cpu-governors-explained.513426/
:good::good::good::good::good::good:
Thanks if helped :highfive: