DISCLAIMER
BACKUP and BACKUP ALWAYS AND BE FIRST
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed. Please
do some research if you have any concerns about features included in this KERNEL
before flashing it! YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you.
==================================================
Please read completely this thread before using for minimize FAQ
If you coming from other custom kernel, please restore boot.img that came with your current rom or dirty flash your rom before flash this!
Only for Falcon (Moto G 1st gen)
Requirement
TWRP
LaOS 14.1 or AOSP 7 .1.x
Note
Please backup your boot from TWRP, if something wrong happen, you can restore it and avoid losing any data.
Features
Latest Source Lineage OS
Compiled with Uber 4.9.4
Wake Gesture (DT2W) disabled by default (will add after stable stage)
add smartmax, lionheart, impulse cpu governor
enable kernel mode neon
optimized crypto 256/384/512 Neon
disable jump label
support init.d ! (Make sure your rom has installed busybox under side /system/xbin)
Change Logs
Please check at my github
BUGS ?
You tell me with proper logs (kmesg/dmesg)
Credits
Google
LineageOS
Motorola
Gabriele M
Savoca
Christopher83
franciscofranko
Faux123
Hurtsky
anyone who i can't remember the name
Download
https://www.androidfilehost.com/?w=files&flid=196044
XDA:DevDB Information
Clarity Kernel Moto G (Falcon), Kernel for the Moto G
Contributors
rainforce279
Source Code: https://github.com/ryan-andri/android_kernel_motog
Kernel Special Features:
Version Information
Status: Beta 2
Beta Release: 2017-07-11
Created 2017-07-05
Last Updated 2017-07-11
FAQ (Frequency Asked Question)
A: Error when installing this kernel in TWRP, why ?
B: Try update your TWRP or send to me TWRP Log.
A: I've found bugs with this kernel ?
B: tell me with logs.
A: My device is Bootloop ?
B: report to me, and pls dirty flash your current rom or restore your backup boot from twrp.
A: This kernel can help me to save my battery ?
B: No, its depend on your usage.
A: DT2W not working, why ?
B: DT2W is still in progeress testing due its feature come with Pocked mode, i'll do the best for you. So pls support me by send logs if DT2W not working or Buggy.
A: Can i flash this to stock rom ?
B: never try it, atleast your device will bootloop.
A: Can i flash this to Marshmallow ?
B: possible boot but wifi will broken.
Awesome kernel. Very smooth. But sometimes phone gets stuck while scrolling. Overall great kernel ! Thanks.
emil_515 said:
Awesome kernel. Very smooth. But sometimes phone gets stuck while scrolling. Overall great kernel ! Thanks.
Click to expand...
Click to collapse
thanks for your report mate,
can you provide to me Last kernel message and Driver Message ?
you can take it using Kernel Adiutor in section settings.
i hope i can resolve stucking when scrolling with thats log.
thanks
rainforce279 said:
thanks for your report mate,
can you provide to me Last kernel message and Driver Message ?
you can take it using Kernel Adiutor in section settings.
i hope i can resolve stucking when scrolling with thats log.
thanks
Click to expand...
Click to collapse
Haven't taken one before but I hope this is the right one.
Push Beta
logs:
- fix bugs from testing release (Stuck whe scrolling should be fix from here)
- added dt2w disabled by default (in testing, pocket mode will coming soon)
- enable kernel mode neon
- optimized crypto 256/384/512 neon
- disable jump label
if you found bugs, please report with last_kmesg and dmesg.
Download
https://www.androidfilehost.com/?w=files&flid=196044
@rainforce279 Last beta failed to update kernel on AOSP Extended 4.3. I then merged the kernel with current ramdisk on P.C first and then installed as a regular boot.img - that worked perfectly.
I don't use DT2W but the rest of the kernel seems to be working nicely. Thanks for your efforts :good:
Feature request: Any chance of including some modest degree of fast-charge over USB? The stock charging rate is miserably slow.
Using it on Aospex which was smooth enough, but now its even smoother, will report again about battery after some days, well done and thank you:good:
jajk said:
@rainforce279 Last beta failed to update kernel on AOSP Extended 4.3. I then merged the kernel with current ramdisk on P.C first and then installed as a regular boot.img - that worked perfectly.
I don't use DT2W but the rest of the kernel seems to be working nicely. Thanks for your efforts :good:
Feature request: Any chance of including some modest degree of fast-charge over USB? The stock charging rate is miserably slow.
Click to expand...
Click to collapse
ok i'll make change for flashable zip to fix that problem.
yes we can adding usb force fastcharge but thats feature a bit risky and can damaging our loved device.
Squid2 alread explain how usb force fastcharge is risky.
squid2 said:
This kernel charges at the rate supported by the charger. When you connect to an AC adapter, it will make use of the current it can provide. When you connect to a 'turbo charger" (12V), it will charge at the turbo rate. When you connect to a normal USB port, it will comply with the specification and draw the 500 mA that the specification permits normal USB ports to safely provide. This is the same behaviour as the stock kernel.
What the so-called "Fast Charge" feature does is that it forces all USB ports, including normal USB data ports on you're computer to behave as wall chargers and it will draw all the current that the port can provide. This violates the safe limits specified by the USB specification, but it usually works because the USB ports on good quality computer boards will have protection circuitry on the other side to prevent overcurrent. However, if you connected your phone to a compliant USB port only designed to provide 500 mA, and the port had damaged or lacking protecting circuitry, the phone could damage your computer's USB port.
I don't like the idea of violating the USB specification and potentially damaging USB ports. Thus, I prefer maintaining the present compliant and safe implementation. Your phone will charge at the rate that the port you plug it in to is intended to do so.
Click to expand...
Click to collapse
@rainforce279 Thanks for the reply. I understand the risk in pulling too much current from USB ports. I was hoping that the USB max charge current could be manipulated rather than invoke a dodgy fast-charge hack. I have not tested what the maximum charge current on USB is but it seems to charge very slowly. I will check it out - if it is indeed 500mA then I will be content
Edit: Indeed the max USB charging current is 500mA but the actual current tapers off as the battery voltage increases. It gets to a point of stalemate as he device consumption equals the charge current. That is the cause of slow charging on USB - not the 500mA max limit.
So the question becomes: Is there a charging current / voltage table or value that can be adjusted that will maintain a higher current to the end of charging via USB?
@rainforce279 Edit 2: On charger limit is set to 650mA so the standard fast-charge behavior applying this to USB ports would not be overly drastic in the case of our phone. I would be happy to gain that little bit faster charging over USB. Maybe give the option to set it but defaults to not enabled?
Can I flash this kernel in my moto g falcon running Viper OS nougat rom?
Works smooth as for me. I'm on latest LOS 14 nightly build.
jhfm said:
Can I flash this kernel in my moto g falcon running Viper OS nougat rom?
Click to expand...
Click to collapse
you can try it, backup your stock boot first
dranik said:
Works smooth as for me. But it seems that all kernels works at 1190Mhz all the time. Changing CPU governors or MPDecision doesn't fix anything. I'm on latest LOS 14 nightly build.
Click to expand...
Click to collapse
nah, i'll look it asap.
can u post ss of cpufreq table statistic from kernel adiutor ?
also can u post dmesg ? take it from kernel adiutor pls.
thanks
Push Beta 2 [110717]
Logs:
bf894f9 cpufreq: impulse: bring back get_cpu_idle_time function
8514000 Revert "input: import Doubletap2wake driver"
708b1ed Revert "dt2w: adapt to falcon"
168f81d Revert "dt2w: change to powersuspend and listen synaptic driver"
e5f9889 Revert "cpufreq: Move get_cpu_idle_time() to cpufreq.c"
c96ce8f Revert "cpufreq: remove old get_cpu_idle_time from some governor"
8cede3e Revert "soc: qcom: rq_stats: remove the redundant iowait check"
the update reverted some patch suspected lead to high frequency all the time,
pls give a report about this update.
post dmesg and last_kmesg too
thanks have a nice day !
Download
https://www.androidfilehost.com/?w=files&flid=196044
Thanks! Keep up the good work.
Is this compatible with Slim Rom 7?
rainforce279 said:
Logs:
bf894f9 cpufreq: impulse: bring back get_cpu_idle_time function
8514000 Revert "input: import Doubletap2wake driver"
708b1ed Revert "dt2w: adapt to falcon"
168f81d Revert "dt2w: change to powersuspend and listen synaptic driver"
e5f9889 Revert "cpufreq: Move get_cpu_idle_time() to cpufreq.c"
c96ce8f Revert "cpufreq: remove old get_cpu_idle_time from some governor"
8cede3e Revert "soc: qcom: rq_stats: remove the redundant iowait check"
the update reverted some patch suspected lead to high frequency all the time,
pls give a report about this update.
post dmesg and last_kmesg too
thanks have a nice day !
Download
https://www.androidfilehost.com/?w=files&flid=196044
Click to expand...
Click to collapse
Just installed, seems to work fine!
But Kernel Auditor gave very little option to personalize!
I will see next days how will behave!
Did you still work on this project?
thank you.
Looks like the screen rotation is broken in the latest version
I'm using LOS 14.1 and it seems like that in the latest version of this kernel, the screen rotation is broken. How can I fix it?
NOTE: This only happens when I install this kernel, the stock kernel from LOS doesn't have this problem.
What is the max CPU frequency in this kernel?
Related
Hi all,
some of you know me from the other OnePlus (One and Two) or Samsung devices areas, where I provide my kernels already for more than two years to OnePlus One, OnePlus Two, Galaxy S5, S3 and Note 10.1 users for all sort of platforms (Samsung, Cyanogenmod, Omnirom etc.)
Please note:
I am not heading to have as many features as possible implemented, this is not my design goal. If you are more into that, move on to other kernels. If you are searching for a good mix of improvements and new functions while not sacrificing stability, you are welcome here (see below the history section for more info).
Compatibility
Important: This kernel is only meant to be compatible with official OnePlus OOS and nothing else.
So when the kernel does not run on custom rom XYZ, do not even bother me with it or ask hundred times in the thread for compatibility.
I could not care less about it !!
Important notes
]When using new anykernel concept Boeffla-Kernel: Flash stock kernel of rom first !
Make sure you flash the correct kernel version, depending on whether you really use Oxygen OS or a different OS !!!
Also note: You have to use Boeffla-Config app which I provide on my homepage to tweak the kernel. 3rd party apps will not be able to unleash the full power of the kernel.
Saying that, the Boeffla-Sound app in Play Store is not designed to work on the OPX, neither was it developed by me, hence it will never work on the OPX ever. Boeffla-Config is the way to go here !!!
Support
First read the FAQ section on the Homepage !!!
Click here to learn about all possible kernel settings in the config app (quite outdated, as it is focused on S3 still).
Click here to learn about using the config app (quite outdated, as it is focused on S3 still).
I will refuse to give support if you do any undervolting and experience freezes or hot reboots.
I will also not provide any support if you do not use Boeffla-Config app to tweak the kernel, other 3rd party tweaking apps are known (and intended) to cause issues.
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.
Otherwise, you can get in touch with me via the support e-mail address: [email protected]
Please provide kernel version, rom version, a detailed issue description and ideally supporting screenshots or log files.
Change logs
(you can also access them directly in Boeffla-Config V2 by pressing menu and selecting "change log...")
Change log for Oxygen OS 3.x.x kernel - Click here
Change log for Oxygen OS 2.x.x kernel - Click here
Features
Support of anykernel concept (only latest kernels) - flash stock kernel before flashing Boeffla
Full integration with Boeffla-Config V2 (you need at least version 2.2.29 or higher !!!) configuration app (get it from http://www.boeffla.de) to configure all kernel settings
Additional governors: zzmoove, intelliactive, intellidemand, intellimm, wheatley, smartmax, smartmax_eps, slim, intellimm, pegasusq, nightmare, lionheart, impulse, ondemandplus, yankactive
Zzmoove supporting native hotplugging profiles
Additional schedulers: fiops, bfq, sio, tripndroid, zen
Many Hotplug tweak profiles (Default, Optimized, 1 core max, 2 cores max, 3 cores max, 2 cores min, 3 cores min, 4 cores min, 2 cores exact, 3 cores exact)
Notification LED control (fading, speed, brightness)
Boeffla-Sound engine (Headphones volume configurable currently)
True dynamic FSync (activated if screen on, deactived if screen off), configurable
Touch boost frequency and duration configurable, touch boost switch
CPU Overclocking up to 2.54 GHz
CPU Voltages interface for undervolting/overvolting
GPU idle frequency 27 Mhz added
GPU governor selection support with fixed simple_ondemand0
Show GPU frequency usage per frequency in Boeffla-Config
KCAL color control driver
Swipe2wake gestures
Swipe2sleep gestures
Haptic feedback control
SD card read ahead buffer configurable (default increased to 1024 kB)
Ext4 File system tweaks (default to on, can be disabled)
System Tweaks predefined supported
Kernel logger (dmesg) configurable
Charge rates for AC charger and USB charging separately configurable (set charge rate to 0 to have stock charge logic back)
Charge information display support via Boeffla-Config V2 app
CIFS support (module, do not mount inside /data, if you rooted with Chainfire SuperSu, make sure you uncheck the namespace separation in SuperSu app)
NFS support (module)
exFat opensource support
NTFS support (module) - read-only
XBox support (module)
OTG-Ethernet support (module)
TCP Congestion changed to Westwood
Multiple additional TCP congestion algorithms available
Swap supported
init.d support (in /system/etc/init.d - set correct permissions!)
Default entropies increased
Automatic EFS backup
Full support for mpdecision for best compatibility and smoothness (no min cpu frequency reset, use Boeffla-Config to configure min frequencies only)
Integrated full busybox 1.24.2 (own compilation)
Kernel initialisation log file (with history of 3 log files)
Emergency reset script automatically placed into /boeffla-kernel-data folder of your internal memory
Presets supported in Boeffla-Config by kernel (Extreme power, power, normal, battery friendly and battery saving)
Kexec hardboot patch for multirom usage (not supported, not fully working)
Google gcc 4.8 toolchain used for best stability
Always using latest Oxygen OS Initramfs
Always based on latest Oxygen OS kernel sources (https://github.com/OnePlusOSS/android_kernel_oneplus_msm8974)
Note: I do NOT upstream the kernel to higher Linux kernel versions anymore as this usually has zero benefit but likely introduces new issues + is a waste of effort in the end
Download
For all information and downloads (stable AND testing versions), visit the Boeffla-Kernel homepage:
www.boeffla.de
History and design targets
Basically I created my first Boeffla-Kernel in 2012 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. Also it does not aim to have the broadest feature set available everywhere.
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 !!!
These design targets are also valid for the OnePlus kernel here!!!
This said, I will definitely NEVER implement:
things I do personally not need
things I do not like
things that are in any way dangerous
anything which is highly experimental
f2fs - it is known to cause various issues and compatibility problems
custom hotplugging algorithms
a CAF based kernel
anything that requires upstreaming of kernel parts to a higher kernel major version
So do not even ask for it if it falls into the listed categories. Everything else I am happy to check and decide.
And: I do not really care about benchmark numbers, they say almost nothing as long as something is not completely wrong. Important for me is the feel-good factor.
I am also not interested in gaming at all, so never expect a gamer kernel. It will just not happen...
Compatibility
To reiterate it again: Flash the correct kernel depending on whether you are using Oxygen OS or another rom !!!
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.
You need at least version 2.2.29 or higher for the OnePlus X Boeffla Kernels.
Donation
If you like my work, feel free to donate: Donation-Link
If you donate at least 2,49 EUR (to be in line with the donation app prices on Google Play store), you will receive a personal donation code which unlocks some nice little comfort functions in Boeffla-Config V2 on top.
Source code
All sources can be found in my Github repository: http://github.com/andip71
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:
* ZaneZam
* Grarak
* Yank555
* Hardcore
* Chainfire
* AndreiLux
* Netarchy
* Gokhanmoral
* Simone201
* Mialwe
* Entropy512
* Faux
* Harunjo
* FranciscoFranco
* Ak
... 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 your custom recovery and safely store your personal data before you flash a new kernel.
Cheers and enjoy
Andi
Latest change logs:
http://kernel.boeffla.de/oneplusx/boeffla-kernel-oos/oos3xx/changelog.htm
*** You want my support? Then stick to my rules ***
Guys, I am receiving more and more completely useless support requests in different threads. Useless because people provide nothing to be able to help, not even the minimal possible information they could give.
Hence, I will now remind anyone again on the support guide lines stated here:
http://boeffla.de/index.php/support/support
Also you need to ensure you follow the installation guide lines incl. trouble-shooting stated here:
http://boeffla.de/index.php/support/installation-how-to
And to cut a long story short: If you do not at least provide what I request in the support guide lines, I will IGNORE YOUR REQUESTS IN FUTURE.
Straight and simple. I have enough of people wasting my time just because they are too lazy to write details.
Period.
Also as a reminder:
you use xposed? -> no support, everything is your own issue
you use a custom rom and not the official stock or CM one? -> good luck, you are on your own
you undervolt or overclock? -> have fun, but without my support
Sorry, this might sound harsh (and it is meant to sound harsh), but you cannot imagine about how crappy support requests can be. Stating something does not work is just not enough.
Please consider that!!!
Andi
Great to have you here
Welcome Andi !!! Gonna flash your kernel as soon as I get my OPX .... Will make profiles for it too
Welcome again !!!
Naman Bhalla said:
Welcome Andi !!! Gonna flash your kernel as soon as I get my OPX .... Will make profiles for it too
Welcome again !!!
Click to expand...
Click to collapse
Hehe, nice. I see you everywhere, isn't it?
Andi
sorry if i sound like a noob but if i have bluspark kernel already flashed, can i just flash this ontop of it? or do i have to restore a backup (of the opx before i flashed bluspark) and then flash this kernel? thanks in advance
Thanks a ton. Is CM support planned?
ihs0201 said:
sorry if i sound like a noob but if i have bluspark kernel already flashed, can i just flash this ontop of it? or do i have to restore a backup (of the opx before i flashed bluspark) and then flash this kernel? thanks in advance
Click to expand...
Click to collapse
You can flash on top of it as Boeffla kernel works on a different principle (Sorry.. I forgot what it is called... LOL... Maybe Andi can tell) .... But yeah, if issues come, flash stock and then the Boeffla (shouldn't happen though )
#HappyFlashing
Lord Boeffla said:
Hehe, nice. I see you everywhere, isn't it?
Andi
Click to expand...
Click to collapse
hehe !! I try to help the community as much as possible...
---------- Post added at 12:04 AM ---------- Previous post was at 12:01 AM ----------
RJDTWO said:
Thanks a ton. Is CM support planned?
Click to expand...
Click to collapse
I don't wanna post on behalf of Andi... But if you have been following Andi , he usually builds for CM once official builds roll out with everything working... For now, there is no official build, though almost everything is working now...
But Boeffla is in initial phase of development for OPX so I feel lord will focus more on Oos...
In short, don't expect a CM version till official nightlies start.
Naman Bhalla said:
You can flash on top of it as Boeffla kernel works on a different principle (Sorry.. I forgot what it is called... LOL... Maybe Andi can tell) .... But yeah, if issues come, flash stock and then the Boeffla (shouldn't happen though )
#HappyFlashing
Click to expand...
Click to collapse
Thanks for the quick reply
Nice to see boeffla kernel here. Was waiting for this after seeing a thread on oneplus forum. Is there a version for cm12/13 as well?
Edit: Never mind
Finally, I can't wait to flash it. You're the best, Andi, I'm proud I can say I designed your avatar, hahaha.
well i tried to install, and it gave me the error : your device is onyx. this zip is for ONE
i did install this zip: boeffla-kernel-4.0-beta1-OOS2xx-OnePlusX.recovery.zip
can anyone help/has the same problem
ihs0201 said:
well i tried to install, and it gave me the error : your device is onyx. this zip is for ONE
i did install this zip: boeffla-kernel-4.0-beta1-OOS2xx-OnePlusX.recovery.zip
can anyone help/has the same problem
Click to expand...
Click to collapse
Which recovery did you use ? As can clearly be seen, this issue is from Updater-script .... So either you can delete that line from the script or best is to use another twrp
Naman Bhalla said:
Which recovery did you use ? As can clearly be seen, this issue is from Updater-script .... So either you can delete that line from the script or best is to use another twrp
Click to expand...
Click to collapse
it is version twrp v.2.8.7.0, but i will try and update and then get back to you
ihs0201 said:
well i tried to install, and it gave me the error : your device is onyx. this zip is for ONE
i did install this zip: boeffla-kernel-4.0-beta1-OOS2xx-OnePlusX.recovery.zip
can anyone help/has the same problem
Click to expand...
Click to collapse
You downloaded the wrong kernel ( you downloaded the OnePlus one variant) so don't flash it as it might brick your device.
Scroll a bit more down in the Web page till you find OnePlus X.
P.S. The website can be a bit confusing for newer members, so here you go.
http://boeffla.df-kunde.de/oneplusx/boeffla-kernel-oos/oos2xx_download/Test/
Cheers.
dagger said:
You downloaded the wrong kernel ( you downloaded the OnePlus one variant) so don't flash it as it might brick your device.
Scroll a bit more down in the Web page till you find OnePlus X.
P.S. The website can be a bit confusing for newer members, so here you go.
http://boeffla.df-kunde.de/oneplusx/boeffla-kernel-oos/oos2xx_download/Test/
Cheers.
Click to expand...
Click to collapse
no it was the opx variant, as the filename showed opx when i flashed it. thanks anyway, and yeah the website is a bit jumbled
but the problem was an old twrp version. updated it and the kernel flashed no problem . BTW i like ur icon pack, might try it
Can someone explain the difference between this kernel and blu-spark to us common people?
What do you take into consideration when deciding which one to use?
Hi Andi,
Good to have Boeffla kernel again!
The real deal just came to opx. Thanks, bro! Hope opx gets official cm so you can provide support for cm too, as I cannot live without cm.
** Note: This kernel is end-of-life and will no more be maintained. There will be no LineageOS 15.1 or newer kernel be available anymore **
Hi all,
some of you know me from the other OnePlus (One and Two) or Samsung devices areas, where I provide my kernels already for more than two years to OnePlus One, OnePlus Two, Galaxy S5, S3 and Note 10.1 users for all sort of platforms (Samsung, Cyanogenmod, Omnirom etc.)
Now I own a OnePlus X device and decided to port my kernels also to this device.
Please note:
I am not heading to have as many features as possible implemented, this is not my design goal. If you are more into that, move on to other kernels. If you are searching for a good mix of improvements and new functions while not sacrificing stability, you are welcome here (see below the history section for more info).
Compatibility
Important: This kernel is only meant to be compatible with official Cyanogenmod and nothing else.
So when the kernel does not run on custom rom XYZ, do not even bother me with it or ask hundred times in the thread for compatibility.
I could not care less about it !!
Important notes
When using new anykernel concept Boeffla-Kernel: Flash stock kernel of rom first !
Make sure you flash the correct kernel version, depending on whether you really use CM or a different OS !!!
Also note: You have to use Boeffla-Config app which I provide on my homepage to tweak the kernel. 3rd party apps will not be able to unleash the full power of the kernel.
Support
First read the FAQ section on the Homepage !!!
Click here to learn about all possible kernel settings in the config app (quite outdated, as it is focused on S3 still).
Click here to learn about using the config app (quite outdated, as it is focused on S3 still).
I will refuse to give support if you do any undervolting and experience freezes or hot reboots.
I will also not provide any support if you do not use Boeffla-Config app to tweak the kernel, other 3rd party tweaking apps are known (and intended) to cause issues.
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.
Otherwise, you can get in touch with me via the support e-mail address: [email protected]
Please provide kernel version, rom version, a detailed issue description and ideally supporting screenshots or log files.
Change logs
(you can also access them directly in Boeffla-Config V2 by pressing menu and selecting "change log...")
Change log for CM13 kernel - Click here
Features
Support of anykernel concept (only latest kernels) - flash stock kernel before flashing Boeffla
Full integration with Boeffla-Config V2 (you need at least version 2.2.42 or higher !!!) configuration app (get it from http://www.boeffla.de) to configure all kernel settings
Additional governors: zzmoove, intelliactive, intellidemand, intellimm, wheatley, smartmax, smartmax_eps, slim, intellimm, pegasusq, nightmare, lionheart, impulse, ondemandplus, yankactive
Zzmoove supporting native hotplugging profiles
Additional schedulers: fiops, bfq, sio, tripndroid, zen
Many Hotplug tweak profiles (Default, Optimized, 1 core max, 2 cores max, 3 cores max, 2 cores min, 3 cores min, 4 cores min, 2 cores exact, 3 cores exact)
Notification LED control (fading, speed, brightness)
Boeffla-Sound engine (Headphones volume configurable)
True dynamic FSync (activated if screen on, deactived if screen off), configurable
Touch boost frequency and duration configurable, touch boost switch
Additional swipe2wake gestures
Additional swipe2sleep gestures
CPU Overclocking up to 2,57 GHz
CPU Voltages interface for undervolting/overvolting
GPU idle frequency 27 Mhz added
GPU governor selection support with fixed simple_ondemand
Show GPU frequency usage per frequency in Boeffla-Config
KCAL color control driver
Swipe2wake gestures
Swipe2sleep gestures
Boeffla generic wakelock blocker V1.1.0 (documentation)
SD card read ahead buffer configurable (default increased to 1024 kB)
Ext4 File system tweaks (default to on, can be disabled)
System Tweaks predefined supported
Kernel logger (dmesg) configurable
Charge rates for AC charger and USB charging separately configurable (set charge rate to 0 to have stock charge logic back)
CIFS support (module, do not mount inside /data, if you rooted with Chainfire SuperSu, make sure you uncheck the namespace separation in SuperSu app)
NFS support (module)
exFat opensource support
NTFS support (module) - read-only
XBox support (module)
OTG-Ethernet support (module)
TCP Congestion changed to Westwood
Multiple additional TCP congestion algorithms available
Swap supported
init.d support (in /system/etc/init.d - set correct permissions!)
Default entropies increased
Automatic EFS backup
Full support for mpdecision for best compatibility and smoothness (no min cpu frequency reset, use Boeffla-Config to configure min frequencies only)
Integrated full busybox 1.24.2 (own compilation)
Kernel initialisation log file (with history of 3 log files)
Emergency reset script automatically placed into /boeffla-kernel-data folder of your internal memory
Presets supported in Boeffla-Config by kernel (Extreme power, power, normal, battery friendly and battery saving)
Updated wifi drivers
Kexec hardboot patch for multirom usage (not supported, not fully working)
Google gcc 4.9 toolchain used for best stability
Always using latest CM Initramfs
Always based on latest CM kernel sources (https://github.com/CyanogenMod/android_kernel_oneplus_onyx)
Note: I do NOT upstream the kernel to higher Linux kernel versions anymore as this usually has zero benefit but likely introduces new issues + is a waste of effort in the end
Download
For all information and downloads (stable AND testing versions), visit the Boeffla-Kernel homepage:
www.boeffla.de
History and design targets
Basically I created my first Boeffla-Kernel in 2012 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. Also it does not aim to have the broadest feature set available everywhere.
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 !!!
These design targets are also valid for the OnePlus kernel here!!!
This said, I will definitely NEVER implement:
things I do personally not need
things I do not like
things that are in any way dangerous
anything which is highly experimental
f2fs - it is known to cause various issues and compatibility problems
custom hotplugging algorithms
a CAF based kernel
anything that requires upstreaming of kernel parts to a higher kernel major version
So do not even ask for it if it falls into the listed categories. Everything else I am happy to check and decide.
And: I do not really care about benchmark numbers, they say almost nothing as long as something is not completely wrong. Important for me is the feel-good factor.
I am also not interested in gaming at all, so never expect a gamer kernel. It will just not happen...
Compatibility
To reiterate it again: Flash the correct kernel depending on whether you are using CM or another rom !!!
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.
You need at least version 2.2.42 or higher for the OnePlus X Boeffla Kernels.
Donation
If you like my work, feel free to donate: Donation-Link
If you donate at least 2,49 EUR (to be in line with the donation app prices on Google Play store), you will receive a personal donation code which unlocks some nice little comfort functions in Boeffla-Config V2 on top.
Source code
All sources can be found in my Github repository: http://github.com/andip71
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:
* ZaneZam
* Grarak
* Yank555
* Hardcore
* Chainfire
* AndreiLux
* Netarchy
* Gokhanmoral
* Simone201
* Mialwe
* Entropy512
* Faux
* Harunjo
* FranciscoFranco
* Ak
... 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 your custom recovery and safely store your personal data before you flash a new kernel.
Cheers and enjoy
Andi
Latest change logs:
CM14
http://kernel.boeffla.de/oneplusx/boeffla-kernel-cm/cm14.0/changelog.htm
CM13
http://kernel.boeffla.de/oneplusx/boeffla-kernel-cm/cm13.0/changelog.htm
Configuration and profile thread
http://forum.xda-developers.com/oneplus-x/general/profiles-boeffla-kernel-profiles-t3330187
*** You want my support? Then stick to my rules ***
Guys, I am receiving more and more completely useless support requests in different threads. Useless because people provide nothing to be able to help, not even the minimal possible information they could give.
Hence, I will now remind anyone again on the support guide lines stated here:
http://boeffla.de/index.php/support/support
Also you need to ensure you follow the installation guide lines incl. trouble-shooting stated here:
http://boeffla.de/index.php/support/installation-how-to
And to cut a long story short: If you do not at least provide what I request in the support guide lines, I will IGNORE YOUR REQUESTS IN FUTURE.
Straight and simple. I have enough of people wasting my time just because they are too lazy to write details.
Period.
Also as a reminder:
you use xposed? -> no support, everything is your own issue
you use a custom rom and not the official stock or CM one? -> good luck, you are on your own
you undervolt or overclock? -> have fun, but without my support
Sorry, this might sound harsh (and it is meant to sound harsh), but you cannot imagine about how crappy support requests can be. Stating something does not work is just not enough.
Please consider that!!!
Andi
Am I going to have the first post here ?
Naman Bhalla said:
Am I going to have the first post here ?
Click to expand...
Click to collapse
Oh yes, looks very much like that
You're already making my day a good one, bro. Thanks! Time to play.
jonrodz said:
You're already making my day a good one, bro. Thanks! Time to play.
Click to expand...
Click to collapse
Testing new kernel on RR Rom, till now all seems to work fine :good:
already tested on exodus rom,stucking at booting.So anyone who use exodus rom need not to try.
nihilista said:
Testing new kernel on RR Rom, till now all seems to work fine :good:
Click to expand...
Click to collapse
... on your own risk. Don't report any issues if you have them.
Andi
Lord Boeffla said:
... on your own risk. Don't report any issues if you have them.
Andi
Click to expand...
Click to collapse
No, i won't Just wanted to give a little feedback for those who are interested. Btw, its own risk all the time if developer said its alpha version without support, i know that and hope it won't burn my device
nihilista said:
... i know that and hope it won't burn my device
Click to expand...
Click to collapse
You would be for sure the first one
Andi
@Lord Boeffla
You should update your signature if you have time, I mean if you are still using CM12.1 official nightlies on the one device then idk
hellcat50 said:
@Lord Boeffla
You should update your signature if you have time, I mean if you are still using CM12.1 official nightlies on the one device then idk
Click to expand...
Click to collapse
Yeah, that was VERY outdated meanwhile.
I gave it some rework.
Andi
nihilista said:
Testing new kernel on RR Rom, till now all seems to work fine :good:
Click to expand...
Click to collapse
I'll try it later... Right now l'm on cm13. Tried it on aicp but it bootloops.
jonrodz said:
I'll try it later... Right now l'm on cm13. Tried it on aicp but it bootloops.
Click to expand...
Click to collapse
Yeah... Use Ashwins build. Tameseks and AOKP also work well
Just to report:
I am currently on AOKP with Xposed installed, flashed Boeffla kernel over blu_spark kernel. Didn't encounter any issue so far with zzmove and Battery Yank governor settings.
Will make a full charge and see how battery life is tomorrow.
Thanks, Lord Boeffla, for your work. Greetings from Cologne :good:
orville87 said:
Just to report:
I am currently on AOKP with Xposed installed, flashed Boeffla kernel over blu_spark kernel. Didn't encounter any issue so far with zzmove and Battery Yank governor settings.
Will make a full charge and see how battery life is tomorrow.
Thanks, Lord Boeffla, for your work. Greetings from Cologne :good:
Click to expand...
Click to collapse
Did you start Boeffla-Config once after you flashed the kernel?
Just curious whether it complained about missing mpdecision (bluspark in the past on oos removed mpdecision...).
Only being curious...
Andi
kaixuan_1995 said:
already tested on exodus rom,stucking at booting.So anyone who use exodus rom need not to try.
Click to expand...
Click to collapse
Exodus i guess is AOSP based... N this kernel CM13 based... So!!!!
You can get what i am saying... It will definitely stuck at boot. :fingers-crossed:
Finaly.. I think its now the time to move to CM13
Thanks Lord
Lord Boeffla said:
Did you start Boeffla-Config once after you flashed the kernel?
Just curious whether it complained about missing mpdecision (bluspark in the past on oos removed mpdecision...).
Only being curious...
Andi
Click to expand...
Click to collapse
Yeah, I did, but no complaints about the missing mpdecision. At least there was no popup window or a red text indicating something important.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.*/
Features
You get the usual set of well known tweaks, mods and other improvements. Please check commits of the source repo which will be mentioned below for detailed list of changes. The key ones are -
Live Kernel flashing with backup support for previous kernel - Liverepack implementation of @psych.half is used, which also backs up your previous kernel (boot.img) and other system files which would be changed.
KCAL - A well known display parameters calibration driver for MSM devices, written by @savoca.
Dynamic Fsync 1.2 - We all know what it is about, dont we? Credits - @faux123
ThunderPlug - A hotplug driver by @varun.chitre15.
Kernel Add-on support - For CM based ROM only. More about it in later posts.
More features will be eventually added.
Kernel Adiutor will list 90% of stuff that can be tweaked by the kernel, rest will be mentioned in further posts.
What does not work?
Various display tweaks by Xiaomi like Reading mode etc in MIUI ROMs - That is because Xiaomi did not open source that aspect of the kernel. The same will probably not work on any Kernel that is compiled from source. But thanks to KCAL, this tweaks can be worked around, check further posts.
Compatibility
This kernel is only meant to be flashed on lollipop based MIUI 7/8 ROMs.
This kernel is also compatible with Official CM and other similar source based ROMs.
Version naming
I gave up on maintaining proper versions of a kernel, its lot of hard-work. Instead, naming scheme of CyanogenMod and other prominent ROMs has been used, reflected in the zip naming. LOCAL_VERSION will be same for all versions hence we will talk about versions on date of build basis.
Installation
Make sure the ROM on which you are going to flash is compatible. Once done, simply flash it through TWRP.
Reporting Bugs
In case an error has occurred during flashing, please report it with /sdcard/liverepack.log.
In case of kernel errors, please get me a dmesg.
Feature Requests
I mainly focus on quality rather than quantity. But still, you can request a feature you would like and I will see what can be done.
Download - Here
If you want to download MIUI version, please download the file with no suffix (zd-20160803-kenzo.zip). Suffix will come in the next MIUI update.
If you want to download CM version, please download the file with cm suffix (zd-20150806-kenzo-cm.zip).
Add-ons can be found in Addons folder. Only CM based kernel supports Addons.
Source/ Tools used
Source - https://github.com/TeamButter/android_kernel_xiaomi_kenzo
Toolchain used - Aarch64 4.9 by google
XDA:DevDB Information
ZD Kernel, Kernel for the Xiaomi Redmi Note 3
Contributors
corphish
Kernel Special Features:
Version Information
Status: Stable
Created 2016-08-02
Last Updated 2016-08-06
Reserved
Kernel Addons
There are certain features which some people want in the kernel, whereas others do not want that at all (they even dont want the feature to be present in the kernel ).
So to meet the needs, we would have to maintain to separate kernel builds, one with the feature, one without it.
Which is where kernel add-on comes to play,
Here the users will need to flash the main kernel. Then, if they choose to, they can flash the kernel addon (which generally contains a feature).
If users choose not to, that feature wont be present at all (just as they wanted), whereas for those who flashed the addon, the feature will be present.
It makes lives of both us and users easier, right?
Addons are low in size flashable zips, as the name suggests. You will need to flash addons if you choose to, after flashing the kernel.
Only CM based ROMs support addons, as init.d support is needed, which is not present in MIUI.
Also, by distributing addons, I guarantee that no copyright infringements are made.
Addons available
-Thunderplug
Workaround for Xiaomi's display tweaks
We will use different values for tweaking offered by KCAL. To do that, open Kernel Adiutor and go to 'Screen' page.
Reading mode
Set Blue to 196.
Colour mode: Warm
Set Green to 240, Blue to 208
Colour mode: Cool
Set Red to 208.
You can also tweak contrast values and other stuffs.
If you are not satisfied, feel free to tweak similarly.
Thunderplug
For some reason, TZ app crashes on MIUI, and kernel adiutor does not fully have support for ThunderPlug.
By default, ThunderPlug does sched based hotplugging. Hence stuffs like endurance mode wont work as it only works when hotplugging is done on per-core basis.
To enable hotplug on per-core basis, open terminal and type:
Code:
su
echo 1 > /sys/kernel/thunderplug/hotplug_style
To go back to sched based hotplug:
Code:
su
echo 2 > /sys/kernel/thunderplug/hotplug_style
Reserved
Changelog
20160803
-Fixed -2% battery bug and camera bug on devices shipped with newer hardware.
20160802
-Initial release for MIUI ROMs
Wow, zapdos was my fav kernel on condor, let's see on kenzo xD
Flashed, no problems for now great work :good:
Working great here, thank you, I have one question, Did you implement Adreno idler? Because my gpu is going to 19mhz, and also Can you please explain the sched and per core mods of thunderplug? Thax
It has the bug of the battery of -2%
dmesg: http://pastebin.com/df8fBgme
donalberto17 said:
Working great here, thank you, I have one question, Did you implement Adreno idler? Because my gpu is going to 19mhz, and also Can you please explain the sched and per core mods of thunderplug? Thax
Click to expand...
Click to collapse
No Adreno idler is not implemented yet.
In sched based hotplugging, the load is shared among cores, there are no practical differences with the stock setup.
In per core basis of hotplugging, cpu cores are only plugged in when its really required, otherwise they are off.
mega-samu said:
It has the bug of the battery of -2%
dmesg: http://pastebin.com/df8fBgme
Click to expand...
Click to collapse
Alright, could you tell me when does this happen? When the battery is very low?
And looks like its a well known bug heh?
Ok thank you for your answer, based on your experience wich one it's better? Per-core or sched?
Waiting for CM version, nice work!
corphish said:
Alright, could you tell me when does this happen? When the battery is very low?
And looks like its a well known bug heh?
Click to expand...
Click to collapse
The mistake happens after flash the kernel. I think that it is for that xiaomi the new one put in indicator of battery, in the recent xiaomi.
I leave this post you, for if it can use you as help:
http://forum.xda-developers.com/redmi-note-3/how-to/fingerprint-battery-issues-custom-roms-t3429464
Well I discovered 2 bugs, when I change the style to per-core basis it doesnt stick after a reboot, another bug is when I change to per-core basis the Fingrepint sensor stops working
mega-samu said:
The mistake happens after flash the kernel. I think that it is for that xiaomi the new one put in indicator of battery, in the recent xiaomi.
I leave this post you, for if it can use you as help:
http://forum.xda-developers.com/redmi-note-3/how-to/fingerprint-battery-issues-custom-roms-t3429464
Click to expand...
Click to collapse
Ok. Have you flashed any other ROMs or kernel in which this issue isnt there.
Looks like xiaomi has done quite some changes in kernel since release.
donalberto17 said:
Well I discovered 2 bugs, when I change the style to per-core basis it doesnt stick after a reboot, another bug is when I change to per-core basis the Fingrepint sensor stops working
Click to expand...
Click to collapse
That change wont persist through reboot, you will have to do it everytime, or perhaps write an init.d script. Not any app supports this toggle which can provide set on boot.
And all I can make from this FP sensor issue when per core basis is it requires like all 6 cores to function, because in stock, I never saw any core go offline.
corphish said:
Ok. Have you flashed any other ROMs or kernel in which this issue isnt there.
Looks like xiaomi has done quite some changes in kernel since release.
Click to expand...
Click to collapse
In cm13 santosh with the patch camera fix or in mokee official, does not happen to me.
Nowadays I have the miui 8 of xiaomi.eu, that does not happen with the kernel stock either.
corphish said:
Ok. Have you flashed any other ROMs or kernel in which this issue isnt there.
Looks like xiaomi has done quite some changes in kernel since release.
Click to expand...
Click to collapse
I havn't tried your kernel but as i'm one of people with newer devices that have this problem, i can answer the question
mokee rom doesnt have this problem and the camera fix mentioned in here fixes the problem on CM maybe you can take a look and see what is the fix in that file.
mega-samu said:
In cm13 santosh with the patch camera fix or in mokee official, does not happen to me.
Nowadays I have the miui 8 of xiaomi.eu, that does not happen with the kernel stock either.
Click to expand...
Click to collapse
Alright, I am making a new build and will upload it as soon as its done.
Unfortunately I cant verify whether the battery bug is fixed or not.
Could you flash it and see then?
Thanks both of you for bringing this to my notice.
Let me know if there are any other breakages.
Edit
Here it is - https://www.androidfilehost.com/?fid=24659325368664523
Could you flash this and see? @mega-samu
corphish said:
Alright, I am making a new build and will upload it as soon as its done.
Unfortunately I cant verify whether the battery bug is fixed or not.
Could you flash it and see then?
Thanks both of you for bringing this to my notice.
Let me know if there are any other breakages.
Edit
Here it is - https://www.androidfilehost.com/?fid=24659325368664523
Could you flash this and see? @mega-samu
Click to expand...
Click to collapse
I have just proved it and it continues the bug.
Edit: The camera does not work
Edit2: In the kernel radon they finish of fix.: http://forum.xda-developers.com/redmi-note-3/development/kernel-t3414884/post68012485#post68012485
Enviado desde mi Redmi Note 3 mediante Tapatalk
mega-samu said:
I have just proved it and it continues the bug.
Edit: The camera does not work
Edit2: In the kernel radon they finish of fix.: http://forum.xda-developers.com/redmi-note-3/development/kernel-t3414884/post68012485#post68012485
Enviado desde mi Redmi Note 3 mediante Tapatalk
Click to expand...
Click to collapse
Alright, could you test yet another build soon?
Edit:
Here you go, this build has same name as previous one but they are different build, separately made and uploaded - https://www.androidfilehost.com/?fid=24591000424951734
Also check whether camera works fine or not @mega-samu
corphish said:
Workaround for Xiaomi's display tweaks
We will use different values for tweaking offered by KCAL. To do that, open Kernel Adiutor and go to 'Screen' page.
Reading mode
Set Blue to 196.
Colour mode: Warm
Set Green to 240, Blue to 208
Colour mode: Cool
Set Red to 208.
You can also tweak contrast values and other stuffs.
If you are not satisfied, feel free to tweak similarly.
Thunderplug
For some reason, TZ app crashes on MIUI, and kernel adiutor does not fully have support for ThunderPlug.
By default, ThunderPlug does sched based hotplugging. Hence stuffs like endurance mode wont work as it only works when hotplugging is done on per-core basis.
To enable hotplug on per-core basis, open terminal and type:
Code:
su
echo 1 > /sys/kernel/thunderplug/hotplug_style
To go back to sched based hotplug:
Code:
su
echo 2 > /sys/kernel/thunderplug/hotplug_style
Click to expand...
Click to collapse
if i change to echo1 fingerprint sensor is misbhaving ... one finger works other doenst and also a little bit of irresponsiveness
sasaboor64 said:
if i change to echo1 fingerprint sensor is misbhaving ... one finger works other doenst and also a little bit of irresponsiveness
Click to expand...
Click to collapse
Yeah I realized that.
Looks like all CPU cores are needed for it properly function.
As in stock all cpu cores are always on, I never saw anyone go off.
I might remove hotplug in next build.
Hello!
I want to introduce my first custom kernel for the Essential PH-1. This is based of several sources, I cherry-picked commits to make improvements to the stock LOS kernel. I'm not a developer, but i really like to port stuff over .
Kernel is suitable for AOSP based ROMS such as RR/AICP/CARBON/LOS etc... If you want to request for specific features, let me know and i'll do my best to bring them over.
Special Features:
Updated to lastest LOS Stock Kernel
Added a few governors like: cultivation / impulse
added a few IO Schedulers: Maple
Kcal Color Control driver
USB Fast Charge - pending will be added in R2
SafetyNet Patch (Bypass bootloader unlocked check)
Dynamic Fsync control
a little Overclock - will be added in R2
Motorola Quickwake - Will be added in R2
and manny other small fixes (you can check the commits in the sources)
Download
Disclaimer: I am not responsible if you use this and brick your device or if your device blows up, implodes, flames start shooting from it or it kills your neighbor's dog. Flash at your own risk. I am not responsible.... It was the other guy... I swear....
Latest Release: SMF-Kernel R2
Known issues:
05.17.2018 - CPU Freq don't always stick, known issue caused by other drivers. Phone will eventually set your frequencies, dont' panic.
Installation:
Obviouly you have a Unlocked Bootloader since you're running a custom rom (make sure to never lock your bootloader in this state)
Boot into Bootloader (adb reboot Bootloader)
If you want to root flash the "Magisk" version of the kernel, it's been prerooted with the latest Magisk Beta available.
Code:
fastboot flash boot SMF-Kernel-R1-Magisk.img
reboot
If you want to manually root, first flash twrp, then from twrp flash the 'non magisk' version and after that flash the magisk zip.
Special Thanks to:
jcadduono
franciscofranco
bedalus
lord_boeffla
flar2
sultanxda
...and many others from whom i cherry pick commits... Sorry if I forgot to mention anyone!
XDA:DevDB Information
SMF-KERNEL, Kernel for the Essential Phone
Contributors
jimbo77
Source Code: https://github.com/Jimbo77/android_kernel_essential_msm8998
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: R1
Stable Release Date: 2018-05-17
Created 2018-05-17
Last Updated 2018-05-17
Changelog 05.23.2018
Enabled Motorola QuickWake Driver - This will enable system to do checks or syncs without fully resuming the device, main objective is battery life.
Enabled Dynamic Sync Control by default
OverClock
USB Fast Charge to up 900ma (Original is 500ma)
Disabled Gentle Fair Sleepers
Enabled Boefla Wakelocks - Check the ammount of wakelocks you can block now!
Enabled Wireguard
Enabled several TCP Options - "Westwood" is enabled by default
Min/Max Brightness options is now configurable as well, to avoid the screen go too dim or to bright.
Somehow camera has been fixed! haha
Changelogs 05.17.218
Updated to lastest LOS Stock Kernel
Added a few governors like: cultivation / impulse
added a few IO Schedulers: Maple
Kcal Color Control driver
SafetyNet Patch (Bypass bootloader unlocked check)
Dynamic Fsync control
and manny other small fixes (you can check the commits in the sources)
Reserved
Looks awesome! I'll give it a try soon!
(For anyone wondering about overclocking the CPU, he committed some changes to the github that would apply this and it should appear in the next revision of the kernel.)
Just installed and so far it's buttery smooth.
WARpig5 said:
Just installed and so far it's buttery smooth.
Click to expand...
Click to collapse
I'm glad is running fine for you!
Good stuff, thanks for this! Could you tell me a little more about cultivation? I can't seem to find much information online about it
Also a request, if possible vibration level control would be super appreciated
pantherking said:
Good stuff, thanks for this! Could you tell me a little more about cultivation? I can't seem to find much information online about it
Also a request, if possible vibration level control would be super appreciated
Click to expand...
Click to collapse
I found Cultivation to be really great in terms of perfornance. It's a little bit agressive with the CPU so you get buttery smooth experience with Screen On but it may cost a few % on battery at the end of the day. The good thing is that it has specific tunables and you can set a low cpu freq for when the screen is off.
Specific details from its developer:
-based off of caf 4.4 commits
-uses per-pcu timers
-use state_notifier for screen off timer
option to set different timer rate when screen off
-improrted fastlane with threshold from blu_active
In regards of vibration control. It should be there. I'm using EX Kernel Manager and i can see the vibration option under "Miscellaneous"
jimbo77 said:
I'm glad is running fine for you!
Click to expand...
Click to collapse
Thanks for this. It's running amazing so far. Performance has been great and I'll see how battery life is, but so far it's great.
I can't wait for further updates. I really wanna see what Moto quickwake is haha
jimbo77 said:
In regards of vibration control. It should be there. I'm using EX Kernel Manager and i can see the vibration option under "Miscellaneous"
Click to expand...
Click to collapse
Thanks for the info on cultivation, I don't mind trading some battery life for butter so I'm using it now
For the vibration control, it doesn't actually work/stick. I've tried kernel auditor and EX Kernel Manager. To be fair, so far it has only worked on LOS and I think invisiblek may have rewritten the stock controller or something so no worries if it isn't a high priority haha
pantherking said:
Thanks for the info on cultivation, I don't mind trading some battery life for butter so I'm using it now
For the vibration control, it doesn't actually work/stick. I've tried kernel auditor and EX Kernel Manager. To be fair, so far it has only worked on LOS and I think invisiblek may have rewritten the stock controller or something so no worries if it isn't a high priority haha
Click to expand...
Click to collapse
I'll take a look at the latest commits but I've used the latest los kernel base so I'm not sure why is not sticking maybe it needs rom support too (not sure honestly) hahaha
I've been testing R2 since yesterday. Will update after y he weekend!
Just out of curiosity, was anything involving the camera done to this kernel? I am now able to record videos without the bug, on any of the affected ROMs, with this kernel.
stompysan said:
Just out of curiosity, was anything involving the camera done to this kernel? I am now able to record videos without the bug, on any of the affected ROMs, with this kernel.
Click to expand...
Click to collapse
Nothing related to camera. Are you sure it works with no issues?
What roms have you tested?
jimbo77 said:
Nothing related to camera. Are you sure it works with no issues?
What roms have you tested?
Click to expand...
Click to collapse
So far, AICP and LOS, both with Essential camera app and GCAM port, HD and 4K, 30 and 60 fps where applicable. Issues presented before flashing very consistently, and so far I have been unable to replicate after flashing this kernel.
stompysan said:
So far, AICP and LOS, both with Essential camera app and GCAM port, HD and 4K, 30 and 60 fps where applicable. Issues presented before flashing very consistently, and so far I have been unable to replicate after flashing this kernel.
Click to expand...
Click to collapse
Sp you were right. Honestly don't know what happened but I installed the latest RR (clean install) put R2 on top of it and bam recording works as you mentioned lol..
I guess it was a lucky strike!
after flashing the kernel with magisk, stuck on "AICP is starting"
is this normal?
update: the phone works but no magisk (pre root) after flashing the kernel.....
sinkoo1979 said:
after flashing the kernel with magisk, stuck on "AICP is starting"
is this normal?
update: the phone works but no magisk (pre root) after flashing the kernel.....
Click to expand...
Click to collapse
Hey!
Have you booted once and setup everything before flashing the prerooted image?
I've had that error but having all set and then flashing the image will get me rooted. Try to see if you can find magisk manager in the apps list from the settings if you do, reboot and there will be magisk
Double post... Sorry
jimbo77 said:
Hey!
Have you booted once and setup everything before flashing the prerooted image?
I've had that error but having all set and then flashing the image will get me rooted. Try to see if you can find magisk manager in the apps list from the settings if you do, reboot and there will be magisk
Click to expand...
Click to collapse
Thank you for the reply.
the phone was running AICP and I wanted root so I flash the kernel. I can't find the magisk manager or in the settings about magisk. I guess you have to clean install from the beginning to get the root. Thank you for the Kernel
sinkoo1979 said:
Thank you for the reply.
the phone was running AICP and I wanted root so I flash the kernel. I can't find the magisk manager or in the settings about magisk. I guess you have to clean install from the beginning to get the root. Thank you for the Kernel
Click to expand...
Click to collapse
Shouldn't. If you flashed the prerooted magisk image try downloading the magisk manager app manually from xda and see if magisk works
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this kernel
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.*/
RZ Kernel aims for as stock experience as possible. It is made from Samsung's stock kernel with stability updates thanks to great guys who made ELS (exynos-linux-stable) branch
It also attempts to increase overall multitasking performance while maintaining good battery life with proper settings
Features
Adapted new Samsung EMS scheduler from Samsung 4.14 kernel (with 16ms PELT)
Gaming optimizations (reduce heat while maintaining performance stability)
Disabled battery-hogging WAKELOCKS
WireGuard and DriveDroid support
Security patch fixes adapted
Thanks to corsicanu for helping me with initial kernel support
XDA:DevDB Information
RZ Kernel, Kernel for the Samsung Galaxy S9
Contributors
remilia15
Source Code: https://github.com/diepquynh/android_kernel_samsung_universal9810
Kernel Special Features:
Version Information
Status: Testing
Created 2020-04-11
Last Updated 2020-08-27
Download link: Drive folder
CHANGELOG:
20200412: Initial release
20200823 [FINAL]: Post #10
Notices and Q&A
The kernel is based on tw10-android-4.9-q branch of ELS, which is currently at stable state from my experience
Other related features of the kernel were picked from other sources. Credits belong to the owner
The kernel's energy costs table is remade in favor of new EMS scheduler
Questions and Answers (Q&A)
Q: AnTuTu scores please?
A: This kernel isn't made for benchmarks so let's not talk about it
Q: My phone gets hot while using this kernel?
A: Short answer: It's your own issue, fix it yourself. Nobody makes a kernel just to burn your hands
Long answer:
Install Termux app from Play Store
Enable screen rotation, open Termux in landspace mode
Type this command: su -c top -d 2
A list of processes will appear and refresh with 2s interval. Find which process consumes the most CPU usage with [%CPU] column and the package name in ARGS column. You should see the culprit of your issue
Reminder: There is no such thing as "I have nothing in background but the phone still heats up". There definitely something happen and 99% of the time it's some of the rogue apps running in background
Q: Can you add X Y Z feature to this kernel?
A: I want to keep the kernel clean and simple. However, if the feature is really useful, I'll consider adapting it with proper performance check before releasing
Q: Installation procedure?
A: Simply flash the kernel with supported ROM and forget. No Magisk reinstallation needed
Reversed for future usage
Another kernel for S9 devices, awesome.?
Thanks
Updated initial release with latest defconfig base for DTC5 vendor
Limit of downloadings from google...
Hey. Will this kernel Work with dtc4 vendor?
Build kernel from scratch
I need help with building kernel outside of android build system.
I have downloaded sources from here: https://github.com/LineageOS/android..._universal9810 , installed cross-compiler, configured with "make exynos9810-starlte_defconfig", build with "make". For now I have file arch/arm64/boot/Image .
How to build correct dtb and pack it with the Image file to bootable image?
Thank you.
Second public build is coming, and this will be the final build of the kernel project!
We have been going through lots of ups and downs in the testing group, so here are the results
Changes:
Fixes zram on boot
Adapted a new kernel scheduler, supporting 32/64-bit task scheduling
Critical scheduler performance fixes
Adapted newer vendor support
As this is the final build of the whole kernel project, I'd like to say thank you to all supporters/developers who helped me improving the kernel. The whole project hasn't lasted long, but it was a great time. This and the RZ Kernel project for Exynos 8895 will also be abandoned, unfortunately
Once again, thank you for all your support!
remilia15 said:
Second public build is coming, and this will be the final build of the kernel project!
We have been going through lots of ups and downs in the testing group, so here are the results
Changes:
Fixes zram on boot
Adapted a new kernel scheduler, supporting 32/64-bit task scheduling
Critical scheduler performance fixes
Adapted newer vendor support
As this is the final build of the whole kernel project, I'd like to say thank you to all supporters/developers who helped me improving the kernel. The whole project hasn't lasted long, but it was a great time. This and the RZ Kernel project for Exynos 8895 will also be abandoned, unfortunately
Once again, thank you for all your support!
Click to expand...
Click to collapse
Arigathanks! I've been using the kernel for quite sometime and I like how it's underclocked by default. What device would you be moving to?
Sad to see such a nice kernel getting abandoned.
What needs to be done to keep it updated and relevant? Would love to keep it alive.
Using this kernel with havoc os, all is good as a daily driver battery life with this combo is awesome
Revontheus said:
Arigathanks! I've been using the kernel for quite sometime and I like how it's underclocked by default. What device would you be moving to?
Click to expand...
Click to collapse
I'm still using my daily driver (S8+) and currently don't have plans buying any other devices
BackToAndroid said:
Sad to see such a nice kernel getting abandoned.
What needs to be done to keep it updated and relevant? Would love to keep it alive.
Click to expand...
Click to collapse
Perhaps you can clone my kernel repo and do something with it. The most contemplating thing is to handle future vendor updates from Samsung. The kernel might go unbootable on latest One UI at some point, so someone must be doing the stock defconfig update (that's the least requirement to boot One UI ROMs with newer vendor)
Hmmm....Usually I can verify that the kernel has been installed by checking it's build date. But it still shows the same like before. I'm running official LOS and flashed the kernel in LOS recovery. According to the log it went fine. Maybe it doesn't work with that recovery?
Edit: Ok, in TWRP it works fine.
Anyone tried using with the latest vendor / security patch? I'm on Alexis ROM 1.8 would love to continue using this kenel.
BackToAndroid said:
Anyone tried using with the latest vendor / security patch? I'm on Alexis ROM 1.8 would love to continue using this kenel.
Click to expand...
Click to collapse
It works without issues for the most part except for USB C audio output which stutters compared to stock kernel.
BackToAndroid said:
Anyone tried using with the latest vendor / security patch? I'm on Alexis ROM 1.8 would love to continue using this kenel.
Click to expand...
Click to collapse
I tried it. Some tweaks not working like showing download speed and reverted back the old power menu (no emergency call) which is baked in the rom and the settings menu changes like 2 battery options in the menu. One is fixed at maximum power saving and cant change while another is on the device health or something which can be change. I also found that sometimes it ramps up the clocks without any reason i still manage to get 4.5-5.3hrs of sot with light usage. The chrome is unusable since it bugged out like its inverted color and cant see sh*t.
BackToAndroid said:
Anyone tried using with the latest vendor / security patch? I'm on Alexis ROM 1.8 would love to continue using this kenel.
Click to expand...
Click to collapse
Just flashed it - seems to work fine with 1.8
UweRammelt said:
Just flashed it - seems to work fine with 1.8
Click to expand...
Click to collapse
How was the standby drain? What twrp did you use? I used 3.4.0.0 of TWRP. The chrome is super dark and cant see. Can you confirm this or im an isolated case? Do you think its because of not using twrp 3.3.1.1 that bugged mine? Hope you can help me. Thanks!