[KERNEL][Fighter][AOSP][4.4][26Jul] Bubba Kernel - Verizon HTC Droid Incredible 4G LTE

Disclaimer:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed.
* YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
* blah blah blah you get the point.
*/​
1# post: Disclamer - special thanks
2# post: Current release & source
3# post: FAQ - bugs - future features
Donator List: (huge thanks for support)
here
Suggested kernel control app: trickstermod
I don't know if it works because i don't own the device but i have got ville which is pretty similar
[GUIDE]How to compile a kernel
Credits and Thanks:
dsixda, showp1984, ngtools, faux123, Christopher83, franciscofranco, msm8960 team, jrior001

---

Features:
Based on linux 3.4.99
Compiled with linaro toolchain 4.9.1 2014.07 optimized for cortex-a15
Linaro -O3 optimization
avaiable CPU governors: interactive, ondemand, performance, powersave, intellimand, intelliactive
avaiable GPU governors: ondemand, performance, simple
avaiable schedulers: row, deadline, noop, cfq, bfqv7r4, fiops, sio
Sleepy Plug
NTFS read & write support
exfat support
UTF8
Voltage control
Sweep2Wake
Double tap 2 wake
Pocket detection
Intelli-thermal
zRam with LZ4 compression
zCache with LZ4 compression
CPU OC to 1.7 GHz
GPU OC to 512MHz (3D) and 320MHZ (2D)
Faux sound control v. 3
Improved alghorithm: SHA1, AES, SQRT, lib/string (glibc version), lib/memcopy (glibc version), XOR (neon)
dynamic fsync by faux123
fastcharge
powersuspend driver (replace earlysuspend)
KCAL control (RGB)
heavly patched memory allocators, RWSEM and mutex (take a look at my github, too many changes to make a list here)
Changelog:
Code:
[JUL 26 2014]
Revert "prctl: adds the capable(CAP_SYS_NICE) check to PR_SET_TIMERSLACK_PID."
Revert "prctl: adds PR_SET_TIMERSLACK_PID for setting timer slack of"
add qseecom support
some defconfig changes
cpufreq: revert CAF's cpu policy save code
sched/cpuidle: reduce IPI storm. Backport upstream 3.16
mm, hugetlb: improve page-fault scalability
mm: per-thread vma caching
update compiler to linaro toolchain 4.9.1 2014.07 optimized for cortex-a15
update to 3.4.99
added KCAL control by faux and fixed by me
add F2FS support
Revert "msm: htc: update mem mapping"
[JUL 17 2014]
update to 3.4.98
sync with cm
sync with codeaurora/kk_2.7-stable
update sleepy_plug
bfq: BFQ-v7r5
bugfix from google (see github)
[JUN 29 2014]
Remove JustArchi GCC flags cos they are unstable
update to 3.4.95
sync with CM
sync with codeaurora/kk_2.7-stable
ext4: Speedup WB_SYNC_ALL pass called from sync(2)
[JUN 19 2014]
update compiler to linaro toolchain 4.9.1 2014.06 optimized for cortex-a15
update to 3.4.94
remove -fdata-sections GCC flag (cause of reboot issue)
sync with CM
sync with codeaurora/kk_2.7-stable
updated sleepy_plug
[JUN 09 2014]
sync with codeaurora/kk_2.7-stable
memset patch to fix bootloops
[JUN 08 2014]
3.4.92
reverted some KGSL CAF patches
removed -ftrace flag
sync with CM
improved int_sqrt algorithm
update bfq to v7-r4
[MAY 28 2014]
sync with codeaurora/kk_2.7-stable
update sleepy_plug
cpufreq: ondemand: Calculate load_at_max_freq based on current policy->max
sched: add do_avg_nr_running to fix avg_nr_running
[MAY 19 2014]
update to 3.4.91
merge codeaurora/kk_2.7_rb1.38
update bfq to v7-r3
sleepy_plug now supports quadcore CPUs
fix headset support (CM)
new GCC flags
update compiler
[MAY 03 2014]
block: support volname for HTC devices with proc/emmc support
[MAY 02 2014]
compiled with Linaro GCC 4.9.1 optimized for cortex-a15
sync with CM
update devices_htc from Jet jb 4.3 kernel
update headset driver from Jet jb 4.3 kernel
update memory mapping (more RAM avaiable)
update pn544 driver
update bma250 driver
OC to 1.7GHz
[APR 29 2014]
fix boot
update to 3.4.88
sync with codeaurora/kk_2.7-stable
some other CAF patches
max OC to 1.5 GHz
[APR 28 2014]
fixed boot (?)
[APR 24 2014]
first release
If you like my work please consider making a donation, I spend almost all my free time on making this kernel the best
i'll buy another phone to continue to support the android development!
Download:
androidfilehost folder: http://www.androidfilehost.com/?w=files&flid=14183
normalToQV: http://www.androidfilehost.com/?fid=23501681358544069
(if you don't see the new version just wait some minutes, it's uploading)
Kernel Source: Github

