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

[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