Database Develop

[KERNEL] {ADA} *NEW AOSP* v3.0.51 ZenSERIES v2 *BreakingGround* {Jelly Bean} [KERNEL]

Please stay tuned

Reserved

I heard this kernel is one of great kernel in GNex forum.
I'll flash it right away
Sent from my Nexus S using Tapatalk 2

Cool, I love flashing new releases

A new challenger appears! I'll have to try this out sometime in the near future, but it will be hard to tear me away from Marmite.
Sent from my Nexus S using xda app-developers app

Does not boot.
using latest CM10 nightly

Brishen said:
Does not boot.
using latest CM10 nightly
Click to expand...
Click to collapse
No Custom IOCTL stuff I guess..
Sent from my Nexus S using Tapatalk 2

Op does not Specify weather this Kernel is for,
CM Based roms
AOSP Based roms
AOKP Based Roms
I Tried it on Latest Paranoid Android (CM Based) and it black screens.

Is now compatiable with AOSP ROMS Only. I will have bbedward from post #2 look into some of the comments here. He is our kernel developer building blindly on this device
Thank you all for trying and posting your experiences, we will certainly get you fixed up!
Purian23

Thank you for your sharing.

purian23 said:
Should be compatible with all ROMS out there. Same as it is on the Nexus. I will have bbedward from post #2 look into some of the comments here. He is our kernel developer building blindly on this device
Thank you all for trying and posting your experiences, we will certainly get you fixed up!
Purian23
Click to expand...
Click to collapse
AOSP and AOKP based roms use the same Kernels but CM Based roms use different Kernels and will not work unless setup specifically for CM Roms.

This is 5.4 MB? Hmmm...need to see how it performs.

Tested this kernel. Overall snappy & fast with Ondemandx even at stock speeds. There is no bigmem support. This is very important for Nexus S due to low available memory. Screen colors look too yellow. This can be adjusted by user if Voodoo color is included. Inclusion of USB fast charge will give an added advantage.

anshumandash said:
Tested this kernel. Overall snappy & fast with Ondemandx even at stock speeds. There is no bigmem support. This is very important for Nexus S due to low available memory. Screen colors look too yellow. This can be adjusted by user if Voodoo color is included. Inclusion of USB fast charge will give an added advantage.
Click to expand...
Click to collapse
also no Crt Fix ..

Didnt work for me with a cm10.

raducux said:
Didnt work for me with a cm10.
Click to expand...
Click to collapse
will a cm10 version be available?

Its based on aosp source and was tested on crossbones ROM, I'll get the rest of you guys figureld out soon.
---------- Post added at 02:18 PM ---------- Previous post was at 01:22 PM ----------
Big Dog KMc said:
AOSP and AOKP based roms use the same Kernels but CM Based roms use different Kernels and will not work unless setup specifically for CM Roms.
Click to expand...
Click to collapse
I understand, looks like CM requires a kernel patch for this http://review.cyanogenmod.org/#/c/23541/
I was unaware as it was tested on an aosp based rom

We made a decision here, we're not going to support CyanogenMOD officially.
We will update the OP accordingly, it's just not desirable to maintain 2 builds for 1 device. The kernel should be fully compatible with AOSP/AOKP, and will be the kernel bundled with the CrossBones rom.
If you wish to use this kernel on CyanogenMod, you may build a copy yourself using herring_zen_defconfig and setting CONFIG_FOR_CYANOGENMOD=y . Keep in mind unofficial builds won't be officially supported by us. Please when building an unofficial kernel ALWAYS SET CONFIG_ZEN_VERSION_CODE=0. While it may not have any affect now, it may affect some userspace apps.
The kernel source is located here: https://github.com/AndroidDeveloperAlliance/ZenKernel_Crespo
We also provide a custom prebuilt GCC toolchain you can use here: https://github.com/AndroidDeveloperAlliance/ZenKernel_ARCH_armv7a_compiler
Only official builds are supported!
Thanks

bbedward said:
We made a decision here, we're not going to support CyanogenMOD officially.
We will update the OP accordingly, it's just not desirable to maintain 2 builds for 1 device. The kernel should be fully compatible with AOSP/AOKP, and will be the kernel bundled with the CrossBones rom.
If you wish to use this kernel on CyanogenMod, you may build a copy yourself using herring_zen_defconfig and setting CONFIG_FOR_CYANOGENMOD=y . Keep in mind unofficial builds won't be officially supported by us. Please when building an unofficial kernel ALWAYS SET CONFIG_ZEN_VERSION_CODE=0. While it may not have any affect now, it may affect some userspace apps.
The kernel source is located here: https://github.com/AndroidDeveloperAlliance/ZenKernel_Crespo
We also provide a custom prebuilt GCC toolchain you can use here: https://github.com/AndroidDeveloperAlliance/ZenKernel_ARCH_armv7a_compiler
Only official builds are supported!
Thanks
Click to expand...
Click to collapse
Looks like I won't be trying this kernel, then.

Stay tunes for V2, thanks for the feedback from some of you. Added bigmem, voodoo color support, usb fast charge support, some more lowmemorykiller upstream updates, and also cifs+fuse FS support.
ScOULaris said:
Looks like I won't be trying this kernel, then.
Click to expand...
Click to collapse
We're offering this to the community with no expectations that you use it, but for those who do use it we want them to be completely satisfied.
If it doesn't work for you, then I encourage you to use something from one of the other great development teams out there.
I thought of a couple solutions: 1.) creating 2 kernel builds, 2.) creating a sysfs interface so CM users could flash an init script that'd enable the CM ioctl's. Basically it comes down to this - neither solution is up to my standards for now.

[UNOFFICIAL] CM-compatible franco/faux kernels

Notice: Probably won't be keeping up with this much longer. CM has a slew of other commits, but I've only been including the two responsible for the discoloration...
Franco:
I've compiled franco's kernel with two cherrypicks from CM's github: c53fb6d134 and 07cbfb9a9c
These are required for recent nightlies of CM and its derivatives (caveat: if your rom specifically has commits reverted to not require such a workaround, then of course this isn't pertinent to you).
No changes to ramdisk or .config. Compiled using arm-linux-androideabi-4.7 from android ndk r9.
It should go without saying that you shouldn't flash this unless you understand what those commits are for and have a need for them. Those using the "colorfix" zip or otherwise reverting to an earlier liboverlay.so will find that method no longer "works" with newer builds (it spewed errors in dmesg nonstop when it worked).
IMPORTANT: Make sure you update to the new liboverlay.so if you're currently using the old one or you will have problems. Flash this on a rom that doesn't have the corresponding rom-side commits and you will of course have problems too (and I will laugh at you). As well, make sure to remove any addon.d script that you may have been using, if applicable. I don't know if there are multiple "colorfix" zips in circulation, but the one that I came across looks like it creates /system/addon.d/95-cm.sh. After deleting this file, you should be able upgrade/reflash the rom to bring liboverlay.so back up to date. Or if you're lazy/inept, wipe /system and reflash your rom+gapps.
Because of ramdisk customizations (incompatibilities) among roms/kernels, this zip will attempt to patch your existing ramdisk with franco's changes during flash. Things can obviously go wrong, so be ready.
4.4: 2013.11.29 1411ET: [franco-r195-cm-ziddey.zip]
4.4: 2013.11.25 0257ET: [franco-r194-cm-ziddey.zip]
4.3: 2013.10.26 2049ET r193: [JWR] [JSS/JLS]
-------------------------------------
Faux:
I built faux's kernel with the two commits as well.
4.4.1/4.4.2:
Faux: [030u-CM] [030m-CM]
4.4:
Faux: [029u-CM] [029m-CM]
4.3:
Faux: [028u-JSS] [028m-JSS] [028u-JWR] [028m-JWR]
Faux: [027u-JSS] [027m-JSS] [027u-JWR] [027m-JWR]
Note this is an "anykernel" and uses whatever the existing ramdisk is. If switching from Franco (or another kernel that includes a ramdisk), a "reset" kernel is recommended (reflash rom).
Built with arm-linux-androideabi-4.7, with bfd linker instead of gold.

Same as cm10_colorfix.zip?

Thanks alot! I will see if I can comment on any improvement in battery life or performance.
Sent from my Nexus 4 using Tapatalk

I don't think that these two patches will improve performance or battery life.

droidjam said:
I don't think that these two patches will improve performance or battery life.
Click to expand...
Click to collapse
But the use of incompatible library and the constant stream of errors caused by it may impact negatively on them.
Sent from my Nexus 4 using Tapatalk

Thanks alot for doing this.

Will be flashing this soon, all of @ziddey's mods have worked great!

Using this kernel for a while now. Working good if not better.
Thanks ziddey , for filling in such gaps whenever needed. That helps in keeping the ecosystem open to choices
Sent from my Nexus 4

Just flashed will test battery ect
Sent from my Nexus 4 using xda app-developers app

Is there a specific build I should be on when using PAC? I'm on the 16 and even with colorfix I can only use one other kernel that I know of, hells core. Others don't let me pass the boot animation. The same thing happens with this kernel. No colorfix and I used jss
Sent from my Nexus 4 using Tapatalk 4

Thanks a lot, it works great! I hope you will keep this updated when Franco releases a new version.. I should definitely learn how to compile it by myself
Inviato dal mio Nexus 4 con Tapatalk 4

NUNsLAUGHTER92 said:
Is there a specific build I should be on when using PAC? I'm on the 16 and even with colorfix I can only use one other kernel that I know of, hells core. Others don't let me pass the boot animation. The same thing happens with this kernel. No colorfix and I used jss
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
link to kernel source for pac

ziddey said:
link to kernel source for pac
Click to expand...
Click to collapse
RoliSoft said:
According to this https://github.com/PAC-man/android_vendor_pac/blob/cm-10.2/dependencies/mako.dependencies dependency list, the complied kernel for mako is this: https://github.com/zyonee/android_kernel_google_msm
Click to expand...
Click to collapse

And you said as of which build did it stop working, 10/16? There haven't been any new kernel commits since 10/3: https://github.com/zyonee/android_kernel_google_msm/commits/cm-10.2
Further, here's the cm kernel git for comparo: https://github.com/CyanogenMod/android_kernel_google_msm/commits/cm-10.2
https://github.com/PAC-man/android_vendor_pac/blob/cm-10.2/dependencies/mako.dependencies
It uses cm's mako repo.

ziddey said:
And you said as of which build did it stop working, 10/16? There haven't been any new kernel commits since 10/3: https://github.com/zyonee/android_kernel_google_msm/commits/cm-10.2
Further, here's the cm kernel git for comparo: https://github.com/CyanogenMod/android_kernel_google_msm/commits/cm-10.2
https://github.com/PAC-man/android_vendor_pac/blob/cm-10.2/dependencies/mako.dependencies
It uses cm's mako repo.
Click to expand...
Click to collapse
I haven't been able to since I used the 10/9 nightly. If there haven't been any other changes then I don't know why it won't work. I wiped data before going to the nightly on the 16th and it would boot if I didn't flash a different kernel, but if I did then it'd stay on the boot animation forever. It does that for the 20th too, although I didn't wipe data before going to the nightly.
Sent from my Nexus 4 using Tapatalk 4

Thank you thank you thank you!

Stock camera wont start with this kernel for me on latest 2013-10-21 nightly for me.

Fine here. Referring to gallerygoogle and not gallery2
Sent from my phone. Please forgive typos and brevity.

build r192 is available on Franco's thread
http://forum.xda-developers.com/showpost.php?p=46663872&postcount=50533

Uh huh
Sent from my phone. Please forgive typos and brevity.

CyanogenMod/Omni are Using very old Blobs for Yuga

most of us here are either using cm11 or omnirom or AOKP no idea if anyone here actually realised it but the blobs we are using are based on 4.1.2 which some patched to get it working in kitkat most of the time there is nothing wrong with it.. but as this blobs are closed source we are not aware of the changes thus we may be lacking in important improvement like more smoothness ? cutting down our battery usage etc
also I have no idea if the latest kernel changes are merged in but it looks like this hopes of this device becoming down hill is starting to rise..
I really hope this device isn't forgotten due to google play edition or the z1

iKillCypher said:
most of us here are either using cm11 or omnirom or AOKP no idea if anyone here actually realised it but the blobs we are using are based on 4.1.2 which some patched to get it working in kitkat most of the time there is nothing wrong with it.. but as this blobs are closed source we are not aware of the changes thus we may be lacking in important improvement like more smoothness ? cutting down our battery usage etc
also I have no idea if the latest kernel changes are merged in but it looks like this hopes of this device becoming down hill is starting to rise..
I really hope this device isn't forgotten due to google play edition or the z1
Click to expand...
Click to collapse
I have *no* idea what you're talking about.
Kernel: https://github.com/CyanogenMod/android_kernel_sony_apq8064/commits/cm-11.0
Commits to look at: https://github.com/CyanogenMod/andr...mmit/f16949940d1cf4a292de0a02409b284713bd8c5c (merge .2.67 release)
https://github.com/CyanogenMod/andr...mmit/289394f3bd6b121ec5b42453f5b6b1c8614196ba (merge old cm11 commits to new cm-11.0 branch)
https://github.com/CyanogenMod/andr...mmit/751383c3b257f23485b5aa7981573db1b6289282 (merge kk2.7 to new cm-11.0)
What this means: Contains .2.67 code from Sony, plus kk2.7 code from codeaurora, making the kernel arguably more up to date than Sony's.
Vendor: https://github.com/TheMuppets/proprietary_vendor_sony/commits/cm-11.0
Commits to look at: https://github.com/TheMuppets/propr...mmit/0a442f0b87e168ebdbc0f30b70d05dbe01a18ed3 (update blobs to .2.67)
What this means: Blobs updated to .2.67
The last I checked, .2.67 was 4.2.2, not 4.1.2. I'm not even sure why I'm so mad, maybe it's just that I don't like misinformation, particularly misinformation that can be *easily* checked.

As an example i could state the old modem they use? There are massive improvements in the modem in the 4.3 official version, but all these are missing when running CM11. It's the reason why i went back to 4.3 official.

beN.. said:
As an example i could state the old modem they use? There are massive improvements in the modem in the 4.3 official version, but all these are missing when running CM11. It's the reason why i went back to 4.3 official.
Click to expand...
Click to collapse
It would be nice if you could show what the "massive improvements in the modem in the 4.3 official version" are I mean, I'm not trying to be sarcastic, but new things for the sake of new things doesn't make much sense unless there are provable differences. Besides, the 4.3 stuff is probably being worked on right now, you can see that the camera is already being tested, for example.

For me the massive improvement is getting stable Wi-Fi at places where CM11 doesn't even find the network or fails to connect.
Range and stability is improved a lot in 4.3 official.

hey pandaball
I just spoke to Kali- few hours ago and it seems like they will be pushing for 4.3 blobs updates soon... for cm 11
also the kernel it seems like I got mislead cause there was no gerrit updates on it ? is it confirm that the latest CM11 is indeed using the latest kernel source from Sony ?
18<Kali-18> i got a talk with cdesai about Z 11.0 blob
18<Kali-18> and we should move to 4.3.3 blob/kernel
18<Kali-18> no update on 10.2

iKillCypher said:
hey pandaball
I just spoke to Kali- few hours ago and it seems like they will be pushing for 4.3 blobs updates soon... for cm 11
also the kernel it seems like I got mislead cause there was no gerrit updates on it ? is it confirm that the latest CM11 is indeed using the latest kernel source from Sony ?
18<Kali-18> i got a talk with cdesai about Z 11.0 blob
18<Kali-18> and we should move to 4.3.3 blob/kernel
18<Kali-18> no update on 10.2
Click to expand...
Click to collapse
The kernel typically doesn't get committed via gerrit, it is pushed directly to the CM github. It isn't using the latest Sony kernel, it uses the 2.67 kernel with the kk2.7.1 branch from codeaurora, which is more up-to-date than the Sony kernel in terms of SOC drivers.

At best this is a Q&A thread.
So lets just consider the question answered and put this baby to bed.
Thread closed

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

[EOL][KERNEL][UNOFFICIAL BUILDS] Boeffla Kernel Linaro/Uber
hi Guys,
It's me again and this time with a special "build-service" for boeffla kernel users! As some of them liked the "linaro build" made by Lord Boeffla in form of his 5.1 beta 13 version and requested it for newer versions too i decided to "tune" my build script a bit and spent that 2 min 40 sec in addition on every build for those of you who requested a Linaro build of recent versions of the boeffla kernel. As i anyway do my own builds of every new released (but only for samsung sources!) Boeffla Kernel version mainly for testing new versions of the ZZMoove Governor, building itself isn't that much more effort.
As stated Lord Boeffla used the linaro toolchain in his kernel version 5.1 beta 13 but he finally came back again to the well proven Android Stock Toolchain in following versions for stability reasons. Good and understandable decision because this is really what Boeffla stands for, stability and i underlined that *g*!! Kernel images build with linaro toolchain tend to be less stable then build with a stock toolchain due to the optimizations it makes to the code when it builds the image. Anyway they run a little bit "smoother/faster" and for some of you it even might not make any troubles at all. So in agreement with Lord Boeffla i want to provide you these self made linaro builds here for your further usage. Beside of that for really brave guys *g* i will in addition use this thread for own purposes too and will put in here beta versions of zzmoove governor compiled into boeffla kernel. But they will only be "Samsung" versions as i'm using only stock roms and they will only be build with stock toolchain because zzmoove is sometimes experimental enough, i have no need for more "unexpectedness" by using linaro toolchains during testing
ok then let's start...
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!
About bugs: Before you report ANY issues with the linaro builds provided here (doesn't matter which one!) FIRST TRY the non-linaro 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 builds of boeffla kernel.
About benchmarks and comparisons between toolchains: It's common known that linaro 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 repositories from HERE
with some not worth to mention minor changes to be able to build it on my build environment.
all images are compiled with following build flags which were also used in boeffla kernel 5.2 beta 4
and with NEW Toolchain Linaro 4.9.3-2015.03 - Credits to @Christopher83 for the preconfigured toolchain and many many thanks to @P$T for the pm with the info and credits for the needed modifications i could use from his repo! :highfive: meanwhile even @Lord Boeffla benefited also from this info and therefore we had also a stock toolchain 4.8 build
all images are build with lzma compression instead of gzip to produce a compatible images size with the used optimization flags below
Code:
-Wall -Wundef -Wstrict-prototypes -Wno-trigraphs
-fno-strict-aliasing -fno-common
-Werror-implicit-function-declaration
-Wno-format-security -Wno-array-bounds
-fno-delete-null-pointer-checks -fno-schedule-insns2 -ffast-math
-mtune=cortex-a9 -march=armv7-a -mcpu=cortex-a9 -mfpu=neon -marm
-fno-schedule-insns2 -mno-unaligned-access -fno-pic
ifdef CONFIG_CC_OPTIMIZE_FOR_SIZE
KBUILD_CFLAGS += -Os
else
KBUILD_CFLAGS += -Ofast -fmodulo-sched -fmodulo-sched-allow-regmoves -fno-tree-vectorize
endif
all images are build with changes from following repos:
Samsung i9300 Stock
https://github.com/zanezam/boeffla-kernel-samsung-s3
Samsung i9300 CM/LineageOS/Omnirom
https://github.com/zanezam/boeffla-kernel-cm-s3
https://github.com/zanezam/boeffla-kernel-omnirom-s3
Elite Boeffla Kernel:
https://github.com/zanezam/elite-boeffla-kernel-lineage14.1-i9300
Samsung n51x0 Stock
https://github.com/zanezam/boeffla-kernel-samsung-n51x0
Samsung n51x0 CM/LineageOS
https://github.com/zanezam/boeffla-kernel-cm-n51x0
what i will do:
build the source code with linaro toolchain and (like Lord Boeffla usually does) provide a odin-flashable tar.md5 and 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 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 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 experienced user comes up with "better" ones (feel free to post and let me know, linaro specialists! *g*)
Downloads:
Galaxy S3
GT-I9300 Samsung builds
(for Samsung JB 4.3 and Samsung KK 4.4 ARCHIPORT)
GT-I9300 Cyanogenmod 11 builds
(for CM11, Temasek unofficial CM11)
GT-I9300 Cyanogenmod 12 builds
(for CM12, full support for TeamUB unofficial CM12, confirmed to run also on some other CM12 variants but u have to try yourself as they are untestet by me)
GT-I9300 Cyanogenmod 12.1 builds
(for CM12.1, full support for unofficial CM12.1 by JustArchi, Moster2 and arter97, confirmed to run also on some other CM12.1 variants but u have to try yourself as they are untestet by me)
GT-I9300 Cyanogenmod 13.0 builds
(for CM13.0, support for official CM13.0 and based roms)
GT-I9300 Cyanogenmod 14.1 / LineageOS 14.1 builds
(for LineageOS14.1/CM14.1, support for official LineageOS14.1/CM14.1 and based roms)
GT-I9300 Omnirom builds
(for Omnirom, Slimkat, Carbon, AOKP etc.)
Elite Boeffla Kernel:
Elite Boeffla Kernel GT-I9300 Cyanogenmod 14.1 / LineageOS 14.1 builds
(for LineageOS14.1/CM14.1, support for official LineageOS14.1/CM14.1 and based roms)
Check out original thread with info and changelogs of Elite Boeffla Kernel
Galaxy Note 8
N5100:
GT-N5100 Samsung Jelly Bean 4.2.2 builds
(for Samsung JB 4.2.2 roms)
GT-N5100 Samsung KitKat 4.4.2 builds
(for Samsung KK 4.4.2 roms)
GT-N5100 CyanogenMod 12.0 builds
(for CyanogenMod 12.0 roms)
GT-N5100 CyanogenMod 12.1 builds
(for CyanogenMod 12.1 roms)
GT-N5100 CyanogenMod 13.0 builds
(for CyanogenMod 13.0 roms)
GT-N5100 LineageOS 14.1 builds
(for LineageOS 14.1 roms)
N5110:
GT-N5110 Samsung Jelly Bean 4.2.2 builds
(for Samsung JB 4.2.2 roms)
GT-N5110 Samsung KitKat 4.4.2 builds
(for Samsung KK 4.4.2 roms)
GT-N5110 CyanogenMod 12.0 builds
(for CyanogenMod 12.0 roms)
GT-N5110 CyanogenMod 12.1 builds
(for CyanogenMod 12.1 roms)
GT-N5110 CyanogenMod 13.0 builds
(for CyanogenMod 13.0 roms)
GT-N5110 LineageOS 14.1 builds
(for LineageOS 14.1 roms)
N5120:
GT-N5120 Samsung Jelly Bean 4.2.2 builds
(for Samsung JB 4.2.2 roms)
GT-N5120 Samsung KitKat 4.4.2 builds
(for Samsung KK 4.4.2 + 4.4.4 roms)
GT-N5120 CyanogenMod 13.0 builds
(for CyanogenMod 13.0 roms)
GT-N5120 LineageOS 14.1 builds
(for LineageOS 14.1 roms)
Mirror on Androidfilehost for all devices (only latest kernel versions)
NOTE: if u got issues with root (cause is currently unknown!) after flashing one of these images u can try this method provided by @VictorLapin (thx for letting us know!)
previously known issues with recent boeffla kernel versions compiled with linaro toolchain (none of them appeared since one of newer toolchain 4.9.1 versions and also did not appear with actual used 4.9.2 version):
stuck of max. frequency for example at 1400mhz even if it is set to a higher max. frequency - reported by some users, and confirmed by me!
fix would be to temporary change the governor once or also temporary change the governor settings once (for example with profiles in boeffla config app)
EDIT: This is not related to the toolchain!
slower hotplug or sometimes stucking cores in zzmoove governor - reported by some users, not confirmed by me
higher "idle" temperature and operating temperature in general - confirmed by me
noticeable higher energy consumption (maybe related to next issue) - confirmed by me
lags when using zram and or in combination with frandom tweaks - confirmed by me
random hot reboots - confirmed by Lord Boeffla, not confirmed by me
see? that's really not boeffla like, isn't it!? but anyway as always these problems might depend "just" on one, some, or on a combination of multiple things so it might be that you never face them. If you find a setting and/or have other informations which workarounds or even fixes the issues feel free to post them here they would be highly appreciated! Even if this is not the main aim of that thread yet we maybe can find a way to a more stable linaro build of boeffla kernel and that would be a good thing, though! :highfive: Beside of that feel also free to post new issues found with the linaro builds but keep in mind don't forget to crosscheck with non-linaro offical builds to be sure that it is really related to the toolchain.
finally i wanna throw out big thanks to Lord Boeffla for his great work and for accepting that i provide you the linaro builds here especially because he had a bad feeling about this, but i think we will not disappoint him, won't we?!
enjoy living on the edge...

reserved
Reserved

Reserved
this one too

Great idea and thanks for all the work. If people get used to read OP before doing anything, we shouldn't be worried at all.
Sent from my GT-I9300 using XDA Premium 4 mobile app

Lulavc said:
Great idea and thanks for all the work. If people get used to read OP before doing anything, we shouldn't be worried at all.
Sent from my GT-I9300 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thx, yeah that might be the only problem

Lulavc said:
Great idea and thanks for all the work. If people get used to read OP before doing anything, we shouldn't be worried at all.
Click to expand...
Click to collapse
Isn't that like saying: There will be trouble for sure?

SaschaKH said:
Isn't that like saying: There will be trouble for sure?
Click to expand...
Click to collapse
Most likely yes. In the past we had overheating phones and zRam being weird.
But... still, thanks to ZaneZam to take the work and build the Linaro versions for it for the ones that like trouble
Andi

Version 5.2 beta 1 ready
Hi Guys,
just for info:
Boeffla-kernel-5.2-beta1-Samsung-i9300-linaro - build ok - testing
arriving in about a day (if everything is ok *g*)
EDIT: and looks good to me therefore added to the OP! enjoy!
regards
ZZ

fantastic !

Just want to say that I am using this kernel for about one week now and this is by far the smoothest kernel I have used. I really can feel the difference between Google Toolchain and linaro (Beofflas build is also smooth but I think this one is a tick faster). I don't have any of the problems mentioned in OP. Everything is working like it should.
@ZaneZam there is a new linaro build available - 14.01. I also see there are many devs using linaro 4.8.3. What is the difference compared to the linaro version 4.7.4 you are using?
Many thanks in advance.

bone069 said:
Just want to say that I am using this kernel for about one week now and this is by far the smoothest kernel I have used. I really can feel the difference between Google Toolchain and linaro (Beofflas build is also smooth but I think this one is a tick faster). I don't have any of the problems mentioned in OP. Everything is working like it should.
@ZaneZam there is a new linaro build available - 14.01. I also see there are many devs using linaro 4.8.3. What is the difference compared to the linaro version 4.7.4 you are using?
Many thanks in advance.
Click to expand...
Click to collapse
Thx for the info! nice to hear that! :highfive: well honestly atm i dunno exactly what's the differnce between these two toolchains (but i think it might be a lot, question is if it has big relevance for us ) i have to check that in a quiet minute. but what i know since yesterday from my own experience is that recent boeffla kernel beta2 (inofficial yet, but will come soon) + zzmoove 0.8b10 (release candidate, comes also soon) build with linaro 4.8.3 runs very good!! if that positive result stays for one more day :fingers-crossed: i will jump on that one and forget the other one!
we will see...

ZaneZam said:
Thx for the info! nice to hear that! :highfive: well honestly atm i dunno exactly what's the differnce between these two toolchains (but i think it might be a lot, question is if it has big relevance for us ) i have to check that in a quiet minute. but what i know since yesterday from my own experience is that recent boeffla kernel beta2 (inofficial yet, but will come soon) + zzmoove 0.8b10 (release candidate, comes also soon) build with linaro 4.8.3 runs very good!! if that positive result stays for one more day :fingers-crossed: i will jump on that one and forget the other one!
we will see...
Click to expand...
Click to collapse
Very nice to hear that. Thank you very much buddy

Waiting for the Linaro beta 2...

5.2 beta2?
Bro ZZ,
Any plan to recompile for 5.2 beta2?

Let me know when the omni version is up! I'm eager to help with any testing necessary.

ymy3890 said:
Bro ZZ,
Any plan to recompile for 5.2 beta2?
Click to expand...
Click to collapse
Yeah man, in a few hours and test with new Toolchain was very positive so this one will be a linaro 4.8.3 build

ZaneZam said:
Yeah man, in a few hours and test with new Toolchain was very positive so this one will be a linaro 4.8.3 build
Click to expand...
Click to collapse
Glad to hear it.

Little mess
ymy3890 said:
Glad to hear it.
Click to expand...
Click to collapse
hi guys,
sry to all of you who are waiting for the latest linaro build and still can't use it yet!
unfortunately this build delays a bit because of three reasons:
first: a dumb-ass "git" accident during prepare of sources - i really nuked my brand new build script - what a fu.... mess still can't beleve it
(for insiders: NEVER EVER do a "git clean -f -d" if you are in hurry or try to do mutli-tasking (last one applies not on girls *g*)! backup? what is this? needed? no yet! *g* yeah i hear u laughing insiders but i think some of u know exactly how this really feels if u have spend some hours for what u lost, actually so: :crying: well i will survive this but throws me back a bit. some of u might think: wtf? hours needed to a make a build script? well due to the latest motivation because of this thread here *g* it has grown up from a advanced script to a full automatic build programm
second: i have a "feeling" that Lord Boeffla will release a new beta soon!
third: day has too less hours (hence this giant automatic build "programm" *g*)
i'm just doing a dump of the latest changes i made from my brain into an older backup of the script
and will be back again if it is up and running and maybe also with new beta of boeffla kernel thenl! :good:
aaand yes as i said i did already a test with recent beta2 build with new linaro toolchain but this build has "something" included which is only for interenal testing yet. yeah u got me it has some final changes for the new "beast" included
so I ask for a little bit patience, thx!
cheers
ZZ

Thanks!
ZaneZam said:
hi guys,
[HIVE]
sry to all of you who are waiting for the latest linaro build and still can't use it yet!
unfortunately this build delays a bit because of three reasons:
first: a dumb-ass "git" accident during prepare of sources - i really nuked my brand new build script - what a fu.... mess still can't beleve it
(for insiders: NEVER EVER do a "git clean -f -d" if you are in hurry or try to do mutli-tasking (last one applies not on girls *g*)! backup? what is this? needed? no yet! *g* yeah i hear u laughing insiders but i think some of u know exactly how this really feels if u have spend some hours for what u lost, actually so: :crying: well i will survive this but throws me back a bit. some of u might think: wtf? hours needed to a make a build script? well due to the latest motivation because of this thread here *g* it has grown up from a advanced script to a full automatic build programm
second: i have a "feeling" that Lord Boeffla will release a new beta soon!
third: day has too less hours (hence this giant automatic build "programm" *g*)
i'm just doing a dump of the latest changes i made from my brain into an older backup of the script
and will be back again if it is up and running and maybe also with new beta of boeffla kernel thenl! :good:
aaand yes as i said i did already a test with recent beta2 build with new linaro toolchain but this build has "something" included which is only for interenal testing yet. yeah u got me it has some final changes for the new "beast" included
so I ask for a little bit patience, thx!
cheers
[/HIVE]
ZZ
Click to expand...
Click to collapse
Bro ZZ, I will be patiently waiting for it.

ZaneZam said:
second: i have a "feeling" that Lord Boeffla will release a new beta soon!
ZZ
Click to expand...
Click to collapse
Your "feeling" was absolutely right. Seems you got some insider information, hehe.
But now it is out, so go for it with Linaro
Thanks
Andi

[KERNEL][AOSP][11/11/15] Semaphore_Modified_6.0.0

This kernel is based on latest Semaphore 3.4.0 sources.
I was just missing some features in Semaphore kernel.. So added it for myself. Been using my modified version for long. Decided to release it for public now.
All credit goes to Stratosk (Developer of Semaphore kernel) for sharing such awesome kernel with us.
Special thanks to Ivan Lopez for helping me out.
Note: This kernel is for Android 6.0.0 (Marshmallow). Please do not flash it on Lollipop builds
Extra features that i added in semaphore kernel are:
- USB fast charging
- faux123 sound control
- Added fsync on/off support
- msm thermal: enhancements
Download: Semaphore_N4_6.0.0_Modified
XDA:DevDB Information
Semaphore_Modified kernel, Kernel for the Google Nexus 4
Contributors
snak3ater
Source Code: https://github.com/snak3ater/kernel_msm
Kernel Special Features:
Version Information
Status: Beta
Created 2015-11-11
Last Updated 2015-11-11

Reserved

Otg supported for nexus 4 with y-cable ?

Is this better than Tauras Kernel ?

mjehan said:
Is this better than Tauras Kernel ?
Click to expand...
Click to collapse
that totally depends on your experience with every kernel...why don't you try both and see which better fits your usage.

Tons of thanks for you. Waiting for semaphore6.0 for a long time. Lol.

yyfvteuemfw said:
Tons of thanks for you. Waiting for semaphore6.0 for a long time. Lol.
Click to expand...
Click to collapse
No problem..
But please note that it isn't Semaphore kernel. It's based on Semaphore kernel sources. 'Unofficial'.. To be precise ☺
I couldn't come up with a suitable name. So gave it a name of Semaphore_Modified ☺

Compiled using the same toolchains and stuff?
Edit: Not really important but thx for porting this kernel, really enjoy the extra speed and smoothness

jer_ying_fd said:
Compiled using the same toolchains and stuff?
Edit: Not really important but thx for porting this kernel, really enjoy the extra speed and smoothness
Click to expand...
Click to collapse
Toolchain used was linaro 4.7.4

Tried it for a day. WLAN did not stay active in deep sleep and lots of governors/schedulers missing.

XenderX666 said:
Otg supported for nexus 4 with y-cable ?
Click to expand...
Click to collapse
Otg is not yet supported

gandharva said:
Tried it for a day. WLAN did not stay active in deep sleep
Click to expand...
Click to collapse
Tested on Cataclysm Nov 08 Beta. WLAN had intermittent connection issues on 5 GHz. When using hells-Core b85 (Sabermod 4.9) with the same prima version, it works without issue. Could it be something in the upstream Linux patches in 3.4.110 or the Linaro toolchain conflicting?
If you want more info, I can reflash and get you a logcat.
Sent from my Nexus 4 using Tapatalk

Great
Using it since it was released on MinimalOS (21.Oct build). No issues, superb performance - as expected.
No wifi or other stability issues.
SOT 2h with 21h standby time and 46% remaining. Full sync, mixed Wifi and 3G
Tweaked: max CPU: 1350, Ondemand with Touch Load: 45 (918Mhz)
Thanks Stratosk and Snak3ater ! :good:

@snak3ater,
This is by far the most stable kernel for my Cataclysm Nexus 4!
A million thanks for bringing @stratosk masterpiece on MM.

xenyz said:
Tested on Cataclysm Nov 08 Beta. WLAN had intermittent connection issues on 5 GHz. When using hells-Core b85 (Sabermod 4.9) with the same prima version, it works without issue. Could it be something in the upstream Linux patches in 3.4.110 or the Linaro toolchain conflicting?
If you want more info, I can reflash and get you a logcat.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Like Semaphore was coded for 4.8.3 but not 4.7.4?

jer_ying_fd said:
Like Semaphore was coded for 4.8.3 but not 4.7.4?
Click to expand...
Click to collapse
Perhaps, but Semaphore was always 4.7 though. Lollipop kernels were built with GCC 4.6, but all Marshmallow kernels are built with GCC 4.8 now, I believe.
@snak3ater could you please rebuild the kernel with CONFIG_MODULES disabled? I've noticed some log spam and found the following info:
Kernel module_request personality-8:
Of course, none of this is needed if you have CONFIG_MODULES=n, which is preferred for Android.
Also, it could be worth trying a build on Linaro 4.7 as well as latest 4.8 to compare?
The good news is my WLAN seems to be working just fine today, after some bizarro problems over the weekend. I'm trying to reproduce the issue I experienced, but just can not.
Sent from my Nexus 4 using Tapatalk

xenyz said:
Perhaps, but Semaphore was always 4.7 though. Lollipop kernels were built with GCC 4.6, but all Marshmallow kernels are built with GCC 4.8 now, I believe.
@snak3ater could you please rebuild the kernel with CONFIG_MODULES disabled? I've noticed some log spam and found the following info:
Kernel module_request personality-8:
Of course, none of this is needed if you have CONFIG_MODULES=n, which is preferred for Android.
Also, it could be worth trying a build on Linaro 4.7 as well as latest 4.8 to compare?
The good news is my WLAN seems to be working just fine today, after some bizarro problems over the weekend. I'm trying to reproduce the issue I experienced, but just can not.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
I thought semaphore was built with Linaro gcc 4.8.2 201306 as written on the front page

jer_ying_fd said:
I thought semaphore was built with Linaro gcc 4.8.2 201306 as written on the front page
Click to expand...
Click to collapse
Nah, OP is incorrect
Sent from my Nexus 4 using Tapatalk

@xenyz this kernel uses Semaphore anykernel installer? Just to be safe as I read your post about TaUrUs Kernel and AK on Cataclysm thread.
---------- Post added at 03:52 PM ---------- Previous post was at 03:37 PM ----------
danielcepa said:
Using it since it was released on MinimalOS (21.Oct build). No issues, superb performance - as expected.
No wifi or other stability issues.
SOT 2h with 21h standby time and 46% remaining. Full sync, mixed Wifi and 3G
Tweaked: max CPU: 1350, Ondemand with Touch Load: 45 (918Mhz)
Thanks Stratosk and Snak3ater ! :good:
Click to expand...
Click to collapse
Nice. What ROM and app to change the kernel settings was you using?

Cristiano Lira said:
@xenyz this kernel uses Semaphore anykernel installer?
Click to expand...
Click to collapse
Yes, Semaphore_Modified uses the same Semaphore installer.
Sent from my Nexus 4 using Tapatalk