This is my Squid Kernel for the 2015 Moto E LTE. It's based off the stock kernel available on Motorola's GitHub. Flash it using TWRP. Bug reports and contributions are welcome.
This is a development thread. Questions should go in the Q&A thread.
Disclaimer:
This is for the 2015 Moto E LTE only! Version r22b and up require ROMs with an updated ACDB (audio calibration database) loader, such as LineageOS 14.1 builds from January 2018 and newer. If your ROM has an incompatible ACDB loader, you may experience low audio volume. Stick with version r22 for Marshmallow ROMs (including stock) and older Nougat ROMs without an updated ACDB loader.
You must update your modem to the Android 5.1 version or newer for the r12 kernel and newer to work properly. You can find modems in the modems thread. If you can't find an up to date modem for your variant and are running a Marshmallow ROM, try the older r15c version. The r6-r11e kernels are for 5.1 ROMs only. Don't flash this on the 3G model. This kernel is provided AS-IS, with no warranties. I am not responsible for bricking your device. Flash at your own risk.
Features:
LED notification support
Moderately undervolted
Updated to Linux 3.10.108
Synced with latest CodeAurora changes
Improved memory caching backported from Linux 3.15
Improved storage performance
Optimized ARM crypto routines
Updated f2fs and WiFi drivers
FIOPS and BFQ I/O schedulers
Lionfish CPU governor
IntelliPlug CPU hotplug (by faux123)
KCAL MDP5 colour control (by savoca)
Improved zRAM backported from Linux 4.9
Vibration intensity control
Compiled with Linaro GCC 7.3 and optimized for Cortex A53
Stripped down and optimized configuration
Release History:
Code:
r23: August 15, 2018
- Fixed surnia front camera
- Tonnes of security patches
- Updated binder
- Compiled with Linaro GCC 7.3.1
r22b: January 13, 2018
- Audio driver fixes
- Requires a ROM with an updated ACDB loader
r22: January 11, 2018
- Security patches
- Updated camera drivers
r21: December 6, 2017
- Updated to Linux 3.10.108
- Security patches
- Oreo support related patches
r20: August 2, 2017
- Updated to Linux 3.10.107
- Tonnes of security patches from many places
- Updated sdcardfs from Google
- Updated WiFi driver from CAF
- Compiled with Linaro GCC 6.3.1
r19: January 1, 2017
- Added support for Nougat ROMs
- Updated zRAM from Linux 4.9
- Updated (optimized) FUSE from CAF
- Kernel ASLR and many info leak fixes
- ARM PXN support for exploit mitigation
- Tons of security updates
- Some CAF updated from LA.BR.1.2.9_rb1.10
- Fixed kernel panic on VPN disconnection
- Updated compiler to Linaro GCC 6.2.1
r18: November 8, 2016
- Tons of security updates
- Updated to Linux 3.10.104
- Updates from Motorola Harpia kernel
- GPU driver latency reduction
r17: August 16, 2016
- Security updates
- Updated to Linux 3.10.102
- CyanogenMod compatibility updates
r16g: May 16, 2016
- Security updates
r16f: April 14, 2016
- Reverted f2fs update
- Updated zRAM from Linux 4.4
r16d: April 8, 2016
- Security fixes
- Vibration intensity control
- Updated f2fs
- Patches for CM13 compatibility
- IntelliPlug disabled by default
- Built with Linaro GCC 5.3
r16: March 20, 2016
- Updated to Linux 3.10.101
- Updated to Motorola MPD24.107
- Updated WiFi driver from CAF
- IO optimizations under heavy load
- Miscellaneous bug and security fixes
r15c: March 5, 2016
- Updated to Linux 3.10.99
- Updated camera driver configuration
- Compatible with Marshmallow stock ROM
r15b: Feburary 27, 2016
- Updated to Linux 3.10.98
- ARMv8 crypto related fixes
- Use ARMv8 crypto for adopted storage
r15: February 6, 2016
- Updated to Linux 3.10.96
- Updated f2fs from Linux 4.5
- Kernel library optimizations
- Improved CFQ IO scheduler
- Improved kernel PRNG
- ARMv8 accelerated crypto support
- Better use of ARM instruction set
- Added minimum CPUs parameter for IntelliPlug
- Miscellaneous bug fixes
r14b: January 23, 2016
- Fixed low/poor call audio
- Security fix for CVE-2016-0728
r14: January 16, 2016
- MARSHMALLOW ONLY
- Updated to Motorola Marshmallow sources
- Updates from CAF LA.BR.1.2.7_rb1.1
- Security and bug fixes from Linux 3.12.52
- Compatible with Marshmallow stock ROM
- More than a dozen CAF security fixes
- Miscellaneous bug fixes
- Somewhat smoother animations
r12: December 25, 2015
- FOR CM13 ONLY!!!
- Updated to Linux 3.10.94
- Updated to LA.BR.1.1.3_rb1.41
- Updated zRAM
- Improved memory caching scheme from Linux 3.15
- Optimized memory allocation and management
- Optimized CPU scheduler
- Optimized performance event tracking
r11e: December 1, 2015
- Fixed some cpufreq races
- Minor bug fixes
r10g: November 11, 2015
- Patched Pronto CR-930533 vulnerability
- Fixed possible use-after-free in zRAM
- Updated to Linux 3.10.93
- Compiled with Linaro GCC 5.1
r10f: November 8, 2015
- Updated to Linux 3.10.92
- Updated to CAF LA.BR.1.1.3_rb1.36
- Updated to Moto Maxx 2 Kernel
- Security and stability improvements
r10d: October 26, 2015
- Fixed r10c SELinux regression on stock ROM
r10c: October 24, 2015
- Fixed encryption
- Patches for Android 6.0 compatibility
r10b: October 4, 2015
- Fixed move app to SD card issue
- Cleaned up DTBs to reduce size
r10: October 3, 2015
- Added KCAL colour control (by savoca)
- Added optimized crypto routines for ARM
- Updated to Linux 3.10.90
- Optimized memory performance
- General cleanup and optimization
r9e: October 1, 2015
- Updated to lux kernel sources
- Updated to Linux 3.10.89
- Updated to LA.BR.1.1.3_rb1.32
- Small tweaks and optimizations
r8: Septemver 15, 2015
- Updated to Linux 3.10.88
- Updated to LA.BR.1.13_rb1.29
- Improved zRAM backported from Linux 4.1
- WiFi driver background scan changes
- Added adaptive low memory killer
- Included the WLAN NV patch I had posted earlier
r7f: August 25, 2015
- Downgraded WiFi driver to LA.BR.1.1.2_rb1.18
- This actually fixes the WiFi crashes :D
r7e: August 25, 2015
- Added LED notification support
- Updated WiFi driver to LA.BR.1.2.4_rb1.14
- Maybe this will fix bootloop issues for affected users
r7d: August 23, 2015
- Updated everything to LA.BR.1.1.3_rb1.25
- There were some interesting WLAN driver changes
- Maybe this will fix WiFi bootloop issue in r7c
r7c: August 20, 2015
- Updated WiFi driver to LA.BR.1.1.3_rb1.23
- Maybe it will fix DHCP issues with certain routers
r7b: August 19, 2015
- New universal flashing script
- Works on any surnia variant and ROM
r7: August 19, 2015
- Updated to Linux 3.10.87
- Updated to Qualcomm LA.BR.1.1.3_rb1.24
- Updated to Motorola MMI-LPI23.72-9
- Added a few extra WiFi driver options
- Added CPU touch booster feature
r6: July 28, 2015
- Rebased for use on 5.1 ROMS ONLY
- Updated to Qualcomm's LA.BR.1.1.3_rb1.21 release
- Updated to Linux 3.10.84
- Updated WiFi drivers
- Added my new and original Lionfish CPU governor
- Added Conservative CPU governor
- Added faux123's IntelliPlug CPU hotplug implementation
- Added BFQ IO scheduler
- Numerous bug fixes
r5: April 21, 2015
- Updated to Linux 3.10.75
- Added FIOPS I/O scheduler
- Updated f2fs drivers backported from Linux 4.0
- Milder undervolt for improved stability and compatibility
- Uses full Boost Mobile ramdisk for CDMA variant
r4: April 15, 2015
- Updated to Linux 3.10.74
- Milder undervolt to better support all devices
- Cleaned up defconfig and device tree
- Various minor bugfixes
r3c: April 5, 2015
- Fixed still picture taking with front-facing camera
r3: April 4, 2015
- Initial public release
Downloads:
Main downloads tab
XDA:DevDB Information
Squid Kernel for Styx LTE, Kernel for the Moto E 2015
Contributors
squid2
Source Code: https://github.com/sultanqasim/android_kernel_motorola_msm8916
Kernel Special Features: undervolted, lionfish, fiops, intelliplug, latest Linux and Qualcomm fixes
Version Information
Status: Stable
Current Stable Version: r23
Stable Release Date: 2018-08-15
Created 2015-04-04
Last Updated 2018-08-15
Squid TWRP
I also have a TWRP build that uses my kernel, compiled from source with the OmniRom tree. Links for it are it are on the main download tab. My device tree for it is on GitHub. My device tree is based off Cybojenix's TWRP tree for this device, but it uses a special stripped down version of my kernel instead of the prebuilt stock kernel. That is why my TWRP is 4 MB smaller than the Cybojenix version.
The latest build of my TWRP shows the correct time and includes hardware encryption support (thanks @vlcdsm).
UPDATE: I've made a separate thread for this TWRP.
Installation Instructions
The r11e version is the latest for Lollipop 5.1 ROMs. CM12.1 users and LPI23.29 stock users should use the version posted here. Users of the new LPI23.72 stock 5.1.1 should use the osprey version instead. See squid_kernel_r11e-osprey-stock.zip
For CM13 and similar Marshmallow ROMs, use my latest version (r12 at the moment).
My suggested install procedure:
Boot into TWRP (make sure you have a suitable ROM installed)
Flash my kernel zip.
Reboot into Android.
After following these steps, you will be running my new kernel. You can verify in Settings->About phone->Kernel version. If the ROM behaves strangely on first boot, reboot the phone. It should be stable after the second boot.
Attention 5.0 Stock ROM Users:
The latest versions of this kernel (r6 and up) are only for 5.1 ROMs. I suggest that you update to 5.1 if possible. If you need to stay on 5.0 and want my kernel, you will need to use the old r5 version.
Lionfish and Recommended Settings
My new Lionfish governor combines traits of the conservative, ondemand, and interactive governors. It is designed to maximize battery life without noticeably impacting performance. It responds quickly to heavy loads (similar to ondemand and interactive) while staying within the region of optimal CPU performance per watt. With moderate loads, it periodically votes to raise, maintain, or decrease the frequency. When there are enough votes to change the frequency, it is ramped up and down gradually. The voting mechanism reduces frequency jitter compared to ondemand and conservative. My testing had found that this governor uses moderate frequencies (where efficiency is optimal) more effectively than interactive, ondemand, and conservative. This improved frequency distribution results in a moderate reduction in CPU power consumption while maintaining responsiveness comparable to the interactive governor.
IntelliPlug is enabled by default in this kernel. The default governor is still interactive. For optimal performance and battery life, I recommend using the fiops IO scheduler, Lionfish governor, and lowering the CPU idle frequency to 400 MHz (from the default of 800 MHz). The combination of IntelliPlug, Lionfish, undervolting, and reducing idle to 400 MHz should result in a CPU power consumption reduction of around 20% compared to the stock kernel. This will typically correspond to 8-15% increase in battery life compared to the stock configuration.
Well my phone is acting up, and I need to go ahead and start testing roms and things, but this seems like a great way to go! Anyone try this yet? Or will I be the first one? Thanks for your work dev!
squid: your kernel is already interesting, developement sound promising.
report:no problem hang or bootloop during boot,
---------- Post added at 09:30 PM ---------- Previous post was at 09:19 PM ----------
wifi not working unable to turn on,
but camera seems to works definitely even with root.
pixiebob said:
squid: your kernel is already interesting, developement sound promising.
report:no problem hang or bootloop during boot,
---------- Post added at 09:30 PM ---------- Previous post was at 09:19 PM ----------
wifi not working unable to turn on,
but camera seems to works definitely even with root.
Click to expand...
Click to collapse
Hmm, WiFi works fine for me. My kernel requires signed kernel modules, but I do provide a Pronto WLAN driver signed for my kernel in the zip. Could you post the output of dmesg right after your phone boots up? Maybe that would give me a hint as to the cause.
Is anyone else having WiFi issues?
torch2424 said:
Well my phone is acting up, and I need to go ahead and start testing roms and things, but this seems like a great way to go! Anyone try this yet? Or will I be the first one? Thanks for your work dev!
Click to expand...
Click to collapse
Alright! everything working great! Everything works on my end, but I did notice a SLIGHT slowdown on the device with this kernel, but hey it's totally worth it for the root and everything working
My Steps:
I came from a fresh device (Moto E 2015 4g Unlocked GSM) which I never took the time to do anything so here's what i did
1. Unlock Bootloader using this: http://forum.xda-developers.com/mot...tool-moto-e-toolkit-one-click-unlock-t3047150
- Just follow the step and it worked fine for me! however, It wouldnt allow me to flash the recovery, it would just crash so...
2. Install TWRP from this thread: http://forum.xda-developers.com/moto-e-2015/orig-development/twrp-moto-e-2015-recovery-t3049726
- I had to boot into fastboot (Hold Power and volume Down) and boot into my linux (ubuntu) to run the commands and successfully install the recovery
3. Boot into recovery, and BACKUP BACKUP BACKUP!
- To boot into recovery, I boot into fastboot, then use the volume keys until the little Dialog says recovery, the press power. I made a backup with twrp, Forgetting this step sucks, never forget...
4. Flash the kernel
- I flashed the kernel from twrp first to see if it had root pre-installed but it doesn't (Didnt check, but there was no supersu so I'm assuming so). Also, didnt check camera at this point
5. Install superSU/Root from here: http://download.chainfire.eu/696/SuperSU/ . Thank you to spblinux for this post: http://forum.xda-developers.com/showpost.php?p=59761431&postcount=46
- I flashed the zip through twrp, and everything is working fine, and this is where I am now!
Thanks to the dev for his work. I will report back with more usage and thoguhts later!
Edit: Sorry for the typos, I'm a lazy typer. And Dont forget to hit the thanks button to the devs, and also me if I helped you out!
Edit:Edit: The download link is in the first post, there's some tabs at the top that link to it! (Took me a while to fins it haha)
squid2 said:
Hmm, WiFi works fine for me. My kernel requires signed kernel modules, but I do provide a Pronto WLAN driver signed for my kernel in the zip. Could you post the output of dmesg right after your phone boots up? Maybe that would give me a hint as to the cause.
Is anyone else having WiFi issues?
Click to expand...
Click to collapse
here dmsg log, good luck
torch2424 said:
Well my phone is acting up, and I need to go ahead and start testing roms and things, but this seems like a great way to go! Anyone try this yet? Or will I be the first one? Thanks for your work dev!
Click to expand...
Click to collapse
squid2 said:
Hmm, WiFi works fine for me. My kernel requires signed kernel modules, but I do provide a Pronto WLAN driver signed for my kernel in the zip. Could you post the output of dmesg right after your phone boots up? Maybe that would give me a hint as to the cause.
Is anyone else having WiFi issues?
Click to expand...
Click to collapse
Same here, no wifi issues for me! Thanks for the hard work!
pixiebob said:
here dmsg log, good luck
Click to expand...
Click to collapse
I looked through your dmesg log and didn't see anything too noteworthy. I saw one potentially relevant message (below) that came from a piece of code that I added.
Code:
<3>[ 21.821810,1] subsys-pil-tz a21b000.qcom,pronto: wcnss: Failed to load blob wcnss.b11. Retrying. ERR -2
In my testing, I had encountered a race condition that caused WiFI firmware blobs to sometimes fail to load. I implemented a hack to retry loading firmware blobs if the initial loading failed. Quite often, at least one blob seems to fail to load the first time through, but it always works on the second attempt. The same thing happened on your end, as wcnss.b11 failed to load the first time through, but it successfully loaded on the second attempt. Anyway, I don't think this blob is the problem.
Have you tried rebooting and checking if WiFi works after that? I've never had any WiFi issues with my kernel, but I just want to rule out a race condition being the cause of your issue.
One more thing: Could you post the output of "cat /proc/modules" when WiFi is not working?
CDMA Variant Support
On the Q&A thread, bzo22 reported that the Boost Mobile version (XT1526) fails to read the SIM card when running this kernel. I did some preliminary investigation and found that the ramdisks differ. All Canadian variants of the XT1527 (Telus, Videotron, Rogers, and Wind) have the same CID and run the exact same software, free of carrier crapware, bloatware, or spyware. The unlocked variants sold on Motorola's website in the US should also be crapware free, though they have a different CID. However, the Boost Mobile variant is full of carrier specific stuff.
Test Kernel for CDMA Variant
Alright Boost Mobile people, I've made a test kernel for the CDMA variant. I don't know if it will work. Try it out and let me know whether or not your cellular connectivity works.
For some reason, XDA is giving me an "Upload Error: 500" when trying to post it to the downloads section, so I am attaching it to this post instead.
Reminder: THIS TEST KERNEL IS FOR THE LTE CDMA VARIANT (XT1526) ONLY! For the LTE GSM version (XT1527), use the normal version in the downloads section.
Confirmed new kernel is working with cmda variant and yes camera is working
squid2 said:
One more thing: Could you post the output of "cat /proc/modules" when WiFi is not working?
Click to expand...
Click to collapse
sorry but it does nothing:
adb shell
$ cat /proc/modules
cat /proc/modules
---------- Post added at 02:43 PM ---------- Previous post was at 02:24 PM ----------
squid2 said:
Have you tried rebooting and checking if WiFi works after that? I've never had any WiFi issues with my kernel, but I just want to rule out a race condition being the cause of your issue.
?
Click to expand...
Click to collapse
i keep the kernel all the day and it is stable.
concerning wifi i try multiple time to reboot but always unable to turn on
i set minimal frequencie at 200 mhz but the kernel seem unable to reach this minimal ,i think undervolted is the reason of this difficulty being stable at lower frequencie,it is bad for battery life .
pixiebob said:
sorry but it does nothing:
adb shell
$ cat /proc/modules
cat /proc/modules
---------- Post added at 02:43 PM ---------- Previous post was at 02:24 PM ----------
i keep the kernel all the day and it is stable.
concerning wifi i try multiple time to reboot but always unable to turn on
i set minimal frequencie at 200 mhz but the kernel seem unable to reach this minimal ,i think undervolted is the reason of this difficulty being stable at lower frequencie,it is bad for battery life .
Click to expand...
Click to collapse
It looks like the kernel refuses to load modules on your phone. Rather strange, as the provided signed modules seem to work fine for everyone else. What happens when you do this on the phone:
Code:
su
insmod /system/lib/modules/pronto/pronto_wlan.ko
As for the 200 MHz step, I don't think undervolting has anything to do with it. It's probably the governor's fault. Try switching to the ondemand governor. I'm fairly confident that all frequencies will work. With that said, I found that setting the base frequency to 400 MHz gives a smoother experience without hurting battery life noticeably.
squid2 said:
What happens when you do this on the phone:
Code:
su
insmod /system/lib/modules/pronto/pronto_wlan.ko
Click to expand...
Click to collapse
i obtain this on su:
insmod /system/lib/modules/pronto/pronto_wlan.ko
insmod: init_module '/system/lib/modules/pronto/pronto_wlan.ko' failed (Required key not available)
pixiebob said:
i obtain this on su:
insmod /system/lib/modules/pronto/pronto_wlan.ko
insmod: init_module '/system/lib/modules/pronto/pronto_wlan.ko' failed (Required key not available)
Click to expand...
Click to collapse
You must have a module version mismatch. This shouldn't happen, as the correct modules are provided in the zip. Which recovery did you use to flash my kernel? Did you use the TWRP linked in the first post, a different TWRP, or a different recovery altogether? When you go into the Settings->About Phone, what does it indicate as the kernel version?
squid2 said:
You must have a module version mismatch. This shouldn't happen, as the correct modules are provided in the zip. Which recovery did you use to flash my kernel? Did you use the TWRP linked in the first post, a different TWRP, or a different recovery altogether? When you go into the Settings->About Phone, what does it indicate as the kernel version?
Click to expand...
Click to collapse
oh sorry i understand my mistake, i fastboot flash only boot.
i will install zip.file containing wifi driver.
we have a kernel fully fonctionnal now ,wifi too, you seem to resolve issue camera when it's rooted
Related
These kernels are provided as-is without warranty. I'm not responsible for any problem you may encounter with your phone or tablet or if your cat suddenly dies.
Although, don't expect support even if I will eventually help because I love cats.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Overview & features :
"With great power comes great responsibility". Don't go crazy with overclocking, only the best devices will be able to get 2.3 GHz stable or even bootable, though heat will be your main issue.
- Based on Google AOSP 3.4.0 and LineageOS's kernel sources for MSM devices
- CPU OC up to 2.3Ghz with OV/UV support / minimum frequency down to 81 MHz (configurable)
- L2/bus speed OC up to 1.49GHz / 4.8GBPS
- GPU OC up to 627 MHz with OV/UV support
- CPU governors : Faux's intellidemand, interactive, ondemand, smartmax, intelliactive, conservative, elementalx
- I/O schedulers: noop, deadline, cfq, fiops, sio, BFQ, zen
- Kernel based intelli-thermal driver by Faux123
- Kernel based msm hotplug driver by Fluxi
- tni.andro's battery life extender support
- Magnetic on/off setting
- USB fast charge support
- USB OTG charge hack support by flar2
- FauxSound support
- LineageOS's PCC color tweaking
- Fsync switch on/off
- Touchscreen patches by Showp1984
- Touchscreen wake/sleep gestures by flar2
- Kali Pwn Pad experimental support
- Optimized algorithms and libraries
- Various performance and power saving tweaks
- NTFS, NFS and exFAT support
- F2FS support up to all-F2FS with automatic ramdisk patching at flash time (reflash if you change partition format !)
- Kexec-hardboot support for Multirom compatibility
- Full package comes with Aroma installer to set core features at flash time (L2 OC level, CPU OC, etc.)
- Pure package will restore Aroma settings backup if present, or else will offer you a balanced preset for day to day usage
- Custom Synapse support with various settings and core features tweaks
- Compiled with Linaro 6.1.3 toolchain with various optimizations
- SELinux Permissive patch (Disabled by default, can be enabled in Aroma)
- Wifi firmware overrider to fix wifi on 4.4.3 & lower or on roms using old wifi firmware (up to r226 - Kitkat only)
CHANGELOGS IN #2 POST
You can tweak multiple options of this kernel with TricksterMod, FauxClock, Kernel Adiutor, Synapse(r500 and up, definitely recommended to get the most available options) or similar apps. (They are all available on the PlayStore)
Note to MultiROM users : don't use the kernel sharing feature. Flash the kernel on each rom instead. Also, it may take more time booting on secondary roms when using F2FS. Don't worry and wait for a bit
Downloads (all kernels are compatible with both flo and deb)
Grab your build from here :
Glitch kernel r574 download - For AOSP 6.0.1/7.x.x and LineageOS 14.1
Mirror + older builds : Mediafire
FAQ :
What are the differences between "Full" and "Pure" builds ?
The "Full" builds are using Aroma Installer so you can tweak various options at flash time. At the end of the process, a file containing your settings will be created (/sdcard/glitch-settings.conf). The "full" builds are also able to restore your settings from Aroma after a rom flash or wipe for example.
On the other hand, "Pure" builds aren't coming with Aroma and will try to restore your settings from your SDcard, or use a default profile if none is found. Both Full and Pure builds are coming with a custom Synapse support to let you tweak all the core options on the fly once booted.
If you flash a "Pure" build without a profile, the default preset will be applied. It's been tweaked for a good balance between performance, power consumption, stability and functionality for day to day usage. The default settings applied are as follow :
- 1.7GHz max CPU freq (from 1.5GHz stock) / 1GHz max CPU freq when the screen is off / "Balanced" L2 OC
- msm_hotplug driver in place of msm_mpdecision
- 450MHz max GPU freq (inline with other Snapdragon 600 devices - from 400MHz stock)
- Safe CPU and GPU undervolting for lower heat and power consumption
- Deadline I/O sched / Interactive CPU governor
- Doubletap to wake and fastcharge enabled (Doubletap to wake will slowly drain power during suspend, so disable it if not used)
- Everything else is kept stock
What do I have to do to use F2FS on one (or more) of my partitions ?
First, BACKUP your data if needed, especially if you're planning to use F2FS on DATA partition, as changing filesystem will wipe the partition. Change partition formats as needed in your recovery. It is NOT recommended to convert system partition as F2FS as it'll be slower than EXT4 to begin with (as the partition is mostly read only) and will alter compatibility with many roms (especially CM/LineageOS based). The last thing to do is to flash any Glitch kernel with a revision number past r150. You can restore your settings from SDcard if any, the install process will detect the partitions and modify the ramdisk accordingly so you can finally boot and use your fresh FS.
What L2/cache OC setting should I use ?
This setting will overclock bus speed and RAM so it's a bit delicate to tweak, yet it can give a nice "free" global performance boost. A simple test to check for stability is to run the camera app 3 or 4 times in a row while waiting for 10 seconds between each launch. If your device freezes, it's unstable ! It's also the only setting you can't change on the fly once booted, either from Synapse or sysfs, and requiring a reflash (using Aroma or changing the value in /sdcard/glitch-settings.conf).
Let me give you some details about the available settings so you can choose wisely :
Stock (1.13GHz-4.26GBps) is the regular, out of the box, non OC setting.
Improved (1.19GHz-4.26GBps) is the same as "ElementalX" setting in Flar2's kernel.
Balanced (1.22GHz-4.66GBps) is the same as "Ultra" setting in Flar2's kernel.
Fast (1.35GHz-4.66GBps) is a nice jump over "Balanced", yet stable for most devices. A kind of sweet spot.
Extreme (1.43GHz-4.80GBps) is were most users will start to get issues. Provides a great boost if stable.
Glitchy (1.49GHz-4.80GBps) pushes your hardware to the limits. Will be unstable for most devices.
Thanks to everyone helping me to debug and find new useful things to integrate !
Without all of you, this kernel wouldn't be !
XDA:DevDB Information
Glitch kernel for Flo, Kernel for the Nexus 7 (2013)
Contributors
Tk-Glitch, Google, animania260, CyanogenMod, TeamDouche, flar2, Faux123, franciscofranco, Showp1984, Team-Hydra, sixstringsg, Poondog, ZeroInfinity, Fluxi, arter97, neobuddy89, alesaiko, 228aye, AndreiLux, amarullz ,followmsi, and all my community
Source Code: https://github.com/Tk-Glitch/Flo_AOSP
Kernel Special Features: CPU OC/UV 2.3 GHz, GPU OC/UV 627MHz, FauxSound, S2W/S2S/DT2W, Bus speed OC
Version Information
Status: Stable
Created 2013-09-19
Last Updated 2017-09-13
logs
Git commits for nerdz & lolcats
Latest release's changelog with words for humans :
14/09/2017 - r574 :
- Synced with latest LineageOS 14.1;
- Updated toolchain to Linaro GCC 7.1.1-2017.08;
- Added touchscreen-calibration fix patch by parrotgeek1;
Previous changes below :
17/07/2017 - r572 :
- Synced with latest LineageOS 14.1;
11/07/2017 - r571 :
- Synced with latest LineageOS 14.1;
29/06/2017 - r570 :
- Synced with latest LineageOS 14.1;
- Updated toolchain to Linaro GCC 7.1.1-2017.05.
03/06/2017 - r566 :
- Synced with latest LineageOS 14.1;
- Changed the behaviour of the permissive/not permissive switch to either force permissive or keep rom default (instead of forcing enforcing before) to prevent issues with some implementations;
- Added a service that restarts GMS (Google Mobile Services) post boot to fix memory leak/battery drain linked to them - Curently working in permissive mode only (like init.d and some advanced Synapse settings);
- Updated toolchain to Linaro GCC 6.3.1-2017.05.
07/05/2017 - r565 :
- Synced with latest LineageOS 14.1;
- Added a simple check for the MPDecision service starting mechanism used by your rom : If it's using the same trigger as LineageOS (init.flo.power.rc), you'll be able to enable/disable the service at will after boot. If it's using a different trigger, the binary will be nuked the old way (renamed to mpdecision_bck) if you're using the in-kernel msm_hotplug driver (effectively preventing you to play with it after boot). It's not a solution that pleases me, but it will fix cases of both hotplug drivers loaded at the same time on non-LOS-based roms, and that's all that counts for now.
14/04/2017 - r564 :
- Synced with latest LineageOS 14.1;
- Corrected HZ reference in touchscreen driver.
30/03/2017 - r563 :
- Fix potential touchscreen inconsistencies on some panel revisions
- Fix gesture switch (S2S/S2W/timeout)
27/03/2017 - r561 :
- Synced with latest LineageOS 14.1;
- Backported high-resolution support for sched-clock;
- Fixed CPU detection on subsystem_restart;
- Make rpm clocks sleeping clocks;
- Pushed updates from franco kernel regarding GPU, CPU freq and video;
- Added Zen I/O scheduler (pretty nice sched to say the least);
- Enabled I/O is busy flag for msm_hotplug driver by default (boosts CPU freq during heavy I/O load -> big smoothness gains in many apps and games);
- Added compiler fixes and optimizations from alesaiko (breakfast kernel);
- Moved to latest Linaro GCC 6.3.1 compiler (as the changes above fixed high power consumption issues on GCC5+);
- Consolidated Synapse support. The path of the generated config file is now /data/synapse instead of ramdisk to keep it safe during rom upgrades and reboots. If you get a "No UCI support" message on first Synapse launch, just kill the app and relaunch it. It'll not happen again after that unless you wipe data or I'm forcing a regen in a future update.
- Fixed init.d injection not using the correct path for busybox since a few releases and updated the execution process to N standards;
- Changed the way we get rid of mpdecision to prevent the service from starting in the init process instead of renaming the binary. This enables the possibility to enable or disable mpdecision on the fly after boot, even if using msm_hotplug as default hotplug driver.
- Fixed missing options in Synapse;
- Added various smaller performance patches and optimizations as well as a few more variables to play with for nerdz and lolcats (see github commits);
- Tweaked debugging config;
12/03/2017 - r544 :
- Sync with latest LineageOS 14.1
- Disabled backlight dimmer by default - Added a note to Aroma installer about potential issues with some panel revisions
23/12/2016 - r543 :
- Sync with latest CM14.1
18/12/2016 - r542 :
- Enable RPFILTER (CM14.1 tethering fix)
05/12/2016 - r541 :
- SElinux switch now works on boot without needing root access. As a result, also removed related post-boot script hooks
- Added prebuilt config file for Synapse for faster launch and fix possible error on first launch (clear Synapse data if you get issues)
04/12/2016 - r540 :
Due to some of the changes in this build, restoring settings from sdcard backup (by flashing Pure Edition or restoring through Aroma) may lead to different settings being applied depending on what you set before. It is strongly suggested to use the Full installation at least once to update your settings or delete glitch-settings.conf on the root of your sdcard before flash to use the default preset.
- Post CM14.1 merge cleanup pass. It was definitely needed ! Including, but not limited to :
- Removed Lazyplug and Intelliplug hotplug drivers (due to conflicts leading to performance issues)
- Removed Dynamic Fsync / Added switch to disable Fsync (after corrupting ~15 installations with DynFsync, I don't feel like it's worth the slight I/O perf boost)
- Replaced Showp1984's DT2W by flar2's S2W/S2S/DT2W (the touchscreen issues I faced with it aren't reproducible anymore)
- Removed LZ4 and use XZ compression instead
- Removed WQ_POWER_EFFICIENT (couldn't see a measurable gain with it enabled)
- Removed ROW ioshed
- Rollback'd to older Intellidemand governor- Reworked settings application and restoration system to work with CM14.1/without SuperSU and load it early during boot by init hooking (CM14.1 PCC livedisplay related race condition "fix" included). Note : MultiROM users, you may want to disable MultiROM menu if you have it enabled to further reduce the chances to trigger the issue (completely fixed it on my side). Feel free to report your findings on the matter.
- Added flar2's ElementalX governor
- Updated default profile (the one you get while flashing Pure package or using restoration option in Aroma without sdcard backup)
- Updated thermal profiles
- Updated available options in Aroma
- Updated busybox to 1.25.1 YDS and moved from /sbin to the more convenient and standard /system/xbin
- Updated Selinux switches to work with more roms (now working on CM14.1)
- Moved Synapse files from /data/synapse to /res/synapse in ramdisk
- Updated Synapse presets
- Updated Synapse settings (Aroma installer will give more gestures-related options though, at least for now)
29/11/2016 - r534 :
This kernel will only work with AOSP 7.x and latest CyanogenMod 14.1 based roms. If you get incorrect colors and slow UI, rollback to r533 CM.
- Rebased using CM14.1 tree
- Updated color controls to mimic CM's PCC implementation (Thanks @flar2)
07/11/2016 - r533 :
- Added SDCardFS support
- Fix for CVE-2016-3903
- Fix for CVE-2016-3934
- Fix for CVE-2016-7117
- Added LazyPlug switch and settings to Synapse (hotplug tab)
- Added DT2W switch to Synapse (misc tab)
- Fix GPU voltage range formatting in Synapse
- Fixes regarding power efficiency
- Contextual fixes and speedups
- Now building CM variant of the Nougat kernel too. AICP is the first N rom on this device to require a CM compatible kernel.
14/09/2016 - r530 :
- Modified rom injection/flash time mods logic to be more robust and universal. Fixes inconsistent boot or even bootlooping on hybrid F2FS roms like CyanogenMod or PureNexus THIS CHANGE MAY FORCE YOU TO REFLASH YOUR ROM TO BE ABLE TO BOOT (even on a non-hybrid rom - no wipe required)
- Fixed settings not applying after setting them through Aroma/glitch-settings.conf
- Security patch to avoid invalid access to ashmem area
- Security patch for vulnerability CVE-2016-2059
- Removed deprecated binary injection code
- Default thermal presets calibrated for better efficiency and performance (they were too aggressive in r520)
- Little naming change for the builds. Full is still "Full", but "Restore" is now "Pure". Pure edition is now fully standalone and doesn't require a previously generated profile from Full edition (but will gladly restore it as before if found during install). It can be fully tweaked through config file and/or Synapse like Full edition.
- Nougat build "Full edition" now has a Nougat themed splash screen for Aroma
- Synapse presets are now working. Make sure to press apply when Synapse comes back if you want to keep it ! (Make sure to clear Synapse data after first boot to force a regeneration !)
- Small things you won't notice
24/08/2016 - r520 :
- Rebase from latest AOSP sources
- Synapse support with many more features and personnalization available than ever before ! Aroma settings are a joke compared to what you'll have in Synapse. Don't flash UKM on top by the way, and make sure to clear Synapse data if you've flashed one of the previews. Even more to come soon.
- Updated Neobuddy89's msm_limiter driver to latest from Nexus 6
- Updated Neobuddy89's state_notifier driver to latest from Nexus 6
- Moved to Faux123's Intelli-thermal driver
- Added some memutils optimizations and more for performance
- Updated Xbox One gamepad driver
- Removed loads of dead code and buggy merges
- Switched to Linaro 4.9.4 toolchain - After weeks of testing, my tab runs cooler, stabler, and longer than with 5.x for an invisible performance difference. Worth it !
10/08/2016 - Preview r516 is available here. More options available in Synapse which is now also enabled with the "full" build, merged android-6.0.1_r0.105, and various other tweaks for speed and power savings. Full changelog here.
04/08/2016 - A preview (r513) is available here. Synapse part still needs some work. Notably, some hotplug drivers options are missing and you can't apply presets. The kernel itself should be stable enough for day to day usage.
12/07/2016 - r499 :
- Fix for glitch settings not applying if the rom doesn't use the init.trace.rc file (Dirty Unicorns is one of them)
- Sync fstab with latest cm13 (may fix usb otg on cm13 based roms in some specific configurations)
11/07/2016 - r478 r498 :
- Synced source up to android-6.0.1_r0.98 changes (latest)
- Getting ready for rebase and Synapse-compatible release
- Removed deprecated libs from r478 installer (fixes setperm errors on some custom/recent roms)
- Fixed CM compatibility
10/12/2015 - r412 :
- Merged with android-6.0.1_r0.1 changes
- PowerHAL patch to fully disable touchboost calls when Qualcomm MPdecision isn't used. This gets rid of the touchboost log spam and (small) overhead.
- Updated F2FS
- Installer scripts fixes and cleanups
- Added back CM build - untested
02/12/2015 - r410 :
- Updated base to linux 3.4.110
- Merged with android-6.0.0_r0.1 changes
- Added Neobuddy89's MSM Limiter driver, enabling max/min/suspend frequencies tweaking on the fly. No more need to reflash for that (/sys/kernel/msm_limiter/ for who's interested). Also added his state notifier driver for further tweaking.
- Removed MSM Sleeper as it's covered by MSM Limiter already
- Changed how settings are applied (moved from init.d script to service) to prevent permission denied issues (Thx Flar2). Due to changes to the way your settings are handled, it's recommended to make a full installation. Settings aren't retrocompatible with previous Glitch kernels !
- Performance and stability improvements by removing coresight from Adreno drivers and better CPU management/scaling through MSM Limiter
- Aroma slight changes to reflect internal changes (note : CPU uV is now applied for both 384MHz step and lower ones)
15/09/2015 - r361 :
- Fixed no mobile network issue on DEB
- Disabled unnecessary debugging
13/09/2015 - r360 :
- Merged with android-5.1.1_r0.17 changes
- Added Lazyplug hotplug driver by Arter97 (you may need to make a full installation if you want to switch to this driver)
- Updated F2FS
- Updated BFQ to v7r8
- Added experimental Nvidia relaxed power savings
- More fixes and various optimizations regarding performance and efficiency
09/09/2015 - r353 :
Note : CM related issues some are encountering aren't adressed with this update. CM team is breaking more and more stuff while using AOSP bases for the kernel and I won't make a CAF based version again. The updated toolchain and added fixes in this release may or may not help, but I won't provide support for CM related issues anymore. Sorry for the inconvenience.
- Fixed SELinux switches (You'll need to use the restore function in full package or just the restore package to switch between permissive and enforcing modes. Enabling it in glitch-settings.conf isn't enough for it to work.)
- Disabled Android Logger by default for less overhead
- Updated toolchain to Linaro GCC 5.2.0 with LTO support
- Tiny fixes
02/07/2015 - r350 :
- Merged with android-5.1.1_r0.13 changes
- Fixed missing governors from previous release
- Added native support for Xbox One controller from Linux 3.17
- Fixed a potential instability case in idle state
- Updated base to linux 3.4.108
- Under the hood fixes
- CM and AOSP kernels are now sharing the exact same base for better stability and maintenance
08/05/2015 - Hotfix - r344 :
- Rolled back various GPU driver patches to fix some Chrome scrolling lockups and possible RR linked to the underlying bug linked to them
- Send enforcing=0 to kernel command line if you're using the permissive ramdisk mode (may fix boot on some non-standard roms - AICP still not booting for me though.. If you know why I'm all ears)
- Modify fstab.flo file in ramdisk even when using CM kernel (enables some non-standard CAF based roms with no "multi-mount fstab" support to boot - it mustn't exist, but better safe than sorry)
08/05/2015 - r343 :
- Merged with android-5.1.1_r0.10 changes
- Removed UKSM
- Disabled KSM
- Removed transparent compression support
- Replaced Flar2's S2W/DT2W by showp1984's DT2W
- Various F2FS changes from arter97 and Jaegeuk Kim
- Various backported drivers from arter97
- Updated Intelli-Plug
- Cleaned up base and bumped back to latest 3.4.y (3.4.107 atm)
- Enabled back kernel mode NEON
- Removed PIE bypass patch from Aroma
- Added Motorola's Qualcomm optimized memutils
- Added BFQ v7r7 ioshed
- Updated Intelliactive governor
- Fstab patching changes to fix boot on some non-standard roms
- Updated Random
- Updated toolchain to Linaro GCC 5.1.0 with LTO support
- Added LTO optimizations
19/04/2015 - r330 :
After breaking my partitions while attempting to improve F2FS mounting time, I was forced to format everything. After my backup restoration and system reinstallation, r327 F2FS implementation is now booting faster than EXT4 on my tab (with mounting times of ~5sec versus 30+ before). So I've then decided to revert the planned F2FS changes for r330 (which made it 1sec faster before formatting, but much slower after) as it didn't make sense. If F2FS mounting time is bothering you, fully formatting your partitions and restoring your data will give you a nice performance reward in return.
- Added flush_merge to F2FS mount options for faster flushing
- Added "transparent compression" support (CM sync)
- Added back optimized ARM RWSEM algorithm
- Enabled back unaligned memory access
- Switched to SIO ioshed (from ROW) at boot time as well as others small tweaks for possible further boot time improvements and smaller file size
16/04/2015 - r327 :
- Merged with android-5.1.0_r0.10 changes
- Updated F2FS implementation using Motorola's sources
- Cleaned up permissive ramdisk patches (fixed related SODs with it enabled)
- Introducing "restore" builds. You can now update your Glitch setup without Aroma using these builds. Your settings will be restored from the SDcard backup made by a previous Glitch installation, so if you don't have a "glitch-settings.conf" file in the root of your SDcard, please use a full build first to generate it ! The "full" builds are using Aroma as before.
- Updated toolchain to Cortex A15 optimized Linaro GCC 4.9.3-2015.03
07/03/2015 - r320 :
THIS UPDATE WILL NEED YOU TO REINSTALL YOUR ROM AND TO MAKE A FULL INSTALLATION OF THE KERNEL IF YOU'RE COMING FROM A PREVIOUS GLITCH RELEASE
- Updated F2FS implementation and bumped to latest
- Various scheduler optimizations - Better hardware use means potentially lower max OC !
- Improved boot times (At least with EXT4. F2FS mounting time feels a bit longer with the updated F2FS implementation)
- Reverted Slimbus OC as some users got issues with it
- Removed some ramdisk mods interfering with permissions
- F2FS/EXT4 detection script rewrite to preserve rom's fstab structure
- Added another permissive switch to disable SELinux enforcing (it will be enabled if you tick the permissive patch in aroma)
- Removed wifi patch from Aroma as it's now useless with lollipop
- Added some security patches from CM source
- CM kernel rebased on Glitch AOSP (again) - Looks good after a few days of intensive use
- A few little glitchy tweaks
- Updated toolchain to Cortex A15 optimized Linaro GCC 4.9.3-2015.02
16/01/2015 - r307 :
- Disable wake gestures by default
- Fix for a little color tweaking bug
- Updated CAF variant for CM12 support & sync with Glitch AOSP r307
Note : r307-CM is NOT compatible with CM11. It must be used with CM12 only.
12/12/2014 - r306 :
- Added vmalloc setting to command line to fix some video playback issues. Thanks to @szale9001 for pointing this out !
16/11/2014 - r303 :
- Added Chainfire's partial root ramdisk patch by default
- Added cernekee's PIE patch to Aroma (allows third party native executables to run, lowering security. Fixes various apps)
- Added SELinux permissive + sepolicy ramdisk patch to Aroma (enables full root access but lowers security. Fixes various apps)
15/11/2014 - r300 :
- Updated AOSP kernel with lollipop-release - BREAKS COMPATIBILITY WITH 4.4.x due to GPU driver changes !
- Removed interactive GPU governor
- Merged GPU patches from codeaurora & franciscofranco for better responsiveness and battery life
- Cleanups
26/09/2014 - r226-disabledAVS :
- r226 variant with disabled AVS for users with recurrent instability issues. Higher power consumption than standard build when used without uV.
Follow up to this post : http://forum.xda-developers.com/showpost.php?p=55566837&postcount=1943
22/09/2014 - r226 :
- Added experimental support for Kali Pwn Pad (as it was requested by some - Thanks for the list Flar2 )
- Disabled compaction (a little higher RAM consumption for higher performances - Doesn't seem to affect multi-tasking in a negative way)
- Disabled MSM hardware adaptive voltage scaling (should fix the last remnants of SoDs/RR happening for some even on other kernels - May lead to higher power consumption) I will make a test build with it disabled for who wants to try in the next days
- Updated Faux Sound to 3.6
- Enabled more TCP congestion-avoidance algorithms
- Enabled NFS support
- Moved exfat to built-in instead of module
- Added black magic
17/09/2014 - r223 :
- Better hotplug driver settings in 99glitchsetup script / Fix Qualcomm MPDEC activation
- Lowered "Glitchy" L2/bus settings to make it usable by more users
- Enabled various compiler optimizations (like some GCC graphite optimizations)
- Updated toolchain to Cortex-A15 optimized Linaro 4.9.2 2014.09
- Echo touch firmware version to logfile (/data/local/tmp/glitch-kernel.log)
10/09/2014 - r220 :
AOSP kernel only (CAF kernel will follow as soon as possible) :
- Rebase using latest Google source (fixing various bugs like SoD, random shutdown, slowdowns etc.) and staying on 3.4.0 base for now to prevent issues til I'm able to fix them all with latest Linux upstream
- Aroma Installer rework for less pages on fresh installation mode, similar to Flar2's presentation
- Added new options to Aroma installer
- Updated Flar2's S2W/DT2W system, enabling gesture support
- Replaced Showp1984's MPDecision by Fluxi's MSM Hotplug driver - new default
- Updated Faux123's Intelliplug hotplug driver as well as intellidemand & Intelliactive governors
- Updated/fixed Smartmax and Smartmax EPS (extreme power saving) governors
- Updated FauxSound
- Updated Flar2's msm_sleeper
- Added a backlight dimmer function
- Cleaned up/removed a vast amount of old patches
- Added release number to internal kernel naming so you know what version you're on
- Added a wlan firmware override setting in Aroma. This is basically the same as using 4.4.4 PRIMAtor to enable 4.4.3 or lower support or to fix wifi on a few roms that are using older wifi blobs
- Slight tweaking here and there
- Removed kernel-based NEON support - Needs more testing
- Switched to LZ4 kernel compression - Higher kernel size but faster boot times
- Updated toolchain to Cortex-A15 optimized Linaro 4.9.2 2014.08
05/07/2014 - r151 :
AOSP kernel only :
- Base update from Linux 3.4.86 to 3.4.96
- Removed some unnecessary Aroma pages for faster navigation
- Removed Qualcomm-Optimized Dalvik/Bionic from Aroma to prevent users from softbricks when used on incompatible ROM
- Added F2FS support
- Added F2FS partition detection script to modify ramdisk accordingly at flash time. You will need to launch Aroma installer each time you change FS on supported partitions (DATA, CACHE & SYSTEM) to refresh the ramdisk configuration (you can restore your glitch settings to do that btw, no need to clean install). You can use all of them as F2FS, or just one, you decide.
- Enabled Intelliactive governor
- Added CTCaer's patch to restore forced TS firmware update sysfs
05/06/2014 - r147 :
AOSP kernel only :
- Merged with 4.4.3
- Base update from Linux 3.4.82 to 3.4.86
- Switch to Cortex-A15 optimized Linaro 4.9.1 toolchain
25/02/2014 - r142 :
- Base update from Linux 3.4.79 to 3.4.82
- Added 81 MHz CPU frequency
- Updated ondemand governor
- Switch to Cortex-A15 optimized Linaro 4.8.3 toolchain
- Disable input-boost by default in Aroma
07/02/2014 - r140 :
- Update to Linux 3.4.79
- Switch to XZ compression
- Add kernel mode NEON support as well as NEON accelerated AES & XOR implementations
- Fix CPU load miscalculation
- jbd2 and ext4 optimizations
- Add max screen off frequency support - Thanks to Flar2 (if disabled in Aroma, changing frequency in apps won't have any effect)
- Add UKSM 0.1.2.2 support
- Add dynamic management of dirty page writebacks
- Enable Wiimote HID support
- Enable USB printer support
- Bugfixes
Aroma installer overhaul :
- Reworked installation process to be clearer and more customizable
- Added an automatic backup of your settings to the root of your internal SDcard
- Added a restoration mode to get your settings from internal SDcard backup back on any rom (cross-compatible with Glitch kernel variants)
- Renamed /system/etc/settings.conf to glitch-settings.conf to make it more obviously glitchy
- Removed the need to set CPU OC, L2/cache OC and auto-uV again when keeping previous settings (now reading it from your settings at flash time. Note : editing this part in /system/etc/glitch-settings.conf requires a reflash using the "already glitched" option)
- Added Qualcomm optimized Dalvik/Bionic libraries into the installer (bionic only on CM variant) so you can install/restore them with the kernel
- Added I/O scheduler, CPU governor, read-ahead buffer size, fast charge, max screen off frequency and maximum multi-core power savings to available settings
- Fixed how the min CPU clock is applied to make it more robust and work better with governors
- Fixed how the min CPU freq uV is applied to make it work independently of the min freq (by subtracting the uV amount to the original voltage instead of forcing plain values) - Also, make it capable of setting uV for all freqs for future use.
- Changed the auto-uV menu to reflect the internal changes
- Fixed some permissions issues
- Added hotplug driver check so it's possible to restore it as well from settings without interference
- Change theme
25/01/2014 - r132 :
Performance and stability improvements :
- Enhanced memory management
- Lower CPU overhead
- Improved I/O speed in many cases
- Improved ondemand governor behavior
- Fix a memory leak
- Fix some msm_bus bugs
- Fix a false error report in Aroma log
CM kernel only :
- Fixed the "black caterpillar" bug
- Improved GPU performance consistency
23/01/2014 - r130 :
- Faux123's LCD color control driver updated to Flo version (thanks to him to make it opensource), adding gamma control. (You'll need FauxClock to tweak it - color is still available from TricksterMod)
- Some GPU driver related bugfixes
- Implemented LoUIS API for cache maintenance operations
- Update base to Linux 3.4.77
- Revert some CAF updates (fixes some L2 corruption that could lead to random reboots / black screens)
- Battery life improvements
- Some cleaning
CM kernel only :
- Fixed color control
- Fixed random heavy GPU performance drop
- Changed memory allocation to be in line with CM
- Changed naming in Aroma to differentiate from "pure" AOSP
Older changelogs are available here
Looks like a nice kernel that will really show what this device can do
Sent from my Nexus 4 using Tapatalk 4
Thanks.
That's what I'm trying to make. And I *think* (may be wrong though) I'm the only one yet using a fully working GPU OC implementation on flo kernel. It's an adaptation of Galaxy S IV's (i9505) GPU OC code from Team Hydra.
It seems 627 MHz is around the max possible with stock voltage, probably even 600 MHz for many. I'll see what it can do with a bit more juice.
Other things to do : add more frequency steps for the CPU, lock the default freq, and make the L2/bus speed configurable.
After that I think we'll be able to push the thing to the limits if we want to.
Thanks for your hard work I'm going to try it on pacman ROM I'll let you know how it goes
Sent from my Nexus 7 using XDA Premium 4 mobile app
Thank you, I'm curious to know what results you'll get
Awesome so far .WOW
Sent from my Nexus 7 using XDA Premium 4 mobile app
---------- Post added at 12:20 AM ---------- Previous post was at 12:18 AM ----------
I wanna show u my settings, I use trickster, so sound and faux kernel app to get the results I need was going to show you pictures but all the sudden XDA premium has no picture button I'm a little lost their. Touch responses phenomenal and just like faux kernel the sound is this did really well I can finally listened stock sound sucks on this product even know what has supposedly way better speakers, thanks to people like you I can actually hear the videos I watch without headphones now. Thank you very much I've been using it for about 5 minutes swimming around on everything and everything smooth as hell
Sent from my Nexus 7 using XDA Premium 4 mobile app
---------- Post added at 12:21 AM ---------- Previous post was at 12:20 AM ----------
Add me on gtalk. [email protected]
Sent from my Nexus 7 using XDA Premium 4 mobile app
---------- Post added at 12:24 AM ---------- Previous post was at 12:21 AM ----------
I'm kinda pissed,paid XDA apk all of a sudden has no way to show pictures. Argggg
Sent from my Nexus 7 using XDA Premium 4 mobile app
The problem exists on the free app as well ^^
Try scrolling up and down away from the images and back on them, it'll eventually show up at some point.
Thanks for your work. I'll give this kernel a try.
Coming from N4 motley kernel I'll love to use init.d scripts to set up color "calibration", sleep states, etc. What do you think about implementing / documenting such features for your kernel?
Otherwise, let me see if I need something. Hm, what about USB OTG and ntfs/f2fs support?
USB OTG is working out of the box. NTFS/F2FS support isn't. I'll look into adding them =)
Your idea is nice, I'll think about it.
Thanks =)
Do you plan on adding Faux's color mod? I will give this kernel a shot and report back.
cyberprodigy said:
Do you plan on adding Faux's color mod? I will give this kernel a shot and report back.
Click to expand...
Click to collapse
When there will be some source, yeah why not =)
Tk-Glitch said:
When there will be some source, yeah why not =)
Click to expand...
Click to collapse
I am running the kernel right now. All I can say is "wow".
You did a fantastic job cherry-picking the best features from various kernels. I notice a slight increase in smoothness compared to Faux's kernel plus D2W and all the other great features you added so I think this may be my new main kernel.
I will use it over the next few days and report any issues I find and how the stability is. Thanks a lot for your work.
Edit: Also, I am running CleanROM and everything seems fine.
Thank you, so it may work with any rom then ! Good to know CM didn't break too much stuff leaving AOSP base.
sleep to wake, doubletap to wake disabled by default? don´t need it xD
need a fast stable kernel and especially want to disable fsynch. if u run a stable rom it justs takes useless power xD
i´m pretty new to the nexus7 like the most of us . is that kernel stable?
atm i´m using faux´s, also used franco. i dunno, but on franco´s i couldnt change gpu govenor and the 3dmark benchmark was about 3000points, stock is about 6000-7000. pretty strange.
i am a pretty minimalistic user, want best batterylife/performance ratio. only using psx, best rom for me
i think i´ll try that kernel
edit: what does "Snake Charmer" do?
edit2: read s2w stuff enabled by default, can it be disabled via trickster?
My N7 is running great with your kernel. Let's see what about perfomance and stability in two or three days. After checking and playing with trickster I miss a kind of dynamic fsync and a color calibration interface - compared to N4 m+ (motley) kernel.
Perhaps you can implement some upstream changes / patches directly from CAF or newer kernels.
It would be nice if you post some information about L2 speed hack, etc. So that everyone can see what this hacks do.
Which file are we supposed to use, they are all dated 20130919. I'm guessing the. 904.
airmaxx23 said:
Which file are we supposed to use, they are all dated 20130919. I'm guessing the. 904.
Click to expand...
Click to collapse
CM10.2-flo-Glitch-20130919.0904
2013 /09 /19/09:04
Year/Month/Day/time
dunno if latest point is time in this case when you compare it to upload date. but yes it seems to be latest. upload time and build date can be different, so i think it´s the time.
L-ViZ said:
CM10.2-flo-Glitch-20130919.0904
2013 /09 /19/09:04
Year/Month/Day/time
dunno if latest point is time in this case when you compare it to upload date. but yes it seems to be latest. upload time and build date can be different, so i think it´s the time.
Click to expand...
Click to collapse
Probably when it was compiled.
cyberprodigy said:
Probably when it was compiled.
Click to expand...
Click to collapse
Just a heads up for those who want to disable swipe2wake or doubletap2wake, you can turn them off with the Trickster app but I did not find a setting in the FauxClock app.
This is a port of my "Squid Kernel" to the Moto X Play. It is based off the Motorola stock kernel and includes updates from CodeAurora and Kernel.org, along with my original work and cherry picks from other sources.
Disclaimer:
This kernel is for the Moto X Play (lux) only! Don't flash it on surnia, osprey, otus, or any other device. This kernel is provided AS-IS, with no warranties. I am not responsible for bricking your device. Flash at your own risk. Versions r22 and up are only intended for Nougat ROMS!
Features:
LED notification support
Moderately undervolted
Slightly overclocked
Updated to Linux 3.10.108
Synced with latest CodeAurora changes
Improved memory management
Improved VMA caching backported from Linux 3.15
Optimized ARM crypto routines
Updated f2fs and WiFi drivers
FIOPS and BFQ I/O schedulers
Lionfish CPU governor
ClusterPlug big.LITTLE hotplug (designed for MSM8939)
KCAL MDP5 colour control (by savoca)
Improved zRAM backported from Linux 4.9
Vibration intensity control
Compiled with Linaro GCC 7.3 and optimized for Cortex A53
Stripped down and optimized configuration
Release History:
Code:
r23: August 15, 2018
- Restored aggressive BCL for deteriorated lux batteries
- Tonnes of security patches
- Updated binder
- Compiled with Linaro GCC 7.3.1
r22c: January 14, 2018
- Fix lux speakerphone on modern ROMs
r22b: January 13, 2018
- Audio driver fixes
r22: January 11, 2018
- Security patches
- Updated camera drivers
r21: December 6, 2017
- Updated to Linux 3.10.108
- Security patches
- Oreo support related patches
r20: August 2, 2017
- Updated to Linux 3.10.107
- Tonnes of security patches from many places
- Updated sdcardfs from Google
- Updated WiFi driver from CAF
- Compiled with Linaro GCC 6.3.1
r19: January 1, 2017
- Added support for Nougat ROMs
- Updated zRAM from Linux 4.9
- Updated (optimized) FUSE from CAF
- Kernel ASLR and many info leak fixes
- ARM PXN support for exploit mitigation
- Tons of security updates
- Some CAF updated from LA.BR.1.2.9_rb1.10
- Fixed kernel panic on VPN disconnection
- Updated compiler to Linaro GCC 6.2.1
r18: November 8, 2016
- Tons of security updates
- Updated to Linux 3.10.104
- Updates from Motorola Harpia kernel
- GPU driver latency reduction
r17: August 16, 2016
- Security updates
- Updated to Linux 3.10.102
- CyanogenMod compatibility updates
r16g: May 16, 2016
- Security updates
r16f: April 14, 2016
- Reverted f2fs update
r16e: April 10, 2016
- Lower BCL threshold voltage
- Updated zRAM from Linux 4.4
r16d: April 8, 2016
- Vibration intensity control
- Updated f2fs from Linux 4.6
- Patches for CM13 compatibility
- ClusterPlug bug fix
- Built with Linaro GCC 5.3
r16b: April 6, 2016
- ClusterPlug 2
- Security fixes
- Changes for CM13 compatibility
r16: March 20, 2016
- Updated to Linux 3.10.101
- Updated to Motorola MPD24.107
- Updated WiFi driver from CAF
- IO optimizations under heavy load
- Miscellaneous bug and security fixes
r15b: Feburary 27, 2016
- Updated to Linux 3.10.98
- ARMv8 crypto related fixes
- Use ARMv8 crypto for adopted storage
r15: February 6, 2016
- Updated to Linux 3.10.96
- Updated f2fs from Linux 4.5
- Kernel library optimizations
- Improved CFQ IO scheduler
- Improved kernel PRNG
- ARMv8 accelerated crypto support
- Better use of ARM instruction set
- Added minimum CPUs parameter for IntelliPlug
- Miscellaneous bug fixes
r14b: January 23, 2016
- Fixed speakerphone mic
- Fixed low/poor call audio
- Security fix for CVE-2016-0728
r14: January 16, 2015
- Partial update to CAF LA.BR.1.2.7_rb1.1
- More than a dozen CAF security fixes
- Slightly smoother performance
r13b: January 14, 2016
- Security and bug fixes from Linux 3.12.52
r13: January 14, 2016
- Updated to Motorola Marshmallow sources
- Should work on Marshmallow Stock ROM
- Miscellaneous fixes
- Animations seem smoother on CM13 now
- Compiled with Linaro GCC 5.2
r12: December 20, 2015
- CM13 ONLY!!!
- Updated zRAM
- Optimized memory caching, allocation, and management
- Optimized scheduler
- Optimized performance event tracking
- Updated camera driver for new CM13 build
r11f: December 17, 2015
- Updated to Linux 3.10.94
- Updated to LA.BR.1.1.3_rb1.41
- WiFi is a kernel module
- FOR CM13 ONLY!!!
r11e: December 1, 2015
- Fixed some cpufreq races
- ClusterPlug disabled by default on stock ROM
- Minor bug fixes
r11d: November 15, 2015
- Improved Lionfish load calculation
r11c: November 14, 2015
- Disabled the kernel interface for Qualcomm perfd
r11b: November 14, 2015
- Made ClusterPlug more tolerant of PowerHAL/perfd
r11: November 14, 2015
- Added my new ClusterPlug CPU hotplug
- Enabled my Lionfish CPU governor
r10g: November 11, 2015
- Patched Pronto CR-930533 vulnerability
- Fixed possible use-after-free in zRAM
- Updated to Linux 3.10.93
r10f: November 9, 2015
- Updated to Moto Maxx 2 Kernel
r10e: October 31, 2015:
- Security and stability improvements
- Updated to Linux 3.10.92
- Updated to CAF LA.BR.1.1.3_rb1.36
- MDSS brought closer to CAF
- Compiled with Linaro GCC 5.1 snapshot
r10d: October 26, 2015
- Fixed r10c SELinux regression on stock ROM
r10c: October 24, 2015
- Fixed encryption support
- Patches for Android 6.0 compatibility
r10b: October 4, 2015
- Fixed move app to SD card issue
- Cleaned up DTBs to reduce size
r10: October 3, 2015
- Added KCAL colour control (by savoca)
- Added optimized crypto routines for ARM
- Updated to Linux 3.10.90
- Optimized memory performance
- General cleanup and optimization
r9e: October 1, 2015
- Fixed reboot to recovery
r9d: October 1, 2015
- Fixed screen glitches
r9c: September 30, 2015
- Updated to proper kernel sources
- Updated to Linux 3.10.89
- Updated to LA.BR.1.1.3_rb1.32
- Small tweaks and optimizations
r8b: September 18, 2015
- Fixed Moto Voice
- Updated to Linux 3.10.88
r8: September 13, 2015
- Initial release for lux
Downloads:
Main downloads tab
Flashing Instructions:
Flash the zip with TWRP. I recommend making a nandroid backup before flashing. This kernel will work on both the stock ROM and custom ROMs that have WiFi configured as a kernel module.
XDA:DevDB Information
Squid Kernel for Moto X Play, Kernel for the Moto X Play
Contributors
squid2
Source Code: https://github.com/sultanqasim/android_kernel_motorola_msm8916
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: r23
Stable Release Date: 2018-08-15
Created 2015-09-13
Last Updated 2018-08-15
Initial Build Up
The first ever custom kernel for the Moto X Play is now available!
The kernel includes everything mentioned above. It includes notification LED support, and the notification LED will start working on the stock ROM after flashing this kernel. It does not include IntelliPlug or Lionfish, as they are incompatible with big.LITTLE systems in their present state.
I have tested the core functionality and everything appears to work. However, since this is a very early release, I would not be surprised if bugs exist. Please report any bugs or crashes you encounter.
Since everything appears to work in this kernel, we are all set for a CyanogenMod port. Tomorrow, I plan to start porting CM12.1 to this device. If you're lucky, you might be seeing a fully working CM build by tomorrow night.
Mate you freakin legend. That's some quick development support for our battery beast. I'm working too long hours to test this just now if I get chance on a break I'll get twrp installed etc my device is only rooted so far.
Noticed you brought cm12 to osprey as well. Do you have a donations link as I'd like to donate a little when I get paid just as a thank you.
Sent from my XT1562 using Tapatalk
So far haven't noticed any performance improvements (still fresh) but I am LOVING this notification light!!! I can finally at a quick glance tell if it's worth reaching for my phone. And at night, I know where it is. You're awesome! Definitely need a donate link ..
Firstly thanks for working on the X Play. Installed fine but Moto Voice now not working? Cannot switch on in Moto app, was fine prior to flashing this kernel?
Sent from my XT1562 using XDA Premium HD app
CharlesW123 said:
Firstly thanks for working on the X Play. Installed fine but Moto Voice now not working? Cannot switch on in Moto app, was fine prior to flashing this kernel?
Sent from my XT1562 using XDA Premium HD app
Click to expand...
Click to collapse
I just checked and can confirm that the kernel breaks audio input for Moto Voice. The microphone works fine everywhere else though. There is probably a small change Motorola made to the audio path for always listening audio between the osprey and lux kernels, or it might have been broken by a CodeAurora change. I'll do some more investigating when I get time.
Deep sleep issues, the device stay awake 2h now after flashing the kernel.
XMoDuLeSx said:
Deep sleep issues, the device stay awake 2h now after flashing the kernel.
Click to expand...
Click to collapse
Seeing that myself as well. Guessing something related to the Moto Voice glitch (mine Force Closes from time to time).
squid2 said:
...but vache's TWRP will probably work as well.
Click to expand...
Click to collapse
Nope, didn't work. I try it 3 times. TWRP says "successfully" after the zip flash but Android reboot with the original Kernel.
With your TWRP it is no problem.
The deep sleep issues: i have no, BUT i have disabled many Motorola apps with Titanium (Moto Voice too)
the kernel is going well
the system runs a little better and the CPU is clocked down faster which saves battery.
However, the read / write rates from the internal memory card have become worse. Have tested it with Androbench.
about 1000 iops fewer
I/O Scheduler: Fiops with 1024kb Read-Ahead
but that's not so bad
Thank you for your effort
if I may donate you a coffee / beer, tell me
Thank you, finally some led notifikation action
Skickat från min XT1562 via Tapatalk
squid2 said:
I just checked and can confirm that the kernel breaks audio input for Moto Voice. The microphone works fine everywhere else though. There is probably a small change Motorola made to the audio path for always listening audio between the osprey and lux kernels, or it might have been broken by a CodeAurora change. I'll do some more investigating when I get time.
Click to expand...
Click to collapse
Thanks, also to note have flashed back a stock boot.img file via fastboot and can't get on WiFi? The WiFi toggle goes straight back to off? So can either go back to stock and have working Moto Voice but no WiFi, or use your Kernel and have no Moto Voice I used the boot.img here: http://forum.xda-developers.com/moto-x-play/general/recovery-boot-img-t3191436 My phone is the same version as listed, XT1562 EU any ideas please?
CharlesW123 said:
Thanks, also to note have flashed back a stock boot.img file via fastboot and can't get on WiFi? The WiFi toggle goes straight back to off? So can either go back to stock and have working Moto Voice but no WiFi, or use your Kernel and have no Moto Voice I used the boot.img here: http://forum.xda-developers.com/moto-x-play/general/recovery-boot-img-t3191436 My phone is the same version as listed, XT1562 EU any ideas please?
Click to expand...
Click to collapse
That's because the WiFi kernel module must match the kernel. Had you taken a system backup prior to flashing my kernel? If so, restore it. Otherwise, reflash system and boot, and then re-root your device if you want.
XMoDuLeSx said:
Deep sleep issues, the device stay awake 2h now after flashing the kernel.
Click to expand...
Click to collapse
Devhux said:
Seeing that myself as well. Guessing something related to the Moto Voice glitch (mine Force Closes from time to time).
Click to expand...
Click to collapse
Did the two of you have Moto Voice set up before flashing the kernel? I'm not having any wakelock issues myself, but I had never set up Moto Voice. I'll try to reproduce the wakelock issue when I get time.
squid2 said:
Did the two of you have Moto Voice set up before flashing the kernel? I'm not having any wakelock issues myself, but I had never set up Moto Voice. I'll try to reproduce the wakelock issue when I get time.
Click to expand...
Click to collapse
I did. Maybe I'll load wakelock detector to confirm if Moto Voice is the culprit.
Will wait until Moto Voice bug is eliminated to install it.
Moto Voice Status
After some testing, I can confirm that nothing I did broke Moto Voice. I took the osprey stock kernel and added in a minimal set of patches to get it working on lux. Unfortunately, the Moto Voice issue was still present there. It doesn't make much sense to waste many hours trying to figure out what change is needed to fix Moto Voice when Motorola has already fixed the issue and will be releasing kernel sources soon. Thus, you'll probably have to wait for Motorola to release kernel sources for me to fix Moto Voice.
How long can we expect Motorola to make us wait for it. How timely have they been in the past. This is my first Motorola since the Moto Defy!
Sent from my XT1562 using Tapatalk
squid2 said:
That's because the WiFi kernel module must match the kernel. Had you taken a system backup prior to flashing my kernel? If so, restore it. Otherwise, reflash system and boot, and then re-root your device if you want.
Click to expand...
Click to collapse
Yes figured that and restored my boot and system from TWRP thanks, thought it best to mention in case anyone else wanted to revert back to stock Thanks for the quick feedback, will give your kernel a go again once it's all working.
Sent from my XT1562 using XDA Premium HD app
ephumuris said:
How long can we expect Motorola to make us wait for it. How timely have they been in the past. This is my first Motorola since the Moto Defy!
Sent from my XT1562 using Tapatalk
Click to expand...
Click to collapse
Hey man, remember to not ask for ETA on XDA. As a Moto Play user, I know exactly your feelings about this first kernel [emoji106]
PS: Motorola hasn't take long about releasing it's sources.
Cheers
Moto X Play nice
leonardoroza said:
Hey man, remember to not ask for ETA on XDA. As a Moto Play user, I know exactly your feelings about this first kernel [emoji106]
PS: Motorola hasn't take long about releasing it's sources.
Cheers
Moto X Play nice
Click to expand...
Click to collapse
This one's different lol. Not asking a dev, but rather how long the OEM takes to release on average.
I play nice!! Sometimes ... Lol
Mod Edit: Thread Closed per OP request
Welcome to the N0G33K edition Kernel
This kernel is built on the idea of having optimized battery life and performance. A well made balance between these two is what you get.
Read this first
Please do not post requests, because this is my personal kernel and I won't add any stuff I do not want myself (i.e D2W, S2W, AOD, sound control etc). Also I won't add any other support for other devices. Last but not least: I don't reply to questions like: "which governor/scheduler is the best" etc. The choice is all yours.
PS: You need to root yourself (Magisk on Nougat or SuperSU on Marshmallow)
Features
- Based on A810FXXU2CRH7 source
- Unified kernel that supports G920/G925 F/I/S/K/L/T/W8 models
- Upstreamed to Linux version 3.10.108
- Extra governors & I/O schedulers
- Linaro 6.5 compiler
- Always on display (AOD) support
- Wireguard support
- Knox 0x0 with safetynet bypass
- Permissive mode by default
- Synapse Control for OC/UC, voltages and a lot more
- LZ4 1.8.3
- Other misc optimizations
Download:
- V4 Marshmallowhttps://mega.nz/#!xxAAwBTA!2IL8I5Dx5IZsZp_uwrIT_DKTabzFu8_P6NlkD2EFORk
- Final Nougat https://mega.nz/#!RxhTHaaR!OLsnZ7yulPnaWd-mfSB1JCfMql3M_PjaUWyiFTMi1_U
Changelog:
V1
- Reworked whole kernel
- Optimized battery and performance
V1.1
- Reverted some stuff to test 3
- Fixed Fading LED
V1.5
- Tweaked LMK
- Optimized Workqueue
- Added battery efficiency patches
- AES put to x4 for more speed
- Readahead tweaked
- Vnswap to fast device
- HMP adjusted for more smoothness / battery efficiency
V1.8
- Reverted LMK and Workqueue edits.
- Enabled powereffici�nt Workqueue
- Tweaked Interactive governor
- Added Powersuspend
- Added more Binder changes for UI smoothness
- HMP and Cpuidle improvements.
- LZ4 Compressed
1.9
- Went back to UBERTC 5.3 because N0G33K V1.8 had kernel panics.
- Removed wlan wakelock control and reduced it myself.
- Some other edits and reverts
V2.0
- Reverted ALOT of changes I made in previous versions.
- Updated Kernel source to the latest DPJ2 source
- Compiled with Sabermod 7.0 Toolchain with CCache (should be stable now)
- Updated Linux to 3.10.104
- Backport latest Linux 4.8 random driver (= like super Seeder)
- Backport latest crypto algorithm Chacha20
- Added new battery efficiency patches
- Tweaked interactive governor for better performance/battery.
- Added new governors: Yankactive, Smartmax and Smartmax_eps
- Updated BFQ I/O
- Added dual sim support
- Fixed Invisible CPUset (should actually work now)
- Screen on hotplug disabled (Dynamic hotplug wasnt good enough)
- Added wakelock controls again.
- Updated Synapse
- Patched "Dirty Cow" (CVE-2016-5195) exploit
- Zswap improvements
- Disabled big cores on screen off
- Improved CPUIdle
- Powersuspend hooks added
- and more
V3
Reworked the whole kernel:
- Based on U5DPL4 source
- Powersuspend is out, State Notifier is in.
- Replaced Linux 4.8 random driver with Frandom
- Interactive governor: merged Galaxy S7 Interactive changes (android N changes wont boot, so kept it MM)
- Merged S7 zswap/zpool and zsmalloc android N changes
- Added Impulse governor
- Tweaked I/O Schedulers for our SSD + Zen V2 update
- Xbox control support added and updated to latest upstream (can be enabled in Synapse)
- Noatime as default for better performance
- SafetyNet patched (soon there probably will be a workaround for it...so enjoy as long it lasts)
- More wakelocks toggles added
- Sync on suspend disabled
- Improved Idle drain
- Android OS drain should be better now.
- Removed some other stuff that caused yank like invisible cpusets
V4
- Updated Linux kernel to 3.10.105
- Updated Safetynet patch
- Binder updated to latest Linux 4.6 (smoother UI)
- Backported Linux 4.1.38 random driver and removed Frandom
- DVFS decision mode in Synapse added
- DVFS: scale to 1k instead of 1.2k GHz
- Backported latest CPUidle driver from Linux 4.7 (should give better idle experience throughout the day)
- Other misc optimizations
V7
- Rebased kernel and kept it quite stock/light
- Doesn't use recycle commits (= commits that have been using in all S6 kernels for the last 4 years, without anything new).
- Based on the A810FXXU2CRH7 source code, which means that its newer than any G920x source out there.
- Upstreamed to 3.10.108
- Unification added to work for nearly all S6(e) devices (No A & P model support)
- Improved touch latency
- LZ4 fast 1.8.3
- Compiled with Linaro 6.5
- Added Wireguard support
- Great performance and battery life -> Ask @ananjaser1211 who copied the kernel
The kernel wont be updated anymore (no oreo support/updates), therefore enjoy this last kernel while it lasts. If something is broken in Synapse, then so be it.
Credits:
- CODEG33K - Dear friend that I partially named kernel after
- Aria.A97 - Intensive daily testing
- Everyone else I cherry-picked from.
Source Code: https://github.com/Noxxxious/S6
Want to use this in your rom?: Don't, just forward to the thread.
Disclaimer: I am not responsible for all the damages followed by or to your phone after flashing this kernel. If it bricks, wipes, explodes and you will hold me responsible I will only laugh
Known issues:
- Probably Synapse "backup profile" doesnt work.
F.A.Q. - Frequently Asked Questions
Q: Synapse says no UCI detected
A: Install Busybox to system/xbin
Q: I had a reboot
A: Only report it here if you didn't undervolt and do it with a log.
A2: If you had random reboot without undervolting, then make a proper log please. Which means I need a last_kmsg from right after the reboot.
You create the log by using this command in adb shell or a terminal or use any 3rd party app like Syslog.
Code:
cat /proc/last_kmsg > /sdcard/last_kmsg.txt
Good luck .
Maybe you will add for g925F support to .
senzatiOn- said:
Good luck .
Maybe you will add for g925F support to .
Click to expand...
Click to collapse
+1
That will be awesome
@senzatiOn- @Sommerrain
Read my "Read this first". Already said that I wont.
But never say never, who knows.
So if rhis works with 920f does that mean it work with 920i
panda968 said:
So if rhis works with 920f does that mean it work with 920i
Click to expand...
Click to collapse
Yes, 920F/I same device, just different regions.
Happy flashing :good:
Quintz said:
@senzatiOn- @Sommerrain
Read my "Read this first". Already said that I wont.
But never say never, who knows.
Click to expand...
Click to collapse
I have read this.... i just ask... MAYBE
GL & HF
I lost RIL (signal) after flashing V3.
Unknown IMEI, but efs partition intact.
Going back to Arter v22 Grace, fixes this issue.
OP is aware of this, and will look into it, so have a nandroid backup in your hands, and be sure you have a fresh efs backup, prior to flashing V3.
It might not happen to you, but since some users have V3 installed already without issues, consider your self warned.
-----
senzatiOn- said:
I have read this.... i just ask... MAYBE
GL & HF
Click to expand...
Click to collapse
Thanks !
CODEG33K said:
I lost RIL (signal) after flashing V3.
Unknown IMEI, but efs partition intact.
Going back to Arter v22 Grace, fixes this issue.
OP is aware of this, and will look into it, so have a nandroid backup in your hands, and be sure you have a fresh efs backup, prior to flashing V3.
It might not happen to you, but since some users have V3 installed already without issues, consider your self warned.
-----
Click to expand...
Click to collapse
Yes like I stated the N7 compatibility is still in beta. So far this is the first case where there is no signal. I am taking a look into it.
Also people you dont need an EFS backup or something, flashing back to stock or arter N7 kernel will just be fine.
I'm happy to see you finally here ?
Inviato dal mio SM-G925F utilizzando Tapatalk
Quintz said:
Thanks !
Also people you dont need an EFS backup or something, flashing back to stock or arter N7 kernel will just be fine.
Click to expand...
Click to collapse
Couldn't hurt
It's refreshing seeing a new kernel here, thank you for your efforts and your development, I shall surely be trying this out.
like u my bro and thanks for hard work
gave glory make perfect kernel for us
keep going im with you:fingers-crossed:
CODEG33K said:
Yes, 920F/I same device, just different regions.
Happy flashing :good:
Click to expand...
Click to collapse
If thats the case if i find a rom that only says 920f it will work for my phone
Great work!
Quintz said:
Thanks !
Yes like I stated the N7 compatibility is still in beta. So far this is the first case where there is no signal. I am taking a look into it.
Also people you dont need an EFS backup or something, flashing back to stock or arter N7 kernel will just be fine.
Click to expand...
Click to collapse
I can confirm, using tamerlan n7 port ROM, I lost signal and my IMEI
And thanks for your hard work , nice to see other developers on our device.
Netmain36 said:
I can confirm, using tamerlan n7 port ROM, I lost signal and my IMEI
And thanks for your hard work , nice to see other developers on our device.
Click to expand...
Click to collapse
Lol I'm using tamerlan and is all good
Cesarcami53 said:
Lol I'm using tamerlan and is all good
Click to expand...
Click to collapse
Yes wait, I help my friend to fix this
AlexisXDA said:
Yes wait, I help my friend to fix this
Click to expand...
Click to collapse
Alexis signal works the problem is after every reboots takes like 2 minutes to get signal again
Argon kernel, for Android 8.1 & 9.0 ROM's (bacon).
Disclaimer:
use this kernel at your own risk. Flashing it without any knowledge of what you're doing may brick your device. I'm not responsible for any software/hardware damage.
Argon v11 is the last version for Oreo! Starting from v12 only Pie is supported.
Changelog:
v16.1 (August 11th)
support for OTG Y cables
minor bug fixes and security patches
Previous releases:
v16 (August 2nd)
kernel code base synced with LineageOS
lots of misc. bug fixes and small improvements
sdfat driver now replaces both vfat and exfat
some f2fs backports
v14 (April 24th)
built with the newest GCC toolchain for ARM
dynamic management of dirty page writebacks
some useless drivers have been removed (this might give us a few additional MB's of RAM)
a couple of improvements for the random number generator driver
IRQ threading is enabled by default (as suggested by Con Kolivas)
v13 (March 31st)
memory bandwidth overclock
lots of small updates and improvements (mainly for the assembly memory routines)
a few updates for the impulse CPU governor
new TCP congestion control algorithm: 'ascarex'
v12 (March 10th)
official Pie support (LineageOS 16 & Lineage-based ROMs)
small bug fixes and misc. tweaks
a few updates for the "impulse" CPU gov
memory management backports from Linux 3.8
lighter kernel (some debugging options have been turned off)
v11 (January 27th)
built with the newest ARM toolchain
power-efficient workqueues have been implemented in a couple of places
minor source updates & fixes
DDR bandwidth boost has been fixed
important updates for Sultan's CPU boost driver
v10.2 (January 19th)
synced with our LineageOS kernel (mainly bug fixes and security patches)
v10.1 (January 12th)
some source updates and bug fixes
v10 (December 29th)
built with the latest GCC 8 toolchain by Arm
some debugging options are disabled (this might slightly improve performance)
lots of small bug fixes and source updates
v9 (December 11th)
zzmoove governor updated to the latest version
boosted L2 cache frequencies
Spectrum support
Sultanxda's simple thermal driver (replaces Intellithermal)
miscellaneous kernel updates, backports and fixes
dynamic fsync has been (temporarily?) removed
v8.1 (November 23rd)
lots of kernel source updates & fixes
exFAT/sdFAT support
new CPU governors: intellimm, yankactive, zzmoove and impulse
dynamix fsync (disabled by default)
v8 (November 4th) - diff against v6:
built with GCC 8
old charging drivers (these are stable and work properly for everybody)
several improvements for the audio drivers, the memory management libraries, the CPU boosting driver, f2fs, zram, etc.
latest sdcardfs fixes from Google
Intellithermal (with configurable throttling threshold)
latest security fixes
CPU overclocking (disabled by default)
updated bricked hotplug
UKSM with automatic toggling (wip, it's not fully working as of now)
async fsync for ext4 and f2fs
v7.7 (October 23rd)
rebased on top of v7 + all the extra changes of v7.6
msm_hotplug removed (bricked is the default hotplug)
v7.6 (October 23rd)
completely rebased on top of Argon v6.1 (which seems to be the latest stable release) + the following changes
built with GCC 8.2
MSM hotplug enabled by default
cpu_input_boost improvements
latest sdcardfs updates
several other security fixes and improvements
v7.1, v7.2, v7.3, v7.4, v7.5 (October 10th - 11th - 15th - 16th - 17th)
stability fixes
v7 (October 9th)
msm_hotplug replaces bricked as the default hotplug
optimizations for msm8974 boards
older charging drivers from LineageOS 14.1 (they seem to fix all charging problems)
some more minor tweaks, fixes and optimizations
v6.1 (September 30th)
mpdecision is replaced by bricked hotplug by default
v6 (September 27th)
stability fixes
AIO optimizations reverted (this fixes filesystem errors for ext4 users)
slimbus overclock
several improvements and updates (for the ext4 fs, the LMK and many other drivers)
charging current interface
cpu_input_boost by Sultanxda (it replaces CAF's cpu_boost)
v5 (September 19th)
zram is supported
AIO optimizations & backports
minor tweaks and updates
v4 (September 15th)
Per-process reclaim
minor updates and improvements (including security fixes)
v3 (September 8th)
DDR bandwidth boost on screen unlock
misc. kernel updates, fixes and improvements
v2 (August 31st)
several secuirty fixes and kernel source updates
f2fs driver updates
new CPU hotplug: bricked hotplug
power-efficient workqueues are implemented in more drivers
v1 (August 24th)
based on idprophecy's kernel, thus it should be compatible with any Oreo ROM
built using QUVNTNM-TC, based on GCC 7.3.x
CPU underclocking (268,8 MHz)
several compiler optimizations enabled
sound contol by franciscofranco
lots of miscellaneous fixes and improvements
sysfs interface for Gentle Fair Sleepers and Arch power
power-efficient workqueues
Downloads
Latest version: here.
Argon kernel on MEGA
Argon kernel on AndroidFileHost
Thanks to:
@idprophecy
@dorimanx
@faux123
@Sultanxda
@CertifiedBlyndGuy
@osm0sis
@franciscofranco
@GalaticStryder
@nikhil18
the LineageOS team
and all the other authors of the hundreds of commits in Argon's github repo!
XDA:DevDB Information
Argon kernel for Oneplus One, Kernel for the OnePlus One
Contributors
Tomoms
Source Code: https://github.com/Tomoms/argon_kernel
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: 16.1
Stable Release Date: 2019-08-11
Created 2018-08-24
Last Updated 2019-08-11
Reserved
How to set up the charging speed interface in Kernel Adiutor?
First thing, download the attached zip and decompress it. You'll find two .json files in it, place them in your internal storage and open KA. Go in the "Custom controls" tab, tap on the "+" button, choose "Import" and select the first of the files you downloaded, then import the second one too. Done! You can now delete the two files.
Keep in mind that the "0" value means that the standard charging logic will be used, and that the AC charging speed cannot be set to a value lower than 200 mAh, even though the slider allows you to set any value. If you set any value between 1 and 199, the driver will fallback to 200.
working fine with AEX 5.7.
is it compatible with oxygen os blobs or sultan blobs?
Running well for me on AEX 5.7.
antfior93 said:
is it compatible with oxygen os blobs or sultan blobs?
Click to expand...
Click to collapse
Starting from Oreo, all ROMs implement Sultan's camera, thus this kernel only supports Sultan's camera HAL.
New version is available
It's an important updates that brings lots of improvements (mainly "under the hood"), for more info I suggest you to check my Github repo!
Really nice work. Don't want to sound rude or something but is there a chance of getting a Pie build? ?
rolarocka said:
Really nice work. Don't want to sound rude or something but is there a chance of getting a Pie build?
Click to expand...
Click to collapse
Most probably, this kernel already works on Pie
You just need to flash it, then flash the Kernel Permissive Patcher (link - needed to set SELinux to Permissive before booting the OS) and you should be good to go. If you try, let me know the result!
What is the stock setting this kernel comes in? I want to try it but don't want to use root (for now). So I'm wondering what settings are default. Would kinda make this a flash and forget kinda kernel
twowheeler said:
What is the stock setting this kernel comes in? I want to try it but don't want to use root (for now). So I'm wondering what settings are default. Would kinda make this a flash and forget kinda kernel
Click to expand...
Click to collapse
The stock settings are kind of good. Not the best you could get, but close (I'll tweak the default configuration a little more in the future). If you're using idprophecy's ROM you will end up having maple as the default I/O scheduler, while if you're using other ROMs, I'm pretty sure you won't. Anyway, if you flash this kernel, I'm sure you'll benefit from the general improvements I implemented, which do not need any tweak to be enabled.
Works well on following ROMs;
-AOSiP 20180825( Argon v1 )
-TugaPower O25 ( Argon v2 )
Hi i installed it over AEX 5.7 . it works but charging is buggy. Keeps disconnecting and connecting .
tamboli007 said:
Hi i installed it over AEX 5.7 . it works but charging is buggy. Keeps disconnecting and connecting .
Click to expand...
Click to collapse
I have the same thing on all ROMs based on the LOS core. And this kernel is based, as I understand it, on the LOS core ... For example, with FranoKernel there are no such problems.
tamboli007 said:
Hi i installed it over AEX 5.7 . it works but charging is buggy. Keeps disconnecting and connecting .
Click to expand...
Click to collapse
MrYuraB said:
I have the same thing on all ROMs based on the LOS core. And this kernel is based, as I understand it, on the LOS core ... For example, with FranoKernel there are no such problems.
Click to expand...
Click to collapse
I experience the same issue when using a certain non-original (yet good-quality) cable. The weird thing is that if I charge the phone while it's turned off, it charges perfectly. Anyway, I can try to fix this issue. It shouldn't be difficult. I'll keep you informed.
Good to see you're still contributing for Bacon.
Tomoms said:
I experience the same issue when using a certain non-original (yet good-quality) cable. The weird thing is that if I charge the phone while it's turned off, it charges perfectly. Anyway, I can try to fix this issue. It shouldn't be difficult. I'll keep you informed.
Click to expand...
Click to collapse
Yesterday I tried to send you message, but it is why it is not sent... I agree
I've uploaded a new kernel!
Argon v3 is a small yet important update: it brings DDR bandwidth boost on screen unlock (basically, the RAM bandwidth is boosted when you unlock your phone so that opening an app immediately after waking the device from idle takes less time) and some general fixes & improvements for the kernel. More details are available on Github, as usual
Tomoms said:
I've uploaded a new kernel!
Argon v3 is a small yet important update: it brings DDR bandwidth boost on screen unlock (basically, the RAM bandwidth is boosted when you unlock your phone so that opening an app immediately after waking the device from idle takes less time) and some general fixes & improvements for the kernel. More details are available on Github, as usual
Click to expand...
Click to collapse
I've been loving the Kernel on AEX 5.7, but I've needed to reboot a few times because the screen won't turn on, or the screen has frozen.
Do you think that could be from the default underclock?
@Ruggerxpunk Same issue on my side since V2 version, but I don't have any logs cause I'm not using it at this moment.
Hello!
I want to introduce my first custom kernel for the SM8250 family of Snapdragons. This is based of latest Samsung OneUI 2.5 Sources and I cherry-picked commits to make improvements to the stock base. I'm not a developer, but i really like to port stuff over .
I will try to have this Kernel updated as soon as new source tarballs are drop by Samsung. If you want to request for specific features, let me know and i'll do my best to bring them over.
Special Features:
Changelog is in post #2
How to Install:
First, make sure you are in any OneUI 2.5 (BTH* or BTI*) ROM and have TWRP on the device. Make sure you take a backup of your current boot partition in twrp, now install either the boot.img (extract from the tar file) or use ODIN to flash in Dowload mode. Please make sure to read Post #3 regarding issues with the current OS Patch Level. Images from 1.5.0 onwards are pre-rooted but you will probably need to update magisk either manually or by flashing latest magisk.zip file.
Keep in mind the following table to determine your phone model:
x1q = S20 - G981X
y2q = S20+ - G986X
z3q = S20U - G988X
r8q = S20 FE - G781B
c1q = Note 20 - N981X
c2q = Note 20U - N986X
IMPORTANT NOTE: It seems some users need to flash a vbmeta image file provided by Google in order to boot and user the Custom Kernel. If you find yourself in a situation were you are not able to boot, please flash the attached vbmeta img along with the Kernel and if still bootlooping share the last_kmsg to determine what's driving the issue.
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....
You can use THIS link to get the latest builds. These and other downloads can also be found in the Telegram Group.
Sources for Q? https://github.com/Jimbo77/JimboK_common_sm8250
Sources for R? https://github.com/Jimbo77/Jimbok_common_sm8250-R
Join the Telegram Group for additional discussions and downloads - HERE
Special thanks to:
Afaneh
Ianmcd
0smosis
flar2
Lord Boeffla
jesec
elliwigy
pappasmurf
For their work and dedication to development!
Changelog or features or whatever
04.10.21 - JimboK-R-2.6.0
Upstreamed to .185
04.05.21 - JimboK-R-2.5.0[/B]
Sync code to add missing changes in upstreamed branch
Reworked the DEVFREQ_BOOST driver
Tweaked SchedHorizon default freqs
Tweaked DEVFREQ_BOOST defaults in defconfig
03.31.21 - JimboK-R-2.4.0[/B]
Upstreamed to Stable Linux 4.19.184
Built with cortex-a55 specific optimizations
removed facebook process from 'kill-in-the-background' mod. This was affecting the user experience (for those that use Facebook a lot, like my wife lol)
02.24.21 - JimboK-R-2.3.0[/B]
Upstreamed to Stable Linux 4.19.176
Switched from G988U source as base to N986N source drop for OneUI 3.1
Removed a lot of unused configs from defconfig. This resulted in a reduction of Kernel size and will have an impact on the overall performance and resource utilization.
Reworked the DEVFREQ and CPU_INPUT_BOOST drivers
Added and Enabled schedhorizon governor
Imported the option to edit the CPU Frequency table
Performance Governor is default for LITTLE Cluster now
02.03.21 - JimboK-R-2.1.0[/B]
Upstreamed to Stable Linux 4.19.172
Moved to KOR dts to improve on stability for custom DTBO's
Added Flicker-Free or DC Dimming. There are two versions of the Kernel and this will be the only version with Flicker Free. After this, there will not be added since i don't like how it messes the Screen Colors/Performance.
Disabled Bootstats
Enabled MPTCP
01.25.21 - JimboK-R-2.0.0[/B]
Upstreamed to Stable Linux 4.19.169
Disabled several not needed debug Samsung Configs
CPU ASSIST Feature
Disabled ZRAM and SWAP
DTS (dtb and dtbo) updates for all variants to their latest source drops
General CLANG and LLVM optimizations
01.01.21 - JimboK-R-1.8.0
Reworked both DEVFREQ and CPU_INPUT Boost functionalities
finetuned for SM8250 (Samsung) specific frequencies/values
added and enabled Simple Low Memory Killer (SLMK)
added: CIFS, NTFS and ISO9660 FS in-kernel Support
added Wireguard Support
Several 'under the hood' improvements to task/memory management.
12.28.20 - JimboK-R-1.7.0
Added BBR2 TCP Config and made Default
Several updates to NET protocols and BBR2
Added PROC_MAGISK_HIDE_MOUNT
Added a script to fix Shealth, Smart View and set ZRAM parameters.
12.25.20 - JimboK-R-1.6.0
Added Dynamic Fsync
Tweaks for Memory Management
Updated LZ4 compressor
Enabled ZSTD Compressor for ZRAM - Default now
12.21.20 - JimboK-R-1.5.1
Fixed Wifi Calling
12.20.20 - JimboK-R-1.5.0
Fsync On/Off Support
Readahead 0
Slimbus OC
Toggle to enable/disable CRC
Turned off several debug options within the tree
added EAS related commits
12.16.20 - JimboK-R-1.4.0
Added Kcal Color Control Driver
Added KLAPSE Driver
Disabled Gentle Fair Sleepers
Added Boeffla Wakelock Blocker
Disabled AVB Flag for better protector in terms of SafetyNet
Misc fixes and addons to dtb
12.15.20 - JimboK-R-1.3.0
Skipped, no public Release xD
12.13.20 - JimboK-R-1.2.0
Added IO-SCHED drivers like: ZEN, FIOPS, MAPLE etc...
Added DevFreq Boost Driver and tuned based off OP8
Added Adreno Boost Driver
12.12.20 - JimboK-R-1.0.0
Initial Android R (OneUI 3.0) bring up
Source is based off the G988U source drop. This includes all other variant files, i have added support to all previous phones from day one now
Disabled Samsung Security useless stuff (DM Verity for example)
11.01.20 - JimboK-1.6.3
Added a fix to hide Magisk Mount for Isolated Processes. This is a critical leak in MagiskHide that can be exploited by apps trying to determine if the device is rooted. I had an issue with two payment apps that after applying this fix, they work. Not sure if they were finding magisk with this method lol. Read more here https://darvincitech.wordpress.com/2019/11/04/detecting-magisk-hide/
Finally removed the warning upon boot. EdXposed compatibility was not affected by the removal of it.
10.27.20 - JimboK-1.5.0
Rebased to S20 FE source as baseline for all models. This is to ensure support for the S20 FE is added and to keep the most up date source from Samsung
Streamlined even further the 'common' defconfig and updated all other variant defconfigs to make it easier to build individual Kernels.
Removed GPU OC - This is to test drive if performance takes a small hit but battery is gained. I have this as *temp change* consider it a 'test' phase so i will need your feedback on it to see whether if we keep it or not. Also, the OC was causing issues to boot in N20 units and some weird hiccups in the System-UI for my S20U.
Added BBR2 TCP CONG protocol. By far, the best TCP CONG to speed up the network connections overall. Read out more here: http://dl.ifip.org/db/conf/networking/networking2018/2B1-1570416152.pdf
BBR2 is now default TCP CONG for the Kernel. I recommend ya'll to make the switch
Several Upstreams to NET/TCP in order to improve Network Connectivity and Speed.
Kernel comes pre-rooted now (via ramdisk). In the event of a magisk update you will only need to update through Magisk Manager. This is for the sake of simplicity
10.16.20 - JimboK-1.4.0
Removed several DEBUG options from defconfig that should not be present in a Production Kernel
Disabled ZSWAP and VBSWAP (this will create conflict with ZRAM) and ZRAM has proven to be more effective and create less wear than ZSWAP
Disabled LZO, updated LZ4 compression algorithms
Enabled ZSTD Compression, it is recommended to enable this for ZRAM moving forward
Disabled KPERFORM in defconfig
Enabled .gz compression for Kernel. Kernel is now almost 1/3 in size of what it used to be
Added and Enabled HID: NINTENDO SWITCH controllers support
10.13.20 - JimboK-1.3.0
Unified Sources a bit more. Removed the individual defconfigs to have one single plus each variant
for X1Q and Y2Q moved dts sources from CHN OPEN to KOR to keep it in line with main (Z3Q) sources and also for CXQ sources. BTI3 (latest software release) is now used for those models.
Enabled a few drivers inside of Kernel: CDC, NTFS, CIFS and some native gaming devices as well
Disabled DM_VERITY checks. This will help with the booting times
JimboK-1.2.0 and before:
Build with latest LLVM Clang 11
Disabled Samsung Security useless stuff (DM Verity for example)
GPU OC up to 895mhz
Adreno Boost
Boeffla Wakelock Blocker Driver
Disabled ZRAM and moved to ZSWAP and VBSWAP
KCAL Color Control Driver (Up to date)
KLAPSE Driver (check out https://forum.xda-developers.com/an...apse-kernel-level-livedisplay-module-t3907025)
Added IO-SCHED drivers like: ZEN, FIOPS, MAPLE etc...
Latest Wireguard Driver
BBR TCP Congestion algorithm by Default
built-in Kernel Westwood and other modules
SLIMBUS OC to improve the Audio Mods
Several Debug Options removed from driver and all over the Kernel itself
QCACLD-3.0 Support
Dynamic Sync Control
Fsync On/Off Toggle
Several EAS commits for balancing power+efficiency
OS PATCH LEVEL set as 2099-12 (Read post #3 - Mandatory)
OS PATCH LEVEL PROBLEM
This is a modified version of @evdenis post HERE
My Kernel uses an OS Patch Level of 2099-12 to maximize its compatibility among all releases by Samsung across all the supported phones. That's it. No other reason as to why choose that date, now, when you continue using my Kernel update after update there will be no issue, but if you change the kernel to any other (specially stock) chances are that Kernel is using the current month OS PATCH LEVEL which will cause two things:
You will not be able to pass beyond your lockscreen. No matter what you try, it won't let you unlock upon reboot
Your Samsung Account will warn you to log off and log back in but you will not be able to do so
The problem is not in sources. It's due to os_patch_level mismatch with you current kernel. As mentioned JimboK Kernel does not uses common security patch date to be in sync with the official samsung firmwares. You can check the default os_patch_level in build.mkbootimg.* files. However, this date can be higher than other kernels use. When you flash a kernel with an earlier patch date on top of the previous one with a higher date, android activates rollback protection mechanism and you face the problems stated earlier. It's impossible to use a "universal" os_patch_level because different users use different custom kernels and different firmwares. JimboK Kernel uses a highest date by default in order to suite most of users.
How can you solve the problem? 6 ways:
You can restore my kernel and the problems will be gone
You can flash the attached zip file. backtothefuture-2099-12.zip, it will make your new Kernel Patch OS Level 2099-12 thus avoiding the issues above. - read more about the zip HERE. You will have to flash this with any new kernel if you ever use mine (unless you do a full wipe as mentioned at the end of this list).
You can check the os_patch_level date of your new kernel here https://cruelkernel.org/tools/bootimg/ and patch the kernel image image to the same date. If your previous kernel is mine (JIMBOK), patch your new Kernel to 2099-12 date.
You can reboot to TWRP, navigate to data/system and delete 3 files those names starts with 'lock'. Reboot. Login, set a new pin. To fix samsung account login, reinstall the app
You can rebuild JimboK Kernel with os_patch_level that suites you. To do it, you need to change the OS PATCH LEVEL to the desire date when using mkbootimg.
You can do the full wipe during the new Kernel flashing
Update 10.20.20
Updated the zip file to add support for W models.
Update 10.19.20
Updated the zip file to remove Exy devices and focus solely in N20 and S20 Snap line.
Finally kernel for s20 thanks a lot.
Works great!
I've got bootloop with my S20U G9880 after flashing this kernel even with a full wipe
Working
It works on my G9810 Thanks!!!
stszf9124 said:
I've got bootloop with my S20U G9880 after flashing this kernel even with a full wipe
Click to expand...
Click to collapse
Strange I have G988N which is just about the same and I don't have that issue. Did you come from a rooted device? Were you in a custom ROM before?
Can you tell me a bit more of your setup?
Are there any other G9880 users with the same issue?
I have s20+ 5g g986u
Unlocked bl
Flashing twrp
Flashed the kernel
Flashed vmbeta disabler
Flashed magisk
Boot
All ok
Thank you
thank you
my device is running custom Rom and stock kernel, the firmware is BTH6 , last night I installed the latest version of TWRP and format data and flashed the multiple disabler, the device booted , but it got this issue after the kernel was installed even with a full wipe again
has battery life been improved?
can i flash this and then magisk to get root?
Smartphones13 said:
can i flash this and then magisk to get root?
Click to expand...
Click to collapse
Yes, you can do that.
Viet.molet said:
has battery life been improved?
Click to expand...
Click to collapse
I flashed this and did a minor debloat and gained roughly 30 minutes of screen on time.
I also noticed the animation from recents to home screen is slightly snappier.
Could be placebo but I like it.
@jimbo77 what kind of benefits do I get by flashing your Kernel?
chieco said:
@jimbo77 what kind of benefits do I get by flashing your Kernel?
Click to expand...
Click to collapse
Disabled some Samsung Security, you will be able to run edxposed if you are into that. Also a few changes and add-ons, read the op for some of the features added to the Kernel
Works on sm-g9810?
jucin said:
Works on sm-g9810?
Click to expand...
Click to collapse
It should. Although I haven't personally tried since I own a G988N
jimbo77 said:
Yes, you can do that.
Click to expand...
Click to collapse
Hey man, how's it going? Did you do anything special to get kcal working on the kernel? Mental made a kernel for the Note 20 Ultra but said he could not get Kcal working.
Also, even better, would you consider making a common kernel for the Note 20 Ultra Snapdragon? I'd definitely send a donation your way.