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

Root KingxKlick releases AOSP kernel(CM6/AOSP roms)

Two_cents

Well-Known Member
it was released a few days ago and didn't know if anyone has seen it... its a BFS Kernel for AOSP roms such as Ruby and CM6... he reccomends wiping dalvik cache before flashing the kernel.. first boot is a long one as usual with the wipe

KingxKlick Forums • View topic - [KERNEL] [AOSP/CM] [2.6.32.15] [HAVS] [BFS] KiNgxKernel #1

quad scores on cm6
CAP201009131420.jpg

CAP201009131419.jpg
 
What do you have it clocked at. I can't stay stable past 1.13 my best was a 1800 flat and I haven't seen it dip under 1675 . My best before was 1575 I believe and that was when I was able to keep 1.15 stable for a few runs before it froze.
Guessing 1.19ghz would probably be high 1800s
 
I can get mine to work past 1.113 ... I tried anything higher and either set cpu crashes or quad freezes and closes... that wa at 1.113 with performance governor
 
I tried this kernel yesterday on Ruby 1.1.1. I had it going for a while and it seemed to make my phone slower. I had it overclocked to 1.13. It seemed rather sluggish and it seemed like it took longer for the phone to wake up when I hit the unlock button. The lock screen would lag and stall. Are there any settings that have been proven to be optimal with this kernel so that this does not happen? I would really like to use this kernel for it's battery life and other goodies, but it just doesn't seem to want to work well for me. Any suggestions?

EDIT: Oh and my phone doesn't like anything past 1.13. I had the SetCPU setting at Interactive as well and had a profile set to run at 345 (I think) when the screen was off.
 
I run most of my kernels at 883 which is slightly under clocked ... never have any sluggish at all... did you whipe your dalvik cache? thats the only time I have ever had slugish kernels is when I didn't know to whipe that between kernels... I haven't run ruby but I am back to virtuous now since I really like the sense features that cm and ruby are missing... all i ran cm for was for the galaxy theme... but now there is a virtuous theme so I'm extra happy now
 
I run most of my kernels at 883 which is slightly under clocked ... never have any sluggish at all... did you whipe your dalvik cache? thats the only time I have ever had slugish kernels is when I didn't know to whipe that between kernels... I haven't run ruby but I am back to virtuous now since I really like the sense features that cm and ruby are missing... all i ran cm for was for the galaxy theme... but now there is a virtuous theme so I'm extra happy now

Yup, I wiped the dalvik cache before installing the kernel. I wonder why I haven't had much success with these kernels. I even tried the kernel for sense when I was running Virtuous and I had the same results. I have found that Hydra Kernels have performed the best for me.
 
I didn't like hydra kernels personally cause it was like all or nothing.. they recommend not to use set cpu so once I install the 1.15 I'm stuck basically... kings at 883 give me great battery and have worked well for me... both the aosp and the sense kernels...
 
Has anyone had any problems since flashing this kernel? My battery used to do very well in the beginning, but now I've been seeing it drain quicker. In battery stats the Android System is using a lot of battery, it comes in second after the display. I've never seen it take this much before with the stock CM kernel. Plus, and I don't know if it has anything to do with the kernel, my Dinc seems to run a little slower. It takes longer to load up the contacts in my call log and there seems to be more lag when using the keyboard.

Anyone else?
 
Has anyone had any problems since flashing this kernel? My battery used to do very well in the beginning, but now I've been seeing it drain quicker. In battery stats the Android System is using a lot of battery, it comes in second after the display. I've never seen it take this much before with the stock CM kernel. Plus, and I don't know if it has anything to do with the kernel, my Dinc seems to run a little slower. It takes longer to load up the contacts in my call log and there seems to be more lag when using the keyboard.

Anyone else?
not me, i am running shadowrom with this kernel and my battery life is steller. 100% at 7am when i take it off the charger, 5pm its at 65% usualy and thats with me on it all day, being a buisness owner and all, i am on it quit alot. my quads are in the mid 1700s like the first pics and i am completely stable at 1.115 over. all my profiles are set to ondemand and i havent had one bug except for a force close. have been running this setup for 72 hours and no lockups or freezes either.
 
not me, i am running shadowrom with this kernel and my battery life is steller. 100% at 7am when i take it off the charger, 5pm its at 65% usualy and thats with me on it all day, being a buisness owner and all, i am on it quit alot. my quads are in the mid 1700s like the first pics and i am completely stable at 1.115 over. all my profiles are set to ondemand and i havent had one bug except for a force close. have been running this setup for 72 hours and no lockups or freezes either.

Wow, I wish my battery life could get close to that.
 
is anyone else lagging a lot with this? the stock cm6 kernel runs smooth and quadrants are 1500-1550 and ruby 1.11 1550-1580 and then with with this kernel with wiping data and davlik cache both roms run 1175-1280?

I'm not really sure whats going on
 
So is this kernel compatible with Virtuous 3.0.1?

Nope. I use the custom v2 kernel when on virtuous with setcpu set to ondemeand and a screenoff profile. I've tried the KK kernels with virtuous and adrynalynes custom kernel was far superior in battery life dept. It also ran just as smooth if not smoother.
 
What I did find interesting is I believe this kernel is the stock kernel on the MIUI ROM that I'm now running. It's listed as 2.6.32.15-king-aosp-havs-OC-UV erik@Ubuntu #1

That's the same one right?!
 
running king kernel aosp #1 and running really well now at 1.19 stable quadrants 1710-1770 on ruby 1.11

for whatever reason #2 and my phone are not friends

edit: running #1 on cm6 at 1.19 stable and 1821 on quadrant 39.7 mflops on new linpack
 
Back
Top Bottom