Related
Since I've received some requests to share my kernel source, I've uploaded it:
http://www.zomgupload.com/m1geir6ftpfr.html
Feel free to take from me anything you want, I especially recommend SLQB and TinyRCU for starters.
Beware though, like I've already told doomlord, the existent SEMC wlan source doesn't work as it's incomplete and full of debug and tracing and what not. This means that some of my changes to the kernel render the default wlan modules useless, needing these to be recompiled which can only be done at the moment for CM7 (this is why I didn't release for stock).
Any doubts ask here, I've bookmarked this thread.
use github dude
anyways thanks...
wow, i have try this kernel, works good
[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
Hi falcon people!
This is my modified kernel with some kernel optimizations and some compiler optimizations.
The goal of abyss is to achieve improved performance/battery without the cost of stability.
I will not be overhauling this project with changes that are not logical to add.
This kernel should work on the latest 7.x.x (and maybe 6.x.x) roms like CyanogenMod and any other AOSP based rom.
How does one achieve this?
- build kernel with an optimized toolchain
- use compiler optimization flags (experimental)
- remove redundant code
- improve existing code with more efficient code
- reduce/increase speed of timers (depends on what type of function)
- etc. (most are not easy to explain)
Built with Linaro GCC 4.9 optimized for Cortex A7 with vfpv4 technology
Is there actually a performance improvement?
With all the changes added up, there should be. Whether or not one notices the difference is another thing.
Personally, I do feel the performance difference. It is easier to notice the difference with lower level specs like ours.
For those interested in how the kernel optimizations will benefit/work, please look at my github source and read the commit messages.
For those interested in how the compiler optimizations/hacks will benefit/work, please look at this article.
Downloads:
Discontinued
Source:
GitHub
Asking for ETA's won't be necessary because I use this kernel as my daily driver.
I do not mind if there's some non-development/off-topic discussion here, just no discussion about other works that is nowhere near related to mine.
Also, please refrain from comparing works here; it really kills the spirit of development. Go do that in some other thread.
XDA:DevDB Information
abyss kernel for aosp roms, Kernel for the Moto G
Contributors
YoshiShaPow, arter97, flar2, Christopher83, Cl3Kener, frap129
Source Code: [url]https://github.com/abyss-kernels/falcon[/URL]
Kernel Special Features: MAJOR KEY
Version Information
Status: Nightly
Created 2016-05-10
Last Updated 2016-12-18
Don't like the defaults?
Use Kernel Adiutor to change the settings!
Frequently Asked Questions:
Is this a custom kernel?
I was asked this question once, and it posed as a real good question. I do not consider abyss to be a "custom kernel" per se, but more so as a modified kernel. The patches and features that go into this kernel do not make it customizable. What they do is improve what has already been implemented. It is like swapping a car's engine for a better one rather than just adding LED flooring lights and fancy car mats.
Can you add [this] and [that] feature to abyss?
Something I pride myself with this kernel is that it does not have a bunch of random, useless features or patches mashed into it. Everything put into this kernel is thought out well and tested. I see a lot of works being made popular because it has [this] and [that] feature when really, it's nothing revolutionary. As a matter of fact, most things added to any kernel will not make it 5x better than any other kernel. Most of the time, simple is better; and in this case it definitely is!
Main Patches and Features:
- intelliplug (default hotplug)
- intelliactive governor
- KCAL Control Driver
- kexec hardboot patch for Multirom
- USB Force Fast Charge patch
- Abyss Optimizations (compiler)
- disabled debugging for more performance throughout
- lots of patches for better performance here and there... too many to list
How to install:
Download kernel from Basketbuild
Boot into TWRP recovery
(If you're coming from a different kernel, dirty flash current ROM)
Flash kernel zip
Reboot
Nice job bro ! [emoji3]
Thank you for this awesome kernel [emoji6]
Sent from my Moto G using XDA-Developers mobile app
this work with both cm and aosp or aosp only
zydes said:
this work with both cm and aosp or aosp only
Click to expand...
Click to collapse
It will work on any 6.x.x AOSP based rom (CyanogenMod included). The only roms it will not work with to my knowledge are Omni and SlimSaber.
edit: turns out it works with them
nx rom based cm work?
Can you add OC made be @h2o64 ? Really is a the difference if you do the benchmarks and in real life just a little so is true OC..
zydes said:
nx rom based cm work?
Click to expand...
Click to collapse
Yes, most likely.
Eurofighter_ty said:
Can you add OC made be @h2o64 ? Really is a the difference if you do the benchmarks and in real life just a little so is true OC..
Click to expand...
Click to collapse
I will look into it.
YoshiShaPow said:
It will work on any 6.x.x AOSP based rom (CyanogenMod included). The only roms it will not work with to my knowledge are Omni and SlimSaber.
Click to expand...
Click to collapse
Works just fine with Omni so far, SlimSaber would probably work also. Nice to see another kernel for us from you, Thanks!
amarc78 said:
Works just fine with Omni so far, SlimSaber would probably work also. Nice to see another kernel for us from you, Thanks!
Click to expand...
Click to collapse
Updated the OP and my earlier post. Thanks for testing
Thanks ? this kernel work perfeft
Sent from my Moto G using XDA-Developers mobile app
Carlos Arriaga said:
Thanks this kernel work perfeft
Sent from my Moto G using XDA-Developers mobile app
Click to expand...
Click to collapse
in androidfilehost you have kernel for falcon or condor carlosarinaga
zydes said:
in androidfilehost you have kernel for falcon or condor carlosarinaga
Click to expand...
Click to collapse
Perfect example of OT that development threads should not have. No more of these type of posts^ please.
YoshiShaPow said:
Perfect example of OT that development threads should not have. No more of these type of posts^ please.
Click to expand...
Click to collapse
soory for my post
can u add feature underclock for yuor kernel
zydes said:
soory for my post
can u add feature underclock for yuor kernel
Click to expand...
Click to collapse
Sorry, I won't be adding underclocking to this kernel. There really isn't much of a need for underclocking a phone. In the long run, battery consumption will not be changed, maybe only at the slightest.
Also, the more frequencies added, the slower a CPU governor works. Most governors run calculations based on cpu load, checking whether or not it needs to move up or down a frequency step. By adding more steps, the cpu will throttle slower.
Just updated the kernel with frandom support. Also added some ramdisk modifications to support it.
More entropy == better performance.
egg-caf-falcon-nightly-20160513.zip
Battery backup is good...give a try
It's great to see feedback from the users. New build with modified values; it should improve multitasking performance.
egg-caf-falcon-nightly-20160515.zip
navaneethkom said:
Battery backup is good...give a try
Click to expand...
Click to collapse
Yes, the battery is great, 18 hours standby and i get almost 4h sot, left with 52% right now. Anybody looking for great battery should go for it.
Here is my build of LineageOS 13.0 for the Galaxy S4 LTE A. It is based on the pure LineageOS code unless indicated otherwise.
* IMPORTANT *
Please note that these builds are based on nothing else than the unchanged official code from LineageOS. So every credit goes to the ones providing the code.
I will not and cannot make any changes to the code. The only thing I can do and will do is build the ROM.
Also, it should be understood that I take no responsibilities whatsoever if anything goes wrong when you install the ROM. Like any custom ROM this is completely at your own risk!
However, you can expect that any ROM I share has been installed on my own GT-I9506 (starting with the latest official Samsung firmware 5.0.1) and runs without obvious issues. Your mileage may vary.
https://www.mediafire.com/?c8q4lqh675hc97b,7dhley6dl6j9dnb
Based on LineageOS official code up to https://review.lineageos.org/154230
Which modem and boot loader can you recommend?
audianer said:
Which modem and boot loader can you recommend?
Click to expand...
Click to collapse
I flashed the latest official Samsung firmware to prepare for LineageOS 13.0
I'm trying to build the latest version, which does build without error, but upon booting gets stuck at starting the apps, i.e. just before showing the lock screen. The latest working build was from January 5th 2017 and I experienced the error first on a build of January 8th 2017. So I suspect the commit in question is one from January 6-8.
Before I'm forced to manually investigate commit-by-commit from the latest working version, does anyone know what has changed that causes this error? I was not able to get any output from adb logcat either, so I have no idea what went wrong... which is rather frustrating.
What device tree and kernel did you use?
DualJoe said:
What device tree and kernel did you use?
Click to expand...
Click to collapse
The same as the working previous build: LineageOS/android_kernel_samsung_ks01lte & LineageOS/android_device_samsung_ks01lte. As far as I can see nothing in the kernel or device tree has changed, thus it must be some incompatibility with the rest of the LineageOS code.
I just tried another build just an hour ago, same result: stuck at the final starting apps (before the vibration). I also tried reverting to a working state of the source (of January 5) by using "repo forall -c 'git checkout `git rev-list --all -n1 --before=", but that one didn't even build.
I would appreciate any help here. It's not like there were some exhaustive documentation about how to build LineageOS. And anyway, apparently building is not the issue here.
If that's still Solk2's stuff it might be very old indeed.
DualJoe said:
If that's still Solk2's stuff it might be very old indeed.
Click to expand...
Click to collapse
No. It seems that @solk2 has started to develop the ks01lte again. See the github commits:
https://github.com/LineageOS/android_kernel_samsung_ks01lte/tree/cm-13.0
https://github.com/solk2/android_kernel_samsung_ks01lte/commits/cm-13.0
https://github.com/LineageOS/android_device_samsung_ks01lte/tree/cm-13.0
https://github.com/solk2/android_device_samsung_ks01lte/commits/cm-13.0
(Note: There is no cm14.1 branch on @solk2's github repo yet.)
WeirdSoup said:
No. It seems that @solk2 has started to develop the ks01lte again. See the github commits:
https://github.com/LineageOS/android_kernel_samsung_ks01lte/tree/cm-13.0
https://github.com/solk2/android_kernel_samsung_ks01lte/commits/cm-13.0
https://github.com/LineageOS/android_device_samsung_ks01lte/tree/cm-13.0
https://github.com/solk2/android_device_samsung_ks01lte/commits/cm-13.0
(Note: There is no cm14.1 branch on @solk2's github repo yet.)
Click to expand...
Click to collapse
Uhm... There are cm-14.1 branches too.
zardak said:
Uhm... There are cm-14.1 branches too.
Click to expand...
Click to collapse
I said "@solk2's repo".
And as you can see, there are no additional commits on CM14.1 branch in LOS's ks01lte device repo, compared to cm13.
WeirdSoup said:
I said "@solk2's repo".
And as you can see, there are no additional commits on CM14.1 branch in LOS's ks01lte device repo, compared to cm13.
Click to expand...
Click to collapse
Well, solk2 started to push changes on his kernel's repo days ago, even on cm-14.1 branch.
Anyway, I think is just a matter of time. We'll get official builds sooner or later.
I just don't understand why solk2, kyasu, and possibly gugu0das and others don't collaborate all together to only one kernel/device for this phone
zardak said:
Well, solk2 started to push changes on his kernel's repo days ago, even on cm-14.1 branch.
Anyway, I think is just a matter of time. We'll get official builds sooner or later.
Click to expand...
Click to collapse
Oh, I'm sorry. I misstated. I mean, the "device" repo. (https://github.com/solk2/android_device_samsung_ks01lte/commits/cm-13.0)
zardak said:
Well, solk2 started to push changes on his kernel's repo days ago, even on cm-14.1 branch.
Anyway, I think is just a matter of time. We'll get official builds sooner or later.
I just don't understand why solk2, kyasu, and possibly gugu0das and others don't collaborate all together to only one kernel/device for this phone
Click to expand...
Click to collapse
It looks like a waste of time and work, doesn't it? There is no point in having 3 or more different builds with no particular differences. Devs might want to join the official repos instead and make their changes there.
zardak said:
It looks like a waste of time and work, doesn't it? There is no point in having 3 or more different builds with no particular differences. Devs might want to join the official repos instead and make their changes there.
Click to expand...
Click to collapse
You are absolutely right. I dont know, maybe they have reasons not to join the LineageOS team, but when I got my S4 I was rather confused with all this different versions. I mean for many devices you get unofficial builds with extra features/improvements, but for the I9506 its hard to tell the differences. However at the moment I would say the build by gugu0das is the best, but it looks like he is not going to update it anymore. So yes, it would be great to have all those talented developers out there working on the same repos.
PixelChris95 said:
So yes, it would be great to have all those talented developers out there working on the same repos.
Click to expand...
Click to collapse
I believe this is some sick "if you don't figure it out yourself, you're not supposed to know how to do it" attitude of some (most?) developers. Or another symptom of "not invented here" syndrome.
If LineageOS official builds are available I will surely not waste time to build it myself, but in the meantime I would like to be up-to-date. So still, anyone pointing me to information how to do it is very welcome.
zardak said:
Well, solk2 started to push changes on his kernel's repo days ago, even on cm-14.1 branch.
Anyway, I think is just a matter of time. We'll get official builds sooner or later.
I just don't understand why solk2, kyasu, and possibly gugu0das and others don't collaborate all together to only one kernel/device for this phone
Click to expand...
Click to collapse
I think the same of you. It could be better for all of us to make a ROM with the best of their ROMs.
JohnMcClane1htc said:
I think the same of you.
Click to expand...
Click to collapse
What do you think? That I do not share what I do? I have provided a ROM for i9506 based on cyanogenmod 11.0 for a long, long time, as well as one for Nexus 7. And I have always made clear from where the sources for those builds came. Perfect transparency, don't you think?
It is because of disrespectful people like you that developers (and people like me, because I am not a developer) stop sharing!
NeuDLi said:
What do you think? That I do not share what I do? I have provided a ROM for i9506 based on cyanogenmod 11.0 for a long, long time, as well as one for Nexus 7. And I have always made clear from where the sources for those builds came. Perfect transparency, don't you think?
It is because of disrespectful people like you that developers (and people like me, because I am not a developer) stop sharing!
Click to expand...
Click to collapse
If my comment has offended you, I apologize. My comment doesn't want to disparage anyone. And I recognize the effort of the developers because, although I am not, I know how difficult it must be to develop a ROM.
If my comment has offended you, I apologize. I am sorry.
I also create content in Htcmania and always share and show the sources. I only would want to say that sometimes, when finding so many ROMs based on CM, it can be difficult to decide for one or the other, since the changes between them are very subtle.
Regards
Maintaining/creating roms is usually the way people learn Linux, Android, compiling, git and such. That's why there are so many one-man projects. Once they are into it most vanish again/go over to other stuff though. Only few people keep over long time like Temasek. In the end there can't be enough roms. More options are always better than none. As long as people are posting the source code for other people to pick up they do work together already.
Hello,
I started making kernel builds again.
CHECK BELOW FOR IMPORTANT INFORMATION!
YOU MUST USE MIUI Q FIRMWARE PACKAGE FOR THIS KERNEL TO WORK. OTHERWISE YOU'LL END UP IN FASTBOOT MODE FOREVER.
Camera won't work on a lot of ROMs due to imcompatible camera drivers in the kernel. This kernel uses a patch for MIUI Stable 11.0.4 release, which introduced updated camera blobs back in Android Pie. Double check, whether your ROM uses these blobs. MIUI Q uses different blobs too, thus won't work until Xiaomi releases it's kernel source code.
FLASH THIS BEFORE FLASHING MY KERNEL. I UPLOADED FIRMWARE PACKAGE FOR YOUR CONVENIECE!
DOWNLOAD LINK FOR MIUI Q FIRMWARE PACKAGE
Flashing procedure is standard - through recovery. Magisk is optional, only if you want root.
*big thanks to rama982 for possible insights and some help from his side*
*nathanchance for android-linux stable and helping upstream our kernels*
*franciscofranco for commits that made our phone happier and snappier*
*sultanxda for his beastly development in Android scene and ridiculous understandment in kernels in general*
*also thanks to osm0sis for Anykernel3. Without this, flashing kernels would be a harder process to do*
XDA:DevDB Information
JellyKernelAlpha, Kernel for the Xiaomi Redmi Note 7
Contributors
airidosas252, rama982, nathanchance, Qualcomm, Code Aurora Forums, osm0sis, other developers
Source Code: https://github.com/airidosas252/Xiaomi_Kernel_OpenSource
Kernel Special Features: Stability, latest kernel sources
Version Information
Status: Testing
Created 2019-11-22
Last Updated 2020-02-01
DOWNLOAD LINK FOR GITHUB RELEASES
Due to different kernel base, older releases are irrelevant from now on.
UPDATE: I added a link for MIUI Q firmware package in the OP. Check it out and remember to flash it first before flashing my kernel. Thanks.
-------------------------------CHANGELOG------------------------------
Jelly Kernel Alpha 1.1.1 Hotfix
ALSA: pcm: Add missing copy ops check before clearing buffer (bootloop after voip videocall should be gone now)
-----------------------------------------------------------------------------------------
Jelly Kernel Alpha 1.1 beta release
IMPORTANT INFO! Camera won't work on a lot of ROMs due to imcompatible camera drivers in the kernel. This kernel uses a patch for MIUI Stable 11.0.4 release, which introduced updated camera blobs back in Android Pie. Double check, whether your ROM uses these blobs. MIUI Q uses different blobs, thus won't work until Xiaomi releases it's kernel source code.
If this kernel is not booting for you (going straight to fastboot mode), you need to use MIUI Q firmware package.
Changelog:
*Bringup for Clang 10 and it's now compiled with Clang 10
*Using LZ4 compression for zRAM
*Forcefully load modules (this should fix Wi-Fi problems on various ROMs)
*Rapid GC for F2FS filesystem
*Added fsync and crc check switches
*kgsl fixes and optimizations included
*Introduce additional NEON accelerated arm64 routines
*cfq io scheduler fixes and optimizations
*Tick rate increased to 300HZ for improved responsiveness
*CPU mask affinity set to 4 cores for improved efficiency
*Enabled F2FS filesystem support with encryption
*F2FS fixes
*Increased slmk's aggression rate to 192MB per app kill
*Enabled Dolby DS2 audio standard
*And more I don't really remember, check commit history for more detailed changes
-----------------------------------------------------------------------------------------
Jelly Kernel Alpha 1.0 beta release (don't use this release, it's deprecated)
*Complete rebase on jasmine's Q tag.
*Linux 4.4.211
*Adrenoboost enabled and set on low parameter
*Workqueques reworked for better responsiveness and lower power consumption
*Small UV for both CPU and GPU
*CPU Bitmasking
*DTB debloat (reduced kernel's footprint)
*LA.UM.8.2.r2-00600-sdm660.0 CAF tag
*Using older Wi-Fi CAF tag for better down/up speeds
And more stuff I don't remember.
-----------------------------------------------------------------------------------------
DISCLAIMER:
-There will be 1-3 kernel builds per week, unless there's nothing I can improve, then builds will be as is.
-Anyone, who has tested it already, give me some feedback in the comments.
-If you get freezes, crashes, restarts, write me up with a attached dmesg, log, anything, that can give me a clue what's wrong. Thanks. Happy JellyKernel'ing ^^
Where is the download link?
Zulwiczek1983 said:
Where is the download link?
Click to expand...
Click to collapse
Use the browser - there's a section DOWNLOADS above the thread. There you will find my kernel build. Cheers.
Zulwiczek1983 said:
Where is the download link?
Click to expand...
Click to collapse
Here, for short: https://forum.xda-developers.com/devdb/project/dl/?id=32079
NEW BUILD IS AVAILABLE NOW!
Check higher posts for download link. Happy flashing!
airidosas252 said:
NEW BUILD IS AVAILABLE NOW!
Check higher posts for download link. Happy flashing!
Click to expand...
Click to collapse
Does it support Kcal? Regards :good:
rubentkato77 said:
Does it support Kcal? Regards :good:
Click to expand...
Click to collapse
Yes it does. Look up using kernel manager.
airidosas252 said:
Yes it does. Look up using kernel manager.
Click to expand...
Click to collapse
Thnk you, will flash to test :good:
Is the any chance to get the turbo frequencies on the GPU?
I read that on some other page I can't remember where, can you please why that supposed frequency is not on the stock kernels, does it take to much energy?
tekkaman7 said:
I read that on some other page I can't remember where, can you please why that supposed frequency is not on the stock kernels, does it take to much energy?
Click to expand...
Click to collapse
I believe Qcom left off this frequency just because CPU is already close to some of their flagship SOCs in terms of CPU performance.
Everything in the source code is left done, you just need to modify a code a bit and you have higher frequency. If you want to go any higher, you would need to modify the code a lot more. Tried it and gave up on that.
It could be anything, really.
Moreover, you don't see too many phones using this exact SOC.
P.S. Funny thing though, this OC feels like placebo effect, like CPU is running faster but it's really not.
Think about it, when sdm660 came out, it was between SD821 and SD835 in terms of CPU performance. GPU is more or less the same as Adreno 430.
Gonna release new kernel build soon.
Still working out some quirks I come up every once in the while.
Stay tuned for news. Good day.
airidosas252 said:
Gonna release new kernel build soon.
Still working out some quirks I come up every once in the while.
Stay tuned for news. Good day.
Click to expand...
Click to collapse
Thanks for your work, we will waiting :good:
NEW KERNEL BUILD AVAILABLE NOW!
As usual, check main page for a download link. Happy flashing!
airidosas252 said:
NEW KERNEL BUILD AVAILABLE NOW!
As usual, check main page for a download link. Happy flashing!
Click to expand...
Click to collapse
thank you, downloading. :good:
Overclocked? Using Evira for now on MIUI 11 Pie, but Evira is outdated..... Can't support Android 10
So, hope can have Overclocked kernel support Android 10
xiaomi.lim said:
Overclocked? Using Evira for now on MIUI 11 Pie, but Evira is outdated..... Can't support Android 10
So, hope can have Overclocked kernel support Android 10
Click to expand...
Click to collapse
Yep, it's overclocked and it's for Android 10.
I've seen people running this with MIUI too.
airidosas252 said:
Yep, it's overclocked and it's for Android 10.
I've seen people running this with MIUI too.
Click to expand...
Click to collapse
Overclocked to ? 2.46GHz?
xiaomi.lim said:
Overclocked to ? 2.46GHz?
Click to expand...
Click to collapse
Yes, but I don't think I'll keep the OC for much longer. I really don't see the benefit of it.
Phone is already really fast and snappy.
I did a build with stock clocks and compared it to the OC one. And here's the surprise - there isn't almost any difference.
I fixed several known issues which bugged me a lot and those seem to remedy all of the problems I had.
Moreover, I hate overbloated kernels with features I don't use. I like being clean and compact.
Hi, the sound control (for speaker, earpiece and headphones) available or do you plan to add it in future? They get pretty handy really. I do appreciate keeping the kernel without much bloat though. : D