He probably meant module, not kernel
4x4, I can be a smartass, I know,..and if irony were made of strawberries, we would all be having fruit smoothies for a month... and again, I really AM sorry about that(text doesn't show emotion as well as being in a face to face conversation), but, regardless, I got over zealous w my defense...I gota have a big brick wall to defend myself and make my superiority known when im dealing w the snot-nosed-kids that work for me...I shouldn't bring that persona here, again, sorry, now to the fun-phone-stuff.(i always use my phone and i hate scrolling back up...marijuana makes things slip my mind so ima try to recall best i can)...droid overclock wasnt what i did the custom txt file w frequencies, it was setcpu, it has an option to load a custom list...in a thread i read the guy suggested using setcpu and milestone in tandem with each other, by loading the custom frequency list onto setcpu and then loading milestone and sliding it over to custom, all I did on the txt file was add one more frequency being 1.4(not literallyy 1.4, it was 1400000), saved it to root of sd card and it loaded fine...when I say it 'jacked my phone up' I use that loosely, and basicly meant that it simply slowed down my phone and made it start sweating like a hooker in church(figuratively speaking)...after which, I tried using each app han-solo style, and it left me with the same results, sluggishness and a tendency of random overheating, even when not in use... ...I also used quickclock, but, I never got far with this app, it always threw me an error message saying it can't unload the current module(the one that comes stock on the global), and after trying a few times I just threw in the towel on that one... ..if anything, I would want droid overclock on my phone as my oc app, just because it was solid on my d2 and I fell in love w it...but, then I got this global...god I hate this phone... ..I think that covers it, but..I,again, could be wrong
Your problem is 1.4....not all phones hit the perfect mark. Set 1.35 max and it will usually work fine. Sweet spot for most droid 2/x and ms2...higher puts the cpu in protect mode...
Sent from a D2G Dark Angel
I selected use most current module and am on interactive governor ocd to 1.35mhz. Its seems to be working great. Super responsive and no lag, some of the problems I encountered before with droid 2 overclock. And it shows 1.35 in the 5th slot. Two profiles, screen on and off. Battery hasn't got above 26 degrees C. I will see how it acts today while at work, as far as overheating and batt life change.
my ANGEL blacked out at 1.35 Ghz
Hottie, I always heard quadrant scores are useless, why, I am not sure, havnt read up on it in detail, but several people have said this to me...maybe someone can shed some light?
Ok now I am not an expert on overclocking, far from it, but those results are quite odd. I honestly cant say much more then that, but will elaborate on my Droid OC App experience latter on. I know that when using setcpu and milestone, I saw no signs of sluggishness.
I seem to recall, now that you mention it a guide about importing profiles in to setcpu and using it with Milestone. Might try to dig it up and see what I can come up with on all that.
Ok now on to my results from Droid Overclock, I did use the newer module. I didnt try any OCing itself, I just played with profiles for now. The only profile I set was Screen Off = 300 Mhz with a conservative governor. Problem I saw was that occasionally when I wouldnt use my phone for awhile, and then started using it, I saw bad lag. Almost unusable. When I would check Droid Overclock I noticed my scaling was set at 300 max and min. Might play with profiles a bit more, and some over clocking.