Overclock Issue - EVO 4G Q&A, Help & Troubleshooting

I was flashing ROMS and went back to my old one AVA Froyo Z3 and flash Nectary 4.3.1-cfs-havs-nosbc kernel for overclocking, but everytime I try to use SetCPU to increase the max CPU when I get above Stock and into an overclock setting my phone freezes and reboots. I wiped delvik cache and reflashed ance it didn't fix it. Any ideas?
Sent from my PC36100 using XDA Premium App

Not all phones can be overclocked. Every single processor is different, and some just can't be overclocked. How much are you trying to overclock? Most phones should be able to go to 1150000 without any problems.

I was trying 1260000 but ill reflash and try less
Sent from my PC36100 using XDA Premium App

Reflashed the Rom and kernel and now its letting me overlook to 1200000. So problem fixed
Sent from my PC36100 using XDA App

Related

Question about my Rom/kernel setup

Ok, on running the latest virus airborne with kk 11 and my touch screen ia getting some horrible response issues. Anyone else noticing this issue on different setups?
Sent from my PC36100 using XDA App
Have you tried rebooting it?
are you using setcpu? and if so, whats ur cpu clocked to?
i rebooted but it didnt seem to help. setcpu is 245/1190 conservative. i'll try and flash the kernel again. i'll wipe cache and dalvik 2 times this time

Set cpu with stock kernel droid incredible

I just rooted my incredible and I'm using the kernel that came with it stock. I disabled perflock and I left the max speed to 998 and the min speed to 245.
When I'm not doing anything on my incredible, I see that the speed constantly changes from the max to the min. Not even one second passes before it just goes back and forth, back and forth. Is this normal?
Coming from the d1 where it would stay at the min when idle, I'm not sure if what's going on with my incredible is normal.
Sent from my ADR6300 using XDA App
Yes that's normal. For better battery life, I'd try a kernel with smartass governor. It spends more time on the lower frequencies.
Sent from my ADR6300 using Tapatalk
Switching to a different kernel will give you the ability to overlook//underfoot the system needed.. this in turn increases battery life.. kingklick, ziggy's, chad's kernel are all well known kernels.. you will want to play with different kernels.. not every kernel will be stable to overlook to certain speeds on certain Rom's.. switching kernels is almost as addictive as switching roms.. always nandroid before flashing anything..
Sent from my ADR6300 using XDA App
Typos on my end.. underfoot = undervolt.. overlook = overlook.
Sent from my ADR6300 using XDA App
Will those kernels work on my rooted stock incredible?
Sent from my ADR6300 using XDA App
Yea! By stock i'm assuming all you did was root. I am currently running SkyRaider 3.5 Sense along with
"2.6.32.26-ubcredujuerbek-12082010 [email protected] #11"
I will edit with links to these two items.
SkyRaider 3.5 Sense - SkyRaider
Chad's Kernel - Incredikernel
My phone runs amazingly fast with sense but yet, even with heavy usage (Texting constantly, on the internet, gmail, even Fring) I can go an easy 24 hours on one charge. If my phone stays screen-off idle I could last at 95%-100% for several hours.
Yes, all I did was root.
Does the chad kernel provide wireless tether and will i still need to disable perflock in setcpu?
Sent from my ADR6300 using XDA App
the non stock kernels all disable perflock already, you do not need to do it..
flash the kernel via clockwork, and you are set.. jump into setcpu and adjust some settings and add profiles.. you'll be golden..
What he said ^^
Sent from my ADR6300 using XDA App
20twins10 said:
the non stock kernels all disable perflock already, you do not need to do it..
flash the kernel via clockwork, and you are set.. jump into setcpu and adjust some settings and add profiles.. you'll be golden..
Click to expand...
Click to collapse
Not quite. I believe Lou's has some tweaks within perflock, so disabling it would lose those.
And most kernel devs, particularly Lou and the ones who use HAVS, advise against using SetCPU. I'd check with your chosen kernel thread for details.
Sent from my ADR6300 using Tapatalk
Also, I wouldn't 'set on boot', at least till you find frequencies that your phone can handle safely. Otherwise, you'll get a 'crash' loop, where your phone starts up just fine, but once you go past the initial lockscreen it'll crash and reboot. Very annoying...
Sent from my Incredible using XDA App
what rager said... ive put on kernels and ran em high only to get a "boot loop".. its tuff to get out of cause you need to get back into setcpu to scale back otherwise it keep on going.... i learned to put the setcpu app icon on my main screen so i can get there fast to scale back..
http://forum.xda-developers.com/showthread.php?t=866736 can you install these with the stock rom. i wanted to experiment to get better battery life but didnt really want to install a different one.
keith4321 said:
http://forum.xda-developers.com/showthread.php?t=866736 can you install these with the stock rom. i wanted to experiment to get better battery life but didnt really want to install a different one.
Click to expand...
Click to collapse
Some. Make sure it's a sense version if you're using stock sense.
Sent from my ADR6300 using Tapatalk
Mr. Rager said:
Also, I wouldn't 'set on boot', at least till you find frequencies that your phone can handle safely. Otherwise, you'll get a 'crash' loop, where your phone starts up just fine, but once you go past the initial lockscreen it'll crash and reboot. Very annoying...
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
That exact thing happened to me...pissed me off like crazy at first I was clueless then I just did a restore
Sent from my ADR6300 using XDA App
Yeah, if you let it boot loop too long it'll hard boot, which is where the phone cuts off completely. That has happened to me, and it ruins apps.
Sent from my Incredible using XDA App

Freezing while playing games.

