Jump to content

  1. 0
  2. 0
  3. 0/5

Rate this Topic

* * * * -
4 votes

[KERNEL 3.0.38+] [July22] KangBang Kernel-v2.0-Last Senseful Edition [AOSP/SENSE] CAF DRIVERS

  • Please log in to reply

OP synergy

synergy

Kanging 'n Baking

Posted 06 June 2012 - 04:43 PM #1

Mod Type:: Kernel

Difficulty:: Very Easy

Mod Status:: Stable

Apply In:: CWM Recovery

Optional:: Overclocked

Requires Root:: No

Optional:: Debloated

Source:: https://github.com/K...ngBanged-Kernel
Are you ready to be KangBanged?

*SHOULD* NOW WORK ON HOLIDAY BASES(UNTESTED)

S-ON? FOLLOW THIS GUIDE TO FLASH THE UPDATEZIP (THANKS TO DASPAZZ FOR WRITE UP)

Main Features:
  • MILD GPU OC (but powerstate scaling/VERY HIGH BUS FREQS)
  • Up to 2GHz OC!
  • NO Bullshit and unnecessary governors (just tweaked OnDemand, Interactive, and InteractiveX for better battery life (sleep state))
  • TinyRCU
  • Compiled with daily built Yuxon toolchain and TONS of optimizations
  • Cleaner CAF3.4 wakelock/power code
  • CAF Block and FS Drivers
  • CAF Scheduler Code (fairsched, etc)
  • Tweaked Voltages (WiFi voltages even)
  • Increased Potential Bus Throughput at higher clockstates
  • CodeAuroraForum GPU/Video drivers (opposed to HTC (the update for AOSP net most a 15-20% gain))
  • Larger PMEM allocations
  • CodeAuroraForum updated headers/drivers such as memcopy/kgsl/msm_rotator
  • CodeAuroraForum FS/Block/MMC/IO Scheduler Drivers/Headers
  • Other CodeAuroraForum Display Header Tweaks
  • CodeAuroraForum VMAlloc
  • CodeAuroraForum IRQ
  • CodeAuroraForum Thermal Drivers
  • CodeAuroraForum Genlock Tweaks
  • TONS MORE that you can see on git (if you can make sense of it...)
  • UNIVERSAL across AOSP/Sense!
DISCLAIMER: I AM NOT RESPONSIBLE FOR PHONES ON FIRE, BLACK EYES, FINDING YOUR PHONE IN ORIFICES SURPRISINGLY, FRIED PHONES, YOUR CAT DYING, OR YOUR KID DOING A LINE OF BATH SALTS AND EATING YOUR FACE


Thanks and Credits:
  • IOMonster
  • KozmikKick
  • Faux123
  • MDeejay
  • ShowP1984
  • Cayniarb
  • Kali-
  • CodeAuroraForum
  • Bhanvidia
  • DeamonFish
  • MrSchapps
  • Kraizk
  • ALL Team Codefire members
  • Google
  • KushDeck
  • Aus_azn
  • BananaCakes
  • Contactwajeeh
  • Rafyvitto
  • dumpsta
  • cruzin_cruzin
  • zacgoesrawr
  • daspazz
  • jenkem110
  • NO THANKS to HTC for HORRIBLE SOURCE
  • NO THANKS to Chad KANGMAN(beats dude)
  • NO THANKS to GSLEON3 for moderating Vivid XDA forum with his own agenda
Guide/Troubleshooting:
  • IF you run into video/music issues, your ROM is using too old of libs. Bug your ROM dev to update to latest CodeAuroraForum libs.
  • Before any issue will be diagnosed, Please wipe dalvik cache, and disable any app that sets scheduler or cpu frequencies.
  • Run Ondemand up to 1.8ghz. Above 1.8ghz scaling may make it unstable
  • If your device is limited at a higher clock, then it cannot handle the voltage required and the regulator is reporting an unstable voltage. THIS IS GOOD.
  • TO RUN 2GHZ FOR BENCHES, RUN PERFORMANCE GOV FOR BENCHES
Changelog
Look on Git until I re-do changelogs (were accidentally lost, and I just started over but got it all back up to speed (and them some) quickly.

Like my work? Feel free to buy me a beer for early morning dev HERE

Download Here!
[b]ChangeLog From SR2.0 Forward

Edited by synergy, 22 July 2012 - 01:08 PM.

  • 15 Likes

rafyvitto

rafyvitto

Developer

Posted 06 June 2012 - 04:44 PM #2

Woot woot =]
  • 2 Likes
