Veno Kernel for Huawei HI6250 devices
Note: I'm waiting for Huawei to release new kernel sources with Nougat, until then I'll focus on fixing any bugs people find. New features will come with Linux 4.1.
The goalTo provide better battery life and more smoothness to your everyday experience, but without sacrificing one in the name of the other (so no +smooth/-battery tweaks and vice versa).
Maybe some extra features? I don't know, I hate unnecessary bloat that provides nothing to everyday user (or even developer).
Okay, so what's in?
Based on latest Huawei VNS sources from January 2017
Turns out newest sources are unstable, I rebased the kernel on 2016 release
Patched to 3.10.105 upstream
Built using Linaro 6.3 toolchain
DM Verity disabled
UKSM 0.1.2.6 (backported from Linux 4.0)
BFQ I/O scheduler
ROW I/O scheduler
Thunderplug hotplugging driver*
Dynamic Fsync
AnyKernel2 package! Compatible with any ROM except stock newer than B336.
For full list of changes see here.
* - Thunderplug is out for now, as it made the device unstable
Installation
Make sure you have TWRP installed
Create backup of your current boot
Flash the zip package (it will modify your boot instead of flashing entire boot.img)
Reboot and enjoy! Look below for how to use additional features
THAT'S A LOT OF CHANGES, BUT I HAVE NO IDEA WHAT I'M READINGA quick ELI5 then:
Patched to 3.10.105 upstream
Newer source = less bugs and better kernel in general.
Built using Linaro 6.3 toolchain
Kernel has extra ARM optimizations and phone is faster/has better battery life.
DM Verity disabled
Big brother won't know that you have fiddled with root.
UKSM
More free RAM and less CPU load, so MORE RAM, PERFORMANCE AND BATTERY LIFE.
BFQ I/O scheduler
ROW I/O scheduler Schedulers
With default settings phone will run smoothly even when you're playing FLAC music, compressing 10 archives of 5GB of music and banging your gf (I can't actually know that)
Dynamic Fsync
When you're using the phone, it cares more about your smooth experience than writing data to disk, so the system seems more responsive.
AnyKernel2 package
Can install on top of anything, Huawei is upgrading to kernel 4.1 with EMUI5 though, so flashing might be going backwards (this is 3.10), at least until they release new sources.
DOWNLOAD AND SOURCE
THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH
REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT,
INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM
LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE
OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
PERFORMANCE OF THIS SOFTWARE.
Source code:
https://github.com/Avsky/kernel_hi6250_vns (unstable sources)
https://github.com/Avsky/android_kernel_huawei_hi6250_nem
Latest release: 2017-05-22
Download: https://www.androidfilehost.com/?w=files&flid=161384
20170406
Rebased on older, more stable Huawei sources (from 2016, everything else is the same)
Removed some of the debugging stuff from the kernel
Enabled Huawei hotplugging driver (it appears to only control big cores tho?)
20170405
UKSM patched to v0.1.2.6 again
Enabled/Disabled a lot of stuff in defconfig
Disabled mostly debugging stuff, which should result in slightly faster kernel.
Enabled a lot of USB drivers (so most stuff should work with Host Mode, if anyone ever uses that)
Enabled some missing Huawei code from older kernel sources, which I believe caused lowmem killer to go haywire, causing heavy apps to randomly close (I tested this one a bit, apps like Snapchat seem to no longer close, can never be sure)
20170404 - BUGFIX attempt
Rolled UKSM back to v0.1.2.3, should help with apps closing without any error
20170330
Removed Thunderplug, as it was causing freezes and bootloops (Huawei HMP doesn't like to have cores offline apparently), system should be stable now
Hotplugging will most likely return, with different driver or when Huawei releases 4.1 kernel sources.
My birthday release, yay, have a stable kernel everyone
20170329
Fix multiple lcd_notify calls
Protect against some hotplug race conditions
Run Thunderplug in per-core mode by default (gotta save the energy!)
Dynamic Fsync (ported to lcd_notify)
Fixes to backported UKSM (possibly fixes binder errors, apps not opening until reboot)
20170325
Initial release
Works with LineageOS 14.1?
---------- Post added at 10:11 AM ---------- Previous post was at 10:10 AM ----------
Or nougat not supported?
RazOne said:
Works with LineageOS 14.1?
---------- Post added at 10:11 AM ---------- Previous post was at 10:10 AM ----------
Or nougat not supported?
Click to expand...
Click to collapse
Yes, I'm running it on LOS 14.1 right now.
If somebody could test it on stock and EMUI5 ROMs (just for the heck of it, keep backup) I'd be grateful.
Sent from my VNS-L21 using Tapatalk
Installed succesfully on L31 running Resurrection Remix nougat. I will try for a few days and report back feedback
Will try it on EMUI 5 as soon as I have time.. very happy to see our device is getting devs' attention, keep up the good work!
Good afternoon. Your modification will work on EMUI 4 ?
thank you
upd.: on EMUI 4 it worked
http://cs5-1.4pda.to/9967169/Screenshot_2017-03-26-14-54-33.png?e28279d161430a29fd16f793d314a066
Hello
I have tested on vns-l31c636b361 (nougat), it does not start blocking your device is booting now ....
(I think I forgot the root)
I will re-try with but I get it with dload c636b170.
New try, l31c636b170 (emui 4) + twrp meticulus, ok :good:
Flashed it more than a day ago, working great on LineageOS 14 (VNS-L31), yet to find any issues...
Wat does it really do haha? Saw "whats in" but dont really know what that means hahaha.
Are you planning to add other CPU/ GPU governors?
uspy said:
Are you planning to add other CPU/ GPU governors?
Click to expand...
Click to collapse
It's something I'd like to do at some point, but there are very few governors which are properly adapted to octacore devices and none so far worked out of the box with Huawei kernel. I'm keeping my eye mostly on ElementalX and Impulse, but they'll need changes to even compile.
For now stick with interactive, next release with thunderplug enabled by default will bring better battery life.
Sent from my VNS-L21 using Tapatalk
It's really nice to hear that you are working on it. Thanks for your reply.
20170329 release
New release is out! Note that I wasn't running on a new build for very long, so issues might still surface, keep a watch on this thread.
Changes:
Fix multiple lcd_notify calls
lcd_notifier call was implemented in wrong section of Huawei LCD driver, oops.
Protect against some hotplug race conditions
Stability fixes mostly, based on ThunderZap kernels.
Run Thunderplug in per-core mode by default (gotta save the energy!)
Due to how scheduling works in Huawei kernel, it might keep one or two big cores up after heavy load, but should be fine once the screen is turned off.
Dynamic Fsync (ported to lcd_notify)
I moved Dynamic Fsync (thanks faux123) to lcd_notify to avoid kernel bloat from powersuspend or earlysuspend (which are not present in the kernel).
Fixes to backported UKSM (possibly fixes binder errors, apps not opening until reboot)
My derp in commiting changes might have caused critical fail in Android Binder, which resulted in random reboots and new apps not opening. Tell me if anyone encounters it.
Overall this release should bring much better battery life and smoothness to the system (mostly thanks to dyn fsync).
Download: https://www.androidfilehost.com/?fid=673368273298943375
Settings crash, dialer crashes when dialing any number after flashing latest release.
Anyway to unflash, or fix this? I didn't do a twrp backup prior to this, but I did do a cache/dalvik wipe after flashing.
Will a factory reset fix this? Or maybe just wipe /system in twrp?
I'm running stock b170 on vnsl21, meticulus twrp, rooted with magisk. I also have systemless xposed installed, maybe there's a conflict?
zgomot said:
Settings crash, dialer crashes when dialing any number after flashing latest release.
Anyway to unflash, or fix this? I didn't do a twrp backup prior to this, but I did do a cache/dalvik wipe after flashing.
Will a factory reset fix this? Or maybe just wipe /system in twrp?
I'm running stock b170 on vnsl21, meticulus twrp, rooted with magisk.
Click to expand...
Click to collapse
Ask someone for stock boot.img or extract it from huawei image.
Also logs, I need logs.
Avsky0 said:
Ask someone for stock boot.img or extract it from huawei image.
Also logs, I need logs.
Click to expand...
Click to collapse
So then, would a fastboot flash boot boot.img work to uninstall the kernel?
edit: I was just about to instal catlog to provide logs, while going for another round of dalvik/cache wipe and guess what - it seems everything is ok now. Will keep you posted if any issues arise.
zgomot said:
So then, would a fastboot flash boot boot.img work to uninstall the kernel?
Click to expand...
Click to collapse
Yes, that's how you flash kernel images. Also keep backup next time.
Sent from my VNS-L21 using Tapatalk
Also a question if I may. Would this kernel provide any benefits over the stock one if I don't install Kernel Adiutor and change any of the settings - basically just flash it and forget it?
edit: 2 questions if you could be so kind as to indulge me.
Does this modify haptic feedback? As it seems to me - either that or I'm crazy - that keyboard haptic feedback is different after flashing this. It's weaker and a little strange (?), however, navbar haptic feedback and other vibrations seem to be the same as with the stock kernel.
Thanks for your time
further edit for feedback: The fingerprint sensor is a bit iffy now. It's considerably slower sometimes, and generally slower and doesn't always vibrate on unlock, like 9/10 times it doesn't vibrate.
I flashed today's build and I noticed that only one core was active, and I can't turn on more than 4 cores so I can basically use 2 little and 2 big cores. Is this as it should be expected?
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.
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
Kirisakura-Kernel for the Pixel 3 and Pixel 3 XL
Hello everyone,
To keep it short: Here is Kirisakura - Kernel for the Pixel 3 aka Blueline and the Pixel 3 XL aka Crosshatch, together Bluecross.
I would appreciate if everybody that flashes the kernel, reads at least once through this opening post and the following ones.
Kirisakura - Kernel is designed to bring a handful of beneficial features to the device, while ensuring excellent performance and smoothness to get you safely through the day!
This project aims to keep most of the subsystems updated, way ahead of the stock kernel, thereby improving security and performance, while keeping stability as the focus during testing! This includes Linux-Stable, CAF-Upstream and kernel/common.
If reading about upstream in the paragraph above got you curious,have a read about Linux-Stable and why it is important here. The stable-process is not the same for every subsystem, but the general idea, rule of thumb and benefits are applicable for other subsystems as well.
Quick explanation of CAF-Upstream. CAF is short for Codeaurora-Forums. This is the place where development from Qualcomm for their SoCs happens. This includes the Snapdragon 845 that´s built into Pixel 3 and Pixel 3 XL.
The kernel-bases available on the Codeaurora-Forums, are basically the foundations OEMs use, to build their own kernel additions on top for devices featuring Qualcomm SoCs.
The Qualcomm developers push regular updates to the bases of the different SoCs, a bit similar to how Linux-Upstream works. OEMs usually stop updating the initial base after the phone is released.
This kernel focuses amongst the other features to provide the latest CAF-Updates merged in a regular manner, to provide updates, improvements and enhancements for SoC specific drivers and subsystems! This might take a while, because a lot of device specific testing is done on my end to ensure stability.
The EAS implementation is heavily updated with changes from CAF, kernel/common and other improvements.
To have a read about our scheduler, which is called EAS, take a look here:
https://developer.arm.com/open-source/energy-aware-scheduling
Main Features:
- Based on latest kernel sources from Google, Kernel is made for Android 12 (Android S)!
- Linux-Stable-Upstream included to latest 4.9.317
- compiled with prebuilt Clang 13.0.1 from Google and built with -O3 optimizations
- ZRAM patched up to latest kernel/common state and use ZSTD LZ4 as default compression algorithm to improve memory managment (more info see this post regarding the earlier switch to ZSTD) and this post regarding the switch back to LZ4
- fixes the magisk freezes caused by f2fs-stable
- Safety Net patches are included -> Kernel passes Safety Net
- Wake Gestures from @flar2 included
- Flashing the kernel will keep root!
- Tested to work on custom ROMs
- Flashable via EXKM and FKM on a rooted system!
- AnyKernel3 powered by @osm0sis (big thanks!)
EAS related features:
- EAS implementation patched up to latest CAF state
- Schedutil is patched up with kernel/common and CAF patches to improve performance and efficiency!
- Memory Leaks inside EAS are fixed
- disable autogroups and use cgroups for more efficient task placement!
- Enable sched_min_task_util_for_boost_colocation feature from CAF
CPU related features:
- Power saving workingqueues enabled by default (toggleable in EXKM)
have a read here: https://lwn.net/Articles/731052/
this complements EAS in general
- Change various drivers (WLAN, MM, audio, charger, power, thermal, glink etc) to user power efficient workingqueues. This should work well in conjunction with EAS
- improved Schedutil governor
- Add hold functionality to schedtune CPU boost
- WQ_HIGHPRI for the IO and crypt workqueues (replaces googles approach with a better upstream one)
- cpufreq/times vastly improved
File System related features:
- Include rapid GC by @arter97 ( best thing is to read the commit description linked here. I compared GC on stock google f2fs, upstreamed f2fs and f2fs with rapid GC. Rapid GC is the most effective, followed by upstreamed f2fs.)
- Set the bio REQ_NOENCRYPT flag (When lower layers such as dm-crypt observe the REQ_NOENCRYPT flag, it helps the I/O stack avoid redundant encryption, improving performance and power utilization. )
Usability related features:
- High Brightness Mode for increasing backlight level related to brightness accessible via EXKM app
- High Brightness Mode for just boosting display to max level accessible via EXKM app
- Vibration Intensity adjustable via EXKM app
- Backlight dimmer functionality included (adjustable via EXKM App)
GPU related features:
- KCAL to control the display
- KLAPSE integrated
- KCAL/KLAPSE: changes safety measures -> allow completely disabling two RGB values (this was requested to, for example, only have red values on night dimming)
- Enabled NAP power saving state of Adreno 630
- improve GPU profiling for improved rendering performance (1,2 , 3 )
- Update GPU driver to latest CAF state
Network related features:
- Wireguard Support (Details)
Memory related features:
- Enable Userspace LMK/freak07/Kirisakura_bluecross/commit/aac453635549699c13a84ea1456d5b0e574ef855"]2[/URL])
- Patch up kernel LMK backend (PSI) with kernel common upstream
- ZRAM patched up to latest kernel/common state and ZSTD LZ4 as default algorithm. (information can be found in this post regarding the switch to ZSTD, which is now reverted) and this post regarding the switch back to LZ4
- possibility to use lzo-rle as default ZRAM compression algorithm (more information here and there )
- possibility to use zstd as default ZRAM compression algorithm!
- Speculative Page Faults (1. 2)
- Fix various memory leaks in different subsystems
- Reap memory of a task that receives sigkill
- various other changes from mainline
Sound related features:
- Adjust microphone gain via sound control in EXKM
- Adjust speaker gain via sound control in EXKM
Security related features:
- CFI and LTO both kept intact and are used to keep additional security Google implemented for us!
- Shadow Call Stack
- built with latest clang found on google repo
Misc Features:
IO-Schedulers:
- cfq
- maple
- deadline
- noop
- tripndroid
- fiops
TCP Congestion Algorithms:
- advanced algorithms enabled
- includes new bbr and sociopath tcps
Wakelock Blocker:
- advanced wakelock blocker with the ability to block any wakelocks (dangerous, use with caution)
- please read this for further info
Other features:
- enable some additional Sony and XBox controllers
- add support for steam and nintendo switch controller
- patches to loop device, xfrm and usb gagdet
- disable logging to make the kernel more lightweight in various places
- add support so you can enable faster charging for non pixel wireless charging stands (use at your own risk, disabled by default, how to enable here)
Feature section for the "non visible" but perceptible improvements:
- updated binder section (responsible for interprocess communication)
- updated sdcardfs ; have a read about it here:
Requirements
- unlocked Bootloader
- USB-Debugging in developer options enabled
- latest adb and fastboot binaries
- working adb and fastboot environment
How to flash the Kernel:
1. Download the kernel.zip to your device. Make sure your device is rooted properly, with the magisk version suiting your current firmware version.
1a. Optional: While it may not be necessary all times, you may want to restore stock boot.img, reroot with magisk and optionally install twrp.zip if coming from another kernel. Before reporting issues make sure you do that! Thank you!
2. Flash the kernel.zip via either a kernel manager app capable of flashing kernels or TWRP if available. Make sure whatever method/app you decide to use, supports your current Android Firmware. Apps/Recoveries need to be possibly updated for firmware updates!
It´s your job to ensure compatability.
Flashing the kernel will preserve root.
3. Reboot and profit! Before reporting any issues make sure to read the Release-Post of Bluecross_Q_Release_1.0.0!
DOWNLOAD:
Download is located in these respective folders:
Android 9:
Downloads for : -Android- Generic Device/Other | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
Android 10/11:
Downloads for : -Android- Generic Device/Other | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
Android 12:
Downloads for : -Android- Generic Device/Other | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
Important: Read after Download
Please take a look at the second post after flashing the kernel!
Changelog:
Android 9 / Pie Kernels
1.0.0 Initial Release
1.5.0 https://forum.xda-developers.com/showpost.php?p=78151322&postcount=81
1.5.1 https://forum.xda-developers.com/showpost.php?p=78154423&postcount=112
1.7.0 https://forum.xda-developers.com/showpost.php?p=78196945&postcount=190
1.7.1 https://forum.xda-developers.com/showpost.php?p=78220526&postcount=227
1.7.2 https://forum.xda-developers.com/showpost.php?p=78221906&postcount=228
1.8.0 https://forum.xda-developers.com/showpost.php?p=78249473&postcount=267
1.8.1 https://forum.xda-developers.com/showpost.php?p=78280355&postcount=285
1.8.2 https://forum.xda-developers.com/showpost.php?p=78316038&postcount=345
1.8.3 https://forum.xda-developers.com/showpost.php?p=78330435&postcount=389
1.8.4 https://forum.xda-developers.com/showpost.php?p=78364541&postcount=451
1.8.5 https://forum.xda-developers.com/showpost.php?p=78377334&postcount=481
1.8.6 https://forum.xda-developers.com/showpost.php?p=78396058&postcount=538
1.8.7 https://forum.xda-developers.com/showpost.php?p=78420137&postcount=591
1.8.8 https://forum.xda-developers.com/showpost.php?p=78449511&postcount=621
1.8.9 https://forum.xda-developers.com/showpost.php?p=78496196&postcount=654
1.9.0 https://forum.xda-developers.com/showpost.php?p=78564181&postcount=701
1.9.1 https://forum.xda-developers.com/showpost.php?p=78637123&postcount=758
1.9.2 https://forum.xda-developers.com/showpost.php?p=78672005&postcount=775
Milestone 2.0.0 https://forum.xda-developers.com/showpost.php?p=78689028&postcount=782
2.0.2 https://forum.xda-developers.com/showpost.php?p=78761004&postcount=853
2.0.3 https://forum.xda-developers.com/showpost.php?p=78767857&postcount=867
2.0.4 https://forum.xda-developers.com/showpost.php?p=78805387&postcount=896
2.0.5 https://forum.xda-developers.com/showpost.php?p=78838240&postcount=928
2.0.6 https://forum.xda-developers.com/showpost.php?p=78840488&postcount=936
2.0.7 https://forum.xda-developers.com/showpost.php?p=78851682&postcount=953
2.0.8 https://forum.xda-developers.com/showpost.php?p=78898745&postcount=981
2.0.9 https://forum.xda-developers.com/showpost.php?p=78913421&postcount=991
2.0.10 https://forum.xda-developers.com/showpost.php?p=78950068&postcount=1007
2.0.11 https://forum.xda-developers.com/showpost.php?p=78975193&postcount=1025
2.0.12 https://forum.xda-developers.com/showpost.php?p=79009799&postcount=1041
2.0.13 https://forum.xda-developers.com/showpost.php?p=79043694&postcount=1067
2.0.14 https://forum.xda-developers.com/showpost.php?p=79050238&postcount=1103
2.1.0 https://forum.xda-developers.com/showpost.php?p=79136483&postcount=1182
2.1.1 https://forum.xda-developers.com/showpost.php?p=79159209&postcount=1221
2.1.2 https://forum.xda-developers.com/showpost.php?p=79190516&postcount=1261
2.1.3 https://forum.xda-developers.com/showpost.php?p=79214430&postcount=1279
2.2.0 https://forum.xda-developers.com/showpost.php?p=79291045&postcount=1372
2.2.1 https://forum.xda-developers.com/showpost.php?p=79332619&postcount=1452
2.2.2 https://forum.xda-developers.com/showpost.php?p=79425173&postcount=1531
2.3.0 https://forum.xda-developers.com/showpost.php?p=79463560&postcount=1569
2.4.0 + 2.4.1 https://forum.xda-developers.com/showpost.php?p=79505198&postcount=1623
3.0.0 https://forum.xda-developers.com/showpost.php?p=79533358&postcount=1641
3.1.0 https://forum.xda-developers.com/showpost.php?p=79570912&postcount=1685
3.1.1 https://forum.xda-developers.com/showpost.php?p=79575209&postcount=1698
3.1.2 https://forum.xda-developers.com/showpost.php?p=79578541&postcount=1722
3.1.3 https://forum.xda-developers.com/showpost.php?p=79612212&postcount=1743
3.2.0 https://forum.xda-developers.com/showpost.php?p=79658098&postcount=1774
3.3.0 https://forum.xda-developers.com/showpost.php?p=79696166&postcount=1807
3.3.1 https://forum.xda-developers.com/showpost.php?p=79736674&postcount=1829
3.3.4 https://forum.xda-developers.com/showpost.php?p=79791144&postcount=1857
3.4.0 https://forum.xda-developers.com/showpost.php?p=79919877&postcount=1929
3.4.5 https://forum.xda-developers.com/showpost.php?p=80023518&postcount=2064
Legacy Downloads for Pie Kernels: https://www.androidfilehost.com/?w=files&flid=285183
Android 10/ Q Kernels
1.0.0 https://forum.xda-developers.com/showpost.php?p=80269185&postcount=2132
1.1.3 https://forum.xda-developers.com/showpost.php?p=80324259&postcount=2199
1.2.0 https://forum.xda-developers.com/showpost.php?p=80533347&postcount=2291
1.2.2 https://forum.xda-developers.com/showpost.php?p=80809357&postcount=2325
1.3.0 https://forum.xda-developers.com/showpost.php?p=81115229&postcount=2451
1.4.0 https://forum.xda-developers.com/showpost.php?p=81418351&postcount=2519
1.4.1 https://forum.xda-developers.com/showpost.php?p=81421719&postcount=2529
1.5.0 https://forum.xda-developers.com/showpost.php?p=81684289&postcount=2582
1.5.1 https://forum.xda-developers.com/showpost.php?p=81947785&postcount=2607
1.5.2 https://forum.xda-developers.com/showpost.php?p=82213193&postcount=2635
1.5.3 https://forum.xda-developers.com/showpost.php?p=82484463&postcount=2642
1.5.4 https://forum.xda-developers.com/showpost.php?p=82742517&postcount=2688
1.5.5 https://forum.xda-developers.com/t/...ixel-3-xl-aka-bluecross.3864563/post-84424203
Android 11
2.0.0_R https://forum.xda-developers.com/showpost.php?p=83554503&postcount=2753
2.1.0_R https://forum.xda-developers.com/showpost.php?p=83649655&postcount=2808
3.0.2_R https://forum.xda-developers.com/showpost.php?p=84007163&postcount=2906
3.0.4_R https://forum.xda-developers.com/t/...ixel-3-xl-aka-bluecross.3864563/post-84230135
3.0.5_R https://forum.xda-developers.com/t/...ixel-3-xl-aka-bluecross.3864563/post-84605183
3.0.6_R https://forum.xda-developers.com/t/...ixel-3-xl-aka-bluecross.3864563/post-84812093
3.0.7_R https://forum.xda-developers.com/t/...ixel-3-xl-aka-bluecross.3864563/post-84975703
3.0.8_R https://forum.xda-developers.com/t/...ixel-3-xl-aka-bluecross.3864563/post-85166867
3.0.9_R https://forum.xda-developers.com/t/...ixel-3-xl-aka-bluecross.3864563/post-85298651
3.1.0_R https://forum.xda-developers.com/t/...ixel-3-xl-aka-bluecross.3864563/post-85432093
Android 12
4.0.0_S https://forum.xda-developers.com/t/...ixel-3-xl-aka-bluecross.3864563/post-85808391
4.1.0_S https://forum.xda-developers.com/t/...ixel-3-xl-aka-bluecross.3864563/post-86249089
5.0.0_S https://forum.xda-developers.com/t/...ixel-3-xl-aka-bluecross.3864563/post-86413291
5.1.0_S https://forum.xda-developers.com/t/...ixel-3-xl-aka-bluecross.3864563/post-86541411
5.1.1_S https://forum.xda-developers.com/t/...ixel-3-xl-aka-bluecross.3864563/post-87007931
Donations:
Donations are not mandatory but very welcome if you want to support development or just buy me a coffee
If you like my work: http://paypal.me/freak07
Credits:
@osm0sis for all his work, including the ak3 installer!
@tbalden for being the best HTC wingman!
@LeeDroid for his awesome roms!
@Captain_Throwback for all the mentoring and guidance!
@Eliminater74 for bringing me into the game and the Inspiration
@nathanchance for his upstream guidance and assistance
@RenderBroken for helping me out
@flar2 for all his work
@joshuous for all the help he provided to me in the past!
@topjohnwu for magisk!
@Sultanxda for all of his work!
Contributors
Freak07
Source Code: https://github.com/freak07/Kirisakura_bluecross/
FAQ
Important: What to do if you face issues on Android 10/Q
You might face issues on Android 10 like non working sensors, edge sense not working properly or similar things.
Here´s a thread that has more info about it: https://forum.xda-developers.com/pixel-3-xl/how-to/android-10-sensors-bug-t3964904
This also caused seemingly in a random fashion issues with magisk modules not unpacking properly when you flash them via magisk manager.
I recommend everybody who faces symptoms of random issues, which they cannot explain, to completely nuke their device and flash a factory image with -w intact, as to complete set up the device from scratch.
This will wipe your whole phone, so backup videos, photos, music, apps and other stuff you don´t want to lose!
@jcmm11 and me were hunting this magisk bug for a week and it turned out it´s connected to the above mentioned issue, although it gets more prominent by the latest CAF - EAS changes, which are merged in my kernel. Probably due to the way tasks get handled a bit differently.
Please everybody keep this in mind, before reporting back.
Question: Upon flashing the kernel zip I got a message that there is an error with ramdisk. What to do?
Answer:
Procedure to fix the ramdisk issue:
The ramdisk error is now fixed. Please take a look at this post from @osm0sis for more information:
Big thanks to @osm0sis and @topjohnwu for everything at this point here! And everyone else that helped in the process!
Important:
What do you have to do to get finally rid of the ramdisk error?
1. Flash back a stock clean boot.img either for stock rom or the custom rom you´re on. (not a backup from some time ago, a clean stock boot.img)
Link to stock boot.img from Google´s december factory image for convenience
2. REDOWNLOAD(!) either magisk 18.0 or the latest canary directly from magisk manager and delete all old magisk zips on your device. (this is really important!)
3. Optional: Reinstall twrp.zip if you want to.
4. Flash the redownloaded magisk zip in TWRP
5. Flash my kernel either via TWRP, EXKM App or FKM App
6. Profit
Question: Is root preserved when flashing this kernel?
Answer: My kernel.zip keeps a device rooted by magisk rooted.
Question: How to report bugs properly?
Answer: Have a look at post #3 in this thread. The linked guide is a pretty good starting point.
Before reporting any bug make sure you´re not using any mods, magisk modules, scripts or other modifications that alter various functions like sound mods etc.
Try to describe the issue as detailed as possible! Give your exact setup, like rom, magisk version, kernel version.
Is the issue reproducible? Does it happen frequently?
Provide logs, otherwise debugging is a lot harder. If you can already reproduce the issue and provide logs it greatly limits the amount of time I have to spent until I figure out how to reproduce it.
If the device force reboots/randomly reboots (that means you see the bootloader unlocked screen!) provide a ramoops file.
Easiest way is immediately after booting up, with a root explorer navigate to sys/fs/pstore. Copy the contents to your internal storage, zip it up and send it to me.
If the issue happens while the device is running provide a dmesg plus a logcat that you take while/shortly after the issue happens. This will log what´s running in the current session. Try to be as detailed as possible what´s happening when the issue appears. It will also help me in reading the log!
To easily get a logcat in case of a crash take a look at this post:
https://forum.xda-developers.com/showpost.php?p=79462002&postcount=1566
Big thanks to @jcmm11 for it
Here´s a tasker task to automatically copy /sys/fs/pstore on each boot to internal storage. Be advised these files get also created on correct reboots.
https://forum.xda-developers.com/showpost.php?p=79549126&postcount=1670
thanks @jsauder2 for this little trick
Useful Resources
How to report bugs:
It is incredibly useful if bug reports are done in a proper way. That saves everyones time and will ultimately lead to a faster bugfix (hopefully).
The following guide from @nathanchance is a very good guideline on how to properly report a bug!
https://github.com/nathanchance/Android-Tools/blob/master/Guides/Proper_Bug_Reporting.txt
Gonna give this a go now. Thanks!
Sweet, thank you sir!
Sent from my Pixel 3 XL using Tapatalk
fsync toggle?
How much do the 3 and xl differ on kernel level?
Would this flash and work on the 3?
frewys said:
How much do the 3 and xl differ on kernel level?
Would this flash and work on the 3?
Click to expand...
Click to collapse
Working on mine
RE: " - Flashing the kernel will keep root ! "
Who had done the steps and ( then the pixel ) lived to see to see another happy day ?
( assuming magisk ( root ) is installed and and has been happy for days... )
turn security pin off, fastboot twrp_323 image, twrp the kernel zip, twrp the twrp_323 zip, reboot back into twrp, wipe the cache to see that the finger presses workie, boot to system, re-verify root is okay, buy the man a beer...
May I ask if you could add zram zstd from Pixel 2 XL ? It is a BIG improvement for ram management.
Gesendet von meinem Pixel 3 XL mit Tapatalk
frewys said:
How much do the 3 and xl differ on kernel level?
Would this flash and work on the 3?
Click to expand...
Click to collapse
Kernel is unified, the main difference is the display driver (ftm5 vs sec_touch)
virtyx said:
fsync toggle?
Click to expand...
Click to collapse
I can include it, but I recommend to leave it on. I know several people that suffered from corruption when something unexpected happened and their device shutting down.
I´ll include the toggle but leave fsync on by default, just like the wakelock blocker.
frewys said:
How much do the 3 and xl differ on kernel level?
Would this flash and work on the 3?
Click to expand...
Click to collapse
Chronzy said:
Working on mine
Click to expand...
Click to collapse
thanks for chiming in @frewys
also thanks for confirming it works on the regular pixel 3 too @Chronzy
old_fart said:
RE: " - Flashing the kernel will keep root ! "
Who had done the steps and ( then the pixel ) lived to see to see another happy day ?
( assuming magisk ( root ) is installed and and has been happy for days... )
turn security pin off, fastboot twrp_323 image, twrp the kernel zip, twrp the twrp_323 zip, reboot back into twrp, wipe the cache to see that the finger presses workie, boot to system, re-verify root is okay, buy the man a beer...
Click to expand...
Click to collapse
yeah it works I tested it.
In theory you can flash the kernel "on the go" without a computer and keep root via franco kernel manager. which is pretty handy.
although I only recommend to tinker with pixel phones when a computer is nearby and available. :good:
Komodoketavaran said:
May I ask if you could add zram zstd from Pixel 2 XL ? It is a BIG improvement for ram management.
Gesendet von meinem Pixel 3 XL mit Tapatalk
Click to expand...
Click to collapse
yes that´s one of the things I definitely wanted to try in the nearby future. it was my kernel that firstly introduced it on the pixel 2 xl but memory managment on my unit is not as bad as I saw in some reviews/videos.
Additionally I think the underlying cause, when Pixel 3 cannot hold more than 3 apps in background is a bit different than pixel 2 xl "just having 4gb of ram".
But I´m sure there is room for improvement. Just wanted to use the phone as it is to get a baseline of how it works before I start modifying all sort of stuff.
Freak07 said:
I can include it, but I recommend to leave it on. I know several people that suffered from corruption when something unexpected happened and their device shutting down.
I´ll include the toggle but leave fsync on by default, just like the wakelock blocker.
Click to expand...
Click to collapse
Thank you that'd be great
Freak07 said:
yeah it works I tested it.
In theory you can flash the kernel "on the go" without a computer and keep root via franco kernel manager. which is pretty handy.
although I only recommend to tinker with pixel phones when a computer is nearby and available. :good:
Click to expand...
Click to collapse
Can confirm it's working. I flashed with FK Kernel Manager. Root still intact, Magisk and all still installed.
Worked for me to flash try exkm
Root remainder. Was hoping the kernel would fix an issue with magisk not passing safety net whenever hit the check safety net. It asks me to download. I hit yes and then it fails immediately was like this on stock as well
That would be great. It is very bad on my unit.
On my P2XL there are nearly no redraws with your kernel
Freak07 said:
yes that´s one of the things I definitely wanted to try in the nearby future. it was my kernel that firstly introduced it on the pixel 2 xl but memory managment on my unit is not as bad as I saw in some reviews/videos.
Additionally I think the underlying cause, when Pixel 3 cannot hold more than 3 apps in background is a bit different than pixel 2 xl "just having 4gb of ram".
But I´m sure there is room for improvement. Just wanted to use the phone as it is to get a baseline of how it works before I start modifying all sort of stuff.
Click to expand...
Click to collapse
Gesendet von meinem Pixel 3 XL mit Tapatalk
old_fart said:
RE: " - Flashing the kernel will keep root ! "
Who had done the steps and ( then the pixel ) lived to see to see another happy day ?
( assuming magisk ( root ) is installed and and has been happy for days... )
turn security pin off, fastboot twrp_323 image, twrp the kernel zip, twrp the twrp_323 zip, reboot back into twrp, wipe the cache to see that the finger presses workie, boot to system, re-verify root is okay, buy the man a beer...
Click to expand...
Click to collapse
When I followed those steps my phone would only boot straight to twrp with no touch. Had to flash factory boot.img to get it back.