Been running cm7.0.3 for a while and have been using the kernal that came with the rom, and it seems any game I play after a few minutes the game ends up freezing. Tried different governer modes and Max clock speed and stock clock speed, with no difference. Any suggestions? I'm assuming its my kernal....
Sent from my ADR6300
I'm not sure if the stock CM kernel is overclockable (very well may be) but I have had really good results with either Chad's incredikernel or invisiblek. Never ran into any issues playing games, even CPU intensive ones.
Sent from my ADR6300 using XDA App
Those are the ones from nightly right? And its been forever since I've flashed a kernal, do I wipe dalvik and that's it?
Sent from my ADR6300
The nightlies still have the stock CM kernel. Those other kernels are in the development forum. And yes, you just flash the kernel in recovery like a rom. A cache/dalvik cache wipe is all that's necessary.
Sent from my ADR6300 using XDA App

Undervolting, Overclocking and random freezes.

I'm running back into the problem of custom Roms freezing on me, no FC's, just the phone freezing and requiring a battery pull to re-boot. I odin EC05 plus, let it boot and sit for a few minutes, reboot, let it convert, flash cwm purple, wipe, then flash whatever rom, and eventualy they all freeze.
The only roms to never give me that problem is CM7, MIUI and true stock.
Tried everything, except for not using the stock cable, but even still, cm7 and miui have no problem.
Sent from my SPH-D700 using XDA App
I've had the same problem with SRF 1.2...and I linked the problem to certain SetCPU settings like on demand and userspace and to undervolting to much in the higher OC'd frequency ranges...even though I've experimented wih these settings and found a somewhat stable medium...I still get the random freezes once in a blue...I don't know what else it could be.
Sent from my rooted, suited, & booted Epic 4G kno dat!
Right now I'm on SRF with the 1.1.1 Kernel, using setCPU 200-1000, cfq, and no undervolting at all. I was on the 1.1.0 Kernel using voltage control when I had it freeze. I've uninstalled voltage control and galaxy tuner. Oddly enough setcpu dosent fc when I go into the voltages, which it did a few flashes back.
Sent from my SPH-D700 using XDA App
What problems do you think Galaxy tuner was giving you...I'm using it right now?
Sent from my rooted, suited, & booted Epic 4G kno dat!
I wasn't sure, but I figured with using setcpu it would be best to uninstall it so there wasn't any sort of conflicts between the two.
Sent from my SPH-D700 using XDA App
I'm not sure I follow where the conflict btwn those 2 apps would be...once controls cpu speed, governing, and voltage...and the other controls screen brightness and sound attributes...not trynna be a smart ass I'm just trynna make the connection?
Sent from my rooted, suited, & booted Epic 4G kno dat!
In galaxy tuner there is some options for overclocking, as well as IO scheduling.
Sent from my SPH-D700 using XDA App
At any rate. Ill sell you my phone fully uv and tweaked for max battery and speed
Sent from my SPH-D700 using XDA Premium App
You didn't read my OP, I have no problems at all with FC's, my problem is the phone freezes and I have to pull the battery to restart.
Custodian said:
At any rate. Sounds like your phone is garbage. Make sure you enable journaling to help mend the fc's.
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
Sent from my SPH-D700 using XDA App
Skimp Killah said:
You didn't read my OP, I have no problems at all with FC's, my problem is the phone freezes and I have to pull the battery to restart.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
If you aren't undervolting and are having this issue on multiple ROMs, it sounds like a conflict between some apps like you suspected. That or something is not right with your phone. Freezes happen to me when undervolting too much but you aren't doing that....edit...maybe your phone just doesn't like the 200 minimum that well. If I remember right, stock values are 1000 max and 400 min.
Sent from my SPH-D700 using XDA Premium App
I'm wondering if maybe the 200mhz is whats doing it then, I always figured 200-1000 was stock, and the phone would only freeze when the screen was off. Right now I'm using setCPU with it set at 200-1000 with cfq IO scheduling. If I have more freezes I will try bumping up to 400-1000.
JohnCorleone said:
If you aren't undervolting and are having this issue on multiple ROMs, it sounds like a conflict between some apps like you suspected. That or something is not right with your phone. Freezes happen to me when undervolting too much but you aren't doing that....edit...maybe your phone just doesn't like the 200 minimum that well. If I remember right, stock values are 1000 max and 400 min.
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
im currently undervolted with the aosp rom from dub with genocide's final kernel...200mhz is perfectly fine...if 200 is underclocked too low or other frequencies are too low...sod or freezes will happen with the frequency with the wrong voltage is reached..i have setcpu and voltage control together but mainly use the new setcpu...when idling, i see a 1 percent draw in 2 hours and 6 minutes...and use stability test whenever you underclock to see if it safe to use...just my 2 cents...

Need a good kernel for cm9 unofficial.

I'm looking for any sbc kernels that work with the unofficial cm9. I tried the tiamat ics kernel with SBC and all it did was Max out my CPU and hold it maxed until it either lags into a reboot or just freezes and I can't do anything else. Any idea what could cause this or can someone give me a list of available kernels?
Sent from my PC36100 using xda premium
Use mason kernel. Just make sure u grab the one for ics
XDA Moderator
I looked at them and I've tried both. It worked for a total of 20 mins and I got the same result. I've completely wiped and cleared everything except the SD card memory. After 20 mins the CPU maxes itself and crashes the phone. The rom runs fine by itself but it decides to go completely unstable when I add a kernel. Any ideas what could be causing it? Software/hardware inefficiency or something?
Sent from my PC36100 using xda premium

Categories

Resources