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.
Related
Introduction
Hello dear developers and android hackers,
On this thread, I will share with you a project I am developing as I am learning kernel programming / hacking. This kernel is based on Sony kernel sources with some enhancements for battery saving and performance.
Click to expand...
Click to collapse
Features
Based on Sony 23.5.A.0.570 kernel sources
Compiled with linaro GCC 4.9.1 toolchain, -O3
Governors : interactive, ondemand, performance, conservative, smartassV2, intellidemand2 and intelliactive.
Fast hotplug
CPU overclock up to 2.8 GHz Thank's to Faux123 and DooMLoRD
Changed GPU frequency table to 27 - 657 MHz Thank's to Myself5
Sony RIC disabled
Undervolt
TWRP recovery included, fota partition support
Breathing notification light thank's to glocklee
Force Fast Charge
KCAL Advanced color control Thank's to savoca
Click to expand...
Click to collapse
Installation instructions
Code:
Use this kernel at you own risk !
I am not responsible for any damage or problem.
Flash the zip via recovery
Reboot
Click to expand...
Click to collapse
Download
Please read FAQ and second post if you have any issue
Recovery flashable zip :
Abricot kernel v8.1.zip
mirror
Kernel Source :
Kernel
Ramdisk
Click to expand...
Click to collapse
Changelog
Abricot kernel v8.1 : 12.05.16
Disable RIC at kernel level (Fixes partition mounting in recovery)
Add KCAL Advanced color control Thank's to savoca
Abricot kernel v8 : 10.05.16
Based on Sony sources 23.5.A.0.570
Updated TWRP to version 3.0.2-0
Abricot kernel v7 : 01.04.15
Updated to Lollipop kernel sources 23.1.A.0.690
Update TWRP to 2.8.5.0
Add Force Fast Charge
Removed splash screen
Abricot kernel v6 : 24.12.14
Fix default freq not applying for all cores at boot
Fix -O3 compiler optimization
Fast hotplug : plug in cores in descending order
Abricot kernel v5 : 15.12.14
Increase voltage of higher frequency for better stability
Add support for displaying the number of tasks running
Add VR, SIO and FIFO schedulers
Add lagfree governor
Update TWRP to 2.8.1.0
Fix scaling_max_freq permissions
Set default frequency to 2.3GHz
Abricot kernel v4 : 11.12.14
Add CPU overclock up to 2.8 GHz (Thank's to Faux123 and DooMLoRD)
Change GPU frequency table to 27 - 657 MHz (Thank's to Myself5)
Disable Sony RIC
Remove msm_mpdecision
Set qcom mpdecision as default
Abricot kernel v3 : 07.12.14
First public release
Check my github to see all the changes.
Click to expand...
Click to collapse
FAQ
Q : With what ROM can I use this kernel ?
A : With any ROM based on Sony stock Marshmallow
Q : Your kernel isn't working / My phone isn't booting anymore
A : Read this whole post once more, search for your problem in thread and report it if you haven't found a solution.
Q : Can I install this kernel on locked bootloader ?
A : No ! This kernel is only for unlocked bootloader.
Q : Does this kernel include recovery ?
A : Yes ! You can access by pressing buttons when the led is lighting. Volume down to go to TWRP and Volume up to load recovery from FOTA..
Q : What are mpdecision and fast hotplug ?
A : This is what manage your cpu cores and decide which core will be online. Fast hotplug is a brand new hotplug that I wrote. See next post for more information
Click to expand...
Click to collapse
Thanks To/Credits
* Sony for their sources and device
* @DooMLoRD
* @thewadegeek for his Tutorial
* @show-p1984 for his mpdecision
* @glocklee for his breating notification mod
* @Envious_Data for his help and links
* @dssmex
* @Androguide.fr for Pimp my Z1
* bbedward
* Erasmux
* faux123
* The xda community for making me discover android and for answering so many of my questions
* Google for kernel sources and its search engine
* Apple for making expensive phone so that I never bought one of theirs
Click to expand...
Click to collapse
Please let me know per pm if there is any mistake or misspelled word in this thread. Automatic correction does a great job but since english isn't my mother thongue I'm pretty sure I made mistakes.
XDA:DevDB Information
Abricot kernel, Kernel for the Sony Xperia Z2
Contributors
pec0ra
Source Code: https://github.com/pec0ra/abricot
Kernel Special Features:
Version Information
Status: Testing
Created 2014-12-07
Last Updated 2016-05-20
About Fast hotplug
Motivation
I wasn't convinced by show-p's msm_mpdecision nor faux123's intelli_plug ( I don't even talk about qcom mpdecision ). I also wanted to start working on a bigger programming project to learn more about kernel developing so I decided to write my own hotplug.
Main features
I tried to make fast hotplug the lightest possible, so that it consumes the less resources possible when it is not needed (mainly at idle). One of the second goals was to make it customizable.
How to use
Deactivate qcom mpdecision (Pimp my Z1 will do this automatically when you choose fast hotplug)
Activate fast_hotplug
Code:
adb shell "echo 1 > /sys/module/fast_hotplug/parameters/fast_hotplug_enabled"
Tune it to your liking
How to configure
Unfortunately, there isn't yet any user friendly application to configure fast hotplug. The only way to configure it is to manually edit the module files with adb or a file editor.
I modified Pimp my Z1 to be compatible with fast hotplug. You can find the modified version at post 12
You can also find all the parameters at
Code:
/sys/module/fast_hotplug/parameters/
and edit them with adb command
Code:
adb shell "echo [COLOR="Navy"]<value>[/COLOR] > /sys/module/fast_hotplug/parameters/[COLOR="Navy"]<variable_name>[/COLOR]"
You can configure the following parameters :
fast_hotplug_enabled : 0 for disabled, 1 for enabled
boost_duration : Duration of boost in ms when screen is touched
threshold_to_boost : Instead of automatically pluging in cores on touch, fast hotplug checks that the load is above this threshold. This avoid cores coming online when reading file or website.
max_cpu_on : Maximum number of online cpu when screen is on
min_cpu_on : Minimum number of online cpu when screen is on
idle_threshold : Threshold under which fast_hotplug will remain almost idle and won't perform any check. This applies when only 1 core is online
plug_in_core_X_threshold : with X between 1 and 3. This is the threshold to plug in coreX.
plug_in_core_X_delay : This is the number of fast_hotplug cycles (see refresh_rate) to skip before pluging in coreX.
plug_out_core_X_threshold : Like plug_in_core_X_threshold but to plug out.
plug_out_core_X_delay
refresh_rate : Time in ms between fast hotplugs checks
screen_off_singlecore : 1 for activated, 0 for deactivated; Allows only one core to be online when screen is off.
If you are using linux, you can easily change the configuration with this small program : https://github.com/pec0ra/fast_hotplug_controller
You will probably want to create init.d script to make your configuration stay after reboot. If enough users want it, I can create an example of script.
Bugs / stability
Due to some conflicts with qcom mpdecision, it is possible that you encounter some bugs / reboots when both are enabled.
Configuration doesn't stick after reboots
Help needed
If you are a java developer (or want to learn ) and want to help in developing an app (or editing an already existing one) to control the hotplug, please send me a pm
Please tell me your impression, your custom configuration and / or your recommendation so that I can make it better in future releases.
Good luck.
Will try as soon as I can. :good:
Welcome! :good:
pec0ra said:
Help needed
If you are a java developer (or want to learn ) and want to help in developing an app (or editing an already existing one) to control the hotplug, please send me a pm
Click to expand...
Click to collapse
Regarding this, there is already an app out there that is FOSS, licensed under the GPLv2 license, looks sexy and should be easy to modify. It's called Pimp My Z1, I think it offers pretty much everything you want.
Other than that, cool that you're developing something new, I'll give it a shot!
Edit:
You may want to disable Sony's RIC it prevents you from writing to /system. This should help you.
I can't seen to get notification breath effect,i didn't do the mpdecision step,so could this make the diference?
Is this kernel compatible with franco kernel apps?
Sent from my D6503 using XDA Free mobile app
B1nny said:
Regarding this, there is already an app out there that is FOSS, licensed under the GPLv2 license, looks sexy and should be easy to modify. It's called Pimp My Z1, I think it offers pretty much everything you want.
Other than that, cool that you're developing something new, I'll give it a shot!
Edit:
You may want to disable Sony's RIC it prevents you from writing to /system. This should help you.
Click to expand...
Click to collapse
Thank you for the link
I'll see if I can do something with this app when I have more time (I've never made any android app).
Disabling ric is a good idea I'll do this for next version.
FrosteezBR said:
I can't seen to get notification breath effect,i didn't do the mpdecision step,so could this make the diference?
Click to expand...
Click to collapse
No, mpdecision won't affect it. Have you tried it on YadliKernel ? Did it work for all the notifications ? It seems like on abricot kernel they work for most of the notifications but not for sms.
vendetta718 said:
Is this kernel compatible with franco kernel apps?
Sent from my D6503 using XDA Free mobile app
Click to expand...
Click to collapse
It is probably compatible (I didn't tried it) but you will probably not be able to change most of the configurations since they are not implemented in my kernel. Some configuration from my kernel (like fast hotplug) are also not implemented in the app so you can't change them from there.
pec0ra said:
Thank you for the link
I'll see if I can do something with this app when I have more time (I've never made any android app).
Disabling ric is a good idea I'll do this for next version.
No, mpdecision won't affect it. Have you tried it on YadliKernel ? Did it work for all the notifications ? It seems like on abricot kernel they work for most of the notifications but not for sms.
It is probably compatible (I didn't tried it) but you will probably not be able to change most of the configurations since they are not implemented in my kernel. Some configuration from my kernel (like fast hotplug) are also not implemented in the app so you can't change them from there.
Click to expand...
Click to collapse
i try with facebook,whatsapp,messaging and gmail
with a led tester its the same blink as stock
would i send you a dsmeg or anything?
FrosteezBR said:
i try with facebook,whatsapp,messaging and gmail
with a led tester its the same blink as stock
would i send you a dsmeg or anything?
Click to expand...
Click to collapse
There's no printing in the mod I think so dmesg would be useless. I'll try again with WhatsApp. Have you tried it on other kernels? Was it working ?
Edit : ok, maybe there is an error... In this case dmesg could be useful. If you have time you can send it, yes.
And I reconfirm that it works for telegram
Hey, can someone show us the notification mod?
Pimp my Z1
As @B1nny suggested, I tried editing Pimp my Z1 to add fast hotplug support. Everything seems to work and I even added some tweaks for a better support for our Z2 ( some default values were not really compatible with our device ). There are probably bugs for configurations other than fast hotplug. If I have time, I will fix them but for now, please use another app to set your frequencies / governors / voltage or live with the bugs. If you have questions about the app, you could also take a look at the official thread to see if it is already there or maybe just to give the dev a thanks.
I'll probably make a pull request to @Androguide.fr with the changes but until then you can use my own build linked to this post. If you already have the app installed, you will have to uninstall it first because signature is different.
You can see the full source and the changes on my github : https://github.com/pec0ra/Pimp_my_Z1
Special thanks to @Androguide.fr for his great app and to @B1nny for his link
@pec0ra
Good news to have a new kernel dev for our beloved Z2 !
However, I've tried to flash your kernel, the flashing process seems to work correctly but actually I stay stuck to the last doomlord advanced stock kernel. Any suggestion ?
nreuge said:
@pec0ra
Good news to have a new kernel dev for our beloved Z2 !
However, I've tried to flash your kernel, the flashing process seems to work correctly but actually I stay stuck to the last doomlord advanced stock kernel. Any suggestion ?
Click to expand...
Click to collapse
You should try to extract the .elf from the zip and flash it via fastboot
Code:
fastboot flash boot <name>.elf
Anyone else experiencing the same issue ? Maybe I did something wrong in my zip.
pec0ra said:
You should try to extract the .elf from the zip and flash it via fastboot
Code:
fastboot flash boot <name>.elf
Anyone else experiencing the same issue ? Maybe I did something wrong in my zip.
Click to expand...
Click to collapse
I think you mean the .img file instead of .elf.
Other than that, the kernel works fine for me. I did manually flash it via fastboot. (because I prefer to flash it via fastboot)
I took a quick look at your updater-script and compared it to Doomlord's updater-script and this is what I found:
Your script tries to write the kernel to this partition:
Code:
/dev/block/platform/msm_sdcc.1/by-name/Kernel
While Doomlord's script writes the kernel to this partition:
Code:
/dev/block/platform/msm_sdcc.1/by-name/boot
Maybe that's the culprit?
B1nny said:
I took a quick look at your updater-script and compared it to Doomlord's updater-script and this is what I found:
Your script tries to write the kernel to this partition:
Code:
/dev/block/platform/msm_sdcc.1/by-name/Kernel
While Doomlord's script writes the kernel to this partition:
Code:
/dev/block/platform/msm_sdcc.1/by-name/boot
Maybe that's the culprit?
Click to expand...
Click to collapse
I was going to post the same thing
Waiting for confirmation...
B1nny said:
I think you mean the .img file instead of .elf.
Other than that, the kernel works fine for me. I did manually flash it via fastboot. (because I prefer to flash it via fastboot)
I took a quick look at your updater-script and compared it to Doomlord's updater-script and this is what I found:
Your script tries to write the kernel to this partition:
Code:
/dev/block/platform/msm_sdcc.1/by-name/Kernel
While Doomlord's script writes the kernel to this partition:
Code:
/dev/block/platform/msm_sdcc.1/by-name/boot
Maybe that's the culprit?
Click to expand...
Click to collapse
Thank you
Yes, I meant .img. It seems like it'll take some time to get used to this new device. The kernel destination you pointed out is probably the issue, yes. And that's probably the notification problem too. Seems like the kernel never got flashed so it's logical that notification mod doesn't work...
I'll change this tomorrow morning
Maybe someone can test it until then.
pec0ra said:
Thank you
Yes, I meant .img. It seems like it'll take some time to get used to this new device. The kernel destination you pointed out is probably the issue, yes. And that's probably the notification problem too. Seems like the kernel never got flashed so it's logical that notification mod doesn't work...
I'll change this tomorrow morning
Maybe someone can test it until then.
Click to expand...
Click to collapse
Yes, this was indeed the issue, I've just succesfully flashed your kernel changing "Kernel" to "boot" in the script.
Now testing
I can't rename mpdecision.. I tried with root explorer and root browser
sh4d1t0 said:
I can't rename mpdecision.. I tried with root explorer and root browser
Click to expand...
Click to collapse
That's due to Sony's RIC being enabled by default. If you look at my previous post where I mention it there is a command you can run in ADB to temporarily disable it, not ideal but it will help you rename the file.
** 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.
Thunderoar Kernel For SM-T113
(Tab 3 Lite 7.0 Wifi)
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards, corrupted partition, nuclear disasters
* Please do some research before using this mod!
* YOU are choosing to make these modifications,
* If you point the finger at me for messing up your device, I will laugh at you.
Features:
Overclocked
Deferred Timer for KSM
USB Fast Charge
Arch Power
Frandom
Powersuspend for battery life/saving
QuickWakeup for battery life/saving
Dynamic Sync Control
Fsync control on/off
Voltage Tweak
NVS hibernate driver
Multicore Power Saving
Schedule workqueues on awake CPUs to save power
CPU Boost
Adaptive Low Memory Killer
Software CRC control toggle
Gentle Fair Sleepers toggle
and so on...
CPU Hotplug:
AutoSMP
Added CPU governors:
Sprdemand
Conservative
Ondemand
Userspace
Powersave
Interactive
Performance
and so on...
Planned Update
-nothing i guess (but u can suggest somethin to me that possible)
Bugs(s)
-No MORE BUG!
Custom kernel Installation:
Download the kernel from here
Choose the tar.md5 if flashing from odin
Choose the zip files if flashing from custom recovery
Choose the latest version
Odin Instruction:
Open any version of odin
Choose your tar.md5 file from AP Tab
And Start
Custom Recovery Instruction:
Reboot into recovery if usin zip files (recommended to make a nandroid)
Flash the kernel zip
Reboot and enjoy!
Stock kernel Installation:
Download the stock kernel from here
Enter recovery mode, choose install, choose install image,
and then go to the directory of your downloaded stock kernel
choose it and then check mark on the boot circle.
And then flash it
Notes:
20/12/2107
Kernel Update!!
Thunderoar-Kernel 5.0 Codenamed "Angel Beats!"
Fix all issues regarding MTP not working
and random reboot, is this a comeback? xD, i don't know xD
It appears that my kernel uses a lot more memory than i expected,
Possibily some problem with memory patch in the kernel source
The workaround for this problem is you have to increase your disksize
In the kernel adiutor, if it stays at 300mb, it will not enough and cause a problem
Which is stuck or complete crash of device. Recommended size is 500mb or more if
you encountered it again and set swappiness into 60
XDAevDB Information
Thunderoar Kernel, Kernel for the Samsung Galaxy Tab 3 7.0
Contributors
@Thunderoar
Credits:
@Osm0sis-For the Anykernel2
@stathis95194-For the stock kernel
Github:
Kernel source
Version Information
Status: Stable
Current Stable Version: Angel Beats! || 5.0
Stable Release Date: 2017-12-24
Created 2016-12-26
Last Updated 2017-12-24
Press the "Thanks" button if you appreciate my work or if i helped you
Changelog:
V5.0 Codenamed "Angel Beats!" (2017-12-24)
+Kernel upstream version 3.10.17->3.10.108
+Gpu update
+Fix MTP
+CPU Frequency change 200MHz upto 1.5GHz
+Entropy Update
+Multicore Power Saving
+CPU Boost
+Arch Power
+Power Suspend
+Quickwakeup
+Read-ahead set to 512kB
+Adaptive Low Memory Killer
+Software CRC control
+Gentle Fair Sleepers
+Fsync On/Off
+Built from scratch and fixed random reboot
+Dynamic Fsync
-Removed Obselete Cpu Governor
-Removed Obselete I/O Scheduler
-Removed UKSM and use normal KSM
V4.1.1 update (2017-7-5)
+Fix some devices not booting
+New CPU Hotplug: AutoSMP
V4.1 update (2017-7-3)
+Just another update for stability
V4.0 update (2017-7-3)
+No more Reboot or similar effect - Tested
+Linux kernel downgraded into 3.10.32 temporarily because rebuilt from scratch
+Auto cpu boost on input without predefined frequency
+UKSM(Ultra Kernel Samepage Merging)
+LZ4 Z-RAM - Faster Memory
+Asynchronous Fsync -Faster storage management
+USB Fast Charge are back
-Removed cpu governor: OndemandX, Zzmoove, Scary *Temporary*
V3.4 update (2017-6-22)
+The most stable kernel that i've ever built
+Linux Kernel 3.10.44
+No more frequent reboot or similar effect
+Bug fixes
V3.3 update (2017-6-17)
+Linux Kernel 3.10.40
+Properly fix the bug that mentioned on the v3.2 update and lower the risk of instability
+A bunch of cpu governor
*Hotplug
*Lionheart
*Reworked version of intelliactive
*Ondemandplus
*OndemandX
*Hyper
*Zzmoove
*Nightmare
*Wheatley
*Badass
*Scary
*All of them are properly functioning and tuned for compatibility
and if you want the hotplug features, use the hotplug governor provided
+Bug Fixes
-Adaptive cpu governor removed parmanently
V3.2 update (2017-6-8)
+Update: Linux Kernel 3.10.37
+Update: Using the latest Anykernel2 zip
+Update: Minimum frequency change into 254MHz and also voltage change for nice battery lasting
+Update: cpu-boost set to 765MHz and running for 3 seconds when touch detected
+Update: Set CFQ as default scheduler
+Fix: Bug that cause long running app either in the background or foreground to freeze/lagging/reboot etc.
+Fix: Bug that cause the device to reboot randomly
+Fix: Bug that cause the graphic being not working/properly lagging or some sort
+Fix: Bug that cause the device to reboot or freeze when standby
+Fix: Bug that causing the kernel to working improperly/lagging/rebooting/unstable after a while
+Bug fixes
V3.1 update (2017-5-7)
+CPU Frequency minimum change -> 384MHz
+Fix Frequency bug stuck at 768MHz
+Faster charging
V3.0 update (2017-5-7)
+Kernel version updated from 3.10.22 - > 3.10.26
+Using updated Anykernel zip
+Frequency: changed into 1600Mhz and minimum is 386Mhz
+GPU: function updated
+Deferred Timer working as it is
+LZ4 compression
+"Schedule workqueues on awake CPUs to save power" are back
+Remove conflict between Samsung touch booster and my CPU-Boost so you can actually set the amount you want
for boost
+Sync threshold for cpu-boost are not set
+I/O scheduler default to deadline
+Fsync are on by default
+TCP Congestion Algorithm set default to Westwood which is the fastest for network usage
+Additional TCP Congestion Algorithm are added
+Additional tweak to make the kernel faster
+Camera Fix!!!
+MTP Function (unconfirmed)
+A whole lot of bug fixes
-sprdemand governor
-Fastcharge (for now)
V2.8 update (2017-1-31)
+Frequency: changed into 1660Mhz and minimum is 580Mhz
+Cpu-boost: defined stable values
+Less OS tearing
+Fastcharge updated
+Audio functionality improved
+Voltage: change for low-power use
+Many bug fixes
+Selinux: updated
-Automatic Cpu Hotplug: removed for better stability but with little to no battery drainage but you still can deactivate the cores through Kernel Adiutor
-Sprdemand: removed
V2.6.1-MR1 update (2017-1-1)
*Note:This is maintenance release therefore some features may temporarily unavailable
Add: cpu-boost currently disabled but provided as an option
Add: voltage change
Add: frequency change from 386Mhz to 1600Mhz for more stable
FIx: serious bug that causing switching off mobile data make it freeze/crash
Fix: bug that causing the device freezing/crash throughout all my kernel update release
V2.6 (2016/12/27)
+Initial release
After flashing all apps start to crash.
Jimbus369 said:
After flashing all apps start to crash.
Click to expand...
Click to collapse
Quick note on the crashing apps.
T113XXU0APE2: Does not have this issue
T113XXU0APH5: When I use this ROM, than indeed everything goes bananas after booting up the tablet.
Before flashing the kernel I advice to disable all unnecessary services and with that I mean everything with Samsung in the name and also all of the google apps you don't use. It seems that com.google.process.gapps is causing a crash chain reaction so do disable this services as first. I'm using lucky Patcher for disabling services and for those who are unfamiliar with this my advice is to not uninstall an app but first disable it and later when you are satisfied you than may safely uninstall the unwanted app/service.
Bugs
Camera doesn't working
My apps continue to crash in the latest version Also after a Dalvik wipe.
Build: T113XXU0APH5
Jimbus369 said:
My apps continue to crash in the latest version Also after a Dalvik wipe.
Build: T113XXU0APH5
Click to expand...
Click to collapse
All the app?
Thunderoar said:
All the app?
Click to expand...
Click to collapse
Yes, all apps.
This is extremely exciting and can't wait to try it out!
Build T113XXU0APA5
Will let you know how it goes....
Wanted to ask (not that it's a huge deal) is there init.d support in this kernel?
If so do I need to do anything special to enable it?
Going to go ahead with it anyway and see what happens!
Thunderoar said:
* If you point the finger at me for messing up your device, I will laugh at you.
Click to expand...
Click to collapse
Better start laughing, 'cause my finger's pointing directly at you! And also twitching slightly out of frustration!
....Nah, it's all good. :highfive: I screwed things up all on my own by getting flash-happy. :crying:
On the plus side: It worked GREAT! :highfive: Thanks so much for putting this together for us tiny-tab users, you did a great job.
Not only did Byron (my T113's name) run smoother and faster than I've seen yet (yay!), but suddenly Mounts2SD had no issues whatsoever. Up till now it's been a supreme struggle to get /sd-ext to mount properly, to be used properly, etc. etc. - but after flashing this kernel, on first boot boom, everything just worked. Without changing anything I'd already done.
Should have just left it the way it was, eh? But noooo, I had to go "try something else" and made a stupid mistake somewhere, and now no combination of ROM / kernel / nandroid backup (meticulously organized and annotated) is booting up. I even lost TWRP for a little bit.... As penance for my sin of wanting "more", I've gotta dig up Odin, go back to stock, and start from scratch.
SO! QUESTION FOR YOU! (OR ANYBODY REALLY....)
When I fire up Odin and restore the official stock ROM (eg from Sammobile or Samsung), does that include the stock kernel too?
If the stock kernel IS a separate file, where should I look? (Your OP for the T116 kernel includes a link for that model, but not OP in here. I'm sure I can find it on my own but right now I'm just whiny.)
Not going to wait for an answer/s before moving ahead, but any response here will serve as documentation for myself and others in future!
(How don't we have a smiley for "pointing finger"? There's at least TWO in Unicode but I'm too lazy to go get it right now....)
PushyPhoenix said:
When I fire up Odin and restore the official stock ROM (eg from Sammobile or Samsung), does that include the stock kernel too?
Click to expand...
Click to collapse
Yes, it will revert itself to its normal condition such as stock rom, stock kernel and everything
PushyPhoenix said:
If the stock kernel IS a separate file, where should I look? (Your OP for the T116 kernel includes a link for that model, but not OP in here. I'm sure I can find it on my own but right now I'm just whiny.)
Click to expand...
Click to collapse
The kernel is in the md5 file or in the zip file, named boot.img
That's awesome to know, and came to the same conclusion when stock setup started asking personal questions and wanted a wifi password. Rooting it this very moment, though if I'd waited *just* a little longer I wouldn't have to. Wow you're fast!
That boot.img file info will come in handy when I screw up on any ROM, thanks! This one is going ASAP into a safe and accessible place for "just in case"....
Hey, I've always wondered and maybe you can tell me:
When flashing this type of file in recovery or adb, does the filename matter? If I rename it "T113-[build]-boot.img" for example, will anything go wrong?
Feel free to point me elsewhere to learn more about how these things work, I've followed a lot of guides but want to understand the "why" as well.
Sent from my SM-G900W8 using XDA Labs
PushyPhoenix said:
That's awesome to know, and came to the same conclusion when stock setup started asking personal questions and wanted a wifi password. Rooting it this very moment, though if I'd waited *just* a little longer I wouldn't have to. Wow you're fast!
That boot.img file info will come in handy when I screw up on any ROM, thanks! This one is going ASAP into a safe and accessible place for "just in case"....
Hey, I've always wondered and maybe you can tell me:
When flashing this type of file in recovery or adb, does the filename matter? If I rename it "T113-[build]-boot.img" for example, will anything go wrong?
Feel free to point me elsewhere to learn more about how these things work, I've followed a lot of guides but want to understand the "why" as well.
Click to expand...
Click to collapse
I do believe that when flashing a boot.img through TWRP with the image flasher, the file needs to say boot.img I may be wrong but I had issues before when I changed the name of the file to keep track of which one it was....lol... I have since started putting the boot.img files in their own folders with the appropriate name on the folder.
By the way, great to see development on this tablet. I am going to be testing this kernel in a personal build and see if I can squeeze as much out of it as I can get. So thank you dev.. Awesome work and greatly appreciated. : )
glockman4519 said:
I do believe that when flashing a boot.img through TWRP with the image flasher, the file needs to say boot.img I may be wrong but I had issues before when I changed the name of the file to keep track of which one it was....lol... I have since started putting the boot.img files in their own folders with the appropriate name on the folder.
Click to expand...
Click to collapse
That's a great idea... Ugh, adding another folder to the folder full of folders on my computer frightens me. But if that's what it takes!
Sent from my SM-G900W8 using XDA Labs
---------- Post added at 11:28 PM ---------- Previous post was at 11:23 PM ----------
Thunderoar said:
Yes, it will revert itself to its normal condition such as stock rom, stock kernel and everything
Click to expand...
Click to collapse
So I've run into a bit of a problem. Tried outFyrestone ROM and i love it, but it's based on PH5 firmware and doesn't play nice with your wonderful kernel. Which means my sd-ext is broken...
I know you're very busy (and I haven't a clue what kind of work is required), but wondered if you know when we can expect to see an update?
Thanks so much for all your hard work!
Sent from my SM-G900W8 using XDA Labs
PushyPhoenix said:
That's a great idea... Ugh, adding another folder to the folder full of folders on my computer frightens me. But if that's what it takes!
Sent from my SM-G900W8 using XDA Labs
---------- Post added at 11:28 PM ---------- Previous post was at 11:23 PM ----------
I get it, it clutters things s bit. But I am one who like an organized setup anyways so adding more folders is common for me. It may not be everyone's cup of tea so to speak.
But on my PC and in my external SD , on my tablet, I have a folder named tab "what ever", then inside there are folders named mods, ROMs, kernels and then gaops. In the kernel folder I have sub folders for just this reason and those folders will have the kernel name on it and then inside will be the standard "boot.img"..
It works for me and above all, works for TWRP.
Click to expand...
Click to collapse
First of all, sincere thanks for replying; this advice may help others as well
glockman4519 said:
PushyPhoenix said:
Ugh, adding another folder to the folder full of folders on my computer frightens me.
Click to expand...
Click to collapse
I get it, it clutters things s bit.
Click to expand...
Click to collapse
My apologies for not being more clear on what exactly 'frightens' me about this idea. There have been times when I've backed things up this way and couldn't get into them again because of the number of characters in the path and file name - they were just too long!
Mind you, this was tens of years ago on WinXP and it never occurred to me to try finding a fix.
But on my PC and in my external SD , on my tablet, I have a folder named tab "what ever", then inside there are folders named mods, ROMs, kernels and then gaops. In the kernel folder I have sub folders for just this reason and those folders will have the kernel name on it and then inside will be the standard "boot.img"..
Click to expand...
Click to collapse
That's a fantastic system, very similar to the one I'm now using, and will add new folders as you've suggested. Hopefully reading this will benefit those who are new to this world so they don't wind up with folders full of mysterious files and untagged backups for various devices, that made perfect sense at the time. (Like the one folder for my first few devices, which now looks like gobbledygook....)
Lollipop ROM for T113 (Samsung Tab 3 lite "7 wifi-only)
Topic:
Lollipop ROM for T113 (Samsung Tab 3 lite "7 wifi-only)
Is there any lollipop/marsmallow/Nougat ä ROM that works in my T113 (Samsung tab 3 lite "7)? This device runs natively Android 4.4.4, but I Really need Android 5 or higher! Lollipop would do just fine.. I took a look at most popular custom roms to this device, but most were 4.x.x.. And nothing for t113! And all of those were to T221 or so, in the list they're were few supporting T110/T111, but now T113. Does those work in this T113? Isn't it just same device?
Please tell me if you have any idea of rom with Android 5 or newer that works in this T113!
It would be awesome to have Lollipop-Slimrom or Resurrection remix with Android 5/6/7..
Even Stock Lollipop would be adequate, android 4 lacks important features...
There's many roms to this device, but they are for T2XX or T110/T111... Does any of those run in t113?
I have already rooted this tablet and installed TWRP.
Thank you so much for help in advance! Any information that gets me closer to have Lollipop or newer is very very much appreciated!
Sincerely,
tatu-o aka. mlc
PushyPhoenix;[email protected] said:
SO! QUESTION FOR YOU! (OR ANYBODY REALLY....)
When I fire up Odin and restore the official stock ROM (eg from Sammobile or Samsung), does that include the stock kernel too?
If the stock kernel IS a separate file, where should I look? (Your OP for the T116 kernel includes a link for that model, but not OP in here. I'm sure I can find it on my own but right now I'm just whiny.)
Click to expand...
Click to collapse
1.Yep
2.The stock kernel is in the md5 file which is boot.img, the md5 file I mentioned is in the stock rom
I guess I double answered this question, my bad :silly:
PushyPhoenix said:
Hey, I've always wondered and maybe you can tell me:
When flashing this type of file in recovery or adb, does the filename matter? If I rename it "T113-[build]-boot.img" for example, will anything go wrong?
Click to expand...
Click to collapse
It varies, sometimes when flashing thing through adb or recovery with filename had a space in it, it would not detect it cuz the name is spaced and separated and it didn't recognize it as a file cuz the file extension doesn't connected to the name cuz it separated/spaced.
Thunderoar said:
I guess I double answered this question, my bad :silly:
Click to expand...
Click to collapse
Hahaa, thought it sounded familiar! No problem, better to get the answer multiple times than not get an answer at all.
---------- Post added 01-29-2017 at 12:01 AM ---------- Previous post was 01-28-2017 at 11:59 PM ----------
Thunderoar said:
It varies, sometimes when flashing thing through adb or recovery with filename had a space in it, it would not detect it cuz the name is spaced and separated and it didn't recognize it as a file cuz the file extension doesn't connected to the name cuz it separated/spaced.
Click to expand...
Click to collapse
Good to know! I've had so many issues over the years, with spaces in filenames, that any renames for files like this get an underscore or dash instead of spaces. Helps in lots of other ways, too.
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