Related
Current release: Version 2.0 (stable) [09/06/2012]
SOURCE CODE: Available at GitHub
*WARNING PLEASE USE AT YOUR OWN RISK*
DISCLAIMER
FIRST OF ALL THIS IS NOT AN OFFICIAL KERNEL, IT IS NOT SUPPORTED BY OFFICIAL CM10 ROMS OR ANY PREVIEW ROMS.
ONCE YOU INSTALL THIS KERNEL YOU WILL NOT BE SUPPORTED IN THE CM10 / CM9 OFFICIAL/UNOFFICIAL DEVELOPMENT THREADS
OF ANY FORUM i.e XDA, SLATEDROID, etc.. THIS MEANS THAT YOU MUST NOT REPORT ANY ANDROID / CM BUGS TO THE ORIGINAL
COMMUNTIY THREADS FOR THE ROM YOU USE! YOU MAY HOWEVER REPORT ANY CM/ANDROID/KERNEL RELATED ISSUES TO THIS THREAD ONLY!
Click to expand...
Click to collapse
Features
CPU Overclocking up to 1500mHz (default is set at stock 1000mhz)
Stable GPU Overclock @ 450mhz (scales from 300 - 450)
Userspace CPU undervolting support
Brick prevention/precaution - disabled MMC_CAP_ERASE function from kernel
I/O Schedulers: BFQ, CFQ, SIO, DEADLINE, NOOP, V(R) (Default VR as of v1.3 - prior to 1.2 default = deadline)
Autogroup Scheduler patched to work with Android via User ID task grouping
CPU Governors: Lionheart, SavagedZen, Lazy, Scary, Intellidemand, LagFree, Wheatley, Lulzactive, SmartAssv2, Interactive, Ondemand, Powersave, Userspace, Performance (depending on ROM - interactive governor is usually set as default gov from userspace during init)
ARM libs from Linux 3.x (v2.0+)
Android Drivers from Linux 3.x (v2.0+)
Linux Security from Linux 3.x (v2.0+)
Cleancache + Zcache Support (v2.0+)
Working Zram - to enable see instructions below (v2.0+)
Fixed Video driver glitches (v1.4+)
Cleaned up tons dmesg errors and warnings (v2.0+)
Memory management fixes and patches from 3.x (v2.0+)
Alsa SoC Tiny HAL patch for better compatibility with Jelly Bean and ICS (reduces/eliminates popping sounds)
Plus various other improvements to kernel configuration and code.
Downloads: (if anyone experiences issues downloading from the androidfilehost mirrors please contact [email protected] to notify of outage as requested by afh admin, thanks!)
Current Stable:
Code:
[URL="http://goo.im/devs/godmachine81/a100_kernel/gm-a100-v2.0-signed.zip"]version 2.0[/URL]
Previous Releases:
Code:
[URL="http://beta.androidfilehost.com/?fid=9390062577138008066"]version 1.5[/URL]
[URL="https://github.com/downloads/godmachine81/Acer-A100-JellyBean-Custom-Kernel/godmachine-a100-kernel-v1.3a-signed.zip"]version 1.3a[/URL]
[URL="https://github.com/downloads/godmachine81/Acer-A100-JellyBean-Custom-Kernel/godmachine-a100-kernel-v1.2b-signed.zip"]version 1.2b[/URL]
[URL="https://github.com/downloads/godmachine81/Acer-A100-JellyBean-Custom-Kernel/godmachine-a100-kernel-autogroup-v1.1-signed.zip"]version 1.1[/URL]
[URL="https://github.com/downloads/godmachine81/Acer-A100-JellyBean-Custom-Kernel/godmachine-a100-kernel-autogroup-v1.0.1b-signed.zip"]version 1.0.1b[/URL]
[URL="https://github.com/downloads/godmachine81/Acer-A100-JellyBean-Custom-Kernel/godmachine-a100-kernel-autogroup-v1.0.1-signed.zip"]version 1.0.1[/URL]
[URL="https://github.com/downloads/godmachine81/Acer-A100-JellyBean-Custom-Kernel/godmachine-a100-kernel-autogroup-v1.0-signed.zip"]version 1.0-pre[/URL]
Tools:
Code:
[URL="https://github.com/downloads/godmachine81/Acer-A100-JellyBean-Custom-Kernel/toggle-ag.sh"]toggle-ag[/URL] Tool to Enable/Disable Autogroup and check the status.
'toggle-ag' now included with kernel zip as of 1.3a and is located at /system/xbin/toggle-ag - You may run from a terminal or create Script Manager widgets for each of the script arguments:
Code:
toggle-ag status
toggle-ag on
toggle-ag off
toggle-ag help
Please remember that this script has to be ran as root if you plan to enable/disable autogroup, however you may run as regular user to check the status or get the help dialog.
Important info on toggle-ag script usage (from the script comments):
#**Please note that toggling back and forth the scheduler will
#produce undesired effects, as it takes the system a few minutes
#to switch the process scheduler each time effectively. Imagine
#all processes that run in the backround are rearranged each time
#you switch the process scheduler. In other words you shouldn't
#toggle back and forth to make comparisons as they WILL NOT be
#effective immediately!!
Click to expand...
Click to collapse
Goo Manager Support (NEW!)
You can now download my custom kernels, recovery, tweaks, etc from Goo Manager, available on the Play Store. Goo Manager is similar to ROM Manager, except it works very well with my release of TWRP 2.2.2.0.
First time use instructions:
Set Download path to: /sdcard/goomanager/ in "Settings" (This is important as the location on Android and TWRP need to both be exact same!)
Go back to the main screen in Goo Manager and click Browse Compatible Roms
Choose 'godmachine81'
For kernels choose a100_kernel (you are welcome to look around in my other directories)
Choose the release you wish to download
Choose 'begin download'
You will see a notification for 'Download Finished' - Tap on it
It will prompt you to Select Zip(s) to flash, you may choose more than 1!
After you have selected all the zips you want to flash, go to the option 'Order and flash selected' or if you want to add a zip from a custom location, choose the 'Add zip from another location option'
Once in the Order and flash menu, it is important that you set the order to flash in the proper order, when you are sure it is right, then click Flash (First time you use Goo Manager, it will prompt you that an OpenRecovery is needed, choose that you already have one)
After You click flash, the system will reboot to TWRP, flash your .zip files, and reboot back to android without any user interaction.
ZRAM
What is it?
Zram was developed so that systems with a limited amount of physical ram may allocate a percentage of that to a system swap device using compression. By compressing the data that is in the swap space you can fit more data into the same amount of ram. For example App#1 is consuming 500mb of a total 725mb ram, this leaves you with 225mb free. If you have Zram enabled then App#1 may begin to swap to the zram device, when doing this you will have an advantage, because any amount of data from App#1 that gets swapped out to Zram will be compressed meaning it is actually using less physical ram. So instead of only 225mb free of 725mb you may now end up with something more like 400mb free because data from App#1 is compressed in Zram, in this example thanks to compression you cut the 500mb memory usage of App#1 to 325mb. Zram should have a minimal impact on performance while giving you the benefit of fitting more data into the amount of physical ram your device has.
HOWTO
This kernel includes functional ZRAM support, however to take advantage of it you must enable it from userspace (Android). Cyanogen Mod has an option in Settings > Performance > Memory to enable Zram, however it doesn't properly work - I'm not sure exactly how it is coded in the cm sources, but when you enable zram it doesn't create the zram swap device like it should. To work around this I wrote the following flashable .zip files that contain a script to automatically create the zram swap device at boot, please download and flash the size you wish to allocate to zram:
Zram - 100MB (14% ram)
Zram - 150MB (20% ram)
Zram - 200MB (28% ram)
Zram - 250MB (34% ram)
Zram - 300MB (41% ram)
Zram - 350MB (~50% ram)
To Disable/Remove Zram
In the event that you want to disable Zram then just remove the file(s) at:
/system/etc/init.d/50zram-*
After the 50zram- file has been removed, just reboot your device and you will no longer have Zram enabled. To re-enable just reflash one of the above files.
Flash Back stock kernel?
For those who wanted it: stock-kernel-signed.zip click here to download the stock ICS Kernel - This is the Stock CM kernel from The Android_Device_Acer_A100 Prebuilts on github.
To cut down on general discussion in this thread please note that I have been in the Freenode IRC Dev channel a lot lately. server: irc.freenode.net channel: #iconia-dev - My IRC handle is godmachine81 Join me there for general discussion if you don't mind. Thanks!
Video of Kernel in action on CM10 (appologize for audio and poor quality)
*All references to the Xtreme releases has been removed due lack of time needed to maintain it aside from the stable releases - will update the thread when I Xtreme development gets back underway
ChangeLog:
2.0
Backport several bits mainline code from Linux 3.5 - including Security, ARM Libs, MM, and Android specifics
Zcache + Cleancache added
Ability to concatenate kernel cmdline configuration to Bootloader's cmdline without breaking compatibility with any bootloaders ( needed for zcache/cleancache to work)
Zram patches and updates
Clean up dmesg logs
Deadline IO Sched tweak (1:1 ratio writes/fifo) - VR remains default IOsched
CONFIG: turn off some verbose logging/debugging to reduce overhead, enabled Load Lens Correction Data to smooth out camera operation
TweakIO init script included by default to optimize disk read/write performance
Several other small patches and tweaks to underlying sources
1.6
Minor patches to sources and configuration
1.5
GPU voltage and frequency updates
Interactive governor updated from N7 grouper
Adjust frequency scaling per core for new interactive gov.
1.4
This release was a testing Xtreme release which has recently been removed due to lack of development
1.3a
Script: toggle-ag now included in zip, installs to /system/xbin/toggle-ag
Default IO Scheduler V(R)
Default CPU Governor Lulzactive
1.2b
Bug Fix release for 1.2 - BFQ randomly causing "black screen" issue immediately after boot animation, preventing full boot - reboot resolved issue in most cases, but comes back at random on boot - Setting default I/O scheduler to NOOP until BFQ issue is resolved.
1.2
Autogroup per UID instead of TTY task (huge improvement to autogroup on android)
Set BFQ as default I/O Scheduler
Allocator: Switch to SLUB from SLAB
Remove verbose debugging symbols
Set proper firmware/calibration paths for WiFi in configuration
1.1
Add userspace support for undervolting
GPU OC (400mHZ) on CPU OC > 1000mHZ
Fix "Recent Apps" bug - The glitchy behavior when loading an app cached in the "Recent Apps" menu. Pointed out by DarkNight
Tune SmartassV2 for better behavior and ideal freq set at 760mHZ
Add the following CPU Governors: Lionheart, SavagedZen, Lazy, Scary, Intellidemand, LagFree, Wheatley
Deprecated the non-autogroup release also known as (default)
various other improvements to CPU, voltage, video.
1.0.1b
Add SmartAssv2 CPU Governor
Fix LOCALVERSION
1.0.1
Patched MMC_CAP_ERASE as precautionary to avoid hard brick
1.0-pre
V(R) I/O scheduler Added
SIO I/O scheduler Added
Zram sources backported from 3.0 resolved compile issue
Alpha (First public download)
Overclock added: Min Freq: 216 Max Freq: 1504
CPU Governors: Lulzactive, Ondemand, Interactive, Conservative, Userspace, Performance, Powersave
IO Schedulers: Noop, Deadline, CFQ, BFQ
Autogroup or Default Kernel available
Patch for Tiny HAL - resolves popping in audio on JB/ICS
Click to expand...
Click to collapse
If you would like to help out with the continuance of kernel development for your Acer Iconia Tab A100 please consider a small donation to help out with bills, baby formula, wipes, diapers, etc. All donations are very appreciated by my family and I! Thanks
This kernel is pretty slick, tested a previous version of it, nothing but good things to say of it, hit thanks on your way to flash this.
Tapatalked from my Galaxy S II.
pio_masaki said:
This kernel is pretty slick, tested a previous version of it, nothing but good things to say of it, hit thanks on your way to flash this.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
Same to all your projects pio_masaki! I always hit the "thanks" for you too buddy! BTW, the kernel you have been testing is the equivalent in the downloads section to the "default", you may want to take a stab at the "autogroup" kernel. I have been testing it with great responsiveness. Also added in SIO and tweaked some timings/voltages in the new downloads. Glad to hear you have had good results thus far
linuxsociety said:
Same to all your projects pio_masaki! I always hit the "thanks" for you too buddy! BTW, the kernel you have been testing is the equivalent in the downloads section to the "default", you may want to take a stab at the "autogroup" kernel. I have been testing it with great responsiveness. Also added in SIO and tweaked some timings/voltages in the new downloads. Glad to hear you have had good results thus far
Click to expand...
Click to collapse
Yup I have every intention of banging that new kernel, waiting a minute while I build yet another CM10 for further testing of the autobrightness levels, added a couple more slots into the array, should have it nailed this time.
pio_masaki said:
Yup I have every intention of banging that new kernel, waiting a minute while I build yet another CM10 for further testing of the autobrightness levels, added a couple more slots into the array, should have it nailed this time.
Click to expand...
Click to collapse
Was really curious to see how BFS performed with Jelly Bean /ICS either one, but i've not had any luck with getting BFS to run stable so I removed it from my kernel tree for the time being. If i can get a full port to the grouper tree with all our device sources, I'm pretty confident I can get a newer revision of BFS to working. From most of my experience with other devices and other x86 systems though, the BFS doesn't out perform Autogroup anyway, but its mostly just curiosity that makes me want to go through all the trouble of getting it working with tegra2. On another note, I'm not sure why but regardless of the kernel or configuration I use Jelly Bean seems to have a weaker performance in any benchmark than the same kernel/configuration used in ICS. I'm yet to figure out where the bottleneck is in JB. (testing with linpack, quadrant, antutu benchmark all produce lower scores than with ICS) The thing that is most important to me is the actual user experience and feel that you get and not some benchmark score.. I can say that JB is very smooth and the scores don't mean nothing if you don't look at them!!
Awesome kernel! Seems stable enough, audio also works
sent from my A1/500 Iconia slab of awsomeness
Every time I download the zip file and try to flash it I get a Failed message. I am using TWRP to flash with.
tidewaterns said:
Every time I download the zip file and try to flash it I get a Failed message. I am using TWRP to flash with.
Click to expand...
Click to collapse
download it again
tidewaterns said:
Every time I download the zip file and try to flash it I get a Failed message. I am using TWRP to flash with.
Click to expand...
Click to collapse
In TWRP do you have MD5 verification enabled? If you do then it should work after you turn that off, the zip file is signed with SignAPK.jar so it should work without any issues. I have personally flashed both to my device using TWRP. If you are using adb through TWRP to push the .zip then you shouldn't be pushing it to /sdcard/ in recovery the proper location for internal storage is /data/media/ so if you have pushed it to /sdcard/ in adb then it will exist in a directory where permissions aren't accurate for the loader. Push with adb to /data/media if in recovery, or push to /sdcard/ if pushing with adb while your tablet is booted to Android OS.
If for some reason the .zip files are corrupted on github for other users please let me know and I will recompile, recompress, resign, and reupload.. Thanks
Fransis88 said:
download it again
Click to expand...
Click to collapse
Francis88: I assume the zip files flashed ok for you? Anyone else having problems?
Mine works fine. Flashed with twrp. Of course, I cleared dalvik before I flashed. The rebooted. Works fine.
sent from my A1/500 Iconia slab of awsomeness
I really don't like flashing from internal, and twrp, at least 2.1.1, says sdcard for whatever one is mounted. Keep that in mind when flashing in twrp. I think 2.2 says sdc instead. Also in jellybean it goes to storage/sdcard0 for internal sdcard1 for external sdcards. You can probably still use the old paths but those are the correct paths for jellybean.
Tapatalked from my Galaxy S II.
I copy everything to my SD card. You can flash from it.
Actually, I've only ever flashed from internal once, it was jb gapps
sent from my A1/500 Iconia slab of awsomeness
das_webos_transformer said:
I copy everything to my SD card. You can flash from it.
Actually, I've only ever flashed from internal once, it was jb gapps
sent from my A1/500 Iconia slab of awsomeness
Click to expand...
Click to collapse
Well I'm not saying you can't its more of a personal call to never store stuff I don't want to lose on internal, especially since it gets wiped when I wipe for testing.
Tapatalked from my Galaxy S II.
I think there may be some confusion when I say "internal" and "/sdcard" Assuming that one doesn't have an external sdcard, then /sdcard would be internal storage while in android OS (meaning ICS, Gingerbread, Honeycomb, Jellybean, etc), and that same path would be /data/media while in TWRP/CWM (Recovery mode). I've never had my external sdcard (removable one) to mount at /sdcard or /mnt/sdcard on my a100 so I assumed it was safe to recommend flashing from there as I have never had any issues with it, but like I mentioned in the previous post, /sdcard is only your internal user storage while booted into Android OS and not while in Recovery, while in Recovery the symlink doesn't exist so the right location is /data/media..
If anyone isn't familiar with the hierarchical file system and the mount points for their device, then I strongly encourage them NOT to use experimental ROMS, Kernels, etc. including this one. The kernel is a very critical part of the software on the device, and without a working kernel, you WILL NOT have a working device. So if something happens that you don't have the original kernel backed up and a way to flash it, or a full backup that you can access from recovery, then testing experimental kernels is like playing with fire..
A soft brick is highly possible if you obtain: A) the wrong kernel for your device B) a corrupted download kernel -OR - C) An experimental kernel that may be misconfigured or contain "bad" source code. << All of these can be repaired easily from recovery if you have a known good version to restore from, but if you have trouble flashing one kernel that is known to flash successfully for others, then what happens when you get the Fail message when trying to restore your working kernel/system??
Hope nobody takes this the wrong way, just trying to look out for people before things go bad. Good luck..
pio_masaki said:
Well I'm not saying you can't its more of a personal call to never store stuff I don't want to lose on internal, especially since it gets wiped when I wipe for testing.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
I have never had to wipe the internal user storage AKA /data/media & /sdcard while testing any build, Of course it would be very easy to mess things up and accidentally wipe it from recovery, but I've never ran into any issues needing my internal SD wiped (so far).
Pio_masaki you could be talking about something else by internal storage though? Like /system or / or somewhere other than /data/media, /mnt/sdcard[0-] ?
linuxsociety said:
I have never had to wipe the internal user storage AKA /data/media & /sdcard while testing any build, Of course it would be very easy to mess things up and accidentally wipe it from recovery, but I've never ran into any issues needing my internal SD wiped (so far).
Pio_masaki you could be talking about something else by internal storage though? Like /system or / or somewhere other than /data/media, /mnt/sdcard[0-] ?
Click to expand...
Click to collapse
No I mean internal SD. I fully wipe /data including /data/media. Occasionally I dd zero them all too.
Tapatalked from my Galaxy S II.
linuxsociety said:
In TWRP do you have MD5 verification enabled? If you do then it should work after you turn that off, the zip file is signed with SignAPK.jar so it should work without any issues. I have personally flashed both to my device using TWRP. If you are using adb through TWRP to push the .zip then you shouldn't be pushing it to /sdcard/ in recovery the proper location for internal storage is /data/media/ so if you have pushed it to /sdcard/ in adb then it will exist in a directory where permissions aren't accurate for the loader. Push with adb to /data/media if in recovery, or push to /sdcard/ if pushing with adb while your tablet is booted to Android OS.
If for some reason the .zip files are corrupted on github for other users please let me know and I will recompile, recompress, resign, and reupload.. Thanks
Click to expand...
Click to collapse
I do not have MD5 verification enabled. Every time I try to flash it gets to the Verifying partition sizes then I get a failed in red on the screen.
tidewaterns said:
I do not have MD5 verification enabled. Every time I try to flash it gets to the Verifying partition sizes then I get a failed in red on the screen.
Click to expand...
Click to collapse
I would redownload, that's usually a cause if everything else is good. Any error message, like status 7?
Tapatalked from my Galaxy S II.
I finally got it installed and I overclocked it to 1504 mhz . Thanks for your help!
Sent from my A100 using xda premium
vTweaks Reborn
Simple Explanation :
vTweaks is a simple compiled tweaks that I encountered in my stuff. It gives a lot than you think, while having nice scripting in it
Tweaks that are included:
Better Performance
Better Battery Life
Better Net Speed
FlagTuner (For better Battery life and Performance)
BOOST script to free up RAM when you need to.
Trims Partitions (ext4) for some boost
Remount Partitions (Remounts them with performance improving options)
Sched Features Tuning
Gaming Lagfix
VM Tweaks
Null Kernel Tweaks
AND EVEN MORE THAT IS YET TO COME
ADD-ONS:
LMK Tuner
LMK Minfree Parameters Tuner
LMK Minfree is a set of parameters that sets the limits at which apps are killed in order to free RAM
Stock LMK minfree values are good by itself, but this aims to improve it to be better by fine tuning it based on your device's RAM.
zRam Tuner
zRam Tuner
zRam is a module of the Linux kernel, previously called "compcache". ZRAM increases performance by avoiding paging on disk and instead uses a compressed block device in RAM in which paging takes place until it is necessary to use the swap space on the hard disk drive.
Database Optimizer
Database Optimizer
Android Apps have databases in it. Optimizing databases regularly(not always) can improve RAM usage and CPU usage of apps.
Current Version: Reborn v2.2.1
PREREQUISITES:
'init.d' ENABLED
'busybox' INSTALLED - http://forum.xda-developers.com/android/software-hacking/tool-busybox-flashable-archs-t3348543 - Recommended
And of course, ROOT
DIRECTION:
On the current Version, It is compressed and turned into a single script (So no need to flash anything). Just download the zip, extract it and copy it to /system/bin and set permissions to rwxr-rw-x. Then go to Terminal emulator and type:
Code:
su
vtweaks
If you want to use Add-Ons (which are only available in v2.0+), make a directory in /system/etc/vTweaks name Add-Ons and put the addon files there then run vtweaks in Terminal Emulator.
Note: To update, simply replace the previous version (delete the vtweaks file from /system/bin) and set the correct perms (rwxr-xr-x) to the file, open it in terminal emulator and it will update itself.
If it's asking something related to busybox, please flash the busybox I linked above.
Add-Ons are present in the zip file. There are instructions/readme.txt there, follow it and you'll be good to go.
On Version 2.1 and above, there are binaries included, which are present in /bin folder. They are needed for some functions of vTweaks to work properly. You need to follow the instructions/readme.txt to make things work.
DOWNLOAD HERE
Source Code:
NO MORE
Thanks To These Guys:
@hoholee12 - for inspiration and ultra bashing
@sonickles9 - for his bash prowess and tricks
@Paget96 - i used some of his tweaks
@DiamondBond - for flagtuner
@YashdSaraf - for his great busybox (which I recommend for this script)
@FeraVolt - Some of his tweaks in FDE are present
This new Script is a little bit tricky, so here's some tricks Iv'e included in it:
Open Terminal Emulator
Directly Execute the tweaks enabled:
Code:
vtweaks -a
Boost Directly:
Code:
vtweaks --boost
Create Boost shortcut:
Code:
vtweaks -mb
Trim Partitions:
Code:
vtweaks --trim
Clean junks:
Code:
vtweaks --clean
Logging purposes
Code:
vtweaks --verbose
Version
Code:
vtweaks -ver
Enable init.d
Code:
vtweaks --init
Install busybox if detected
Code:
vtweaks --bbinstall
Check busybox installation
Code:
vtweaks --bbcheck
Check Device
Code:
vtweaks --device
That's it, thanks to @hoholee12 since this was inspired by his sched_tuner :good:
does it work in stock revolutionalized rom by rajat
pyumredkar said:
does it work in stock revolutionalized rom by rajat
Click to expand...
Click to collapse
Yes, it's compatible with all
Sent by a Cool Guy using XDA-Developers mobile app
veez21 said:
Yes, it's compatible with all
Sent by a Cool Guy using XDA-Developers mobile app
Click to expand...
Click to collapse
flashed this in stock revolutionalized rom and did a factory reset, wifi isn't working correctly
pyumredkar said:
flashed this in stock revolutionalized rom and did a factory reset, wifi isn't working correctly
Click to expand...
Click to collapse
Wifi is not affected by veezTweaks
Sent by a Cool Guy using XDA-Developers mobile app
Does it work on Nokia XL?
And is it really necessary to do a factory reset after flashing it?
Ronnie_180808 said:
Does it work on Nokia XL?
And is it really necessary to do a factory reset after flashing it?
Click to expand...
Click to collapse
Yes, and you don't have to do a factory reset for it to work.
Sent by a Cool Guy using XDA-Developers mobile app
Nice work.??
So far so good. Wifi, bluetooth etc everything working well.
And I can clearly feel the difference.
Thank you.
Updated to v8.2. Now with reference file.
Sent by a Cool Guy using XDA-Developers mobile app
Hey bro, do we have to run "system/etc/init.d/00-7veez21" command after every reboot to enable it?
Ronnie_180808 said:
Hey bro, do we have to run "system/etc/init.d/00-7veez21" command after every reboot to enable it?
Click to expand...
Click to collapse
Not really since it's an init.d script. It should run on boot and generate a log file in your sdcard, if not then check out /data/vTweaks/vTweaks_log.txt
Sent by a Cool Guy using XDA-Developers mobile app
Updated to v8.5
Now with disable logcat, updated gp fix, and updated boost script.
Sent by a Cool Guy using XDA-Developers mobile app
Updated to v9.1
Updated Boost script
Updated Google Play Battery Drain fix
Minor setprop optimization
Fixed some minor issues on update-binary
Net Speed Tweaks updated
Fixed something in the reference file
Updated to v9.2
FSTrim(lagfix)
Updated boost script
Code optimization
Updated to v10
Now with Terminal UI
Major Script Stucture Overhaul
Code optimizations
Busybox Binary added
Check it out for more
reflashed stock revolutionalized rom and flashed v10 zip. but play store not working. reverting back to older version of vtweaks
pyumredkar said:
reflashed stock revolutionalized rom and flashed v10 zip. but play store not working. reverting back to older version of vtweaks
Click to expand...
Click to collapse
what does play store say when it's opened, or is it just white screen
it shows rh-01 error. I tried googling about it. did every possible step for solving that. even did a factory reset but it is always same.
pyumredkar said:
it shows rh-01 error. I tried googling about it. did every possible step for solving that. even did a factory reset but it is always same.
Click to expand...
Click to collapse
try this
http://www.ministryofsolutions.com/2016/01/google-play-store-error-rh-01-100.html?m=1
*** This kernel is now end-of-life, not supported and developed anymore !!! ***
Hi all,
some of you know me from the other OnePlus or Samsung devices areas, where I provide my kernels already for more than three years to OnePlus 3, 2, one and X, 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, good existing 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 !!
To add: An open beta (aka community build) is NOT an official build supported here. If you use a community build and have issues, don't complain or even report. I am not merging any kernel changes from open betas into my kernels !!
Important notes
When using new anykernel concept Boeffla-Kernel: Flash stock kernel of rom first !
This kernel is ONLY compatible to OxygenOs stock, nothing else !!!
If you are using a custom rom that bases on OxygenOs, it might work. However, if it does not work, do not expect me to do tweak to make the kernel running with your favorite rom. I would not do it - my one and only reference is OxygenOs stock.
It is not supposed to be compatible to CM, HydrogenOS etc.
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.
Installation
Read the install instructions in the support section on the Boeffla Site.
Support
First read the FAQ section on the Homepage !!!
Click here to learn about all possible kernel settings in the config app (outdated at the moment).
Click here to learn about using the config app (outdated at the moment).
I will refuse to give support if you do any undervolting/overclocking 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 OxygenOS 4.x.x kernel - Click here
Change log for OxygenOS 3.x.x kernel - Click here
Known issues
none
Features
Note: This kernel only runs on OOS 3.x.x for the OnePlus 3T - nothing else !!!
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.4.21 or higher !!!) configuration app (get it from http://www.boeffla.de) to configure all kernel settings
Dash charging fully supported
The two CPU clusters (big and little cpu) can be configured completely separate in terms of min/max frequencies, governors and CPU core profiles
Additional governors: Impulse, zzmoove, elementalx, conservative, ondemand, blu_active
Additional schedulers: fiops, bfq, sio, sioplus, fifo, vr, tripndroid, zen, maple
No CPU overclocking and voltage interface, no GPU overclocking and voltage interface
USB charge rate bumped up to 900 mA
Boeffla charge analysis (display of charger type and charge current in Boeffla-Config app in real time)
Boeffla touchkey LED control (LEDs fully off, LED on screen touch, configurable duration)
CPU core profiles to restrict number of CPU cores being used (the OP3 does not hotplug based on load)
Notification LED control (effect + speed for blinking/fading, brightness for continuous notification like battery charging etc.)
Boeffla-Sound engine: Headphone volume and speaker volume (only lowering volumes for speaker)
Dynamic FSync (activated if screen on, deactived if screen off), configurable
Input boost frequencies and duration configurable per CPU cluster, input boost switch
Show CPU frequency usage per CPU and frequency in Boeffla-Config
Show GPU frequency usage per frequency in Boeffla-Config
KCal V2 Color control
Display backlight limits configurable (to avoid display brightness gets too low in some situations)
Display backlight dimmer
Swipe2wake gestures
Control haptic feedback of gestures (except fingerprint)
Haptic feedback intensity control
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 (only when data volume is formated with ext4, stock default is f2fs)
Kernel logger (dmesg) configurable
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)
NTFS support (module)
XBox support (module)
OTG-Ethernet support (module)
TCP Congestion changed to Westwood
Many additional TCP congestion algorithms available
Entropy values configurable
Hardware touch keys are locked as long as screen is in use (touched) for better usability
Swap supported
Doze mode switchable
Verifiedbootstage flag remove to avoid triggering safetynet
Various minor kernel tweaks
Doze mode configurable in Boeffla-Config
Full selinux strict support (switchable to permissive on demand)
Show speedbin information (PVS level) in Boeffla-Config app
init.d support (in /system/etc/init.d - set correct permissions!)
Entropies configurable
Automatic EFS backup
Integrated full busybox 1.27.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
Security patches included, which are not in the official repo
Google gcc 4.9 toolchain (64 bit) used for best stability
Always based on latest OOS kernel sources (https://github.com/OnePlusOSS/androi...neplus_msm8996)
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
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 kernel only if you are running a compatible 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.4.21 or higher for the OnePlus 3T 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
* Osm0sis
... 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 log:
OOS4
http://kernel.boeffla.de/oneplus3t/boeffla-kernel-oos/oos4xx/changelog.htm
OOS3
http://kernel.boeffla.de/oneplus3t/boeffla-kernel-oos/oos3xx/changelog.htm
--- Reserved 2 ---
Here we go!
First beta is online for you guys.
As always, find everything on www.boeffla.de
And just to stress it again: It is the VERY FIRST beta, so expect bugs!
Have fund
Andi
nice! downloading right now!
so happy to see you again andi! your kernel was simply the best on my galaxy S5 and I missed your affords in my S7!
so happy flashing to everyone!
Sent from my ONEPLUS A3003 using XDA-Developers mobile app
After jumping from kernel to kernel (since there are many more kernel devs here than on the OP2) with various minor niggles, finally back to the one I feel fits my needs best. This release brings me relief, as now I don't have to go kernel hopping again, and I think Boeffla provides the best support of all. No bugs so far, multirom boot menu works, everything runs great.
Out of curiosity, is the kernel systemless? (Can I revert to stock by just flashing stock boot.img from latest ROM zip?) I ask because flashing the entire stock ROM takes a long time, and the TWRP loading time is also long.
Also, ext4 tweaks is not hidden for me and is enabled when a profile is reset to default settings. I'm on the default filesystems. (f2fs data, ext4 everything else)
Should I leave ext4 tweaks on or off?
PS: I was probably the first person to like and subscribe to this thread. (within 5 minutes of thread creation)
Edit: Flashable stock kernels? Perfect, thank you @Lord Boeffla ! Does it revert any custom kernel to stock kernel?
Been with Boeffla since S3 and via OPO this will be my third phone with the kernel.
Thanks!
Skickat från min ONEPLUS A3003 via Tapatalk
knpk13 said:
After jumping from kernel to kernel (since there are many more kernel devs here than on the OP2) with various minor niggles, finally back to the one I feel fits my needs best. This release brings me relief, as now I don't have to go kernel hopping again. No bugs so far, multirom boot menu works, everything runs great.
Out of curiosity, is the kernel systemless? (Can I revert to stock by just flashing stock boot.img from latest ROM zip?) I ask because flashing the entire stock ROM takes a long time, and the TWRP loading time is also long.
Click to expand...
Click to collapse
This is not possible on OOS in a clean way.
The kernel comes with modules which are placed in /system/lib/modules too.
So only flashing stock boot.img would not replace the kernel modules by stock ones. So it is only a "half-good" solution.
But, as most of the time, I have a solution for you
Look here: http://boeffla.de/index.php/downloads/downloads-general
Flashable stock kernels for the 3T, which also include the modules.
Guess this is what you need.
Andi
knpk13 said:
Also, ext4 tweaks is not hidden for me and is enabled when a profile is reset to default settings. I'm on the default filesystems. (f2fs data, ext4 everything else)
Should I leave ext4 tweaks on or off?
Click to expand...
Click to collapse
This is something I might need to correct in the app then. Leave them off, there is no ext4 anymore on /data volue with stock OOS (but the f**inkg f2fs).
I will look into that over the next days then.
EDIT: Just tried it - cannot replicate that. Maybe your /data partition is indeed formatted in ext4???
(you can check by firing the following command in a terminal: mount | grep data)
Andi
Lord Boeffla said:
This is something I might need to correct in the app then. Leave them off, there is no ext4 anymore on /data volue with stock OOS (but the f**inkg f2fs).
I will look into that over the next days then.
Andi
Click to expand...
Click to collapse
I reopened the app, and ext4 tweaks was off. But when I click on reset profile settings, it turns on. But on reopening again, it turns off automatically every time, so I guess it's working fine. Yes I'm sure I'm on f2fs.
knpk13 said:
I reopened the app, and ext4 tweaks was off. But when I click on reset profile settings, it turns on. But on reopening again, it turns off, so I guess it's working fine.
Click to expand...
Click to collapse
Yep, and also means, your data partition is not formatted with f2fs (my op3t came with /data on f2fs)... lucky you. I love ext4 much more, I even consider reformatting /data with ext4 soon, hehe.
Andi
Ok guys, evening hours here in Germany.
I am off for today. If you have any questions, you can also move over and read in the OP3 thread. The devices are - concerning my kernel - 99,99% the same.
So you would most probably find all answers to your questions already there.
Tomorrow I will catch up again.
Andi
Lord Boeffla said:
Yep, and also means, your data partition is not formatted with f2fs (my op3t came with /data on f2fs)... lucky you. I live ext4 much more, I even consider reformatting /data with ext4 soon, hehe.
Andi
Click to expand...
Click to collapse
I'm sure I'm on f2fs. Even TWRP says I'm on f2fs. 3T comes stock with f2fs. This is the output of mount | grep data, but since I'm using magisk I think the output has many partitions and I can't make sense of it.
I think the ext4 tweaks toggle is working fine since it reverts to off automatically when the app is restarted. Thanks!
Here is the output: https://hastebin.com/iwokiramek.hs
Welcome to the 3t Lord Boeffla.. Enjoyed having your kernels and support on the s5 when I was running that phone.. Look forward to the same here..
Sent from my ONEPLUS A3000 using Tapatalk
Lord Boeffla said:
But, as most of the time, I have a solution for you
Look here: http://boeffla.de/index.php/downloads/downloads-general
Flashable stock kernels for the 3T, which also include the modules.
Guess this is what you need.
Andi
Click to expand...
Click to collapse
nice, been waiting for this since day one. :good:
So it is not oos 4.0.0 compatible
Gesendet von meinem ONEPLUS A3003 mit Tapatalk
inzaghi75 said:
So it is not oos 4.0.0 compatible
Gesendet von meinem ONEPLUS A3003 mit Tapatalk
Click to expand...
Click to collapse
No. OOS 4 has not yet been officially released and no kernel source has been released.
christmas is here since andi is our santa.
welcome to the 3T world.
loyalists like me have been waiting for you perhaps since the device was launched.
glad OnePlus and XDA did such an awesome thing to distribute devices to devs.
been following your work for a while now.
your kernel turned my OpO into a beast.
just flashed onto my 3T.
will report issues as and when(and if) I can find them.
cheers
Glad to see you here Andy!
finally you will develope on 3T:good:
Glad to see you here Andi:victory:
I use your kernel since Galaxy S3, also flashed it on my opo and my wife's opt.
:good: Now the kernel it's running very well on my new op3t.
initial thread here, further clarifications in recently added posts below OP/1st post
Lunar-Kernels
tl;dr - too long didn't read / first things first
Stock ROM kernels are attached in posts #1-4 or link to Google Drive
AOSP/LineageOS kernels are attached in post #5 or folder
simply dropping the folder with kernels here (Stock ROM):
https://drive.google.com/open?id=1xL5gEiG-fjzTuSGM_kUDsrOKy-jTtGr1
Description: 3 sub-folders (thus kernels) available:
"old" shouldn't really be used, this is a very bare to LG stock source kernel and (probably) using outdated ramdisks which prevent FM Radio, Mirrorlink, etc. from working
"stable" stable has gotten more testing (or more recent fixes) and is deemed fit for daily driver usage
"bleeding edge" is newest branch, very experimental changes/fixes or just the very latest kernel (if those don't end up in "stable" already)
Stable and bleeding edge are the
Further notes for "eas":
From the tests so far - it has turned out that power consumption ALWAYS was higher compared to HMP and/or the default shipped LG kernel (tweaked HMP)
So the best results up until now was to underclock CPU, underclock GPU (or keep at lowest 1-2 levels) and add tweaks to shut phy power source off for display, this is similar results like anandtech with Exynos EAS/HMP tests: https://www.anandtech.com/show/12620/improving-the-exynos-9810-galaxy-s9-part-2/3
Meaning: NO EAS kernels until further notice - only HMP kernels will be developed/provided right now
Usage case: [outdated]
"old": should work pretty reliable, everything is built conservatively & close to stock one of the first kernels
"stable": probably great daily driver material - FM Radio & MirrorLink, etc. still broken
"bleeding edge": just the latest and greatest from upstream, security, tuning, etc. - features might break in the process
eas [attached here]: daily driver, long running for lots of reading, lots of watching videos, high SOT demand ; suitability for gaming has yet to be evaluated
NOT working and probably will NOT in the near future (or at all): [outdated]
- FM Radio (broken with "old", "stable" kernels - those use v300 ramdisk)
- MobiCore - thus MirrorLink, etc. (broken with "old", "stable" kernels - those use v300 ramdisk)
- FM Radio & MirrorLink currently works with bleeding edge kernels
Notes (Kernel):
This kernel is built first and foremost FOR ME and shared with the community to benefit from that work,
you don't owe me anything and I don't owe you anything
like with Sony (yeah, even Sony !) and other vendors with their modified, proprietary non-AOSP ROMs - kernel development is extremely bothersome, each few commits kernel doesn't boot or compilation fails, so don't expect e.g. 4.4.137 kernel or catchup with latest codeaurora changes since that takes simply too much time and work (time, effort, nerves, etc.)
tested on H930 (Europe) V30 ONLY, test at your own risk on H930DS (dual SIM) or other devices; ramdisks and device configs WILL differ (global defconfig used - so compatiblity should be higher, limitations/compatibility issues with US, Korea and other models possible)
You need to have knowledge how this device behaves in case of flashing broken kernels, filesystem corruption and other worst-case scenarios
You must:
stay calm all of the time while flashing and must NOT do anything rash or chaotic
know how to get into bootloader/fastboot mode via USB-cable (when device is off) OR via adb command from a running system
know how to force the device to turn off (it will turn on again but that might help in certain cases) - this way you easily can get into fastboot/bootloader again
know and/or have a basic understanding that the device will settle most issues on its own
have your device charged to a battery level AT LEAST to 50-60% in case boot loops take longer (it is caught in boot loop) and you can't quickly turn the device off anymore
know/expect that flashing Magisk and other mods most certainly will lead the device too boot several times ("artificial bootloop") and might get you uneasy or confused, we need to figure out how to speed up the process that it finally boots into the ROM
potential issues & potential remedies/fixes: [up-to-date]
might have high load unless rctd disabler is flashed (root detection tool) => flash rctd
might not boot unless no-verity is flashed, custom ROM => flash no-verity
might not boot or work with encrypted phone or encrypted anything => should be self-explanatory, don't use LG encryption on custom ROMs/mods
some security functionality might not work => TEE/qseecom/lgecrypto_module might not work, encryption safe, folder encryption, etc. might be broken (if applicable)
might not boot or bootloop microSD with exfat is cause of LOT of trouble => in doubt remove microSD before flashing custom Kernels or ROM mods to avoid having additional trouble-maker to troubleshoot
phone boot-"loops" several times => seems to be default bootloader behavior for LG V30 (and/or other LG phone)
phone boot-"loops" several times => might need a few times to "settle" to boot the ROM up
booting up takes long => might actually rebuild dalvik cache or do some filesystem checking
SIM PIN isn't request and WiFi is dead as well => several reboots might fix it;
SIM PIN isn't request and WiFi is dead as well => permission corruption might have occurred, (need root) try to fix via: https://stackoverflow.com/questions...acct-uid-10064-read-only-file-system-in-emula
after flashing (custom) Kernel or (custom) ROM phone (re)boots into fastboot => "no OS" , Kernel might not actually be bootable , kernel issue, system partition issue
after flashing (custom) Kernel or (custom) ROM phone (re)boots into fastboot => might have incompatible ramdisk, no-verity was not flashed
after flashing (custom) Kernel or (custom) ROM phone (re)boots into fastboot => Kernel might be broken (totally not work or be compiled with non-compatible features)
after flashing (custom) Kernel or (custom) ROM phone (re)boots into fastboot => OS/Android might be broken (filesystem corrupted, etc.)
Flashing rctd & no-verity/verity-disabler is only necessary for LG Stock-based ROMs !
Not necessary for AOSP, LineageOS, etc. !
prepare kernel for flashing : [up-to-date]
rename the zip-file to 7z (file size limit)
extract the 7z (needs 7z that support PPMd compression)
rename it into boot.img
suggested flash : [up-to-date]
Get into fastboot mode (turn off => connect cable end to phone => hold VOL down => connect PC end of cable)
fastboot flash boot boot.img
fastboot boot TWRP.img (keep USB cable connected ALL of the time)
flash rctd disabler
flash no-verity
(optional) flash Magisk
disconnect USB cable
(optional) wipe /cache
(optional) dalvik cache
reboot system
Help:
Forcing the device to reset usually is done via Power + VOL DOWN - keep both pressed for several seconds, then the screen should turn off
the device is set up to (re)boot again - so have the USB cable, a PC/phone [on the go] with fastboot ready to connect the cable immediately when it was off
.
If you plan on using the microSD more extensively and are on non-Stock (e.g. AOSP, LineageOS, dot os, etc.) - [backup your data !] then format the microSD to ext4 in TWRP, that should give you 2x the write performance of exfat and also somewhat faster read performance
As a bonus of using ext4 on the microSD - access to your files should be available when flashing/trying out the GSIs (Project Treble)
Kernel boot test (DEVs):
[Kernel testing or if you want to try] I usually do a fastboot boot boot.img first to see if the bootanimation is successful (boots into bootanimation [non-Stock] or it boots into the ROM itself with reduced functionality [Stock ROM])
After that I do a real flash of the kernel via fastboot flash boot boot.img
Quirks (V30* phones compared to others & bootloader/boot(loop) behavior):
After first flashing - the kernel might fail at 1st boot, then reboot device and properly boot into the ROM
with Magisk it can be more reboots (I counted at least 3-4).
.
.
If the bootlooping is much longer - force reset the device (Power + VOL DOWN), that should usually allow the device to recover after 1-3 (re)boots
.
If that still doesn't help - remove the microSD - until you've successfully booted the kernel up, the exfat driver is known to cause trouble and make things much less predictable and irritating
To make things more predictable (and exclusively using AOSP/LineageOS-based ROMs) - you can format the microSD to ext4, that might help a bit with the amount of (re)boots during flashing)
FIXME:
additional notes, warnings, guides, etc.
(theory) while the device seems to bootloop after flashing Magisk or other "bigger" modifications - occasionally press the volume down button while you see the LG V30 ThinQ logo (boot splash/image) to speed up booting (input = boosting = quicker everything ?)
Kernel Source:
android_kernel_lge_msm8998/branches
lunar-kernel_II_WIP5_boot-work [current "bleeding edge"]
other/older kernels are earlier states of latest bleeding edge branch
Kudos:
Linus Torvalds, Linux Kernel devs
Greg Kroah-Hartman our favorite upstream Kernel LTS maintainer <3
Google kernel & other Android devs
codeaurora, linaro & all other devs working on qualcomm goodies
LG kernel & other devs
nathanchance for his kernel, toolchain and other reference work
sonyxperiadev & devs
sultanxda
freak07
franciscofranco
andip71
frap129
GreyLeshy
SGCMarkus
the XDA , 4PDA and all other android communities
all other devs & folks to be mentioned
last edited:
28.06.2018, add attachment: specifically built kernel for ls998, US sprint V30 model (US firmware, US998)
28.06.2018, add attachment: uploaded II_EAS_I_stable , EAS kernel on early ported EAS state, should be pretty efficient, deemed stable material, read notes: at its announcement post
06.07.2018: updated text for bleeding-edge added link to it https://forum.xda-developers.com/showpost.php?p=76996622&postcount=88
12.07.2018: attached latest HMP kernel to OP (1st post), removed EAS kernels since those had a bug with frequency being stuck at max frequency
26.10.2018: removed older attached HMP kernels, newer ones are in posts below
#1
"old", barebones kernel with absolute minimum changes (from LG) will be here
#2
"stable", only minimum additional functionality & fixes will be here
if not mentioned otherwise these are ONLY for LG Stock-based ROMs (Boombox, A.I.S., Stock, debloated Stock, etc.)
Checksums (md5sum):
d0c4572563a389ec495f1c661332c185 boot_oreo_I_6_WIP4_stock__H932_spr_US__tmo_US_20K.img
f29fc429d32de4fd79d3117642d39137 boot_oreo_I_6_WIP4_stock__H932_spr_US__tmo_US_20K_PPMd_7z.zip
6307cd6d40e97404a3c66bf78d20437f boot_oreo_I_6_WIP4_stock__US998init_spr_US_20D.img
f181f7589ecb3426006fa0d15c1e161d boot_oreo_I_6_WIP4_stock__US998init_spr_US_20D_PPMd_7z.zip
f31791fcd8b57db7e3b91ba5e4755bf3 boot_H930_21A_oreo_I_6_WIP4_LG_stock.img
d77c0504c9119f2d86880dd74d8fc0cd boot_H930_21A_oreo_I_6_WIP4_LG_stock_PPMd_7z.zip
Source:
https://github.com/zachariasmaladro...mmits/oreo_I_6_WIP4_stock__H932__US998_spr_US
#3
"bleeding edge", current development branch & WIP (work-in-progress) drops
Stability troubleshooting:
disable zram
set lowest CPU frequency and max CPU frequency to default
lower GPU max frequency
...
change each setting separately and see if that improves stability then please report your results
oreo_I_6_WIP7_3_stock
Branch:
https://github.com/zachariasmaladroit/android_kernel_lge_msm8998/commits/oreo_I_6_WIP7_3_stock
Changes:
rolled back kernel to earlier state (October 1st), troubleshooting stability
re-added sdcardfs aosp msm upstream changes, mostly "Drop dentry cache to prevent unknown file status" change in behavior (data integrity)
sdcardfs fixes
ext4, f2fs, ecryptfs and fscrypt updates and changes close to latest upstream
lockdep improvements
further oom, oom_reaper, fork-handling fixes and improvements
force 16b ECC for pstore
scheduler fixes (hmp.c; ...)
updated simple_lmk (not used in this branch)
[eval] reverting to basic optimizations for armv8-a
[eval] reverting to Google's 4.9 Toolchain (best compatibility, stability, etc.)
devfreq fixes and improvements
PCIe wake improvement for msm8998
configure i2c for bit-banging bus recovery
[eval] revert several previous changes
several other changes
Click to expand...
Click to collapse
md5sum checksums:
91273b50c1126bf44e2fa9b7d3eb00bb boot_oreo_I_6_WIP7_3_stock__H932_spr_US__tmo_US_20K.img
859fa1eb9948f19821110da85d2d996a boot_oreo_I_6_WIP7_3_stock__H932_spr_US__tmo_US_20K_PPMd_7z.zip
e20bb8036273960e99316cb7bac57c78 boot_H930_21A_oreo_I_6_WIP7_3_stock.img
0a360f4dd4cedf6cf95ded2dbd78fa1d boot_H930_21A_oreo_I_6_WIP7_3_stock_PPMd_7z.zip
0b7fc9259836f9a79c2e1715ba7bd79a boot_oreo_I_6_WIP7_3_stock__US998init_spr_US_20D.img
9c1d1f917f7cd9ba50c2464a2b8b4bb0 boot_oreo_I_6_WIP7_3_stock__US998init_spr_US_20D_PPMd_7z.zip
Click to expand...
Click to collapse
oreo_I_6_WIP8_stock
Branch:
https://github.com/zachariasmaladroit/android_kernel_lge_msm8998/commits/oreo_I_6_WIP8_stock
Changes:
faster initialization of kgsl/3d adreno graphics driver (quicker boot)
removed (for now): DTS Eagle - caused more noticeable humming/buzzing/whirring of sound at lower volume levels with aqstic (internal) DAC
timers: fix for lock contention and failing
CIFS/SMB: security fixes up-to-date [driver not used right now]
qcacld-3.0: updated WiFi driver & firmware to latest revision for Android 8.1
removed: LiveDisplay driver (only used in LineageOS; RR, etc. ?)
[eval] switched to 300Hz tickrate from 1000Hz tickrate which tends to be quite unstable on LG Stock ROMs
wcd934x: (internal DAC) a few fixes & improvements
removed/reverted: change that caused horizontal line of AOD display
several other changes
Click to expand...
Click to collapse
Known issues:
inverted color on AOD display [needs investigation] - e.g. red equals to turquoise for whatever reason
md5sum checksums:
8acd26556f1f6afe1659cff54fe61efc boot_H930_21A_oreo_I_6_WIP8_stock.img
32b8e679cdb8c066cdb945785334822c boot_H930_21A_oreo_I_6_WIP8_stock_PPMd_7z.zip
a29bda002d9c70f617180f3a955cb066 boot_oreo_I_6_WIP8_stock__H932_spr_US__tmo_US_20K.img
b06ddaba4f4c0124448b81ff78f479ba boot_oreo_I_6_WIP8_stock__H932_spr_US__tmo_US_20K_PPMd_7z.zip
3c46f82d1bb45e2fe3dfe5fc55f8b815 boot_oreo_I_6_WIP8_stock__US998init_spr_US_20E.img
e7d42505842abcb08e3ec0c90c26924d boot_oreo_I_6_WIP8_stock__US998init_spr_US_20E_PPMd_7z.zip
Click to expand...
Click to collapse
oreo_I_6_WIP9_7_5_2_stock
Leaving this here for a bit (from the Telegram Group https://t.me/LGEV30 ):
New experimental/WIP kernel for Stock LG ROMs [regression fix, headset detection might stop working after a while]
internet max throughput should be 25-30% higher than before, ZZMoove governor is onboard along with other custom ones (cultivation, impulse, blu_active), MPTCP got updated, additional fixes & improvements to cut down latency & raise stability, ppp subsystem has been updated and enhanced (potentially fixing VPN connection issue), peripheral-loader, slimbus, glink subsystem updated; camera actuator updated - uses boost to make zooming smoother, several other subsystems updated, cpu_input_boost used - screen output smoothing/boosting, oom handling fixed/improved, HSWAP (swap + lmk + page_alloc LG in-house variant) disabled in favor of upstream lmk, binder fixes and improvements, regulator fixes & improvements, mempolicy got updated, eliminated a few battery drainers (idle drain should be lower)
H930/H930DS, 21A:
https://drive.google.com/open?id=1iyX8yY8QuX1ZJv8VcUn9CEpx4bOtaU98
US998, 20E:
https://drive.google.com/open?id=1ne06IAK4AJ7k22OYiD91yicjkp0nGtZ-
H932, 20K:
https://drive.google.com/open?id=1s6y8YSEdh5QXheqPrEaqdSiiYdc6QsO-
open towards suggestions on how to reduce battery consumption of WiFi usage further
Click to expand...
Click to collapse
Kernel source branch:
oreo_I_6_WIP9_7_stock__H932__US998_spr_US
Click to expand...
Click to collapse
Note:
Attached file is a 7zip (PPMd compression) renamed to zip due to filesize limitation
rename to .7z and extract - some archiver can handle the file without renaming ...
#4
due to attachment size limitations - the file was packed with 7z PPMd (max) compression, then renamed to .zip, so: rename to .7z and unpack
afterwards flash the boot.img either
via fastboot flash boot boot
via TWRP
oreo_I_6_WIP7_3 (almost identical to current LG Stock ROM kernel)
Branch:
pie_I_6_WIP7_3
Changes:
rolled back kernel to earlier state (October 1st), troubleshooting stability
re-added sdcardfs aosp msm upstream changes, mostly "Drop dentry cache to prevent unknown file status" change in behavior (data integrity)
sdcardfs fixes
ext4, f2fs, ecryptfs and fscrypt updates and changes close to latest upstream
lockdep improvements
further oom, oom_reaper, fork-handling fixes and improvements
force 16b ECC for pstore
scheduler fixes (hmp.c; ...)
updated simple_lmk (not used in this branch)
[eval] reverting to basic optimizations for armv8-a
[eval] reverting to Google's 4.9 Toolchain (best compatibility, stability, etc.)
devfreq fixes and improvements
PCIe wake improvement for msm8998
configure i2c for bit-banging bus recovery
[eval] revert several previous changes
several other changes
Click to expand...
Click to collapse
md5sum checksums:
0639cd649bd4d8aa27bf2db5ed065761 boot_oreo_I_6_WIP7_3_H930_AOSiP-8.1-Derp_29.08.2018.img
3807e6991580b96ec796836c8c1f1bb7 boot_oreo_I_6_WIP7_3_H930_AOSiP-8.1-Derp_29.08.2018_PPMd_7z.zip
9ecaafd28851c2471c4c4de0dbd8e6be boot_oreo_I_6_WIP7_3_H930_lOS-15.1_27.09.2018.img
f148bd763cbb606508ac332b45ef15a7 boot_oreo_I_6_WIP7_3_H930_lOS-15.1_27.09.2018_PPMd_7z.zip
d9ead2f72bd19d02d50a9bf12bb85a79 boot_oreo_I_6_WIP7_3_H930_RR-O-6.1.0_29.08.2018.img
59aee22119d981b8aa91c1c846a5075e boot_oreo_I_6_WIP7_3_H930_RR-O-6.1.0_29.08.2018_PPMd_7z.zip
2a60f4130b4005736fdba05981cff408 boot_oreo_I_6_WIP7_3_H930_dotOS_2.5_27.09.2018.img
f7643c6f30c61755f7e066b4ff4d5fae boot_oreo_I_6_WIP7_3_H930_dotOS_2.5_27.09.2018_PPMd_7z.zip
Click to expand...
Click to collapse
these 4 different Kernel releases are needed because the ramdisk/init content is fundamentally different preventing the phone/ROM from booting if it doesn't match
Dirty Unicorns 9.0-based Kernels (06.10.2018 build):
see attachment
Checksums (md5sum) :
be498bf45017a28d7ead8ccada514868 boot_pie_I_6_WIP3__DU_9.0__06.10.2018.img
30c34e1566fece2ac8721868fa89b88c boot_pie_I_6_WIP3__DU_9.0__06.10.2018_PPMd_7z.zip
a4425bb19177033622d402c3b6795a4d boot_pie_I_6_WIP4__DU_9.0__06.10.2018.img
f89adcd02831700eed629195639497c7 boot_pie_I_6_WIP4__DU_9.0__06.10.2018_PPMd_7z.zip
please also take a look at the "experimental" folder if there are newer ones there (currently: 26.10.2018 - there are none newer ones)
edit (01.09.2018):
removed the attached kernel since 3 different kernels, depending on ROM, are needed to avoid confusion
edit (26.10.2018):
added updated kernels for recent AOSiP, lineageOS 15.1, Resurrection Remix Oreo 6.1.0, dotOS 2.5 builds (all Android Oreo, 8.1)
Interested in checking this out. Would I be able to get past bootloops on an already loaded rom full of Magisk mods or would this need to be done solely through clean rom flashes?
XCaliburX said:
Interested in checking this out. Would I be able to get past bootloops on an already loaded rom full of Magisk mods or would this need to be done solely through clean rom flashes?
Click to expand...
Click to collapse
Not sure what you mean with "solely through clean rom flashes"
Just do a TWRP backup of each partition separately: /boot, /system, /data
then get into fastboot:
boot into bootloader (adb reboot bootloader)
turn phone OFF, connect USB cable to phone, hold volume down - connect other end to PC
First test-run to see if it boots for you:
Code:
fastboot boot boot.img
then
Code:
fastboot flash boot boot.img
after that boot into TWRP and flash Magisk.
I've had Magisk installed before and after each kernel flash you, of course, need to install Magisk again (Magisk Mods probably, too - that at least was the case I tried NanoMod/microG via Magisk).
tl;dr
bootloops or longer booting would/could still happen no matter ROM state - ideally you should be able to flash or fastboot boot the new kernel without issues
Magisk always needs to be re-installed after new kernel (boot.img) flash, same applies to Magisk modules
Thanks
Nvm.
Thanks for your work. Is it possible to flash your kernel, as img, in twrp as usual ? Whithout using adb code ?
Envoyé de mon LG-H930 en utilisant Tapatalk
XCaliburX said:
Nvm.
Click to expand...
Click to collapse
Thanks for your comment (before replacing it )
You ran into any issues ?
The stable kernel/branch is more suitable to gain battery savings since it has the phy-off change included that allows the phy power supply to be turned off during idle state and the scheduler change (the "old" one doesn't - it constitutes the absolute bare minimum).
The scheduler change effectively reduces battery consumption during usage by approx. by half (confirmed with e.g. music playback with PowerAMP).
The flashing is actually quite straight-forward, the notes in OP / first post matches with the previous (incomplete) understanding I had how the device behaves and needs to be amended once I further understand how to most efficiently
do all the steps ...
The device (or bootloader) seems it's set up that way to bootloop (when a broken kernel/boot.img is flashed) - returning to the warning screen that the bootloader is unlocked - and once the phone was turned off (via Power button), it'll immediately boot successfully via the existing kernel on the boot partition to the ROM.
So with the boot.img files I offer actually non of the bootlooping should happen (after flashing Magisk, it'll reboot once but should boot into ROM afterwards).
There are additional power savings possible e.g. sending the GPU off to nap once it's idle but that needs careful tuning to reduce lag/non-smoothness - which I currently don't have time to do,
also we're limited to using the enhanced HMP kernel for now - EAS is off limits, so that should prevent further power savings and enhanced smoothness with high efficiency.
guigui33 said:
Thanks for your work. Is it possible to flash your kernel, as img, in twrp as usual ? Whithout using adb code ?
Envoyé de mon LG-H930 en utilisant Tapatalk
Click to expand...
Click to collapse
I haven't tried doing that yet,
but if that possibility is there it most probably should work - please give it a try
Merci
No problem flashing .img via TWRP. flashed the "stable" Kernel 2h after OP posted the links. Running fine for now w/o problems. Smooth as butter und more battery friendly than stock
Great work i have to say.
Cheers
Just a question. I replaced the kernel boot.img of a rom inside the zip with the "old" kernel. After coming across some problems, I decided to wipe partitions and restore a previous save. When I tried this, the restore would send me to the bootloader screen instead of rebooting. Is there something wrong with the save or does this mean there's some conflict with the kernel the phone's currently on and the saved restore's kernel? I'm only able to boot if I fresh reinstall the rom with the original kernel intact. Phone is a US998R.
Will try the "stable" kernel and report back if I come across anything.
XCaliburX said:
Just a question. I replaced the kernel boot.img of a rom inside the zip with the "old" kernel. After coming across some problems, I decided to wipe partitions and restore a previous save. When I tried this, the restore would send me to the bootloader screen instead of rebooting. Is there something wrong with the save or does this mean there's some conflict with the kernel the phone's currently on and the saved restore's kernel? I'm only able to boot if I fresh reinstall the rom with the original kernel intact. Phone is a US998R.
Will try the "stable" kernel and report back if I come across anything.
Click to expand...
Click to collapse
Both "old" and "stable" kernels use the "stock" modified ramdisk from SGCMarkus which was working fine while flashing his debloated (Korean origin) Stock ROM,
it could be that the device nevertheless is reacting allergic to modifications/deviations from a kernel which is very close to stock.
Can't really tell what could be the reason for it to react up - HOWEVER nothing in "old" kernel looks suspicious to can cause that.
tl;dr:
no idea
in case of doubt use completely stock kernel
don't forget to use rctd-disabler & no-verity/forced-encrypt disabler
once you have a working base, go from there
As someone with one of the"Franken-phones" ( h931 flashed to us 998 nougat and updated to Oreo via LGUP) would it be worth trying to flash this kernal? Currently these devices have issues with the Aosp roms and therefore require a rom that is closer to stock in order to avoid bootlooping. In settings my lgv30 displays as a H930 unit, so theoretically it could work.. would be nice to get a customized kernal. Any input would be appreciated. Thanks
MetaMaverick said:
As someone with one of the"Franken-phones" ( h931 flashed to us 998 nougat and updated to Oreo via LGUP) would it be worth trying to flash this kernal? Currently these devices have issues with the Aosp roms and therefore require a rom that is closer to stock in order to avoid bootlooping. In settings my lgv30 displays as a H930 unit, so theoretically it could work.. would be nice to get a customized kernal. Any input would be appreciated. Thanks
Click to expand...
Click to collapse
That's an AT&T/Time Warner model, right ?
it uses a different mode of operation/has changes in ecryptfs
runs in FIPS mode
has an in-built VpnClient security module which supports an "interceptor" netfilter module
doesn't seem to have multi-path (MPTCP) vs. the global model (or at least kernel config)
it comes with an enhanced TrustZone/qseecom driver "to enable Periodic Kernel Monitoring driver for LG IMA" (PKM)
adds support for "ccaudit logging using additional fifth buffer" (which doesn nothing ?)
haven't seen the ramdisk yet (boot.img ?)
but I guess there might be interference as soon as the kernel strays too much from stock since qseecom/TZ is involved which pretty quickly can lead to a non-booting kernel on Stock ROM (had it happen on Z5).
There might very well be additional changes from the global (H930) model - I've only looked at the main files so far ...
I have flashed the bleeding version, and it seems to be hard to boot with and to make a battery drain.
I'm on the stock twrp rom.
I flash then the stable kernel, and lt's better, the boot is fast and it seems to have no battery drain.
In case of problem, can you join the stock kernel in the topic to be flashable as image or zip via twrp ?
Good work !
Envoyé de mon LG-H930 en utilisant Tapatalk
Using the stable on ls998 stock and boots nicely...no issues so far...hopefuly be able to squeeze a bit of extra battery life out with it...thank you and great work...on another note i flashed as an image through twrp without issues
Reboots a few seconds after unlocking screen. Kmesg from twrp. Ls998 (converted from Verizon). Pretty sure twrp grabs the correct kmesg
Happens on stable and old.
TotallyAnxious said:
Reboots a few seconds after unlocking screen. Kmesg from twrp. Ls998 (converted from Verizon). Pretty sure twrp grabs the correct kmesg
Happens on stable and old.
Click to expand...
Click to collapse
Thanks for the feedback,
nope though:
Linux version 4.4.78-perf+ ([email protected]) (gcc version 4.9.x 20150123 (prerelease) (GCC) ) #11 SMP PREEMPT Sat Mar 24 22:16:32 CET 2018
Click to expand...
Click to collapse
that one's from SGCMarkus.
Can you post more info how your system is set up ?
zacharias.maladroit said:
Thanks for the feedback,
nope though:
that one's from SGCMarkus
Click to expand...
Click to collapse
I'm having trouble figuring out a way to get a kernel log then. The phone reboots too soon for adb. Any ideas? Google has only shown me ways when the phone is working normally and reboots.
---------- Post added at 02:01 AM ---------- Previous post was at 01:57 AM ----------
zacharias.maladroit said:
Can you post more info how your system is set up ?
Click to expand...
Click to collapse
Debloated from latest kdz Oreo. Magisk 16.4. I flash the img, flash magisk 16.4 then reboot. I've tried keeping wifi off (didn't change anything). I've tried with and without my personal magisk mod. All that's left is magisk mods like BusyBox and other utilities.
Kirisakura-Kernel for the Asus Rog Phone 2
Hello everyone,
I proudly present Kirisakura-Kernel made for the Asus Rog Phone 2 aka Yoda!
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 foucs during testing! This includes Linux-Stable, CAF-Upstream and kernel/common.
Kernel Control Flow Integrity (Kernel-CFI), which is achieved by linking the kernel with LLD and Link Time Optimization (LTO), more precisely ThinLTO, are quite unique security features. In fact this may be one of the only 4.14 msm kernels with a fully working Kernel-CFI implementation and CFI-Violations fixed on a smartphone.
The only kernels made by OEMs offering this security feature are the ones for the Pixel 3 and Pixel 4 devices.
If that 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 855+ that´s built into the Asus Rog Phone 2.
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 others 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 kernel includes a lot of improvements and contributions from other developers as well. Without this kernel would not exist.
Many others contributed in some way or another to this kernel.
A big thanks to all of them at this place!
Now lets continue with a list of features in the next paragraph!
Main Features:
- Based on latest kernel sources from Asus for Android 11 and intended for use on Asus Stock Rom
- compiled with Clang 13.0.1 and built with -O3 speed optimizations
- Linux-Stable-Upstream included to 4.14.243
- CAF-Upstream merged
- Link the kernel with LLD and use KASLR
- include all important fixes/improvements from kernel/common
- F2FS implementation updated to latest state of kernel/common and kernel.org maintained by Jaegeuk Kim.
- Safety Net patches are included -> Kernel passes Safety Net
- Flashing the kernel will keep root!
- Sweep to sleep functionality
- Flashable via EXKM and FKM on a rooted system!
- specifically tuned EAS for the Asus Rog Phone 2
- removed nolog usage, remove rtb logging from the kernel
- remove selinux auditing from kernel for lower overhead
- remove IPC logging from the kernel
- Anykernel zip is based on the all new Anykernel3 release from @osm0sis
- option for 144hz refresh rate (Android 10 only)
- option to improve visibility in dark scenes
EAS related features:
- EAS implementation patched up to latest CAF state
- disable autogroups and use cgroups for more efficient task placement!
- Dynamic Stune Boost to inflate task utilization and not overload cores on interaction (thanks to @RenderBroken and @joshuous )
- improved schedutil governor
- updates from kernel/common
CPU related features:
- Power saving workingqueues enabled by default
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
- include cpuidle patches from CAF
- improvements to cpufreq/times/stats
- vDSO 32 patches to improve 32-bit performance
- arm64: lse: Prefetch operands to speed up atomic operations (thanks to @kdrag0n )
File System related features:
- F2FS implementation updated to latest state of kernel/common and F2FS-Mainline on kernel.org maintained by Jaegeuk Kim.
- 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.)
- adapt F2FS to be inline with Pixel 4s code from Google, which is also directly maintained by Jaegeuk Kim
- include a few F2FS fixes from the Pixel 4 kernel
- include optimizations to UFS-Driver from Pixel 4
- various improvements to FS-Performance from the Pixel 4
- f2fs fix to prevent data loss in case of sudden power failure
GPU related features:
- Update GPU driver to latest CAF state
- remove debugging and non-sd855+ specific code from the GPU driver
- introduce low priority worker thread to improve performance in UI-critical situations
Network related features:
- Wireguard Support (Details)
- advanced TCP algorithms enabled
- includes new bbr and bbr2
Memory related features:
- Speculative Page Faults (1. 2) (CAF default)
- enabled per process reclaim (CAF default)
- Fix various memory leaks in different subsystems
- improved mm with patches from latest mainline
- various other changes from mainline
- included zstd and lz0-rle as options for ZRAM-algorithm (lz4 is probably the best all around, so only change it if you know why and what you are doing)
- allow swappiness up to a value of 200
- remove unused mem regions to free more RAM (thanks to @kdrag0n )
Security related features:
- Control-Flow-Integration (CFI) andLink-Time-Optimization (LTO) ported from 4.14 kernel/common and Pixel 4 Kernel
- Shadow Call Stack ported from 4.14 kernel/common and Pixel 4 Kernel
- enable init_on_alloc for even more security, more information can be found in the commit message
Misc Features:
TCP Congestion Algorithms:
- advanced algorithms enabled
- includes new bbr2
Wakelock Blocker:
- advanced wakelock blocker with the ability to block any wakelocks (dangerous, use with caution)
- please read [URL="https://arstechnica.com/gadgets/2018/08/p-is-for-power-how-google-tests-tracks-and-improves-android-battery-life/"]this for further info
Other features:
- disable logging and debugging to make the kernel more lightweight in various places (includes binder, mm, vma, gpu, ipa etc)
- remove VLAs from the kernel (more info)
- add support for steam controller
- add support for nintendo switch controller
Feature section for the "non visible" but perceptible improvements:
- updated binder section (responsible for interprocess communication)
- updated sdcardfs ; have a read about it here:
- fix CFI violations
- add ramoops/pstore support (thanks @luca020400)
Requirements
- unlocked Bootloader
- USB-Debugging in developer options enabled
- latest adb and fastboot binaries
- working adb and fastboot environment
- magisk root
- a backup of boot.img and dtbo.img to be able to restore to stock. you should be able to do this easily via TWRP.
How to flash the Kernel:
1. Download the latest kernel.zip and make sure you have properly updated to the latest Asus Firmware
1a. Optional: While it may not be necessary all times, you may want to restore stock boot.img and dtbo.img, re-root with magisk and optionally install twrp.zip if coming from another kernel. Before reporting issues make sure you do that! Thank you!
2. Make sure to use latest Magisk stable. (not the latest canary!)
3. Flash the kernel.zip via latest EXKM or FKM app, or TWRP (haven´t tested TWRP myself as I don´t need it) and do a full reboot.
4. Flash the kernel again. This step is needed because flashing the kernel disables verity on vendor in order to modify two files. Disabling verity takes a reboot. Flashing the second time allows the two files to be changed correctly. This step is necessary if you flashed a firmware update. (This step should not be necessary when updating my kernel, if you are already running it, but if you want to be on the safe side just flash it twice)
5. Reboot and profit. It will take around 15 seconds for the kernel and the system to execute all changes done by flashing the kernel.zip. After 15 seconds 120fps will kick in, if you use 120fps setting!
DOWNLOAD:
Download is located always in this folder:
https://www.androidfilehost.com/?w=files&flid=303784
Important: Read after Download
Please take a look at the second post after flashing the kernel!
Changelog:
Android 9
1.0.0 Initial Release
1.0.2 https://forum.xda-developers.com/showpost.php?p=81389411&postcount=33
Android 10
2.0.0 https://forum.xda-developers.com/showpost.php?p=82238713&postcount=141
2.1.0 https://forum.xda-developers.com/showpost.php?p=82317211&postcount=191
2.6.0 https://forum.xda-developers.com/showpost.php?p=82495531&postcount=252
2.6.2 https://forum.xda-developers.com/showpost.php?p=82560081&postcount=261
2.6.4 https://forum.xda-developers.com/showpost.php?p=82602927&postcount=267
2.7.2 https://forum.xda-developers.com/showpost.php?p=82834055&postcount=281
2.7.5 https://forum.xda-developers.com/showpost.php?p=82837791&postcount=285
2.9.0 https://forum.xda-developers.com/showpost.php?p=83100663&postcount=306
3.0.6 https://forum.xda-developers.com/showpost.php?p=83526987&postcount=391
3.1.0 https://forum.xda-developers.com/showpost.php?p=83606511&postcount=406
3.1.3 https://forum.xda-developers.com/t/...us-rog-phone-2-aka-yoda.4028237/post-84124933
3.1.5 https://forum.xda-developers.com/t/...us-rog-phone-2-aka-yoda.4028237/post-84617449
3.2.0 https://forum.xda-developers.com/t/...us-rog-phone-2-aka-yoda.4028237/post-84717691
3.2.1 https://forum.xda-developers.com/t/...us-rog-phone-2-aka-yoda.4028237/post-84799241
3.2.2 https://forum.xda-developers.com/t/...us-rog-phone-2-aka-yoda.4028237/post-85145887
3.2.3 https://forum.xda-developers.com/t/...us-rog-phone-2-aka-yoda.4028237/post-85431627
Android 11
1.0.0_R https://forum.xda-developers.com/t/...us-rog-phone-2-aka-yoda.4028237/post-86201183
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:
Asus for the Rog Phone 2
@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!
@arter97 for giving me advice
@kdrag0n for his help too
@topjohnwu for magisk!
@osm0sis for anykernel!
XDA:DevDB Information
Kirisakura Kernel, Kernel for the ASUS ROG Phone II
Contributors
Freak07
Source Code: https://github.com/freak07/Kirisakura_Yoda
F.A.Q:
Question: Why does the kernel version show as "unavailable" in settings after flashing it.
Answer: Asus does not allow for custom kernel names in their settings. Use a kernel manager to check the kernel version.
Question: Is root preserved when flashing this kernel?
Answer: Yes the Anykernel Zip will detect root and keep it.
Question: How do I return back to stock or another kernel.
Answer: Extract boot.img as well as dtbo.img from matching firmware you are on and flash the extracted boot.img via fastboot.
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, data traffic 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!
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!
android-tools/guides/proper_bug_reporting.txt at main · nathanchance/android-tools
Publicly available Android stuff. Contribute to nathanchance/android-tools development by creating an account on GitHub.
github.com
and one more for me
Wow!!! Awesome! Plans for kcal in the future?
Thank you so much for giving me a reason to unlock the bootloader. Finally am happy to see development for the device and that too from a well known developer ???? cheers mate and a very happy new year.
Can I flash Android 10 beta fota file to my cn version phone using this recovery?
I love your work bro keep this devlopment continue
All rog2 user support your hardwork ,
And more developer will come after seeing your hardwork
a5he said:
Can I flash Android 10 beta fota file to my cn version phone using this recovery?
Click to expand...
Click to collapse
please help..now my device stuck and keep looping in bootloader mode after trying to flash this kernel on Android 10 beta fota..and i cant reboot into twrp recovery and system..
sakamaki izayoi said:
please help..now my device stuck and keep looping in bootloader mode after trying to flash this kernel on Android 10 beta fota..and i cant reboot into twrp recovery and system..
Click to expand...
Click to collapse
flash the boot.img extracted from the android 10 beta firmware via fastboot.
Kernel is made for Android Pie as stated in the OP.
Welcome bro and thanks for the first rog 2 custom kernel.. ?
After flashing in twrp it says i should flash companion magisk module. Is there one yet?
mohammed510 said:
Welcome bro and thanks for the first rog 2 custom kernel.. ?
After flashing in twrp it says i should flash companion magisk module. Is there one yet?
Click to expand...
Click to collapse
Oh that’s a remnant of another kernel in the flashing script.
No there is none needed. I’ll remove that message in the next release!
thanks for the hint!
You just gave me a reason to unlock my bootloader and go back to Pie
What a day! Thanks a lot @Freak07! I'm happy for you being around!
Cheers,
anthonws.
sakamaki izayoi said:
please help..now my device stuck and keep looping in bootloader mode after trying to flash this kernel on Android 10 beta fota..and i cant reboot into twrp recovery and system..
Click to expand...
Click to collapse
Extract the boot.img from Update and flash it under .img in twrp.
Goodluck
Very thanks
Please work on power saving and governor
Thank you for joining the ROG 2 Forums @Freak07
apollo3x said:
Extract the boot.img from Update and flash it under .img in twrp.
Goodluck
Click to expand...
Click to collapse
How to extract the Payload file of Android 10 FOTA?
The current Payload dumper doesn't support it.
Thank you so much for your hard work, I can't wait for you to make an version for Android 10 , hopefully once we have a custom kernel we can finally enjoy the 6000 mah battery
Mohamad313 said:
Very thanks
Please work on power saving and governor
Click to expand...
Click to collapse
avivv said:
Thank you so much for your hard work, I can't wait for you to make an version for Android 10 , hopefully once we have a custom kernel we can finally enjoy the 6000 mah battery
Click to expand...
Click to collapse
No idea about Android 10, but I’m enjoying the 6000mah on Pie already. That Android 10 build floating around is no finished or final piece of software.
I’ll attach my current stats from this morning.
No extensive gaming, mainly browsing, exploring the phone, massaging, videos, some calls etc.
but all on constant 120hz.
Wow that's great stats, when I had android 9 I the battery life was worst than I expected, if there was a way to rollback to android 9 without wiping the data I would have done it just to try this kernel.
would it be possible to add battery charge limiting support? currently apps like ACC don't work with this phone.