Whenever i overclock my htc wildfire device (running jokerdroid 4.2 without any kernel modifications, the included standard nFinity), my device will freeze and i will have to restart my device by popping the battery out and in again
if i make the overclock set at boot, it will freeze upon boot ofcourse
this will happen with every overclock app i've tested so far
since the kernel supports overclocking, i can't really find a solution myself.
why does it freeze,and how do i fix it?
yes, i gave it superuser powers, ofcourse xD
Thanks already.
How much are you o/c'ing by?
Every device is different some run fine at 768 and slightly above others cannot. Its not that the kernel supports o/c but more enables it then its up to you to find the right balance for your phone.
Sent from my HTC Wildfire using xda premium
Scratch0805 said:
How much are you o/c'ing by?
Every device is different some run fine at 768 and slightly above others cannot. Its not that the kernel supports o/c but more enables it then its up to you to find the right balance for your phone.
Sent from my HTC Wildfire using xda premium
Click to expand...
Click to collapse
from 710 to 768, but jokerdroid must be able to oc to that clockspeed, also, on cm7, i actually WAS able to oc to 768mhz using an app but also through the performance tweak settings that cm7 has
Does seem strange to me that you can't o/c across roms I'm fine on any rom at 768, have you tried lowering it a bit to see if it doesn't freeze? Try the 690 setting, I've put mine back to 576 as battery life seems better there and as I hardly ever stress the phone I don't even notice a difference in speed.
Sent from my HTC Wildfire using xda premium
seems to freeze after a random amount of minutes after i make setcpu be ignored at advanced task killer, not instant anymore
i'll try deleting advanced task killer then, else, i give up
if so, thanks for helping
btw, every change makes it freeze, under- or overclock
No point having an auto task killer, they just create problems and use more battery than without, by all means having one installed to make it easier to kill troublesome apps easier is not a bad thing but autokill is just the wrong way to do it.
Sent from my HTC Wildfire using xda premium
i didn't say it's auto.....
Related
I have been bouncing back in and forth from rom to rom. Most are great. Warm 2.2, DamageControl, and Virus (currently running). The issue I'm having is no matter witch rom or kernal I run on my Evo froyo, every time I install Setcpu within a couple of hours my launcher (no matter witch one) stops working. I have gone into root to reinstall, install and uninstall and nothing works. All Rome are affected by what I can tell. I'm finding the problem to be with setcpu. I'm surprised if can't find much information on this. Does anyone have ideas?
Sent from my Evo using Tapatalk
Yea, setcpu can improve things but also causes issues elsewhere. I was using launcher pro for a while, and using that in conjunction with setcpu gave me nothing but poor battery life and terrible freezing. I have since then stopped using setcpu and my phone works fine. Besides the difference between 1ghz and 1.1-1.2 is negligible on the Evo unless your benchmarking imo
sent from my DAMN Evo!!
Stop putting your phone's minimum frequency at 128 or 245MHz. Also, tweak your launcher's memory settings properly.
drmacinyasha said:
Stop putting your phone's minimum frequency at 128 or 245MHz. Also, tweak your launcher's memory settings properly.
Click to expand...
Click to collapse
I did all that already. I had my screen off set to 384mhz, im no novice, setcpu has great benefits but has some negatives also.
OP, try ziggys 10/26 kernel. It has scripts that handle oc'ing up to 1.13ghz using interactive governer WITHOUT using setcpu
sent from my DAMN Evo!!
I use SetCPU and Launcher Pro Plus and have used these 2 on every ROM I have used...which is a LOT!! My screen off is set to 245 and I OC to around 1228. I have NEVER had any issues on amy ROM. I dont know what is causing your issue but it isnt SetCPU and Launcher Pro....
[Q] cm7 cpu setting or setcpu?
well atm i am running an evo 4g with cm7 and i just switched my kernel to savaged zen and it's running great. my phone was rebooting on its own w/ the regular cm7 kernel i think its b/c i was using setcpu and people are saying it messes up cm7.
so i was wondering if anyone knew if i can use setcpu with cm7 and savaged as the kernel or if it's possible to make profiles on the cpu settings on cm7 i saw some1 post somewhere that you can but they never explained how.
p.s. please also visit this thread on battery life
AFirst of all, all SavagedZen kernels are Havs kernels (as far as I remember, I'll double check in a few). Anyway, if you are using a Havs kernel, changing cpu settings is pointless/counteractive. I would either leave the settings alone or switch to a no-havs kernel. You can check in settings>about phone.
EDIT: However, if you must mess with the settings, you can find them in Cyanogenmod Settings under Performance Settings. I don't know of a way to set profiles from that screen, though - only max/min & governor.
hi i have an evo running cm7 and i had setcpu and my phone kept restarting however i looked up setcpu again in the market and it said that they just ran an update to stop the problem with cm7, does this mean that setcpu is better to use than the cpu setting in cm7?
Green_Arrow said:
hi i have an evo running cm7 and i had setcpu and my phone kept restarting however i looked up setcpu again in the market and it said that they just ran an update to stop the problem with cm7, does this mean that setcpu is better to use than the cpu setting in cm7?
Click to expand...
Click to collapse
You shouldn't need setcpu use the cpu setting in cm7. They put it there for a reason, those guys are sharp!
I still use setcpu because I like my screen off profiles etc. You should update your setcpu if it prompted you to. I think the latest changes were for cm7/GB.
Sent from my PC36100 using XDA Premium App
Yes but it doesn't let u make profiles unlike setcpu, or does it?
I believe the profiles is definately the most useful
Sent from my PC36100 using XDA Premium App
It says it was for cm7
Sent from my PC36100 using XDA Premium App
I believe the SavageZen governor is a specially tweaked/optimized version of the SmartAss governor.
And if you use Smartass/SavageZen governor, I think it also automatically undervolts when sleeping, and essentially mimics what a screen-off profile in SetCPU would do.
plainjane said:
AFirst of all, all SavagedZen kernels are Havs kernels (as far as I remember, I'll double check in a few). Anyway, if you are using a Havs kernel, changing cpu settings is pointless/counteractive. I would either leave the settings alone or switch to a no-havs kernel. You can check in settings>about phone.
EDIT: However, if you must mess with the settings, you can find them in Cyanogenmod Settings under Performance Settings. I don't know of a way to set profiles from that screen, though - only max/min & governor.
Click to expand...
Click to collapse
but how exactly does havs control battery usage? and if i use setcpu wouldn't the havs not function only setcpu will function b/c of priority?
serdna75 said:
I believe the SavageZen governor is a specially tweaked/optimized version of the SmartAss governor.
And if you use Smartass/SavageZen governor, I think it also automatically undervolts when sleeping, and essentially mimics what a screen-off profile in SetCPU would do.
Click to expand...
Click to collapse
how do u use Smartass/SavageZen governor?
Threads Merged... please post your question once.
Green_Arrow said:
how do u use Smartass/SavageZen governor?
Click to expand...
Click to collapse
In CM Settings, go to Performance Settings & then CPU settings. Under available governors choose SavagedZen or Smartass. I'd try them out & see which you like the most. I prefer SavagedZen, I seem to get better battery life & performance.
egzthunder1 said:
Threads Merged... please post your question once.
Click to expand...
Click to collapse
Thanks, sorry its my 2nd day on this forum
plainjane said:
In CM Settings, go to Performance Settings & then CPU settings. Under available governors choose SavagedZen or Smartass. I'd try them out & see which you like the most. I prefer SavagedZen, I seem to get better battery life & performance.
Click to expand...
Click to collapse
thanks atm im using the savagedzen, and jw is autokiller memor optimizer useful now or not?
Green_Arrow said:
thanks atm im using the savagedzen, and jw is autokiller memor optimizer useful now or not?
Click to expand...
Click to collapse
Personally I have never needed a task killer while on CM7, so I am going to recommend against it.
Well I had talked to someone else that is using it like that and they said they get amazing battery life
Sent from my PC36100 using XDA Premium App
I say no toward any kind of task killer. First of all, they're pointless. You're killing stuff that isn't using any power to begin with, which then restarts anyway. The task killer itself is actually doing something, running on a set schedule, where as the tasks you're killing are just sitting in memory for faster opening.
It bugs me that even the techs at Sprint recommend it, so every person that doesn't know anything about how their phone works thinks it's necessary. Then in the market for every clock widget you see everyone going "like zomg the clock doesn't keep time your app sucks 1*" because the damn task killer is killing it. That's if they can even figure out how to use it & not complain that it "won't open", despite clear instructions on how to put a widget on your screen.
Sorry, totally went off on a rant there.
But yeah, stay away from task killers & let Android do its job. You don't have to have a ton of memory free for your phone to run perfectly fine under normal usage. I don't notice a difference between 300mb & 50mb free. If you don't worry about it, you won't either.
Free memory does not equal more battery.
plainjane said:
I say no toward any kind of task killer. First of all, they're pointless. You're killing stuff that isn't using any power to begin with, which then restarts anyway. The task killer itself is actually doing something, running on a set schedule, where as the tasks you're killing are just sitting in memory for faster opening.
It bugs me that even the techs at Sprint recommend it, so every person that doesn't know anything about how their phone works thinks it's necessary. Then in the market for every clock widget you see everyone going "like zomg the clock doesn't keep time your app sucks 1*" because the damn task killer is killing it. That's if they can even figure out how to use it & not complain that it "won't open", despite clear instructions on how to put a widget on your screen.
Sorry, totally went off on a rant there.
But yeah, stay away from task killers & let Android do its job. You don't have to have a ton of memory free for your phone to run perfectly fine under normal usage. I don't notice a difference between 300mb & 50mb free. If you don't worry about it, you won't either.
Free memory does not equal more battery.
Click to expand...
Click to collapse
but doesn't free memory mean less things are running or even being used just a tad bit which does mean a better battery life?
Green_Arrow said:
but doesn't free memory mean less things are running or even being used just a tad bit which does mean a better battery life?
Click to expand...
Click to collapse
No. Memory has nothing to do with battery.
Screen, radios, and CPU use battery and that's about it.
Sent from my PC36100 using XDA App
matt2053 said:
No. Memory has nothing to do with battery.
Screen, radios, and CPU use battery and that's about it.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
So do u agree w/ system panel/juice defender?
Sent from my PC36100 using XDA Premium App
What are the safe/stable clockspeeds for underclocking and overclocking my Desire Z? Also, what app do I use? Like, I don't mind paying for the app (as long as it's not too expensive)
Sent from my HTC Vision using XDA App
SetCPU can be used to overclock if you're rooted. Depending on the ROM and Kernel combination, overclocking to about 1.3ghz is usually safe. Some go up to 1.5ghz or even 1.8ghz, but are often quite unstable depending on other configurations you have in your ROM.
As far as underclocking goes, some custom kernels clock all the way down to 122mhz, I've been using a streamline5 kernel on CM7 (which offers 122mhz min) and haven't had any ill effects with this.
I have the Virtuous Sense ROM (with it's default kernel, although it does have other kernels which can give other cpu speeds), right now but might try out another ROM soon (maybe) do you know what's the min and safe max for this ROM?
Also, can I just set a particular clock speed (e.g. 500MHz) and it should be ok or is there any stability difference between say 500MHz and 505MHz? Just curious. I looked at SetCPU and it looks like a good one. Also, if the clock speed I set makes things go wrong, can I revert it or can I get stuck with it and need to do a wipe?
Sent from my HTC Vision using XDA App
zaghy2zy said:
I have the Virtuous Sense ROM (with it's default kernel, although it does have other kernels which can give other cpu speeds), right now but might try out another ROM soon (maybe) do you know what's the min and safe max for this ROM?
Also, can I just set a particular clock speed (e.g. 500MHz) and it should be ok or is there any stability difference between say 500MHz and 505MHz? Just curious. I looked at SetCPU and it looks like a good one. Also, if the clock speed I set makes things go wrong, can I revert it or can I get stuck with it and need to do a wipe?
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
No, there's no need to set a particular clock speed. Just whatever works for you. I wouldn't recommend going under 800mhz, as the phone will really really bog down even with normal use.
I haven't used that particular ROM, but I'm assuming anywhere around 1.3ghz should be safe on the upper limit. Like I said before, anything above that might start to cause issues. You might also want to consider the battery life implications of severe overclocking.
You can change the clock speed any time you want. If you're having wakeup or heat or any other issues just go back to SetCPU and change the max clock speed again. You can also use profiles in SetCPU to change the clock speed when the phone is overheating, or when the screen is off, or when the battery gets to a certain %. There are tons of posts detailing how others have setup their SetCPU profiles.
One last note, don't forget to check the box for "Set on Boot" in SetCPU, this way your changes aren't undone on reboot.
Thank, I think I got everything I need to know in your last reply
I'm on CM7, with the CM7 kernel, and clocked in at 1.5GHz, and have no problems, and the rom is super fast. And I use SetCPU.
This will be my first time flashing a kernel and I'm gonna go with freedom ,any tips on settings or anything ?
Sent from my 3dvo using XDA App
And I'm also reading around underclocking is not safe for your phone, true?
Sent from my PC36100 using XDA App
Underclocking won't break the phone. Maybe slow it down a good bit, depending how low you put it, but you'll be fine. Overclocking is what you have to be careful with.
Sent from my PC36100 using XDA App
What is a safe setting to keep it on and does OC really give it that much of a boost ?
Sent from my PC36100 using XDA App
Underclocking wont hurt ur phone. Neither will undervolting. Overclocking wont hurt it but will sacrifice battery life and also if u overclock to high Ull get constant rebooted. Try to keep it under 1198. Also watch what what governor u choose. I usually use conservative for better battery life but I've seem on demand and interactive work well also.
Also noticed if u underclock to 294 or lower u sometimes get a problem where when u get a call and the phone screen isn't on it has a hard time waking up plus phone lags as well
free the dirk
Thanks for the help. Gonna be flashing soon . Mainly trying to do this for battery conservation so would I go for underclocking or undervolting
Sent from my PC36100 using XDA App
I have been on sense this whole time, up until yesterday I finally made the CM7 switch...
BUT with sense roms you can underclock to the low 600's with and min of 128 and be just fine haha, depends on what you use the phone for though.
Mainly just alot of texts. A lil calling and surfing the web alot
Sent from my PC36100 using XDA App
EarnyBaller said:
This will be my first time flashing a kernel and I'm gonna go with freedom ,any tips on settings or anything ?
Sent from my 3dvo using XDA App
Click to expand...
Click to collapse
Underclocking will not hurt your phone but some phones do not like to be underclocked and you may crash from time to time. The best thing is to start out with the default CPU Settings. You can experiment with raising the max and lowering the min (using SetCPU) but do not check the box for "Set at Boot" until you are sure they are stable. That way if it is not and you reboot it will not set it right back to an unstable value after the reboot.
The area where people seem to have a problem underclocking is lowering the min clock to 128MHz. Some phones do not like to go that low. I had great results leaving the min at 245MHz and changing the max to 768MHz.
Another detail about Freedom. This kernel uses Undervolting to save power. There are four levels. You choose the level by the file you download. It is not configurable.
Freedom: No Undervolting
Less Freedom: -50mV
More Freedom: -100mV
Aggressive Freedom: -150mV
If you start with Aggressive and find it to be unstable then move down to More, then Less and finally Freedom.
I am a newbie on rooted phones. Just rooted the phone to CM7.0.3 Stable and found out that we have a setting to change the Govenors, currently set using SMARTASS with 245/729.
One question, is it nessesary to install apps such as Setcpu to overclock? or it is just adequet to use the setting in CM7 ? Will both conflict each other? Many thanks
Its useful I think, because you can setup CPU speeds for certain things, such as when your screen is off or when the battery drops below a certain threshold.
Sent from my HTC Wildfire using xda premium
depends on you need dude. playing games/ watching videos/ hearing music/ simple phone usage/ battery conservation etc. stock one dont have profiles. but 3rd party like set cpu have it. so that it auto switches profiles according to ur present phone status.
Sent from my HTC Wildfire using XDA App
SetCPU is much more useful than the cyanogenmod CPU functions, I did use the cyanogenmod one but I didn't see any changes
Sent by fire!
yes, the good things are the profiles! but I'm not sure if underclocking the processor really saves battery since i've heard that its just a saying/placebo
cedriccc said:
yes, the good things are the profiles! but I'm not sure if underclocking the processor really saves battery since i've heard that its just a saying/placebo
Click to expand...
Click to collapse
Yeah I think your right, strangely enough I think it's the same with overclocking, I put mine up to 700ish MHz and the battery still lasts just as long, I expected a reduction in battery life!
Sent by fire!