• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Quickclock on GB problem.

cougar214

cougar214

Android Expert
After getting my Quickclock back I overclocked my phone and sat back and enjoyed it. But there is one problem, Quickclock isn't applying my settings at boot. Anyone else getting this issue?
 
cougar214 said:
After getting my Quickclock back I overclocked my phone and sat back and enjoyed it. But there is one problem, Quickclock isn't applying my settings at boot. Anyone else getting this issue?
Click to expand...

I don't think any of the OC apps are able to set on boot with GB. QuickClock does not apply my settings after a reboot either.
 
i use milestone overclock and setvsel and mine load up at boot. milestone is for the oc kernel, and setvsel is for, you guessed it, to set my vsel for each freq.
 
Does setvsel work on GB? I tried it out on stock froyo but it wouldn't run correctly. Airmaxx, droid oc does work fine on GB. it even sets on boot. At least mine did. But I like the one click method in Quickclock. I like having an app that overclocks and undervolts at the same time and does it all for me.

Quickclock is working on GB so I guess Ill just have to deal with applying the settings myself manualy until the dev fixes this issue.

mrstealthusmc, can you clarify what you mean by Milestone is for the kernel? I'm not totally sure but I think I may know. Milestone wouldn't be getting physically used right? It's just needed so setvsel can do it's thing?
 
i have the milestone overclock set at 1.2ghz at 65vsel and set to load at boot. i also have setvsel and have adjusted each frequency and vsel, but i also have that set at 1.2ghz at 65 vsel and to load at boot. so, it is my understanding that the milestone overclock loads the overclock module (not kernel, sorry) and setvsel will then be able to set each vsel. i also use gingerbread .588 with drew garens LL Gingeraid 4.2 rom
 
funny, i just tried uninstalling milestone overclock to see if setvsel would work without it, and now i am in a happy bootloop...
 
haha, well, i guess since i deleted milestone and setvsel was trying to find the overclock module, itstarted to bootloop, then my linux machine stopped recognizing my phone so i couldnt sbf, so after 2 hours of trying to figure out the problem, a simple reboot of the computer and i was able to sbf!!!!yay, wow that was a pain.
 
Yeah, you're a jinx too....lol......i tried doing the same thing you did. I didnt get stuck in a bootloop but every time i tried loading setvsel the damn thing kept rebooting. So i loaded a backup and went back to using quickclock until i figure out what happened. Im thinking trying to use setvsel and milestone at the same time caused a severe conflict in the processor.
 
You must log in or register to reply here.
Back
Top Bottom