Hi
I just flashed lean kernel and gave it a day or two to settle down
I have been trying to over clock it and it just won't stay that way
Every time I restart it just goes back to how it was
What can I do to make it stick
Thanks
Sent from my Nexus 7 using XDA Premium HD app
If you have more than one dameon control installed they may conflict with each other and revert back to "stock" at start up. Are you using set cpu to overclock? Does your rom have overclocking abilities in settings?
Lastly, did you see an option 'set on boot'
Sent from my HTC Vision using xda premium
According to what you've said, its most likely due to the powerhal. The stock powerhal reverts back to 1.3 GHz after a while no matter what you set it on. Best thing if you want oc is to flash imoseyn's 1.5ghz powerhal found in his rootz thread
Sent from my iPhone 5
demkantor said:
If you have more than one dameon control installed they may conflict with each other and revert back to "stock" at start up. Are you using set cpu to overclock? Does your rom have overclocking abilities in settings?
Lastly, did you see an option 'set on boot'
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Yes its ticked as "Start on Boot"
I'm on stock rom but LeanKernel, I'm trying to overclock with ROM Toolbox PRO but it keeps reverting to 1.3ghz, 1.5ghz is used if I overclock everytime I restart but then reverts when rebooted.
markj338 said:
According to what you've said, its most likely due to the powerhal. The stock powerhal reverts back to 1.3 GHz after a while no matter what you set it on. Best thing if you want oc is to flash imoseyn's 1.5ghz powerhal found in his rootz thread
Sent from my iPhone 5
Click to expand...
Click to collapse
Yeah I think your right here mate, did a little bit of research over last few days and it seems PowerHAL is the culprit.
Could you explain what that PowerHAL is and how it effects overclocking etc?
Im guessing its like the native frequency setting?
Thanks !
Related
Hi, I'm having trouble staying overclocked. The phone will stay overclocked for a short while then it will eventually reboot back to original clock, why?
-z4 rooted, 2.2.
Ps. Ovetclock app by Jrummy
Sent from my DROIDX using XDA App
Are you sure that you are setting the frequency at boot? if you want it set at boot then you have to choose the option from the main menu to set at boot.
If you are having frequent reboots though I wouldn't recommend setting that at boot, only set at boot once you have found a stable setting that does not reboot on you or cause other issues (i.e force closes or causing the phone to feel like an oven).
Ty, that was it... just a bit of testing to find the stable OC. 1.2ghz seemed to be just fine. No heat, or boot lap. And also using the free app called D2/DX overclock actually worked best.
Sent from my DROIDX using XDA App
With faux's smartass/minmax, etc kernel I will need go run set cpu correct? Im on my rooted stock sensd that ivd removed some of the bloat from.
Again ty!
Sent from my HTC Glacier using XDA App
Crazydaddy said:
With faux's smartass/minmax, etc kernel I will need go run set cpu correct? Im on my rooted stock sensd that ivd removed some of the bloat from.
Again ty!
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
to overclock, yes you would need to use setCPU. However, I am unsure whether the smartass governor would take effect whether or not you had setCPU to OC with.
Thanks! I'm new to this but figured it would make no sense to install the kernel with no way to actually OC. I like alot of the roms out but I'm happier with the stock setup the way I've modded it. Removed the bloat I know I'll never use, changed the boot ani, battery icon on status bar....etc. Short press google/long press Genius (the way it should be!)
This phone is amazing once rooted!
Crazydaddy said:
Thanks! I'm new to this but figured it would make no sense to install the kernel with no way to actually OC. I like alot of the roms out but I'm happier with the stock setup the way I've modded it. Removed the bloat I know I'll never use, changed the boot ani, battery icon on status bar....etc. Short press google/long press Genius (the way it should be!)
This phone is amazing once rooted!
Click to expand...
Click to collapse
It sure is also, while setCPU is a paid app, its increased my speed and battery life several hours beyond that of the normal speeds with no profiles set for screen off or battery level. Well worth the buck, in my opinion.
btw, dont forget the thanks button
Hmmm all I get is boot screen locks or loops. With and with out cache/dalvik wipes. Is it a requirement to have set cpu installed prior to flashing this kernel?
Sent from my HTC Glacier using XDA App
Crazydaddy said:
Hmmm all I get is boot screen locks or loops. With and with out cache/dalvik wipes. Is it a requirement to have set cpu installed prior to flashing this kernel?
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
no, it shouldnt be.. I had it installed, but I dont think its required.
Hmmm I wonder why im having no luck then.....
Sent from my HTC Glacier using XDA App
And I meant to say if you wanted to try this kernal in my first post, not rom... I bet on the stealers and am still pissed...lol
Sent from my HTC Glacier using XDA App
Lol I figured so!
Sent from my HTC Glacier using XDA App
I dunno if this'll help at all, but I'm on pretty much the exact same setup (rooted, stock, removed bloatware, changed battery in status bar, changed genius button to google search, etc.) and faux123's kernel loaded right up for me, I followed his instructions and came from grankin's kernel.
I have SetCPU but I only use it to OC it a bit, I have max to 1209, no profiles. I'm not sure how much it changes and helps, some days it's really good but today it's been unplugged for 3 hours and it's at 80% with a few texts, about 20 min of internet and 20 min on XDA app.
Sent from my HTC Glacier using XDA App
i recently rooted my wildfire and have installed cyanogenmod 7.0.3 and wanted to double check something, ive been looking around threads and these overclocking guides and i saw that one of them said you only need a kernel with the ability to overclock if you are on stock rom, otherwise you can install setcpu straight away and overclock, could someone please just clarify this, thanks
Cm7 has overclock built in so no need for additional kernal or setcpu app
Go to Settings > Cyanogenmod settings > performance > CPU settings
It's basically setcpu built in
Sent from my HTC Wildfire using XDA Premium App
Eddster3000 said:
Cm7 has overclock built in so no need for additional kernal or setcpu app
Go to Settings > Cyanogenmod settings > performance > CPU settings
It's basically setcpu built in
Sent from my HTC Wildfire using XDA Premium App
Click to expand...
Click to collapse
thanks, i gave it a go but every time i boot it always restores itself to 528, how can i set it to stick at a certain speed? thanks
deezykhara said:
thanks, i gave it a go but every time i boot it always restores itself to 528, how can i set it to stick at a certain speed? thanks
Click to expand...
Click to collapse
There is a check box that says something like " set at boot" tick this and it will retain your settings
Sent from my HTC Wildfire using XDA Premium App
Also Smartass Governor is very good. Its interactive so manages CPU when required or when your handset is idle
Sent from my HTC Wildfire using XDA Premium App
Eddster3000 said:
Also Smartass Governor is very good. Its interactive so manages CPU when required or when your handset is idle
Sent from my HTC Wildfire using XDA Premium App
Click to expand...
Click to collapse
so does this mean it wont affect battery too much as it will automatically reduce the speed and increase it when required, also what speeds would you recommend for min and max?
deezykhara said:
so does this mean it wont affect battery too much as it will automatically reduce the speed and increase it when required, also what speeds would you recommend for min and max?
Click to expand...
Click to collapse
Yeah, as far as I know it caps min setting to 352 when idle/sleep even if you have yours min set higher than that. It then uses required CPU up to your Max depending on what processes are taking place.
Overclocking will effect battery life if you push it to far. I currently have mine set at 352/691 and it works for me giving speed and battery life.
Experiment your own tho
Sent from my HTC Wildfire using XDA Premium App
thanks again for all your help
So I just opened up is monitor and happened to go to the processor tab and discovered that the second core was underclocked to 456MHz with the governor set to conservative. Now my xoom is flying. Its great.
Step by step:
Open os monitor (im on tiamat 2.2.2)
Go to misc tab
Tap on more next to CPU
Change it to the settings you want
???
Profit
Let me know if you have any success with this.
Sent from my Xoom using xda premium
Just ran Antutu to do some benches and noticed on my cpu usage bar that only one core was used in the benchmarking process, except for reading/writing to the sdcard which did use both cores.
Sent from my Xoom using xda premium
Good lookin. Ill have to check mine out now
Sent from my PG86100 using Tapatalk
Over night my core got underclocked again. So im thinking its the OS doing this to save battery when it doesn't absolutely need that core.
Sent from my Xoom using xda premium
Worked like a Charm
d3athsd00r said:
So I just opened up is monitor and happened to go to the processor tab and discovered that the second core was underclocked to 456MHz with the governor set to conservative. Now my xoom is flying. Its great.
Step by step:
Open os monitor (im on tiamat 2.2.2)
Go to misc tab
Tap on more next to CPU
Change it to the settings you want
???
Profit
Let me know if you have any success with this.
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
Thanks on this one, I had no issues and checked quadrant and got a personal high of 3796 I really don't understand why the Xoom gets such a bad rep, I love mine and to this day still able to find new things to learn about it.
-NooRotic
Both cores running at full clock on stock.
mcnob said:
Both cores running at full clock on stock.
Click to expand...
Click to collapse
I was running Rogue's 1.4.1 kernel and it was underclocking the second core. Now I'm back on Tiamat kernel and it isn't underclocked.
Seems to be kernel specific.
d3athsd00r said:
I was running Rogue's 1.4.1 kernel and it was underclocking the second core. Now I'm back on Tiamat kernel and it isn't underclocked.
Seems to be kernel specific.
Click to expand...
Click to collapse
ooh i wouldn't say so... i'm using rogue 1.4.1 and both cores are the same freq.
Lizzo said:
ooh i wouldn't say so... i'm using rogue 1.4.1 and both cores are the same freq.
Click to expand...
Click to collapse
Bah. Idk then. I saw some people complaining about it elsewhere but didn't take the time to find anything out.
Sent from my Xoom using xda premium
I started this thread because i want to be able to use Sparksco kernel v14 but it freezes when its set to 1.0GHZ I been running v10 as my daily kernel and its bottomline on my top list of kernels. Any help will be much appreciated, im on the latest nightly CM255, i had to revert back to v10 because i need speed to check emails and surf the internet...If theres another update for the V14 in the future i hope that can be a fix or its probably my setup that prevents me from reaching any higher speeds, overall Sparksco you the man!!! By the way ICS devs yall get mad props peace...
I use sparks v14 kernel on cm nightly 255 clocked right under 1ghz using smartass governer no problem. I did a full wipe of everything, and formatted system before install of everything of course. Edit: I clocked it to 2ghz and no freezes here. Did you do a full wipe before the install of the ROM/kernel?
Sent from my PG06100 using xda premium
Hey sparksco, luv your kernels, can we get smartass2 included?
Sent from my PG06100 using XDA App
Wrong forum buddy. This is a development section.
This belongs in Q&A
Just for future reference.
notsointeresting said:
Wrong forum buddy. This is a development section.
This belongs in Q&A
Just for future reference.
Click to expand...
Click to collapse
I'm notsointeresting in hearing what u got to say but I get the point XDA supervisor...
peanjr said:
I use sparks v14 kernel on cm nightly 255 clocked right under 1ghz using smartass governer no problem. I did a full wipe of everything, and formatted system before install of everything of course. Edit: I clocked it to 2ghz and no freezes here. Did you do a full wipe before the install of the ROM/kernel?
Sent from my PG06100 using xda premium
Click to expand...
Click to collapse
I'm going to have to give that a shot homie...
Kernel v14 is more geared for battery saving. I haven't updated the voltages yet because I'm not compiling gingerbread anymore, rather been working on getting a stable ICS rom build before I do more work on it. As soon as we get ICS gingerbread will be a thing of the past. Kernel v14 works good for some and v10 for others. I like v14 because of the battery I've been able to get on 122mhz min and 998mhz max. But if you up the min to the next highest setting (230mhz) you shouldn't get any lockups. Or even try 307mhz.
Edit: looks like 307mhz min is the only clock speed that allows me to overclock to 2ghz and not have any lockups. I'm also on cm nightly 255 pzguzman, and I always keep it on smartass governor.
P.S. The mods should be able to move this thread no problem without removing the comments or thread.
Sent from my PG06100 using xda premium
Yeah, forgot to mention as sparks said, at 2ghz the min is at 307mhz.
Sent from my PG06100 using xda premium
sparksco said:
Kernel v14 is more geared for battery saving. I haven't updated the voltages yet because I'm not compiling gingerbread anymore, rather been working on getting a stable ICS rom build before I do more work on it. As soon as we get ICS gingerbread will be a thing of the past. Kernel v14 works good for some and v10 for others. I like v14 because of the battery I've been able to get on 122mhz min and 998mhz max. But if you up the min to the next highest setting (230mhz) you shouldn't get any lockups. Or even try 307mhz.
Edit: looks like 307mhz min is the only clock speed that allows me to overclock to 2ghz and not have any lockups. I'm also on cm nightly 255 pzguzman, and I always keep it on smartass governor.
P.S. The mods should be able to move this thread no problem without removing the comments or thread.
Sent from my PG06100 using xda premium
Click to expand...
Click to collapse
Oh okay i see Sparksco thanks for clarifying the setup, i dont mean to steer anybody in the wrong direction especially from working on a ICS BUILD which is the most highly anticipated OS for android. But im going to flash v14 and try out the setting and will get back and let you know thanx homie...
No luck but its amazing how you guys achieve the speeds... Tried the settings but my phone cant handle the pressure lol...Im gonna stick with this kernel tho... My bad for posting this thread in the wrong section its a rookie mistake...
peanjr said:
Yeah, forgot to mention as sparks said, at 2ghz the min is at 307mhz.
Sent from my PG06100 using xda premium
Click to expand...
Click to collapse
It worked i only needed to do a full wipe, thanx homie...
By the way Sparksco i got your setup on my rom, fully functional overclocked at the max with no feezes, thanx homie...
YOU'RE USING THE WRONG GOVERNOR MIN/MAX SETTINGS
For example:
IF I want to get 2ghz out of my phone I use the performance governor and use min/max of 2ghz.
OR:
I would use:
Gov: Smartass
Min CPU: 300mhz
Max CPU: 1.5ghz
You would freeze too if you were a CPU constantly going from 100mhz to 2000mhz all the time!
prguzman1978 said:
By the way Sparksco i got your setup on my my rom, fully functional overclocked at the max with no feezes, thanx homie...
Click to expand...
Click to collapse
Glad you got it working.
Sent from my PG06100 using xda premium
jefftet said:
Hey sparksco, luv your kernels, can we get smartass2 included?
Sent from my PG06100 using XDA App
Click to expand...
Click to collapse
Smartass2 was made for the HTC Sensation which is a dual core gsm phone much like the Evo 3D (but cdma instead). I could never get it to clock passed 1.4ghz so I don't think it likes our phones much. It's a great concept but the normal old smartass still works much better for the shift.
Sent from my PG06100 using xda premium
FWIW I am hitting 2.0Ghz with no lockups or anything. I previously had been using ScaryStable for a while and anything past 1.6Ghz would lock right up nearly immediately.
danibri82 said:
FWIW I am hitting 2.0Ghz with no lockups or anything. I previously had been using ScaryStable for a while and anything past 1.6Ghz would lock right up nearly immediately.
Click to expand...
Click to collapse
Again, it depends on the governor and the min cpu. I ran scary stable at 1.9ghz for 24 hours+ straight, no lockups.
for the heck of it I ran it @ the min of like 1something hz for the low and 2.0 max just to see how it ran, and it was solid.
danibri82 said:
for the heck of it I ran it @ the min of like 1something hz for the low and 2.0 max just to see how it ran, and it was solid.
Click to expand...
Click to collapse
I understand but say you ran scary at min 100mhz and max 1.9ghz with a gov of ondemand, that would freeze for sure on any phone.
VICODAN said:
I understand but say you ran scary at min 100mhz and max 1.9ghz with a gov of ondemand, that would freeze for sure on any phone.
Click to expand...
Click to collapse
I think what he's saying is that he ran this kernel (pershoot v14) with a low min and a high max and it ran fine.
Sent from my PG06100 using xda premium