[Kernel]***[M8] B14CKB1RD AOSP [11/27]***
B14CKB1RD
Kernel for the HTC ONE M8
~THE MOST UP TO DATE KERNEL FOR THE HTC ONE M8! YOUR ANSWER FOR PERFORMANCE AND SECURITY!~
B14CKB1RD is a custom kernel meant for AOSP KitKat based Roms. There are 8 governors and 8 I/O schedulers. It's built with the 4.10 sabermod toolchain and -O3 compiled for best optimizations and performance. It comes fully stable and suitable for what uses you want from your phone. From best battery life to best performance you can find for your phone. As usual happy flashing. Just note I am not responsible if you (the user) messes up your phone. I will always be around to help in any way i can so if any issues arise please feel free to send me a pm or ask in the thread. ABSOLUTELY NO TROLLING, BASHING, OR ARGUING on the post please. Actions will be taken and you will loose my personal support.
How to Install:
1. Boot to recovery
2. Flash Kernel .zip
3. Wipe Cache
4. Wipe Dalvik Cache
5. Reboot to profit
Click to expand...
Click to collapse
Features:
Governors:
Dancedance
Intelliactive
interactive
Ondemand
Optimax
Performance
Smartmax
Wheatley
I/O Schedulers:
Bfq
Cfq
Deadline
Fiops
Noop
Sio
Vr
Zen
TCP Congestion Controls:
Bic
Cubic
Highspeed
Htcp
Hybla
Illinois
Lp
Reno
Scalable
Vegas
Veno
Westwood
Yeah
After Install Instructions:
I personally Prefer the use of Trickster MOD for kernel tuning. if you want to switch to using trickster i recommend removing built in kernel tweaking app if possible. I used rom toolbox's app manager to do so. Trickster can be found on Play Store or on xda. For frequency changes to stick: In Trickster Mod, change to the frequency you want and tap on "Frequency Lock" to enable it and tap on the checkmark at the top right to apply and save
Notes:
Again, if you need any kind of support, do not be afraid to ask politely in this thread! Check back often, as I am patching this kernel on an almost daily basis to continue to update it, I am a stickler for security just as much as performance.
Click to expand...
Click to collapse
Credits & Thanks
@Snuzzo (for teaching me all he knows about kernel and his code used on many devices)
@REV3NT3CH ( for being a great source of support, guidance and inspiration. Also for allowing me to build his famous B14CKB1RD Kernel for our M8)
@savoca (for his work and code used on the m8 and many devices, for helping me with the zip script and for releasing the furnace kernel which I used as my starting point)
@xboxfanj (for his work, code, and answering my [at times silly] questions and sharing fixes with me)
and to any other devs i missed...all your work is very much appreciated. if you feel i should put you on the list let me know via pm and ill do so
XDA:DevDB Information
[Kernel]***[M8] B14CKB1RD AOSP [11/27]***, Kernel for the HTC One (M8)
Contributors
Damacy, REV3NT3CH
Source Code: https://github.com/VanirRezound/B14CKB1RD_kernel_m8
Kernel Special Features:
Linux Kernel 3.4.34 (We are updating the kernel often, we started on 3.4.0
UnderVoltage Control
DoubleTap2Wake
Battery Optimizations
Version Information
Status: Stable
Current Stable Version: 3.4.34
Stable Release Date: 2014-11-20
Created 2014-11-27
Last Updated 2016-08-13
A Special thank you to @jtommyj for the donation!
FAQs:
Q: Damacy, is there an available, up to date features list?
A: Yes there is! @JennyLikesSka' s FULL FRONTAL, uncensored, IN-YOUR-FACE Feature list!
Q: Damacy, do you have a Lollipop version of thsi kernel available?
A: Why yes I do! See the above post!
Q: Damacy, what ROM do you use for your phone and for your testing purposes?
A: I use EXODUS or Vanir, Here is the nightlies folder for EXODUS: http://www.vanir-exodus.from-me.org/exodus/m8/
Here's the nightlies folder for Vanir: http://www.emccann.net/nuclearmistake/VanirAOSPNightlies/m8/
Q: Why do you have 2 different sources posted above?
A: I'm an IT guy by trade, and it comes down to 3 simple rules: BACKUPS, BACKUPS, BACKUPS!
Q: Damacy, why are you updating this once or twice (or more) a day or once a week?
A: I'm working on patching this kernel, and patching can either be really fast in the case of small patches, or large (like 3.4.12) that take much longer.
Q: What numbering system are you using for kernel versions?
A: I use the number of the patch as the number for the kernel version.
Q: Do you test every patch that you post?
A: Yes, I test EVERY patch that I post before I post it. I won't update the kernel with a patch that causes poor performance (In the case of 3.4.28 caused stuttering and made the phone unable to register with the network provider!)
Q: Why haven't you include feature _____ in the kernel?
A: I am slow to add new features to the kernel because patching is my main focus at the moment. @JennyLikesSka is the lovely feature queen! She adds features that she and I both think will add performance tweaks to the kernel.
Q: I hear you repeatedly mention 'patching' the kernel, what IS patching?
A: Patching is the means for updating the files used to compile the B14CKB1RD (Linux) kernel. Usually, patching is pretty quickly done, but in the case of HTC kernel files, this is the exact opposite. HTC removed all of the comments from the kernel files, so most of the patching I have to do manually (i.e. BY HAND! :X)
Q: How many patches ARE there?
A: In the current 3.4.X kernel line, there are a total of 106 patches. (Yes, dems a lotta patches!)
Q: "Do you have changelogs for these patches/updates. ? "
A: Yes I do! On the kernel source, there's a file called "PatchLog.txt" that has a list of the files changed by the patch.
Q: Damacy, this kernel is so bleedingly fast! Is this even legal?
A: Yes it is legal! >
Q: Does this kernel have a Flux Capacitor or TARDIS Framework inside of it?
A: Well, I think that would be best answered by asking Candle Jac
Awesome awesome work dude!! So happy to see a kernel built with the Sabermod toolchain. Keep it up, flawless
Hope you all enjoy it.... I know @Damacy here has spent many weeks, days and hours working on bringing my kernel to you guys. No need to really thank me...he did all the hard work for you guys to have it...with very minimal help from me
'Course, I find this after I jump on the L train!
Sent from my HTC6525LVW using Tapatalk
nice one! only thing i miss, is multi-rom support!
_moelle said:
nice one! only thing i miss, is multi-rom support!
Click to expand...
Click to collapse
this can be easily added
Nice kernel m8....thanks for the drop
Sent from my One M8 using XDA Free mobile app
Thanks for the kernel downloading and going to run it and see what it's all about
OK just flashed and I see that Faux Sound is on V32 do you plan on updating it to the latest v36
One more question just curious about the governor optimax never heard of this one
dandan2980 said:
Thanks for the kernel downloading and going to run it and see what it's all about
OK just flashed and I see that Faux Sound is on V32 do you plan on updating it to the latest v36
One more question just curious about the governor optimax never heard of this one
Click to expand...
Click to collapse
To answer your first question, we will get to it. This is a DevDB board post, so go ahead and request the feature. Kernel patching is my main priority at the moment.
To answer about Optimax... "This is based on ONDEMAND, like almost all governors that have arisen from XDA. It contains some enhancements from LG, particularly to freq boost handling so it will boost to a set level, almost like HTC's governor. It has different tunables to the HTC governor but it behaves pretty similar, the tunables it comes with default are a bit more conservative."
Can this kernel be used on Android L?
TouchscreenLover1 said:
Can this kernel be used on Android L?
Click to expand...
Click to collapse
I haven't tested it on L yet. I'm curious to see if it is.
Nice job, Larry!
xboxfanj said:
Nice job, Larry!
Click to expand...
Click to collapse
Thanks bro!
It IS a task to get it patched, but I've been learning a ton.
Thanks again for your input and putting up with my silly questions.
Thanks for the kernel!
Sent from my One M8 using Tapatalk
Any idea why trickster mod is not giving me the option to undervolt on this kernel? Normally there's a list of all the frequencies and I undervolt from anywhere between 50 and 65. Thx!
Damacy said:
I haven't tested it on L yet. I'm curious to see if it is.
Click to expand...
Click to collapse
Just reporting in, doesn't boot on latest cm12
Sent from my 831C using XDA Free mobile app
Maestertk said:
Just reporting in, doesn't boot on latest cm12
Sent from my 831C using XDA Free mobile app
Click to expand...
Click to collapse
Thanks. That'll be added on the list of things to add.
Damacy said:
Thanks. That'll be added on the list of things to add.
Click to expand...
Click to collapse
PM sent
I added an FAQ. I hope that this will answer a few of your questions! Not to mention I have followed up with some kernel updates.
Related
[KERNEL][BUILD•2] ★TITANIUM KERNEL★ OC/UV • CIFS • TUN • SIO • And lots more!
Whats up guys,
Presenting you my First Kernel build for SGS III-
~I DO NOT OWN THE DEVICE~
Features - What my Kernel is made up of-
Root, Busybox
Bootanimation Support (/system/media/bootanimation.zip)
CIFS/TUN Support
XZ Compression and Decompression Used
PegasusQ and Adaptive Governer along with other stock Governers
Readahead size set according to disk size
Many lowmemorykiller Tweaks
CFS Autogroup
SLUB Memory Allocator with slight improvements
Some mm Parameters Tweaked
Used memcopy macros and functions
Used Makefile Optimizations!
Disabled GENTLE_FAIR_SLEEPERS
Overclock upto 1.8Ghz (Thnx to AndreiLux)
Undervolt, and UV_mV_table support (Thnx to AndreiLux)
Added Simple IO Scheduler
Triangle Away Compatible Kernel.
CFS Parameters tuned for best performance
Refer to my github and changelogs for more details!
Known issues-
WIFI
Mounting of external SD-CARD
Keep testing and keep giving me feedback!
~Cheers!
Yoo
Downloads-
BUILD#1
BUILD#2
Will need this..
Changelogs-
BUILD#2
Added Overclock upto 1.8Ghz
Added Mv_Uv Support
Removed some debug from Mali driver
NOATIME and NODIRATIME set as default
CFS Parameters tuned
New Voltage interfaces
Add optimised swahb32() byteswap helper
Many small changes which are there in my github...!
Credits-
AndreiLux - For overclock and some cool patches
simone201 - For guiding me on certain issues which I had
gokhanmoral
bangalorerohan
sakindia123
~Its your criticism and feedback that made me a better dev ~
that was fast
last
last reserve
GadgetCheck said:
that was fast
Click to expand...
Click to collapse
Had downloaded it in the morning and compiled also .. Damn these studies.
Have you added the show hidden partitions patch chainfire talked about?
Totòòò said:
Mod Edit: Rubbish
Click to expand...
Click to collapse
Wait. What patch? I just compiled from source directly.
Adi_Pat said:
Wait. What patch? I just compiled from source directly.
Click to expand...
Click to collapse
a patch chainfire released so that his Triangle away app is compatible
Adi_Pat said:
Wait. What patch? I just compiled from source directly.
Click to expand...
Click to collapse
u sure did
sakindia123 said:
a patch chainfire released so that his Triangle away app is compatible
Click to expand...
Click to collapse
The post by Totoo was lame. He could have been a bit more specific than being so rude >_<
Anyways,
This one -> http://git.kernel.org/?p=linux/kern...it;h=371a689f64b0da140c3bcd3f55305ffa1c3a58ef
Patching it up.
Adi_Pat said:
The post by Totoo was lame. He could have been a bit more specific than being so rude >_<
Anyways,
This one -> http://git.kernel.org/?p=linux/kern...it;h=371a689f64b0da140c3bcd3f55305ffa1c3a58ef
Patching it up.
Click to expand...
Click to collapse
Jep! That is the patch.
Thank you! I'll test when I get the device
Btw: I'm also 14 okay near 15 but
Hum I'm 14 and i got the device.
Gesendet von meinem GT-I9300 mit Tapatalk 2
On XDA we encourage development regardless if the person in question owns the device, at the same time we expect our users to read and understand the risks taken in flashing their device.
Thank you.
Adi_Pat said:
The post by Totoo was lame. He could have been a bit more specific than being so rude >_<
Anyways,
This one -> http://git.kernel.org/?p=linux/kern...it;h=371a689f64b0da140c3bcd3f55305ffa1c3a58ef
Patching it up.
Click to expand...
Click to collapse
call the post whatever name you want. I stand to what I told you. Kernels require a certain knowledge and from what I can see you lack that knowledge. However as the mod said, developing is very welcome and so are you but at least before posting a kernel make sure that the device boots up, instead of creating a thread in the dev section saying "hey guys I think I compiled a kernel from source but I have no idea if the device will be able to boot". Maybe I am wrong though, good luck!
I'm testing this kernel. No problem found. I feel standby battery seem better than stock kernel!
Totòòò said:
call the post whatever name you want. I stand to what I told you. Kernels require a certain knowledge and from what I can see you lack that knowledge. However as the mod said, developing is very welcome and so are you but at least before posting a kernel make sure that the device boots up, instead of creating a thread in the dev section saying "hey guys I think I compiled a kernel from source but I have no idea if the device will be able to boot". Maybe I am wrong though, good luck!
Click to expand...
Click to collapse
Your point, but the samsung devices are not bricked with even no kernel present, so if it does not boot, just odin another kernel and you are back...
------------------------------
tapatalked from Galaxy S
Adi_Pat said:
Whats up guys,
I just downloaded GT-I9300 sources some hours back to see what was inside it
And ended up compiling a kernel for GT-I9300 AKA Galaxy SIII
So here we go,
~I DO NOT OWN THE DEVICE~
So here is a Test build,
No features at the moment.. Just some minor tweaking done..
Can anyone confirm and tell me if it is booting?
I will then update the build.
Used the ramdisk which is provided by Chainfire..
Attached is the tar archive to be flashed via ODIN or however u guys flash Kernels.
~~TESTERS REQUIRED~~
~Cheers!
Click to expand...
Click to collapse
adi i will happily test it for u. but i need the changelog first.
Sent from my GT-I9300 using xda premium
Good work
can you share ramfs sources ...
Kernel for stock roms
Features
Overclock
UV
15 Governers
smartassV2
interactive
InterectivX
conservative
ondemand
userspace
powersave
performance
braziliawax
scary
lazy
savageszen
lagfree
minmax
Lionheart
I/O Schedulers
noop
deadline
cfq
vr
sio
XZ compression
Good battery life
very smooth and some other changes
More feachers will add soon
Download
http://www.mediafire.com/?1w6uwvk158t1a6u
For oc and changing governer and for changing I/O schedulers use noFrill app attached at end of post
BUGS
bootanimation not showing (was working with stocklight so I thought its fixed)
Credits
ketut.kumajaya
madman
an0nym0us_
skynet28
dragonn
LibiSC
and some other awesome people
SOURCES
https://github.com/nims11xda/cooper_stock_kernel
Changelog 15-8-2012
15 Governers
Added more I/O schedulers
XZ compression
reduced size of zimage
some other changes I not remember
Changelog 12/8/2012
Fix bootanimation ( work with stock light rom)
additional ram 1-2mb (now 280mb total ram because in past it was around 278mb , not too big jump but its good than nothing
tune dirty background ratio and vm dirty ratio
fix some kernel memory leak
few changes for uv
and some minor changes for future
Changelog 11/8/2012
added more frequency range
better battery drive ( thanks to dragonn and LibiSC)
uv module
thanks nims! Btw it's Features
Nims finally makes his own kernel! NICE!
Awesome!
Nimms got a kernal
Gotta try it
Anyone tried it? I am using CF-Root-S5830-v3.7-b84 on The Myth 2, any difference?
EDIT: TESTING!
EDIT 2: No bootanimation, so far stable and fast on Myth 2.
BLN?
Sent from my GT-S5830 using xda premium
No boot animation in xperiatized v12
sorry 4 my bad english
I think you've missed something.
eagleeyetom said:
Rule No.1 - If you are about to post a new Kernel you need to be in compliance to GPL2 since kernel does contain Linux code, this mean that if you have modified a kernel you MUST provide source code:
(choose what best for you)
- A github link
- packing your kernel and uploading
- a diff .patch files
- Credits to people in case of an already custom kernel
- Sources must be posted in first post of development.
pulser_g2 said:
The GPL is a software license agreement, under which parts of the Android operating system are licensed. The majority of Android is licensed under the Apache license, but the Linux Kernel (which is present in every running Android ROM in some shape or form) is licensed under the GPL (version 2).
Many of the amazing developers at XDA create custom kernels, which feature many improvements and changes over the “stock” kernels released by OEMs, including performance and stability tweaks. This is exactly what the GPL is designed to protect, by ensuring that anyone can get access to the original source code used to build the kernel. Given a suitably configured computer, it should be possible for anyone to reproduce a released kernel using the provided source code.
Recently it has come to our attention that a number of users have been neglecting to follow XDA’s GPL regulations, which amount to posting the sources for any kernel you build from source to share with others.
As a result, we would like to clarify our position on the GPL, and users’ obligations to this effect. By posting your work on XDA-Developers, you are agreeing that it complies with relevant licensing conditions. As such, by posting a kernel or other work containing GPL code, you are confirming to us that you have made this source code available publicly under the GPL, and should highlight this in your thread with a link. (Plenty of respected and trusted sites will host the code for you free of charge, such as GitHub and BitBucket.)
By posting open sourced work on XDA, you are also ensuring that your available sources are up-to-date with the work you have released. This means that if you update your kernel to add a new feature, for example, your sources should be updated to include this change. If they are not, this means you are not complying with the GPL.
There is no provision in the GPL to withhold access to sources based on time or other conditions, so please don’t attempt this, as it will only earn yourself a formal GPL request. If you do not provide the correct, accurate, and up-to-date sources (and keep them up-to-date), you will be non-compliant with the GPL.
In order to be fully GPL compliant, your sources must:
Successfully build and produce a valid output file, which is the same format as provided in the binary
Contain all source code, interface definition files, scripts used to control compilation and installation of the executable (it is not required to include the actual compiler/toolchain, but sufficient information should be made available to obtain the SAME configuration, including compiler flags, as used to build the binary version as released)
The GPL is a legally enforceable license agreement, and while it offers users freedoms to copy and redistribute code, that permission is conditional upon all changes which are released being made publicly available. If you require further advice on this matter, we suggest you review the license itself or consult a lawyer.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
xarcom said:
No boot animation in xperiatized v12
sorry 4 my bad english
Click to expand...
Click to collapse
yes I not noticed that
will fix that
CallMeLewis said:
I think you've missed something.
Click to expand...
Click to collapse
may be
But you also missed
there is written choose what best for you
give credit to people incase of already custom kernel
and I did same and when I add some thing new that I not pached from others github will give sources as now not any that stuff that you like to fork from mine
but will add new stuff soon so will give as patch because i can not upload whole source tree and even samsung already uploaded that
Update
Kernel updated
nims11 said:
Kernel updated
Click to expand...
Click to collapse
hi nims
with previous kernels there was a problem with touch with overclocking !!!!!
has it been resolved ??????
drprateekluthra said:
hi nims
with previous kernels there was a problem with touch with overclocking !!!!!
has it been resolved ??????
Click to expand...
Click to collapse
yes but test and give feedback about it
Can u add inid.d support ?
Nice work BTW !
Cryss said:
Can u add inid.d support ?
Nice work BTW !
Click to expand...
Click to collapse
I assumed init.d was supported as I'm running 2.3.6 KTM and still have a2sd after flashing this kernel. Not sure how it would be working without init.d.
Is it have any lag or bug?
And is it better than batteryextend?
Thanks
Can you make one for cm7
Sent from THE Ace
Update
Kernel updated
fixed few things and added few stuff
for chagelog see 2nd post
may be new update will be next week end as will busy with my study and college
TechNoJerky said:
Can you make one for cm7
Sent from THE Ace
Click to expand...
Click to collapse
I already compiled but want to add more stuff so may be in week or so it will available
Goal: kickstart 3.x custom kernel development.
Changelog:
Built with Google's 4.6 toolchain (* see notes).
Merged Interactive from mainline and enabled input boost by default as part of Google's Project Butter. Interactive will be the only available governor as it's Jellybean's "official" governor and having more selection only slows down the kenel. Interactive will provide more smoothness, especially with input boost enabled, but it may be slightly more expense on the energy consumption (significantly? maybe).
The I/O scheduler is deadline with the fifo batch reduced to 1. For smartphones the best I/O schedulers are often the simpler ones and that means deadline, simple or noop. However, for these 2 years deadline keeps providing me the best results, at least in single-cores. Noop is also available. And yes, I know about the new BFQv4 and all the tweaks/heuristics for flash devices, it's still crap.
Switched the slab allocator to slub with a decreased max_slab_order (Andrea Righi) in order to reduce overhead.
Glibc versions for memcopy and memmove, improved CRC32 and RWSEM algorithms, Tiny Shmem implementation, etc.
Changed RCU to Tiny Preempt without RCU boost, some config cleanups and debug removal (like frame pointer) and so on.
... more changes can be seen in: https://github.com/knzy/lge-kernel-sniper/commits/android-omap3-3.0
A few notes: BCM4329's PM_FAST is already enabled by LGE. I also didn't merge many mainline updates as like it has already found out this often hurts performance and decreases stability. Furthermore, you may notice that there aren't many modifications to the kernel but this is because most patches out there are bull**** and rely on placebo effect. Even some changes I did will have a doubtful influence in the kernel. Oh, one more thing, it's possible to build it with Linaro 4.7 toolchain (it needs a few fixes in Makefile though) but it's less stable and not that much faster.
Download: There'll be no available flashable zips. Just build the kernel if you want and use Aprold's kernel injector package.
Now, any kernel posted in XDA must be GPL compliant which means sharing the source, the config file and the toolchain used. I will now shortly describe how you can build the kernel in a linux (ubuntu-based) machine (by the way, if you see anyone sharing a kernel without providing source, config or toolchain, tell me and I'll report them):
Code:
git clone git://github.com/knzy/lge-kernel-sniper.git ## default branch is omap3-3.0 already
git clone https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.6 ## Add -b master if building on 64-bit
cd lge-kernel-sniper
make ARCH=arm knzo_p970_defconfig
make ARCH=arm CROSS_COMPILE=../arm-eabi-4.6/bin/arm-eabi-
The kernel will be at arch/arm/boot (zImage), use it with Aprold's kernel injector package and voilá.
Awesome Welcome back
koila33 said:
Awesome Welcome back
Click to expand...
Click to collapse
Oh, it's just for fun and to keep aprold busy.
Make sure to add git://github.com/CyanogenMod/lge-kernel-sniper.git as upstream and keep it updated.
Ah, don't disable KSM as I did in my first test release as P970 will probably struggle for RAM in JB.
As for my repo/changes, feel free to fork, test, retest, revert, whatever.
How to use?
Sent from my Nexus 7 using xda app-developers app
wskyvwsk said:
How to use?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Reading couple of lines is too hard for you, eh? You didnt found link to download and just replayed to thread thoughtlessy?
performance test ?
Cedlad said:
performance test ?
Click to expand...
Click to collapse
Benchmarks are so Gingerbread, we don't use that anymore. The most faithful benchmark is everyday's usage.
Done, i have made a new boot.img with your mofifications.
Lets see.
knzo said:
Benchmarks are so Gingerbread, we don't use that anymore. The most faithful benchmark is everyday's usage.
Click to expand...
Click to collapse
But CM10 Kernel is so Bad.. :/ i want to see if there is a better one ..
Cedlad said:
But CM10 Kernel is so Bad.. :/ i want to see if there is a better one ..
Click to expand...
Click to collapse
Yeah, Aprold told me CM10 was still a bit sluggish but I'm not sure it's the kernel fault. Give rmcc some time to iron out the port.
Already tried the kernel and everthing works fluid and fast, i have an issue with wi-fi but that can be fixed easly Good job.
waiting
Nice post knzo
Wow. Good see you again here in XDA.
Welcome hack, knzo.. Nice to see you again at P970 forum
Code:
PS: I'm not typo "back" with "hack" :p
redy2006 said:
Welcome hack, knzo.. Nice to see you again at P970 forum
Code:
PS: I'm not typo "back" with "hack" :p
Click to expand...
Click to collapse
where is the kernel's flashable zip
aasimkhan30 said:
where is the kernel's flashable zip
Click to expand...
Click to collapse
*facepalm*just show that you can't read
Hi guys, I'm going to try build this kernel, just for fun.
It will be my second attempt on building a kernel, my first try didnt work like it should...I wonder why
I'm more into Windows Servers/AD/TCPIP and that kind of stuff and very basic skills on linux.
Can I count on your help?
ontour said:
Can I count on your help?
Click to expand...
Click to collapse
Yeah of course but it's actually quite simple.
Just grab virtualbox and an ubuntu image, install it then open a terminal and do the commands I posted.
As for all the others asking for a flashable zip: no, crackflashers and average users, this thread is not for you. This is for developers, pseudo-developers, enthusiasts and oldschool users who are here to learn, not for those who are here because they think they are entitled to the service of after-market customization.
knzo said:
Yeah of course but it's actually quite simple.
Just grab virtualbox and an ubuntu image, install it then open a terminal and do the commands I posted.
As for all the others asking for a flashable zip: no, crackflashers and average users, this thread is not for you. This is for developers, pseudo-developers, enthusiasts and oldschool users who are here to learn, not for those who are here because they think they are entitled to the service of after-market customization.
Click to expand...
Click to collapse
Hahaha you cant even imagine, how much I like this post Nice to see you back here Do you already have got a P970 again?
Thanks for sharing
Development Goals:
- stability
- energy savings due to more efficient ARM algorithms
- strictly no overclocking unless approved by the manufacturer or my source base integrates it (also, even if my source base integrates it, expect no support for it)
- no undervolting as well unless the manufacturer approves it since it's relatively pointless IMHO...
- all improvements should require MINIMAL user interaction (e.g. you don't need to do anything except flash the kernel or at the very least use SetCPU or the like to set fixed options)
- stability
*note: FAQ is at the 3rd post
Latest Kernel Here
Boot-B -> LBY29G
Boot-O -> LMY47O PH
Boot-M -> LMY47O India
OR
Boot-Universal -> custom recovery flashable zip for all ROMs (I hope :fingers-crossed
*there are significant ramdisk differences between PH and India versions which is weird
20150524_05XX:
- missed something in the previous commit
*this is why I don't like developing kernels on devices I don't use or stopped using actively :/
20150523_21XX:
- implemented minor config changes and a better fix for kernel ooops upon changing CPU governors
20150509_11XX:
- modified proportional frequency allocation algorithm to prefer minimum frequency more
20150503_17XX:
- improved power efficiency of entire kernel
20150426_09XX:
- optimized frequency scaling algorithm to minimize scaling to max during hotplug and under certain situations
20150423_22XX:
- ported one of my Kindle Fire modification which I just remembered could impact performance extremely well
20150417_14XX:
- reverted RCU patch mistakenly committed without dependency which caused RCU slowdown
20150412_20XX:
- numerous backports from linux 4.0 for timer, scheduler and ARM
20150411_21XX:
- numerous backports from linux 4.0 for timer, mutex and slub functionality performance improvements
20150411_18XX:
- kernel tweaks from imoseyon
20150410_17XX:
- timer optimization
20150409_17XX:
- disabled dithering since I think hardware doesn't need it (please report any sign of image degradation)
- now also in flashable zip form (please test as I don't have custom recovery)
20150408_23XX:
- merged Motorola's lowmemorykiller tree improvement
- applied latest ondemand patches to hotplug to improve frequency selection
20150407_14XX:
- recoded some MediaTek modifications with more optimal instructions
- removed more unnecessary kernel options
20150405_19XX:
- removed touch boost as it seems to be unnecessary
- removed some useless logging entries
- adjusted some code that prevented the frequency from being ramped down immediately
20150405_10XX:
- changed default IO scheduler to ROW imported from Lenok source with additional commits due to MediaTek changes
- modified readahead value to 512KB
20150403_16XX:
- bug fix due to incorrect scoping of the touch frequency modification causing excessive use of 747Mhz
20150402_06XX:
- integrated Mali commits by varun
- some minor optimizations
20150331_22XX:
- modified hotplug governor to use ondemand algorithm
- hotplugging now doesn't raise frequency to max before doing a hotplug operation
- touch boost frequency now set to 747Mhz instead of max to lower power consumption
20150329_16XX:
- finished porting all relevant commits from Lenok source to Sprout
- initial full release
- significant changes include:
enabling of full tickless mode
modification of some kernel libraries to use optimized ARM instructions
Disclaimer:
Flash at your own risk.
You can find my other kernels at:
http://intersectraven.euroskank.com/kernels
GitHub is at:
intersectRaven's GitHub
XDA:DevDB Information
intersectRaven's Android One Kernel, Kernel for the OEM Cross Device Development
Contributors
intersectRaven
Kernel Special Features:
Version Information
Status: Testing
Created 2015-04-03
Last Updated 2015-04-02
Special Thanks To:
DooMLoRD - some patches I integrated are from his repo
faux123 - some patches I integrated are from his repo
arter97 - some patches I integrated are from his repo
varun - Mali patches are from his repo and his generic kernel implementation
Other devs I neglected to mention.
FAQ:
1.) How do I flash this on my device?
You could use fastboot, flashify, or flash through recovery using the provided recovery flashable zips.
2.) How do I return to stock kernel?
Use the "fastboot flash boot" command using the stock boot image I provided in another thread here.
3.) Will you be releasing frequent updates?
Right now I don't see anything else needed to improve this kernel as I am quite satisfied with it. You could post suggestions BUT they must have MINIMAL USER INTERACTION or will only seek to enable editing of certain values.
4.) How do you verify that it flashed correctly?
Well, if it booted after fastboot showed the "writing" dialog, then it should be ok already. If you're ultra paranoid that maybe fastboot is lying to you or the NSA doesn't want you to know that it didn't overwrite the stock kernel which contains their secret spy stuff that wants to know how frequently you exercise you could enter the ff. command through adb:
cat /proc/version
and the kernel should show #7 and intersectRaven there together with the date that the kernel was compiled which is what I use to indicate the release.
Reserved 3
which is better thunderzap or yours? thanks
Androidoo said:
which is better thunderzap or yours? thanks
Click to expand...
Click to collapse
I guess it's not right to compare both kernel. Both are awesome, but this kernel are optimized for stock, while ThunderZap are optimized for both CM12.1 and stock.
Will this improve battery life
Sent from my Android One using XDA Free mobile app
Kohul Raj said:
Will this improve battery life
Sent from my Android One using XDA Free mobile app
Click to expand...
Click to collapse
Yes, depends on your usage. I notice a bit of increase in battery life, but that's all depends on your usage.
F4uzan said:
Yes, depends on your usage. I notice a bit of increase in battery life, but that's all depends on your usage.
Click to expand...
Click to collapse
Interesting. What version are you using currently? 20150402_06XX? Can you use the one after that (or the latest one released today) and observe battery life with your typical usage? Might be the bug I introduced due to an improper understanding of what a line was doing.
intersectRaven said:
Interesting. What version are you using currently? 20150402_06XX? Can you use the one after that (or the latest one released today) and observe battery life with your typical usage? Might be the bug I introduced due to an improper understanding of what a line was doing.
Click to expand...
Click to collapse
Sure, I'll try Gotta backup and reflash stock then.
-EDIT : I have flashed it, I'll test it for two days and I'll report the results
F4uzan said:
Sure, I'll try Gotta backup and reflash stock then.
-EDIT : I have flashed it, I'll test it for two days and I'll report the results
Click to expand...
Click to collapse
Thanks! You didn't have to if you're not on stock already so I appreciate it!
I'm happy because android one development is growing now
By the way, i'm in thunderzap kernel, can i flash this directly? or i have to go back to stock kernel then flash this? Thanks..
yonzz said:
I'm happy because android one development is growing now
By the way, i'm in thunderzap kernel, can i flash this directly? or i have to go back to stock kernel then flash this? Thanks..
Click to expand...
Click to collapse
This is for stock ROMs. Doesn't matter if you're using a different kernel, what's important is you're not on CM or any non-AOSP based ROM.
anyone can report the result please ? ?
Sent from my MITO_A10 using xda Forum
mrahmanda said:
anyone can report the result please ?
Sent from my MITO_A10 using xda Forum
Click to expand...
Click to collapse
I have used it for a day, there is a slight improvement in battery life.
Can you add USB OTG support and double tap to wake
stuck after android logo... using O for LBY ... build number LBY25G
acus123 said:
stuck after android logo... using O for LBY ... build number LBY25G
Click to expand...
Click to collapse
That's odd. Did you flash anything else before or is this pure stock Cherry Mobile One?
Way better than stock kernel. Performance has improved and battery drains slowly(Compared to stock kernel). I would prefer this kernel over stock anytime!
Regards.
PS: I would request the developer to make a flashable ZIP next time or can provide as an additional package because it's a bit inconvenient to open up PC and flash via ADB. Anyway, a great work!
I've tested the kernel extensively over few days and I can confirm battery improvements
This is a collection of add-on modules for the stock November 2016 boot image kernel, as found in the latest versions of the CM 12.1 and Fire Nexus roms by @ggow. This started as a personal project to see if I could compile a working kernel module for the PegasusQ CPU governor.
There are now ROM-specific packages depending on whether you are using CM 12.1 or Fire Nexus. So before downloading, check which ROM version and build date you are using to make sure you grab the right package.
Package for ROMs Based on 5.3.2.0 Boot Image
If you are using any of the following CM 12.1 builds:
-2016-11-21
-2016-11-22
OR any of the following Fire Nexus builds:
-24 November 2016
-02 February 2017
Then you need the package for 5.3.2.0 boot image. <--(Link updated as of 6 Feb 2017)
Package for ROMs Based on 5.1.4 Boot Image
If you are using any of the following CM 12.1 builds:
-2016-06-14
-2016-07-10
-2016-08-10
-2016-09-22
-2016-10-21
OR any of the following Fire Nexus builds:
-15 June 2016
-28 July 2016
-12 August 2016
-08 February 2017 (or later)
OR any build of Lineage-12.1
Then you need the package for 5.1.4 boot image. <--(Link updated as of 12 Feb 2017)
Instructions:
Download the correct package for your ROM
Flash in TWRP or FlashFire. (Can be "dirty" flashed; no need to wipe anything)
Use Kernel Adiutor or your favorite kernel tuner to set your desired parameters.
Notes:
If something goes wrong, or if you flash the wrong package and end up with a bootloop, flash this REMOVER zip to disable the script that loads the modules. The REMOVER zip should work on any ROM. I recommend downloading it and copying it to your SD card at the same time you flash the main package so that it's already on the device in the event you need to use it.
The hotplug drivers may need some experimentation to get right. Alucard seems to work pretty well out of the box, but is pretty aggressive. It may cause a lot of lag on games. Thunderplug may have an issue. In my brief test, it seemed to peg one of the cores at 100% continually, but YMMV.
If you find a combination of settings that work well for any of these modules, please let me know so I can consider changing the default tunables.
(Side note: I'm not a developer by any stretch and just did this as a self-challenge. If there are any other specific modules such as governors, hotplug drivers, or schedulers you'd like me to try, let me know. No promises, but we'll see what happens!)
Credits:
ByungChang Cha (for the PegasusQ governor)
@osm0sis (for the AnyKernel2 installer)
Change log
12 February 2017
-Built and started maintaining separate packages, one for Fire Nexus 2/8/17 build and newer, and the other for last CM 12.1 and Fire Nexus pre-2/8/17.
06 February 2017
-Added a bunch of TCP congestion control algorithms (Highspeed, Illinois, Vegas, Yeah, HTCP, LP, Veno, Hybla, Scalable, Westwood)
04 February 2017
-Added Smartmax CPU governor
-Added ThunderX CPU governor
-Added Alucard hotplug driver
-Added Thunderplug hotplug driver
-Added BFQ I/O scheduler
-Added TripNDroid I/O scheduler
-Added ZEN I/O scheduler
02 February 2017
Initial release
Awesome! How's performance and battery comparing to stock?
I wonder if you could make cpu or gpu OC. Or some gpu governor with better perf.
tonibm19 said:
Awesome! How's performance and battery comparing to stock?
Click to expand...
Click to collapse
I'm not sure. It's been a while since I used the Fire on a regular basis (my kids are the main users these days). But with PegasusQ, I noticed ~2% battery drain overnight (8 hours), and it seemed to me to be below average drain when in use with no noticeable performance penalty. Granted, I haven't tested it thoroughly, so I'm interested in comments from others.
tonibm19 said:
I wonder if you could make cpu or gpu OC. Or some gpu governor with better perf.
Click to expand...
Click to collapse
Unfortunately, I don't think overclocking is going to be possible with the locked bootloader. CPU/GPU overclocking requires modifying the kernel drivers and recompiling the kernel, but we can't boot custom kernels with the bootloader locked. Alternative GPU governors might be possible. I don't have the Fire in front of me right now, but is there a GPU tab in Kernel Adiutor?
@theophile2 - Works wonderfully on the Fire Nexus ROM and sticks even after reboot provided using a Kernel Manager. I now have renewed hype for this tablet, lol. This was hugely needed to enhance performance. I see you are planning on adding more governors down the line and I'm looking forward to it! Huge thanks for this advancement!
theophile2 said:
You can download a flashable ZIP here
Click to expand...
Click to collapse
Is there any way to put this into an existing installation w/o re-flashing the rom, i.e. either simply copy it or use FlashFire with just this zip (which exact settings in FlashFire)?
Sorry for this noob question, but I don't want to go through a whole recovery procedure if I get it wrong...
Marsu42 said:
Is there any way to put this into an existing installation w/o re-flashing the rom, i.e. either simply copy it or use FlashFire with just this zip (which exact settings in FlashFire)?
Sorry for this noob question, but I don't want to go through a whole recovery procedure if I get it wrong...
Click to expand...
Click to collapse
1. Select Flash Zip in FlashFire.
2. Select the Zip and flash it.
3. Look for any kernel manager in the Play Store.
4. Change your CPU Governor and set it to boot so it sticks after a device restart.
theophile2 said:
Alternative GPU governors might be possible. I don't have the Fire in front of me right now, but is there a GPU tab in Kernel Adiutor?
Click to expand...
Click to collapse
No, there isn't.
tonibm19 said:
theophile2 said:
I don't have the Fire in front of me right now, but is there a GPU tab in Kernel Adiutor?
Click to expand...
Click to collapse
No, there isn't.
Click to expand...
Click to collapse
There's one in EX Kernel Manager though, but it says "not supported" :-\
nirogu325 said:
1. Select Flash Zip in FlashFire.
2. Select the Zip and flash it.
3. Look for any kernel manager in the Play Store.
4. Change your CPU Governor and set it to boot so it sticks after a device restart.
Click to expand...
Click to collapse
Thanks, after some trial & error I'm now using "No Frills CPU Control" to set it on boot.
Added a bunch more modules and updated the OP with new link. Let me know how it works for you!
theophile2 said:
Added a bunch more modules and updated the OP with new link. Let me know how it works for you!
Click to expand...
Click to collapse
I suggest adding an update date in the thread's title as a heads up to users.
theophile2 said:
-Added BFQ I/O scheduler
Click to expand...
Click to collapse
I have admit when first reading about these replacement modules, it sounded rather nerdy to me, but I'm amazed how much more responsive the device is with pegasusq and bfq.
http://www.alliance-rom.com/wiki/governors-explained/
http://algo.ing.unimo.it/people/paolo/disk_sched/
Let's hope someone takes a week off, tries all possible combinations of these modules and reports back on stability and performance :->
Marsu42 said:
http://www.alliance-rom.com/wiki/governors-explained/
http://algo.ing.unimo.it/people/paolo/disk_sched/
Click to expand...
Click to collapse
Here's another reference link for those interested. This one's very detailed when it comes to schedulers advantages, disadvantages and many other things such as read-ahead: LINK
nirogu325 said:
Here's another reference link for those interested. This one's very detailed when it comes to schedulers advantages, disadvantages and many other things such as read-ahead: LINK
Click to expand...
Click to collapse
Based on that, could we have the ROW scheduler, pretty please with sugar on it :-> ? " It is a good all-round scheduler despite being biased to read operations. Your device may feel more responsive after selecting ROW because it was designed for mobile devices. Older devices may see more of a boost in performance compared to newer devices."
Btw; ZEN hangs my "No Frills CPU Control" app when trying to set it, while the others work fine.
Marsu42 said:
Btw; ZEN hangs my "No Frills CPU Control" app when trying to set it, while the others work fine.
Click to expand...
Click to collapse
ZEN is also force closing EX Kernel Manager here. Something's funny going on with ZEN.
Marsu42 said:
Based on that, could we have the ROW scheduler, pretty please with sugar on it :-> ? " It is a good all-round scheduler despite being biased to read operations. Your device may feel more responsive after selecting ROW because it was designed for mobile devices. Older devices may see more of a boost in performance compared to newer devices."
Click to expand...
Click to collapse
I looked at ROW, but most implementation I've seen require patching the kernel, which we can't do (locked bootloader). I'll keep my eyes out to see if there's an implementation that doesn't require this.
Marsu42 said:
Btw; ZEN hangs my "No Frills CPU Control" app when trying to set it, while the others work fine.
Click to expand...
Click to collapse
Zen works for me with Kernel Adiutor.
In other news, I just upped a new version that adds a new thing to get nerdy about: TCP congestion control algorithms. I've built modules for all the ones in the stock kernel that Amazon stripped out (Highspeed, Illinois, Vegas, Yeah, HTCP, LP, Veno, Hybla, Scalable, and Westwood).
In a nutshell, if you want max download/upload speed with no noticeable latency penalty, switch to Westwood.
BTW, Google submitted a kernel patch a couple of months ago to add a new algorithm they developed. I plan to check that out and see if it will compile against this relatively old kernel (3.10).
BTW, the new version of Fire Nexus uses boot.img from Fire Is 5.1.4, so I don't think this is compatible anymore. Is it?
EDIT: No, it is not. Bootloops.
PorygonZRocks said:
BTW, the new version of Fire Nexus uses boot.img from Fire Is 5.1.4, so I don't think this is compatible anymore. Is it?
EDIT: No, it is not. Bootloops.
Click to expand...
Click to collapse
Yeah I just tested it earlier and had no idea what was wrong :/ that explains it.
PorygonZRocks said:
BTW, the new version of Fire Nexus uses boot.img from Fire Is 5.1.4, so I don't think this is compatible anymore. Is it?
EDIT: No, it is not. Bootloops.
Click to expand...
Click to collapse
Yeah I just tested it earlier and had no idea what was wrong :/ that explains it.
PorygonZRocks said:
BTW, the new version of Fire Nexus uses boot.img from Fire Is 5.1.4, so I don't think this is compatible anymore. Is it?
EDIT: No, it is not. Bootloops.
Click to expand...
Click to collapse
That's odd. Nothing in the zip should be capable of causing a bootloop, even on an incompatible kernel. At worst, it should just "not work."