[EOL][KERNEL][UNOFFICIAL BUILDS] Boeffla Kernel Linaro/Uber - OnePlus 2 Android Development

hi Guys,
as some of u maybe know from the Samsung Galaxy S3 or OPO area i'm doing a "build-service" for non official boeffla kernel builds and as we recently also got a boeffla kernel
for the One Plus Two device (kudos to @Lord Boeffla!) i want to share with u my self made Linaro/Uber builds for that device in addition.
i'm gonna reduce redundancy and keep it shorter this time as about how this started and my primary intention can also be taken from the corresponding Samsung Thread
for people who asks themself: Linaro, Sabermod, Uber what? here some good info about it: https://docs.google.com/document/d/1C-ehLWl6XcStOmB30QHDA_DOdceXiGIyzXT_0eIg5nQ/edit (thx to @ViditM14 for providing the link!) and finally more infos about Uber Toolchains : https://plus.google.com/+ChetKener/posts/YzMJEkzPQgp and here: https://plus.google.com/communities...3/stream/ac70dec1-dad7-438d-baeb-f8d6644217fd
so without further ado let's go:
First of all the obligatorily Disclaimer:
As also written in the title please note these builds are UNOFFICIAL, are NOT SUPPORTED in any way by Lord Boeffla or myself and might be EVEN UNSTABLE! So take them as they are! As always flash them at your own risk and make a backup before flashing! (yeah take this advice seriously!)
About bugs: Before you report ANY issues with the linaro/uber builds provided here (doesn't matter which one!) FIRST TRY the non-linaro/uber official builds from HERE to see if they will be gone then. if they wont, you can go on and report your problems in the official boeffla kernel thread! I hope you understand that we have to treat and keep these builds here completely separate from official ones as they have in no terms something to do with each other! Not respecting this will force me to stop building further linaro/uber builds of boeffla kernel.
About benchmarks and comparisons between toolchains:
It's common known that linaro (maybe also uber?) builds might give us higher benchmark rates and that seems great for some people (in fact it's pointless per se in my opinion)
so please if you really must, post them ONLY here and NOT in official boeffla kernel thread, thanks!
Now some more precise informations about what's going on here:
what i did:
the images are always build with original sources from official boeffla kernel OPO repositories from HERE
with some not worth to mention minor changes to be able to build it on my build environment with non stock toolchains.
all images are compiled from special branches from this forked Boeffla Kernel repository
with a self compiled Linaro Toolchain 4.9.1-2014.07-1 (source: https://github.com/zanezam/ct-ng_linaro) + recent version of Uber Toolchain 4.9.4 (Credits to Team Uber for the pre-configured/-build toolchains)
all images are build with changes from different branches in following repository:
https://github.com/zanezam/boeffla-kernel-oos-oneplus2
Beside of some additional fixes from my side all changes are taken from repositories of @ak
so all credits to him, and thx again for the starting point!
before someone asks some last words about the used toolchain versions: i did a lot of testing before releasing these builds here
and the used Linaro / Uber versions are the maximum versions which can be used to make working builds with pure boeffla
kernel sources and without changing a lot of code in addition. So if u are able to biuld a kernel and still want to try higher versions i must state here that Linaro versions
above 4.9.1 and Uber verisions above 4.9.4 might produce a "messed up" image which at the end gives you a boot-looping or not booting device and that might even be dangerous, so be aware !!
if someone has a clue what exactly has to be done to use higher versions of the corresponding toolchains (with respecting the original kernel source of course) feel free to let us know,
it will be definitely appreciated!
what i will do:
build the source code with linaro/sabermod toolchain and (like Lord Boeffla usually does) provide a CWM image of recent boeffla kernel versions.
do a test for about 1 day with this builds and if they work without any big issues, add them here in the thread.
i will try to keep the linaro/uber toolchains as up-to-date as possible till the need of bigger code change will be reached.
not providing versions that are not released by Lord Boeffla yet.
not providing an image if it is not working - well of course not *g* but it will be marked as "canceled" then for info.
not change the source code to add/remove features or fix boeffla kernel related bugs.
not support the whole stuff here.
what i will maybe do (sooner or later):
provide ZZMoove Governor test builds if there are any new versions to test - more infos and discussions about ZZMoove Governor can be found HERE
maybe tune the build flags if some more linaro/sabermod/uber experienced dev comes up with "better" ones (feel free to post and let me know, toolchain specialists! *g*)
Downloads:
One Plus Two Oxygen OS 2.x.x
(*l491* linaro / *u494* uber)
One Plus Two Oxygen OS 3.x.x
(*l491* linaro / *u494* uber)
One Plus Two CM13.0
(*l491* linaro / *u494* uber)
One Plus Two CM14.1 / LineageOS 14.1
(*l491* linaro / *u494* uber)
Mirror on Androidfilehost for all devices (only latest kernel versions)

reserved

reserved too

Nice! Flashing now! Welcome
Sent from my ONE A2005 using Tapatalk 2
---------- Post added at 05:40 PM ---------- Previous post was at 05:15 PM ----------
@ZaneZam do you own our device or are you just optimizing the Lord's builds?
Sent from my ONE A2005 using Tapatalk 2

jmtjr278 said:
Nice! Flashing now! Welcome
Sent from my ONE A2005 using Tapatalk 2
---------- Post added at 05:40 PM ---------- Previous post was at 05:15 PM ----------
@ZaneZam do you own our device or are you just optimizing the Lord's builds?
Sent from my ONE A2005 using Tapatalk 2
Click to expand...
Click to collapse
yeah i got one lying in front of me (but not as a daily driver yet) so yes i'm also running these builds
i'm doing this only for devices i own, otherwise it wouldn't be possible to provide anything decent
btw guys don't be confused about the "COS" naming in the images that's just a typo and will be gone in next version, sry

If you don't mind me asking, what are you using as your dd? Opo still?
Sent from my ONE A2005 using Tapatalk 2

jmtjr278 said:
If you don't mind me asking, what are you using as your dd? Opo still?
Sent from my ONE A2005 using Tapatalk 2
Click to expand...
Click to collapse
yes

Man im so happy to have you here!
---------- Post added at 06:36 PM ---------- Previous post was at 06:35 PM ----------
ZaneZam said:
yes
Click to expand...
Click to collapse
Lol me too until I have a good combo rom with your kernel

So glad to see you joining this party ZZ!

So glad to see more famous developers are coming forward to provide support. Please bring regular updates.

nirmalkurienmathews said:
So glad to see more famous developers are coming forward to provide support. Please bring regular updates.
Click to expand...
Click to collapse
will definitely do, even though for the used toolchain part it's harder than with other devices but time will tell

Love your work, will be flashing soon
Cheers !!

Whats the difference between U494 & 1491 ?
Just wanted to be sure before i flash, thanks !!

New Builds!
Funk Wizard said:
Whats the difference between U494 & 1491 ?
Just wanted to be sure before i flash, thanks !!
Click to expand...
Click to collapse
u494 = Build with Uber toolchain (gcc v4.9.4), l491 = Build with Linaro toolchain (gcc v4.9.1 ) apart from that optimization flags are the same atm.
u can flash any of these on top of offical builds or vice versa settings of boeffla app are preserved. which one is better or IF there are big differences isn't known yet
but let us know if u face any pros or cons with these builds here, thx !
and btw:
builds of...
Boeffla-kernel-1.0-beta2-OOS2xx-OnePlus2
uploaded!
Enjoy!
ZZ

Under Testing..
Thanks a lot @ZaneZam, You finally arrived officially

ZaneZam said:
u494 = Build with Uber toolchain (gcc v4.9.4), l491 = Build with Linaro toolchain (gcc v4.9.1 ) apart from that optimization flags are the same atm.
u can flash any of these on top of offical builds or vice versa settings of boeffla app are preserved. which one is better or IF there are big differences isn't known yet
but let us know if u face any pros or cons with these builds here, thx !
and btw:
builds of...
Boeffla-kernel-1.0-beta2-OOS2xx-OnePlus2
uploaded!
Enjoy!
ZZ
Click to expand...
Click to collapse
Thanks Zam for your explanation, running the beta2 for few hours now and it looks promising.
Cheers !!

Thanks! The really good kernel!

Thanks for your work.
I have one question for you...
Are you abel to build official kernel (https://github.com/OnePlusOSS/android_kernel_oneplus_msm8994) with uber/linaro toolchain?
I have a lot of error when I try to build official kernel with uber toolchain
Thanks,
Flavio

Didn't try but as boeffla kernel uses this as base I can say : Only with v4.9.4 from uber and a self made Linaro 4.9.1. with uber 5.x or 6.x there are errors which I was able to fix (except one ice on latest 6.x but that's a bug in gcc which will be fixed in next toolchain version hopefully) but however the 5.x and 6.x images are not booting at the moment. this needs some special attention or some special knowledge which I don't have atm
Gesendet von meinem ONE A2003 mit Tapatalk

sorry for the stupid question, but what is the difference between this kernel and official boeffla kernel??

Related

[KERNEL][CM11][Linaro] Unofficial SlimKat Kernel [20140413]

UNOFFICIAL SlimKat Kernel for Xperia Z Ultra​
This is a port for the Xperia Z Ultra of the SlimKat Kernel, from their original Xperia Z1 sources at GitHub. No features have been added or removed, I've just made the necessary changes for it to run on the Xperia Z Ultra. This is ONLY for CM11-based firmwares (I tested only with Carbon Rom 4.4.2).
This is not my original work! I've just ported and compiled it for the Z Ultra, so please also thank the original creators (see "Credits" below)! Also, avoid reaching them directly for any issues you may find in this build, since it's UNOFFICIAL and they may not be able to provide support. Post here in this thread instead.
Features:
TCP Congestion Algorithms: westwood, reno, bic, cubic, htcp, vegas
I/O Schedulers: noop, deadline, row, cfq, sio, fiops, bfq
Faux Sound
Compiled using Linaro GCC 4.8.2 with optimizations (-O2, -mcpu, -mtune etc.)
And all the standard CM11 kernel features
Credits:
@prbassplayer - original work for the Xperia Z1 (here), and for letting me port it to the Xperia ZU
SlimRoms Team - for their work on SlimKat ROM and Kernel (here)
@Androguide.fr - for helping me on my first attempt to build a CM-based kernel (while trying to port his Pimped Kernel for Z1; still on my list!), and I also borrowed his updater-script
Download:
Version 20140413 - XDA
Version 20140407 - XDA
Version 20140328 - Mega or XDA
Changelog:
Latest commits on GitHub.
Starting on 20140413:
Removed debug symbols from kernel.
Compiled with SaberMod toolchain 4.8.3.
Added camera patches from faux123, hopefully they will solve or minimize the camera freeze issue.
Notes:
Always make a backup of your /system directory, in case you want to return to your previous kernel (flash it first, then restore the backup)
XDA:DevDB Information
SlimKat Kernel for Xperia Z Ultra, a Kernel for the Sony Xperia Z Ultra
Contributors
dbolivar, prbassplayer, SlimRoms Team
Kernel Special Features: Additional TCP Congestion Algorithms, I/O Schedulers, Faux Sound, Linaro Optimizations
Version Information
Status: Beta
Current Beta Version: 20140413
Beta Release Date: 2014-03-28
Created 2014-03-28
Last Updated 2014-04-13
Have you tried it with my build of Carbon? I have run slimkat's kernel on my carbon several times without issue.
If this is fully working i'll link to it from my build thread.
I've also been looking into building carbon with the above slim/saber tweaks
Sent from my Xperia Z Ultra using Tapatalk
blueether said:
Have you tried it with my build of Carbon? I have run slimkat's kernel on my carbon several times without issue.
If this is fully working i'll link to it from my build thread.
I've also been looking into building carbon with the above slim/saber tweaks
Click to expand...
Click to collapse
Running it exactly with your Carbon build, my friend. Working like a charm.
Regarding the tweaks, are you talking about the Linaro optimizations? If yes, you can just "trick" the CM build system by copying the Linaro toolchain over the default toolchain CM is using (or symlink the dir). I did that for the kernel and it worked normally, but of course had to use the tweaked Makefile with the optimizations and adjustments of the warning flags. These optimizations I think are enough:
Code:
-munaligned-access -fgcse-lm -fgcse-sm -fsched-spec-load -fforce-addr -ffast-math -fsingle-precision-constant -mcpu=cortex-a15 -mtune=cortex-a15 -marm -mfpu=neon -ftree-vectorize -mvectorize-with-neon-quad -funroll-loops
But I don't know how to adjust the CM Makefiles except for the kernel. Do you know how to do that? I'm in the process of learning how to build a ROM, and would love to know these tricks beyond the standard ". build/envsetup.sh; breakfast ...; etc.".
Thanks for this @dbolivar
Sent from my Xperia Z Ultra using Tapatalk
Sweet! Thanks!
Sent from my C6833 using Tapatalk
Thanks dude
thanks dbolivar. Can you include TWRP recovery with this..that would be a nice addition-maybe not dual boot if too much of a task but another one with the TWRP recovery, if you can.
Just had a sod. Anyone else experienced this?
Sent from my Xperia Z Ultra using Tapatalk
---------- Post added at 10:30 AM ---------- Previous post was at 09:59 AM ----------
I think I had the sod because of me changing governor to ondemand. I'll keep it on interactive and I'll report back.
Sent from my Xperia Z Ultra using Tapatalk
pemell said:
Just had a sod. Anyone else experienced this?
Click to expand...
Click to collapse
It is very possible you experimented a SoD with this kernel, since the recent fixes the CM team implemented have not yet been merged in SlimKat's kernel. As soon as they do that, I'll create a new build here.
can you add F2FS support ?
Because F2FS clearly provides better performance than ext4.
MEGAX91 said:
can you add F2FS support ?
Because F2FS clearly provides better performance than ext4.
Click to expand...
Click to collapse
This would be very useful!
Sent with my Xiaomi MI2 with Tapatalk Pro
MEGAX91 said:
can you add F2FS support ?
Because F2FS clearly provides better performance than ext4.
Click to expand...
Click to collapse
Sorry guys, but I don't plan to add / change / remove any features to this kernel, because then it won't be SlimKat's Kernel anymore. However, I may in the future port other kernels with F2FS, or build my own.
dbolivar said:
Sorry guys, but I don't plan to add / change / remove any features to this kernel, because then it won't be SlimKat's Kernel anymore. However, I may in the future port other kernels with F2FS, or build my own.
Click to expand...
Click to collapse
thanks man
i think Pimped Kernel or Doom Kernel would be best options.
MEGAX91 said:
thanks man
i think Pimped Kernel or Domm Kernle would be best options.
Click to expand...
Click to collapse
Yes, in fact I've been trying to port Pimped Kernel for a few days, but it always bootloops on the ZU. I need more time to investigate. DoomKernel I plan to work when (if) I return to stock someday, since currently I'm using CM11-based firmwares, but stay tuned...
the kernel does not want to boot on the latest cm-11-20140404-NIGHTLY-togari.zip
The SONY boot logo shows up and stays a long time, purple light comes on and off. Then it moves on to a blank black nothing..
Kernel worked fine on cm-11-20140330-NIGHTLY-togari.zip ...darn now it wont boot at all Fuuuuu!!!
Oh I see whats going on: http://www.cmxlog.com/11/togari/ every old nightly changelog has been removed before mars 31, went back to cm-11-20140330-NIGHTLY-togari.zip as my phone didn't boot at all with the new nightly.
I will wipe the phone clean tomorrow and try again, can't mess with my phone now as I'm leaving early in the morning
New version 20140407
New version 20140407 released. Changelog in the OP. Enjoy.
Can anyone confirm if camera is working as it should?
pemell said:
Can anyone confirm if camera is working as it should?
Click to expand...
Click to collapse
I think the camera issue is ROM-related, not kernel (but not 100% sure). Anyway, I'm still getting the initial freeze when opening the camera. My workaround for it is: immediately after boot, open the camera. It should open normally after a short initial freeze (just wait). After that, it continues to work until next reboot, when you can just redo these steps. I noticed that if I don't open the camera immediately after boot, the chances for a "permanent" freeze with subsequent "can't connect to camera" message (solvable only by rebooting) are higher.
The kernel isn´t working with CM11 for me. The process com.androidphone has stopped.
Solutions?
Flashed 0407 and got stuck on Sony logo. I'm on carbon 0329
Sent using C6833 - Carbon KitKat

[EOL][KERNEL][UNOFFICIAL BUILDS] Boeffla Kernel Linaro/Uber

hi Guys,
as some of u maybe know from the Samsung Galaxy S3 area i'm doing a "build-service" for non official boeffla kernel builds and as we recently also got a boeffla kernel for the One Plus One device (kudos to @Lord Boeffla!) i want to share with u my self made Linaro (and here also Uber!) builds for that device in addition.
i'm gonna reduce redundancy and keep it shorter this time as about how this started and my primary intention can also be taken from the corresponding Samsung Thread
for people who asks themself: Linaro, Sabermod, Uber what? here some good info about it: https://docs.google.com/document/d/1C-ehLWl6XcStOmB30QHDA_DOdceXiGIyzXT_0eIg5nQ/edit (thx to @ViditM14 for providing the link!) and finally more infos about Uber Toolchains : https://plus.google.com/+ChetKener/posts/YzMJEkzPQgp and here: https://plus.google.com/communities...3/stream/ac70dec1-dad7-438d-baeb-f8d6644217fd
so without further ado let's go:
First of all the obligatorily Disclaimer:
As also written in the title please note these builds are UNOFFICIAL, are NOT SUPPORTED in any way by Lord Boeffla or myself and might be EVEN UNSTABLE! So take them as they are! As always flash them at your own risk and make a backup before flashing! (yeah take this advice seriously!)
About bugs: Before you report ANY issues with the linaro/uber builds provided here (doesn't matter which one!) FIRST TRY the non-linaro/uber official builds from HERE to see if they will be gone then. if they wont, you can go on and report your problems in the official boeffla kernel thread! I hope you understand that we have to treat and keep these builds here completely separate from official ones as they have in no terms something to do with each other! Not respecting this will force me to stop building further linaro/uber builds of boeffla kernel.
About benchmarks and comparisons between toolchains: It's common known that linaro (maybe also uber?) builds might give us higher benchmark rates and that seems great for some people (in fact it's pointless per se in my opinion ) so please if you really must, post them ONLY here and NOT in official boeffla kernel thread, thanks!
Now some more precise informations about what's going on here:
what i did:
the images are always build with original sources from official boeffla kernel OPO repositories from HERE
with some not worth to mention minor changes to be able to build it on my build environment with non stock toolchains.
all images are compiled from special branches from this forked Boeffla Kernel repository
with Toolchain Linaro 4.8.4-2014.11 + Toolchain Linaro 4.9.3-2015.03 - Credits to @Christopher83 for this pre-configured toolchains and Toolchain Sabermod 4.8.4 + Toolchain Sabermod (Uber) 4.9.3 - Credits to RobbieL811 for this preconfigured toolchains and thx to @ak for pointing me to it! Since 27.03.15 there are also images compiled with Toolchain Uber 4.9.3 20150501 + Toolchain Uber 5.1.1 20150501 + 6.0.0 20150501 (experimental) Credits and Thx to Uber Team!
all images are build with changes from following repos
for Boeffla Kernel CM13.0/CM12.1/CM12/CM11/CM11s/CM12s/COS12.1 Linaro/Uber :
https://github.com/zanezam/boeffla-kernel-cm-bacon
for Boeffla Kernel Oxygen OS 1.0.x Linaro/Uber :
https://github.com/zanezam/boeffla-kernel-oos-bacon
Beside of some additional fixes from my side all changes are mixed up and taken from repositories of ak
and DerRomtester so all credits to them!
...and also for letting me bother them! thank u guys for bring me "on track"!
before someone asks some last words about the used toolchain versions: i did a lot of testing before releasing these builds here
and the used Linaro / Uber versions are the maximum versions which can be used to make working builds with pure boeffla
kernel sources and without changing a lot of code in addition. So if u still want to try higher versions i must state here that Linaro versions
above 4.8 might produce a "messed up" image (without optimized flags and without warnings/errors etc. during build!)
which at the end gives you a boot-looping device and that might even be dangerous, so be aware !! if someone has a clue what exactly has to be
done to use higher versions of the corresponding toolchains (with respecting the original kernel source of course) feel free to let us know,
it will be definitely appreciated!
Update 15.03.15: found one reason and i'm able to use some higher versions now!
But with CM11s and CM11 only Uber 4.9.3 and Linaro 4.8.4 are possible!
builds with higher Linaro/Uber toolchain versions still doesn't boot!
what i will do:
build the source code with linaro/uber toolchain and (like Lord Boeffla usually does) provide a CWM image of recent boeffla kernel versions.
do a test for about 1 day with this builds and if they work without any big issues, add them here in the thread.
i will try to keep the linaro/uber toolchain as up-to-date as possible till the need of bigger code change will be reached.
not providing versions that are not released by Lord Boeffla yet.
not providing an image if it is not working - well of course not *g* but it will be marked as "canceled" then for info.
not change the source code to add/remove features or fix boeffla kernel related bugs.
not support the whole stuff here.
what i will maybe do (sooner or later):
provide ZZMoove Governor test builds if there are any new versions to test - more infos and discussions about ZZMoove Governor can be found HERE
maybe tune the build flags if some more linaro/uber experienced dev comes up with "better" ones (feel free to post and let me know, toolchain specialists! *g*)
Downloads:
CM11s (for stock roms!)
One Plus One Bacon CM11s stock builds
(for CM11s XNPH38R/44S/05Q *l484* linaro / *u493* uber)
CM12s (for stock roms!)
One Plus One Bacon CM12s stock builds
(for CM12s YNG1TAS0YL+YNG1TAS17L+YNG1TAS2I3 *l494* linaro / *u494* + *u521* + *u600* uber)
CM12.1s (for stock roms!)
One Plus One Bacon CM12.1s stock builds
(for CM12.1s YOG4PAS1N0 *l494* linaro / *u494* + *u521* + *u600* uber)
COS13.0 (for stock roms!)
One Plus One Bacon COS13.0 stock builds
(for COS13.0 ZNH0EAS2JK *l494* + *l531* linaro / *u494* + *u531* + *u600* + *u700* uber)
COS13.1 (for stock roms!)
One Plus One Bacon COS13.1 stock builds
(for COS13.1 ZNH2KAS1KN *l494* + *l531* linaro / *u494* + *u531* + *u600* + *u700* uber)
CM11 (for genuine roms!)
One Plus One Bacon CM11 builds
(for CM11 roms only! *l484* linaro / *u493* uber)
CM12 (offical nightlies and based ones)
One Plus One Bacon CM12 builds
(for CM12 roms only! *l493* linaro / *u493* + *u511* + *u600* uber)
CM12.1 (official builds and based ones)
One Plus One Bacon CM12.1 builds
(for CM12.1 roms only! *l494* linaro / *u494* + *u521* + *u600* uber)
Oxygen OS 1.x.x
One Plus One Bacon Oxygen OS 1.x.x builds
(*l494* linaro / *u494* + *u521* + *u600* uber)
Oxygen OS 2.x.x
One Plus One Bacon Oxygen OS 2.xx builds
(*l494* + *l531* linaro / *u494* + *u531* + *u600* uber)
CM13.0 (official builds and based ones) + Nethunter and "Cafcam" special builds
One Plus One Bacon CM13.0 builds
(for CM13.0 roms only! *l494* + *l531* linaro / *u494* + *u531* + *u600* + *u700* uber)
CM14.1 (official builds and based ones) + Nethunter special builds
One Plus One Bacon CM14.1 / LineageOS 14.1 builds
(for CM14.1 roms only! *l494* + *l531* linaro / *u494* + *u531* + *u600* + *u700* uber)
Mirror on Androidfilehost for all devices (only latest kernel versions)
Nethunter Install Packs:
For One Plus One Bacon Marshmallow Roms
finally i wanna throw out big thanks to Lord Boeffla for his great work and for accepting that i provide you these linaro/uber builds here! :highfive:
so now i wish u much fun with these builds and maybe some of u can drop a line about how they work for u
reserved
this one too
Welcome, will test the versions. I tried Ak with linaro. It's ready fast.
Sent from my A0001 using Tapatalk
---------- Post added at 11:40 PM ---------- Previous post was at 11:00 PM ----------
Test now the sabemod version, It's fast. Apps open very quick. Scrolling is Smooth en benchmarks are great 47350 point on antutu. Tomorrow I will test more. Thanks ZaneZam.
Sent from my A0001 using Tapatalk
I'd be interested to see what gains/ if any can be made with another toolchain, but I'm holding out on a CM version..
Sent from my One A0001 using XDA Premium 4 mobile app
yeah that's the question on this device the differences are hard to see but well not every system is the same and maybe "something" works significant better.
i had the impression the builds are a bit more "fluid" then stock and sabermod a bit more "fluid" then linaro but well atm with 2 tired eyes will have to look closer tomorrow
and yes i will add CM11 builds after Lord Boeffla releases im also curious about that CM11s-CM11 differences
ZaneZam said:
yeah that's the question on this device the differences are hard to see but well not every system is the same and maybe "something" works significant better.
i had the impression the builds are a bit more "fluid" then stock and sabermod a bit more "fluid" then linaro but well atm with 2 tired eyes will have to look closer tomorrow
and yes i will add CM11 builds after Lord Boeffla releases im also curious about that CM11s-CM11 differences
Click to expand...
Click to collapse
He has test builds up, I'm running it now.. It IS speed, it IS fluidity.. Its also stable, no worries.. If a new tool chain could make this any better, I'd be such a happy camper.. All in its own time.. Rest up, I'm here to test when you have time to build..
Sent from my One A0001 using XDA Premium 4 mobile app
Setting.Out said:
He has test builds up, I'm running it now.. It IS speed, it IS fluidity.. Its also stable, no worries.. If a new tool chain could make this any better, I'd be such a happy camper.. All in its own time.. Rest up, I'm here to test when you have time to build..
Sent from my One A0001 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Which one are you currently running? Also to anyone out there, what's the main differences between linaro and sabormod? Thanks.
ZaneZam said:
yeah that's the question on this device the differences are hard to see but well not every system is the same and maybe "something" works significant better.
i had the impression the builds are a bit more "fluid" then stock and sabermod a bit more "fluid" then linaro but well atm with 2 tired eyes will have to look closer tomorrow
and yes i will add CM11 builds after Lord Boeffla releases im also curious about that CM11s-CM11 differences
Click to expand...
Click to collapse
I'm sure he would link you to where he has builds already would love to see the difference having ran lord boeffla kernel for a while the cm11 version much alohas
Sent from my One A0001 using Tapatalk
My Phone reboot, after I overclock the Phone. It doesn't matter but Ak kernel is stable at 2.88
Sent from my A0001 using Tapatalk
ZaneZam version that you recommend? Linaro or Sabermod... Sorry my english but I'm using a translator ...
otisman said:
I'm sure he would link you to where he has builds already would love to see the difference having ran lord boeffla kernel for a while the cm11 version much alohas
Sent from my One A0001 using Tapatalk
Click to expand...
Click to collapse
actually I have access to Lord boefflas "other" reposities so I even could make a build but it's not official yet so I won't
mdv53 said:
My Phone reboot, after I overclock the Phone. It doesn't matter but Ak kernel is stable at 2.88
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Ah oc, well I had problems too (on every build also official stock and with pvs value of 5)
They are gone after using +50mv (+25mv is the actual standard) on all oc freq or at least on 2.88. So maybe that helps?
NeGriTa79 said:
ZaneZam version that you recommend? Linaro or Sabermod... Sorry my english but I'm using a translator ...
Click to expand...
Click to collapse
I cannot give any recommendations atm because the builds are too "fresh" had only about 1 day with each of them and also did rebuilds/reboots during that time. So I'm testing like u haven't found "mine" yet.
Any consideration for F2FS compatibility in future ?
Sent from my A0001 using Tapatalk
I'm afraid not from my side as stated in op I will make no changes to the source code except toolchain related ones, so it stays a pure boeffla. If Lord boeffla considers to add it it will also be in these builds here but I think he has already made his point clear about f2fs and not adding it. it's a benefits/problems question I guess.
suaverc118 said:
Which one are you currently running? Also to anyone out there, what's the main differences between linaro and sabormod? Thanks.
Click to expand...
Click to collapse
about the toolchain difference: well honesty i dunno exactly sabermod toolchain was made for the Sabermod AOSP rom and has AOSP related patches included
but i think the biggest difference between the used toolchains HERE is the difference in gcc version per se 4.7 and 4.8 but someone with more experience/knowledge can surely "spend more light" only thing i know for sure is that these versions are working
ZaneZam said:
actually I have access to Lord boefflas "other" reposities so I even could make a build but it's not official yet so I won't
Ah oc, well I had problems too (on every build also official stock and with pvs value of 5)
They are gone after using +50mv (+25mv is the actual standard) on all oc freq or at least on 2.88. So maybe that helps?
Click to expand...
Click to collapse
+25 did the trick. Thanks, sabemod kernel works great.
Sent from my A0001 using Tapatalk
@ZaneZam
finally your thread is born .... i'm here for eventually help ...
thanks a lot for your hard work. :good:
I have to thank, mate! Because of your work/help I was able to start this and thx good to know that u have an eye on
Very good kernel. With my personal config and ZZMoove governor OPO is very smooth with good battery performance.
Regards !

[KERNEL][UBERTC 4.9.3][Lollipop 5.1] Black Moon [01/04/15]

Hi guys,
I want to present you freshly cooked fork of Code_Blue kernel compiled with UBERTC 4.9.3 and flags from Uber Kernel
Download:
REMOVED
Changelog:
31032015
Build with latest myself compiled UBERTC
31032015
Merged flags from Code_Blue
Merged lastest commits
30032015
Initial release
Credits:
eng.stk for kernel and flashable zip
Cl3Kener for toolchain and kernel flags
me for free time
If you want to support student and his work:
​
XDA:DevDB Information
[KERNEL][UBERTC 4.9.3][Lollipop 5.1] Black Moon, Kernel for the Google Nexus 5
Contributors
mastero9017
Source Code: https://github.com/mastero9017/Black_Moon
Kernel Special Features:
Version Information
Status: Stable
Created 2015-04-01
Last Updated 2015-04-02
nyyc !!
based on 919r code blue? can i flash your kernel on my code blue kernel? any changelogs or features?
Eltorito94 said:
based on 919r code blue? can i flash your kernel on my code blue kernel? any changelogs or features?
Click to expand...
Click to collapse
It's newer than what you get in r919, changelog is on eng.stk github as always. Main feature is toolchain and flags i used. You can flash over normal Code_blue.
Nice, will try it soon Piąteczka
Nice! I've been looking for this. Trying this on @bokbokan euphoria build :good:
Works like charme on latest Optistock with data + cache on f2fs
Madsunable said:
Works like charme on latest Optistock with data + cache on f2fs
Click to expand...
Click to collapse
+1 using this kernel with rastatop.
Working well with euphoria latest..
Hi Mastero
this kernel sounds good
i'm on cataclysm 5.1 with latest uber kernel 03/20
please can you add more information?
Faux sound etc.
is this kernel synapse and UKM compatible?
or has it the .cfg file like uber kernel (flash and forgett)?
thanks in advance
cheers
@danmaman
It's newer than what you get in r919, changelog is on eng.stk github as always. Main feature is toolchain and flags i used. You can flash over normal Code_blue.
Click to expand...
Click to collapse
MotoFlasher said:
@danmaman
View attachment 3237787
View attachment 3237788
Click to expand...
Click to collapse
Dankeschön:good:
Is this any better than the original code blue in terms of battery/performance?
Tanged said:
Is this any better than the original code blue in terms of battery/performance?
Click to expand...
Click to collapse
just as good...if not better
i'm testing since in the morning
liquid smooth.....and battery friendly with stock settings
i like the mix between/with... ubertc and code_blue
thanks mastero and all other kernel Dev's:good:
Hi guys!
New build is online. I took more flags from original code_blue and merged 3 commits from today.
Tomorrow i will post version with myself compiled UBERTC, because Cl3Kener made some new changes to it.
And we want the best of the best, don't we?
Enjoy!
Thanks for 650 downloads in 24h! :good:
danmaman said:
Hi Mastero
this kernel sounds good
i'm on cataclysm 5.1 with latest uber kernel 03/20
please can you add more information?
Faux sound etc.
is this kernel synapse and UKM compatible?
or has it the .cfg file like uber kernel (flash and forgett)?
thanks in advance
cheers
Click to expand...
Click to collapse
For now, it's only custom build of Code_Blue for better optimization, no additional changes.
Tanged said:
Is this any better than the original code blue in terms of battery/performance?
Click to expand...
Click to collapse
Main reason why i post this. For me those builds feel at least smoother.
danmaman said:
just as good...if not better
i'm testing since in the morning
liquid smooth.....and battery friendly with stock settings
i like the mix between/with... ubertc and code_blue
thanks mastero and all other kernel Dev's:good:
Click to expand...
Click to collapse
Be sure to try new build
Do you use the latest UBERTC 4.9.3?
Assa551N said:
Do you use the latest UBERTC 4.9.3?
Click to expand...
Click to collapse
I use latest compiled precompiled from 23/03. Tomorrow i will compile it from sources to merge latest changes.
Awesome... My 2 favorite kernels lol how ironic. I'm anxious to see the thing progress
Kroniq said:
Awesome... My 2 favorite kernels lol how ironic. I'm anxious to see the thing progress
Click to expand...
Click to collapse
It's more like toolchain rather than the uber kernel but whatever liking this toolchain/kernel combo.
Hi guys again
I just got message from eng.stk and he doesn't want to use Code_Blue name outside his thread, but i am going to keep this kernel/toolchain combo.
I will change name tomorrow, you can propose them in this thread. Thanks in advance

[Kernel][CM/CAF][OC/UC] BlueBerry Kernel [OP2][v1.4]

[FONT="Open Sans, Roboto, sans-serif"]
BlueBerry Kernel for OnePlus 2
Based on benschhold's custom kernel
Disclaimer
Code:
YOU are doing this modifications to your device.
YOU take the full responsibility for whatever you do with your device.
I am NOT responsible, nor will I provide any support if your device gets any damage by this software, your boss fired you because you missed an alarm or it caused a thermonuclear war.
By downloading and/or installing this software ("kernel") you agree that you are fully responsible for your actions.
Thanks!
Features
Basically everything you get from benschhold's kernel, plus:
Tweaks in Virtual Memory (Swappiness, VFS Cache Pressure, and more)
-> Better performance without side effects on OnePlus 2!
Default I/O Scheduler: sioplus
Default TCP Congestion Algorithm: htcp
Latest Kernel Adiutor by @Grarak (Everything should work fine, including Sound settings)
Super compatible with halogenOS
QuadRooter security patches
Other security patches
This kernel is provided as a flashable ZIP file. The kernel is installed using AnyKernel, which gives better compatibility on various ROMs!
Prerequisites
OOS3 firmware
Android Marshmallow ROM (CAF/CM13)
An already working kernel installed on your device
FAQ
Does this work on ROM x?
Try it yourself, please!
Download
Download from AndroidFileHost
Credits
This kernel is based on benschhold's custom kernel.
Credits go like following:
benschhold
Grarak
Altaf Mahdi
regalstreak
If you feel that you are left out here, please contact me!
Sources
Kernel source
AnyKernel source
[/FONT]
XDA:DevDB Information
BlueBerry Kernel (OP2), Kernel for the OnePlus 2
Contributors
xdvs23, This kernel is based on benschhold's
Source Code: https://github.com/xdevs23/android_kernel_oneplus_msm8994
Kernel Special Features: Overclock, Underclock, Tweaks, everything else you also get from benschhold's kernel
Version Information
Status: Stable
Current Stable Version: 1.3
Stable Release Date: 2016-08-16
Created 2016-07-26
Last Updated 2016-08-21
Reserved
Reserved
Extra reserved
Reserved
"Super compatible with halogenOS"
Love this <3
Great work!
regalstreak said:
"Super compatible with halogenOS"
Love this <3
Great work!
Click to expand...
Click to collapse
Thanks bro
Excited to try this out.
New Version is up - 26th July 2016 - v1.1 (bh 3.6)
Changelog
Update Linux Kernel version to 3.10.84
Set sioplus as default I/O Scheduler
Set htcp as default TCP Congestion Algorithm
Ship new Kernel Adiutor Beta by @Grarak
Download here
works pretty well with tipsy.thxs
Sent from my ONE A2003 using XDA-Developers mobile app
xdvs23 said:
New Version is up - 26th July 2016 - v1.1 (bh 3.6)
Changelog
Update Linux Kernel version to 3.10.84
Set sioplus as default I/O Scheduler
Set htcp as default TCP Congestion Algorithm
Ship new Kernel Adiutor Beta by @Grarak
Download here
Click to expand...
Click to collapse
charge control?
Sent from my oneplus2 using Tapatalk
Nik_ said:
charge control?
Click to expand...
Click to collapse
What exactly do you want to know?
This kernel supports charging with up to 2000 mA, which is Qualcomm QuickCharge.
Hope that answers your question.
xdvs23 said:
What exactly do you want to know?
This kernel supports charging with up to 2000 mA, which is Qualcomm QuickCharge.
Hope that answers your question.
Click to expand...
Click to collapse
yeah that's what i wanted to know that does your kernel has charge current control... thanx for adding that patch...
Sent from my oneplus2 using Tapatalk
---------- Post added at 12:18 AM ---------- Previous post was at 12:17 AM ----------
xdvs23 said:
What exactly do you want to know?
This kernel supports charging with up to 2000 mA, which is Qualcomm QuickCharge.
Hope that answers your question.
Click to expand...
Click to collapse
one more thing you mentioned your kernel is based on boefla's sources...his new kernel is any kernel work both on cm as well as oxygen os.. same in your case?
Sent from my oneplus2 using Tapatalk
Nik_ said:
yeah that's what i wanted to know that does your kernel has charge current control... thanx for adding that patch...
Click to expand...
Click to collapse
No problem, credits go to @benschhold for adding that
Nik_ said:
one more thing you mentioned your kernel is based on boefla's sources...his new kernel is any kernel work both on cm as well as oxygen os.. same in your case?
Click to expand...
Click to collapse
Hold on, the kernel is not based on Boeffla's. It is based on benschhold's.
xdvs23 said:
Hold on, the kernel is not based on Boeffla's. It is based on benschhold's.
Click to expand...
Click to collapse
lol ok sorry.. but did you made it specially for aosp based roms or cm too? or should i give it a shot and try?
Sent from my oneplus2 using Tapatalk
Nik_ said:
lol ok sorry.. but did you made it specially for aosp based roms or cm too? or should i give it a shot and try?
Click to expand...
Click to collapse
It is for CM and CAF based ROMs.
And because I use AnyKernel, it should work on most ROMs.
But of course it is worth to give it a try.
Nik_ said:
lol ok sorry.. but did you made it specially for aosp based roms or cm too? or should i give it a shot and try?
Sent from my oneplus2 using Tapatalk
Click to expand...
Click to collapse
it works with tipsy.tipsy is aospb based.
Sent from my ONE A2003 using XDA-Developers mobile app
Deleted
Does it have the bug which keeps your device awake
nice to see that kernel development is going on, on OnePlus 2.

[REFERENCE] [OOS/CUSTOM] OnePlus 5T kernel source with linux-stable (4.4.162)

Introduction
Hello everyone, this is a thread to introduce both users and kernel developers to the concept of linux-stable as well as give developers some tips and a tree to either merge into their own, use as a base, or just as a reference. Feel free to ask questions and enjoy!
What is it?
linux-stable is, as the name implies, the stable branch of the Linux kernel, the base of Android. The phone could not run without the Linux kernel (at least not without reworking a lot of stuff). The Android kernels are based on the longterm stable trees:
Longterm
There are usually several "longterm maintenance" kernel releases provided for the purposes of backporting bugfixes for older kernel trees. Only important bugfixes are applied to such kernels and they don't usually see very frequent releases, especially for older trees.
Click to expand...
Click to collapse
Source: https://www.kernel.org/category/releases.html
All Linux development happens on the master branch, which is governed by Linus Torvalds. When issues are discovered there, the fixes are applied then backported to these various stable trees for consumption. It is not uncommon for a fix to need to go back a few years.
There is a LOT more information available in the notes repo in the android-linux-stable organization if you care to learn more in-depth: https://github.com/android-linux-stable/notes
What does this mean for me?
If you are a developer, this means you should be merging these changes into your own tree. These are vetted, stable fixes to real world problems and they are being handed out for free. It does not take long to get up to date (as you can just merge this tree directly into your own or do it yourself using the tree as a reference) and once you are up to date, there is usually a release once every two weeks, give or take. I provide a rebuttal to a lot of various complaints here. If you still feel like there is a good reason not to do this, please let me know, I'll be happy to try and debate on it!
If you are a user, it means that you should be looking for and using kernels that have these fixes, as it shows the developers care for your security and stability. The current version for this device is 4.4.78 on OOS and 4.4.100 on Lineage while the current version upstream is 4.4.162 so all you need to do is go into Settings > About phone and look at the kernel version to know if you are up to date.
How do I use?
If you are a developer, the reference tree is located in the android-linux-stable organization: https://github.com/android-linux-stable/op5
There are three branches, one for OxygenOS 8.0 stable, one for OyxgenOS 8.1 beta, and one for Lineage 15.1.
This can either be merged into your existing kernel tree if you have one or be used as a fresh base. You do not need my permission to use it nor do you need to give me credit (although it would be appreciated).
If you are a user, use a kernel that has the changes added in!
Getting notified about updates
There are a few ways to get notified of linux-stable updates:
The linux-kernel-announce mailing list: http://vger.kernel.org/vger-lists.html#linux-kernel-announce
The android-linux-stable Telegram channel: https://t.me/alsupdates
Subscribe to this thread
Follow me on Google+ or Twitter
Getting help
If you have any issues with getting these changes into your tree or want to ask a question, there are a few different ways to do it:
Post in this thread
Join the linux-stable support chat on Telegram: https://t.me/joinchat/C1UAJ1EMSX31PCFdwLnOSg
File an issue either in the android-linux-stable notes repo or the android-linux-stable repo for this device
When requesting help, please give some solid details as to what you are struggling with, as I am happy to provide assistant and clarity but not to do something for you (unless I screwed up).
The OP has been updated, including some more information for users as well as some more ways of getting help and notified of updates! Enjoy
Very Nice.!!! :fingers-crossed:
nathanchance said:
The OP has been updated, including some more information for users as well as some more ways of getting help and notified of updates! Enjoy
Click to expand...
Click to collapse
Thanks for everything Sir.
You really are techno-Jesus, here to teach the ways of kernel perfection. I love your work, dedication, and care for your kernel users. Flash4lyfe.
Yes, please flame me for being a fanboy. You can never show enough appreciation for our beloved xda developers (especially the ones that don't treat users like ****).
Many thanks for your work and initiative @nathanchance :good: appreciated :highfive:
Currently giving a try to make a kernel version based from linux .116 of your op5 branch and looks like I have the following error :
Code:
fs/f2fs/f2fs.h:136:20: error: static declaration of 'inode_nohighmem' follows non-static declaration
Any idea ? I was thinking of a "KBUILD_CFLAGS" addition into Makefile (or something like that), but I'm probably wrong I guess.
FYI I'm using stock 4.9 android google toolchain
AndroidGX said:
Many thanks for your work and initiative @nathanchance :good: appreciated :highfive:
Currently giving a try to make a kernel version based from linux .116 of your op5 branch and looks like I have the following error :
Code:
fs/f2fs/f2fs.h:136:20: error: static declaration of 'inode_nohighmem' follows non-static declaration
Any idea ? I was thinking of a "KBUILD_CFLAGS" addition into Makefile (or something like that), but I'm probably wrong I guess.
FYI I'm using stock 4.9 android google toolchain
Click to expand...
Click to collapse
Wow I am so sorry about that, I must not have built 4.4.116 I removed all of the upstream f2fs code in my own kernel tree so I didn't encounter this error. I have pushed the fix that popped up in kernel/common, should be able to pull and build successfully now :good: :highfive:
nathanchance said:
Wow I am so sorry about that, I must not have built 4.4.116 I removed all of the upstream f2fs code in my own kernel tree so I didn't encounter this error. I have pushed the fix that popped up in kernel/common, should be able to pull and build successfully now :good: :highfive:
Click to expand...
Click to collapse
No worries
Thanks, it works like a charm now (currently trying my kernel on .116), again good job :highfive:
Cheers'
4.4.117 has been merged in.
4.4.118 has been merged in (conflict notes).
4.4.119 and OOS 5.0.4 have been merged in.
4.4.120 has been merged in (conflict notes).
thanks for making this, trying to build lineage and I keep getting the following error:
Code:
drivers/bluetooth/btfm_slim.c:26:23: fatal error: btfm_slim.h: No such file or directory
Any ideas?
---------- Post added at 10:47 PM ---------- Previous post was at 10:20 PM ----------
lol, found one of your comments on another post that helped
Use an out folder.
mkdir out
make O=out mata_defconfig
make O=out -j$(nproc --all)
Click to expand...
Click to collapse
new problem, the kernel compiles into an Image.gz, how would I go about getting a zImage for use in AnyKernel
aeppacher said:
thanks for making this, trying to build lineage and I keep getting the following error:
Any ideas?
---------- Post added at 10:47 PM ---------- Previous post was at 10:20 PM ----------
lol, found one of your comments on another post that helped
new problem, the kernel compiles into an Image.gz, how would I go about getting a zImage for use in AnyKernel
Click to expand...
Click to collapse
That is the zImage (you'll actually want to use Image.gz-dtb), you can just add it to the AnyKernel2 zip as is, the backend handles that name.
Sent from my Google Pixel 2 XL using XDA Labs
nathanchance said:
That is the zImage (you'll actually want to use Image.gz-dtb), you can just add it to the AnyKernel2 zip as is, the backend handles that name.
Sent from my Google Pixel 2 XL using XDA Labs
Click to expand...
Click to collapse
It booted perfectly, thanks so much! I would use the thanks button but it doesn't seem to be working :/
4.4.121 has been merged in.
I will have a new tree based on the 8.1 sources out tonight.
Sent from my Google Pixel 2 XL using XDA Labs
I have added a new branch for the 8.1 beta source; I will continue to update both 8.0 and 8.1 until 8.1 goes stable.
https://github.com/android-linux-stable/op5/commits/oneplus/QC8998_O_8.1
4.4.122 has been merged in.
4.4.123 has been merged in.

Categories

Resources