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
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.
{
"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"
}
Introduction
NOTE: This kernel is currently not being updated. I recommend using Sultan's kernel instead.
Hello everyone, this is my personal kernel for the Pixel 2 (walleye) and Pixel 2 XL (taimen). I only own the latter but the kernel is fully unified. While I am not a super star kernel developer, I do know my way around it. My philosophy on kernels is pretty simple:
Follow stable Linux always. Updates will be delivered within 24 hours of their release to kernel.org.
Stable kernel rules work best (only add small things when possible).
Security and stability are paramount. Vulnerabilities are patched as soon as they are disclosed.
Features will be added only as needed (I have a list of things in the FAQ I will NOT add, even if requested).
Hopefully you enjoy
Important thread information!
I refuse to acknowledge/respond to bug reports that do not include clear steps to reproduce, a logcat, and a console ramoops (if random rebooting) or a dmesg (any other issues). Follow this guide to do this.
Keep things civil, I do NOT tolerate flaming of any kind.
OT is allowed.
Features
Here are the major features of the kernel (feel free to explore Github)
Up to date with the November security update (android-9.0.0_r0.37) [see device specific notes below]
Up to date with the latest stable Linux version (4.4.162)
Patches from Code Aurora Forum targeting GPU, touchscreen/video, storage, and sound
Kernel hardening from CopperheadOS
Mainline Linux patches for CFQ and media memory allocation
Latest energy aware scheduling patches from kernel/common's android-4.14 branch
Several subsystems converted to use power efficient workqueues
Westwood as the default congestion algorithm
Optimized input and wake boosting and other optimization from Sultanxda
The following user facing features:
KCAL color control
Minimum/maximum backlight control
Vibration control
Wake gestures (thanks to @flar2)
Wakelock control
Latest WireGuard snapshot (0.0.20181018)
Built with a self compiled Clang 7.0 toolchain with a local initialization sanitizer (previously built with the latest Google Clang 6.0 toolchain here)
Hides bootloader unlock from SafetyNet (can still fail through other means)
Available to flash with AnyKernel2 (thanks to @osm0sis) [zip will automatically detect when Magisk is installed and patch the kernel so reflashing Magisk becomes unnecessary]
Downloads
Primary: https://github.com/nathanchance/wahoo/releases
It is called Wahoo as that is the unified name for the Pixel 2 (walleye) and Pixel 2 XL (taimen) [link 1 and link 2].
Installation
NOTE: These sets of steps should work for both initial installations and upgrades. All sane kernels on this device are just replacing the kernel image and maybe adding some cmdline parameters, which this kernel won't care about. If there are ANY issues after flashing this kernel over another, be sure to flash the stock boot image for your ROM, TWRP + Magisk if you want them, then the kernel before reporting any issues.
Through TWRP:
See their instructions for further information, you can install the kernel with TWRP temporarily booted or permanently installed.
Boot into TWRP.
Flash the zip (flashing Magisk is not necessary if you already have it installed).
Reboot and enjoy!
Through FK Kernel Manager (requires root):
Download the zip (and optionally, the md5) from my server
Tap on "Manual flasher"
Navigate to Download
Tap on the zip, select Auto-flash, and choose one of the options.
Reboot and enjoy!
Changelog
Latest release post!
Commits
Frequently asked questions
1.1 Q: I am having an issue, can you help me?
1.1 A: I am not an amazing kernel developer but I will certainly try my best. First, start by reading the release posts, as I may make note of a particular issue. Also search the thread to see if I have discussed it before. If you see nothing, please provide me with a dmesg/last_kmsg and logcat, your ROM/kernel version, and a detailed description of the issue, following this guide. If I can't reproduce reliably, I'm not going to fix the issue.
1.2 Q: Can you add xyz feature?
1.2 A: If you link me the commits or tell me what kernel you had the feature in, I can take a look at them. I will not go digging super hard for commits and I will ignore requests that don't include this information. I won't promise that I will merge every request but I will always take it into consideration. I will NOT add the following:
Overclocking or underclocking of CPU or GPU
Undervolting
Any governors other than schedutil
Any schedulers other than cfq and maple
Anything that compromises performance
1.3 Q: How do I control the kernel?
1.3 A: I want to be very clear: the kernel does NOT need to be tuned to be useful. Most of the improvements are under the hood and don't require any user intervention to take advantage of them. In fact, if you don't know what you are doing, you could degrade the experience.
To control the user visible features of the kernel listed above, I recommend using either @franciscofranco's FK Kernel Manager (which has Flash Kernel support for downloading and automatically flashing the latest kernel zip along with some nice, user friendly ways for tuning the kernel) or @flar2's EX Kernel Manager.
1.4 Q: OMFG MY BATTERY SUXXXX PLS FIX!!!
1.4 A: The kernel doesn't drain any battery, use an app like BetterBatteryStats to figure out what app is screwing with your phone.
Thanks to:
The various other developers for their patches (specifically @zx2c4 for WireGuard)
@osm0sis for AnyKernel2
@franciscofranco for adding Flash Kernel support to FK Kernel Manager
@phantom146 for the thread banner
All of you guys for viewing the thread
A note about donations
Quite a few people have asked to donate to me in the past and I have turned them down. I am not in this for the money, this is my hobby, something I truly enjoy. If you truly want to donate to something (it is not expected in the slightest), I recommend an entity like the Open Source Initiative, the Free Software Foundation, XDA, or any one of the people I have thanked in the OP. Additionally, you are free to copy any and all of my work; the only thing I request is that you not ask for donations as well (though I can't really enforce this lol). Thank you.
Kernel source links
8.0.0: https://github.com/nathanchance/wahoo/tree/oreo-dr1
8.1.0/9.0.0 Preview (2.00-2.28): https://github.com/nathanchance/wahoo/tree/oreo-mr1
8.1.0/9.0.0 Preview (2.29+): https://github.com/nathanchance/wahoo/tree/oreo-m2
9.0.0 (3.00-3.06): https://github.com/nathanchance/wahoo/tree/pie
9.0.0 (3.07+): https://github.com/nathanchance/wahoo/tree/pie-r2
DISCLAIMER: I openly welcome off topic in my threads. Mods, please do not clean off topic discussion and users, do not complain about off topic discussion here. I may direct you to another thread if it is so suited but I won't have the discussion cleaned. Thank you.
Device specific nuances
Due to the way Google has structured security on the Pixel 2 and Pixel 2 XL, TWRP and the boot images may fail to boot when the security updates are out of sync (ROM is on one, kernel/TWRP is on another). I cannot control this. You are responsible for knowing when to flash a new update. If you are boot looping, flash back to the previous boot image.
Some of you may be wondering what this dtbo image is. It is short for device tree blob overlay, which allows Google to unify the kernel for the Pixel 2 and Pixel 2 XL. You are required to flash this along with the boot image to maintain full compatibility. This is automatically done with the zip so you do not need to worry about anything.
Reserved
Thanks Nathan! Couldn't be happier you're on board
Edit : Damn Gboard auto correct
Thank you as always Nathan. Nice to come from the 6p running your kernel, and now on the P2XL. Looking forward to what you and Beans have in store for us :good::good:
thanks Nathan!!!! woooo hooooo
I missed your work since i changed from my nexus to pixel. Awesome to have you here!
Awwwwwwwwww yeah!!!!!!!
Thanks Nathan. I just flashed it no problem, great to see you here.
Thank you. Worked great.
Quick question, if I now format user data can I run unencrypted?
Can someone hook me up with an md5?
Ok @nathanchance since off topic is allowed please allow me to use the freedom to say cheers to you! Reading your OP reminded me of why I got into Android. Friendly atmosphere, off topic allowed, not in it for fame or donations and a sense of community contribution. That's what it's all about. :good:
cjkacz said:
Ok @nathanchance since off topic is allowed please allow me to use the freedom to say cheers to you! Reading your OP reminded me of why I got into Android. Friendly atmosphere, off topic allowed, not in it for fame or donations and a sense of community contribution. That's what it's all about. :good:
Click to expand...
Click to collapse
Could not have said it better. Glad you're here with @nathanchance!!
Lawlrus said:
Can someone hook me up with an md5?
Click to expand...
Click to collapse
boot.img
7873b4713587273873b22d1e36850257
dtbo.img
87d428860b5f12d8926ad8ed38fefaf9
Thanks nathan. Good to see your work on the xl2!
Mike02z said:
Thank you. Worked great.
Quick question, if I now format user data can I run unencrypted?
Click to expand...
Click to collapse
No idea what will happen. As noted in the OP, I don't touch any sort of encryption status. The way things are done on Oreo is vastly different from anything before.
Lawlrus said:
Can someone hook me up with an md5?
Click to expand...
Click to collapse
I'll start providing these as additional files, sorry I forgot this time around!
And thanks for the warm welcome everyone, glad to see so many familiar faces!
Sent from my Pixel 2 XL using XDA Labs
Cheers - will be hanging here sometimes.
def. hanging in the telegram channel!
and thank you sir!
nathanchance said:
No idea what will happen. As noted in the OP, I don't touch any sort of encryption status. The way things are done on Oreo is vastly different from anything before
Click to expand...
Click to collapse
Got it. Is your kernel running enforcing then, or is it permissive.
Mike02z said:
Got it. Is your kernel running enforcing then, or is it permissive.
Click to expand...
Click to collapse
Enforcing and that will never change. If you want to go permissive, use Magisk to run an init script.
Sent from my Pixel 2 XL using XDA Labs
My 2 XL was delivered yesterday afternoon and I didn't have time to set it up until this morning. I check XDA, and voila, there's root and flash kernel. Awesome.
{
"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.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Kernel features:
Build with custom upstream LLVM 14.x (Clang 14.0.5 + LLD linker)
Full -O2 build with device and target flags enhanced, build improvements and compiler fixes, 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
Modded schedutil governor merged from latest CAF sm8150 patchset
No OC, use 250HZ base timer frequency
msm_performance touchboost toggle on/off (enabled by default), tweaked cpu_boost driver
Enhanced TCP methods (westwood is default, BBR available), 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 default) and with file disabled, LZO-RLE and ZSTD are available
Vibrator Strength tunable and Gesture Haptic Feedback control (touchpanel and FPR)
KGSL fixes and general improvements for GPU driver
adrenoboost ready (disabled by default)
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 FKM, EXKM, Kernel Adiutor and others
DOWNLOAD KERNEL ZIP
FKM download configs: oos | custom
(No mirrors please)
Setup and troubleshoot: To install just flash the zip on a stock setup with either TWRP or autoflash kernel app.
If you come from other kernel or have any issues, you should restore your stock boot.img or dirty flash your ROM before flashing blu_spark zip to avoid problems. Also uninstall or clean data of any kernel control app you're using.
If you are upgrading between blu_spark versions, just flash the kernel zip.
About bugs and reports: don't bother to post if a log isn't ready or without steps so the behavior can be replicated. I only active support stock OOS ROM with NO mods whatsoever (apart from root). That includes NO support if using xposed, Magisk with added modules, etc.
If you're using custom ROMs (including stock based ones) and OOS Open Betas you're much on your own. I'm mostly interested on debugging stuff in stock and stable OOS.
Also try not to spam the thread with OT. There's threads for all kind of stuff, use them.
Going back to stock: This kernel installer doesn't change your filesystem. You can backup your boot.img with TWRP or kernel app before flashing blu_spark if you want to go back to full stock or just dirty flash your full ROM.
Source Code: https://github.com/engstk/op7
Don't forget to hit thanks, it's free
OnePlus 7T 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.
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
Since there is no TWRP yet, how to flash the kernel in OOS?
Nishchay1 said:
Since there is no TWRP yet, how to flash the kernel in OOS?
Click to expand...
Click to collapse
You can use EXKM or Franco kernel Manager.
It flashed and booted fine on my 7T Pro.
Sent from my OnePlus7TPro using XDA Labs
Lossyx said:
You can use EXKM or Franco kernel Manager.
It flashed and booted fine on my 7T Pro.
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
I'm already rooted. Flashing this over the patched boot.img will cause any trouble?
Nishchay1 said:
I'm already rooted. Flashing this over the patched boot.img will cause any trouble?
Click to expand...
Click to collapse
nope, i was also rooted and flashed this using EXKM and had no issues
Nishchay1 said:
I'm already rooted. Flashing this over the patched boot.img will cause any trouble?
Click to expand...
Click to collapse
MrGimpGrumble said:
nope, i was also rooted and flashed this using EXKM and had no issues
Click to expand...
Click to collapse
Indeed flash via autoflash kernel apps work fine in a rooted environment and is thw way to go atm.
Or sideload the zip via twrp, use usb flash drive, etc.
Sent from my blu_spark'd OnePlus
Aww yeah, I remember Blu on my Nexus 5 ??
My finger print unlock stopped working after flashing custom ver. 60
Sent from my HD1905 using Tapatalk
Getting forbidden error on downloads.
ChongoDroid said:
Aww yeah, I remember Blu on my Nexus 5 ??
Click to expand...
Click to collapse
Yes same here, best kernel for Nexus 5
I'm guessing we flash oos zip if we're on stock ROM and custom if we're on custom?
morbidj said:
My finger print unlock stopped working after flashing custom ver. 60
Sent from my HD1905 using Tapatalk
Click to expand...
Click to collapse
anybody else also getting this? I'm on Global 10.0.5
aleck0112 said:
anybody else also getting this? I'm on Global 10.0.5
Click to expand...
Click to collapse
I think its buggy on the lock screen. Found it does work sometimes if you press very lightly.
I believe ElementalX had the same problem which was rectified with removal of verifiedbootstate hide for OP7t and OP7tPro
notegalaxy said:
I think its buggy on the lock screen. Found it does work sometimes if you press very lightly.
I believe ElementalX had the same problem which was rectified with removal of verifiedbootstate hide for OP7t and OP7tPro
Click to expand...
Click to collapse
yeah im gonna hold on for now:silly:
Does anyone know how to get the logs which would be relevant to the dev to help solve this issue?
shorty1993 said:
Getting forbidden error on downloads.
Click to expand...
Click to collapse
Working fine.
ChongoDroid said:
I'm guessing we flash oos zip if we're on stock ROM and custom if we're on custom?
Click to expand...
Click to collapse
OOS for OOS baswd ROMS.
Custom for AOSP/CAF source build ROMs.
morbidj said:
My finger print unlock stopped working after flashing custom ver. 60
Sent from my HD1905 using Tapatalk
Click to expand...
Click to collapse
aleck0112 said:
anybody else also getting this? I'm on Global 10.0.5
Click to expand...
Click to collapse
notegalaxy said:
I think its buggy on the lock screen. Found it does work sometimes if you press very lightly.
I believe ElementalX had the same problem which was rectified with removal of verifiedbootstate hide for OP7t and OP7tPro
Click to expand...
Click to collapse
Weird, never seen anything like that in any device for that matter.
7T Pro is working normal and all peachy.
Was it always like that or became so because of a ROM update?
Did you guys try to troubleshoot it, like removong the pronts and enroll again, clear Store data, etc?
Sent from my blu_spark'd OnePlus
eng.stk said:
Working fine.
OOS for OOS baswd ROMS.
Custom for AOSP/CAF source build ROMs.
Weird, never seen anything like that in any device for that matter.
7T Pro is working normal and all peachy.
Was it always like that or became so because of a ROM update?
Did you guys try to troubleshoot it, like removong the pronts and enroll again, clear Store data, etc?
Sent from my blu_spark'd OnePlus
Click to expand...
Click to collapse
working fine here on my 7T! Running like a champ... Thanks!!
855+ not capable of being overclocked?
ermacwins said:
855+ not capable of being overclocked?
Click to expand...
Click to collapse
Honestly I would even prefer a downclock at SD855 frequencies to save some juice.