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

Root 2.6.32.15 KiNgxKernel #1 with SVS and HAVS implemented

Hand76 said:
Yes but like I asked in the XDA thread what the hell does that mean?

Either SetCPU is running or it's not. If you use it to o/c it is running.



BFS #5 is up. I will try it and hope for the best.

KingxKlick Forums • View topic - [KERNEL] [2.6.32.15] [HAVS] [BFS] KiNgxKernel #3/#5
Click to expand...

Meaning that if you use SetCPU then some of the code in his kernel, which is supposed to conserve power, will not work. This is because setCPU imposes priority over the kernel. If you are overclocking then you won't need his power saving features/they wouldn't work anyway.

This kernel fixed some choppy sound/lag issues in games/emulators I usually have with Sense-based ROMs.
 
BiNGE said:
If you are overclocking then you won't need his power saving features/they wouldn't work anyway.
Click to expand...

Yea but no one overclocks 100% of the time. I think most of us are looking for the battery saving features 90% of the time with some slight overclocking thrown in when we need a boost.

My understanding is (just like Hydras kernals) you have the undervolt to save on battery life when SetCPU is set to 998 or lower clock speed but lose that advantage when you start to overclock. Which is understandable.

SetCPU doesn't do anything else. It shouldn't effect the rest of his kernal. Especially if you are leaving the govenor the same as King has it set. (now at Interactive)
 
Hand76 said:
Yea but no one overclocks 100% of the time. I think most of us are looking for the battery saving features 90% of the time with some slight overclocking thrown in when we need a boost.

My understanding is (just like Hydras kernals) you have the undervolt to save on battery life when SetCPU is set to 998 or lower clock speed but lose that advantage when you start to overclock. Which is understandable.

SetCPU doesn't do anything else. It shouldn't effect the rest of his kernal. Especially if you are leaving the govenor the same as King has it set. (now at Interactive)
Click to expand...

I agree you're touching the right ideas, but KK's Kernel feature HAVS does exactly what you're stating. All that's being said is that SetCPU will interfere with the Kernel's native undervolting and underclocking known as HAVS. I used SetCPU with all of KK's kernels but with #5 I really don't see the need. With #4 it was necessary as HAVS was broken.
 
Hand76 said:
So you suggest just completly uninstalling SetCpu?
Click to expand...

I did since I wasn't overclocking. I had a screen off profile set but I really wanted to see if it was saving as much battery as people claimed it was. On Thursday, the first day without SetCPU, I had a little over 14 hours of up time and over 4.5 hours of up time with 43% battery left. On Friday, I had over 17 hours of up time and just over 7 hours of awake time with 31% of battery left. That's just as good if not better than what I was getting while using SetCPU. Both days were with Kings BFS #4. Loaded up BFS #5 today and I'll see give that a couple days and see what's up.
 
upther said:
I did since I wasn't overclocking. I had a screen off profile set but I really wanted to see if it was saving as much battery as people claimed it was. On Thursday, the first day without SetCPU, I had a little over 14 hours of up time and over 4.5 hours of up time with 43% battery left. On Friday, I had over 17 hours of up time and just over 7 hours of awake time with 31% of battery left. That's just as good if not better than what I was getting while using SetCPU. Both days were with Kings BFS #4. Loaded up BFS #5 today and I'll see give that a couple days and see what's up.
Click to expand...

TBH, I wouldnt uninstall setCPU. I did when I installed the new BFS #5 kernel, and when my screen was off, i got 2 texts and the battery went from 95% to 83% in 2 hours with no use (i didnt even see the texts cause i had a baseball game, so screen off the whole 2 hours), so i reinstalled setCPU when my battery was at 73%, and with a screen off profile the battery ended at 67% after a whole 6 hr work shift getting like 15-20 texts and having screen off majority of the time.
So, I would keep setCPU.
 
Ok, so I am back to kernel #2. With every single kernel but the #2 (of king's, haven't tried hydra or others), handcent eventually freezes up on me without me knowing, keeping my phone awake in my pocket and draining my battery. I have uninstalled, reinstalled handcent and everything, but once it freezes, i can't get it to work anymore until i restore to when i had #2. So I am back to #2 for a while now.
 
Well #5 starts to slow down my phone now too.

After 60 hours of uptime cpu jumps to 100% and needs a restart. Sometimes starting up or exiting out of certain apps will fix it, but others are starting to report the same thing as well in the XDA thread. :(
 
You must log in or register to reply here.
Back
Top Bottom