KiNgxKernel #3/#3 "It's Charged"

[rugbyua9]

Thought you guys would like to know. KingKlick has released his 3rd kernel. This one is called KiNgxKernel #3/#3 "It's Charged". He might be doing an update to this kernel too, as posted on page 129 comment 1287. He has it set to default to powersave governor and probably will have it changed to interactive or on demand. This will only slow down your boot time and can be changed via SetCPU to correct. Look for the update in the next coming days.

http://forum.xda-developers.com/showthread.php?t=760050

Here is the changelog:
Kernel #3

- BFS Scheduler patched up to BFS330
- Applied and tweaked BFS330 test patch on top
- Voltage tweaks for battery life (245Mhz is $$$)
- Higher clock speeds will be MUCH more stable now! (1.113=ez)
- Battery charging tweaks to allow your battery to charge faster
- Be sure to wipe dalvik cache before flashing
- Compiled with neon arm optimizations
- Quadrant scores boosted
- Now using powersave governor, feel free to change it via SetCPU
- Cifs module compiled as a module per your requests
- More I will add

 

[FD2]

This kernel has some issues. He will be updating it tomororow.

 

[Upstreammiami]

Did you wipe dalvik cache before flashing. Cuz I don't have issues

 

[FD2]

Tried BFS#2 without Setcpu battery was always warm and drained phone rapidly Quadrant 1200+

Loaded BFS#3 without Setcpu it was slow and jumpy Quadrant dropped to 400 range.

I am back at BFS#1 this time without Setcpu..

I suggest changing the stock profile back to interactive governor. Defaulting on powersave makes boot-up veeery slow.

Wow...nothing like a cap of 245mhz.


King...what was the thoughts behind this change?

He's talking about powersave. When you're in powersave mode, the phone doesn't clock it higher than your minimum speed. So the phone is booting up at a 245MHz clock without overclocking to stock. And considering SetCPU doesn't work until the system boots up, it takes a very long time. But it's good to see you're going to change it.

The current issues have nothing to do with wiping.

 

[Upstreammiami]

Just change it on setcpu

 

[rugbyua9]

Yup... it's just the kernel stock profile is set to Powersave which I said in my original post. There are no other issues.

SetCPU fixes it after boot...or just wait till tonight/tomorrow for the update.

 

[JB turbo]

I know this is probably a dumb question but how do I wipe dalvik cache? Thanks

 

[rugbyua9]

I know this is probably a dumb question but how do I wipe dalvik cache? Thanks

In clockwork it will be under the Advanced settings.

 

[Upstreammiami]

Crazy how lagy the phone is at 245 lol .. Feels like a blackberry

 

[Adrynalyne]

Crazy how lagy the phone is at 245 lol .. Feels like a blackberry

I still don't know what he was thinking. Although he is also arguing with us that he is building from the latest source, and is not

 

[mikestorm]

I still don't know what he was thinking. Although he is also arguing with us that he is building from the latest source, and is not

#4 is out with latest source

Kernel #4 changelog

- Now based off of NEW fresh source code from HTC
- Default CPU governor changed to 'Interactive'
- Numerous small changes I won't list that htc did
- Removed bloat from kernel
- Merged all my commits into the new code so
- Still using BFQ I/O scheduler
- Much much more check my code if you have any questions. I am heading out for the night