Preamble
Hey everyone!
Xiaomi JUST released their source on 17/5/17 for mm. THAT IS SO DAMN COOL, THE WAIT IS FINALLY OVER. You guys can expect a custom kernel from me sooner or later(i'm busy). However, if the custom kernel really comes out from me, it won't be on this thread. This thread will maintain active development though, repacks of other custom kernels!
What is a repack? A repack is essentially, in layman terms, porting a kernel. I can run a kernel for AEX on RRN and stuff like that, but please do take note that my repacks are tweaked towards battery life, while keeping some speed. I might add bonus scripts in future, but for now, i'm just trying to get this up and running.
Please flash at your own discretion. I try my best to test at every release, but sometimes i just don't have the time to do so. I have homework and revision and all,and i need sufficient sleep for growth(i'm 13) so just bear with me. I am NOT responsible for anything that happens with your device
Links
KernelsGit Repository
Source
- Stock MIUI Marshmallow Stable V8.2.5.0.MCFMIDL
- Stock MIUI Nougat Dev V7.5.19
Sauce released!
Requirements && Instructions
- TWRP
- Basic flashing skills
- A working human brain
- The will to void your warranty
Just flash the zip after flashing the rom. It'll do it's thing.
Features- Better battery life
- Snappier
- Runtime(Dalvik) optimisation
- Governor optimizations
- TCP tweaks
- 3G Tweaks
- Google DNS
- Faster internet
- Battery tweaks
- JIT as compiler
- Support both ipv4 && ipv6
- No ring delay
- Better voice quality
- GPU optimisation
- Faster boot
- 4 compile thread for dex2oat
- Better camera and image quality
- Purge assets(save battery)
- Logging and debugging disabled(save battery)
All these come from the tweaked ramdisks. All can be found on the git repo above.
Supported Roms- MIUI Marshmallow [V8.2.5.0.MCFMIDL]
- MIUI Nogat [V7.5.19]
- LineageOS 14.1
- Cypher OS V3.6.2
- AOSP Extended 4.2
- crDroidAndroid v3.1
- Android Ice Cold Project
- Xperia Open source Project(XSOP)
- DarkNess reDefined v1.5
- Resurrection Remix Nougat 5.8.3
More will be added based on requests and popularity
Credits
Jarius980 for teaching me how to do repacks and being cool
osm0sis for AIK
Lucas for being cool XDDD (Like the best tester and adviser ever)
CyanGreenMod for fixing the misplaced semicolon
Everyone who contributed/tested/supported
Notes
- WIpe dalvik cache and cache after flash, as dalvik's behavior and execution mode is changed
- Spot something wrong? Pull requests are always welcome!(just make sure you work on the latest upstream)
- Reporting bugs or failed boot are also contributions(VERY HELPFUL)
- Please attach log along with reports if possible
- Pre-release is available on git before release, go ahead and flash if you want
- Safetynet will still be intact since all modifications goes directly to the boot.img
- Thread is still under construction, it may look ugly for now
- NOT ALL THE RELEASES ARE STABLE, PLEASE DO A NAND BACKUP OF YOUR CURRENT BOOT
Thread rules
Do:
- You help one another
- You stay on-topic
- You READ and SEARCH
Don't:
- You do not demand
- You do not ask for ETAs
- You follow the RULES
Announcement:
Please report any issues with build #6
Changelog(please refer to git repo):
Build7:
Dalvik flags
Other tweaks and improvements
Base update
Firmware
Build6:
Update tweaks(dalvik and others)
Update base
Stabilisation
Clean dalvik cache && cache automatically
Build5:
Update tweaks(HUGE)
Fix setprop errors
Build4:
Hopefully fix all wifi issues
Update nogat base
Applied some tweaks
Build #3:
Support new roms (ACIP, RRN5.8.3, XSOP)
Wifi issues fixed for AEX
Build #2:
Fix wifi for some
Stabilisation checks
Build #1:
Compatibility build, so NA
Todo:
Take a huge break because of exams
Create build scripts(in meantime, manual is the only way out)
Dev Log:
[6/5/17]
-I'm too lazy to type it all out, just view my commits on git
[3/5/17]
- Added ACIP, RRN5.8.3, XSOP
- Update AEX Base
- Fix all wifi issues
(More detailed log look at git commits)
[1/5/17]
- Fix wifi for some
[30/4/17]
- Prerelease Build #1
- Complete compatibility checks
- Wrote update script
- Initialised git repo
- Added source unpacked boot files(ramdisk && split_img)
- Setup base and dependencies
Potential feature and support requests:
Known issues:
- Cast screen(Not kernel related unless explicitly proven)
FAQ:
How to NOT break safetynet?
- Just flash the build after the flashing the rom. You can flash mods like magisk and systemless supersu that does not modify /system
Why did i lose my root after flashing(SuperSU)?
- Because supersu patches boot.img and adds a script to start the SU daemon. Flashing a new boot.img will cause the script and patches to be overridden. Just flash the supersu zip again and everything will be reapplied
What can i report?
- After testing a build for a specific rom, you can state the rom your device is on, how old your device is, then the thing you wanna report. You can report failed boots, function bugs and SOT(battery)
Useful Links:
- Telegram Group Chat
https://t.me/joinchat/AAAAAEHQRgRmzU2eCxWK8w
- Whatsapp Group Chat
https://chat.whatsapp.com/7morKcwxExyAcc2deOoYu0
- Discord
https://discord.gg/HS8Ku
- Twrp 3.1.0-0
http://tinyurl.com/midotwrp
- Firmware
https://www.androidfilehost.com/?fid=817550096634766008
- LineageOS addons download
https://download.lineageos.org/extras
- OpenGapps
http://opengapps.org/
-BeanGapps
http://tinyurl.com/beangapps
Wanna donate?
I have to ask my mom again if she allows me to have her paypal donation link. But for now, i guess not
Got any examples of what can be added in? I assume it's mostly ramdisk related since the zImage can't be modified.
AutumQueen92 said:
Got any examples of what can be added in? I assume it's mostly ramdisk related since the zImage can't be modified.
Click to expand...
Click to collapse
yesh. and the ramdisk will be tweaked accordingly
like i can optimise governor values and stuff. the real development will start once sauce gets release(SAUCEEEEEE)
Edit: actually, ill just add this in OP
ala_mo said:
yesh. and the ramdisk will be tweaked accordingly
like i can optimise governor values and stuff. the real development will start once sauce gets release(SAUCEEEEEE)
Edit: actually, ill just add this in OP
Click to expand...
Click to collapse
Welp, is there any way to obtain the voltage values per frequency from there (Reading the values, not changing it)? I wanna read it and make a governor tweak.
AutumQueen92 said:
Welp, is there any way to obtain the voltage values per frequency from there (Reading the values, not changing it)? I wanna read it and make a governor tweak.
Click to expand...
Click to collapse
f im not wrong voltages are inside the kernel source, no way to change that if the kernel does not support it(its not by default)
Governor tweaks can be made. Values are found in init.qcom.rc
Whats rom this working?
Molniya said:
Whats rom this working?
Click to expand...
Click to collapse
Added in OP. I dont't want the first builds to fail, i need to go for class now. Will test myself tonight before release
Does it work on miui 8.2.2.0??
Prem2628 said:
Does it work on miui 8.2.2.0??
Click to expand...
Click to collapse
Miui MM is supported. will upload a build for this tonight.(10more hours) i will have to test before releasing since its the first build
Maybe this kernel will activate technology quick charge by Qualcomm? *Hopefully and I'll migration from Kenzo to Mido ?
Sent from my Redmi Note 3 using XDA Labs
NOS_bzone said:
Maybe this kernel will activate technology quick charge by Qualcomm? *Hopefully and I'll migration from Kenzo to Mido ?
Click to expand...
Click to collapse
QC requires kernel-side changes
AutumQueen92 said:
QC requires kernel-side changes
Click to expand...
Click to collapse
yeah...alot of stuff comes packaged if the kernel supports it(qc, voltage, more governers) but currently, the kernels from xiaomi are not meant for any customization, thus what i can do is to tweak whats currently in store. I cannot add features to the kernel now. I can only tweak the available features The real development starts when the sauce gets released
ala_mo said:
yeah...alot of stuff comes packaged if the kernel supports it(qc, voltage, more governers) but currently, the kernels from xiaomi are not meant for any customization, thus what i can do is to tweak whats currently in store. I cannot add features to the kernel now. I can only tweak the available features The real development starts when the sauce gets released
Click to expand...
Click to collapse
Heh, even with the kernel source I still can't add QC into my Xperia. It's a good thing the Note 4 has more devs. Also, are you experienced in kernel building?
The Carbon Rom that popped up last night listed Mido kernel sources, which I'm highly sceptical if it works. I just need someone to confirm since the OP isn't responding.
AutumQueen92 said:
Heh, even with the kernel source I still can't add QC into my Xperia. It's a good thing the Note 4 has more devs. Also, are you experienced in kernel building?
The Carbon Rom that popped up last night listed Mido kernel sources, which I'm highly sceptical if it works. I just need someone to confirm since the OP isn't responding.
Click to expand...
Click to collapse
from what i know, i suspect it's a partial source. That means that its not full, and there will be some limits
Pertaining to your first question, i can and will build kernels, but i will only do so in December, because my school projects require windows and linux would me more ideal compared to bash on win(always get that dpkg error)
where is the download link? oh, this is just pre-release?
Justin Timberlake said:
where is the download link? oh, this is just pre-release?
Click to expand...
Click to collapse
READ
ala_mo said:
from what i know, i suspect it's a partial source. That means that its not full, and there will be some limits
Pertaining to your first question, i can and will build kernels, but i will only do so in December, because my school projects require windows and linux would me more ideal compared to bash on win(always get that dpkg error)
Click to expand...
Click to collapse
Yeah, linux on windows is a pain. I ended up dual booting with Ubuntu and W10 too.
Related
༼ つ ◕_◕ ༽つIn the name of our great lord Helix!༼ つ ◕_◕ ༽つ
Welcome to the first custom CM12 kernel for the Z3 Compact
Kernel12
We're going on an adventure!
AMAZING FEATURES:
They happen to change so often that you're better off checking the changelog, but if you're stubborn, here's the core ones:
Additional CPU and GPU steps
Faux123's Intelli_plug and Intelli_thermal
adreno_idler
Memory fixes up the arse
Countless battery life and overall performance optimizations
A reason for Myself5 to, as he says, compete
Custom installer that combines both the permissive and enforcing image in one tiny zip
Obviously there's more so go ahead and check my Github!
DOWNLOADS:
http://j.mp/kernel12-1
Generously hosted by Androidfilehost.com
Note that the newest old (stable or not) builds (CM 12.0) are still available on the original site for now: http://bit.ly/kernel12
HOW-TO:
* Use TWRP
* Flash zip
* Read what the zip tells you
SERIOUS DISCLAIMER!
Code:
I guarantee nothing except for squids taking over our planet by the year 3027. #squidmasterrace
I'd also like to point out that the kernel developers for this device are different people with different lives, schedules and priorities, which shows in many differences in their work. We are not enemies or competitors but rather friends and colleagues, but we each support what we do as we are able to and as we deem is best.
Kernel sources: https://github.com/someone755/android_kernel_sony_msm8974 (cm12.x)
https://github.com/someone755/android_kernel_sony_msm8974-1 (cm14/lineageos 14)
༼ つ ◕_◕ ༽つPRAISE HELIX༼ つ ◕_◕ ༽つ
XDA:DevDB Information
Kernel12, Kernel for the Sony Xperia Z3 Compact
Contributors
someone755
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: r_12
Stable Release Date: 2017-10-30
Created 2015-02-22
Last Updated 2017-10-30
A quick FAQ that you'd better read before posting.
1. What was up with the nonsense naming scheme before 12.1?
A: Back then I believed people would actually test the unstable builds I pushed out very often, but I found out only a minority did so. With 12.1, I've decided to turn a new leaf and try to merge the two -- the builds won't be as extensively tested as the stable ones were before, but they will be released faster.
For now, all you need to know is that rperm means permissive and renf means enforcing builds.
2. How do I flash this?
A: Flash through recovery and read what the recovery tells you.
3. My bootloader is locked, HALP! OR I'm on stock/AOSP/CM7.
A: Then you don't get to install this kernel. Pretty simple but still, tough luck.
4.. What app do you recommend for dealing with CPU settings?
A: TricksterMod and Kernel Auditor work for me. Go around the internet, try different apps and see what works for you, then keep it.
5. Touch Control doesn't work in rXXX release, you suckas, fix plixe! OR My phone exploded, HALP!
A: Go away. I do not respond to bug reports without a proper description and log.
6. I have a bug to report!
A: Great! Unlike the guy in #5, you may submit the error either to DevDB or in the thread (just tag me if you're posting into the thread). Make sure your description of the error is detailed, and that you have a log (located in /proc/last_kmsg). It'd be best to upload the log via pastie.org If possible, please also list the way in which the error was triggered.
7. I want to support you and your work!
A: Awesome! Click thanks and/or share the thread with other guinea pigs who would like to participate!
8. OP is arrogant, I'm gonna call the Internet Police? OR Why are you such a derp and asshole
A: Indeed I am. Deal with it.
9. Where may I find the discussion thread?
A: This thread serves as both the development and discussion thread. Please to not litter (GTFO with "thanks" and "+1" posts), and try to keep to the topic. That said, if you're reporting a bug or requesting a new feature, you may use either DevDB or the thread, but please tag me should you opt for the latter. Just remember, reviews go in the "Reviews" tab!
Special shoutouts to (in no particular order, all help is equal help):
AndroPlus
funiewski
Myself5
sm4tik
nelvinchi
franciscofranco
Freexperia and jerpelea
faux123
Google, Sony and HTC
All Nozomi developers!
EXTREME CHANGELOG:
Releases since r_08: http://bit.ly/changelog12-1 (Nougat/Android 7.0)
Releases r_05 to r_07: http://bit.ly/changelog12 (Lollipop/Android 5.x)
Releases pre-r_05:
Code:
for a more detailed changelog, check my GitHub (although you're probably better off not doing that)
for STABLE BUILDS
[*] r_05 ### 16/8/2015 ***UPDATE***
-merge upstream CM commits (more WiFi commits)
-enable adreno_idler to reduce GPU frequency spikes
-even more fixes to the installer
[*] r_04 ### 30/7/2015 ***UPDATE***
-enable screen color control
-downgrade powersuspend to a version that Kernel Adiutor supports
-more memory tweaks
-fix a bug that caused the CPU to spike after thermal throttling kicked in
-enable a 2.5 GHz CPU step
-introduce some fixes to the new installer (code is _still_ dirty -- I'll be working on it)
[*] r_03 ### 29/7/2015 ***UPDATE***
-enable F2FS
-fix the 268 MHz and 2419 MHz steps and allow voltage control
-use the already-existing ramdisk instead of using our own
-merge the permissive and enforcing image into a single zip -- let the user choose what to do on install
[*] r_02 ### 18/7/2015 ***UPDATE***
-merge upstream CM commits (wifi updates)
-upgrade intelli_plug to 4.0
-improve GPU driver and allow apps to use more RAM
-introduce 268 MHz and 2419 MHz CPU frequencies
-disable mpdecision and enable intelli_plug in its place
-enable intelli_thermal by default, set throttling point to ~80°C and poll time to 3 seconds
[*] r_01 ### 18/7/2015 ***UPDATE***
-merge upstream CM commits, update the whole thing to better work with lp-mr1
-downgrade intelli_plug to 3.9 as 4.0 was causing issues -- future TODO!
-bring kexec support to stable builds (multirom is finally supported)
-move to a new download host (androidfilehost)
-go back to CM ramdisk
[*] O3 ### 15/4/2015 ***UPDATE***
-update intelli_plug
-disable Qualcomm's MP-Decision and enable intelli_plug by default
-merged CM upstream commits (including a LOT of wifi fixes)
-power (powersuspend) and fs tweaks
[*] O2 ### 12/3/2015 ***UPDATE***
-Motorola memutils
-upstream CM commits
-faux123's snake charmer
-intelliactive CPU governor
-kexec_hardboot
-removed recovery from the ramdisk; we're using the FOTA partition as recovery, and we save 3MB on size
[*] O1b ### 10/3/2015 ***UPDATE***
-LZ4 kernel compression
O1b ### 7/3/2015 ***UPDATE***
-upstream CM commits
-asynchronous file sync (reduces IO latency by as much as 34%)
-screen color calibration (KCAL)
[*] O1 ### 25/2/2015 ***UPDATE***
-GPU OC to 657 MHz, added 100 MHz step
-GPU idle set to 27 MHz
-KSM
-FSYNC
-intelli_plug
-intelli_thermal
-voltage control
I hope you like the colors.
Sorry for having 3 OPs, but I'd rather have more than 1 long one.
First off, thank you so much! There's been a massive lack of kernels for our device. Now for my real question, is there any chance you could make a Selinux Permissive variant so we can get xposed working? I'm only asking because you seem to be the only one with a CM12 kernel out :good:
EDIT: Never saw the tabs for feature requests in a thread before, so this should probably go there, my mistake.
C2fifield said:
First off, thank you so much! There's been a massive lack of kernels for our device. Now for my second question, is there any chance you could make a Selinux Permissive variant so we can get xposed working? I'm only asking because you seem to be the only one with a CM12 kernel out :good:
Click to expand...
Click to collapse
Hello yes I would like to science please.
I'll see what I can do, the layout of a boot image has changed drastically since 2012. xD
EDIT: @C2fifield: No biggie, I don't mind feature requests in the thread. To be honest I don't mind anything as long as it's about this kernel/thread.
EDIT2: I've spent two hours trying to set SELinux to Permissive. What I managed to create were a handful of ramdisks that were supposed to change it to permissive (but didn't) and a zImage that completely disables SELinux.
If anyone knows what in the world I have to do for permissive, please let me know. So far everything I've found on the internet about this is how to type "setenforce 0" in a su shell.
EDIT3: I am an idiot. Continue with your lives, the Permissive image will be up in a few minutes.
C2fifield said:
First off, thank you so much! There's been a massive lack of kernels for our device. Now for my real question, is there any chance you could make a Selinux Permissive variant so we can get xposed working? I'm only asking because you seem to be the only one with a CM12 kernel out :good:
EDIT: Never saw the tabs for feature requests in a thread before, so this should probably go there, my mistake.
Click to expand...
Click to collapse
You can use this method.
http://forum.xda-developers.com/showpost.php?p=58887725&postcount=230
was12 said:
You can use this method.
http://forum.xda-developers.com/showpost.php?p=58887725&postcount=230
Click to expand...
Click to collapse
It's alright, I already figured it out. What C2 wanted, if I understood correctly, was for init and onwards to be permissive. If I read that correctly, your proposal only turns SELinux into permissive on Android boot.
I don't know if this makes sense and it may or not be wrong.
EDIT: Also tried your suggested way, didn't work for me.
someone755 said:
It's alright, I already figured it out. What C2 wanted, if I understood correctly, was for init and onwards to be permissive. If I read that correctly, your proposal only turns SELinux into permissive on Android boot.
I don't know if this makes sense and it may or not be wrong.
EDIT: Also tried your suggested way, didn't work for me.
Click to expand...
Click to collapse
Try this. Create su.d folder in /system/ and create a text file that permissive.sh and insert code in permissive.sh and give permissions 755 to both folder and file.
Code:
#!/system/bin/sh
setenforce 0
He wanted to get xposed working. This way makes system permissive on boot and lets xposed framework working properly. This way works for him.
And also thanks for your kernel. Do you consider adding more features to your kernel such as OC,KSM,etc. ??
was12 said:
Try this. Create su.d folder in /system/ and create a text file that permissive.sh and insert code in permissive.sh and give permissions 755 to both folder and file.
Code:
#!/system/bin/sh
setenforce 0
He wanted to get xposed working. This way makes system permissive on boot and lets xposed framework working properly. This way works for him.
And also thanks for your kernel. Do you consider adding more features to your kernel such as OC,KSM,etc. ??
Click to expand...
Click to collapse
That sounds more like it! Still though, I've found it's only one line when putting the boot.img together:
Code:
androidboot.selinux=permissive
Ofc I intend to add more, you didn't think I'd open a thread for just two cherry picks? xD
Looking into a lot of things, my GitHub isn't even half of what I decide to push. KSM is literally just one push of a button in the config, and I just need to cherry-pick others and get them to work (the latter is really where most of the work is at, there's a lot of trial and error).
@someone755 thanks for your kernel!
As the script method with permissive.sh causes some serious issues with dialer and settings (FC) on my device (CM12 02/22) and this is only a not so clean workaround it would be very nice of you if you could consider a permissive variant of your kernel. Thanks in advance!
Zwulf said:
@someone755 thanks for your kernel!
As the script method with permissive.sh causes some serious issues with dialer and settings (FC) on my device (CM12 02/22) and this is only a not so clean workaround it would be very nice of you if you could consider a permissive variant of your kernel. Thanks in advance!
Click to expand...
Click to collapse
Have you tried version ZX1? It works for me but YMMV (which is also why I'm still labeling everything as beta).
someone755 said:
Have you tried version ZX1? It works for me but YMMV (which is also why I'm still labeling everything as beta).
Click to expand...
Click to collapse
Permissive! Gr8, thanks a lot!
someone755 said:
Hello yes I would like to science please.
I'll see what I can do, the layout of a boot image has changed drastically since 2012. xD
EDIT: @C2fifield: No biggie, I don't mind feature requests in the thread. To be honest I don't mind anything as long as it's about this kernel/thread.
EDIT2: I've spent two hours trying to set SELinux to Permissive. What I managed to create were a handful of ramdisks that were supposed to change it to permissive (but didn't) and a zImage that completely disables SELinux.
If anyone knows what in the world I have to do for permissive, please let me know. So far everything I've found on the internet about this is how to type "setenforce 0" in a su shell.
EDIT3: I am an idiot. Continue with your lives, the Permissive image will be up in a few minutes.
Click to expand...
Click to collapse
Thanks so much! I've been hoping for a permissive LP kernel for our device!
@someone755
Oh, I agree that was a fool question
Ok now, I'm waiting your next works. I hope you to add new features and create a good kernel for our device.
Maybe this is a stupid question but what kernel is this based on? The unified kernel? Or is it built from scratch?
@someone755 thx for your work. How about kexec? I know there is no multi rom for z3c yet but maybe it will come soon.
smorgar said:
Maybe this is a stupid question but what kernel is this based on? The unified kernel? Or is it built from scratch?
Click to expand...
Click to collapse
What do you mean, from scratch? o.o
It's based off the CM msm8974 repo's cm-12.0 branch. The branch unifies all Sony msm8974 devices' CM12 kernels, so I guess it's kinda unified.
funiewski said:
someone755 thx for your work. How about kexec? I know there is no multi rom for z3c yet but maybe it will come soon.
Click to expand...
Click to collapse
I'll worry about MultiROM when it gets here. Of course, if it gets here.
someone755 said:
What do you mean, from scratch? o.o
It's based off the CM msm8974 repo's cm-12.0 branch. The branch unifies all Sony msm8974 devices' CM12 kernels, so I guess it's kinda unified.
Click to expand...
Click to collapse
That answers my question perfecly. The 1:st post does not say wich kernel its based on so i just wanted to make sure
Edit: By "from scratch" i ment if you built it on your own based on nothing. It could be the case sinse you dont state wich/what kernel you based your kernel on.
smorgar said:
That answers my question perfecly. The 1:st post does not say wich kernel its based on so i just wanted to make sure
Edit: By "from scratch" i ment if you built it on your own based on nothing. It could be the case sinse you dont state wich/what kernel you based your kernel on.
Click to expand...
Click to collapse
But ... you have the sources right there... Says "forked from Cyanogenmod/android_kernel_sony_msm8974".
There really is only one source I could build something that boots into a CyanogenMod ROM, and it's from CyanogenMod sources.
I still don't understand what you mean by "from scratch" -- starting from either the base Linux kernel or the stock Sony ones is madness.
someone755 said:
But ... you have the sources right there... Says "forked from Cyanogenmod/android_kernel_sony_msm8974".
There really is only one source I could build something that boots into a CyanogenMod ROM, and it's from CyanogenMod sources.
I still don't understand what you mean by "from scratch" -- starting from either the base Linux kernel or the stock Sony ones is madness.
Click to expand...
Click to collapse
Sorry to confuse you. Maybe i did not read the post as i should have... My bad.
My thaught was like you say: madness to build from linux kernel or stock sony but i had to ask to be sure what this was since i did not read the post well enough as it seems
Gonna try this kernel ASAP. Thank you and keep up the work!
Hi all,
this is the thread about the CM version of the well-known Boeffla-Kernel for the Samsung Galaxy S3 lte.
Note: This kernel is only for CM based roms!!! Do not install it on a Samsung based rom!!!
For Omnirom, please do not use the CM kernel but the separate Omnirom kernel I also provide.
If you have questions to settings, presets, others configuration and wanna share your configuration, head over to the unofficial Boeffla-Config App Config sharing thread:
http://forum.xda-developers.com/showthread.php?t=2621308
Support
First read about "Known Issues" in 2nd post!
FirstSecondly read the FAQ section on the Homepage !!!
Click here to learn about all possible kernel settings in the config app.
Click here to learn about using the config app.
I will refuse any support if you do any undervolting and experience freezes or hot reboots.
I will refuse to give support if you have xposed framework installed and reporting any kind of weird issues. My opinion to xposed it quite clear: too powerful for >90% of the users that just mess up their system with it. Test w/o Xposed first, if issue still occurs then report here. If issue doesn't occur anymore, also report here so I can list under "Xposed known issues"
Lastly, if you are using one of the latest versions with anykernel, please read this before proceeding
Lord Boeffla said:
Hi all,
it is time for the first CM13 kernel with the new anykernel concept.
Before you start, make sure you have read and understood the following:
http://boeffla-kernel.de/index.php/7...new-anykernels
If you ask questions which are addressed in this article, or you have issues which are a consequence of not reading the article, I will not answer. It is your responsibility to understand what you do BEFORE you do it.
(and also read this for more background: http://boeffla-kernel.de/index.php/6...ernels-new-app)
Side note:
Although the kernel is now likely to be much more compatible with custom roms using CM basis, I will not change my support conditions at all. If you report an issue on a non-original CM rom, do not expect me to react (http://boeffla.de/index.php/support/support)
Ensure you update to latest Boeffla-Config App 2.3.1 BEFORE you flash the new kernel !!!
Enough threatening now, here we go:
Version 5.1-beta1
12.07.2016
Note: This is the first Boeffla-Kernel with the new anykernel concept.
Make sure you read and understand the basics: Boeffla-Anykernel Know-How and New concept kernels/New app
Note: You have to use Boeffla-Config version 2.3.1 or newer in order to use all functionality !!
This kernel as exactly the same functionalities as the last stable kernel release
Enjoy
Andi
Click to expand...
Click to collapse
Change logs
(you can also access them directly in Boeffla-Config V2 by pressing menu and selecting "change log...")
Features
* To tweak and configure the kernel, manually load and install the app "Boeffla-Config V2" from here: DOWNLOAD
* Support for generic framework naming convention framework-2.jar instead of proprietary rom framework names
* Upstreamed to Linux 3.0.101(www.kernel.org)
* CPU "soft" overclocking to 1500 or 1600 MHz
* CPU undervolting interface
* GPU frequencies configurable (underclocking, overclocking up to 700 MHz)
* GPU voltages configurable (undervolting, overvolting)
* Configurable zRam
* Configurable touch-to-wake
* Configurable touch boost frequency
* Configurable early suspend time (for screen off animations, 100ms default)
* Configurable LED for fading mode, speed and brightness
* Softkey touch button LEDs controllable
* Configurable charger rate for AC, USB and wireless (default increased to 1100 mA for ac charging)
* Charge information display support via Boeffla-Config V2 app
* Charging logic supports ignore unstable power and remove safety margin
* Boeffla-Sound engine V1.7.1 to unleash the power of the Galaxy S3 audio chip
* Additional governors: zzmoove 0.8, pegasusqplus, smartassv2 and lulzactiveq
* Governor profiles for pegasusq, pegasusqplus and zzmoove for performance, battery saving etc.
* Additional schedulers: ROW, ZEN, BFQ (v6r2) and SIO
* Schedulers configurable separate for internal and external SD memory
* Hardcore speedmod sharpness fix implemented (default is off)
* Black crush fix for better balanced display
* SD card read ahead buffer configurable separate for internal and external SD memory (default increased to 256 kB)
* Ext4 File system tweaks (default to on, can be disabled)
* System Tweaks predefined supported (default is off, new Mattiadj tweak set included)
* WIFI Multicast filter for better battery life
* WIFI wakelock times reduction
* Proportional rate reduction for TCP
* TCP congestion changed from Cubic to Westwood
* Wifi mac address change support
* Dynamic fsync 1.2 implemented
* Timeout for external SD card changed to improve handling of crappy SD cards
* Swap supported (but not recommended, use zRam instead)
* init.d support (in /system/etc/init.d - set correct permissions!)
* NTFS (read-only access only!) compiled as a module
* CIFS compiled as a module
* NFS compiled as a module
* XBox controller support as module
* exFat support (if supported by used firmware)
* Battery monitor wakelocks reduced
* Android logger can be disabled
* Disabled various debug logs and traces
* Frandom compiled as a module (for mods like Crossbreeder)
* Triangle away supported
* Automatic EFS backup to external (priority) or internal SD Card (fallback) - now compatible with tools like kTool
* Kernel initialisation log file (with history of 3 log files)
* Emergency reset script automatically placed into /boeffla-kernel-data folder of your internal memory
* Compatibility to common standard apps (Voltage Control, SetCPU, System tuner etc.)
* Compiled with Google arm 4.8 toolchain
* Internal kernel busybox version 1.24.2
Download
For all information and downloads (stable AND testing versions), visit the Boeffla-Kernel homepage:
www.boeffla.de
Downloads over at my AFH Folder
History
Basically I created the Samsung version of Boeffla-Kernel as there was no kernel for the Samsung Galaxy S3 around that had exactly the mix of functionalities that I wanted. I wanted to have full flexibility in undervolting and charge rates for instance, but did not like the sharpness and/or brightness tweaks many kernels have implemented as per default.
Hence, I began to create my own kernel after a while, adding all the features I like. This is the result of my work, which in the end I decided to share with you. I hope you like it as much as I do.
The objective of this kernel is to have a kernel for daily use. It does not aim for best battery life, or best smoothness or best benchmark scores. It aims more for a good mix of all, not sacrificing stability and functionality in the end.
And - most important: It aims to stay quite close to stock !!! Which in fact for the CM kernel means now... close to CM kernel sources.
This said, I will definitely NEVER implement:
dual boot (I do not need it)
color "calibration"
real hard overclocking higher than 1600 MHz as this is outside of Exynos specs
f2fs - it is known to cause various issues and compatibility problems
a CAF based kernel
[*] anykernel method to use the ramdisk of the installed rom
anything that requires upstreaming of kernel parts to a higher kernel major version
Any TC other than google's
So do not even ask for it. Everything else I am happy to check and decide.
Compatibility
To reiterate it again: This kernel is only for CM13 based ROMs. It is not designed to run on Samsung based roms! AOSP based is not tested, though it should work.
Configuration of the kernel
To tweak and configure the kernel, manually load and install the app "Boeffla-Config V2" from the downloads section on www.boeffla.de.
Donation
If you like my work, feel free to donate: Donation-Link
You will receive a personal donation code which unlocks some nice comfort functions in Boeffla-Config V2 on top.
Source code
All sources can be found in my Lord Boeffla's Github repository: http://github.com/andip71
My source can be found below, at "DevDB Information"
Credits to developers
Of course, I had never been able to create all that by my own. So I want to give credits to the really good developers around, that have given me all the inspiration and from which I cherry picked lots of the implemented functionalities:
* Lord Boeffla (For providing kernel in the first place )
* Yank555
* ZaneZam
* Hardcore
* Chainfire
* Harunjo
* AndreiLux
* Netarchy
* Gokhanmoral
* Simone201
* Supercurio
* Mialwe
* Entropy512
* Faux
... I just hope I did not forget someone. If so, please let me know and I will add you of course.
Thanks to all of you for your great work !!!
Disclaimer
*** As always - Flash on our own risk! ***
Make sure you flash the correct version depending on your firmware version!
I can and will not take any responsibility for bricked phones or lost data.
It is generally recommended to run a complete Nandroid backup in TWRP recovery and safely store your personal data before you flash a new kernel.
Cheers and enjoy
Andi
XDA:DevDB Information
Boeffla Kernel, Kernel for the Samsung Galaxy S III I9300
Contributors
limjh16, n0aaz, aaz03, ZaneZam, Lord Boeffla
Source Code: https://github.com/limjh16/boeffla
Kernel Special Features:
Version Information
Status: Beta
Current Stable Version: 5.0
Stable Release Date: 2016-07-04
Current Beta Version: 5.1-b7
Beta Release Date: 2016-08-30
Created 2016-06-09
Last Updated 2016-08-30
Known Issues
Known Issues NOT involving Xposed
1. SuperSU and Superuser other than Stock DOES NOT WORK on Temasek ROM and possibly all other CM13 ROMs
2. F2FS WILL NOT WORK, AND WILL NOT EVER WORK, AS DESCRIBED IN OP
Known Issues involving Xposed
None I have experienced thus far.
To-Do List
1. Fix SuperSU because I really love it.
2. Archi Optimisations Test Doesn't work
3. Make file names correspond to "beta" tag
1. Attempt bug fixing Archi Opti Test
1. Test on AOSP ROMs
2. Dragon TC??
Installation
Dirty flash works fine, just remember to clear cache.
If you are coming from another kernel e.g. agni kernel, you must wipe /system (not just flash ROM zip for the updater script) and flash everything accordingly.
If you need specifics on what to do first, follow ROM installation instructions and right after you flash ROM zip just flash boeffla ZIP
If you still don't understand you should not be here and should be reading up on what flashing zip is...
Credits & a History Lesson
Credits other than those listed in OP:
1. @Lord Boeffla for allowing me to port, and post this thread.
2. @ZaneZam for guidance
3. @aaz03 YES I DID IT
I take absolutely no credit, all work was done by @aaz03 and all I did was follow his instructions and pester @ZaneZam a bit, and I got a flashable zip that works.
A very, very unimportant history lesson
So, I was looking at github.com/n0aaz and I saw he was trying to port boeffla. I PM'ed aaz, and he told me his laptop broke so he couldn't continue. He then asked me to help him continue and that he was very close to completion. However he rarely responds to PM, so I contacted @ZaneZam to ask for more guidance. He was very helpful and kind of guided me through how I should use the build script/edit the build script, and how to manage the boot.img
Well, @aaz03 you were very very close to completion indeed, you just had to take a new boot.img from CM. Uber toolchain was probably another factor.
Boeffla 5.0beta34 will be built this weekend or when I have time.
I will not be providing new Boeffla Builds where the changes do not concern i9305 (eg, just source updates for other devices) I will only be providing when there are universal updates.
Feel free to post bug reports here instead of the bug reports tab (I don't even recall if I enabled that tab)
If you want screenies tell me, I got stuff to do for now
Can someone help test with other ROMs and especially AOSP ROMs?
limjh16 said:
Credits other than those listed in OP:
1. @Lord Boeffla for allowing me to port, and post this thread.
2. @ZaneZam for guidance
3. @aaz03 YES I DID IT
I take absolutely no credit, all work was done by @aaz03 and all I did was follow his instructions and pester @ZaneZam a bit, and I got a flashable zip that works.
A very, very unimportant history lesson
So, I was looking at github.com/n0aaz and I saw he was trying to port boeffla. I PM'ed aaz, and he told me his laptop broke so he couldn't continue. He then asked me to help him continue and that he was very close to completion. However he rarely responds to PM, so I contacted @ZaneZam to ask for more guidance. He was very helpful and kind of guided me through how I should use the build script/edit the build script, and how to manage the boot.img
Well, @aaz03 you were very very close to completion indeed, you just had to take a new boot.img from CM. Uber toolchain was probably another factor.
Click to expand...
Click to collapse
Heh, very good job i couldn't be very active on xda because of all my exams. Even though i don't have a 9305 anymore i'm glad that you managed to fix issues i had to face . Good continuation
aaz03 said:
Heh, very good job i couldn't be very active on xda because of all my exams. Even though i don't have a 9305 anymore i'm glad that you managed to fix issues i had to face . Good continuation
Click to expand...
Click to collapse
See that you got yourself a redmi note 3 pro... wanted to get that too except i realised I rather save up for a Nexus
P.S. don't quote OP, I got this thread subscribed
limjh16 said:
...
Also, (a little advertising) what is the behavior of button backlight in boeffla?
Click to expand...
Click to collapse
Your advertising worked fine
I didn't know you've just started a Boeffla thread! Well done! Thanks for your work.
My answer to "what is the behavior of button backlight in boeffla?" is: I don't know, I didn't test.
FLooDW said:
Your advertising worked fine
I didn't know you've just started a Boeffla thread! Well done! Thanks for your work.
My answer to "what is the behavior of button backlight in boeffla?" is: I don't know, I didn't test.
Click to expand...
Click to collapse
Oh haha
Just felt lonely here.
I'm sorry if I was breaching any xda rules haha
Sent from my GT-I9305 using XDA Labs
Had time after dinner, here's beta34: https://www.androidfilehost.com/?fid=24572369242686106
Accessible via folder link in 1st post too. Now I bother to change zip names so it will be beta34 instead of alpha1 haha...
Anyways, as I was playing around trying to find a fix for supersu, I made backups and flashed while taking a log. Well, after I booted to system and prepared adb for a log, it booted, and surprisingly no bootloops! And it's a wierd solution that I found: Don't charge phone while booting. I attempted this 2 times, and the 2nd time it worked because I was not charging phone. Wierd? I know right...!
Great to see that development is still strong after all those years. Congrats on getting it all done and thanks to all your work you did the last few weeks/months.
Whats your problem whit f2fs?
The original boeffa support it.
Its really good future and really improve the performance.
F2FS has noting todo with the mentioned optimizations. Both can survive next to each other .
---------- Post added at 07:34 PM ---------- Previous post was at 07:12 PM ----------
Which kernel or sound app are you using or recommend to configure the beoffla sound settings? Can you link it?
Its already linked in op, sorry.
Running this on CM13 (pan's build, set to Muppett's RIL).
All seems to be working OK so far.
I'm using the Boeffla Control App V2 linked to in the OP. This has Boeffla sound settings in it, all seems to be working fine.
Now I just have to wait and see if the network issues I get when I use AGNi kernel on CM13 (but not CM own kernel) stay away.
Sorry haven't seen it in op. I am a newbie and didn't read the op proper .
Small issue - I set the charging current to 1500mA and turned on ignore unstable charging etc.
When I do this on AGNi, the 'Galaxy Charging Current' app says 1500 for 'reference', 'maximum' and 'average'.
On Boeffla it says 1500 for 'reference' but only 1000 for the other two numbers.
I had a bootloop when try boefla kernel with cyanide latest version.
So I try it with temasek and everything's working fine here, will test to see if the ril problem is fixed. Good work ! Thanks for bringing back this awesome kernel.
Mrxyzl said:
I had a bootloop when try boefla kernel with cyanide latest version.
So I try it with temasek and everything's working fine here, will test to see if the ril problem is fixed. Good work ! Thanks for bringing back this awesome kernel.
Click to expand...
Click to collapse
Seems like doesn't work with aosp.
Sent from my GT-I9305 using XDA Labs
Glenn2 said:
Small issue - I set the charging current to 1500mA and turned on ignore unstable charging etc.
When I do this on AGNi, the 'Galaxy Charging Current' app says 1500 for 'reference', 'maximum' and 'average'.
On Boeffla it says 1500 for 'reference' but only 1000 for the other two numbers.
Click to expand...
Click to collapse
Try using ampere or just the built in on the 1st page of boeffla config app, it'll correspond.
Also, now you can set charging current to 1600
Edit: http://i.imgur.com/IMlEiau.png
Sent from my GT-I9305 using XDA Labs
rodman01 said:
Sorry haven't seen it in op. I am a newbie and didn't read the op proper .
Click to expand...
Click to collapse
If you're a newbie all of us have not been born yet
Sent from my GT-I9305 using XDA Labs
Temasek + boeffla i cant hear any voice when call nor people can hear me.. Not even in loud speaker.. Or am i missing something? But boeffla rock!
I had this prob on unicorn aokp + agni4.5.5. So i stay stock. But because of boeffla, i went back to cm
Thank for porting.
Sent from my GT-I9305 using XDA-Developers mobile app
Mono Kernel for HTC One M9 (Hima)
Let's start this off with the basic and regular warning and disclaimer :
Code:
#ifdef (IF_YOU_FLASH_THE_KERNEL)
* No one except you chooses to flash this kernel, this is your [B]own[/B] choice
* Do not flash this if you expect stability that equals to a stock kernel
* Neither me or XDA is responsible if the kernel destroys your device
* No cats harmed during the creation of this kernel
#endif
Mono Kernel is a kernel made with simplicity and customizations in mind, I never wanted a kernel with gazillions of "bloaty" features (governors, schedulers, etc) that gives me uneasiness since there's too many choices to be made.
Technical details :
If you want to know about the toolchain and stuff I used
- Compiled with Google GCC 4.9 (pre 21-07-2016 releases), and UberTC 4.9.4 (21-07-2016 release and newer)
- Built on a SlimROM source tree
- Little to no weird optimizations flags, I'll avoid adding -Ofast, -O3, Graphite or anything related to them
Features :
Some bits of features that you'll see
- Latest upstream kernel, currently on 3.10.102
- zzmoove (bLE edition) and elementalx governor
- FIOPS and SIOPLUS scheduler
- Configurable thermal control
- Toggleable CRC and Dynamic Fsync
- USB Fastcharge
- UKSM 0.1.2.3 (Ultra KSM, an improved KSM)
- KCAL v2 (post-processing control for display)
- state_notifier driver, replaces earlysuspend and powersuspend
- Franco's Sound Control
- zRAM support
- Mini-bits of somewhat-safe (but not necessarily stable) optimizations
- Lots of updates and upstream works from various sources (CAF, Google, and Linux)
- And probably more
Bugs :
- Possible bug: Stereo channels are reversed (left to right and right to left) (False report on my side)
- None, at least for now
Download :
Get it while fresh!
AndroidFileHost Folder
Installation :
Please read all of this before continuing
For .img format (Slim6 only) :
IMG is deprecated as of 12 July release, please use ZIP instead
- Download the .img and put it somewhere
- Reboot to recovery (I'll assume you're using TWRP here)
- Press 'Install' then press 'Install Image' (located on the bottom-right side)
- Locate the .img
- Make sure you select 'Boot', not 'System Image' or 'Recovery'
- Swipe and install, but don't reboot
- Reinstall any Systemless mods (Systemless Root, Xposed, etc) if you have one
- Reboot and wait for it to boot!
For .zip format :
- I mean... you probably know how
- Just flash the zip
Compatibility List :
Check if your ROM is compatible
- Tested on Slim6
- Working on CM
- Possibly working on RR
Credits :
All these talented people deserves a cookie
(In no order)
- flar2
- faux123
- franciscofranco
- anarkia1976
- chadouming
- neobuddy89
- imoseyon
- myfluxi
- yarpiin
- Grarak
- ##W4TCH0UT##
- benschhold
- Evolutionzz & Dims_Camper (some nice friends to talk)
There's too many people that deserves to be here, if you're one of them (in case I somehow forgot to credit you here and on the source code / Git repo page), please, don't hesitate to PM me!
Notes :
- Mono Kernel will always remain on 'testing' phase, mostly because I tend to screw up and break stuff, so I don't warrant any stable release, unless otherwise mentioned
- This kernel is working on CM (and possibly other ROM based on it)
- Nope, I have never tested this on any other variant of the M9 apart from the International variant
- Yes, no hotplug support for now, I'm still experimenting with hotplugs on this device
XDA:DevDB Information
Mono Kernel, Kernel for the HTC One (M9)
Contributors
F4uzan
Source Code: https://github.com/F4uzan/mono_hima
Kernel Special Features: Uh... it's downloadable ?
Version Information
Status: Testing
Created 2016-07-09
Last Updated 2016-07-31
FAQ (Frequently Asked Questions)
Q : I want "x" and "y" feature to be added in this kernel
A : Sure thing, I'll give no promises it'll be added, but if I find it interesting (and usable), why not?
Q : Hey, can you fix "x" issue ? (if you provides no log or details whatsoever)
A : Please, give me more details, how can I reproduce the issue on my side ? If I'm unable to reproduce the issue then can you please provide more details to the issue ?
Q : What logs are needed to give you an exact information of my issue ?
A : /sys/fs/pstore/console-ramoops, dmesg, and any kind of kernel logs (not logcat) you can find
Q : Will this work on "x" ROM based on AOSP / CM ?
A : Probably, it might or might not work, test it out by yourself
Q : Will this work on stock or any Sense based ROM ?
A : Nope and probably never will, but I'll reconsider that if there's enough request
Reserved #1
More reserved (just in case)
One question-do you have the FM module and IR module in the kernel enabled? If you do, I;m willing to test on CM-I've been waiting for that.
wyvernwaddell said:
One question-do you have the FM module and IR module in the kernel enabled? If you do, I;m willing to test on CM-I've been waiting for that.
Click to expand...
Click to collapse
FM and IR module ? I'm pretty sure I didn't use both, so, the answer is probably no, let me double check just to be sure
EDIT : IR works fine using "SURE" Universal Remote app, I'll check if FM works
EDIT2 : Double checked whether IR works or not, it works with both my TV and air conditioning unit, so it's definitely working
EDIT3 : I don't think FM is working, I've tested with the CM FM Radio app, and it can't open /dev/radio0 (the device for FM radio), I'll see if I can find a way to fix it
AWESOME!
I'll be testing this ASAP! Thanks for this kernel!!! I assume it's MM Compatible? I'm using cm13 and will post any results I have after testing it out for a bit. So glad for this :good:
F4uzan said:
FM and IR module ? I'm pretty sure I didn't use both, so, the answer is probably no, let me double check just to be sure
EDIT : IR works fine using "SURE" Universal Remote app, I'll check if FM works
EDIT2 : Double checked whether IR works or not, it works with both my TV and air conditioning unit, so it's definitely working
EDIT3 : I don't think FM is working, I've tested with the CM FM Radio app, and it can't open /dev/radio0 (the device for FM radio), I'll see if I can find a way to fix it
Click to expand...
Click to collapse
YOU ARE THE MAN! Thank you!!
Sent from my NVIDIA SHIELD Tablet using XDA Labs
Can't wait to try this out. Thanks for your dedication
Skickat från min HTC One M9 via Tapatalk
Roobwz said:
Can't wait to try this out. Thanks for your dedication
Skickat från min HTC One M9 via Tapatalk
Click to expand...
Click to collapse
Be sure to send me some feedback, thanks for trying out
wyvernwaddell said:
YOU ARE THE MAN! Thank you!!
Sent from my NVIDIA SHIELD Tablet using XDA Labs
Click to expand...
Click to collapse
Thanks !
Krsmqn said:
I'll be testing this ASAP! Thanks for this kernel!!! I assume it's MM Compatible? I'm using cm13 and will post any results I have after testing it out for a bit. So glad for this :good:
Click to expand...
Click to collapse
Yes, it's actually only compatible with MM (unless the changes from L to M isn't that huge, I might be able to bridge a compatibility between both).
Have you experienced better battery with the kernel compared to stock? I remember when I was using the cm kernel and got really bad SOT thanks to the frequencies jumping all around all the time..
Skickat från min HTC One M9 via Tapatalk
Did NOT work on
[ROM] [ M9 ][himaul]Resurrection Remix M v5.7.0- MM 6.0.1_r46
Bootloop!
Roobwz said:
Have you experienced better battery with the kernel compared to stock? I remember when I was using the cm kernel and got really bad SOT thanks to the frequencies jumping all around all the time..
Skickat från min HTC One M9 via Tapatalk
Click to expand...
Click to collapse
Hmmh, I can say the battery usage is pretty on par with stock (I get an average of 4.5 hours of SoT, on stock it's roughly 5 hours)
AlphaAnimal said:
Did NOT work on
[ROM] [ M9 ][himaul]Resurrection Remix M v5.7.0- MM 6.0.1_r46
Bootloop!
Click to expand...
Click to collapse
Thanks for the report, I have been working on the AnyKernel version that should fix this, for now, everyone should avoid using this in any CM based ROM since the result might be the same
F4uzan said:
Hmmh, I can say the battery usage is pretty on par with stock (I get an average of 4.5 hours of SoT, on stock it's roughly 5 hours)
Click to expand...
Click to collapse
Well i gotta try it myself then. I'm running ice ATM and getting around 6-6:30 SOT no problem. May be cheating cause of airplane mode.. ?
Skickat från min HTC One M9 via Tapatalk
Let's all be patient now and let the dev do his magic.
Eagerly, but patiently awaiting.
Thanks for all the reports on CM13 !
I can't test it out on CM myself because I really need the phone to be on a somewhat stable condition, but I'll be fixing it soon !
Hello everyone !
A new update is up now, it should fix CM compatibilities. It's also in AnyKernel zip format (no more tedious .img flashing).
For complete changes, you can check the source link (I'm not going to write all of them here), but it's mostly just changes I merged from CodeAurora / CAF and Google, there's also some more optimizations in code.
The download link is here or in the link in OP
Happy testing !
https://www.androidfilehost.com/?fid=24591023225178092
F4uzan said:
Hello everyone !
A new update is up now, it should fix CM compatibilities. Its also in AnyKernel zip format (no more tedious .img flashing).
For complete changes, you can check the source link (Im not going to write all of them here), but its mostly just changes I merged from CodeAurora / CAF and Google, theres also some more optimizations in code.
The download link is here or in the link in OP
Happy testing !
Click to expand...
Click to collapse
Boots just fine. Gonna use it a bit and evaluate. Any recommendations for kernel control?
Krsmqn said:
Boots just fine. Gonna use it a bit and evaluate. Any recommendations for kernel control?
Click to expand...
Click to collapse
Until I add Synapse support, I recommend this modded Kernel Adiutor, the regular Kernel Adiutor works fine but it doesn't have all the control necessary for the kernel
Glad to see some movement on dev-kernel section!! I have been using Smoocha kernel for a while and return to stop again since the support is abandoned.. I could help and test this kernel on CM13 (since is now compatible), I am a cherry-picked addicted.
It could be great seeing working with Uber 5.x-6 toolchain, this is the only thing that I really envy of Nexus 6p.
Many thanks for your support and contribution :good:
Hi Huawei P9 people!
This is my modified kernel with some kernel optimizations and some compiler optimizations.
The goal of abyss-caf is to compromise stability and improved performance.
I will not be overhauling this project with changes that are not logical to add.
This kernel should work on all stock based roms; there is a separate version for NCS 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)
This kernel is built with Linaro GCC 4.9.4 that is optimized for ARM64 devices.
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.
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:
BasketBuild
AFH
Source:
GitHub
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 stock and stock based roms, Kernel for the Huawei P9
Contributors
kwoktopus, paulobrien, arter97, flar2, Christopher83, Cl3Kener, frap129
Source Code: https://github.com/kwoktopus/abyss_kernel_eva
Kernel Special Features: MAJOR KEY
Version Information
Status: Testing
Created 2016-08-24
Last Updated 2016-10-08
Main Patches and Features:
- Abyss Optimizations (compiler)
- optimized square root algorithm (3x faster)
- added BFQ io scheduler (now default)
- backported random from Linux 4.2+ (better entropy, better performance)
- utilize power efficient workqueues all over the kernel
- port quickwakeup driver for hisi from moto
- optimized lib patches
- optimized arm64 lib patches
- disabled gentle_fair_sleepers for better UX
- enhanced multicore decision making
How to install:
Flash the proper kernel zip in TWRP.
New to phone development?
If you are new to these forums or development in general,
please consult other members before trying this out.
There is no shame in asking for help politely and respectfully,
as long as you don't quote the whole OP or think slower than a sloth.
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!
Awesome, will stay tune about new releases, will try the kernel later.
Just for clarify, kernel works in any P9 or just for L09 or L19?
jeremymolina said:
Awesome, will stay tune about new releases, will try the kernel later.
Just for clarify, kernel works in any P9 or just for L09 or L19?
Click to expand...
Click to collapse
There's no reason that it wouldn't work, but there's always that slight chance. Pretty sure you'll be fine
Finally! May God bless you!
---------- Post added at 08:13 AM ---------- Previous post was at 08:07 AM ----------
I have a question though.
Will it conflict with the L Speed app I'm currently using?
And to finish off my day (the start of many of yours), here is my 2nd release for y'all.
Code:
- optimized square root algorithm (3x faster)
- added BFQ io scheduler (now default)
- backported random from Linux 4.2+ (better entropy, better performance)
- utilize power efficient workqueues all over the kernel
- port quickwakeup driver for hisi from moto
- optimized lib patches
- optimized arm64 lib patches
- disabled gentle_fair_sleepers for better UX
- enhanced multicore decision making
abyss-caf-eva-nightly-20160824.zip
darthkir said:
Finally! May God bless you!
Click to expand...
Click to collapse
God has blessed me alright :victory:
darthkir said:
Will it conflict with the L Speed app I'm currently using?
Click to expand...
Click to collapse
Not sure why it would, what tweaks do you have turned on? It should be good to go, I highly doubt anything can go wrong with any sort of non-kernel related tweaks.
this is great news! You have my thanks
For anyone on NCS rom, the kernel will not boot for you. Please test this build out. I will be looking into using an AnyKernel 2.0 flash method for TWRP users so that we don't run into conflicts like these in the future.
abyss-caf-eva-ncs-20160824.zip
Not only my rom, its for all recommended if root is installed.
This is ****ing awesome kwoktopus, so excited to try your work (tomorrow). Finally some more new development for the great P9.
Thanks kwoktopus !
Can i flash your kernel on fRomFuture ROM ?
Salamender said:
Thanks kwoktopus !
Can i flash your kernel on fRomFuture ROM ?
Click to expand...
Click to collapse
Not exactly sure. If fRomFuture has ramdisk modifications then probably not, I'll have to make a separate version for it. If you would like to try, download both versions of the kernel and try.
kwoktopus said:
Not exactly sure. If fRomFuture has ramdisk modifications then probably not, I'll have to make a separate version for it. If you would like to try, download both versions of the kernel and try.
Click to expand...
Click to collapse
Neither working on fRomFuture, tried with TWRP flash image method, when i get home ill try with fastboot also.
edint3000 said:
Neither working on fRomFuture, tried with TWRP flash image method, when i get home ill try with fastboot also.
Click to expand...
Click to collapse
If it doesn't work even through fastboot, try flashing my test versions.I will upload it with changes for fRomFuture that may work. Stay posted
edit: i am running low on bandwidth from all the source downloading lately, can someone upload the boot.img from the latest fRomFuture build
Uh...probably super obvious, but do you need unlocked BL and/or root in order to flash the kernel? Ta.
kwoktopus said:
If it doesn't work even through fastboot, try flashing my test versions.I will upload it with changes for fRomFuture that may work. Stay posted
edit: i am running low on bandwidth from all the source downloading lately, can someone upload the boot.img from the latest fRomFuture build
Click to expand...
Click to collapse
Here it is
edint3000 said:
Here it is
Click to expand...
Click to collapse
Try flashing the kernel attached, see if it works
Hi.
I've tried the kernel clean on the NCS ROM 1.2.
Unfortunately, the camera failed to launch and I noticed jerkiness in response.
Hi guys,
I know that this forum is not widely used by ZTE Axon 7 Mini owners, but I still want to share my work the kernel used by the stock firmware.
Most of the parts were of course already based on the work of others, so I will give credits at the end of this thread of course.
Pre-requisites:
Unlocked bootloader
TWRP flashed
Knowledge you do this all at your own risk! I tested this kernel with my EU model, so I don't know if this will work on the US models, too.
Features:
- Based on latest kernel source shared by ZTE (ZTE B2017G Nougat(7.1.1) Kernel(3.10.84))
- Built with GCC 4.9 toolchain
- UC to 499MHz for BIG and 403 MHz for LITTLE (thanks to @flar2)
- OC to 1651 for BIG (again @flar2)
- Additional governors: yankactive, blu-active, impulse
- Additional IO schedulers: Sioplus, Zen, FIOPS. Tweaked Row is set as default
- Additional TCP congestion algorithms with westwood being the default one
- Approx. 30% faster due to CRC calculation and auditing disabling
- Sweep2Sleep on the navigation bar
- frandom RNG
- Sound Control by @flar2
- ZRAM using LZ4 optimized for ARM by default
- Optimized power management driver by @Yank555
- Native exFAT support without needing fuse @dorimanx)
- KCAL
- Vibration control
- uses higher power CPUs to boot (got roughly 3s faster boot time)
- Dynamic Fsync
- Gentle Fair sleepers can be toggled via sysfs and Kernel Adiutor
- Smaller tweaks
To do:
- Switch toolchain
- Remove "dirty" from the kernel name Apparently I need to push all changes to github before compiling(or recompiling the same kernel as soon as I pushed everything)
- Set the phone to accept the lower frequencies without having to set this up in Kernel adiutor
- Alter interactive governor to use full frequency range
- Add D2TS for screen and fingerprint sensor, S2W
- Wakelock reductions
- Maybe BLX, KCAL (even though I don't get the point to implement it) I was curious and did it now, looks nice
- LED and vibration control
- Switch hotplugging mechanism to Lazyplug, hotplugging is not that energy efficient anymore
See the attached picture regarding the CPU stats when using yankactive for example
Credits go to:
@Lord Boeffla @flar2 @dorimanx @Yank555
Unfortunately I didn't give proper credits on my github, I want everyone to know, that none of the features were designed and written by myself, just adapted to work on our phones!
Download here:
https://drive.google.com/drive/folders/0B0mn6OUqIDzBZG1DM1Y4dmxUV2c
Flash in TWRP, root and every other ramdisk modification will be preserved (Anykernel2 by osmosis)
Github:
https://github.com/TheSSJ/tulip_kernel
Changelog
V1.1: Initial version for public release!
V1.2: KCAL support
V1.3: Changed boot CPUs to higher power ones, added dynamic Fsync, added Quick Wakeup driver
V1.4: Gentle Fair Sleepers can be toggled now, ROW scheduler tweaked
NOTE: in case anyone is wondering why I didn't pick the DevDB projects: as our device is not activated to be used with DevDB, I went with normal threads
TheSSJ said:
V1.1: Initial version for public release!
NOTE: in case anyone is wondering why I didn't pick the DevDB projects: as our device is not activated to be used with DevDB, I went with normal threads
Click to expand...
Click to collapse
Hi! Amazing work! Thx for the job.
Can I use this kernel with AOKP? AOKP has android 7.1.2
Askael said:
Hi! Amazing work! Thx for the job.
Can I use this kernel with AOKP? AOKP has android 7.1.2
Click to expand...
Click to collapse
I wouldn't exclude this, but as I am running on stock, I can't confirm or deny...
You could make a backup of your boot and flash it and see what happens, worst thing is that you need to reboot to recovery and restore your backup
TheSSJ said:
V1.1: Initial version for public release!
NOTE: in case anyone is wondering why I didn't pick the DevDB projects: as our device is not activated to be used with DevDB, I went with normal threads
Click to expand...
Click to collapse
TheSSJ said:
I wouldn't exclude this, but as I am running on stock, I can't confirm or deny...
You could make a backup of your boot and flash it and see what happens, worst thing is that you need to reboot to recovery and restore your backup
Click to expand...
Click to collapse
Thank you for replay, what governor you use?
You will need to try and see.
It uses anykernel which is good. But aokp and lineage are on android 7.1.2 while stock is on android 7.1.1. There was at least one kernel api change that may cause problems. But I'm not sure.
I'm assuming this package has the wlan module also...?
Askael said:
Hi! Amazing work! Thx for the job.
Can I use this kernel with AOKP? AOKP has android 7.1.2
Click to expand...
Click to collapse
@ssj @tdm
Guys, try flash kernel, AOKP, don't work.
W8 kernel version from customs
tdm said:
I'm assuming this package has the wlan module also...?
Click to expand...
Click to collapse
You mean the prima wifi stuff I have seen in you github? Honestly I didn't feel the need...does it improve the wifi experience or is it just for making it compatible with LineageOS?
No, I mean the kernel module for wifi, /system/lib/modules/pronto/pronto_wlan.ko. If that doesn't match your kernel, it won't load and you won't have wifi.
Note stock has a handful of other kernel modules, but I don't think any of them are needed Most look like they are for testing.
TheSSJ said:
You mean the prima wifi stuff I have seen in you github? Honestly I didn't feel the need...does it improve the wifi experience or is it just for making it compatible with LineageOS?
Click to expand...
Click to collapse
tdm said:
No, I mean the kernel module for wifi, /system/lib/modules/pronto/pronto_wlan.ko. If that doesn't match your kernel, it won't load and you won't have wifi.
Note stock has a handful of other kernel modules, but I don't think any of them are needed Most look like they are for testing.
Click to expand...
Click to collapse
Oh, ok...pronto driver is built into the kernel though, all other modules are really for debugging and testing as far as I could gather, so they are not included (and the phone works fine)
@Askael: As for a custom kernel for Lineage/AOKP etc: as I won't have these OS's on my phone I use as my daily driver, I can of course create one, but it is always published as untested, so there is no point IMHO.
TheSSJ said:
Oh, ok...pronto driver is built into the kernel though, all other modules are really for debugging and testing as far as I could gather, so they are not included (and the phone works fine)
@Askael: As for a custom kernel for Lineage/AOKP etc: as I won't have these OS's on my phone I use as my daily driver, I can of course create one, but it is always published as untested, so there is no point IMHO.
Click to expand...
Click to collapse
But we can test this. But if you not want - don't worry! :good:
Askael said:
But we can test this. But if you not want - don't worry! :good:
Click to expand...
Click to collapse
Will think about it
Version 1.2 is out, now with KCAL screen control support!
I'm building a kernel with many of these features for the LineageOS ROM. Want me to make a thread, and then you can link it for people interested in using it in your OP? Source is here: https://github.com/djkazic/sombrax_kernel
kevincai96 said:
I'm building a kernel with many of these features for the LineageOS ROM. Want me to make a thread, and then you can link it for people interested in using it in your OP? Source is here: https://github.com/djkazic/sombrax_kernel
Click to expand...
Click to collapse
Hi,
Feel free to open a new thread it is important to push this phone amd its potential as good as possible!
Development will go on, i still have some items to implement :good:
@TheSSJ
Hi! Any news about update?
@TheSSJ
Good to see you in Axon mini from zenfone 2
Askael said:
@TheSSJ
Hi! Any news about update?
Click to expand...
Click to collapse
You mean a custom kernel for CM builds or an update for this stock kernel?
For the CM based one I didn't start, although applying the modifications I applied to my kernel should be working
Druboo666 said:
@TheSSJ
Good to see you in Axon mini from zenfone 2
Click to expand...
Click to collapse
I was spotted It's a great phone, let's get the most out of it
TheSSJ said:
You mean a custom kernel for CM builds or an update for this stock kernel?
For the CM based one I didn't start, although applying the modifications I applied to my kernel should be working
I was spotted It's a great phone, let's get the most out of it
Click to expand...
Click to collapse
For this stok kernel
I was spotted It's a great phone, let's get the most out of it
Click to expand...
Click to collapse
i am using Axon 7 and yeah its a great phone i must miss you in axon 7
Updated version uploaded and available on G-Drive, boot time increased by 3s (you take what you can get )
/EDIT: Next version out, small enhancements and adding the possibility to enable/disable gentle fair sleepers