[KERNEL] [blu_spark r60 OP7/Pro] [OOS /Custom A10] - OnePlus 7 ROMs, Kernels, Recoveries, & Other Devel

{
"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"
}
Kernel features:
Powered by Ubuntu 18.04.3 x86_64 (sparky VPS @ www.servercore.com.br - thanks @ChristianLetti)
Build with custom toolchain blu_gcc-9.2.0 (cortex-a76.cortex-a55 targeted, build with latest Crosstool-NG from GCC-9.2.0 snapshot)
Full -O2 build with device and target flags enhanced, linaro build improvements, etc
Less is more: stockish OP7 builds based on OnePlusOSS/android_kernel_oneplus_sm8150 for max stability
Systemless installer (doesn't touch system partition, OTA friendly), AnyKernel3 backend (compatible with autoflash apps)
Removed some debug and logging options
ARM enhanced performance and battery patches
CVE security patches, general upstream and CAF fixes for important subsystems
Several CPU Governors (blu_schedutil modded governor merged from latest CAF sm8150 patchset)
No OC, use 300HZ base timer frequency
msm_performance touchboost toggle on/off (enabled by default), tweaked cpu_boost driver
Enhanced TCP methods (westwood is default), Network tweaks and updated drivers
Several I/O control tweaks, added schedulers ZEN v2 is default, advanced filesystems enabled (F2FS, ExFAT, NTFS, CIFS & NFS)
Patched SafetyNet flags to pass CTS
Stock thermal driver by default
ZRAM Swap (LZ4) and with file disabled
Vibrator Strength tunable and Gesture Haptic Feedback control (touchpanel and FPR)
KGSL fixes and reworked GPU driver
adrenoboost enabled by default at low level
KCAL - Advanced color control for Qualcomm MDSS v2 (RGB calibration and post-processing features)
KLAPSE support (v5.0)
USB Fast Charge (USB mode up to 900mA with MTP on)
FS fsync toggle on/off
Wakelock blockers available
wireguard support
CDROM emulation on mass_storage (compatible with DriveDroid 0.10.36+)
Compatible with Kernel Adiutor, EXKM, FKM and others
DOWNLOAD KERNEL ZIP​(No mirrors please)​
Warning: If you come from other kernel or have any issues, you should dirty flash your ROM before flashing blu_spark zip to avoid problems.
Reflash ROM -> flash TWRP --> reboot to recovery --> flash Magisk if you want (default, no plugins/modules) -> flash blu_spark.
If you are already rooted or upgrading between blu_spark versions, just flash the kernel zip. Also uninstall or clean data of any kernel control app you're using.
About bugs and troubleshoots: don't bother to post if a log isn't ready or without steps so the behavior can be replicated. I only active support stock OOS with NO mods whatsoever (apart from root). That includes NO support if using xposed, Magisk with modules, etc.
If you're using custom ROMs (including OOS based ones) or Open Betas you're on your own. I'm only interested on debugging stuff in stock and stable OOS.
Save the SOT and battery stats/screenshots for general threads, here we deal with development, not personal tastes and results.
Also don't spam this thread with CM or other ROMs stuff like "this don't work, my app doesn't open, etc" , no OT about OTAs, apps, ROM bugs, Recovery/TWRP troubleshoots and other userspace stuff. There's threads for it, use them.
Going back to stock: This kernel installer doesn't change your filesystem. You can backup your boot.img with TWRP before flashing blu_spark if you want to go back to full stock or just dirty flash your full ROM.
If you like my work, donations are always welcome.
Don't forget to hit thanks and rate the thread nicely, it's free
OnePlus 7 Pro development unit donated by OnePlus. Big shouts to them
Very proud of being on the OnePlus Developer Program, special thanks to Manu J. for being such a supportive person.
XDA:DevDB Information
blu_spark kernel for OnePlus 7/Pro, Kernel for the OnePlus 7
Contributors
eng.stk
Source Code: https://github.com/engstk/op7
Kernel Special Features: Powered by sparky
Version Information
Status: Stable
Current Stable Version: r60 unified
Stable Release Date: 2019-10-13
Current Beta Version: r38 unified
Beta Release Date: 2019-08-24
Created 2019-07-01
Last Updated 2019-11-08

blu_spark r10 release (unified)
All right crew!
New build is up :highfive:
This kernel is unified, should be good on OP7/Pro (I only can test on Pro).
So keep this in mind if there's anything wonky. Check out the 7 Pro thread, some stuff is already discussed there.
blu_spark_r10 release
KCAL v2
KLAPSE v5.0
adrenoboost
USB2 fast charge (if it doesn't work, restart the device without any cable, turn on fast charge and connect the cable after)
couple init settings tune
AnyKernel3 updates
Click to expand...
Click to collapse
Keep in mind: I will give no active support for custom ROMs (including OOS based ones).
I am only interested on debugging stuff in stock and stable OOS (with logs and reproducible steps to replicate the issue).
Don't spam this thread with LOS or other ROMs stuff like "this don't work, my app doesn't open, etc" or debugging features.
Also don't go spam and bug reporting on ROM threads if using this.
No mirrors please
If you like my work, donations are always welcome.
Don't forget to hit thanks and rate the thread nicely, it's free

Will try this soon! Thank you for your work

Finally u r here!!!!

So how's it rolling, all good?
Sent from my blu_spark'd Oneplus

Waiting for the device to come... Then I will flash your kernel... Can't wait

eng.stk said:
So how's it rolling, all good?
Click to expand...
Click to collapse
Yes, all good! "Battery life" and performance are great. Zero heat up while playing heavy games. Keep up the good work!

blu_spark r14 release (unified)
All right crew!
New build is up :highfive:
This kernel is unified, should be good on OP7/Pro (I only can test on Pro).
blu_spark_r14 release
Merge blu_schedutil
input: touchscreen: add haptic feedback control sysfs
power: smb5-lib: reset level on removal (fix fast charge toggle without reboot)
set hz=300 (for interactiveness)
wireguard updates (v0.0.20190702)
some UX improve tuning
AnyKernel3 updates
Click to expand...
Click to collapse
Keep in mind: I will give no active support for custom ROMs (including OOS based ones).
I am only interested on debugging stuff in stock and stable OOS (with logs and reproducible steps to replicate the issue).
Don't spam this thread with LOS or other ROMs stuff like "this don't work, my app doesn't open, etc" or debugging features.
Also don't go spam and bug reporting on ROM threads if using this.
No mirrors please
If you like my work, donations are always welcome.
Don't forget to hit thanks and rate the thread nicely, it's free

Has the kernel something todo with the signal strength/mechanism of a device or is this a rom setting?

nexuspur said:
Has the kernel something todo with the signal strength/mechanism of a device or is this a rom setting?
Click to expand...
Click to collapse
Depends strength of what in particular?
If you're talking about 4g/gsm, nope.
Sent from my blu_spark'd OnePlus

Flashed kernel an hour ago. Will see how it goes. Thanks for your work

eng.stk said:
All right crew!
New build is up :highfive:
This kernel is unified, should be good on OP7/Pro (I only can test on Pro).
blu_spark_r14 release
Keep in mind: I will give no active support for custom ROMs (including OOS based ones).
I am only interested on debugging stuff in stock and stable OOS (with logs and reproducible steps to replicate the issue).
Don't spam this thread with LOS or other ROMs stuff like "this don't work, my app doesn't open, etc" or debugging features.
Also don't go spam and bug reporting on ROM threads if using this.
No mirrors please
If you like my work, donations are always welcome.
Don't forget to hit thanks and rate the thread nicely, it's free
Click to expand...
Click to collapse
Hi,
Thanks for excellent battery friendly Kernal.

pushpendrayadav said:
Hi,
Thanks for excellent battery friendly Kernal.
Click to expand...
Click to collapse
Stock settings?

blu_spark r16 release (unified)
All right crew!
New build is up :highfive:
This kernel is unified, should be good on OP7/Pro (I only can test on Pro).
blu_spark_r16 release
Synchronize codes for Oneplus 7 Pro Oxygen OS 9.5.9.GM21AA
Add GPU 675Mhz freq step (default is 585Mhz)
couple build improvements
defconfig: enable some perf configs and remove cruft
Remove some debug and logging
Add support for OP7 Pro TMO on installer
Click to expand...
Click to collapse
Keep in mind: I will give no active support for custom ROMs (including OOS based ones).
I am only interested on debugging stuff in stock and stable OOS (with logs and reproducible steps to replicate the issue).
Don't spam this thread with LOS or other ROMs stuff like "this don't work, my app doesn't open, etc" or debugging features.
Also don't go spam and bug reporting on ROM threads if using this.
No mirrors please
If you like my work, donations are always welcome.
Don't forget to hit thanks and rate the thread nicely, it's free

pushpendrayadav said:
Hi,
Thanks for excellent battery friendly Kernal.
Click to expand...
Click to collapse
Lol, I get the same SOT with stock kernel.
Edit: @eng.stk the update works great for me on my OP7.
Thanks

I cant set the minimum cpu frequency. It goes back to stock which is the same as the maximum cpu frequency(1785MHz on little cores)

carlsmad said:
I cant set the minimum cpu frequency. It goes back to stock which is the same as the maximum cpu frequency(1785MHz on little cores)
Click to expand...
Click to collapse
I can set it just fine.
1785 is not the default min, if you cant change it and its locked to that max value you have something else derping and locking it.
Sent from my blu_spark'd Oneplus

eng.stk said:
I can set it just fine.
1785 is not the default min, if you cant change it and its locked to that max value you have something else derping and locking it.
Sent from my blu_spark'd Oneplus
Click to expand...
Click to collapse
Okay sir. Thanks. I think I'll just format my phone again.

@eng.stk Portrait mode isn't working with your kernel.

Kollachi said:
@eng.stk Portrait mode isn't working with your kernel.
Click to expand...
Click to collapse
Works fine in 7pro OOS 9.5.9 with stock camera app, used it yesterday actually several times.
Multimedia driver stack, including camera, is totally stock in blu_spark.
edit: also OP7 is behind in ROM versions, they updated camera stuff on latest OOS 9.5.9 sourcedrop, so you may have to stay with previous kernel build until they update OP7 ROM with matching binaries.

Related

[KERNEL][AOSP][AnyKernel][LOS-14.1+EAS] Gamma Kernel for [All Lineage Variants]

{
"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"
}
DESCRIPTION
Hey guys, I have started a custom Kernel based on LineageOS sources with 98% CAF. So I would like to share my own performance and usability improvements with minimal feature and enhancements on top. The intention is to have a minimal light-weight kernel that is very fine tuned for the device.
FEATURES
Minimal Kernel with a stripped defconfig base to be more streamlined and have less memory footprint
User space display color calibration (KCAL) with screen calibrated against iPhone 8 Plus, also helps reducing screen retention
Schedutil governor making use of EAS features with updates from Linux 4.4 and 4.12
Up to date with LineageOS sources for maximum compatibility and security bugfixes
Memory and cache subsystem optimizations, you will feel it
Adaptive LMK enabled by default
Transparent Hugepages are enabled
ZRAM/Swap partition is disabled by default
BFQ IO scheduler set by default to avoid slow-downs on task intensive scenarios
No overclocking was chosen to avoid unnecessary heat, optimizations were focused on other different areas
Kernel Samepage Sharing enabled with deferred timer by default to gain some memory usage optimizations, the process sleeps on regular basis and I've profiled it so that there's no battery drains due to it
Simple temperature controls for msm_thermals exposed
Compiled with GCC 6.x optimized toolchain and -O3 plus other hardware specific flags
Undervolted the Adreno 530 GPU voltage rail to keep things cooler
CAF Rebase on major portions of the Kernel has helped lower the memory footprint a lot
ES9218 Quad DAC automatic toggling working inside the kernel for headphone HIFI playback, please read here for details
DOWNLOADS
AnyKernel: Click Here (Or check top of the post, download tab)
(Optional) LineageOS 14.1 Netflix Black Screen Fix : Click Here
(Optional) Updated Adreno Drivers by @BlackSoulxxx : Click Here
SOURCE
V20-Kernel-Gamma GitHub Source
NOTES
Here is a GeekbenchV4 result example : http://browser.geekbench.com/v4/cpu/7618872
These is intended to be used primarily with LineageOS, I have not tested other ROM's
Since LineageOS uses a way newer Bluetooth stack, this Kernel will most likely not work on old ROM's such as ResurrectionRemix
This will not work with LineageOS 15.1, please see the other thread
KNOWN BUGS
When using v1.0.0 will fail to boot if you had Magisk previously installed. Please install something newer if using Magisk.
When using v13.0.0 - v15.x.x infrared remote control will not work.
I would also like to thanks to various people who contribute tremendously such as:
@x86cpu
@EvilHowl
@USA-RedDragon
@savoca
@albinoman887
@emdroidle
@Rashed97
@joshuous
@RenderBroken
and many others!
<< If you like my work here is my hat, please donate! >>​
​
XDA:DevDB Information
Gamma Kernel, Kernel for the LG V20
Contributors
Omar-Avelar
Source Code: https://github.com/oxavelar/V20-Kernel-Gamma
Kernel Special Features:
Version Information
Status: No Longer Updated
Current Stable Version: 46.0.0
Stable Release Date: 2018-07-11
Created 2017-12-10
Last Updated 2018-10-22
CHANGELOG
46.0.0 - Started msm_irqbalance by default on boot, disabled lp11 and enabled allow mdss phy powerdown during idle screen.
45.0.0 - Smoother memlat ramp and tuned the schedTune DVR cpusets a bit for better performance overall.
44.0.0 - More deep sleep enhancements.
43.0.0 - Update to Oreo TouchScreen firmware and more MDSS PLL merge fixes that help deep sleep.
42.0.0 - Missing MDSS Oreo merges are now in place.
41.0.0 - Added IPA_WS as a default in the wakelock blocker, as well as enabling CONFIG_PM_SLEEP which if missing would in turn cause some ueventd wakeups.
40.0.0 - Disabled CONFIG_RMNET_DATA_DEBUG_PKT. Full fix for USB OTG and added missing slimport drivers. Tweaked the random wakeup values, added some extra cpusets based on Marlin's android-cts-8.0_r8/init.common.rc and fixed some BFQ IO possible hang.
39.0.0 - Disabled CONFIG_RMNET_DATA_DEBUG_PKT. Full fix for USB OTG and added missing slimport drivers.
38.2.0 - Removed LGE's battery manager alarms.
38.1.0 - Fixed potential wireless packet loss.
38.0.0 - Further tweaked the wlan_rx_wake wakelock, migrated the audio and thermal workers to power efficient queues, and added an arm64 prefetching optimization for memcpy.
37.0.0 - Better deep sleep enhancements with the charger infrastructure borrowed from the V30 Kernel Oreo sources.
36.0.0 - Full fix for 6a00000.ssusb wakelocks while keeping fast charging enabled.
34.0.0 - Added boeffla_wl_blocker to tame NETLINK wakelock, this wakelock is caused by IPC between the wireless driver in the Kernel and Android. This was the reason why when on wireless the battery would drain more compared than radio. Also disabled OTG as this keeps the phone from deep-sleeping for now.
33.0.0 - Enabled OTG.
32.0.0 - Fixed a bug from Oreo merge that causes video to go green and crash sometimes. Disabled ZRAM from the compilation rather than AnyKernel patch.
31.0.0 - Merged some V20 Oreo Kernel changes in, as well as some DAC enhancements to prevent popping, better USB PD and QC 2.0/3.0 charging code.
30.0.0 - Oreo Kernel changes in, trying to unify the Kernel to keep support for a little while on 14.1.
29.0.0 - Merged msm idle from Linux 4.4 as well as full EAS 1.4 support from Linux 4.4, reduced the memory subsystem timer ramp values for speedier operation.
27.0.0 - Enabled wifi.supplicant_scan_interval on boot, and disabled IPv4 TCP Timestamps and ICMP responses as well as CCKM fast secure roaming.
26.0.0 - Full EAS 1.4 from Wahoo (Pixel 2XL) backported.
25.0.0 - Updated EAS (schedutil, walt, fair scheduler) to be in sync with Wahoo (Pixel 2XL) latest changes.
24.0.0 - Fixed another performance regression in multi-core scores within schedutil.
23.0.0 - Screen brightness is 50% while booting to reduce heat when it is regenerating cache on boot. v22.1.0 was 25% but this was barely visible if you were rebooting under direct sunlight. So went for the safe value.
22.1.0 - Reduced the screen brightness while booting to reduce the heat of the device during cache wipes.
22.0.0 - WALT and schedutil cpufreq commit fixes backported from RenderBroken.
21.0.0 - The GPU Voltage rail undrervolt is now ~60 mV, do not see any problem and games run way cooler.
20.0.0 - After feedback on frequency utilization/distribution I've put 3 WELT commits that should help alleviate this. And enabled some extra configurations from our wireless driver for better power savings.
19.0.0 - Trimmed around ~40 mV from the GPU voltage rails, and updating the wireless stack to DHD 1.80.13 - 2017.06.22, from us997 V16a.
17.0.0 - Increased the multi-core benchmark scores.
16.1.0 - Reverted the binder to be Nougat only, since Oreo support will be on a separate Kernel anyway. Fixed the Infrared Remote Control support that I had broken, and tuned the memory scaling to be more responsive.
15.0.0 - More audio fixes. This audio CAF merging has fixed the speaker-phone that suddenly stops recording or suddenly stops recieving audio from the phone call in LineageOS. Also have increased the schedutil timer values to be similar to the Pixel 2 XL (Wahoo). And finally have fixed a CONFIG_LGE_PM_LGE_POWER_CLASS_CHARGER_SLEEP problem, so that the charger module now sleeps better and uses less power in idle.
14.0.0 - Updated WALT (Window Assisted Load Tracking) fixes aggregated by RenderBroken. Fixed an audio bug introduced in 13.0.0 where headphone insertion could change the sampling rate of other audio sessions. Changed again the schedutil timer values to favor benchmarks a tiny bit and increased the external SD read-ahead and minimum number of requests so that there is better merging when using slow SD cards while keeping the internal storage device in a low-latency configuration.
13.0.0 - Merged CAF audio upstream changes and enabled transparent hugepages.
12.0.0 - Tuned the memory subsystem frequency scaling parameters further down to focus on batter savings as well as the EAS timers.
11.0.0 - Added cpuidle optimizations to idle more, bumped up the memlatency trigger.
10.2.0 - Reintroduced back QuickCharge 2.0 and QuickCharge 3.0 fast charging support into the Kernel.
10.0.0 - Bumped up the Kernel to version 3.18.71.
9.0.0 - Full arm64 arch CAF update done to the Kernel based on CAF LA.UM.6.5.r1-05300-8x96.0. Added support for H918 variant too.
8.2.0 - Partial update to get the Kernel in a big percent that of CAF LA.UM.6.5.r1-05300-8x96.0, no bugs introduced and using a CAF / LineageOS kernel base. Using the binder interface that works both for Android Oreo and Nougat to be prepared for Lineage15. Also fixed a bug that I had introduced in previous versions related to wireless access point, hence why I had pulled versions 7.x from the server.
4.1.0 - Reintroduced into the LineageOS kernel the partial-update in the panel, to gain some power savings and overall performance feeling when refreshing the panel and screen elements.
4.0.0 - Raised the EAS schedutil timers and the memlat governor threshold to kick in faster. This will bring up the responsiveness to similar levels to HMP even when still using EAS. Brought back KSM after profiling on battery utilization, it doesn't hurt as long as a the timer value is between 4000.
3.0.x - Bugfixes and testing with Magisk compatibility, I think there are no more compatibility problems with Magisk after this, had to remove KSM for testing.
1.0.0 - Initial version, with KCAL, and streamlined defconfig based on cm-14.1 kernel sources and minor commits on top.
Omar-Avelar said:
DESCRIPTION
Hey guys, I have started a custom Kernel based on LineageOS sources to get and share my own performance improvements up and adding minimal feature and enhancements on top. The intention is to have a minimal light-weight kernel that is very fine tuned for the device.
FEATURES
Minimal Kernel with a stripped defconfig base to be more streamlined and have less memory footprint
User space display color calibration (KCAL) with less blue tints by default
Schedutil governor making use of EAS features
Up to date with LineageOS sources for maximum compatibility and security bugfixes
Memory and cache subsystem optimizations, you will feel it
Adaptive LMK enabled by default
ZRAM/Swap partition is disabled by default
BFQ IO scheduler set by default to avoid slow-downs on task intensive scenarios
No overclocking was chosen to avoid unnecessary heat, optimizations were focused on other different areas
Kernel Samepage Sharing enabled with deferred timer by default to gain some memory usage optimizations, the process sleeps on regular basis and I've profiled it so that there's no battery drains due to it
Compiled with GCC 6.x optimized toolchain and -O3 plus other hardware specific flags
Re-introduced stock thermal values and engine for a safer device operation
DOWNLOADS
1) AnyKernel: Click Here (Or check top of the post, download tab)
2) EAS-Project OP3 Prebuilts Flashable : Click Here
3) Thermal Engine Flashable : Click Here
SOURCE
V20-Kernel-Gamma GitHub Source
NOTES
These is intended to be used primarily with LineageOS, I have not tested other ROM's
Please flash all *.zip's mentioned in the download sections for optimal results
KNOWN BUGS
Hopefully none
I would also like to thanks to various people who contribute tremendously such as:
@x86cpu
@EvilHowl
@USA-RedDragon
@savoca
@albinoman887
@emdroidle
@Rashed97
and many others!
<< If you like my work here is my hat, please donate! >>
​
XDA:DevDB Information
Gamma Kernel, Kernel for the LG V20
Contributors
Omar-Avelar
Source Code:https://github.com/oxavelar/V20-Kernel-Gamma
Kernel Special Features:
Version Information
Status: Testing
Current Stable Version: 1.0
Stable Release Date: 2017-12-09
Created 2017-12-10
Last Updated 2017-12-09
Click to expand...
Click to collapse
I don't know how 'in-depth' testing I can do. But I'll be willing to do what I can!
I'll be flashing this soon.
I'm on Desolation ROM, VS995. I'll report back. Thanks for your hard work!
Edit: not necessarily a problem, but it has static on boot.
nightra88 said:
I don't know how 'in-depth' testing I can do. But I'll be willing to do what I can!
I'll be flashing this soon.
I'm on Desolation ROM, VS995. I'll report back. Thanks for your hard work!
Edit: not necessarily a problem, but it has static on boot.
Click to expand...
Click to collapse
Oh, I didn't compile specifically for VS995 so it will have static on boot. Since these two are mostly the same devices I might give u a VS995 Kernel next week with that static gone.
Here are some Geekbench results in case anyone is interested : http://browser.geekbench.com/v4/cpu/5506983
Great to have someone finally building an AOSP kernel!
Any chance you'll be compiling for the H918 sometime in the future? No worries if you aren't. I'm just curious =p
Omar-Avelar said:
Oh, I didn't compile specifically for VS995 so it will have static on boot. Since these two are mostly the same devices I might give u a VS995 Kernel next week with that static gone.
Click to expand...
Click to collapse
That sounds great! I'll look forward to it! But I'm about 12-14hrs in the kernel now, and so far so good! With normal usage.
Have updated Kernel to 1.1.0 version with two minor changes that improve the performance by quite a big. Figured out the OP3 and the Marlin Kernel was using 300 Hz tick timers. But for some reason our Kernel was only using 100 Hz tick's. So two changes in this version.
1. Enable high-res timers for schedulercks
2. arm64: hz: make it configurable
Click to expand...
Click to collapse
Plus I have decided to go on and change the perfd binary again. I was not aware how much of impact this has to EAS and the fluidity, since with EAS the input freq boost in the Kernel is now gone. You can read more about it here : https://github.com/EAS-Project/android_device_voxpopuli in the README.md. I am not yet using 100% of the capabilities of Vox Populi Power HAL but a lot of features from it turned off for now.
NippleSauce said:
Great to have someone finally building an AOSP kernel!
Any chance you'll be compiling for the H918 sometime in the future? No worries if you aren't. I'm just curious =p
Click to expand...
Click to collapse
Most likely yes, but after I polish a few features and once I am 100% happy with the performance
Hmm... Oddly enough if I install I get stuck into a boot loop. Not even a LineageOS boot animation. I am and will continue to use Magisk, even flashed all 3.
x86cpu said:
Hmm... Oddly enough if I install I get stuck into a boot loop. Not even a LineageOS boot animation. I am and will continue to use Magisk, even flashed all 3.
Click to expand...
Click to collapse
Oh shoot... I haven't tested it with Magisk on top myself, I wonder if I removed some thing in the defconfig that Magisk needs... Mmmm, both versions give u that same outcome ? Thx for the report!
Omar-Avelar said:
Oh shoot... I haven't tested it with Magisk on top myself, I wonder if I removed some thing in the defconfig that Magisk needs... Mmmm, both versions give u that same outcome ? Thx for the report!
Click to expand...
Click to collapse
I only tried the latest one. I did not try without Magisk though or the older version, the all 3 reference was all 3 files you had. gamma/vox/thermal.
I noticed in your thermal, that the camera files are the same as Lineage, so you could take those out. I also took out the mixer one as I bumped those VOL up as it was hard to hear on calls without it. If you do find any adjustments that the op3 or marlin did, we might be able to get those into the Lineage msm8996 kernel. Ideally, the commits from op3 in the Lineage tree, then I can cherry pick it to preserve history. I'm all for getting things into Lineage where we can.
Omar-Avelar said:
Oh shoot... I haven't tested it with Magisk on top myself, I wonder if I removed some thing in the defconfig that Magisk needs... Mmmm, both versions give u that same outcome ? Thx for the report!
Click to expand...
Click to collapse
I flashed with Magisk, on the first version, and everything is going fine for me
nightra88 said:
I flashed with Magisk, on the first version, and everything is going fine for me
Click to expand...
Click to collapse
Thanks man, let me re-upload the 2nd version just in case then and will verify the MD5 hash...
Omar-Avelar said:
Thanks man, let me re-upload the 2nd version just in case then and will verify the MD5 hash...
Click to expand...
Click to collapse
No problem! Glad to help.
x86cpu said:
Hmm... Oddly enough if I install I get stuck into a boot loop. Not even a LineageOS boot animation. I am and will continue to use Magisk, even flashed all 3.
Click to expand...
Click to collapse
So I got home to try just in case @x86cpu and I was able to flash Magisk-v14.5(1456).zip after all of the 3 files had been flashed on my system and it booted fine.... so I've re-uploaded the Kernel as v1.1.1 in the downloads section just in case...
Wiped /system (as I had su from LineageOS flashed before)
Flashed system with lineage-us996-*.zip
Flashed OpenGapps
Flashed perfd update (2nd of my zips)
Flashed the 'hotfixes' (3rd of my zips)
Flashed gamma-kernel (1st zip)
Flashed Magisk-v14.5(1456).zip
Hit reboot
If you can let me know if the v1.1.1 version works on your side then I can blame the bad upload. If not I can do more experiments to see if there is some other condition that depends on the order of flashing with my AnyKernel approach... and then I can try and replicate and fix it , please do let me know...
UPDATE: I am able to hit the failure now @x86cpu... let me see if AnyKernel needs any update or something to allow to re-install the Kernel if Magisk is already pre-installed. In order to hit it I had to:
Wiped /system (as I had su from LineageOS flashed before)
Flashed system with lineage-us996-*.zip
Flashed OpenGapps
Flashed perfd update (2nd of my zips)
Flashed the 'hotfixes' (3rd of my zips)
Flashed Magisk-v14.5(1456).zip
Flashed gamma-kernel (1st zip)
Hit reboot
Essentially flashing the Kernel last... which might be a common thing that could happen, let me polish that up...
I've uploaded flashable-us996-gamma-kernel-v1.2.0.zip now with an updated AnyKernel script that seems to now be working even with Magisk installed previously. Thanks to @x86cpu for reporting this bug.
U
Omar-Avelar said:
So I got home to try just in case @x86cpu and I was able to flash Magisk-v14.5(1456).zip after all of the 3 files had been flashed on my system and it booted fine.... so I've re-uploaded the Kernel as v1.1.1 in the downloads section just in case...
Wiped /system (as I had su from LineageOS flashed before)
Flashed OpenGapps
Flashed the 'hotfixes' (3rd of my zips)
Flashed Magisk-v14.5(1456).zip
Wiped /system (as I had su from LineageOS flashed before)
Flashed OpenGapps
Flashed the 'hotfixes' (3rd of my zips)
Flashed gamma-kernel (1st zip)
Hit reboot
Essentially flashing the Kernel last... which might be a common thing that could happen, let me polish that up...
Click to expand...
Click to collapse
I just installed the v1.1.1 before the fix. So. In other words before I saw this update, I just flashed it with no wiping, Desolation rom, and it booted fine, it's just now, in Magisk I can't pass cts or basic integrity. I'll try your updated method and see if that fixes the problem.
Edit: did the above steps, minus wiping twice and flashing the hot fixes twice. Rebooted it. And now I can successfully pass safetynet on the latest gamma kernel!
Edit#2: false hope, my apologies, safetynet apparently isn't passed.
Edit#3: okay. I had a blonde moment. I forgot to wipe my dalvik. It passes now.
What do the HAL's do? And what order should I flash the zips?
Obamaloominaty said:
What do the HAL's do? And what order should I flash the zips?
Click to expand...
Click to collapse
The order doesn't matter as they are independent. And I would suggest you read about the EAS perfd HAL in here : README.md
However keep in mind that I haven't implemented all of the VoxPopuli features from the HAL in the AnyKernel as it needs some SELInux permissions updates (which I can do later on). But without all of those enhancements it will behave like the Pixel HAL.