---

Q: What is QV version?
A: QV means "qualcomm voltages". qualcomm made a patch and stuck all voltages to 1150mv to improve stability. QV version has got all 1150 mv for each freq (like older 3.4 kernels).​Q: I plugged in my pen drive but i can't found it
A: look in /mnt/usbdisk folder.​Q: What's and how i enable/disable fastcharge?
A: with fast charge an USB charger will recognized as AC charger. it won't charge your phone faster with an AC charger. it may not charge your phone faster with an USB charger.
with the usb cable UNPLUGGED edit /sys/kernel/fast_charge/force_fast_charge:
0 -> disable
1 -> enable
than plug in the cable​Q: i've got random reboots, what do you need?
A: first read here
write this info:
kernel version
ROM
governor
scheduler
undervolted? if yes don't undervolt
QV version? if no use it
last_kmsg
Q: what's BLN and how i enable/disable it?
with BLN on when you received a notify the soft key will blink.
to enable/disable edit /sys/class/leds/button-backlight/blink_buttons:
0 -> disable
1 -> enable​Q: what's s2w and how i enable/disable it?
Sweep2wake allows you to wake up your device by swiping your finger across the capacitive buttons from left to right. Swiping from right to left will put it back to sleep (sweep2sleep).
to enable/disable edit /sys/android_touch/sweep2wake:
0 -> disable
1 -> enable​Q: what's dt2w and how i enable/disable it?
DoubleTap2Wake (DT2W) allows you to wake the device by double tapping the capacitive buttons.
to enable/disable edit /sys/android_touch/doubletap2wake:
0 -> disable
1 -> enable​What's sleepy_plug and how can i activate/deactivate it?
sleepy plug it's an hotplug driver (it decide when turn on the second core) i wrote. it's an experimental driver and it may have got performance problem. if you notice some decrease in performance report it.
to enable/disable edit /sys/module/sleepy_plug/parameters/sleepy_plug_active:
0 -> disable
1 -> enable​Install instruction:​S-OFF:
- flash the zip in recovery
- wipe caches (optional)​S-ON:
Windows & Linux:
flash kernel zip.
stay in recovery after flashing the zip
from command prompt (ot terminal) on PC:
Code:
adb pull /tmp/newboot.img
adb reboot-bootloader
fastboot flash boot newboot.img
fastboot reboot
OLD S-ON INSTRUCTION:
Linux:
- flash awesome kernel cleaning script: http://d-h.st/HDi (optional)
- flash the zip in recovery (obsolete, for older kernels with modules outside built outside)
- use zImage switcher to make a new boot.img
-
Code:
fastboot flash boot newBoot.img
Windows: (don't ask me how it works or everything else, i don't know and they have got tutorials on their site)
- repack your ROM boot.img with mine zImage using Virtuous Ten Studio http://www.virtuous-ten-studio.com/index.php/downloads
-
Code:
fastboot flash boot newBoot.img
Bugs 3.4:
None
If you want to use my kernel for your ROM just use it and cit me in credits

---

Great thread and great work. I will be flashing this tonight over a fresh install of snapshot M5 CM11! I'll let you know how it runs, hopefully smooth as butter. Thanks again

---

rmbq said:
Disclaimer:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed.
* YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
* blah blah blah you get the point.
*/​
1# post: Disclamer - special thanks
2# post: Current release & source
3# post: FAQ - bugs - future features
Donator List: (huge thanks for support)
here
Suggested kernel control app: trickstermod
I don't know if it works because i don't own the device but i have got ville which is pretty similar
[GUIDE]How to compile a kernel
Credits and Thanks:
dsixda, showp1984, ngtools, faux123, Christopher83, franciscofranco, msm8960 team, jrior001
Click to expand...
Click to collapse
Can you compile a 4.1.2 SENSE5 kernel? all working
Don't care about my awkward English

---

zhaotiantian said:
Can you compile a 4.1.2 SENSE5 kernel? all working
Don't care about my awkward English
Click to expand...
Click to collapse
I don't work on sense
Inviato dal mio One S utilizzando Tapatalk

