-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root Set CPU mistake.
- Thread starter nathanotis
- Start date
-
- Tags
- htc evo 4g
Yeh Im Legit
Member
Funny... I came on here to ask why this morning my phone shut off and got stuck in a boot loop and read this... Probably explains what happened to mine... Then after recoverying my battery was down to about 60 so I reduced my over clock just because... I dint really do games.. I run Pandora or mp3 download some times and cloudskipper too but other than that words and Facebook and Skype some... What is a good setting for my setcpu to overclock at.. I went down to like 650/245 after recovery and haven't noticed any loss of performance... What's is a reasonable place to lower my over to without worrying about anything to get good battery life out of basic functions and those apps listed working properly?
9to5cynic
Android Expert
@ Dustwun: Did you put it on the root of your sd card?
@ Legit: I'm no setcpu expert, but I think for what you are doing, the most important one is your lower limit. And 245 seems pretty good to me. Most people set up a screen off profile somewhere around 128/256. For underclocking, maybe something like 256/720-ish should be reasonable, maybe even lower.
@ Legit: I'm no setcpu expert, but I think for what you are doing, the most important one is your lower limit. And 245 seems pretty good to me. Most people set up a screen off profile somewhere around 128/256. For underclocking, maybe something like 256/720-ish should be reasonable, maybe even lower.
try anything in the 1000 should be ok. mine can go up to 1190 with no issues.
Yeh Im Legit
Member
Actually I didn't even recover I just wiped dalvik and cache and reflashed my same ROM (kings alliance hybrid rls2... Didn't think I had to fully wipe and recover since i was just going to the same ROM) it worked but maybe that wasn't the right thing to do? I'm still learning... Only got root with rEVOlution cracking 2.3.3 last week so this is all new to me and that's the ibly ROM I've ever used outside stock... I put golden monkey and set CPU on there Friday and got that loop this morning... So if anyone wants to tell me more or anything please feel free
Yeh Im Legit
Member
Maybe I'm missing something... My setcpu is set to on boot ondemand and scaling goes from minimum of 245000 and maximum is 998000
you need to be using a custom kernel to overclock with setcpu.
Yeh Im Legit
Member
And I haven't gotten into profiles on it at all... Im learning the kernel thing still so i didnt touch those... I'm guessing i should get into that though...? I only was doing the basic funtion that opens with the app until I figure it out a little more
you can do that only if it is the same rom. it is one way to wipe a mistake you made. or if there is a glitch or something. a full wipe needs to be done when flashing a different rom.
Yeh Im Legit
Member
I flashed golden monkey 1.1 Friday... By the information I gave did I not successfully do this? I dunno how to check... I do know out of curiosity I just dropped my max to to close to 500000 and I can notice a lag while i type this so i assume its working right
when you re-flashed the rom it also switches kernels as well. so anytime you flash a rom you need to flash the kernel of your choice as well.
Yeh Im Legit
Member
Ok I just saw on there the Linux kernel in setcpu.. just wipe cache and dalvik and flash the kernel.. right? Don't need to remove the old one? I know before reflashing my rom my min and max were still 998 and 245 how are you people getting 1100and 1200 and lows near 150?
Ocn... Sorry... you're probably sick of answering my noob questions...
What all profiles are you guys running with setcpu?
Ocn... Sorry... you're probably sick of answering my noob questions...
What all profiles are you guys running with setcpu?
Yeh Im Legit
Member
Sorry and if mine was overclocled at 998 is it reasonable that that is what caused my bootloop earlier?
dont be sorry, all i'm doing is paying it forward. i was in the same bot you were in around this time last year. and yes that is all you need to do is wipe dalvik cache and cache and flash a kernel. check you setcpu you might have not gotten su permission to change the settings. select menu in setcpu and select device selection. it should then try again and ask su for permission. once it does that then you can over and underclock.
i do not think that is the case. you should be able to go higher then that.
also a way to tell what kernel you are on go into settings/about phone/software info/more then find your kernel.
Yeh Im Legit
Member
so the good news is i got the kernel on and figured that it was most likely the reason for my boot loop....
the bad news is that i discovered this by checking setcpu when it rebooted after flashing the kernel and seeing how high it would go... it got up to 1260 now in the second that it was at 1260 it went back to a boot loop so i once again reflashed my rom but this time it stayed stuck at the white preboot screen... also to get it to go to the flash from.zip i had to fight my phone to scroll through anom ra... i get' E:cant mount cache:recovery/command" and cant open. .. it does scroll and click but it would show that error at the bottom sometimes...
im on my buddies phone posting this now... im one click away from runnin recovery to back to just rooted... any other option before i do this???
the bad news is that i discovered this by checking setcpu when it rebooted after flashing the kernel and seeing how high it would go... it got up to 1260 now in the second that it was at 1260 it went back to a boot loop so i once again reflashed my rom but this time it stayed stuck at the white preboot screen... also to get it to go to the flash from.zip i had to fight my phone to scroll through anom ra... i get' E:cant mount cache:recovery/command" and cant open. .. it does scroll and click but it would show that error at the bottom sometimes...
im on my buddies phone posting this now... im one click away from runnin recovery to back to just rooted... any other option before i do this???
so you can't wipe dalvik cache and cache in recovery?
9to5cynic
Android Expert
yeah. Try the safemode with an empty file called "setcpu_safemode" Details are up a few posts. Basically: Open notepad, save file (empty) as "setcpu_safemode" and save it without a .txt extension (so click all files (.*)). When windows *shows* extensions, it should say "setcpu_safemode".
Place that file on the root of your sd card. Checkout azakabam's and evomattnc's posts for more info.
Place that file on the root of your sd card. Checkout azakabam's and evomattnc's posts for more info.
Yeh Im Legit
Member
Ok I'm back on... Rewiped and re flashed ROM and the cache error went away and it rebooted... so what should i do about the kernel... Does my phone have a weakspot somewhere??? seems like it shouldnt do as bad as it has with kernels, or maybe ots just my noobness but I just checked to see how high it went and it shut down immediately
9to5cynic
Android Expert
Well, are you using the right kernel for your rom? Sense roms need sense kernels, AOSP roms usually require AOSP kernels (sometimes they overlap though (universal kernels))
Check the sticky for Kernels for Dummies, lots of good stuff in there (sbc info ... etc)
Probably don't wanna set setCPU to be "On Boot" until you're sure it can handle it, just to double check.
Yeh Im Legit
Member
Kings alliance supports gold monkey there isn't alot for it but gold monkey and one other... If set cpu manages the kernel what is the difference in having one or another when its controlled by setcpu
every kernel reacts differently. setcpu only sets the voltage parameters that the kernel will run.
i do not think that the kernel cause your phone to bootloop. try flashing the kernel again. wipe dalvik cache and cache and flash gm 1.1
i do not think that the kernel cause your phone to bootloop. try flashing the kernel again. wipe dalvik cache and cache and flash gm 1.1
Yeh Im Legit
Member
Yeah that's where I'm at now... Only running 960 and 245 and have a lower screen off profile and in call profile... Just feeling it out cautiously
Yeh Im Legit
Member
I'm having trouble seeing any other explanation on the bootloop... I mean it touched 1260 and went out immediately but im open to ideas so I can hopefully not have to do this twice a day again
ok go into setcpu and select menu/device selection/autodetect speeds/and a window will pop up select ok/superuser will ask for permission and select allow. hopefully now you can now under and overclock.
Yeh Im Legit
Member
Yeah that's where I'm at now... Only running 960 and 245 and have a lower screen off profile and in call profile... Just feeling it out cautiously