KERNEL❯ LLVM 7 ❯ TREBLE ❯❯ AceKernel • v2.01 • Sept 15

KERNEL❯ LLVM 7 ❯ TREBLE ❯❯ AceKernel • v2.01 • Sept 15
{
"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"
}
THIS KERNEL IS FOR​TREBLE & NO-TREBLE​
Introduction
Hello everyone, I'm Martin and I've been working on Potter for 1 year right now.
I'm constantly trying to improve this device with some change that some developers don't like.
For me EAS is the future of android kernel, that's why I'm already bringing it to you!
I will always follow these three rules:
Follow upstream Linux always
Features will be added only as needed
Security and stability are paramount
I hope you'll all agree with these three rules
Thread Rules
I refuse to acknowledge/respond to bug reports that do not include clear steps to reproduce, a logcat or a dmesg. (Follow this guide)
Stay classy, I won't tolerate flaming of any kind, ever.
OT is allowed.
Features
Here are the major features of the kernel (feel free to explore Github)
Up to date with the latest stable Linux version (3.18.119)
Patches from Code Aurora Forum targeting GPU, touchscreen/video, storage, and sound
Mainline Linux patches for CFQ and media memory allocation
F2FS driver updated
VDSO32 built in
Latest energy aware scheduling patches ported to 3.18 (check EAS)
Converted some workqueues to use power efficient workqueues
Wake up improvements and other optimization from Sultanxda
Rewrited the fingerprint sensor driver (fpc1020_tee)
The following user features:
Faux Sound Control with high-performance audio
Westwood (default)
Maple I/O scheduler
Wakelock control
Lastest WireGuard snapshot
Build with official Clang toolchains 7.0 (clang-4679922).
Hides bootloader unlock from SafetyNet (can still fail through other means)
Flashed with AnyKernel2 (thanks to @osm0sis)
Downloads
Lastest version is the v2.01 (AceKernel-Potter-v2.01_eas_unified.zip)
Eas-Unifiedhttps://download.martichou.me/Potter/
Only small issue is fingerprint gestures broken on Treble rom with this version. I'm working on how to solve this issue.
Old versions: https://download.martichou.me/Potter/Old/
Do not mirror my kernels and don't share the direct link!
Installation
If you are on a custom ROM:
Either dirty flash your ROM or flash the stock boot image. (not mandatory)
Install or temporarily boot into TWRP (follow their instructions)
Reboot to TWRP
Flash the zip.
Reboot and profit!
If you are on a GSI/Treble ROM:
Either dirty flash your GSI image or flash the stock boot image. (not mandatory)
Install or temporarily boot into TWRP (follow their instructions)
Reboot to TWRP
Flash the zip.
Reboot and profit!
Upgrading from one Flash version to the other:
Boot into TWRP
Flash the zip.
Reboot and profit!
Changelog
Complet changelog here:
https://github.com/Martichou/potter/
Thanks to:
@vache for his incredible work on Potter
@joshuous for his work on EAS
@osm0sis for AnyKernel2
The various other developers for their patches (@flar2, @franciscofranco, @frap129, @nathanchance, ..)
All of you guys for viewing the thread
DONATION:
If you want to buy me a beer :good:
Yeah, I'm Belgian, and I love that! http://paypal.me/martichou
TELEGRAM:
There is also an Official Telegram group, for support and to speak directly with me.
https://t.me/joinchat/EWMwLkNn0rKRA-jPluo85w
Website
I've made my personal website. (Hosted at OVH, should be fast for everyone)
It means, I'm gonna upload all zip on it and it also mean that you can take a look at the website
Website: https://martichou.me
DISCLAIMER:
I openly welcome off topic in my threads. Mods, please do not clean off-topic discussion and users, do not complain about off-topic discussion here. I may direct you to another thread if it is so suited but I won't have the discussion cleaned. Thank you.
XDA:DevDB Information
AceKernel, Kernel for the Moto G5 Plus
Contributors
Martichou
Source Code: https://github.com/Martichou/potter
Kernel Special Features:
Version Information
Status: Stable
Created 2018-06-08
Last Updated 2018-09-15
Reserved
Thank you señor
Best kernel overall! (for me). Thanks Martichou!
which non treble rom can I use??
https://potterroms.me/du-mod/
can I use this??
I tried it on cr-droid 01/06, camera stops, so which roms have the latest commits??
Can u please suggest one? Or is it in development??
rishivg said:
which non treble rom can I use??
https://potterroms.me/du-mod/
can I use this??
I tried it on cr-droid 01/06, camera stops, so which roms have the latest commits??
Can u please suggest one? Or is it in development??
Click to expand...
Click to collapse
Basically, all ROM built after the 7th June.
Check on potterroms which were built after this date.
I can't say at 100% that all ROM built after the 7 June is compatible cause it's up to the ROM maintainer to either update his tree or not. So it's better to ask directly to the one who maintains the ROM you gonna use.
Martichou said:
Basically, all ROM built after the 7th June.
Check on potterroms which were built after this date.
I can't say at 100% that all ROM built after the 7 June is compatible cause it's up to the ROM maintainer to either update his tree or not. So it's better to ask directly to the one who maintains the ROM you gonna use.
Click to expand...
Click to collapse
Tried all of them after 7th June... none of them supported this...
rishivg said:
Tried all of them after 7th June... none of them supported this...
Click to expand...
Click to collapse
Try the 8 June Pixelexperience build.
There is also the lastest LOS15.1 from Vache.
As I said, maintainer will have to update their own tree.
Basically it's just a 2-3 days gaps.
As of now, supported roms are PE, LOS, and Firehound
This Kernel works great. The UI runs smooth and my batteries life got up to ~15%.
I want to change the GPU Governor, because I do not need the performance from msm_adreno_tz. This info about adreno I was able to find on xda, but for the other GPU Governors in this kernel I couldn't. Can somebody recommend a GPU Governor for batterie life or balance?
Also, what are the effects of "audio high performance mode"?
ichmyselfandi said:
This Kernel works great. The UI runs smooth and my batteries life got up to ~15%.
I want to change the GPU Governor, because I do not need the performance from msm_adreno_tz. This info about adreno I was able to find on xda, but for the other GPU Governors in this kernel I couldn't. Can somebody recommend a GPU Governor for batterie life or balance?
Also, what are the effects of "audio high performance mode"?
Click to expand...
Click to collapse
I don't recommend you to change the GPU governor. GPU don't take that much battery, and adreno_tz is already pretty great.
On GPU side, you can however change the GPU initial frequency to 133MHz if you want.
If you really want to change GPU governor (even if I don't recommend that at all), you can use simple_ondemand.
And about the Audio High performance mode:
Every phone powered by a Qualcomm processor has a built-in WCD9xx Audio DAC,
but it's rarely configured to be used to its full potential by OEMs.
This might not seem like a problem to some people, but if you're a music lover,
or you simply enjoy high-quality sound, it's an issue you'll definitely want to fix.
By enabling High-Performance Mode, the audio quality of Qualcomm-powered devices
will not only receive a boost in volume but will sound more clear and crisp as well.
- from android.gadgethacks.com
Click to expand...
Click to collapse
Is this kernel compatible with LiquidRemix?
jesus693 said:
Is this kernel compatible with LiquidRemix?
Click to expand...
Click to collapse
If the rom has been merged with june updates, then yes. Otherwise camera won't work.
.... i feel like people are going to yell at me but what is treble? i thought it was all about that bass
Ae3NerdGod said:
.... i feel like people are going to yell at me but what is treble? i thought it was all about that bass
Click to expand...
Click to collapse
No worries. Treble is an initiative by Google that forces OEMs to separate their devices' driver code from the code that powers Android itself. There's a more detailed Android Authority piece that explains it in detail here.
Martichou said:
THIS KERNEL IS FOR​TREBLE & NO-TREBLE​
Introduction
Hello everyone, I'm Martin and I've been working on Potter for 1 year right now.
I'm constantly trying to improve this device with some change that some developers don't like.
For me EAS is the future of android kernel, that's why I'm already bringing it to you!
I will always follow these three rules:
Follow upstream Linux always
Features will be added only as needed
Security and stability are paramount
I hope you'll all agree with these three rules
Thread Rules
I refuse to acknowledge/respond to bug reports that do not include clear steps to reproduce, a logcat or a dmesg. (Follow this guide)
Stay classy, I won't tolerate flaming of any kind, ever.
OT is allowed.
Features
Here are the major features of the kernel (feel free to explore Github)
Up to date with the latest stable Linux version (3.18.112)
Patches from Code Aurora Forum targeting GPU, touchscreen/video, storage, and sound
Mainline Linux patches for CFQ and media memory allocation
Latest energy aware scheduling patches ported to 3.18 (check EAS)
Converted some workqueues to use power efficient workqueues
Wake up improvements and other optimization from Sultanxda
Rewrited the fingerprint sensor driver (fpc1020_tee)
The following user features:
Faux Sound Control with high-performance audio
Westwood (default)
Maple I/O scheduler
Wakelock control
Lastest WireGuard snapshot
Build with official Clang toolchains 7.0 (clang-4679922).
Hides bootloader unlock from SafetyNet (can still fail through other means)
Flashed with AnyKernel2 (thanks to @osm0sis)
Downloads
Treble : AceKernel-Potter-v1.10_eas_treble
No-Treble : AceKernel-Potter-v1.10_eas_no-treble
For no-treble, the ROM need to be updated with lastest blobs from boulzordev GitHub organization.
Do not mirror my kernels and don't share the direct link!
Installation
If you are on a custom ROM:
Either dirty flash your ROM or flash the stock boot image. (not mandatory)
Install or temporarily boot into TWRP (follow their instructions)
Reboot to TWRP
Flash the zip.
Reboot and profit!
If you are on a GSI/Treble ROM:
Either dirty flash your GSI image or flash the stock boot image. (not mandatory)
Install or temporarily boot into TWRP (follow their instructions)
Reboot to TWRP
Flash the zip.
Reboot and profit!
Upgrading from one Flash version to the other:
Boot into TWRP
Flash the zip.
Reboot and profit!
Changelog
Complet changelog here:
For TREBLE variant use the eas_treble branch.
For NO-TREBLE variant, use the eas_no-treble branch.
https://github.com/Martichou/potter/commits/eas_treble
Thanks to:
@vache for his incredible work on Potter
@joshuous for his work on EAS
@osm0sis for AnyKernel2
The various other developers for their patches (@flar2, @franciscofranco, @frap129, @nathanchance, ..)
All of you guys for viewing the thread
DONATION:
If you want to buy me a beer :good:
Yeah, I'm Belgian, and I love that! http://paypal.me/martichou
TELEGRAM:
There is also an Official Telegram group, for support and to speak directly with me.
https://t.me/joinchat/EWMwLkNn0rKRA-jPluo85w
FOR DEVELOPER:
If you want to inline this kernel into your rom, you'll need a change in init.qcom.rc.
I also made this commit to make your life easier. Feel free to pick it [Treble & No-treble branch (depends on what you're building)]
https://github.com/Martichou/android_device_motorola_potter/commit/654854f3bc695a7cfbcc5ff11d7d3943b67869af
DISCLAIMER:
I openly welcome off topic in my threads. Mods, please do not clean off-topic discussion and users, do not complain about off-topic discussion here. I may direct you to another thread if it is so suited but I won't have the discussion cleaned. Thank you.
XDA:DevDB Information
AceKernel, Kernel for the Moto G5 Plus
Contributors
Martichou
Source Code: https://github.com/Martichou/potter
Kernel Special Features:
Version Information
Status: Stable
Created 2018-06-08
Last Updated 2018-06-11
Click to expand...
Click to collapse
Great kernel ??? thank you
monster1612 said:
No worries. Treble is an initiative by Google that forces OEMs to separate their devices' driver code from the code that powers Android itself. There's a more detailed Android Authority piece that explains it in detail here.
Click to expand...
Click to collapse
That is brilliant.
Does this mean our phones compass works on Oreo now? I read somewhere it was because of an issue with not having the 64bit drivers for it. Makes gps apps unusable for me and is basically while I'm still on nougat
hello I want to install the ROM but there is 2 treble version and no treble and I do not know which one to install. I have the latest version of RR-O-v6.0-20180608-potter-official
I already installed it I tried with the non-treble everything works fine even the camera, I'm realizing that I do not have much RAM available less than 400mb in the stock ROM of RR I had always more than 600 now the games are closed only after 5 minutes of opening them by little ram: '(
jesus693 said:
I already installed it I tried with the non-treble everything works fine even the camera, I'm realizing that I do not have much RAM available less than 400mb in the stock ROM of RR I had always more than 600 now the games are closed only after 5 minutes of opening them by little ram: '(
Click to expand...
Click to collapse
You can enable Zram in Kernel Auditor or Exkm or any kernel tweakers.
Enabling Zram should fix your issue.
By the way, I want to say that free ram is wasted ram. The ram need to be full the most of the time. (As far as I know and what others dev said).

[KERNEL][8.1]Reviver Kernel [18 Aug 2019][r3.0]

{
"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"
}
NOTE:
Hello everyone, this is my kernel for the Moto G5S. I will try to maintain a stable kernel however bugs might arise since I'm not a super star kernel developer. I hope you enjoy the releases. You are making modifications to your device at your own risk. Support is community based only.
Important information
I will not reply to complains that do not include clear steps to reproduce the bug, a logcat, and ramoops (if random rebooting) or a dmesg (any other issues). Follow this guide to do this.
Features
Compiled with Latest GCC 4.9.4 Linaro Toolchain
DCache Word Access
Disable CRC Check
Disable Gentle Fair Sleepers
LZ4 is the default compressor
CFQ as default I/O scheduler
TCP Congestion Avoidance Protocols
Downloads
SourceForge
Installation:
NOTE: Please make sure that you return to the stock kernel of the ROM before flashing this kernel. The kernel is only for Moto G5S codenamed montana .
Reboot to TWRP.
Backup boot.
Flash the zip.
Reboot to system.
Changelog
18 Aug 2019
Code:
Update for MMI-OPPS28.65-37-7-2
29 Oct 2018
Code:
Initial Release
FAQs
1.1 Q Can you help me I have this problem?
1.1 A I will surely try to help if proper bug reporting is done as per the fashion described above.
1.2 Q: Can you add xyz feature?
1.2 A: If you link me the commits or tell me what kernel you had the feature in, I can take a look at them. I will not add any useless governors or features that I don't find practical.
1.3 Q: How do I control the kernel?
1.3 A: I recommend using EX Kernel Manager or Kernel Auditor (Both need root)
1.4 Q: OMFG MY BATTERY SUXXXX PLS FIX!!!
1.4 A: The kernel doesn't drain any battery unless you have overclocked it, I have kept it at stock frequencies and voltages. Use an app like BetterBatteryStats to figure out what app is screwing with your phone.
Thanks to:
Fellow Linux Kernel Developers for their patches (if you want a specific mention, please let me know)
AOSP
Motorola Mobility LLC
CAF
@Kamin4ri for his help
TeamReviver:
@lCrD512
@smog2699
@Titan068
@Katzzero
Others:
Alan Max
Source Code:
https://github.com/rajatgupta1998/android_kernel_motorola_msm8937
https://github.com/rajatgupta1998/AnyKernel2
XDA:DevDB Information
Reviver Kernel Montana, Kernel for the Moto G5S
Contributors
rajatgupta1998
Source Code: https://github.com/rajatgupta1998
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: 3.0
Stable Release Date: 2019-08-18
Created 2018-10-29
Last Updated 2019-08-18
Reserved
Screenshots:
Reserved
Changelog:
Intial Build
great job
Kernel installed this morning and no problem, I'll be back in a few days
@rajatgupta1998 do you think it'd be possible to make Oreo kernel support the same aftermarket panels as Nougat kernel did? It's only touchscreen that is not working. What kind of info could we provide to help to debug this? It would be insanely helpful for all of us with bricked phones
My unit has display burn in issues .. the only fix is to turn down the rgb values with manual display calibration options available on Los based roms. Can i use use the stock oreo rom on top of your kernel and achieve the same ?
Thanks! Does it have an TTL editing function? (line TTL in /proc/net/ip_tables_targets)
vmax0770 said:
@rajatgupta1998 do you think it'd be possible to make Oreo kernel support the same aftermarket panels as Nougat kernel did? It's only touchscreen that is not working. What kind of info could we provide to help to debug this? It would be insanely helpful for all of us with bricked phones
Click to expand...
Click to collapse
Great question. If it's a kernel related. @rajatgupta1998 can you find something about touchscreen chip restriction in Original Lenovorola kernel?
lohanbarth said:
great job
Kernel installed this morning and no problem, I'll be back in a few days
Click to expand...
Click to collapse
Amy input sir?
My unit has display burn in issues .. the only fix is to turn down the rgb values with manual display calibration options available on Los based roms. Can i use use the stock oreo rom on top of your kernel and achieve the same ?
THE USER said:
My unit has display burn in issues .. the only fix is to turn down the rgb values with manual display calibration options available on Los based roms. Can i use use the stock oreo rom on top of your kernel and achieve the same ?
Click to expand...
Click to collapse
no
Jemec26 said:
Amy input sir?
Click to expand...
Click to collapse
no problem works perfectly
I need testers for the kernel since I personally don't own the device. All those who are interested, kindly join my testers group on Telegram. https://t.me/montana_reviver . Also I am willing to continue LineageOS and atleast attempt at Oreo bringup for the device, so I will need testers. Thanks :fingers-crossed:
rajatgupta1998 said:
I need testers for the kernel since I personally don't own the device. All those who are interested, kindly join my testers group on Telegram. https://t.me/montana_reviver . Also I am willing to continue LineageOS and atleast attempt at Oreo bringup for the device, so I will need testers. Thanks :fingers-crossed:
Click to expand...
Click to collapse
Nice
New build is up!
File: reviver_kernel_montana_stock_oreo-2.0.zip
Build Date: 13 January 2019
Changelog:
Update kernel source, f2fs and wifi driver from Motorola's OPPS28.65-37-2 Release
Start merging CAF Tags from where Moto dropped: May 2018 (Completed till June '18 right now, more to come) so that we stay up to date with Qualcomm's release for MSM8953 (Snapdragon 625) chipset. Our CPU MSM8937 can be thought of a low powered version of the 625 so they share a lot of code.
Show correct GPU Frequency in sysfs
Silence WLAN, PCIe, and CPU suspend state kernel messages. These are pretty useless.
Add support for Himax Touchscreen Panel
Remove CPU Boost functionality from Interactive CPU Frequency Governor
Minor changes to MDSS (Display) and Camera drivers.
Downloads:
Latest Build: reviver_kernel_montana_stock_oreo-2.0.zip
MD5: 90ad3d7121ba3525fa7605312a89cf28
SHA1: 965cfffd0b0909ee3d41e841519ef90e30c8ae0f
Proposed upcoming features in future releases (No promises)
1. A custom wakelock blocking driver by @ Lord Boeffla
2. KCAL Display Colour Control driver by savoca.
3. More stuff from Qualcomm
Soon we'll start seeing a custom kernel for 64 bit oreo custom roms since GoldenEye has already released a few initial builds of LineageOS 15.1
:fingers-crossed:
rajatgupta1998 said:
New build is up!
File: reviver_kernel_montana_stock_oreo-2.0.zip
Build Date: 13 January 2019
Changelog:
Update kernel source, f2fs and wifi driver from Motorola's OPPS28.65-37-2 Release
Start merging CAF Tags from where Moto dropped: May 2018 (Completed till June '18 right now, more to come) so that we stay up to date with Qualcomm's release for MSM8953 (Snapdragon 625) chipset. Our CPU MSM8937 can be thought of a low powered version of the 625 so they share a lot of code.
Show correct GPU Frequency in sysfs
Silence WLAN, PCIe, and CPU suspend state kernel messages. These are pretty useless.
Add support for Himax Touchscreen Panel
Remove CPU Boost functionality from Interactive CPU Frequency Governor
Minor changes to MDSS (Display) and Camera drivers.
Downloads:
Latest Build: reviver_kernel_montana_stock_oreo-2.0.zip
MD5: 90ad3d7121ba3525fa7605312a89cf28
SHA1: 965cfffd0b0909ee3d41e841519ef90e30c8ae0f
Proposed upcoming features in future releases (No promises)
1. A custom wakelock blocking driver by @ Lord Boeffla
2. KCAL Display Colour Control driver by savoca.
3. More stuff from Qualcomm
Soon we'll start seeing a custom kernel for 64 bit oreo custom roms since GoldenEye has already released a few initial builds of LineageOS 15.1
:fingers-crossed:
Click to expand...
Click to collapse
Great news!
Would love to see your kernel for LOS 15.1 and could test it also.
Custom panel support
Do you think it'll be possible to also support Tianma panels in this kernel? They were supported in Nougat and I managed to get a working Oreo version by replacing whole drivers/touchscreen folder and building my own
montana_n:/ $ cat /sys/class/graphics/fb0/panel_name
mipi_mot_video_tianma_1080p_521
montana_n:/ $ cat /sys/class/graphics/fb0/panel_supplier
tianma
Click to expand...
Click to collapse
vmax0770 said:
...They were supported in Nougat and I managed to get a working Oreo version by replacing whole drivers/touchscreen folder and building my own
Click to expand...
Click to collapse
Could you share it? I've got tianma panel too.
@Cyr4x here you go http://s000.tinyupload.com/index.php?file_id=47365433013478436702
You should flash it on top of stock ROM via TWRP recovery
Thanks, it's working now.

[KERNEL] [blu_spark r106 OP7/Pro] [OOS /Custom A10]

{
"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"
}
Kernel features:
Build with custom toolchain blu_gcc-10.1 (cortex-a76.cortex-a55 targeted, build from gcc-10.1.0 snapshot with latest bleeding edge components)
Full -O2 build with device and target flags enhanced, linaro build improvements, etc
Less is more: stockish OP7 builds based on OnePlusOSS/android_kernel_oneplus_sm8150 for max stability
Systemless installer (doesn't touch system partition, OTA friendly), AnyKernel3 backend (compatible with autoflash apps)
Removed some debug and logging options
ARM enhanced performance and battery patches
CVE security patches, general upstream and CAF fixes for important subsystems
Several CPU Governors (blu_schedutil modded governor merged from latest CAF sm8150 patchset)
No OC, use 300HZ base timer frequency
msm_performance touchboost toggle on/off (enabled by default), tweaked cpu_boost driver
Enhanced TCP methods (westwood is default), Network tweaks and updated drivers
Several I/O control tweaks, added schedulers ZEN v2 is default, advanced filesystems enabled (F2FS, ExFAT, NTFS, CIFS & NFS)
Patched SafetyNet flags to pass CTS
Stock thermal driver by default
ZRAM Swap (LZ4) and with file disabled
Vibrator Strength tunable and Gesture Haptic Feedback control (touchpanel and FPR)
KGSL fixes and reworked GPU driver
adrenoboost enabled by default at low level
KCAL - Advanced color control for Qualcomm MDSS v2 (RGB calibration and post-processing features)
KLAPSE support (v5.0)
Backlight min brightness option
Gamepad support enabled (xbox, ps4, switch)
USB Fast Charge (USB mode up to 900mA with MTP on)
FS fsync toggle on/off
Wakelock blockers available
wireguard support
CDROM emulation on mass_storage (compatible with DriveDroid 0.10.36+)
Compatible with Kernel Adiutor, EXKM, FKM and others
DOWNLOAD KERNEL ZIP​FKM download configs: oos | custom​(No mirrors please)​
Warning: If you come from other kernel or have any issues, you should dirty flash your ROM before flashing blu_spark zip to avoid problems.
Reflash ROM -> flash TWRP --> reboot to recovery --> flash Magisk if you want (default, no plugins/modules) -> flash blu_spark.
If you are already rooted or upgrading between blu_spark versions, just flash the kernel zip. Also uninstall or clean data of any kernel control app you're using.
About bugs and troubleshoots: don't bother to post if a log isn't ready or without steps so the behavior can be replicated. I only active support stock OOS with NO mods whatsoever (apart from root). That includes NO support if using xposed, Magisk with modules, etc.
If you're using custom ROMs (including OOS based ones) or Open Betas you're on your own. I'm only interested on debugging stuff in stock and stable OOS.
Save the SOT and battery stats/screenshots for general threads, here we deal with development, not personal tastes and results.
Also don't spam this thread with CM or other ROMs stuff like "this don't work, my app doesn't open, etc" , no OT about OTAs, apps, ROM bugs, Recovery/TWRP troubleshoots and other userspace stuff. There's threads for it, use them.
Going back to stock: This kernel installer doesn't change your filesystem. You can backup your boot.img with TWRP before flashing blu_spark if you want to go back to full stock or just dirty flash your full ROM.
If you like my work, donations are always welcome.
Don't forget to hit thanks and rate the thread nicely, it's free
OnePlus 7 Pro development unit donated by OnePlus. Big shouts to them
Very proud of being on the OnePlus Developer Program, special thanks to Manu J. for being such a supportive person.
XDA:DevDB Information
blu_spark kernel for OnePlus 7/Pro, Kernel for the OnePlus 7 Pro
Contributors
eng.stk
Source Code: https://github.com/engstk/op7
Kernel Special Features: Powered by sparky
Version Information
Status: Stable
Current Stable Version: r106 unified
Stable Release Date: 2020-06-27
Current Beta Version: r67 unified
Beta Release Date: 2019-12-16
Created 2019-06-30
Last Updated 2020-07-02
blu_spark r7 release (unified)
All right crew!
First build is up :highfive:
OnePlus sent my 7 Pro developer unit yesterday (in all blu glory), today the fist victim is out ;p
This kernel is unified, should be good on OP7/Pro (I only can test on Pro).
blu_spark_r7 release
Synchronize codes for Oneplus 7 Pro Oxygen OS 9.5.8.GM21AA
Build with latest blu_gcc-9.1.0
Lot's of the usual goodies, too much stuff to changelog it (I would say we're at 50%, check git for details)
AnyKernel3 updates
Click to expand...
Click to collapse
Keep in mind: I will give no active support for custom ROMs (including OOS based ones).
I am only interested on debugging stuff in stock and stable OOS (with logs and reproducible steps to replicate the issue).
Don't spam this thread with LOS or other ROMs stuff like "this don't work, my app doesn't open, etc" or debugging features.
Also don't go spam and bug reporting on ROM threads if using this.
No mirrors please
If you like my work, donations are always welcome.
Don't forget to hit thanks and rate the thread nicely, it's free
Thanks and good to see you here, too!
Hell yeah... Nice to see u here!
Good to see you here man. I have used some of your kernels over the years. Will try this out.
@eng.stk do you also plan to provide your famous blu_spark_twrp?
Have you read of the sleep of death/deadlock issues on this device? If so, do you have any ideas for the source of the issue?
THIS!!!!!!! This is what I've been waiting for. Thank you @eng.stk. Couldn't be happier right now.
Welcome to the OnePlus 7 Pro scene mate.
eng.stk said:
All right crew!
First build is up :highfive:
OnePlus sent my 7 Pro developer unit yesterday (in all blu glory), today the fist victim is out ;p
This kernel is unified, should be good on OP7/Pro (I only can test on Pro).
blu_spark_r7 release
Keep in mind: I will give no active support for custom ROMs (including OOS based ones).
I am only interested on debugging stuff in stock and stable OOS (with logs and reproducible steps to replicate the issue).
Don't spam this thread with LOS or other ROMs stuff like "this don't work, my app doesn't open, etc" or debugging features.
Also don't go spam and bug reporting on ROM threads if using this.
No mirrors please
If you like my work, donations are always welcome.
Don't forget to hit thanks and rate the thread nicely, it's free
Click to expand...
Click to collapse
Hi,
Can I use this Kernel on my OnePlus 7.
pushpendrayadav said:
Hi,
Can I use this Kernel on my OnePlus 7.
Click to expand...
Click to collapse
Yes,it's unified
Gesendet von meinem GM1913 mit Tapatalk
Anyone flash this yet and not see any blu_shedutil cpu governer?
Edit: Also anyone seeing KCAL? And or KLAPSE? no where to be found on EXKM, maybe I need to flash it twice? Anyone's guess is as good as mine
MarcoG: said:
Yes,it's unified
Gesendet von meinem GM1913 mit Tapatalk
Click to expand...
Click to collapse
Thanks
TacoTuco said:
Anyone flash this yet and not see any blu_shedutil cpu governer?
Edit: Also anyone seeing KCAL? And or KLAPSE? no where to be found on EXKM, maybe I need to flash it twice? Anyone's guess is as good as mine
Click to expand...
Click to collapse
For me to, no blu_shedutil cpu governer
Gesendet von meinem GM1913 mit Tapatalk
@eng.stk
Hi. We were waiting for you and your work at this forum section. Thank you for providing support for allmost all oneplus line, used your kernel and twrp for more than 2 years.
CAF introduced 675 max gpu freq support for sm8150. Will you allow us to use it, but setting 585 as defualt? Less is more, i'm agree with you.
About deadlocks, someone calls it sleep of death, there is such problem. i faced it myself many times. As far as i can say, its faulty units problem. Replaced my unit and so far no deadlocks for 2 days already. With previous one i had it once in 3-6 hours.
@eng.stk
Nice to see you here. Only now I can buy OP7 PRO and retire my OP6.
Thank you for your time and effort.
Nice to see you here, finally! Flashing.....
ulxerker said:
Thanks and good to see you here, too!
Click to expand...
Click to collapse
Bradl79 said:
Hell yeah... Nice to see u here!
Click to expand...
Click to collapse
mauley said:
Good to see you here man. I have used some of your kernels over the years. Will try this out.
Click to expand...
Click to collapse
trapcoder666 said:
Welcome to the OnePlus 7 Pro scene mate.
Click to expand...
Click to collapse
Oh yeah, ride on guys :highfive:
ulxerker said:
@eng.stk do you also plan to provide your famous blu_spark_twrp?
Click to expand...
Click to collapse
Maybe, not apriority for me at the time, lot's of work to on the kernel.
I honestly use less and less twrp this days, do everything from the ROM with autoflash apps.
Arden144 said:
Have you read of the sleep of death/deadlock issues on this device? If so, do you have any ideas for the source of the issue?
Click to expand...
Click to collapse
Hum, have no idea what's that...
pushpendrayadav said:
Hi,
Can I use this Kernel on my OnePlus 7.
Click to expand...
Click to collapse
TacoTuco said:
Anyone flash this yet and not see any blu_shedutil cpu governer?
Edit: Also anyone seeing KCAL? And or KLAPSE? no where to be found on EXKM, maybe I need to flash it twice? Anyone's guess is as good as mine
Click to expand...
Click to collapse
Stuff is missing still, check git to see what's in (or ask us if you're after something in particular). The rest will come in time, can't do much more in less than a day ;p
Stuff in OP some are in, others are placeholder for what I intend to merge in.
more_than_hater said:
@eng.stk
Hi. We were waiting for you and your work at this forum section. Thank you for providing support for allmost all oneplus line, used your kernel and twrp for more than 2 years.
CAF introduced 675 max gpu freq support for sm8150. Will you allow us to use it, but setting 585 as defualt? Less is more, i'm agree with you.
About deadlocks, someone calls it sleep of death, there is such problem. i faced it myself many times. As far as i can say, its faulty units problem. Replaced my unit and so far no deadlocks for 2 days already. With previous one i had it once in 3-6 hours.
Click to expand...
Click to collapse
Hum if it has CAF support I may look into it, no prob.
That issue seems nasty, is it a widespread thing? Never heard of it...
starche_old said:
@eng.stk
Nice to see you here. Only now I can buy OP7 PRO and retire my OP6.
Thank you for your time and effort.
Click to expand...
Click to collapse
justibasa said:
THIS!!!!!!! This is what I've been waiting for. Thank you @eng.stk. Couldn't be happier right now.
Click to expand...
Click to collapse
Step-han said:
Nice to see you here, finally! Flashing.....
Click to expand...
Click to collapse
Thanks for the support peeps, you keep the spirit alive :highfive:
is this for 5g also?
The OP is either a few year old copy paste and/or is providing the wrong information.
- ARM enhanced performance and battery patches - guess nobody has this since 3.18 kernels
- 300Hz - set to 100
- Klapse - not in source
- KGSL fixes and reworked GPU driver - Nothing has been reworked but using high prio
- Stock thermal driver by default - what else?
- adrenoboost... - not in source
- KCAL - Advanced color control for Qualcomm MDSS v2 (RGB calibration and post-processing features) - not in source
- Several CPU Governors (blu_schedutil modded governor available) - not in source
- CVE security patches, general upstream and CAF fixes - Nothing newer in source
- USB Fast Charge (USB mode up to 900mA with MTP on) - not in source

Development [KERNEL] [blu_spark r131] [A13 Jun 2023]

{
"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"
}
Kernel features:
Build with custom upstream LLVM 14.x (Clang 14.0.6 + LLD linker + IAS)
ThinLTO full -O2 build with device and target flags enhanced, build improvements and compiler fixes, etc
Less is more: stockish kernel+modules+dtb builds based on Google latest sourcedrop for max stability (android-gs-raviole-5.10-android13-qpr3)
Full kernel tree with OEM integrated drivers, for minimal build overhead and fast deploy
Systemless installer (doesn't touch system/vendor partition, OTA friendly), AnyKernel3 backend (compatible with autoflash apps)
Removed some debug and logging options
Misc ARM performance and battery patches
CVE security patches, general upstream and fixes for important subsystems when applicable
No OC, use 250HZ base timer frequency
Enhanced TCP methods (westwood is default, BBR and others available)
Some I/O tweaks (SSG added), advanced filesystems enabled (ExFAT upstreamed, , CIFS & NFS)
ZRAM set at 3G (default lz77eh with lzo-rle, zstd, etc available)
WIP: Vibrator Strength tunable and Gesture Haptic Feedback control (touchpanel and FPR)
Gamepad support enabled (xbox, ps4, switch)
USB2 Fast Charge (force USB CDP mode up to 1500mA with MTP on)
TWRP Support(LZMA/LZ4 Ramdisk)
Wireguard updates
Compatible with Kernel Flasher, EXKM, FKM , Kernel Adiutor and others
DOWNLOAD KERNEL ZIP
Kernel Flasher/FKM download configs: HERE
(No mirrors please)​
Setup and troubleshoot: To install just flash the zip on a stock setup with either TWRP or autoflash kernel app.
If you come from other kernel or have any issues, you should restore your stock setup or dirty flash your ROM before flashing blu_spark zip to avoid problems. Also uninstall or clean data of any kernel control app you're using.
If you are upgrading between blu_spark versions, just flash the kernel zip.
About bugs and reports: don't bother to post if a log isn't ready or without steps so the behavior can be replicated. I only active support stock ROM with NO mods whatsoever (apart from root). That includes NO support if using xposed, Magisk with added modules, etc.
If you're using custom ROMs (including stock based ones) you're much on your own. I'm mostly interested on debugging stuff in stock and stable ROM.
Also try not to spam the thread with too much OT. There's threads for all kind of stuff, use them.
Going back to stock: This kernel installer doesn't change your filesystem. You can backup your boot.img/vendor_boot.img/vendor_dlkm.img with TWRP or kernel app before flashing blu_spark if you want to go back to full stock. You can also flash boot.img/vendor_boot.img/vbmeta.img in fastboot and vendor_dlkm.img in fastbootd from you stock ROM. Or just dirty flash your full OTA ROM zip.
Source Code: https://github.com/engstk/pxl6
Don't forget to hit thanks, it's free
blu_spark_r29 (A12)
So here's blu_spark for the oriole (and probably raven ;p)
Been cracking around on this since I got the device a couple weeks ago.
The new GKI kernel stuff(which imo will kill custom kerneling in the future) and the "let's use 10GB of garbage device tree to build a kernel" is not really for me.
So I decided to put on an full tree with all the vendor stuff on it, with less that 5% of what Google proposes we can play with the device just fine.
My primary objective was also to make a full builtin kernel, but seems like init expects modules and other stuff to be in place so it's a no go, at least for now (maybe with some further init stages crack it's possible, idk)
So kernel output is splitted across boot.img, vendor_boot.img and vendor_dlkm.img.
I also take the time to make AK3 basic hdr v4 compliant (big shouts to @osm0sis for being the best wingman, as always). Because fastboot is tedious and since it's 2021 there's no room for that in my builds.
You can flash the AK3 kernel zip in your favorite kernel app with autoflash functions or with TWRP when/if available. If you want/need to go stock again, instructions are on OP.
Besides Pixel 6, this should work on Pro also, but I can only test on Oriole, let me know how it goes on Raven if you're brave enough.
You can use FKM download kernel feature, just import the link bellow in the app flash section.
FKM download config: HERE
Changelog:
Build with Google Clang 12.0.5 + LLD linker
Full kernel based from kernel/gs+google-modules @ android-gs-raviole-5.10-android12-d1 (android-12.0.0_r0.17) (Nov 2021.1)
Several build fixes and improvements (check git for details)
drivers: google-modules: make it build and additional fixes, remove cruft
Disable some debug and logging
FS and F2FS improvements
Enable advanced TCP congestion control (westwood default)
Add wakelock blocker framework
Tuned a couple IO and ZRAM runtime stuff
AK3 updates (v20211118) plus my own additional fixes for hdrv4 flashing (big shouts @osm0sis for the help)
For root, canary Magisk 23015 or newer is mandatory
Click to expand...
Click to collapse
Keep in mind: I will give no active support for custom ROMs (including stock based ones).
I am mostly interested on debugging stuff in stock ROM (with logs and reproducible steps to replicate the issue).
No mirrors please
Don't forget to hit thanks, it's free
Just installed using FKM will be testing thanks for the hard work
Great to see blu_spark kernel on the Pixel 6. Thanks. Installed last night and ready to give the kernel a go today.
lovin to see it!
gonna flash asap
eng.stk said:
Vibrator Strength tunable and Gesture Haptic Feedback control (touchpanel and FPR)
Click to expand...
Click to collapse
Where are we able to tune this? EXKM & FK don't show anything for me.
Flawn said:
Where are we able to tune this? EXKM & FK don't show anything for me.
Click to expand...
Click to collapse
It's work in progress, some stuff are to indicate what I want to add later on.
eng.stk said:
Kernel features: (WIP)
Build with Google Clang version 12.0.5 + LLD linker
Full -O2 build with device and target flags enhanced, build improvements and compiler fixes, etc
Less is more: stockish builds based on Google latest sourcedrop for max stability (android-gs-raviole-5.10-android12-d1)
Full kernel tree with OEM integrated drivers, for minimal build overhead and fast deploy
Systemless installer (doesn't touch system/vendor partition, OTA friendly), AnyKernel3 backend (compatible with autoflash apps)
Removed some debug and logging options
Misc ARM performance and battery patches
CVE security patches, general upstream and fixes for important subsystems when applicable
No OC, use 250HZ base timer frequency
Enhanced TCP methods (westwood is default, BBR and others available)
Some I/O control tweaks, advanced filesystems enabled (F2FS, ExFAT, NTFS, CIFS & NFS)
ZRAM set at 4G (default lz77eh with lzo-rle, zstd, etc available)
Vibrator Strength tunable and Gesture Haptic Feedback control (touchpanel and FPR)
Gamepad support enabled (xbox, ps4, switch)
USB2 Fast Charge (USB mode up to 900mA with MTP on)
Wakelock blockers available
TWRP Support(LZMA/LZ4 Ramdisk)
Compatible with EXKM, FKM , Kernel Adiutor and others
DOWNLOAD KERNEL ZIP
FKM download configs: HERE
(No mirrors please)​
Setup and troubleshoot: To install just flash the zip on a stock setup with either TWRP or autoflash kernel app.
If you come from other kernel or have any issues, you should restore your stock setup or dirty flash your ROM before flashing blu_spark zip to avoid problems. Also uninstall or clean data of any kernel control app you're using.
If you are upgrading between blu_spark versions, just flash the kernel zip.
About bugs and reports: don't bother to post if a log isn't ready or without steps so the behavior can be replicated. I only active support stock ROM with NO mods whatsoever (apart from root). That includes NO support if using xposed, Magisk with added modules, etc.
If you're using custom ROMs (including stock based ones) you're much on your own. I'm mostly interested on debugging stuff in stock and stable ROM.
Also try not to spam the thread with OT. There's threads for all kind of stuff, use them.
Going back to stock: This kernel installer doesn't change your filesystem. You can backup your boot.img/vendor_boot.img/vendor_dlkm.img with TWRP or kernel app before flashing blu_spark if you want to go back to full stock. You can also flash boot.img/vendor_boot.img in fastboot and vendor_dlkm.img in fastbootd from you stock ROM. Or just dirty flash your full OTA ROM zip.
Source Code: https://github.com/engstk/pxl6
Don't forget to hit thanks, it's free
Click to expand...
Click to collapse
Thanks for kernel...
To go back to stock all three images ( boot, dtbo, vendor dlkm) can be flsahed through EX kernel manager actually....
Flashed the kernel using EX-Manager.
So far, so good on my P6.
cultofluna said:
Thanks for kernel...
To go back to stock all three images ( boot, dtbo, vendor dlkm) can be flsahed through EX kernel manager actually....
Click to expand...
Click to collapse
"with TWRP or kernel app" "fastboot" "dirty flash OTA zip"
People can use what is easier/better for them if there's the need to restore stock.
I don't use dtbo, I don't patch anything there.
eng.stk said:
blu_spark_r29 (A12)
So here's blu_spark for the oriole (and probably raven ;p)
Been cracking around on this since I got the device a couple weeks ago.
The new GKI kernel stuff(which imo will kill custom kerneling in the future) and the "let's use 10GB of garbage device tree to build a kernel" is not really for me.
So I decided to put on an full tree with all the vendor stuff on it, with less that 5% of what Google proposes we can play with the device just fine.
Click to expand...
Click to collapse
Is this the reason there aren't many custom kernels up until now? I thought the GKI would make things easier at least after some time that devs get more accustomed with it.
Btw nice to see you here I was running your kernel for the past few months on op8pro.
eng.stk said:
"with TWRP or kernel app" "fastboot" "dirty flash OTA zip"
People can use what is easier/better for them if there's the need to restore stock.
I don't use dtbo, I don't patch anything there
Click to expand...
Click to collapse
Of course...
Just sharing the info that vendor dlkm img can also be flashed on the phone through the ex manager ( not other kernel manager) ..
Otherwise on fastbootd
@eng.stk booted fine on 6pro
Great to see you on Pixel 6 @eng.stk been using your kernel on most of the devices that i have granted 1 or 2 dont have it but like always you're on your a game and i look foward to how much battery savings we will get with this kernel over time. Seems great so far btw on your kernel.
cultofluna said:
Of course...
Just sharing the info that vendor dlkm img can also be flashed on the phone through the ex manager ( not other kernel manager) ..
Otherwise on fastbootd
@eng.stk booted fine on 6pro
Click to expand...
Click to collapse
Nice, thanks for testing out
arvylas said:
Is this the reason there aren't many custom kernels up until now? I thought the GKI would make things easier at least after some time that devs get more accustomed with it.
Btw nice to see you here I was running your kernel for the past few months on op8pro.
Click to expand...
Click to collapse
Well GKI is for getting vendor/oem life easier the way updates are maintained.
Actually the choices the big G has made over time complicate the aftermarket tinkering.
They are making thinks too convoluted for instance, keeping source scattered all over the place creating artificial dependencies, using a build backend full of unneeded junk, output goes in random places just because, images full of junk with multi-ramdisks and padding with weird layouts, etc.
They started complicating ROM stuff, partitions, etc. Then they went after gapps and root. Now it's kernel.
Android is becoming ChromeOS imo.
Doesn't mean things can't be modded, just the way they are going is deterring to do it.
Excellent to see you here mate! Just got my 6, so I want to give myself some stock time with it, but Im sure I'll be flashing soon
kevp75 said:
Excellent to see you here mate! Just got my 6, so I want to give myself some stock time with it, but Im sure I'll be flashing soon
Click to expand...
Click to collapse
Nice to see here dude, enjoy your oriole
eng.stk said:
Nice to see here dude, enjoy your oriole
Click to expand...
Click to collapse
so far loving it. making a modified case so I can attach it to my telescope
Been working pretty well, I've had a couple of weird freezing and things becoming unresponsive but besides that it's working great.

Categories

Resources