---

looks great.. just flashed CV on new cm11 nightly.. bootloops htc screen

---

Non QV bootloops on HTC Quietly Brilliant screen. CM 11 4/14 nightly. I'll try the QV another day.

---

I think I used wrong voltages for you, freq it's 1.5 GHz instead 1.2. I'll make another version asap

---

I'm running CM11 snapshot M5, I'm not sure which version to flash. Thanks for the work!
Sent from my Incredible 4G LTE using Tapatalk

---

try the new version!

---

still no boot for me, tried new non-qv..

---

and this one? http://www.androidfilehost.com/?fid=23329332407590054

---

^^ there we go! that one works so far so good.. only thing i noticed is max cpu option is still 1728, i don't think this phone can go above 1512, but i may be wrong?
edit: also, trying to disable the button backlight is buggy. the 3 lights will still blink intermittently..

---

itrx said:
^^ there we go! that one works so far so good.. only thing i noticed is max cpu option is still 1728, i don't think this phone can go above 1512, but i may be wrong?
Click to expand...
Click to collapse
officially only 1242MHz even ... but it runs fine at the usual (slight) OC 1458MHz or 1512 ... but also 1674 is fine ... just consumes more battery and gets hotter. even up to 1809MHz should be stable for most, but that is way to hot and batt-sucking imho!

---

official booting version is up, i limited OC to 1.5, 1.7 is too much xD

---

rmbq said:
official booting version is up, i limited OC to 1.5, 1.7 is too much xD
Click to expand...
Click to collapse
for reference our/my: on the Infernal / Infernal-K99 (ICS-Sense custom kernel) ... 1512 / 1458 was set as the std max CPU freq, but we allowed up to 1809 on Infernal (which I admit is rather really high xD) ... and 1674 max OC on Infernal-K99 => the max OC of 1674 is usually auto-selected for the 2nd-core on demand whereas the 1st core admits to whatever limit is set (thus usually 1458)
no real heat probs at all since months with that setting ... 1809 tended to get rather hot (e.g. on reboots) ... not so with 1674 (and a not too high voltage as set in std)
oh, and limiting the "OC" to 1512 isn't really an OC limit ... as that was std for the MSM8960 on almost all devices! (just fireball got an artificial limit of 1242 to further improve on batt runtime). so from that point of view, only everything _above_ 1458/1512 should be considered OC.
just my 2c
PS: apart from that, thanks for working on fireball AT ALL ... there aren't many devs left here unfortunately
on a note: please also enable 192MHz as the lowest CPU freq while you are at it ... never heard any complaints about it for our custom-kernels ... _and_ it greatly improves on total runtime, if 192MHz as lowest for CPU is set ... instead of the regular 384MHz only
cheers,
kimba99

---

Kernel is pretty smooth and getting great battery life, thank you indeed! I'd agree with adding 192Mhz as well.

---

kimba99 said:
for reference our/my: on the Infernal / Infernal-K99 (ICS-Sense custom kernel) ... 1512 / 1458 was set as the std max CPU freq, but we allowed up to 1809 on Infernal (which I admit is rather really high xD) ... and 1674 max OC on Infernal-K99 => the max OC of 1674 is usually auto-selected for the 2nd-core on demand whereas the 1st core admits to whatever limit is set (thus usually 1458)
no real heat probs at all since months with that setting ... 1809 tended to get rather hot (e.g. on reboots) ... not so with 1674 (and a not too high voltage as set in std)
oh, and limiting the "OC" to 1512 isn't really an OC limit ... as that was std for the MSM8960 on almost all devices! (just fireball got an artificial limit of 1242 to further improve on batt runtime). so from that point of view, only everything _above_ 1458/1512 should be considered OC.
just my 2c
PS: apart from that, thanks for working on fireball AT ALL ... there aren't many devs left here unfortunately
on a note: please also enable 192MHz as the lowest CPU freq while you are at it ... never heard any complaints about it for our custom-kernels ... _and_ it greatly improves on total runtime, if 192MHz as lowest for CPU is set ... instead of the regular 384MHz only
cheers,
kimba99
Click to expand...
Click to collapse
about OC ok, i didn't know your device can handle 1.7 GHz and i'll enable it again in next version.
about 192MHz i don't know if i ever will enable it

---

rmbq said:
about 192MHz i don't know if i ever will enable it
Click to expand...
Click to collapse
About over/down clock/voltage CPU & GPU, please check this post:
http://forum.xda-developers.com/showthread.php?t=2217285?&p=51891887