"Todo lo demas es un negativo arbitriario en mi tabla infinita de probabilidades...."
"My words are always epic, my wisdom is unquestionable, im a warlock of unforeseen powers"
Device: Sprint HTC ONE
ROM: CM10.1
Do not PM ME regarding rom support, you can get support on my threads.

noone

noone

Average Android

  • 9 posts

Posted 06 June 2012 - 04:55 PM #3

Must be S-off?
  • 1 Likes

OP synergy

synergy

Kanging 'n Baking

Posted 06 June 2012 - 05:03 PM #4

Must be S-off?

Nope, S-off is unnecessary. All you need to do is get CWM recovery.img on your computer, and run (like flashing a boot.img), fastboot boot recovery.img. This will boot the recovery.img and then you can flash the kernel just as if you are s-off.
  • 1 Likes

noone

noone

Average Android

  • 9 posts

Posted 06 June 2012 - 05:54 PM #5

Already have ClockworkModRecovery on my phone,
tried flashing using that an it hasnt worked :(
Is that what u ment?

Edited by noone, 06 June 2012 - 06:20 PM.

  • 0 Likes

Dagnus

Dagnus

Average Android

Posted 06 June 2012 - 06:30 PM #6

nice! and just flash in fastboot noone, not recovery.
  • 0 Likes

rignfool

rignfool

Android Lover

  • 127 posts

Posted 06 June 2012 - 06:32 PM #7

So I installed your kernel... It defaults to 2.05ghz on-demand... Which your post says is unstable...

I backed it down to 1.18... Let it run for a few... And all of a sudden... It had clocked itself down to 594mhz...

Not sure if that is a feature?

Sent from my HTC PH39100 using Tapatalk 2
  • 0 Likes

jenkem110

jenkem110

Android Lover

  • 149 posts

Posted 06 June 2012 - 07:02 PM #8

NICE 2GHz! ive always wanted 2 push 2 ghz just to say i did. lol. is this the kernel that will be used in cm9?
  • 0 Likes
Device: AT&T LG Optimus G
Rom: CodefireX
Kernel: KozmiKKernel beta 13

OP synergy

synergy

Kanging 'n Baking

Posted 06 June 2012 - 08:07 PM #9

So I installed your kernel... It defaults to 2.05ghz on-demand... Which your post says is unstable...

I backed it down to 1.18... Let it run for a few... And all of a sudden... It had clocked itself down to 594mhz...

Not sure if that is a feature?

Sent from my HTC PH39100 using Tapatalk 2

I just realized I broke the default max. I'll fix it for next release ASAP, though have a few other bugs to work out (this is alpha after all). As far as clocking itself down, I haven't seen the max change on it's own, so you're just seeing the clock scale as it should. Also, I'll edit OP since for most it would seem 2.05ghz scaling is reasonably stable. Another possible bug is camera, though I currently can't test that.

Already have ClockworkModRecovery on my phone,
tried flashing using that an it hasnt worked :(
Is that what u ment?

No, you can't flash an anykernel update zip through recovery if you're s-on. What I wanted you to do was use fastboot to boot the recovery image, then flash it. So you would put the recovery.img in the same directory as fastboot after copying zip to your sd, then run fastboot boot recovery.img. It will boot into the recovery.img, then you can flash the update.zip from recovery. The reason I'm not doing boot.img is because I'd need to include quite a few different boot.img's for different roms.

NICE 2GHz! ive always wanted 2 push 2 ghz just to say i did. lol. is this the kernel that will be used in cm9?

yes it is being used in CM9

Edit: A quick note: If someone runs into camera not functioning with this, please run adb shell cat /proc/kmsg while opening camera, then copy/paste the results. Thank you.

Edited by synergy, 06 June 2012 - 08:10 PM.

  • 1 Likes

noone

noone

Average Android

  • 9 posts

Posted 06 June 2012 - 08:32 PM #10

nice! and just flash in fastboot noone, not recovery.

Okay tried that an getting
FAILED (remote: signiture verify fail)

Assume this is because S-On?

No, you can't flash an anykernel update zip through recovery if you're s-on. What I wanted you to do was use fastboot to boot the recovery image, then flash it. So you would put the recovery.img in the same directory as fastboot after copying zip to your sd, then run fastboot boot recovery.img. It will boot into the recovery.img, then you can flash the update.zip from recovery. The reason I'm not doing boot.img is because I'd need to include quite a few different boot.img's for different roms.


I thought I wasnt quite understanding now i am totally confused, kinda. where do i get the recovery.img from???

Thanks for the help though guys

Edited by noone, 06 June 2012 - 08:39 PM.

  • 0 Likes