{
"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"
}
DISCLAIMER:
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this ROM before flashing it! YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
I don't provide support for OneUI-pie & treble ROMs, asking me if I will ever do is just a waste of time.
INFO:
If you wonder what the hell RAD Kernel is... Then let me explain, RAD Kernel is a project oriented towards people who depend on their phone every day.
RAD Kernel is designed for maximum stability.
All kernel builds are thoroughly tested before Release.
As the title says RAD Kernel per se supports AOSP ROM(s), OneUI 2 ROM(s) and it's meant to be used with it for a better STABLE experience.
RAD Kernel will NOT work with any other ROMS except AOSP & OneUI-2 (i.e no OneUI-pie & treble support).
SUPPORTED DEVICES:
G950(N/F/FD)
G955(N/F/FD)
N950(F/FD)
FEATURES:
Linux 4.4.111
Compiled with Clang 9.
O3 optimizations.
Fast, smooth and great for Daily Use!
Permissive SE-Linux.
Boeffla Wakelock Blocker.
Interactive governor as Default.
Optimized Integer SQRT. for upto 3x faster operation.
Tuned Interactive governor for better balance between performance and battery.
CPU BIG up to 2314MHz.
CPU small up to 1690MHz.
GPU OC up to 572MHz
WireGuard.
Disabled CRC by default - 30% File system performance.
Fsync toggle enabled by default, can be changed in a kernel tweaker.
TCP congestion - bic as default.
Z-RAM enabled by default and set at 2592MB.
Z-RAM compression - lzo
HMP values tuned for better performance!
and the list goes on!
ROOT:
RAD Kernel DOES NOT come with pre-installed ROOT.
You can flash the latest MAGISK to get ROOT!
SUPPORT:
Telegram Group - Click here!
Telegram Channel - Click Here!
CREDITS:
Me, for developing without time and for the struggle to test new things.
Stricted for LineageOS development.
Dr.DoubtReaper for testing my kernel images.
Samsung Open Source for their Kernel source.
Topjohnwu for magisk!
Linus torvalds for Linux!
Thanks to anyone else who made this whole thing possible, you are part of it as well!
and all the people on GitHub whom i might have cherry-picked from!
XDA:DevDB Information
RAD Kernel for Exynos8895, Kernel for the Samsung Galaxy S8
Contributors
bruh™
Source Code: https://github.com/Exynos-nigg/RAD-8895
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: R4
Stable Release Date: 2021-01-07
Created 2020-10-05
Last Updated 2020-11-08
R4 (07/01/2021) [EOL]
BUGS:
DexOnPc is bugged, device wont be recognized (OneUI2 build only!)
DOWNLOADS:
Official Kernel Website - click here!
Google Drive - click here!
INSTALLATION:
NOTE! YOU NEED TO BE ALREADY ON AOSP/OneUI-2 ROM, BEFORE FLASHING THIS CUSTOM KERNEL
Download the provided zip for your device model.
Put the zip inside your storage.
Reboot to TWRP recovery.
Flash the zip and wait until it completes.
Reboot your device, and enjoy the Butter smooth experience.
CHANGELOGS:
R4(07/01/2021)
Added OneUI-2 support! (make sure to flash the OneUI-2 build)
Disabled logging and some debug stuff
Older changelogs below! =)
R3.5 HOTFIX(08/11/2020)
Unified installer zips!
Fix bootloop issues!
Switch from AK3 to AIK zips!
NOTE: This releases has no changes kernel side, but the installation zips have been changed!
NOTE: Sorry for the inconveniences caused because of the bootloops, this releases should (hopefully!) fix em =)
R3 (04/11/2020)
Disabled GFS (Gentle Fair Sleepers) for better UI performance!
Fix placebo tweaks blocker!
General optimizations!
Kill DVFS completely!
Remove excessive logging from decon, GPU drivers & touchscreen drivers!
Unified S8/S8+ kernel!
Set "westwood" as default TCP congestion algorithm!
NOTE: The kernel zips have different time labels on them because i did build them few days before but was just lazy to release them
R2 (13/10/2020)
Changed to Interactive on CPU!
Fixed sound not coming from earpiece!
Remove Audit dependency!
Enabled touch input booster!
Disabled Hotplug!
Change default IO scheduler to "deadline"!
Disable some logging!
This kernel build should be way smoother than R1!
R1 (05/10/2020)
Initial Release!
FAQ: (Read this before flashing the kernel and reporting bugs!)
Q. Gaming performace isnt good in this kernel!
A. Disable Samsung Hotplug from your preferred kernel tweaker app! Hotplug is disabled in builds from R2 onwards!
Q. Whats Fsync? should i disable it?
A. fsync transfers ("flushes") all modified in-core data of (i.e., modified buffer cache pages for) the file referred to by the file descriptor fd to the disk device (or other permanent storage device) so that all changed information can be retrieved even after the system crashed or was rebooted. This includes writing through or flushing a disk cache if present. The call blocks until the device reports that the transfer has completed. It also flushes metadata information associated with the file (see stat(2)).
Too scientific, didnt read! : In layman terms disabling Fsync gives you better performance with the risk of a Data loss/corruption during a system crash!
Q. I cant Flash NFS injector, FDE.AI, MAGNETAR and other tweakers on this kernel!
A. I have added a in-built kernel blocker to block installation of these so called "AIO kernel tweakers". You shouldnt install these tweaks in my opinion! If you still want to use a Tweaker, i prefer you use KTweak though i wont be providing support for issues if u have flashed any mods or anything of this likeliness!
Q. I have an issue and i have reported it in the XDA thread, yet nobody replied to me.
A. I might be slow in responding for issues reported in the XDA thread, if u want me to reply more faster, report it in the Telegram support group!
Q. My phone gets HOT while using this kernel!?
A. Short answer: It's your own issue, fix it yourself. Nobody makes a kernel just to burn your hands.
Long answer:
* Install Termux app from Play Store * Enable screen rotation, open Termux in landspace mode * Type this command: su -c top -d 2 * A list of processes will appear and refresh with 2s interval. Find which process consumes the most CPU usage with [%CPU] column and the package name in ARGS column. You should see the culprit of your issue.
Reminder: There is no such thing as "I have nothing in background but the phone still heats up". There definitely something happen and 99% of the time it's some of the rogue apps running in background.
Thanks to Diep Quynh for finding this one out!
Nice,finally a good kernel for android q
great kernel , ive been using with ZenX OS 1.9
I'm using s8 just for social media without gaming , is there any best battery tweak or kernel auditor config for this kernel ? are conservative cpu governor best suitable for battery life ?
cpunkaz said:
Nice,finally a good kernel for android q
Click to expand...
Click to collapse
Thanks m8!
Claver90 said:
great kernel , ive been using with ZenX OS 1.9
I'm using s8 just for social media without gaming , is there any best battery tweak or kernel auditor config for this kernel ? are conservative cpu governor best suitable for battery life ?
Click to expand...
Click to collapse
I would recommend you use the kernel default presets and yes conservative is pretty good for battery!
Live0verfl0w said:
Thanks m8!
I would recommend you use the kernel default presets and yes conservative is pretty good for battery!
Click to expand...
Click to collapse
i humbly requst u to make 2 kernel one for normal user(who dont want overclock)
and second for advanced user who wants overclock.
thanks
@Live0verfl0w
HMP reworked aka HMP 2.0!
could you please post a "git diff" for this ?
ace2nutzer said:
@Live0verfl0w
HMP reworked aka HMP 2.0!
could you please post a "git diff" for this ?
Click to expand...
Click to collapse
Sorry for the late reply, i dont really login to xda much
as for the query the source is up on github, and by "rework" i merely meant changing the values and also tweaking the up threshold and stuff in my init.rc, the OP has it now cleared.
and Thanks for ur work on a2n kernel, keep it up sir!
Best kernel! Keep up the great work! R2 works great!
R2 on Zen Is, and battery is draining fast and stops charging at 77% and starts discharging, even while plugged in. Is that normal? Didn't experience this in R1
alberto23 said:
Best kernel! Keep up the great work! R2 works great!
Click to expand...
Click to collapse
Thanks man!
[email protected] said:
R2 on Zen Is, and battery is draining fast and stops charging at 77% and starts discharging, even while plugged in. Is that normal? Didn't experience this in R1
Click to expand...
Click to collapse
Its definetely an issue with u or u doing something, i can say this because im on Zenx OS and i dont have this issue.
P.S - Disable all mods and magisk modules:good:
Orangelelo said:
battery uses like hell. heats and freezes in direct sunlight.
Click to expand...
Click to collapse
It's HMP Driver issue.
@ Dev
try to port EAS from RZ Kernel, (didn't test by me, but maybe better than HMP)
or if it's too difficult, try to use my method:
Code:
CONFIG_SCHED_HMP_CUSTOM
It's basically same like stock HMP, but without tasks migration between little and big cpu. Because that's the buggy part of the driver.
That means, you have to hardcode and configure by hand your own CPUSET ... Tasks that are performance critical, will run always on big cpu and tasks (all sort) like audio driver, non important services like logd ..magiskd .. etc should run on little cpu. This basically even improves performance on big CPU for foreground apps, because u'll offload big cpu if you move as much as possible to the little cpu.
Also migration related latencies are completely eliminated.
The only drawback is that you will see lower score in geekbench in multicore ... because the benchmark will use 4 cores instead all 8.
But don't worry, this will not reduce the real performance of the phone because many apps uses only one core .. and even 4 cores are enough.
If you use my method, i suggest my ramdisk related changes for cpuset or make your own.
If you have any problems or questions, feel free to contact me.
Orangelelo said:
battery uses like hell. heats and freezes in direct sunlight.
Click to expand...
Click to collapse
Kindly refrain from posting fake report/bug reports, if u have dramas contain it in telegram and dont bring toxicity in xda and misleading people, kthknx
ace2nutzer said:
It's HMP Driver issue.
@ Dev
try to port EAS from RZ Kernel, (didn't test by me, but maybe better than HMP)
or if it's too difficult, try to use my method:
Code:
CONFIG_SCHED_HMP_CUSTOM
It's basically same like stock HMP, but without tasks migration between little and big cpu. Because that's the buggy part of the driver.
That means, you have to hardcode and configure by hand your own CPUSET ... Tasks that are performance critical, will run always on big cpu and tasks (all sort) like audio driver, non important services like logd ..magiskd .. etc should run on little cpu. This basically even improves performance on big CPU for foreground apps, because u'll offload big cpu if you move as much as possible to the little cpu.
Also migration related latencies are completely eliminated.
The only drawback is that you will see lower score in geekbench in multicore ... because the benchmark will use 4 cores instead all 8.
But don't worry, this will not reduce the real performance of the phone because many apps uses only one core .. and even 4 cores are enough.
If you use my method, i suggest my ramdisk related changes for cpuset or make your own.
If you have any problems or questions, feel free to contact me.
Click to expand...
Click to collapse
1. As for the eas thingy, i dont wanna port eas bcz if i did, then my kernel wud just become a rz reborn - lol
2. As for @Orangelelo "s bug report, he was asking for etas, OC, and forcing people and being toxic in general and i banned him from my TG group, out of this anger he has been posting all these wrong issue reports.
3. As for the HMP thing, thanks m8 and i will look into it, thanks once again for ur reply here =)
Orangelelo said:
heating issue is there. check
Click to expand...
Click to collapse
no there isnt
now kindly refrain from bringing ur toxicity in here too, like u did on telegram before as @Live0verfl0w mentioned earlier
kthxbye
AFAIK Stock HMP Driver only works more or less "fine" if you don't change cpu min/max freq and interactive gov is in use.
If you change just one thing of them, then the driver in certain situations starts to freak out.
That's why i was asking for HMP related commits, because i was hoping that someone finally did managed to fix it.
That Driver is marked as EXPERIMENTAL, see in source code.
But anyway, EXPERIMENTAL doesn't automatically mean that it's quite buggy, as there are a lot of linux kernel drivers marked as experimental but works fine.
But the HMP implementation is really quite buggy wthout any modifications.
So it's very likely that he is right facing "overheating + freezes" issues, because exactly those symptoms i had faced as well even with stock Kernel/ROM.
Havoc OS the phone cannot start with this kernel (R2), S8+ Exynos
kraft6677 said:
Havoc OS the phone cannot start with this kernel (R2), S8+ Exynos
Click to expand...
Click to collapse
Its an installer issue, i have found the cause and am rectifying it, meanwhile
u can flash the kernel zip two times, weirdly enough this seems to fix bootloop issues.
p.s - also havoc os has an issue with sound not coming from earpiece, so if u do encounter that issue kindly do not report it here as its a rom issue that i cant help with.
Thread cleaned!
A friendly word of advice to @Live0verfl0w and @Orangelelo. I will ask you both to kindly refrain from bringing TG issues to XDA plain and simple!! If you continue to have issues with each other, please keep them relegated to PM's since the public forums are not the place for flamming wars or accusations for all to see. Thank you for your cooperation, and a pleasant day to all.
Best regards: Badger50
Related
duki994 Kernel for Stock TouchWiz MM ROMs
Development stopped. I don't have device anymore
This is for MM only!!! For LP go to duki994 LP kernel thread
LP kernel thread
It's based on official Samsung CPE6 sources for Marshmallow firmware.
Important note:
This kernel should work on any custom ROM that is stock lollipop based and is based on stock CPE6 source
Features:
* Wolfson Audio control adapted to G900H implementation (thanks to @AndreiLux)
* Charge control by me (@duki994)
* CPU voltage control for both A7 and A15 cluster (thanks to @AndreiLux)
* Exposed all OPP voltage controls (thanks to @AndreiLux)
* LED fading control (thanks to @AndreiLux)
* Powersuspend v1.7 by @faux123 and @Yank555
* MM and FS powersuspend mods ported from @dorimanx's LG G2 kernel
* SCHED code fixes
* SCHED: HMP thresholds changed and new patches implemented
* OF code updated --> better/faster reading of DTS and faster operation
* Many changes related to ARM instruction code and lowlevel ARM core management
* Enabled NEON mode in kernel with full VFPV4 support
* Added new SHA256 , SHA512, SHA1, ASH2 and AES NEON accelerated algortihms - now blazing fast
* WiFi fixes
* NET updates
* LMK updated and added new feature: Adaptive LMK --> better multitasking
* Enabled all TCP congestion protocols and set Westwood as default (best wireless performance)
* Wakelock disabler: You can disable some common Samsung wakelocks in Synapse "Misc" tab if some of them are draining your battery
* Fully configurable in Synapse application (download from Google Play)
For kernel configuration use Synapse
Download from Google Play.
Google Play link for lazy people:
https://play.google.com/store/apps/details?id=com.af.synapse
/* Important note to other devs */
You cannot include this kernel in your ROMs. I can't be responsible if anything goes wrong, I can't help with any issues without knowing kernel version and users should be routed to this thread if they want this kernel, or if you recommend it. I think that it's best to separately view custom ROM and custom Kernel, so each dev (ROM or Kernel one) can work on bugs/features and make it as compatible as it can.
However, you can add this thread link and mention me in your thread, as so people would know where to ask if kernel problem arises. I will do the same for you
Warranty void
By flashing this kernel you will void your warranty. I'm not responsible if you brick your device, or if someone starts nuclear war.
Note:
Don't change voltages on "Busses" tab if you don't know what you are doing. It can reboot your phone if your memory controllers, ISP or MMC controllers that can't handle low voltage.
If someone happens to have bug with WiFi saved password being lost every reboot, here is fix:
WiFi pasword resetting fix:
Code:
1. open your build.prop file
2. find line ro.securestorage.support
3. change it from true to false (if not already false)
This line being on true WILL make your WiFi forget password each reboot. This is due to Samsung's rooting restriction and other Samsung specific workarounds to stop rooting and flashing. Any custom ROM probably has this line changed to false.
GitHub sources:
Kernel:
https://github.com/duki994/g900h_mm_kernel
Ramdisk:
https://github.com/duki994/g900h_mm_ramdisk
SuperSU problem fix:
After each kernel installation you'll need to reinstall SuperSU from Play Store or from apk.
I'm trying to solve this problem currently.
Root and busybox work as intended. Problem is only with SuperSU app.
Downloads folder:
https://www.androidfilehost.com/?w=files&flid=91231
Downlads mirror:
https://app.box.com/s/v8txuc1n82l48sksdhf2obx2blupol4c
Always make backup of boot partition in case something goes wrong!!! You have been warned
Stock CPE6 flashable kernel:
It's found in downloads folder and in downloads mirror.
Changelog:
Version 1.9 BETA
* MM updates
* IRQ and ARM GIC (Generic Interrupt Controller) updates
* CPUFREQ critical performance and battery saving updates for big.LITTLE architecture
* ARM arch specific updates and workaround for various bugs from Linaro LSK 3.10.x tree and ARM devs
* EXT4 and FS updates for better performance and less CPU usage. Also some code cleanups.
* NET updates
* Silenced mDNIe dmesg hooks. Not needed now as mDNIe control is working as it should.
* RCU NOCB ALL for better softirq workings in kernel (should provide boost to moderate usage)
Version 1.8
* Added mDNIe control (display color interface like KCAL for Qualcomm) (thanks to @AndreiLux)
* Interactive governor updated (will stay on min freq and not ramp up when load is <5%)
Older versions changelog:
Version 1.7
* Further LMK updates. Ported LMK driver from arter97's S6 repository (much faster code with less task searching and choosing loops)
* MM updates needed for new LMK
* Added several protected apps within code
Version 1.6
* Reverted some LMK changes and fully implemented ADJ_RBTREE in Samsung's OOM LMK code (this should fix some performace issues (like small lags) while freeing RAM)
* Added several system processes in LMK protected apps (LMK won't kill them unless your system RAM is highly overloaded and on verge of collapse)
Version 1.5
* Interactive governor optimizations and tunings from other Exynos kernels and other devs + me (mostly from S6 kernels)
* Interactive governor screen off power save
* MM updates
* MemInfo updated so Android OS can have better memory stats and thus better memory management
* Hardcoded some props like securestorage support and TIMA so that they are false/0/off.
* Power management code updated
Version 1.4
* Workaround headset outbound call BUG (thanks to @ponkz for reporting this nasty bug)
* Clean up some code and correct several descriptions in Synapse.
Version 1.3
* Made "Main speaker gain" control for new Clearwater based Arizona-class sound control
Version 1.2.1
* Correctly calibrated equalizer frequencies in sound control (thanks to AndreiLux for tip)
* Updated interactive governor
Version 1.2
* Added IPA thermal trigger temp control
* Removed some battery saving features that were actually DRAINING BATTERY
----> HMP little packing, PE workqueues removed
* Removed Wakelock Control because it causes SoD's when user disables important wakelock!
* Added new 8-band EQ Sound control made for S6 that work awesome (god bless @AndreiLux)
----> it has even per channel 8-band EQ's
* Made some compatibility improvements
Version 1.1
* Added GPU voltage control
* Fixed some ramdisk scripts
* Optimized compiler flags for GPU code
* ro.secure=0 and ro.adb.secure=0 so ADB is now like unchained beast for those who like to play with ROMs and system files and have bootloops
XDA:DevDB Information
G900H MM Kernel, Kernel for the Samsung Galaxy S5
Contributors
duki994
Source Code: https://github.com/duki994/g900h_mm_kernel
Kernel Special Features: Voltage control, Sound control, Charge control, Freq control, LED control
Version Information
Status: Stable
Current Stable Version: 1.8
Stable Release Date: 2016-08-16
Current Beta Version: 1.9
Beta Release Date: 2016-08-21
Created 2016-07-27
Last Updated 2016-11-10
Reserved
CPU OC is unnecessary for our device.
And CPU underclock won't save more battery.
It'll actually drain more battery.
On very low freqs CPU can't finish task and needs to bump freq up. The freq changing is much more power costly than being on stock 500mhz min for A7 and 800mhz min for A15.
Look at power curves.
We have power curves similar to those on 5433, just about 20% lower I think
This are high performance cores (A15, A57, A72...)
{
"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"
}
And this are for power-saving cores (A7, A53...)
The shape of curve for our chip is almost same, only with lower consumption. Look how exponentially it increases as you put frequency after 1.2GHz.
So if I enable OC to, let's say, 2GHz, then power consumption would be 20% higher than on 1.9GHz and performance would be 4% higher.
But don't let that fool you. Phone may last 2s-3s on 2GHz. Then it would throttle down when it overheats due too much power dissipation.
So in the end you get much lower performance than you would have on 1.9GHz.
And keep in mind that Exynos 7420 is built on 14nm FinFET technology, and Exynos 5422 is 28nm HKMG.
So we may use a bit more power than 7420.
My observation:
I get maximum performance on 1.8GHz. Phone is heating at least 10 celsius degrees less than on 1.9GHz so almost no thermal throttling.
For games and high performance apps, I suggest that you lock A15 core cluster on 1.8GHz.
Source for Exynos 7420 in-depth review:
http://www.anandtech.com/show/9330/exynos-7420-deep-dive/5
Tips & Tricks
I suggest you use Xposed for Samsung MM ROMs and Xposed module called XTouchWiz.
They are both maintained by @wanam
XTouchWiz Recommended settings:
* Disable TouchWiz DVFS (you'll get enormous performance boost)
* Disable KNOX/TIMA (disabled TIMA in kernel, but XTouchWiz uses Xposed method hooks to disable it in ROM)
XTouchWiz thread and download link in @wanam's thread:
http://forum.xda-developers.com/xposed/modules/app-xtouchwiz-customize-stock-samsung-t3296878
Xposed for Samsung Marshmallow Latest version and download links in @wanam's thread:
http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
:good::good::good:Great great great...My waiting is finished. thanx a lot for great surprise. Flashing...:good::good:
Good to see you back )) you made my day bro
Is it permissive????
Sent from my SM-G935F using Tapatalk
BlueZ said:
Is it permissive????
Sent from my SM-G935F using Tapatalk
Click to expand...
Click to collapse
Not on boot. You can set it to permissive in Synapse.
But I use patched sepolicy from SuperSU (thanks to Chainfire), so permissive/enforcing shouldn't make too much difference (or problems) anyway
duki994 said:
Not on boot. You can set it to permissive in Synapse.
But I use patched sepolicy from SuperSU (thanks to Chainfire), so permissive/enforcing shouldn't make too much difference (or problems) anyway
Click to expand...
Click to collapse
Thanks I'll try it
Sent from my SM-G935F using Tapatalk
TheDarkSithLord said:
Good to see you back )) you made my day bro
Click to expand...
Click to collapse
Thanks
P.S
Do not quote OP. Never!
Please edit your post and delete OP qoute before moderators do it. It's against XDA rules for a good number of reasons.
One of them is:
If I make changes to OP they won't be reflected to your quote in your post and someone may miss very important info.
Please consider this. It's for good of other users of any kernel/ROM/app on XDA
Sent from my SM-G900H using Tapatalk
Nice I will try it as soon as i get back home. Thx for the hard work.
what about battery life
shahram Ali said:
what about battery life
Click to expand...
Click to collapse
For me, alpha versions were awesome. This one should be better.
Especially when on WiFi/Data or any other internet connection.
If you have bigger battery drain, then you have something wrong in you ROM setup/boot scripts.
Plus wait for a few days to get accurate battery life. I released this version today so no objective batt life readings yet
Be patient and ot'll pay off
Sent from my SM-G900H using Tapatalk
Does it support private mode and other *stock* kernel supported apps?
iDouvie said:
Does it support private mode and other *stock* kernel supported apps?
Click to expand...
Click to collapse
Try and see. I have no need for private mode and I don't use it.
Fingerprint works, S Health and other work too.
I suggest using XTouchWiz and disabling DVFS
Sent from my SM-G900H using Tapatalk
duki994 said:
For me, alpha versions were awesome. This one should be better.
Especially when on WiFi/Data or any other internet connection.
If you have bigger battery drain, then you have something wrong in you ROM setup/boot scripts.
Plus wait for a few days to get accurate battery life. I released this version today so no objective batt life readings yet
Be patient and ot'll pay off
Sent from my SM-G900H using Tapatalk
Click to expand...
Click to collapse
I am tested ut and not that much i will use it for 24 hours then if i saw any bug i will report dude i lived ur LP kernel and this one not bad for battery but greenapple kernel was better hope see next version with better battery
Top notch kernel as always.. can u share ur best battery setting in synapse mr @duki994 because i need a little more battery saving..
Thanks :victory:
Report after first day 0f usage ) kernel is amazing ) battery life is wonderful ) my phone isn't lagging at all)) good job @duki994 ) also thanks to @somadsul for his green apple Kernel ) keep it up too or duki will understand that he beyond compression and will add features not one by one but half by half as nvidia do now )))))
P.S that was a joke
P.P.S about kernel awesomeness it's not a joke
Cheers ))
ponkz said:
Top notch kernel as always.. can u share ur best battery setting in synapse mr @duki994 because i need a little more battery saving..
Thanks :victory:
Click to expand...
Click to collapse
If you really need mre battery saving then replace battery. I'm serious.
I get like 1hr SoT and 80% battery. Just a bit worse than my old G2 with enormous masterpiece, Dorimanx kernel.
Use XTouchWiz and disable DVFS. Everything else sjould work much better.
I can't fully disable DVFS for exynos 5422 in kernel. It's at least 70% userspace and uses ioctl commands.
That's what Samsung did. Disable DVFS via XTouchWiz (via Xposed framework) and you're OK
Can't fix that in kernel. And it uses too much battery.
For power saving, undervolt by 25mV all cores (A7 + A15) and use ROW or NOOP sched. But performance will be at leas 10% lower for maybe 30min more SoT. Maybe !!!
Sent from my SM-G900H using Tapatalk
duki994 said:
If you really need mre battery saving then replace battery. I'm serious.
I get like 1hr SoT and 80% battery. Just a bit worse than my old G2 with enormous masterpiece, Dorimanx kernel.
Use XTouchWiz and disable DVFS. Everything else sjould work much better.
I can't fully disable DVFS for exynos 5422 in kernel. It's at least 70% userspace and uses ioctl commands.
That's what Samsung did. Disable DVFS via XTouchWiz (via Xposed framework) and you're OK
Can't fix that in kernel. And it uses too much battery.
For power saving, undervolt by 25mV all cores (A7 + A15) and use ROW or NOOP sched. But performance will be at leas 10% lower for maybe 30min more SoT. Maybe !!!
Sent from my SM-G900H using Tapatalk
Click to expand...
Click to collapse
Would you recommend using the PE workqueues and HMP little packing options with your kernel?
@duki994 Dude im waiting for this.. Great work.. Could u please add insecure ADB and enable ADB debugging default so as to easy to take logs while in bootloop as i was always playing with system files.
{
"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.
{
"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 ZIPFKM 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
{
"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.
Let's get this out of the way, I'm not responsible for anything more than a kernel panic.
Now that we've got that over with, I introduce to you - Zest Kernel. This ain't your average kernel on XDA. Zest Kernel is tuned down to every last mmap() to ensure that your device runs as fast and smooth as your hardware permits. No longer are the days of your battery dying on the bus, slow network speeds at home, or lags when swiping on those hot, new Android 11 gestures. Zest Kernel will revamp the experience of your device.
Spoiler: Here's what you get with Zest Kernel ꜰᴏʀ ʙʀᴀᴍʙʟᴇ.
Boot Time
By shrinking the kernel's size with Dead Code Elimination (DCE) and removing a bloat of debug and unused drivers, we decrease boot times [1].
LLVM Tools
Zest Kernel is built exclusively with the LLVM toolchain and tools, which allows us to utilise a wide range of security and performance features as well as satisfying my LLVM fanboy needs.
Networking Performance
Due to the addition of the rmnet_perf and rmnet_shs drivers from Qualcomm, cellular networking performance can see improvements due to network aggregation.
Performance
Through backporting mainline improvements to mmap() and locking, the kernel's core code receives improvements in performance and works to reduce jitter and improve system responsiveness. The return of BPF JIT allows us to improve performance with eBPF programs that Android utilises. As well as these changes, Danny (kdrag0n)'s efficient frequencies and Sultan's latency reduction patchsets are included which improve system fluidity and performance. LTO is also enabled, improving overall kernel performance. Tuning for ext4
Security
Zest Kernel utilises Clang's Control Flow Integrity (CFI) to protect against undefined behaviour that tries to subvert the kernel's control flow. Clang's ShadowCallStack, which protects programs against return address overwrites such as stack overflows, is also switched on and enabled with virtually mapped call stacks. All locals that are automatically initialised with zeros instead of patterns, which is safer for strings, pointers, indexes, and sizes. WireGuard is also included to provide a secure, performant VPN tunnel for those who wish to use it.
zRAM Improvements
Backports from mainline and changes from Sony allow us to utilise a more efficient zRAM backend, z3fold. While zRAM is only used on bramble, since 8GB is more than enough memory on redfin, this should provide a nice improvement for zRAM on bramble.
[1] - The first boot may take longer as F2FS (the filesystem we use) needs to check for corruption every time the kernel is changed for safety measures. Subsequent boots should be much faster.
Spoiler: How to install Zest Kernel ꜰᴏʀ ʙʀᴀᴍʙʟᴇ.
1) Make sure you're on the December or January SP.
2) Download Zest Kernel from the link below.
3) Enter fastboot (not fastbootd) with adb reboot bootloader or another method.
4) fastboot boot ZestKernel-Installer-P4A5G<DATE>.img where <DATE> refers to the release date of the specific kernel.
5) Yes, I said boot not flash. I hope you read that correctly.
6) Read my beautiful installation header and wait for your device to boot up.
Spoiler: Download Zest Kernel ꜰᴏʀ ʙʀᴀᴍʙʟᴇ directly from my site.
Visit https://www.thezest.dev, click on "builds", then get the latest build from the relevant folder (Zest Kernel/bramble, in this case).
Releases are named in the form of ZestKernel-Installer-<Device Name><ISO 8601 Date>.img.
Spoiler: Where to get the source code of Zest Kernel ꜰᴏʀ ʙʀᴀᴍʙʟᴇ.
GitHub - lazerl0rd/tryme_redbull: A kernel for the Google Pixel 5 tuned to enhance system responsiveness, efficiency, and security.
A kernel for the Google Pixel 5 tuned to enhance system responsiveness, efficiency, and security. - GitHub - lazerl0rd/tryme_redbull: A kernel for the Google Pixel 5 tuned to enhance system respons...
github.com
Spoiler: Some screenshots of Zest Kernel ꜰᴏʀ ʙʀᴀᴍʙʟᴇ.
{
"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"
}
Spoiler: Notable credits for Zest Kernel ꜰᴏʀ ʙʀᴀᴍʙʟᴇ.
Sultan Alsawaf (kerneltoast/@Sultanxda) for his patchsets which help to improve the fluidity of graphics and more.
Danny Lin (@kdrag0n) for kramflash (the kernel installer) as well as a load of useful patches.
Jason Donenfeld (@zx2c4) for WireGuard.
Artem Labazov for his suggestion to use z3fold as a backend for zRAM.
***
If you enjoyed Zest Kernel, please donate to help keep up maintenance at https://paypal.me/paydiab. I'm strict on quality, and give each release it's quality time and care (possibly even more so than your OEM). Having a small income from these kernels gives me a better incentive to keep pushing them out for y'all.
***
Great work man. Reall appreciate to bring some love for this device despite you own a pissel 5
Thanks for making this for our beloved bramble!
Thanks. I've installed it and will report back.
Much appreciated.
Works perfect since yesterday
So far so good. Battery life seems to have improved which is very nice. Thanks so much for the awesome kernel!
I know this may be a dumb question, but how do I enable Wire guard? Do I need to install a separate client?
Appreciate your work.
I just installed and it seems to have disabled zRAM according to Ex Kernel Manager and FKM. Is it because of the change to z3fold? and if so, are there any apps that could help monitor this?
Also, I was curious if there's any chance you will eventually add color control and high brightness mode like in cleanslate?
PhantomCoder24 said:
So far so good. Battery life seems to have improved which is very nice. Thanks so much for the awesome kernel!
I know this may be a dumb question, but how do I enable Wire guard? Do I need to install a separate client?
Click to expand...
Click to collapse
To use the kernel-backend of WireGuard, install the WireGuard app from GPlay/F-Droid and provide root access when asked. You can check which backend you are using if you go into WireGuard's settings.
mistermojorizin said:
I just installed and it seems to have disabled zRAM according to Ex Kernel Manager and FKM. Is it because of the change to z3fold? and if so, are there any apps that could help monitor this?
Click to expand...
Click to collapse
I'll need to look into that, thanks for bringing it up. zRAM should still be visible in those applications with any backend, by the way.
mistermojorizin said:
Also, I was curious if there's any chance you will eventually add color control and high brightness mode like in cleanslate?
Click to expand...
Click to collapse
I've been thinking about that, and while HBM seems to be a good addition I'm not a fan of colour control within the kernel. If it's an important feature for many users, I'll add it and just build a separate kernel for myself.
LazerL0rd said:
Let's get this out of the way, I'm not responsible for anything more than a kernel panic.
Now that we've got that over with, I introduce to you - Zest Kernel. This ain't your average kernel on XDA. Zest Kernel is tuned down to every last mmap() to ensure that your device runs as fast and smooth as your hardware permits. No longer are the days of your battery dying on the bus, slow network speeds at home, or lags when swiping on those hot, new Android 11 gestures. Zest Kernel will revamp the experience of your device.
Spoiler: Here's what you get with Zest Kernel ꜰᴏʀ ʙʀᴀᴍʙʟᴇ.
Boot Time
By shrinking the kernel's size with Dead Code Elimination (DCE) and removing a bloat of debug and unused drivers, we decrease boot times [1].
LLVM Tools
Zest Kernel is built exclusively with the LLVM toolchain and tools, which allows us to utilise a wide range of security and performance features as well as satisfying my LLVM fanboy needs.
Networking Performance
Due to the addition of the rmnet_perf and rmnet_shs drivers from Qualcomm, cellular networking performance can see improvements due to network aggregation.
Performance
Through backporting mainline improvements to mmap() and locking, the kernel's core code receives improvements in performance and works to reduce jitter and improve system responsiveness. The return of BPF JIT allows us to improve performance with eBPF programs that Android utilises. As well as these changes, Danny (kdrag0n)'s efficient frequencies and Sultan's latency reduction patchsets are included which improve system fluidity and performance. LTO is also enabled, improving overall kernel performance. Tuning for ext4
Security
Zest Kernel utilises Clang's Control Flow Integrity (CFI) to protect against undefined behaviour that tries to subvert the kernel's control flow. Clang's ShadowCallStack, which protects programs against return address overwrites such as stack overflows, is also switched on and enabled with virtually mapped call stacks. All locals that are automatically initialised with zeros instead of patterns, which is safer for strings, pointers, indexes, and sizes. WireGuard is also included to provide a secure, performant VPN tunnel for those who wish to use it.
zRAM Improvements
Backports from mainline and changes from Sony allow us to utilise a more efficient zRAM backend, z3fold. While zRAM is only used on bramble, since 8GB is more than enough memory on redfin, this should provide a nice improvement for zRAM on bramble.
[1] - The first boot may take longer as F2FS (the filesystem we use) needs to check for corruption every time the kernel is changed for safety measures. Subsequent boots should be much faster.
Spoiler: How to install Zest Kernel ꜰᴏʀ ʙʀᴀᴍʙʟᴇ.
1) Make sure you're on the December or January SP.
2) Download Zest Kernel from the link below.
3) Enter fastboot (not fastbootd) with adb reboot bootloader or another method.
4) fastboot boot "Zest Kernel.img"
5) Yes, I said boot not flash. I hope you read that correctly.
6) Read my beautiful installation header and wait for your device to boot up.
Spoiler: Download Zest Kernel ꜰᴏʀ ʙʀᴀᴍʙʟᴇ directly from my site.
https://thebox.thezest.dev:61447/s/Sy2sM26HKtBHB3q?path=%2FBuilds%2FZest%20Kernel%2Fbramble
Spoiler: Where to get the source code of Zest Kernel ꜰᴏʀ ʙʀᴀᴍʙʟᴇ.
GitHub - lazerl0rd/tryme_redbull: A kernel for the Google Pixel 5 tuned to enhance system responsiveness, efficiency, and security.
A kernel for the Google Pixel 5 tuned to enhance system responsiveness, efficiency, and security. - GitHub - lazerl0rd/tryme_redbull: A kernel for the Google Pixel 5 tuned to enhance system respons...
github.com
Spoiler: Some screenshots of Zest Kernel ꜰᴏʀ ʙʀᴀᴍʙʟᴇ.
View attachment 5193437
View attachment 5193439View attachment 5193441
View attachment 5193443View attachment 5193445
Spoiler: Notable credits for Zest Kernel ꜰᴏʀ ʙʀᴀᴍʙʟᴇ.
Sultan Alsawaf (kerneltoast/@Sultanxda) for his patchsets which help to improve the fluidity of graphics and more.
Danny Lin (@kdrag0n) for kramflash (the kernel installer) as well as a load of useful patches.
Jason Donenfeld (@zx2c4) for WireGuard.
Artem Labazov for his suggestion to use z3fold as a backend for zRAM.
***
If you enjoyed Zest Kernel, please donate to help keep up maintenance at https://paypal.me/paydiab. I'm strict on quality, and give each release it's quality time and care (possibly even more so than your OEM). Having a small income from these kernels gives me a better incentive to keep pushing them out for y'all.
***
Click to expand...
Click to collapse
Can i relock bootloader after flashing the kernel ?
MegaJuif said:
Can i relock bootloader after flashing the kernel ?
Click to expand...
Click to collapse
AFAIK No!
Do not relock the bootloader unless the firmware is 100 percent stock. You might brick your phone, if it is not 100 percent stock when you relock the bootloader.
Homeboy76 said:
AFAIK No!
Do not relock the bootloader unless the firmware is 100 percent stock. You might brick your phone, f it is not 100 percent stock when you relock the bootloader.
Click to expand...
Click to collapse
aw, so if i install the kernel google pay wont work anymore ?
I tested the kernel on my smartphone for several days (firmware stock, bootloader open, magisk and root installed), everything is fine. Smartphone performance is faster and better battery drain.
Only there is one caveat - adaptive charging does not work at night, it worked on the stock core.
Measurements were made using Accubattery and 3C programs
MegaJuif said:
aw, so if i install the kernel google pay wont work anymore ?
Click to expand...
Click to collapse
custom kernel does not affect Gpay payment in any way. Unlocking the bootloader affects.
to pay, you need to install Magisk and some modules.
The topic has been discussed many times.
MegaJuif said:
Can i relock bootloader after flashing the kernel ?
Click to expand...
Click to collapse
Unfortunately you can't, sorry.
Homeboy76 said:
AFAIK No!
Do not relock the bootloader unless the firmware is 100 percent stock. You might brick your phone, if it is not 100 percent stock when you relock the bootloader.
Click to expand...
Click to collapse
I think he's noticed ROMs liek Calyx ship lockable ROMs for Pixel devices, this is possible but the entire ROM (inc. the kernel) needs to be signed with a single key - which can't eb done with my installation method unfortunately.
Thanks for all your support with Zest Kernel, and the lovely messages on XDA. Today I've released an update to Zest Kernel for redfin and bramble. The changelog is as follows:
- A bug which caused stuttering and high jitter randomly has been fixed, jitter should stay consistently low now.
- Improvements to the security of your device, with hardening inspired by GrapheneOS and the linux-hardened project.
As always, if you wish to donate my PayPal is available at https://paypal.me/paydiab. It's a great help for those of you who do, as I put in quite some time into my kernels.
LazerL0rd said:
Today I've released an update to Zest Kernel for redfin and bramble.
Click to expand...
Click to collapse
For bramble, did you make any changes that would re-enable the zram?
mistermojorizin said:
For bramble, did you make any changes that would re-enable the zram?
Click to expand...
Click to collapse
It should be working now (I noticed a mistake in the old builds) but if it doesn't, send me a PM and I'll try my best to release a bugfix by tomorrow evening.