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 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
Features
Based on Codeaurora's msm-3.18 kernel branch LA.UM.5.5.r1-06700-8x96.0
Support for the camera laser autofocus
Lightweight (minimal amount of logging, tracing and debugging functions)
Compiled with Linaro GCC 6.4 using flags specific for Kryo
Userspace display color calibration (Kcal)
Under-the-hood performance patches
Caveats/To-Dos
Focusing on getting the NFC working (the kernel supports PN547, however, the blobs/configs provided by Lineage are for PN548)
Add F2FS support
Compatibility
Tested on LineageOS (2018-01-23), using the 20s bootloader/modem firmware
Downloads
https://forum.xda-developers.com/devdb/project/?id=24609#downloads
XDA:DevDB Information
Typhon Kernel, ROM for the LG G5
Contributors
waau
Source Code: https://github.com/waau/platform_kernel_typhon_q
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.x
ROM Firmware Required: 21S
Version Information
Status: Testing
Created 2018-01-26
Last Updated 2018-02-21
Changelog
M1
Initial release.
M2
Added (untested) support for the H830 & RS988 variants
installscript: Removed the partition fstrim step
ramdisk: Some memory bandwidth tweaks thanks to oxavelar @ the V20
Misc updates
M3
Ported the camera driver from stock, there are issues with the Lineage Snap camera see https://jira.lineageos.org/browse/BUGBASH-1076.
M4
Reverted to CAF's initial 3.18.31 kernel tree due to upstream changes causing crashes
Imported LMK changes from Motorola (avg time to find a task to kill from 1004us to 43us)
Misc driver improvements (bt should work better during streaming intensive workloads)
The IPC/Binder has been updated (is Oreo booting now?)
Relaxed the polling rates in some parts of the kernel
Crypto libs update
Booting takes 40 seconds or so.
This should be a stable build for all the supported variants, I'll improve the overall performance after taking a break and revisiting the Lineage kernel for the charging problem. M5 will be a mostly feature-oriented update including battery saving changes.
Artificial benchmarks seem much better now.
https://browser.geekbench.com/v4/cpu/6766622
M5 RC1
Merged EXT4 encryption from Lineage
Attempt to reduce the power consumption (artificial benchmarks will probably take a hit in some areas, the UX should not be affected)
Imported memory bandwidth improvements from Motorola
Re-enabled the ramoops console
Other misc merges
Let the phone settle for a while after the first boot.
The ramoops console has been re-enabled, in case there are any kernel panics, attach the dump and I'll take a look at it (/sys/fs/pstore/console-ramoops) The rest of the features will come in the final version. I'll also try to get the NFC working.
M6
Redone some parts of the memory management system (compaction, slab, ksm, cma, zram), also pagecaches are now dropped when the screen turns off
Dropped the serial console, kernel initialization should be faster
Driver adjustments (targeting memory leaks)
Memory bandwidth improvements from Sony
Enabled NTFS support (for OTG, untested)
Enabled KSM
Cleaned up the ramdisk, media.camera.ts.monotonic will need to be set manually (read: https://jira.lineageos.org/browse/BUGBASH-1076)
This is probably the last build since I'm giving away my G5 this month, if anyone wants to continue the kernel you are welcome to fork it, the new source is here.
https://github.com/waau/platform_kernel_typhon_q
Mirror for the kernel zip https://github.com/waau/platform_kernel_typhon_q/releases/tag/M6
Wait this is actually great. Quick charge on LOS 14.1 is back?
Kye2000 said:
Wait this is actually great. Quick charge on LOS 14.1 is back?
Click to expand...
Click to collapse
Ported from stock since it was too much of a hassle to fix it on the Lineage kernel, probably these merges broke it
https://review.lineageos.org/#/c/181342/
https://review.lineageos.org/#/c/181479/
waau said:
Ported from stock since it was too much of a hassle to fix it on the Lineage kernel, probably these merges broke it
Something amazing has begun. Thank you. :highfive:
Click to expand...
Click to collapse
Yup. Quick charge works on a fresh RRN install. Thank you very much.
EDIT: From an initial impression, the screen burn-in seems to be reduced a bit. Still very noticeable, though.
totalnoob34 said:
Yup. Quick charge works on a fresh RRN install. Thank you very much.
EDIT: From an initial impression, the screen burn-in seems to be reduced a bit. Still very noticeable, though.
Click to expand...
Click to collapse
I didn't reduce the panel voltage in the build posted here, only the one posted in the LOS thread has the panel voltage reduced. Probably going to reintroduce it later.
waau said:
I didn't reduce the panel voltage in the build posted here, only the one posted in the LOS thread has the panel voltage reduced. Probably going to reintroduce it later.
Click to expand...
Click to collapse
That's placebo effect right there. Is anything else different? I can test it, if you want.
totalnoob34 said:
That's placebo effect right there. Is anything else different? I can test it, if you want.
Click to expand...
Click to collapse
Nothing significant, besides reverting the reduced panel voltage stuff and dumping exFAT. Sure gonna attach it to this post after it's compiled.
Edit: Panel UV Build
This is fantastic! I'm itching to move back to LineageOS from Fulmics. Any chance we might see a fix for LiveDisplay or is that not related to the kernel?
halomademeapc said:
This is fantastic! I'm itching to move back to LineageOS from Fulmics. Any chance we might see a fox for LiveDisplay or is that not related to the kernel?
Click to expand...
Click to collapse
I will take a look at it.
waau said:
Nothing significant, besides reverting the reduced panel voltage stuff and dumping exFAT. Sure gonna attach it to this post after it's compiled.
Edit: Panel UV Build
Click to expand...
Click to collapse
Installed. I'll post back on how it goes.
For laser focus:
https://github.com/waau/platform_ke...ers/media/platform/msm/camera_v2/sensor/proxy
check: vl53l010 files.
Maybe it help to check LG G3 LOS kernel source because Laser focus is working.
I'm happy to report that the kernel works on an existing install of RR too, no need to clean flash :victory:
I was still on the 20a bootloader/modem so I flashed 20s first, just in case ... here are the steps I took:
Reboot to recovery
Nandroid
Flash 20s bootloader + modem
Wipe dalvik/cache
Reboot to system ... all good
Reboot to recovery again
Flash qc-typhon-h850-m1.zip
Wipe Dalvik/cache
Reboot to system
I was (well still am) on RR-N-v5.8.5-20171203-h850-Final and everything seems to work without an issue
Thanks for giving us back "normal" charging @waau :good: :highfive:
walter79 said:
For laser focus:
https://github.com/waau/platform_ke...ers/media/platform/msm/camera_v2/sensor/proxy
check: vl53l010 files.
Maybe it help to check LG G3 LOS kernel source because Laser focus is working.
Click to expand...
Click to collapse
Thanks, although I will try to port the camera drivers from stock and hope that the Lineage HAL cooperates.
waau said:
Thanks, although I will try to port the camera drivers from stock and hope that the Lineage HAL cooperates.
Click to expand...
Click to collapse
Would u be willing to recreate this kernel for the rs988? We only have 2 ROMs to choose from PA and rr and both have the slow charging issue
goast said:
Would u be willing to recreate this kernel for the rs988? We only have 2 ROMs to choose from PA and rr and both have the slow charging issue
Click to expand...
Click to collapse
I will add support for the RS998 and H830 tomorrow.
waau said:
I will add support for the RS998 and H830 tomorrow.
Click to expand...
Click to collapse
Thank u and I will be flashing tomorrow too lol
How can I help?
Hello, I have no development experience and am technically limited, but this project really gives me hope for the future of the G5. Is there anyway I can support you or be of assistence? Thank you so much for taking this on!
Hiya!
Would you be able to add CPU and GPU overclocking as well? I found this post from an old kernel developer who isn't updating theirs anymore, so the work is pretty much done I think.
https://forum.xda-developers.com/lg-g5/development/stock-kernel-t3540157/post72361249#post72361249
I would just use theirs and not bother you, but their kernel breaks bluetooth support for some odd reason, and I need that to use.
If you could add in overclocking I would be SUPER appreciative...
thanks!
Chihayafuru might feel like an awkward name for a kernel, but the meaning is pure and beautiful. Inspired from an Anime series, the name means "do towards good direction powerfully" like a "thousand swift swords". That's exactly what this kernel is.
This kernel has been made with love by cherry-picking commits from most of the work already done by other developers and introducing other slight changes which ensure your device gets the love it deserves. From performance to battery saving options, you're in full control of your device and the plethora of configurations available allow you to tweak it to your needs.
Presenting CF Kernel (ver 0.90) for Huawei Honor 8
Compatibility Notes:
This kernel is tested to work with stock EMUI 8, Treble 8.x and 9.x ROMs. Compatibility with other ROMs is not guaranteed, However, this doesn't mean I won't support them. If you face a bug or issue, please report it here and I'll happily take a look at it.
GPL Notice:
This kernel conforms to GPL license requirements. Thus all the source code is freely available here without any charge: https://github.com/hackslashX/android_kernel_hisi_hi3650
Recommended Apps:
To tweak most of the settings in the kernel, I recommend using EX Kernel Manager: https://forum.xda-developers.com/general/paid-software/app-ex-kernel-manager-t3560850, Kernel Adituor: https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor&hl=en and FK Kernel Manager: https://play.google.com/store/apps/details?id=com.franco.kernel&hl=en
Early Release Notice:
The kernel is still young and not yet mature. However, with time and your support, we can help make this project rock solid stable for Honor 8. Even though my initial testing has proved good, things might break on your end. Don't fret when that happens, take some logs and send it to me so that I can take a look at them and attempt for a fix.
Features:
Compiled with UberTC 4.9 toolchain with Cortex A53 and O2 optimizations
Upstreamed to v4.4.198
Added blu_active and enabled sched CPU governors (sched, blu_schedutil)
Enabled Scene Aware, Performance, and Powersave GPU governors
Enabled HiSilicon GPUFreq Hotplug and Frequency Hopping feature
Disabled useless drivers and features
Say no to Huawei D.U.B.A.I analytics and root scan feature
Disabled Huawei OASES and Livepatching feature
Disabled Swap and zRAM for much smoother operations
Mali GPU tweaks for improved performance
Added zen, FIOPS IO Schedulers
Added westwood and other advanced TCP algorithms
Fingerprint boost driver for quick recognition
Added CPU boost driver to reduce input lag
Reduced allowed wakelocks and better timer frequency
Boeffla Wakelock Blocker to kill unecessary wakelocks that interrupt your device sleep
Dynamic Sched Tune CPU support
Fast USB Charging support
Option to toggle FSync
Option to toggle SELinux to Permissive or Enforcing
Wireguard VPN support
Improvements to the sound module and vibration driver
... and more which I didn't note down or forgot xD
Installation:
Installing the kernel is pretty easy. Reboot your device to fastboot and execute the following command:
Code:
fastboot flash kernel <kernel-name.img>
Downloads:
Please check the Downloads tab for all downloads (till versions v0.45).
For v0.60 and later, please download from Google Drive: https://drive.google.com/open?id=1fHd7Y9XulrhzHou4013o3K_Ew3AZx2nq
XDA:DevDB Information
Chihayafuru Kernel v0.90 Honor 8 for Android 8.0+, Kernel for the Honor 8
Contributors
hackslash
Source Code: https://github.com/hackslashX/android_kernel_hisi_hi3650
Kernel Special Features:
Version Information
Status: Stable
Created 2018-09-08
Last Updated 2019-11-05
Thank you for your work
And i hope someone running android pie gsi can test this and see if it fix the overheating problem
Thanks a lot <3
Trying it .. will let you know, if I hit any issues
Does it affect the root after flashing this kernel?
$lim $hady said:
Does it affect the root after flashing this kernel?
Click to expand...
Click to collapse
No root is not affected after flashing this kernel.
The kernel image only modifies the 'kernel' partition and leaves the 'ramdisk' one as it is.
hackslash said:
No root is not affected after flashing this kernel.
The kernel image only modifies the 'kernel' partition and leaves the 'ramdisk' one as it is.
Click to expand...
Click to collapse
Thanks will flash it now..
Thank you bro' i flashed on my FRD-L09 Oreo ( stock + root ) and it's work
enzospain said:
Thank you bro' i flashed on my FRD-L09 Oreo ( stock + root ) and it's work
Click to expand...
Click to collapse
Good to know
delete
PremiumBlaze said:
Thank you hack slash for your support for having the honor 8 finally have a custom kernel, it works very well for me
I Flash the custom kernel using twrp for my honor 8, it went very well,
Performance is nice, I notice some speed improvements in games and also battery Improvment.
Im waiting for Undervolt now and the battery would be awesome!!!
Click to expand...
Click to collapse
Thanks for your review.
For gaming you can also set GPU governor to Performance for a more better experience.
I've noted down your request. I'll do my best to deliver.
I never flashed custom kernel before. Is there any chance of permanent brick? If something goes wrong, can't I just flash stock kernel and get it working again?
Also, do I need to wipe data after flashing kernel to see the changes?
SirDarknight said:
I never flashed custom kernel before. Is there any chance of permanent brick? If something goes wrong, can't I just flash stock kernel and get it working again?
Also, do I need to wipe data after flashing kernel to see the changes?
Click to expand...
Click to collapse
There's no chance of permanent brick. Restoring is as easy as flashing the stock kernel via fastboot.
You don't need to perform a data wipe. However, you should allow the kernel to 'settle' i.e. use it for 2-3 charge/discharge cycles to see the effect.
@hackslash .. Installed it yesterday, seems to be working fine.. Jus wanted to check, I m running LoS B5, any specific recommendations on the Governor setting for battery?
I'm using openkirin RR b2. Recent Openkirin on H8 seems to have the problem to barely go into deepsleep or not anymore at all after a while. So I suffer from a quick battery drain. The support channel suggested to try out a custom kernel. I wonder if you know that this kernel will solved the problem?
How about future openkirin or kernel updates? Will I have to go back to stock first or can I just flash new openkirin while still being on this kernel?
Thanks for your hard work! I recently flashed it and it works like a charm!
UPDATE 1: I redownloaded the EMUI 8 package and now it contains everything, including the stock kernel.
UPDATE 2: Short-term experiences: The fingerprint scanner's performance is drastically improved and now it is just as fast and accurate as on EMUI, the camera performance is now closer to EMUI, but there's a little room for improvement, the fast charging is faster than on EMUI, the phone doesn't want to overheat anymore on my custom ROM and overall the phone is now a little bit faster. I'm testing it with the Kirin-GSI AOSP Android 9.0 Pie ROM, not with an OpenKirin ROM, but it is really stable just like on EMUI and OpenKirin ROMs. And I have a suggestion for bugfixes for Honor 8s (eights) running this AOSP Android Pie ROM: Please fix the broken hotspot function in kernel level on Honor 8s (eights) running this custom firmware, implement the EMUI camera app into the kernel and make the camera performance identical to EMUI's. The Kirin-GSI project is now abandoned because the dev bought a new phone which is not a Huawei phone, so he wouldn't fix the problems anymore. It's really annoying that I can't share my unlimited cellular data to friends or to my PS4 when I'm on vacation.
Damn. Now my touchscreen is no longer working. :crying:
Sujanth said:
Damn. Now my touchscreen is no longer working. :crying:
Click to expand...
Click to collapse
Have you managed to back up or download the stock kernel image? You can flash it back.
---------- Post added at 05:56 PM ---------- Previous post was at 05:55 PM ----------
Sujanth said:
Damn. Now my touchscreen is no longer working. :crying:
Click to expand...
Click to collapse
Have you used fastboot or TWRP? If you used TWRP, you need to flash back the stock recovery and the stock kernel, then you can try again flashing CF via fastboot. Flashing with fastboot makes different results than flashing with TWRP.
Sujanth said:
Damn. Now my touchscreen is no longer working. :crying:
Click to expand...
Click to collapse
Noted. I know what's causing the issue. I disabled several touchscreen drivers since not all of them are needed for Honor 8. Flash stock kernel for your device and please send me the file:
Code:
/sys/devices/platform/huawei_touch/uevent
ThePS4Gamer said:
Thanks for your hard work! I recently flashed it and it works like a charm!
UPDATE 1: I redownloaded the EMUI 8 package and now it contains everything, including the stock kernel.
UPDATE 2: Short-term experiences: The fingerprint scanner's performance is drastically improved and now it is just as fast and accurate as on EMUI, the camera performance is now closer to EMUI, but there's a little room for improvement, the fast charging is faster than on EMUI, the phone doesn't want to overheat anymore on my custom ROM and overall the phone is now a little bit faster. I'm testing it with the Kirin-GSI AOSP Android 9.0 Pie ROM, not with an OpenKirin ROM, but it is really stable just like on EMUI and OpenKirin ROMs. And I have a suggestion for bugfixes for Honor 8s (eights) running this AOSP Android Pie ROM: Please fix the broken hotspot function in kernel level on Honor 8s (eights) running this custom firmware, implement the EMUI camera app into the kernel and make the camera performance identical to EMUI's. The Kirin-GSI project is now abandoned because the dev bought a new phone which is not a Huawei phone, so he wouldn't fix the problems anymore. It's really annoying that I can't share my unlimited cellular data to friends or to my PS4 when I'm on vacation.
Click to expand...
Click to collapse
Thanks for taking the time to review the kernel.
Let's get some facts straight. First, camera performance has nothing to do with the kernel and 'camera app' can't be implemented inside the kernel. That's not how things work. Camera processing and everything is handled by Android and so your ROM developer can help you with that. Taking about hotspot, I'm not sure why it doesn't works with Pie. Again, I believe it's a ROM bug and has got nothing to do with kernel. I would wait for Pie releases by OpenKirin team and see if that bug exists there too and 'really' requires a kernel hack to fix it.
Coconut Kernel for HAVOC OS - With Nethunter Support
Code:
***I'm not responsible for any problems that might occur flashing this kernel or what you do with the kernel support***
This kernel is tested on HAVOC OS 2.2 - 2.4 PIE. This is built from HolyDragon Source with added nethunter support/USB Wifi Adapter Drivers and monitor mode/packet injection
The kernel should also work on every ROM that Holydragon kernel supports.
Requirements
Oxygen OS 5.0.8 firmware is required. The wifi adapter wont work on older firmwares. Those who are using Havoc OS would most probably be on 5.0.8 firmware so this is just a remainder for others and/or anyone who have trouble making this work.
How to install
Make sure that you are rooted with magisk/supersu/any superuser
Download kernel from attachment and flash in TWRP Recovery
Reboot and download any terminal app like Termux
Plugin the USB Wifi card and open Termux
Type the command su
Then type ifconfig wlan1 up
This is how you can test whether it works or not
The kernel works fine with Nethunter as well as other chroot applications like Linux Deploy.
Note:- This kernel does not need any module to be inserted as all wifi drivers are compiled inline. So no need to insmod/modprobe
Credits
@HolyAngel for HolyDragon Kernel Source
Source
https://gitlab.com/HolyAngel/OP3
Thanks sir, this weekend, I test and i say you if I have a problem, but surely not, at this moment it is the kernel that I have but without the controller. I want to learn to compile the kernel on my own so that, in case HolyAngel updates the kernel, it dosn't depend on your work.
Victroid said:
Thanks sir, this weekend, I test and i say you if I have a problem, but surely not, at this moment it is the kernel that I have but without the controller. I want to learn to compile the kernel on my own so that, in case HolyAngel updates the kernel, it dosn't depend on your work.
Click to expand...
Click to collapse
https://forum.xda-developers.com/an...erence-how-to-compile-android-kernel-t3627297
Follow the tutorial above for kernel building.
@fredrickz
Any future build for stock oos pie like your Oreo one, it was perfect man thank you for your efforts regard to the community.?
DoN LoUhI said:
@fredrickz
Any future build for stock oos pie like your Oreo one, it was perfect man thank you for your efforts regard to the community.
Click to expand...
Click to collapse
Stock oos pie source isn't available yet man. I can build pie version from holydragon sources. I'll compile one when stock sources arw available too.
fredrickz said:
Stock oos pie source isn't available yet man. I can build pie version from holydragon sources. I'll compile one when stock sources arw available too.
Click to expand...
Click to collapse
Fair enough, thank YOU:laugh::good:
You explicitly mention this:
This is built from HolyDragon Source with added nethunter support/USB Wifi Adapter Drivers and monitor mode/packet injection
Click to expand...
Click to collapse
And the kernel source points to:
https://gitlab.com/HolyAngel/OP3
Click to expand...
Click to collapse
This can only mean 2 things:
1) you've merely taken holydragon kernel source and renamed it as your own or
2) you're actually breaking the GPL here by not releasing your changes
So which one is it?
And this leaves me no doubt that the second is very likely the case:
Note:- This kernel does not need any module to be inserted as all wifi drivers are compiled inline. So no need to insmod/modprobe
Click to expand...
Click to collapse
@Fredricks
It would be more than appreciated if you could add support for HID brother. Thanks:crying:
anupritaisno1 said:
You explicitly mention this:
And the kernel source points to:
This can only mean 2 things:
1) you've merely taken holydragon kernel source and renamed it as your own or
2) you're actually breaking the GPL here by not releasing your changes
So which one is it?
And this leaves me no doubt that the second is very likely the case:
Click to expand...
Click to collapse
I dont want to break any gpl.. the thing is that all my changes are local. Im not used to github. This kernel and all others i posted werr just for my own use. I have been using @ZaneZam kernel for oneplus3. But the Oreo kernel wasnt working fine. Thats the reason i tried to compile one my own. I shared it with a friend of mine some time ago and he insisted that i should post it so that others may also benefit. The kernel i posted doesn't have tonnes of feature list because i mostly stick to stock. I just added the wifi drivers and was using them. My friend asked me to add support for DriveDroid and i just did that. I don't know much about git and didnt have time to learn.
If this is against the rules then maybe ill post the source later. Im currently out of town.
for now if you want to know what changes i did,
1. Prepare the kernel for standalone build (except holydragon kernel)
2. Added just the wifi drivers mentioned in the nethunter wiki. I didnt add support for usb Bluetooth or sdr.
3. Added support for DriveDroid from official post in xda making changes to adapt the code to 3.18 kernel.
4. Added a fancy name to the kernel.
5. Published it.
DoN LoUhI said:
@Fredricks
It would be more than appreciated if you could add support for HID brother. Thanks:crying:
Click to expand...
Click to collapse
Im out of town bro. Ill add it when i reach home.
fredrickz said:
Im out of town bro. Ill add it when i reach home.
Click to expand...
Click to collapse
Very thankful, have a good time..:good: