{
"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_naro-7.2 (cortex-a15 neon-vfpv4 hard-float targeted, build with latest Crosstool-NG from developer snapshot Linaro GCC 7.2-2017.10)
Full -O3 support with device and target flags enhanced, linaro build improvements, etc
Less is more: stockish builds based on android-msm-hammerhead-3.4-marshmallow-mr3
Kernel compressed with XZ, custom tweaked RAMdisk with GZIP (faster boot times)
Removed some debug and logging options
Enhanced performance and battery patches
Several CPU Governors (blu_active own governor is default- fastlane mode available!)
Voltage Control UV_mV_table (UV down to 700mV possible)
Enhanced TCP methods (westwood is default), Network and Wifi tweaks
Several I/O control (added FIOPS and ZEN is default), tweaked filesystems (F2FS, ExFAT, NTFS & CIFS available)
Disabled stock mpdecision and thermald
blu_plug: Dynamic hotplug for hammerhead
msm_thermal simple driver (default 65º C threshold)
Optimized RWSEM, AES and SHA1 routines (with neon support)
Vibrator Strength tunable (60% default)
KGSL fixes and reworked GPU driver (removed doubled freqs, goes to idle @ 27MHz), Simple GPU Governor by default
Gamma Control and KCAL - Advanced color control for Qualcomm MDSS (RGB calibration and post-processing features)
Backlight dimmer ready (disabled by default, tuned min manual brightness - level 3)
Wakelock blockers available
USB automount (ROM must support it, otherwise use stickmount)
CDROM emulation added to mass_storage (Drive Droid compatible)
Kexec (multirom) full support
doubletap2wake available (0:disabled, 1:enabled, 2:enabled fullscreen), option to disable with power button or after wake_timeout
USB Fast Charge (USB mode up to 900mA with MTP, Increase battery charging current to use higher input current on AC mode, proprietary charger detection
init.d support (put your scripts in /system/su.d or /su.su.d [systemless SuperSU], /magisk/.core/post-fs-data.d [Magisk])
Compatible with Kernel Adiutor, Universal Kernel Manager and others
DOWNLOAD KERNEL ZIP (no mirrors please)
Warning: If you come from other kernel, you should dirty flash your ROM before flashing blu_sp★rk zip to avoid problems.
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. Also, I only actively support stock ROM with NO mods whatsoever (apart from root).
No support will be given to custom ROM including N stuff, so don't clutter the thread with it (specially):
No talking about WiFi and N issues.
No talking about ROM related and misc N issues.
Save the SOT and battery stats/screenshots for general threads, here we deal with development, not personal tastes and results.
Also no OT about OTAs, apps, ROM bugs and other userspace stuff. There's threads for it, use them.
This kernel installer modifies your filesystem, backup your boot.img with TWRP if you want to go back to full stock (or you can fastboot boot.img or dirty flash your ROM also)
If you want to use F2FS, do the following (backup your data before attempt this, it will erase all your Data)
Flash TWRP with f2fs support and flash latest blu_sp★rk zip
Go to Wipe -> Advanced Wipe -> Select only Data -> Repair/Format File system -> Change partition type to F2FS
Go to Wipe -> Advanced Wipe -> Select only Cache -> Repair/Format File system -> Change partition type to F2FS
Reboot and profit
If you like my work, donations are always welcome (but not mandatory).
Don't forget to hit thanks, it's free
XDA:DevDB Information
blu_spark hammerhead, Kernel for the Google Nexus 5
Contributors
eng.stk
Source Code: https://github.com/engstk/hammerhead
Kernel Special Features: powered by sparky
Version Information
Status: Stable
Current Stable Version: r152
Stable Release Date: 2017-11-23
Current Beta Version: r141
Beta Release Date: 2017-09-13
Created 2015-08-10
Last Updated 2019-11-29
Nice! New kernels to play around with :highfive:
Quick question: Can I flash this over ElementalX without having to dirty flash my ROM?
Great kernel remember you from my N7 days
Gesendet von meinem Nexus 5 mit Tapatalk
absoluterebirth said:
Nice! New kernels to play around with :highfive:
Quick question: Can I flash this over ElementalX without having to dirty flash my ROM?
Click to expand...
Click to collapse
You should, it cleans other stuff from other kernels, just try :good:
Tommy-Geenexus said:
Great kernel remember you from my N7 days
Gesendet von meinem Nexus 5 mit Tapatalk
Click to expand...
Click to collapse
Great to see you here mate:good:
Just flashed it over PA. So far so good! Will be reporting back in a few days on the kernel's overall performance and battery life.
Sent from my Nexus 5 using Tapatalk
Woot! Nexus 4 memories! Flashed right away, awesome!!
Thanks so much! Nexus 4 and 7 memories
Gesendet von meinem Nexus 7 mit Tapatalk
Stylez Ray. said:
Woot! Nexus 4 memories! Flashed right away, awesome!!
Click to expand...
Click to collapse
MöCkY said:
Thanks so much! Nexus 4 and 7 memories
Gesendet von meinem Nexus 7 mit Tapatalk
Click to expand...
Click to collapse
Good to see ya mates :good:
eng.stk said:
You should, it cleans other stuff from other kernels, just try :good:
Click to expand...
Click to collapse
The reason I ask this is because the ROM I use comes with ElementalX. So, I'm not sure what I'm really suppose to do :silly:
Is there compatability with CAF ROMs like CM?
-DarkKnight- said:
Is there compatability with CAF ROMs like CM?
Click to expand...
Click to collapse
The current version is for aosp only
Gesendet von meinem C6603 mit Tapatalk
Thanks for back!
Installed a lot of purified kernels in my Nexus 4
Send from my Purified Nexus 5
absoluterebirth said:
The reason I ask this is because the ROM I use comes with ElementalX. So, I'm not sure what I'm really suppose to do :silly:
Click to expand...
Click to collapse
It cleans stuff from elementalx, you should be fine
Hey guys,
Just a forewarning - I tried flashing this kernel on top of my current setup. I'm running the latest Mahdi ROM, and was previously using Uber kernel saber 4.9. I used TricksterMod to set the settings, but before I flashed this kernel, I made sure to turn off the setting that keeps my previous kernel settings locked for the next boot.
After I flashed Purified, my phone booted fine, but got stuck at the boot animation. No biggie, so I just restarted it. Happened again, so I went into recovery to try to reflash my ROM to get back the stock Mahdi kernel then try flashing Purified again. However, I get an error message saying "E: Can't mount /sdcard".
I'm kinda stuck now...this is the first time I've experienced a soft brick like this. Does anyone know how to fix this? I can't even go back and restore my old ROM and kernel setup because of that error message.
EDIT:
Sorry, kinda freaked out just now because I've never had so few options for recovery. No access to reflashing my ROM, no access to nandroiding. I tried ADBing, but couldn't set it up right and my device wouldn't load.
Out of desperation, I factory/data resetted, rebooted, got stuck at the boot animation screen, rebooted back to recovery, then tried accessing the sdcard again. ...somehow that did it. My sdcard was back and I nandroided. I still don't really know what caused this to happen.
I'm guessing, next time just to be safe, reflash the ROM, and then flash over this kernel?
@eng.stk
Thank you and welcome :good:
Ah,finally! Thank you @eng.stk
What the main differences between this release and the default Purity kernel? I know you and @DariosF work together from time to time and he has implemented some of these features into the default purity kernel.
---------- Post added at 06:11 PM ---------- Previous post was at 06:07 PM ----------
Jephre said:
Hey guys,
Just a forewarning - I tried flashing this kernel on top of my current setup. I'm running the latest Mahdi ROM, and was previously using Uber kernel saber 4.9. I used TricksterMod to set the settings, but before I flashed this kernel, I made sure to turn off the setting that keeps my previous kernel settings locked for the next boot.
After I flashed Purified, my phone booted fine, but got stuck at the boot animation. No biggie, so I just restarted it. Happened again, so I went into recovery to try to reflash my ROM to get back the stock Mahdi kernel then try flashing Purified again. However, I get an error message saying "E: Can't mount /sdcard".
I'm kinda stuck now...this is the first time I've experienced a soft brick like this. Does anyone know how to fix this? I can't even go back and restore my old ROM and kernel setup because of that error message.
Click to expand...
Click to collapse
Try mounting options in TWRP, also try a fix permissions.
Jephre said:
Hey guys,
Just a forewarning - I tried flashing this kernel on top of my current setup. I'm running the latest Mahdi ROM, and was previously using Uber kernel saber 4.9. I used TricksterMod to set the settings, but before I flashed this kernel, I made sure to turn off the setting that keeps my previous kernel settings locked for the next boot.
After I flashed Purified, my phone booted fine, but got stuck at the boot animation. No biggie, so I just restarted it. Happened again, so I went into recovery to try to reflash my ROM to get back the stock Mahdi kernel then try flashing Purified again. However, I get an error message saying "E: Can't mount /sdcard".
I'm kinda stuck now...this is the first time I've experienced a soft brick like this. Does anyone know how to fix this? I can't even go back and restore my old ROM and kernel setup because of that error message.
Click to expand...
Click to collapse
Looks like you got something wrong with your ROM, just dirty flash it
Sent from my Nexus 5 using Tapatalk
eep2378 said:
Ah,finally! Thank you @eng.stk
What the main differences between this release and the default Purity kernel? I know you and @DariosF work together from time to time and he has implemented some of these features into the default purity kernel.
---------- Post added at 06:11 PM ---------- Previous post was at 06:07 PM ----------
Try mounting options in TWRP, also try a fix permissions.
Click to expand...
Click to collapse
Me and Dario work almost everyday together, we made stuff for almost every Nexus (at least).
The diferences are in OP, I use same base but to a diferent end.
Sent from my Nexus 5 using Tapatalk
eng.stk said:
Me and Dario work almost everyday together, we made stuff for almost every Nexus (at least).
The diferences are in OP, I use same base but to a diferent end, lot's of stuff added, lot's of tweaks.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Sent from my Nexus 5 using Tapatalk
Related
{
"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"
}
Never skip LAG-day - Live on the EdgeSupported: G925T & G925W8 (Based on sources for International - F -
Code:
###Disclaimer###
Your warranty is now void.
We are not responsible if your phone will be damaged, broken, bootlooping or detonating in a thermonuclear reaction.
YOU are choosing to make these modifications and accept the fact that something might go wrong.
Introduction
SimplKernel is developed by SimplTeam. We originate from the Note4 and have a long story of success there. Our builds are known for being close to stock, yet full of useful features and enhancements. The aim is to provide maximum performance and maximum batterylife. No compromises.
Features
# Based on latest G925FXXU1AOE3
# NightClock fully fixed
# Compiled with AARCH64-Android-4.8 toolchain - Kudos Google, this is one is awesome
# Replaced CPU_FREQ_RELATION_L with C for Interactive -> selects freq with min euclidean distance to target freq, should be more efficient
# MDNIE ColorControl
# VoltageControl (CPU, GPU, HPM, BUS)
# Underclocking by default
# Full Synapse Support
# SELinux mode set to Permissive
# Governors added: powersave, intellidemand, ondemand, bluactive and intelliactive
# busybox and init.d
Click to expand...
Click to collapse
--> More will be added, this is just the start :angel:
Changelog
Code:
R4T/W8 - Same as R4F
R4F
- Based on G925FXXU1AOE3
- Busybox updated to 1.23.2
- NightClock fixed
- GPS Fix for AOE3 based Firmwares
- Synapse included
- Enabled Synapse Support
- mDNIE Control -> Control your DisplayColors! Will be expanded.
- Governor selection for individual cluster (A53 & A57)
- Full CPU VoltageControl for both A53 & A57
- Underclocking to 200mhz enabled by Default
- HPM VoltageControl
- GPU VoltageControl
- Memory Bus, Internal Bus & Image Signal Processor VoltageControl
- mDNIE Tab in Synapse (name is Screen)
- I/O Scheduler settings (Tunables + Definable Read-Ahead)
- BFQ and Deadline I/O scheds added*
- BFQ as default
- VirtualMachine Tweaks
- Full Synapse Settings Backup added
- Fixed 2 GPIO memory leaks + 3rd probable leak
- Memory-killer enhancements (see Github)
- GPU Throttling Levels smoothened
- more stuff I forgot
R2.9F
- Added Overclock and Underclock (@ktoonsez) - Only in Ktweaker for now!
- Added VoltageControl
- Fixed the NightClock - Display is now fully turning off (Switch from MDNIE_LITE to MDNIE)
- DynamicMemoryAllocation: Reduce max PAGE_SIZE to 4 and CMA areas to 4
- Minor tweaks here and there, check my github :D
- Synapse support for 2.9F withdrawn - This build is a patch for NightClock users! R3F coming soon too..
- Added KTweaker for this build - @Ktoonsez ;)
v1.2F/T/W8
- Added T-Mobile, Canadian and I variants (T, W8 & I)
- Added Synapse Support
- Automatized Wifi-Forgetting fix in the ramdisk
- Ported MDNIE HIJACK (ColorControl) - Basic settings for now
- Reverted previous DeepSleep workaround and applied proper patch
- Added awesomeness
v1.1F
- Patched the DeepSleep problem / thanks to @HomerSp for this
- Added governors: Bluactive, Intelliactive, MythX (disabled) and enabled powersave + ondemand
- Added busybox and init.d
- CPU_FREQ_RELATION_C: When scaling freqs, it selects the freq with the minimum euclidean distance to target.
How to install
Via recovery
You have to have a custom recovery like TWRP, Philz or CWM installed.
- Download the kernel
- Reboot to recovery
- A backup is always recommended
- Flash the zip file
- You're done! Reboot and enjoy.
Via Flashify
- Make sure that you are rooted.
- Download the zip and extract the boot.img
- Download the free app Flashify (Caution: Free Version only allows 3 flashes per day!)
- Grant Flashify Root permissions.
- In main screen, select Boot image and navigate to the previously extracted boot.img
Downloads
T-Mobile, Canadian (T & W8): (R4T/W8)
Latest R4T/W8 click here (version with MDNIE and possible viewfinder distortion
Click to expand...
Click to collapse
Please do not make mirrors! If you need one, please post a reply here, and we'll make it happen. Thanks.
If you apply Interactive in Synapse, ALWAYS enable it for both clusters. Enabling it for only one will cause funny effects, perhaps even a solid chaos, batterydrain and other unpleasant things. You've been warned.
Credits
S6 Edge Tester-Team: For doing what no one did before, flashing a never tested build and going through huge pains to help me. It wouldn't be possible without any of you! :angel:
@strikerdj2011
@jaytehnut
@Briz0wn
@charlypaez
@sswagonman
@ShermCraig
@beats4x
@ktetreault14
@nvict
@skivnit
@leoaudio13
@xadidas4lifex
@reesedizan
XDA:DevDB Information
SimplKernel, Kernel for the T-Mobile Samsung Galaxy S6 Edge
Contributors
mythos234
Source Code: https://gitlab.com/mythos234/SimplKernel-LL-G925F
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: R4T
Stable Release Date: 2015-05-24
Created 2015-05-25
Last Updated 2018-06-05
Awesome.... Thanks for you contribution can't wait to try it out.
I'm I wrong does this kernel fix the memory leak
winco209 said:
I'm I wrong does this kernel fix the memory leak
Click to expand...
Click to collapse
"The leak" - There are more leaks than either of us can count, some little ones here and there, and all of them hidden. Unlikely that there ever will come a time that there are no leaks at all
But I guess that you are reffering to the major leak with 5.0? That is in the Rom and framework afaik, and thus not my department to fix. I'm not even sure if 5.1 has the proper fix merged to be honest :/
Flashed on top of Alliance v3, a T-mobile based ROM. Everything is super smooth, call audio is fine, GPS test can't see any satellites. Will try some more stuff to see if I can get it to work and then report back.
EDIT:
Flashed the GPS fix from mythos in the international thread.
That post is here: http://forum.xda-developers.com/showthread.php?p=60932260
Just flashed and rebooted, didn't even wipe cache / dalvik. Worked like a charm!
mythos234 said:
"The leak" - There are more leaks than either of us can count, some little ones here and there, and all of them hidden. Unlikely that there ever will come a time that there are no leaks at all
But I guess that you are reffering to the major leak with 5.0? That is in the Rom and framework afaik, and thus not my department to fix. I'm not even sure if 5.1 has the proper fix merged to be honest :/
Click to expand...
Click to collapse
sorry off topic, but do you think we will get miui ported over to here at some point?
kswa1987 said:
Flashed on top of Alliance v3, a T-mobile based ROM. Everything is super smooth, call audio is fine, GPS test can't see any satellites. Will try some more stuff to see if I can get it to work and then report back.
EDIT:
Flashed the GPS fix from mythos in the international thread.
That post is here: http://forum.xda-developers.com/showthread.php?p=60932260
Just flashed and rebooted, didn't even wipe cache / dalvik. Worked like a charm!
Click to expand...
Click to collapse
Good to hear
srkoza said:
sorry off topic, but do you think we will get miui ported over to here at some point?
Click to expand...
Click to collapse
My profile pic, isn't it? Usually there are votings held in the english MIUI forum to decide which phone will (first) get an official port. By the amount of development and users on XDA, I'd put my bets rather on the edge-less S6. But since we can run their Roms too that should not be too big of a problem.
Then again the official 3rd party MIUI not always is a shining light at the horizon. I never liked it. If there are bugs, they won't always get fixed, very frustrating, but understandable - MiPhones do have priority. As to unofficial porting.. I have literally no idea, but it would be nice to see some CM12.1 and MIUI over here, altough I somehow doubt the latter..
mythos234 said:
Good to hear
My profile pic, isn't it? Usually there are votings held in the english MIUI forum to decide which phone will (first) get an official port. By the amount of development and users on XDA, I'd put my bets rather on the edge-less S6. But since we can run their Roms too that should not be too big of a problem.
Then again the official 3rd party MIUI not always is a shining light at the horizon. I never liked it. If there are bugs, they won't always get fixed, very frustrating, but understandable - MiPhones do have priority. As to unofficial porting.. I have literally no idea, but it would be nice to see some CM12.1 and MIUI over here, altough I somehow doubt the latter..
Click to expand...
Click to collapse
i hope so and yes it was the display picture, im also polish noto dziendobry
No wifi calling I assume?
Woohoo!!
This is going to sound strange, but how do I go about deleting synapse? I've completely reflashed my ROM and it keeps reinstalling itself and I don't want it.
Sent from my SM-G925T using Tapatalk
Awesome update. Thanks.
Malnilion said:
This is going to sound strange, but how do I go about deleting synapse? I've completely reflashed my ROM and it keeps reinstalling itself and I don't want it.
Sent from my SM-G925T using Tapatalk
Click to expand...
Click to collapse
Delete its folder from your sd card and myapps on google play. That should fix it.
Daxxer2007 said:
Delete its folder from your sd card and myapps on google play. That should fix it.
Click to expand...
Click to collapse
Also in /data, delete .simplkernel
Thats new
is bluactive governor a good choice for battery or performance?
never used it before
thanks!
wase4711 said:
is bluactive governor a good choice for battery or performance?
never used it before
thanks!
Click to expand...
Click to collapse
Never tried it, to be honest. I always stick with Interactive
tigercranestyle said:
thx for the kernel, @mythos234 . smooth as butter.
only one thing i've noticed, but it's not isolated to just your kernel. i've had this issue periodically in the past on nexus devices using aosp roms. it always came back to an issue in the kernel... not the rom. this issue is also present in another kernel in the forums for the s6 edge.
the issue is with google play movies not working. the app will open and you can select a movie, but a few seconds after hitting the play button there is a black screen and then it errors out. it doesn't matter if you are streaming the movie or if it's a downloaded one. black screen and then an error.
i've attached a log of the errors.
oh... i'm running simplrom btw.
thx, brosef.
Click to expand...
Click to collapse
Awkward. I'll take a look at it R5 is coming soon as well. It will be called R5U - The U is for Awesome Unified
I dont seem to be able to get bluactive to stick after switching to it; is there a trick to making it active?
I clidk the check mark after changing to it, but after a reboot, its back to interactive..
thanks! This kernel works great on international/s^/Tmobile any rom I have tried it on! :good::good:
wase4711 said:
I dont seem to be able to get bluactive to stick after switching to it; is there a trick to making it active?
I clidk the check mark after changing to it, but after a reboot, its back to interactive..
thanks! This kernel works great on international/s^/Tmobile any rom I have tried it on! :good::good:
Click to expand...
Click to collapse
Did Synapse boot up correctly or did it say something like "Synapse boot cancelled" in the form of a standard toast message?
it does at first, but then it seems to get SU permission, and appears to load correctly...
thanks!
---------- Post added at 06:57 PM ---------- Previous post was at 06:54 PM ----------
Actually I just tried again and I think I got it to work!!!
Sent from my SM-G920T using Tapatalk
How come when I wipe both caches and fix permissions on the kernel after using it for a couple days it makes my battery go to 0% when I boot back up when I knew I still had about 40% left before I did that? Thanks
Sent from my SM-G925T using XDA Free mobile app
Hello guys!
My work on Z1 is done. I will provide little to no support. I moved on to S8+
Some of you may have tried my custom kernel, I have now made another one (I've been running it for like half a year, couldn't decide whether to release it or not).
With this kernel I put stability on first place, then battery life, then performance. Don't expect flashy stuff. If it breaks anything or is cumbersome to implement then I won't do that.
Changelog:
Changes in V8.3:
Fixup code indentation to get rid of all the warnings during compilation.
Final release
Changes in V8.2:
Disable selinux spam in dmesg, it's permissive so AVC messages are unnecessary. That should improve both performance and battery, might not matter at all.
Replaced most of MMC code with one plus one's, that should massively improve internal memory handling.
Replaced the entire qdsp6v2 code with OPO's - this improved mic a million, speakers also seem to work better
Reworked cpu calculations a bit
Changes in V8/1:
Fixed most of sdcard issues - it is now the best kernel to use with SDcards
Replaced most of outdated camera code with One Plus One code, which should improve camera usage massively.
Changes in V7.5(unreleased):
Fixup code formatting
Enable booting with idle GPU freq - 27MHz
Enable stereo call recording thanks @DooMLoRD
Update prima/pronto (wifi drivers) to latest ones
Remove WiFi debugging - useless, provides better battery and performance
Fix NEON and VFP functions to work earlier on boot
Implemented Adreno Idler - helps with GPU Idling
Simple GPU Algorithm by @faux123 - this enables better GPU freq scaling
Implemented msm-sleeper, that allows for lower CPU freqs and less used cores with screen off.
Fixup of fast-charge
better handling of powersuspend based on display state
Changes in V7:
Implemented Intellithermal_v2
Added fast charge as requested, I didn't see much change in charging times to be honest and people have said its not safe to use, but it's there.
Possibly brought back breathing notifications.
Changes in V6.5:
Updated toolchain to linaro 6.2.1
Use hard float and neon FPU - this might provide quite an improvement to overall performance and battery life
Update device ramdisk to actual .236 - all booting issues should be gone along with update nagging
Update TWRP to 3.2
Changes in V6.2:
New bootlogo by IRL friend.
Changes in V6.1:
This is mostly a bugfixing version
Added additional last_kmsg support
MX ROM users - PLEASE SEND LAST_KMSG from this version, it still won't boot yet, so make a backup of your previous kernel in TWRP!
New features in V6:
TWRP 3.0.0.0 (No multirom version yet, let me know if you really need it!)
3x faster int sqrt
selinux fixes
Bigger interval of battery level check
More conservative readahead
Send one packet at a time for touchscreen
Power efficient work queues (better cpu task queuing)
Low memory killer - starts caring about high ram
Faster camera startup and operation
Memory aligning to sector size
GPU optimization flags
Better managment of writing files back to memory
CPU freq/gov fixes
msm limiter - allows for better limiting of cpu freq
Update wifi driver (supposedly)
Update toolchain to Linaro 5.2, latest stable Linaro toolchain!
Change display colors to get less yellowish/warm colors thanks @tomascus !
Please go into white balance in system and reduce blue to around 110 for better white.
GCC 5 cortex a15 CPU optimizations
Notification LED API, from now on it's pulsing instead of blinking on notification
Remove RIC from ramdisk init (this should fix booting issues for some)
Removed few unused defconfig entries
Boost CPU freq when migrating threads from one cpu to another
From V6 I'm packing ramdisk on every kernel build
Using latest sony mkqcdtbootimg, that should improve stuff with boot.img DT's.
Noop is a default I/O sched. It's very good for spindleless disks (Flash memory, SSD's)
Force permissive selinux at all times. It won't go to restrictive anymore.
use memcpy, memmove, copy_page memory optimizations for MSM8974.
Fixed idle cpu calculations
Lots of EXT4 filesystem fixes
Very optimize
Much fast
So battery
Wow
New features in V5:
Further improved sdcard speed
Now compiling Prima WiFi driver with kernel. Faster and more stable WiFi.
New governor - Intelli MinMax - my favourite for now
Finally implemented Intelliplug 4.0 - default hotplug mpdecision replacement by faux123
Corrected notification LED brightness levels
Cleaned up the source a bit
Features of V4:
latest 14.6.A.1.216 source code
Enabled higher eMMC frequencies
disabled cpu boost on screen wakeup
optimized code to get lower CPU usage overall (not by removing anything or slowing stuff down!)
very low minimum screen brightness on the minimal brightness (disable automatic brightness for that and move slider all the way to the left)
Faux's Sound control
Kcal Color control
RIC disabled by default
corrected reported GPU frequency
conservative and ondemand optimizations
Venkat Kamesh's ramdisk that allows flawless multiboot + my own bootlogo (pretty funny )
General performance improvements
gpu optimizations
optimized for Cortex A15 cores (just like krait)
Linaro 4.8 toolchain instead of the GCC 4.7
OOM optimizations
memory optimizations
stability fixes
general performance improvements
intelliactive governor
config.gz viewable in /proc
Nvidia Shield cpu power patches - great battery improvement
added new, shiny quickwakeup and powersuspend drivers that help improving battery life even further
MultiRom Support
MultiRom TWRP
Fixed in kernel random numbers generation - seeder is completely not needed with my kernel.
Download:
V8.3 here - 25.07.2017
V8.3 MULTIROM TWRP here - 06.08.2017
Previous versions
V4 here - 30.12.2015
V5 here - 26.01.2016
V6 here - 14.04.2016
V6.1 here - 07.06.2016
V6.2 here - 11.06.2016 [url=https://www.androidfilehost.com/?fid=24694152805484499]MIRROR[/URL]
V6.5 here - 14.03.2017
V7 here - 17.06.2017
If you get a bootloop, random reboot, whatever, ALWAYS send me last_kmsg log - PRESS HERE for a guide on how to do this, if you don't do that, I won't fix it. Any post with something like "REBOOT, HALP PLS' or "BOOTLOOP, NO WORK" will be reported and then removed.
If you installed XZDR recovery before, some custom rom or you're just not coming from a stock clean rom,please flash THIS before flashing my kernel. It will remove RIC and remnants of XZDR recovery which prevents kernels from booting. Thanks to @venkat kamesh for original script and thanks to @Snp Mania2 for figuring out the problem!
Source code
OK Kernel V4 checksums
{
"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"
}
Many thanks to:
@venkat kamesh for his awesome ramdisk, I would be bashing my head on the wall trying to get multirom to work if not him.
@Tommy-Geenexus for getting my buildscript to work and for his awesome code. He made building the kernel a bliss for me.
@faux123 too many to point out
@DirtyUnicorn team for some commits.
Propably others that I forgot to mention. I will update credits soon.
As always, you do everything at your own risk.
Enjoy! :highfive:
Here's my configuration in Kernel Adiutor geared towards battery life while still being pretty smooth. buttery smooth on v5
My OK Kernel v4 configuration http://imgur.com/gallery/vXPUE
My OK Kernel v5 configuration http://imgur.com/a/m8gl6
Deep sleep from 5th march 2016 kernel v5.5
Screen on time of kernel V5
http://forum.xda-developers.com/showpost.php?p=65690403&postcount=107
thanks a lot for releasing it
will try and feed back soon
---------- Post added at 01:50 AM ---------- Previous post was at 01:10 AM ----------
@olokos
flashed through fastboot , OK kernel boot logo comes up and phone fall into bootloop
ok kernel comes up and restart and again and again...
(stock rom .216 build rooted with UB)
*: wiping cache and dalvik cache after flash didn't help...
Hey nice kernel buddy,
Just a heads up regarding breaking Wifi and external sdcard - if you look at the dmesg you can see that the wlan module and texfat module (and wp_mod and byeselinux too) get broken with some changes to kernel, so those modules would need to be compiled together with the kernel.
I believe texfat is proprietary (no source code =.= ) so the only choice would be to switch to another file system for ext SD such as vfat.
Wlan module is just a regular prima module, I took mine from a AOSP build, which is usually found in drivers/staging/ .
wp_mod and byeselinux has source code you can just compile from too if those break.
agha_jo0n said:
thanks a lot for releasing it
will try and feed back soon
---------- Post added at 01:50 AM ---------- Previous post was at 01:10 AM ----------
@olokos
flashed through fastboot , OK kernel boot logo comes up and phone fall into bootloop
ok kernel comes up and restart and again and again...
(stock rom .216 build rooted with UB)
*: wiping cache and dalvik cache after flash didn't help...
Click to expand...
Click to collapse
This sucks, especially since I'm running the very same setup as you do. Could you try updating your bootloader via Emma?
tomascus said:
Hey nice kernel buddy,
Just a heads up regarding breaking Wifi and external sdcard - if you look at the dmesg you can see that the wlan module and texfat module (and wp_mod and byeselinux too) get broken with some changes to kernel, so those modules would need to be compiled together with the kernel.
I believe texfat is proprietary (no source code =.= ) so the only choice would be to switch to another file system for ext SD such as vfat.
Wlan module is just a regular prima module, I took mine from a AOSP build, which is usually found in drivers/staging/ .
wp_mod and byeselinux has source code you can just compile from too if those break.
Click to expand...
Click to collapse
Thanks for the heads up, that's what's stopping me from getting intelliplug. Have you tried the kernel and lost wifi and external sdcard? Also, I think you meant exfat, not texfat, right?
It's so weird especially since both wifi and sdcard work for me and I haven't had any bootloop since the first build ?
olokos said:
This sucks, especially since I'm running the very same setup as you do. Could you try updating your bootloader via Emma?
Click to expand...
Click to collapse
Sure..
What is Emma!?
How should i do that?!
Sent from my C6903 using Tapatalk
olokos said:
This sucks, especially since I'm running the very same setup as you do. Could you try updating your bootloader via Emma?
Thanks for the heads up, that's what's stopping me from getting intelliplug. Have you tried the kernel and lost wifi and external sdcard? Also, I think you meant exfat, not texfat, right?
It's so weird especially since both wifi and sdcard work for me and I haven't had any bootloop since the first build ?
Click to expand...
Click to collapse
Nah I mean texfat, it's the default format used if you format it through normal settings. I haven't tried your kernel because i'm testing my own right now, but my WiFi and sdcard would be broken without custom compiled wlan and formatting my sdcard to another type.
Personally I have no idea how to get around this or if it is even possible,since the changes completely screw up files depended on by the modules
Sent from my C6903 using XDA Forums
agha_jo0n said:
Sure..
What is Emma!?
How should i do that?!
Sent from my C6903 using Tapatalk
Click to expand...
Click to collapse
http://developer.sonymobile.com/services/flash-tool/how-to-download-and-install-the-flash-tool/
Please also check boot.img checksums, you might have had a corrupted download. I've even downloaded it from dev host and it works like it should. I've added boot.img checksums to the 1st post, compare one of them with your boot.img.
tomascus said:
Nah I mean texfat, it's the default format used if you format it through normal settings. I haven't tried your kernel because i'm testing my own right now, but my WiFi and sdcard would be broken without custom compiled wlan and formatting my sdcard to another type.
Personally I have no idea how to get around this or if it is even possible,since the changes completely screw up files depended on by the modules
Sent from my C6903 using XDA Forums
Click to expand...
Click to collapse
I sent you a PM. I cannot use anything apart from exfat as I have a 128GB sdcard + it would be useless for my users. Please do try my kernel, just for a second or anybody else just to confirm that it works properly. @agha_jo0n had a bootloop and I want to make sure it's something on his side, not on the kernel side, as I mentioned, I didn't have a single boot issue with my kernel. The only problems I had were with WiFi and SDCard, but they should work properly with this release as it does work allright on my device. I even reflashed it like 30 minutes ago just to make sure.
olokos said:
I sent you a PM. I cannot use anything apart from exfat as I have a 128GB sdcard + it would be useless for my users. Please do try my kernel, just for a second or anybody else just to confirm that it works properly. .
Click to expand...
Click to collapse
I flashed it a while ago and all working fine so far wifi is fine, no boot loops, didn't even wipe dalvik .. considering it though, since viper4android is not working correctly. Your kernel is the only one though where I could make it work (install driver) I'll do a clean install of one of the .216 ROMs (currently I'm on DStriker's 001 release).
Edit: Flashed MXROM - did not boot after flashing kernel, flashed DStrikerZ1 Kai ROM 001 and voila all working V4A running as it should, ROM snappy as never, smooooooth as silk. Testing battery, will take a while though.
olokos said:
http://developer.sonymobile.com/services/flash-tool/how-to-download-and-install-the-flash-tool/
Please also check boot.img checksums, you might have had a corrupted download. I've even downloaded it from dev host and it works like it should. I've added boot.img checksums to the 1st post, compare one of them with your boot.img.
Click to expand...
Click to collapse
i redownload the file and also check md5. all was true
but the same as past time i felt into bootloop! i didnt now what casue problem
Great work man
But can je make one for the z1c stock5.1.1 rom. 8216
Yeah it's bootlooping at kernel logo for me as well @olokos
Your boot.img seems to be massive... not sure if that has anything to do with it though
Can I flash this via twrp? This kernel looks great and I really wants to try it.
Ohhdayumm said:
Can I flash this via twrp? This kernel looks great and I really wants to try it.
Click to expand...
Click to collapse
no,you should flash it through fastboot
Ohhdayumm said:
Can I flash this via twrp? This kernel looks great and I really wants to try it.
Click to expand...
Click to collapse
You need to flash it with flashtool (it's a img file)
Using mx rom phone stops at kernel bootlogo (tried also wipe dalvik)
[Fenix] said:
You need to flash it with flashtool (it's a img file)
Using mx rom phone stops at kernel bootlogo (tried also wipe dalvik)
Click to expand...
Click to collapse
I am using the same rom as you what happened when your flashed the kernel?
at least one report that it works, lol. Could sb link the roms that you get bootloops with? I'll check it with multirom.
And anybody that get bootloops. Could you please try updating your bootloader?http://developer.sonymobile.com/services/flash-tool/how-to-download-and-install-the-flash-tool/
olokos said:
at least one report that it works, lol. Could sb link the roms that you get bootloops with? I'll check it with multirom.
And anybody that get bootloops. Could you please try updating your bootloader?http://developer.sonymobile.com/services/flash-tool/how-to-download-and-install-the-flash-tool/
Click to expand...
Click to collapse
I use stock. 216 frimware
Sent from my C6903 using Tapatalk
olokos said:
at least one report that it works, lol. Could sb link the roms that you get bootloops with? I'll check it with multirom.
And anybody that get bootloops. Could you please try updating your bootloader?http://developer.sonymobile.com/services/flash-tool/how-to-download-and-install-the-flash-tool/
Click to expand...
Click to collapse
Did you get my inbox mate? It seems I can't send anything to anyone.
BatStock-Kernel for SM-G955F/FD/N models
{
"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"
}
Supports Touchwiz Roms with AQDD and higher
IF YOU FOLLOW MY STEPS BELOW, YOU WILL LOSE YOUR WARRANTY, KNOX WILL DISPLAY 0x1! I'M NOT RESPONSIBLE FOR ANY DAMAGED DEVICE!
If you want to take my work and need it somewhere, or do other things with it, ask me first for the permission. Otherwise you are not allowed to take it! Thank you !
Features of this Kernel:
- Build with latest self-made 6.3.0 GNU toolchain
- Build with AQF7 kernel source code
- Latest Linux version 4.4.76, is always up to date
- Performance and Batterylife improved
- Choose between different CPU governors: performance, powersave, userspace, ondemand, interactiv (default), conservative, schedutil
- Includes latest AQF7 ramdisk
- I/O schedulers: CFQ (Default), No-op, Deadline
- F2FS enabled for /data and /cache disabled on 1.2.2 for testing
- NTFS enabled
- TCP (Network) control: Bic (default), Reno, cdg, cubic, dctcp, Westwood, Highspeed, Hybla, HTCP, Vegas, Veno, Scalable, LP, Yeah, Illinois, Lia, Olia, Wvegas, balia
- SeLinux is set to permissive
- All samsung security related configs disabled (as knox, tima, restrict rooting)
Download:
V1.2.2 on AndroidFilehost
Bugs/Problems:
- None
Instructions:
0. Have a working recovery and encryption removed!
1. Download kernel
2. Boot into twrp recovery mode
3. Flash kernel
4. Flash any other file which affects ramdisk (Magisk or SuperSU)
5. Reboot
If you wanna join the beta tester group, download yourself telegram and click on the chat link: Telegram Group
Support:
If you like my work, feel free to hit thanks and/or give me a small donation by clicking the link right below. Thank you very much in any way! :good:
PayPal
Credits/Thanks:
- Samsung for sources
- the great linus for his amazing kernel source
- Jesec for his workaround, without him custom kernels won't be possible on the s8!
XDA:DevDB Information
BatStock-Kernel SM-G955F, Kernel for the Samsung Galaxy S8+
Contributors
Tkkg1994
Source Code: https://github.com/Tkkg1994/BatKernel/tree/TW70-stock
Kernel Special Features: Close to Stock Kernel
Version Information
Status: Stable
Current Stable Version: V1.2.2
Stable Release Date: 2017-07-12
Created 2017-05-14
Last Updated 2017-07-12
Changelogs:
BatStock-Kernel V1.0:
- Initial testing release (not on XDA)
BatStock-Kernel V1.0.1:
- Fixed slow read speed
- enabled f2fs
- enabled ntfs
- enabled all included govs/tcp/ioscheds
- random driver updates
BatStock-Kernel V1.1.0:
- Based on latest AQE5 source code
- Updated ramdisk to AQEB
- Added init.d support
- Hopefully fixed some issues with shealth
- Updated linux to most recent 4.4.69
- Changes made by samsung in source code: led cover support, some other battery updates, display updates (mainly for red tint), other small fixes
BatStock-Kernel V1.2.0:
- Based on latest AQF7 release
- Updated ramdisk to AQF7
- Updated Linux to 4.4.74
- ext4: fix data exposure after a crash (which should maybe fix the random reboots)
- Updated included camera binaries
BatStock-Kernel V1.2.2:
- Reverted an alarmtimer update which could have broken some deepsleep things
- Added support for private mode
- Updated linux to 4.4.76
- Added stock init file (without being patched for f2fs, means f2fs won't work right now) to see if that has something to do with continous bootloops
Reserved
Reserved
No root :/
Gesendet von meinem SM-G955F mit Tapatalk
I lose wifi passwords with installing kernel ! And TB don't Reinstall the passwords !
Great kernel, performs better than Stock for me and works well with adoptable storage:good:
Thank you:laugh:
murat669 said:
No root :/
Gesendet von meinem SM-G955F mit Tapatalk
Click to expand...
Click to collapse
As you read per instructions in OP, you need to reflash Magisk or SuperSU. Did you even read them?
clodoux said:
I lose wifi passwords with installing kernel ! And TB don't Reinstall the passwords !
Click to expand...
Click to collapse
That's normal, will only happen if you come from stock kernel to custom kernel. Than it won't loose it anymore
Ok. Thanks. And it's normal that TB can't Reinstall the wifi passwords ? Thanks for all
Tkkg1994 said:
As you read per instructions in OP, you need to reflash Magisk or SuperSU. Did you even read them?
That's normal, will only happen if you come from stock kernel to custom kernel. Than it won't loose it anymore
Click to expand...
Click to collapse
(personally I'm really surprised at the comments popping up everywhere about wifi and bluetooth pairs being lost? Nothing changed from previous years. I wonder if it means that with the S8+ and S8 we have a alot more users who have decided root is the way to go)
@Tkkg1994
Thanks a lot mate.
Tkkg1994 said:
- All samsung security related configs disabled (as knox, tima, restrict rooting)
Click to expand...
Click to collapse
So, Is this good news for Samsung Pay users ?
Hey bud. After flashing your kernel I'm getting a bug in the Facebook app whereby if you are scrolling through comments on a thread the act of pressing on the screen to scroll continually gets picked up as a touch and hold event (i.e. edit post/copy post etc)
Given I didn't have the bug before flashing I have to assume it relates to changes made in your kernel.
Now interestingly I had exactly the same bug on my OnePlus 3 using AOSP or LOS so there must be a connection in the kernel config.
I'll try and pull a log.
clodoux said:
I lose wifi passwords with installing kernel ! And TB don't Reinstall the passwords !
Click to expand...
Click to collapse
Tkkg1994 said:
That's normal, will only happen if you come from stock kernel to custom kernel. Than it won't loose it anymore
Click to expand...
Click to collapse
clodoux said:
Ok. Thanks. And it's normal that TB can't Reinstall the wifi passwords ? Thanks for all
Click to expand...
Click to collapse
I have 2 questions :
1. Loosing the passwords is known consequence. But is there any working way to get them restored? TB doesn't work indeed...
2. What happens if one flashes a different kernel (stock or other custom kernel) again after flashing this kernel. I guess you'll loose them every time, right?
All samsung security related configs disabled (as knox, tima, restrict rooting) but why secure folder doesnt work.after flashing kernel pattern security doesnt work.I cant open with pattern.
JazonX said:
So, Is this good news for Samsung Pay users ?
Click to expand...
Click to collapse
vardar.baris said:
All samsung security related configs disabled (as knox, tima, restrict rooting) but why secure folder doesnt work.after flashing kernel pattern security doesnt work.I cant open with pattern.
Click to expand...
Click to collapse
No it isn't read my post here:
Tkkg1994 said:
Nope. Samsung has fixed this bug from the S7.
And most likely they will patch the s7 soon as well so we won't be able to use it.
On the s7 it was: hmmm kernel gives me no result, I think that means successfull passed.
Pretty stupid [emoji23]
Click to expand...
Click to collapse
kickassdave said:
Hey bud. After flashing your kernel I'm getting a bug in the Facebook app whereby if you are scrolling through comments on a thread the act of pressing on the screen to scroll continually gets picked up as a touch and hold event (i.e. edit post/copy post etc)
Given I didn't have the bug before flashing I have to assume it relates to changes made in your kernel.
Now interestingly I had exactly the same bug on my OnePlus 3 using AOSP or LOS so there must be a connection in the kernel config.
I'll try and pull a log.
Click to expand...
Click to collapse
Hey
Display driver is kept 100% stock and I haven't seen any problems in scrolling. Wouldn't say that it's related to kernel
tiho5 said:
I have 2 questions :
1. Loosing the passwords is known consequence. But is there any working way to get them restored? TB doesn't work indeed...
2. What happens if one flashes a different kernel (stock or other custom kernel) again after flashing this kernel. I guess you'll loose them every time, right?
Click to expand...
Click to collapse
It's because we switch off secure storage to false (from true on stock)
You loose it again each time you switch from secure storage true to false and vis a verse. This is mainly the cause from stock to custom not from custom to custom
this means we cannot use secure folder? I wnt to use it is there a way to use it
vardar.baris said:
this means we cannot use secure folder? I wnt to use it is there a way to use it
Click to expand...
Click to collapse
Seems No.
I was also sorta excited to wipe my device again, and Start from scratch with Magisk and this Kernel. However, My focus was on SamsungPay.
Anyhow knowing tkkg1994 from a long time, This kernel would do better than all other kernels.
also shealth doesnt works.can we do anything
JazonX said:
Seems No.
I was also sorta excited to wipe my device again, and Start from scratch with Magisk and this Kernel. However, My focus was on SamsungPay.
Anyhow knowing tkkg1994 from a long time, This kernel would do better than all other kernels.
Click to expand...
Click to collapse
Sadly this doesn't work anymore, I assume samsung will patch it also on the s7 soon (sadly)
vardar.baris said:
also shealth doesnt works.can we do anything
Click to expand...
Click to collapse
It works fine, using it since I got my phone
{
"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"
}
WARNING :
This kernel is for OnePlus 5 (cheeseburger)
Code:
You will NOT void your warranty after flashing this kernel.
Be sure to make all necessary backups first before processing to installation.
I'am not responsible of any damage caused to your device or data lost after flashing this kernel.
Of course, these are only basic warnings ! but generally you'll not get any problem :)[/COLOR][/FONT]
Some reading..
Welcome to SimpleGX kernel ! a kernel that aims for simplicity, stability, better performance, smoothness and battery life over a pure stock kernel.
This kernel is designed for people who are (like me) bored to flash kernels which integrate tons of unneeded things.
Main goals of it is to stay MUCH closer to stock than every kernels shared here and almost not to be a “custom kernel” on its own. So beware, no exotic stuffs here !
No need for any third app or whatever to control this kernel. Just "flash-n-joy" ! this is how I always liked thing.
Keep in mind that this kernel has been designed for my daily use first.
I would like to personally thanks @Lord Boeffla for his precious help to build my first OP5 kernel ! without him, this kernel won’t be there ! so please consider it.
As always, I'm enjoying sharing my contribution here on XDA for free, which taking me a lot of (my free) time to test before releasing. So, if you can offer me a little beer, it will be really appreciated!
This kernel must be only flashed over an official OnePlus 5 LineageOS (LOS) ROM !
Feel free to include my kernel to your ROMs / threads but please don't forget to inform/ask first via PM and credit me properly in your original thread. It's always appreciated.
★ WHAT TO EXPECT ★ :
(over a pure stock kernel) :
Better battery life
Overall better performance
Trying to include only efficient (but definitely no experimental) tweaks
Stay as close as possible from pure stock source
★ FEATURES (up-to-date) ★ :
Base :
Always directly based from latest available "android_kernel_oneplus_msm8998" Android 7.1.1 source from LineageOS / OnePlus 5 (for clean work)
Compiled with stock Google (4.9.x / aarch64-linux-android) toolchain (for best stability)
Featuring Anykenel2 (for all ramdisk compatibility)
Stock Linux 4.4.52
Main :
Kernel logger disabled
Fixed annoying minimum backlight level
Wakelocks control support (all wakelocks disabled by default)
Several fixes/optimizations patches for stock cpufreq_conservative governor
MAPLE I/O scheduler added (and set as default)
Completely optimized stock 'cfq' I/O scheduler
Xbox controller (and other USB pads) support
All TCP congestion control modules activated with Westwood currently as default
Removed verify and forced encryption + patched SafetyNet flags to pass CTS
Some miscellaneous tweaks, fix, patches and security patches to improve overall smoothness and battery life experience
Various tweaks :
Full changes to be discovered directly in my Github source below
Features that will NEVER be included in this kernel :
adding any other governor (than those stock)
root/busybox auto-installation
CPU/GPU overclocking/undervolting
adreno idler
state_notifier
any upgrade of Linux kernel
dual-boot
etc
★ PREREQUISITE ★ :
An unlocked Bootloader
An Android Nougat firmware (based on LineageOS)
A custom recovery (TWRP recommanded), to flash the kernel
Optional : to control some kernel tweaks, you can install Kernel Adiutor)
★ SOURCE (up-to-date) ★ :
Github >> SimpleGX.
★ INSTALLATION PROCEDURE ★ :
(personally I'm not on LOS, so here is @dr.zook instructions instead (thanks to him!) :
Backup everything you need (internal & external)
Unlock your bootloader
Flash official TWRP recovery
Reboot to TWRP
Wipe system/cache/dalvik and data (without data/media) partitions
Flash your full latest AOSP + 4.5.10 firmware package
Optional: flash your favorite Gapps package
Flash SimpleGX kernel
Flash root (Magisk or SuperSU)
Optional: this last step is only for the unencrypted devices: flash "no_verity_op5.zip"
Reboot and enjoy !
★ FAQ ★ :
How can I update my SimpleGX kernel version ?
Follow THESE steps.
How can I go back to stock kernel ?
Just flash back your full usual rom back.
Is there a OxygenOS (OOS) version of you kernel ?
Of course ! grab it HERE.
How to recover excellent battery life ?
Check my personal tips HERE.
★ for LineageOS ★
/!\ CHECK MD5 BEFORE FLASHING IS ALWAYS HIGHLY RECOMMENDED /!\
/!\ PLEASE DO NOT MIRROR MY DOWNLOADS /!\
Need supports ? all kind of questions must be posted on this thread directly. Be sure to read at least completely this first post before asking any question.
If you enjoy this kernel, don't forget to rate this thread
stars, and clicking the 'thanks' button (right below). It's always appreciated to keep this thread maintained
LIKE MY WORK ?
OFFER ME A
:good::highfive::good:
CHANGELOG
★ CHANGELOG ★ :
22.09.2017 : v1.03 released.
Added one cpufreq_conservative (fix/optimization) patch
Added wakelocks control back and disable them by default (for better battery life)
Add (CVE-2017-1000251) security patch for Bluetooth BlueBorne attack
Added OnePlus5 minimum backlight fix (current value has been set to 8 for now).
17.09.2017 : v1.02 released.
Synchronize codes to latest LineageOS source
Anykernel2: updated to latest version
08.09.2017 : v1.01 released.
Synchronize codes to latest LineageOS source
Removed all queue work on power efficient wq patches from franciscofranco. (Less experimental, more close to stock now).
03.09.2017 : v1.00 released.
Initial release (check actual features. Should match v1.06 of OxygenOS version. The only difference for now is USB fast charge removed due to already integrated fast charge USB tweak from LOS source).
Thanks & greetings
★ THANKS & GREETINGS ★ :
(by alphabetic order)
Lord Boeffla
osm0sis
ZaneZam
. . . and of course to all talented devs credited in my commits!
DONATIONS
★ DONATIONS ★ :
Many thanks @dr.zook :good:
Thank you to support my work ! :highfive:
Reserved (just in case)
Awesome job
Enviado desde mi ONEPLUS A5000 mediante Tapatalk
Awesome, my favorite kernel is there for LOS! ?
Thanks for your great work, keep it up ??
Cheers :highfive:
Sent from my ONEPLUS A5000 using XDA Labs
dr.zook said:
Awesome, my favorite kernel is there for LOS!
Thanks for your great work, keep it up
Cheers :highfive:
Click to expand...
Click to collapse
Wow man, thank you very much for your second donation, very appreciated! :highfive::good:
Also, thank you again to be the first to confirm that beta3 was working (before making final) release
Cheers'
well, I can't use this kernel with LOS.
When the phone boots up it just says "android is starting" with my background picture. I'm using the newest built that came out today + the OOS 4.5.10 files
4RM4N1 said:
+ the OOS 4.5.10 files
Click to expand...
Click to collapse
This kernel is for LineageOS, not OxygenOS :good:
I can't confirm myself if my LOS version is working since I will stick to OOS for now (and no plan to go for LOS one day), but @dr.zook tested my beta3 recently and confirmed working perfectly into official LOS. All I did is just removing "-beta3" from local version, so it should be weird that it's not working anymore.
4RM4N1 said:
well, I can't use this kernel with LOS.
When the phone boots up it just says "android is starting" with my background picture. I'm using the newest built that came out today + the OOS 4.5.10 files
Click to expand...
Click to collapse
Could you please tell what exactly you did?
Clean flash?
Coming from stock or custom kernel?
First boot on stock or SimpleGX?
Root? If yes supersu, magisk or other?
Is your device encrypted or unencrypted?
I am unencrypted.
I clean flashed rom, same firmware as you, then SimpleGX, then magisk,then no_verity_op5.zip and all worked flawlessly.
Sent from my ONEPLUS A5000 using XDA Labs
---------- Post added at 07:35 PM ---------- Previous post was at 07:31 PM ----------
AndroidGX said:
This kernel is for LineageOS, not OxygenOS :good:
...
Click to expand...
Click to collapse
I think he talks about the latest firmware package with is the one I used to flash, too.
It's a thing you have to do on LOS/CAF/AOSP roms.
Sent from my ONEPLUS A5000 using XDA Labs
dr.zook said:
Could you please tell what exactly you did?
Clean flash?
Coming from stock or custom kernel?
First boot on stock or SimpleGX?
Root? If yes supersu, magisk or other?
Is your device encrypted or unencrypted?
I am unencrypted.
I clean flashed rom, same firmware as you, then SimpleGX, then magisk,then no_verity_op5.zip and all worked flawlessly.
Sent from my ONEPLUS A5000 using XDA Labs
---------- Post added at 07:35 PM ---------- Previous post was at 07:31 PM ----------
I think he talks about the latest firmware package with is the one I used to flash, too.
It's a thing you have to do on LOS/CAF/AOSP roms.
Sent from my ONEPLUS A5000 using XDA Labs
Click to expand...
Click to collapse
I'm also pretty sure that he does something wrong anywhere during flashing steps for LOS :highfive:
Thanks for the infos, it looks like it's a bit hard to move into LOS, that is why I guess LOS is not getting much success into OP5 for now
It's more from the "elite" side
dr.zook said:
Could you please tell what exactly you did?
Clean flash?
Coming from stock or custom kernel?
First boot on stock or SimpleGX?
Root? If yes supersu, magisk or other?
Is your device encrypted or unencrypted?
I am unencrypted.
I clean flashed rom, same firmware as you, then SimpleGX, then magisk,then no_verity_op5.zip and all worked flawlessly.
Click to expand...
Click to collapse
I came from RR official. Device is encrypted.
• Factory Reset
• flashed LineageOS with Factory Wipe
• flashed GApps
• flashed the Kernel
• flashed Magisk
4RM4N1 said:
I came from RR official. Device is encrypted.
• Factory Reset
• flashed LineageOS with Factory Wipe
• flashed GApps
• flashed the Kernel
• flashed Magisk
Click to expand...
Click to collapse
What magisk version did you use? Official 13.3 or one of the beta/unofficial versions?
Maybe try to first boot on stock kernel and see if you can get it to boot.
As your device is encrypted it MAY be the cause of the issue, too. I have no experience with encrypted devices, I decrypted my device on day one to have all the options...
Sent from my ONEPLUS A5000 using XDA Labs
---------- Post added at 04:06 AM ---------- Previous post was at 03:57 AM ----------
AndroidGX said:
I'm also pretty sure that he does something wrong anywhere during flashing steps for LOS :highfive:
Thanks for the infos, it looks like it's a bit hard to move into LOS, that is why I guess LOS is not getting much success into OP5 for now
It's more from the "elite" side
Click to expand...
Click to collapse
You're right, but I so much want the customization aosip/rr/aicp and whatnot brings. If the op camera app works on this, I think I'll switch.
I tried a nearly gappless setup with microg magisk module and just the playstore but I could not get it to full functionality on first try. Didn't have the time to dig into the problem.
But that's the way I want it to be. At least for a while ?
Sent from my ONEPLUS A5000 using XDA Labs
dr.zook said:
What magisk version did you use? Official 13.3 or one of the beta/unofficial versions?
Maybe try to first boot on stock kernel and see if you can get it to boot.
As your device is encrypted it MAY be the cause of the issue, too. I have no experience with encrypted devices, I decrypted my device on day one to have all the options...
Sent from my ONEPLUS A5000 using XDA Labs
---------- Post added at 04:06 AM ---------- Previous post was at 03:57 AM ----------
You're right, but I so much want the customization aosip/rr/aicp and whatnot brings. If the op camera app works on this, I think I'll switch.
I tried a nearly gappless setup with microg magisk module and just the playstore but I could not get it to full functionality on first try. Didn't have the time to dig into the problem.
But that's the way I want it to be. At least for a while
Sent from my ONEPLUS A5000 using XDA Labs
Click to expand...
Click to collapse
Problem is that I kept old OOS flashing instructions (so i'ts my mistake also).
If you may sum-up exactly the correct steps one by one which were working for you, I will add it into first post :highfive::good:
I have to go to the Hospital this whole day, will edit once I'll come back home (I hope! haha)
Cheers'
dr.zook said:
What magisk version did you use? Official 13.3 or one of the beta/unofficial versions?
Maybe try to first boot on stock kernel and see if you can get it to boot.
As your device is encrypted it MAY be the cause of the issue, too. I have no experience with encrypted devices, I decrypted my device on day one to have all the options...
Sent from my ONEPLUS A5000 using XDA Labs
Click to expand...
Click to collapse
It is 100% a problem of the ROM. I'm now on AOSPA again and the kernel works there.
I used Magisk 13.6
Everything boots fine on LineageOS but when I add the kernel the whole system is screwy
AndroidGX said:
Problem is that I kept old OOS flashing instructions (so i'ts my mistake also).
If you may sum-up exactly the correct steps one by one which were working for you, I will add it into first post :highfive::good:
I have to go to the Hospital this whole day, will edit once I'll come back home (I hope! haha)
Cheers'
Click to expand...
Click to collapse
OK, here's what I did and how my device is set up.
I use twrp 3.1.1.1 official and I am unencrypted.
I wiped cache/dalvik(art), system and data without data/media.
Then I flashed latest aosip and 4.5.10 firmware package.
Then, if wanted, your favorite gapps package.
Then SimpleGX kernel and magisk 13.3 stable.
Last step is only for the unencrypted devices, flashing the no_verity_op5.zip
That's pretty much it.
Sent from my ONEPLUS A5000 using XDA Labs
Any idea if this Kernel works on Pure Fusion?
mcduffie2010 said:
Any idea if this Kernel works on Pure Fusion?
Click to expand...
Click to collapse
It should work fine.
Do a nandroid backup before you flash, just to be safe.
Sent from my ONEPLUS A5000 using XDA Labs
dr.zook said:
It should work fine.
Do a nandroid backup before you flash, just to be safe.
Click to expand...
Click to collapse
Nandroid is never working for me. It won't boot
{
"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 7T/Pro, Kernel for the OnePlus 7T Pro
Contributors
eng.stk
Source Code: https://github.com/engstk/op7
Kernel Special Features: Powered by sparky
Version Information
Status: Beta
Current Beta Version: r60 unified
Beta Release Date: 2019-11-13
Created 2019-11-13
Last Updated 2019-11-13
blu_spark r60 release (Android 10 unified)
All right crew!
First build for the 7T/Pro is up :highfive:
This kernel is unified, good to go on OP7/T/Pro (I only can test on Pro).
blu_spark_r60 release
All the goodies available from OP7/Pro
Synchronize codes for OnePlus 7T Pro Oxygen OS 10.0.1
CAF updates f2fs, dm-verity/init, mm, crypto drv, devfreq, etc
fs: exfat: version 2.2.0-3arter97
AnyKernel3 updates
If you use root, Magisk 20.1 or newer is mandatory
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
Flashed and booted fine with EXKM.
Used this awesome kernel on the 5T and expect nothing less.
Awesome work!
Lossyx said:
Flashed and booted fine with EXKM.
Used this awesome kernel on the 5T and expect nothing less.
Awesome work!
Click to expand...
Click to collapse
Bam! Enjoy mate
Sent from my blu_spark'd OnePlus
Hi, will this work on OP7T Pro McLaren Edition? Thx
HD1913 on OOS 10.0.3.HD01BA
oooo nice :good:
nice to see you here[emoji106]thxs for you work.
Verstuurd vanaf mijn HD1913 met Tapatalk
Anyone have tried to use twrp to flash this kernel yet?
How to use twrp to flash in? With USB stick?
Nice work
great stuff and really nice features - thanks for this !
gonna flash it right now ...
2 questions:
- reworked GPU driver: what has been reworked here ? Will this affect performance or compatibility (vulkan/ ogl ?)
- Could you add audio-tweaks like global earpiece/ main-speaker gains (so one can modify these in EXKM for example ?)
Stereo-Panorama isn't very well balanced - at least MY main speaker is too loud. Of course we have the audio-balance in Android 10 now, but not all sources (e.g. most emulators) don't play audio through it ...
thanks and regards
jaythenut said:
oooo nice :good:
Click to expand...
Click to collapse
beaverhead said:
nice to see you here[emoji106]thxs for you work.
Verstuurd vanaf mijn HD1913 met Tapatalk
Click to expand...
Click to collapse
Ride on guys
Sent from my blu_spark'd OnePlus
koliberk said:
Hi, will this work on OP7T Pro McLaren Edition? Thx
HD1913 on OOS 10.0.3.HD01BA
Click to expand...
Click to collapse
Don't know what differences that model has.
If it's the same as 7T pro it should work.
Backup and test if you want to try and let us know
ricky886 said:
Anyone have tried to use twrp to flash this kernel yet?
How to use twrp to flash in? With USB stick?
Nice work
Click to expand...
Click to collapse
Yeah twrp should work fine with zip sideload or using usb stick.
Or use autoflash kernel apps like FKM on a rooted environment and profit
Quantuml3ap said:
great stuff and really nice features - thanks for this !
gonna flash it right now ...
2 questions:
- reworked GPU driver: what has been reworked here ? Will this affect performance or compatibility (vulkan/ ogl ?)
- Could you add audio-tweaks like global earpiece/ main-speaker gains (so one can modify these in EXKM for example ?)
Stereo-Panorama isn't very well balanced - at least MY main speaker is too loud. Of course we have the audio-balance in Android 10 now, but not all sources (e.g. most emulators) don't play audio through it ...
thanks and regards
Click to expand...
Click to collapse
Drivers from the graphic stack have been trimmed on cruft, debug, logging, etc to make it a bit more efficient. Also some patches to improve interactiveness. GPU boost is also available to tune it up if you game alot.
Full compatibility with anything same as stock.
I will not touch anything audio related, sorry.
Sent from my blu_spark'd OnePlus
eng.stk said:
Don't know what differences that model has.
If it's the same as 7T pro it should work.
Backup and test if you want to try and let us know
Click to expand...
Click to collapse
Which one should o use if I'm on stock ROM?
blu_spark_r60-custom_op7x_b48eb6a14.zip16.6 MB
blu_spark_r60-oos_op7x_ef7715b31.zip14 MB
koliberk said:
Which one should o use if I'm on stock ROM?
blu_spark_r60-custom_op7x_b48eb6a14.zip16.6 MB
blu_spark_r60-oos_op7x_ef7715b31.zip14 MB
Click to expand...
Click to collapse
It's not too hard to work out
I have tested oos
Flash in failed, error code :1
"Unsupport android version. aborting"
---------- Post added at 03:06 PM ---------- Previous post was at 02:40 PM ----------
Lossyx said:
Flashed and booted fine with EXKM.
Used this awesome kernel on the 5T and expect nothing less.
Awesome work!
Click to expand...
Click to collapse
This worked!!!
eng.stk said:
Backup and test if you want to try and let us know
Click to expand...
Click to collapse
Flashed OOS, phone seems to be a bit faster. Noticed quicker loading of widgets after boot.
But there seems to be a bit to much brightness while booting, as boot animation overshoots it's limits :/
The other issue I had was missing all stock sounds, like ringtones and notifications.
I could only use my own sounds from internal storage. :/
Left with new kernel, right is with stock.
koliberk said:
Which one should o use if I'm on stock ROM?
blu_spark_r60-custom_op7x_b48eb6a14.zip16.6 MB
blu_spark_r60-oos_op7x_ef7715b31.zip14 MB
Click to expand...
Click to collapse
OOS is always for OOS based ROMs.
Custom is for AOSP/CAF ROMs.
koliberk said:
Flashed OOS, phone seems to be a bit faster. Noticed quicker loading of widgets after boot.
But there seems to be a bit to much brightness while booting, as boot animation overshoots it's limits :/
The other issue I had was missing all stock sounds, like ringtones and notifications.
I could only use my own sounds from internal storage. :/
Left with new kernel, right is with stock.
Click to expand...
Click to collapse
Thanks for testing. It may be small changes then.
What ROM does the device run? May be just a case of binaries/kernel mismatch.
If is something done on purpose because of SKU difference, coded on dtb and or even worse in drivers, may be more hard to address.
In the past we had checks we could fake SKU to have the themes and stuff available, I'll take look.
eng.stk said:
OOS is always for OOS based ROMs.
Custom is for AOSP/CAF ROMs.
Thanks for testing. It may be small changes then.
What ROM does the device run? May be just a case of binaries/kernel mismatch.
If is something done on purpose because of SKU difference, coded on dtb and or even worse in drivers, may be more hard to address.
In the past we had checks we could fake SKU to have the themes and stuff available, I'll take look.
Click to expand...
Click to collapse
Thanks, I have included details of my ROM in the attachment.
I think my ROM is global, as just after receiving device from OnePlus UK it was on 10.0.1, than OTA full update to10.0.3 from OOS.
Data as per Oxygen Updater:
OOS Ver: 10.0.3.HD01BA
OTA Ver: OnePlus7TProOxygen_14.E.07_GLO_007_1910120134
Incremental OS Ver: 1910120055
Thanks man. Device is running great on this kernel but I've noticed since I flashed it this morning that the fingerprint reader is really flakey, has anyone else noticed this? I've reregistered a few times but I find I have to try 5-6 times to unlock whereas before it worked first time every time.
daveuk87 said:
Thanks man. Device is running great on this kernel but I've noticed since I flashed it this morning that the fingerprint reader is really flakey, has anyone else noticed this? I've reregistered a few times but I find I have to try 5-6 times to unlock whereas before it worked first time every time.
Click to expand...
Click to collapse
I have the same problem. It's also with kirisakura kernel.
Only flars kernel doesn't have this behavior so far.
Thanks for providing the kernel too us anyways.
daveuk87 said:
Thanks man. Device is running great on this kernel but I've noticed since I flashed it this morning that the fingerprint reader is really flakey, has anyone else noticed this? I've reregistered a few times but I find I have to try 5-6 times to unlock whereas before it worked first time every time.
Click to expand...
Click to collapse
Been noticing this too.
But it only happens when device falls into deep sleep (?) for me.
Example:
I woke this morning and device been sleep overnight the fingerprint wasn't recognized
When I took a shower and came back the fingerprint wasn't recognized.
However when I unlock it and use the phone for a minute or so the fingerprint starts to work fine again.