Database Develop

[KERNEL][I9195][Stock JB/KK] brisK v6

brisK Kernel​
brisK is a KitKat kernel for stock-based ROMs for the Samsung Galaxy S4 mini LTE (GT-I9195).
It aims to be faster and more a bit more battery-friendly than the stock kernel, while retaining its stability.
To prevent bloat I will only apply useful features like BLN. Adding 10 random governors and schedulers is not useful in my eyes, and is also not the goal of this kernel.
Goals
Stability: The original Samsung kernel is stable, so let's not go too far away from it. This kernel doesn't need bleeding edge code - it just works(TM).
Efficiency: Less power consumption by faster computation.
Battery: A battery drain patch is included, which is not in Samsungs original code.
Speed: Minor changes, for example: Trade some screen smoothness for less kernel overhead. Should not be noticeable, though. Also lowers power consumption slightly.
Changelog
v6 (brisk_kk-stock_2015-07-28_15-07-08_64d9234.zip)
Removed more KNOX stuff (--> This fixed some random reboots!)
Finally upgraded to new toolchain: Linaro GCC 4.9.4-2015.06 (Cortex-A15)
Thanks @impactor and @SilviuMik for providing help!
v5
Revert default IO scheduler back to CFQ
Apply changes from new released kernel source (GT-I9195_EUR_KK_Opensource.zip - I9195XXUCOA2)
Apply changes from new released kernel source (GT-I9195_EUR_KK_Opensource.zip - I9195XXUCOE4)
Older versions
v4
Fixed USB-to-PC problems by re-enabling some debugging code
v3
Users reported: USB-to-PC (MTP) doesn't work? (Logfiles appreciated)
Apply changes from Samsungs GT-I9195_EUR_KK_Opensource_Update1.zip
Replace stock Wlan module with kk_2.7_rb1.43
Various kernel config changes:
Disable various unused and debugging features
Re-enable heap randomization
Enable "Optimize very unlikely/likely branches"
Set default IO scheduler to noop
Reduce preemption from "Low-latency desktop" to "Desktop"
Disable Samsungs Rooting Restriction
Added init.d support
v2
Added OTG support (UNTESTED) - Edit: NOT WORKING YET
Removed TIMA
Change to XZ compression
Add BLN support (UNTESTED) - Edit: NOT WORKING YET
v1
Added battery drain patches
Optimize kernel for speed, not size
Preparation for init.d support
Permissive SELinux
Future plans
Add proper Prima WLAN driver - Done!
Add a few more optimizations - Done!
Add init.d - Done!
JellyBean Kernel
The old JellyBean kernel is no longer maintained, but it is stable and its uptime was above 2000 hours on my device. I published it here too, in case someone is happy with their JellyBean ROM and wants this.
Features: BLN, Battery drain patches, kernel config optimized, most debugging code deactivated
Source: https://github.com/TheBootloader/android_kernel_samsung_msm8930-common/tree/jb-stock
Awesome people
@SilviuMik for helping me getting started and providing useful tips - You rock!
@Christopher83 for his toolchains
@F4k for providing source code where I can snoop around
@junkyde for his kernel and his OTG and BLN patches
@arco68 for being another great resource
Downloads & Sources
Source code is on my GitHub.
Releases are at the bottom of this post and on GitHub.
See 2nd post if you need checksums.
PLEASE MAKE FULL BACKUP (/system TOO!) BEFORE FLASHING ANYTHING. The strangest things can happen if you don't have a backup - even if it *should* work.
Downloads are ordered from oldest to newest, so the newest release is at the bottom.

Checksums
brisK JB (brisk_jb_2014-05-16_16-40-39.zip)
MD5: 0f916929e85ae1f8d7b2d1aa8c4e5e1f
SHA256: 8cb1b01358eeb6bc7fb68bbb2fd641d5cda852b78d7e22605ffb28eba6da4156
brisK KK v1 (brisk_kk_2014-08-19_17-33-50_cd36751.zip)
MD5: 8edf28d8a2d1d89d40f8a8f1863d7b57
SHA256: aed1caf0d13ada04888e7c3a020fa6b679fc0fc36ad89678e617ae9a36d637e6
brisK KK v2 (brisk_kk-stock_2014-08-21_01-04-03_765f3f6.zip)
MD5: c004e49779f21f706e76a00233f8fb80
SHA256: df57729a66d425a970d8c8ef222edf6073e4cfc562d8dccea96f12ac0eac7aef
brisK KK v3 (brisk_kk-stock_2014-12-07_00-57-00_23da34c.zip)
MD5: d64b2c7049339eaed9d14bafdc8a9ee3
SHA256: 47741a492077d3e385e120c3596bf6df63426930fffcaa7aa84c924ff43fee91
brisK KK v4 (brisk_kk-stock_2014-12-07_15-31-03_1091455.zip)
MD5: d5fb48434fe9a206a9544968081ee654
SHA256: 122189fb11068be07e6d24cbe179ed57a9872944664e028d0d288fcf804ea4d2
brisK KK v5 (brisk_kk-stock_2015-07-23_23-57-24_518a15c.zip)
MD5: 2a5086c1354e6f475d73b77b41bcfe40
SHA256: 7dce6a173c9e6ddf6f573c802cc8aea7900239a2253ca31722e651e791bb6e6e
brisK KK v6 (brisk_kk-stock_2015-07-28_15-07-08_64d9234.zip)
MD5: 567d7e6ea8762559d218bb092c4cdac4
SHA256: b5b3b41fa7ed10210e4964fa2cd98d14d4572a30b68f7b939e945a3458063a43
Samsungs stock JellyBean Kernel (samsung_jb.zip)
Description: Reverts all changes made by brisK JB by overwriting it with Samsungs original JB kernel (extracted from I9195XXUBML4).
MD5: 388336cec2e9686e258985d0dded0dc9
SHA256: 35777926edee3558208175d5359ef1c466dc3d4dbb1276e233f6727d64b83aa3
Samsungs stock KitKat Kernel (samsung_kk2.zip)
Description: Reverts all changes made by brisK KK by overwriting it with Samsungs original KK kernel and files (extracted from I9195XXUCNE6).
MD5: c71112214620a50841731f4899dd2ca2
SHA256: d2d70f212ee898cf1cedef2d84b3e6345e2388a13579a7112181a254a2c2f3de
Installing
To flash any of these zip-files, you need to install a custom recovery on your phone. (For example: http://forum.xda-developers.com/showthread.php?t=2364980 )
Put zip file on your phone or on its microSD
Boot into recovery: Hold "Volume UP", "Home Button", and "Power Button" when it is off or rebooting
MAKE A FULL BACKUP BY USING THE BACKUP-MENU
Select "Install from zip" or something similar
Navigate to your zip file, select it, and flash it
Reboot your phone
Uninstalling
If you want to go back to Samsungs stock kernel or flash another kernel, you need to install "samsung_jb.zip" or "samsung_kk.zip" first.
brisK uses custom kernel modules. When you run on brisK and then directly install another custom kernel which has no custom modules, you will probably experience issues with WLAN and other stuff. To solve this, flash "samsung_jb.zip" or "samsung_kk.zip" (which flashes the stock modules), and THEN flash whatever custom kernel you want. - Of course you do NOT need to do this if you update to a newer version of brisK.

thank !
GREAT !!!
but for governors and schedulers , i agree with you in half ... but "few" of them are very useful !
what do you think about the recent "zen" ...or "row" ( by default in all customs like cyanogenmod ) ?
for you ,what are the "best" (more adapted ) for better compromise in performance/baterry save ?
why you don't add just 1 or 2 among the best of ones ?

Now running on brisK
{
"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"
}

Loulou-13 said:
but for governors and schedulers , i agree with you in half ... but "few" of them are very useful !
Click to expand...
Click to collapse
I agree that some governors might actually improve performance, but there isn't much information available, some people say governor A is better, some say B is best...
But also: Kernel goal nr. 1 is stability, and ondemand is well tested. That's why I probably won't add any new governor before testing them a lot.
Can you suggest any governors? And do you have proof or URLs why they are better? Thanks!
If you want more features, more governors, etc, f4k will probably release a stock kernel soon. So keep an eye out for that!
Loulou-13 said:
what do you think about the recent "zen" ...or "row" ( by default in all customs like cyanogenmod ) ?
for you ,what are the "best" (more adapted ) for better compromise in performance/baterry save ?
why you don't add just 1 or 2 among the best of ones ?
Click to expand...
Click to collapse
Zen: I don't know what this does different than other schedulers, I have to read about this first.
I considered "row" when I had an Evo 3D, but I didn't notice a difference between "noop" and "row" in normal daily usage, so I'm not sure yet if I will include it or not - needs more testing.

ladislav.heller said:
Now running on brisK
Click to expand...
Click to collapse
Awesome!
If you have any problems, please report them here. And if you don't have any problems at all, please report that here too!

TheBootloader said:
I agree that some governors might actually improve performance, but there isn't much information available, some people governor A is better, some say B is best...
But also: Kernel goal nr. 1 is stability, and ondemand is well tested. That's why I probably won't add any new governor before testing them a lot.
Can you suggest any governors? And do you have proof or URLs why they are better? Thank!
If you want more features, more governors, etc, f4k will probably release a stock kernel soon. So keep an eye out for that!
Zen: I don't know what this does different than other schedulers, I have to read about this first.
I considered "row" when I had an Evo 3D, but I didn't notice a difference between "noop" and "row" in normal daily usage, so I'm not sure yet if I will include it or not - needs more testing.
Click to expand...
Click to collapse
Same thinking as me ...
ondemand for CPU Gov / No-op for I/O sched , they work great and don`t cause problems

SilviuMik said:
Same thinking as me ...
ondemand for CPU Gov / No-op for I/O sched , they work great and don`t cause problems
Click to expand...
Click to collapse
Yes, my experience too!
Although, when I copy big files with "noop", android freezes for the duration of the copy process. That's the nature of "noop", but "row" might actually fix that. But then again: I rarely need to copy big files, so "noop" is okay for now.

TheBootloader said:
Awesome!
If you have any problems, please report them here. And if you don't have any problems at all, please report that here too!
Click to expand...
Click to collapse
No problems, everything works well.

Please add support for USB Host with additional power supply, is very necessary !!!!

killov1982 said:
Please add support for USB Host with additional power supply, is very necessary !!!!
Click to expand...
Click to collapse
+1 for USB OTG support.

Working good so far
Thanks

TheBootloader said:
Yes, my experience too!
Although, when I copy big files with "noop", android freezes for the duration of the copy process. That's the nature of "noop", but "row" might actually fix that. But then again: I rarely need to copy big files, so "noop" is okay for now.
Click to expand...
Click to collapse
NOOP hangs in general when the read/write task becomes too intensive. Consider CFQ if you're going to do a bit write operation, else ROW is better. That my two cent when I tried on my S3 with Boffela kernel.
PS. ZEN hangs even worse than NOOP.

ladislav.heller said:
+1 for USB OTG support.
Click to expand...
Click to collapse
I second that

thank for your work...
is your kernel working with old knox-free bootloaders like Silviumik's kernel?
thanks

battery life compared with carbon 4.4.4 ? PLEASE

s.goten said:
thank for your work...
is your kernel working with old knox-free bootloaders like Silviumik's kernel?
thanks
Click to expand...
Click to collapse
For now i think no, because he did not remove Knox reference from source, i could be wrong tho !

I just released a new version!
A lot people asked for OTG, so here you go! I added OTG and BLN (untested!!!), thanks to junkyDE!
The highest kernel goal is stability, but I don't have time to test these features right now - maybe I can do one quick emergency fix tomorrow if something breaks, but after that I will probably not respond for 2 weeks or more.
So, have fun and enjoy!
brisK v2
Added OTG support (UNTESTED)
Removed TIMA
Change to XZ compression
Add BLN support (UNTESTED)
-----
s.goten said:
thank for your work... is your kernel working with old knox-free bootloaders like Silviumik's kernel?
Click to expand...
Click to collapse
SilviuMik said:
For now i think no, because he did not remove Knox reference from source, i could be wrong tho !
Click to expand...
Click to collapse
I removed TIMA in brisK v2, so.... it -should- work now right?
If it doesn't boot, just restore your boot partition from a backup or re-flash your previous kernel if you had any.
-----
TNCS said:
NOOP hangs in general when the read/write task becomes too intensive. Consider CFQ if you're going to do a bit write operation, else ROW is better. That my two cent when I tried on my S3 with Boffela kernel. PS. ZEN hangs even worse than NOOP.
Click to expand...
Click to collapse
Thanks a lot for your input! Now I know I don't need to consider ZEN, and will stay with NOOP, and aim for ROW when I have time to add it.

I9192?
Sent from my GT-I9192 using XDA Premium 4 mobile app

SilviuMik made a 9192 kernel:
http://forum.xda-developers.com/showthread.php?t=2592308

[KERNEL][AOSP][LINARO-4.8-O3][N80xx][UNDER/OVERCLOCK][FAST CHARGE] MM_alpha-0.6

Hi guys,
since we haven't got any kernel for our omni roms I've decided to make one. For now it's just an alpha but to me seems pretty stable I'm releasing here as a test. Please report what do you think. It's based on "stock" omni kernel with overclock (for now I'm using this commits https://github.com/marco9333/androi...mmit/1d75a501447e609dbb412c350d79ac1ef720a630 and https://github.com/marco9333/androi...mmit/36cf4ca9c78144f336dad4af88049b4a6bf59fac but from next release I'll try @humberos commit https://github.com/humberos/android...mmit/5f768f943d0c420860575e22756b58ff64f0c596 as he suggested See changelog below).
I've tested on Omnirom and @nerdyblonde reported it is working on Carbon, feel free to try on any AOSP based rom (not Samsung based)
Features:
An awful name (I'll try to find a better one)
Different versions for n8000 and n801x
Overclock up to 1600Mhz (booting max freq is 1400Mhz) and underclock to 100 Mhz (booting min freq is 200 Mhz) -> version 0.2 and newer
I've added a (temporary) my commit https://gerrit.omnirom.org/#/c/9555/2 to force cpu frequency range to stock values (I'll decide about merging this in omni rom official builds)
Version 0.1 built with different flags and toolchains but from the next one I'll use only linaro (maybe I'll try sabermod too) See below
See changelog
TODO:
Add fast-charge -> I've almost finished this, I hope to post an update soon (maybe today) DONE
Add underclock (100 Mhz, see humberos commit above) Done.... version 0.2 and up See below
Change installing script to solve possible dialer problems with some roms (unpack modify and repack original boot.img I'll use https://github.com/ModdingMyMind/boot_manipulation but I'll need some time)
Add more schedulers and/or governors (???)
Tell me what would you like to have and I'll think about that
Add thanks to all the developers
DIRECT DOWNLOADS Version 0.6 (LATEST):
N8000 -> https://www.androidfilehost.com/?fid=95784891001603463
N801x -> https://www.androidfilehost.com/?fid=95784891001603462
Link to version 0.5 are removed -> Some tweaks weren't included in the zip so I'm releasing a new version. See second post for changelog
Previous version 0.4:
N8000 -> https://www.androidfilehost.com/?fid=95747613655041727
N801x -> https://www.androidfilehost.com/?fid=95747613655041728
DOWNLOADS FOLDER: https://www.androidfilehost.com/?w=files&flid=19342
HOW TO INSTALL
(*optional) Make a backup (or just keep the original rom zip so you can reflash that to go back to stock omni without losing data)
(*not optional) Use this at your own risk I don't take responsibility for any crash, excessive heat, forced reboot, and whichever problem you could have
Flash the zip in recovery, no need to wipe anything, reboot
Thanks to:
* Omnirom team
* @iofthestorm (is the one who ported and made our devices official with omni)
* @humberos (underclock)
* @Lord Boeffla (overclock)
* @Christopher83 (I'm using his toolchains)
* See my sources on github​

CHANGELOG​
Version 0.1
Initial release
Version 0.2
Added frandom(See https://github.com/Ryuinferno/frandom-android for reference)
Added underclock down to 100Mhz (Thanks to @humberos)
Added more build flags (Check http://forum.xda-developers.com/showpost.php?p=36693600&postcount=9 for reference)
Version 0.3
Added fastcharge support in kernel drivers(need some testing to check the best currents) -> Disabled by default but can be enabled anytime without reboot(Maybe an entry in Advanced settings??? See next post)
https://github.com/marco9333/androi...mmit/b3e4981b88be28d59ab01052cf3f66d5e411c88b
Added support for ntfs and exfat filesystems https://github.com/marco9333/androi...mmit/27b3a545c6651fc89fd8a1eaf0bc801dc6222b09
Now powerkey should switch the screen on faster (no lag between pressing and screen on) All credits to https://github.com/dsc-team/dsc-team-kernel-project Not working
Added some patches from linaro, they should give more battery juice-> got about +400 points with antutu if you believe in benchmarks... I don't
Version 0.4
Changed mounts flags for system,data,cache and preload (with antutu I had about 300 for storage I/O now is around 980-989 with cfq, got better result with row, test it if you find some improvements)
Added some patches from linaro (see my github)
Increased i2c speed with wacom digitilizer(I'll test this tomorrow)
Increased sampling rate of wacom digitalizer (S-PEN should beis smoother (IMHO))
Added init.d script editable by user to set cpu frequency,fast charge and s-pen tweaks(for now)
Fixed Broken charging animation when the tablet is off (I will merge this into official omnirom after some testing, maybe I'll release here before as a preview, if you're curious https://gerrit.omnirom.org/#/c/9658/) ->
Merged into omnirom, if you're using omnirom now this fix is present "by default", if you have another rom the fix is still installed with the kernel (Report if not working)
Backported xpad driver (xbox, xbox 360 and xbox one controller support) from linux 3.17 (Needs testing)
Backported ps2, ps3, ps4 driver from linux 3.17 (Needs testing)
Other minor changes
Version 0.5
Fix for camera recording and hd video playing (waiting approval approved and merged into official omnirom -> https://gerrit.omnirom.org/#/c/9943/ and https://gerrit.omnirom.org/#/c/9944/)
Reduced hdmi out resolution to 720p and set hdmi audio to 2ch (Quite useless now since hdmi isn't working)
Introduced compiler flags from JustArchi's github and switched to linaro-4.8.4 (should give a performance boost)
Version 0.6
Enabled previous added SMT (http://en.wikipedia.org/wiki/Simultaneous_multithreading)
Patches for conservative and ondemand governors
Added zzmoove governor
Enabled more governors (interactive and adaptive)
Other small changes (check my github)
​Source: https://github.com/marco9333/android_kernel_samsung_smdk4412 and https://github.com/marco9333/android_device_samsung_n80xx-common

How to temporary enable fastcharge​You need a rooted device but since you're using a custom rom I assume that you have it
Download a terminal emulator app on google play store
Open it, write su and press enter(superuser or supersu should popup, grant root access)
Write echo 1 > /sys/kernel/fast_charge/fast_charge to enable
Write echo 0 > /sys/kernel/fast_charge/fast_charge to disable
Done
This settings will be reset on startup, if someone is interested I can write a init.d script to set fast_charge on boot just let me know DONE. See below
Stock charging settings AC -> 1800 mAh USB -> 600 mAh
Fast charging settings AC ->1900 mAh USB -> 1500 mAh
How to set kernel parameter on boot (Version 0.4 and up)​
You need root and a root browser (like https://play.google.com/store/apps/details?id=com.jrummy.root.browserfree)
Go to /system/etc/init.d and open 99mm_alpha file (it's a plain text file)
All the settings are commented
First section is for cpu frequency set on boot (by default max freq is the stock one so no overclock, try to set it with a kernel app, if everything is alright you can after modify this file)
The second section is about wacom pen, choose the sampling rate you prefe: higher means more smoothness, but possible higher battery consumption
Last section is for fast charge change the 0 in the last line with a 1 to get fast charge enabled at each boot (you should have echo 1 > /sys/kernel/fast_charge/fast_charge)

This is just for omni Rom correct? I rub carbon rom but I'd like to try it.
Sent from my Note 3's big ass screen

smuvman said:
This is just for omni Rom correct? I rub carbon rom but I'd like to try it.
Sent from my Note 3's big ass screen
Click to expand...
Click to collapse
I haven't got time to try on other roms but should work with every AOSP based (like Carbon). You can always try it just flash in recovery: if the boot is ok then it's working, if you got a bootloop you can go to recovery and reflash the whole rom without wiping so you won't lose your data (I think doing a backup is better, just in case)

I can confirm the kernel works on Carbon Rom.. Underclocking works great... I don't overclock though.. Thanks for compiling this for us!

Thanks for taking the time to create it and thanks nerdy for testing
Sent from my Note 2's big ass screen

Unfortunately can't get it to run. Keep getting this fc error.
Running latest carbon rom. I'll wait for the next version. Thanks though. Btw I have the N8013
Sent from my Note 3's big ass screen
{
"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"
}

smuvman said:
Unfortunately can't get it to run. Keep getting this fc error.
Running latest carbon rom. I'll wait for the next version. Thanks though. Btw I have the N8013
Sent from my Note 3's big ass screen
View attachment 2950595
Click to expand...
Click to collapse
Phone fc is quite strange since you are using a n8013 which don't have a modem. In n801x version of the kernel isn't included the modem driver, so this is the cause of that force close IMHO. You can try two things:
Go to settings-> apps-> all-> dialer-> disable -> reboot and check (now phone app is disabled so it shouldn't crash since is not running)
Or download and flash n8000 kernel. (with the modem drivers so the process can't complain anymore)

I have a N8013 as well.. I didn't get any force closes.. I uninstall all system apps I don't use, the dialer being one of them.. I flashed thru TWRP.. Hope you get it working

Ok that would make sense since I never uninstalled the dialer app. Never needed to lol I will try and report back. Thanks.
Sent from my Note 3's big ass screen

Yea! That did the trick! Thanks guys. Now to tweak!
Sent from my Note 10.1 aka my Mobile Porn Storage Unit

Way to go Marco!! Downloaded and flashed!

Unfortunately this doesn't work on CM11. Tested, and android.phone FCs. :/

Spectral1991 said:
Unfortunately this doesn't work on CM11. Tested, and android.phone FCs. :/
Click to expand...
Click to collapse
If you're using n801x check post #9 http://forum.xda-developers.com/showpost.php?p=55679855&postcount=9

marco9333 said:
If you're using n801x check post #9 http://forum.xda-developers.com/showpost.php?p=55679855&postcount=9
Click to expand...
Click to collapse
I'm using n8000. Tried flashing the related kernel file as well. Still not working on latest CM11.

Spectral1991 said:
I'm using n8000. Tried flashing the related kernel file as well. Still not working on latest CM11.
Click to expand...
Click to collapse
Have you tried to clean Dialer data??

marco9333 said:
Have you tried to clean Dialer data??
Click to expand...
Click to collapse
Couldn't even get there. The FCs happen too quickly. After closing a dialog it immediately appears.

When the message appear do not close the dialog but try to pull down the quicksettings and go to settings from there... If this won't work I'll add a script to kernel zip to clean dialer data (if possible) so you can easily flash directly without further actions
Sent from my Nexus 5 using XDA Free mobile app

Thanks for this Marco, it works great here- Omnirom on a n8013. :good:
Is there any chance you might take over the omnirom development now that iofthestorm is out of the loop? He mentioned he was up for helping someone who was willing to continue the work on it.

Recompiled & Optimized Werewolf Kernel [SM-T211]

Hi!
I was looking through @laufersteppenwolf's kernel source and noticed it was compiled with -Os flag and an old toolchain. I decided to recompile it with graphite and -Ofast flags (the highest optimization level) and with a newer toolchain. Though the later failed (All builds with 4.9+ toolchains failed to boot on this device ) it still feels faster than the original build. I have also disabled some debugging options so that the kernel would fit in the boot partition in addition to some performance gain.
Features
Compiled with graphite and -Ofast flags (linaro 4.7.4)
Undervolted Wi-Fi, Vibration, LCD and Touch by 10% (Not sure if they're effective or not)
Disabled some debugging options
Added a lower charging current level (1700mA) to fast charge options (To reduce heating during charge but must be selected by user, Default is 1800)
Download
laufersteppenwolf said:
Hey guys
As you already might have read in either the CM11 dev thread or the Q&A section, I am working on a custom kernel for our T210(R) and T211. It's still in a pretty early stage, but the current build is fully stable, so I thought why not share it
As I'm pretty new to this community, a few words about myself: My (only) device I have been working on is the LG Optimus 4x HD, for which I also made a custom kernel (also named werewolf kernel, who would have thought of that ). Me and 2 other fellow RDs were able to "switch" many blobs with the ones from grouper, which fixed many, many issues we were facing in 4.4 with the stock 4.1 blobs. I am the official maintainer of namelessROM and vanir for the 4x HD, and am also compiling GummyROM, LegoROM, unofficial CM 11 (using grouper blobs) and SlimKat for the 4x HD on a nightly base. And as soon as we have a proper device tree for our tab, I'm sure I can port the Tab3 to all those ROMs
Now, enough chit chatting, let's talk about the kernel
It's based on @ketut.kumajaya's blackhawk kernel (thanks again, mate ) From v004 on we are based on official KitKat sources, with some additions such as:
Features:
Various network tweaks
Entropy tweaks
I/O speed improvements
cortex a9 and neon omtimizations
Added frandom
Tweaked vm dirty ratios
Dynamic read-ahead values
Added I/O schedulers: ROW, SIO, BFQ, FIOPS, V(R)
Optimized AES and SHA1 routines
Added CPU governors: Lionheart, Adaptive, Intellidemand, Hotplug, Hyper
Reduced RAM usage from logger
Updated lowmemkiller
Overclocked to 1.420 GHz by default
Disabled vsync for better 2D performance
Overclocked GPU up to 624MHz (default 416MHz)
Custom user voltage control (CPU)
Undervolted by default (-25mV)
S2W and DT2W (WIP)
Fast Charging
KSM
Bugs:
You tell me!
Installation:
Download the kernel from HERE
Reboot into recovery (recommended to make a nandroid)
Flash the kernel zip
Recommended to wipe /cache
Reboot and enjoy!
And remember to remove phservice if you want to change some CPU/GPU settings yourself
Notes:
See 2nd post
GPL:
Kernel sources
Kernel Modules (only for v001 - v003)
Used defconfig
Used build script
Thanks:
@ketut.kumajaya for the initial kernel base
@gr8nole for general help, info and testing
XDA:DevDB Information
Werewolf kernel SM-T210/T211, Kernel for the Samsung Galaxy Tab 3
Contributors
laufersteppenwolf
Kernel Special Features: Tuned for best possible performance
Version Information
Status: Stable
Created 2014-07-21
Last Updated 2015-05-25
Click to expand...
Click to collapse
XDA:DevDB Information
Recompiled Werewolf SM-T211, ROM for the Samsung Galaxy Tab 3 7.0
Contributors
mat1371
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Version Information
Status: Testing
Created 2018-08-23
Last Updated 2018-08-23

Reserved
Tweaking Guide
laufersteppenwolf said:
Since v002, we have an updated lowmemorykiller. It behaves a bit snappier than the old one, also with the default minfree values. However, in case you like to tweak your device a bit to make it even more snappy (like me ), I tweaked the minfree values a bit to slightly increase the free RAM without really affecting the multitasking experience. The script can be found in the attachment. All you need to do is to extract the script and place it in your /system/etc/init.d/ folder and that's it. The values will be automatically set on boot.
UV interface
The min possible voltage is 1000mV for now, and the max one is 1400mV. If you want me to lower the min voltage, please let me know.
Also, please note, that the voltage has to be changed in 12.5mV steps. If you apply for example 1110mV, it will be rounded down to 1100mV.
Fast Charge interface
The main interface is inside /sys/kernel/fast_charge/*
/sys/kernel/fast_charge/force_fast_charge (rw)
0 - disabled (default)
1 - use custom mA configured through the sysfs interface (see below)
/sys/kernel/fast_charge/ac_charge_level (rw)
rate at which to charge when on AC (1.8A to 2.3A)
/sys/kernel/fast_charge/usb_charge_level (rw)
rate at which to charge when on USB (0.5A to 1.0A)
/sys/kernel/fast_charge/failsafe (rw)
0 - disabled - allow anything up to 2.3A to be used as AC / USB custom current (USE WITH CAUTION!)
1 - enabled - behaviour as described above (default)
/sys/kernel/fast_charge/version (ro)
display fast charge version information
New kmsg layout
From v008 onwards the kmsg looks a tiny bit different. Instead of displaying the time since boot, it logs the actual time and date.
Now, you may ask yourself: "does that any good?" Sure it does. When you encounter an issue and grab a log, you can send it my way saying "the issue happened at 15:35". It is way harder to find out the exact time (in seconds) since the device booted, right?
Click to expand...
Click to collapse

mat1371 said:
Hi!
I was looking through @laufersteppenwolf's kernel source and noticed it was compiled with -Os flag and an old toolchain. I decided to recompile it with graphite and -Ofast flags (the highest optimization level) and with a newer toolchain. Though the later failed (All builds with 4.9+ toolchains failed to boot on this device ) it still feels faster than the original build. I have also disabled some debugging options so that the kernel would fit in the boot partition in addition to some performance gain.
Features
Compiled with graphite and -Ofast flags (linaro 4.7.4)
Undervolted Wi-Fi, Vibration, LCD and Touch by 10% (Not sure if they're effective or not)
Disabled some debugging options
Added a lower charging current level (1700mA) to fast charge options (To reduce heating during charge but must be selected by user, Default is 1800)
Download
XDA:DevDB Information
Recompiled Werewolf SM-T211, ROM for the Samsung Galaxy Tab 3 7.0
Contributors
mat1371
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Version Information
Status: Testing
Created 2018-08-23
Last Updated 2018-08-23
Click to expand...
Click to collapse
Great! Did you upload your source?
I had been working on it to compile with GCC 8, but haven't got enough time to complete the cherry picks

sscsps said:
Great! Did you upload your source?
I had been working on it to compile with GCC 8, but haven't got enough time to complete the cherry picks
Click to expand...
Click to collapse
It's on github but I didn't link to it cause it's messy. BTW There is no source code change aside from makefile and defconfig.

BTW, that link is blocked in India, can you upload it somewhere else? and also, cna you provide link to your source?

sscsps said:
BTW, that link is blocked in India, can you upload it somewhere else? and also, cna you provide link to your source?
Click to expand...
Click to collapse
Use https:// in download link.

adukale said:
Use https:// in download link.
Click to expand...
Click to collapse
Well, I've got it already, and https didn't quite help, her to use a VPN,
I'm suggesting the OP to upload somewhere else as well.

Thx alot, now it's time to download kitkat rom.
Keep it up sir ?

sscsps said:
BTW, that link is blocked in India, can you upload it somewhere else? and also, cna you provide link to your source?
Click to expand...
Click to collapse
Sorry for late reply, I'm busy with my thesis these days. I've attached the file to the post. Will send you a link to the source (GitHub) in your PV.

Great! Finally something new for T211/0. Love to see some movement here.

Tried installing on a T210 with TRWP but get an error message. Anyone any ideas?
Tried to attach the error but it won't let me... Error talks about asset failed getprop ro.product.device == lt023g etc

@Samw13
SM-T210 = lt02 wifi Tab
SM- T211 = lt02_3g Tab

So, i have deleted requirement in update-script file and kernel seems to work correctly on t210.
Here's link to edited kernel: https://www.upload.ee/files/10238882/kernel-SM-T210-werewolf-Ofast-UV.zip.html
{
"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"
}

Is it fully stable on SM-T211??. Is it the final version??

Hi,
@mat1371,
@lol28
Thank you for the kernel for T210R. Stable, overclocked to 1.42Ghz. I have an issue with the settings I make, they don't stick after reboot. I used kernel adiutor, EX kernel manager, Performance tweaker. I have busybox installed.
I've flashed Powerdaemon.disable.zip from Gr8nole, still the same.
Edit:
I've found Gr8nole's suggestion about deleting /system/bin/phservice. I deleted the file, rebooted, changed to governor to lionheart. It seemed to keep the settings.
Thanks!

[KERNEL] Nebula OOS/AOSP: (OP 6 & 6T) Latest on TG, Or Official Latest on sourceforge

{
"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"
}
Changelogs​
18.0.3: Fixed HBM mode switch, a few other small fixes, and improvements.
Qcacld now uses a profile system ported from CAF's qcacld-3.0 msm8996.
18.0.0: Updated Touchscreen & FP, Changed name of Zip Name, Latest OP sources with 4.9.159:
17.1.0: Built 100% CLANG: Last official for the 4.9.158 series.
17.0.2: Rebased whole new kernel, Updated commits, Build Fully With Clang 9 'DragonTC'.
16.8.3: Reformated code style, For faster optimized code, Now built with POLLY Thanks to @xanaxdroid
Reworked FP. Removed some unneeded TCP CONGS and some debugging code.
16.8.0: Removed most debugging stuff, toned down FP, updated a few other areas.
16.7.0: Fixed the data corruption issue, reworked some things. Calmed down CPU, Pocket Protection works again.
16.6.0: Rebuilt from previous edition. Smoother and faster.
16.4.0: Rebuilt from scratch under fresh new source.
16.3.0: This kernel is being released as is, I made many many changes, I would take heed
when installing this kernel, keep an eye on it. Some things I am not very happy about.
(Then why release? Because I need to make sure its not just me.)
16.1.9: Re-based Kernel, made some cosmetic changes, also reworked defconfig,
Gesture Controls for AOSP based ROMs, will not work, But OOS it will.
WiFi has been tested to work on .10 but many have complained that it will
only work when they upgrade to .11 (Keep this in mind when you report problem)
16.5.0: Both Stock and Custom AOSP Gestures work, (depending on your ROM)
16.1.0: New Download Location added: Also, this is probably my best release yet.
qcacld-3.0 is now compiled inline with Kernel.
Attention​
This is strictly created for OOS, but it has been tested on Custom AOSP based ROMs,
on AOSP, everything works, But WiFi and Gestures, (WiFi uses stock WLAN module) (Gestures, need the API, I never added yet)
One day I will add that in the near future if people on AOSP based ROMs request so.
Compilers Used​
Clang Compiler: DragonTC 9.x Compiled by me w/Polly
GCC Compiler: Uber 9.x <-- We build w/100% CLANG.
Features​
Linux 4.9.159 (w/latest OP/Linux)
CAF: LA.UM.7.3.r1-06700-sdm845.0
Linker: CLANG_LD <-- Yeah thats right, 100% CLANG
Makefile: Optimized to use POLLY
SafeStack (Disabled for now)
qcacld-3.0: (Compiled inline with Kernel)
CPU (New Overclocked Freq Table) (Added: 838mhz and 767mhz) By @pappschlumpf of SmurfKernel (Doesnt work as expected)
GPU (w/Overclock Freqs 767, 838)
AUDIT (Disabled) <Better Performance>
PROC_STRIPPED (Enabled)
Memory Compaction (Disabled)
DEBUG_ALIGN_RODATA (Enabled) <Better Performance>
FRAME_POINTER (Disabled) <Better Performance>
OPTIMIZE_INLINING (Enabled) <Better Performance>
gcma Guaranteed Contiguous Memory Allocator (default)
Simple Low Memory Killer By @Sultan (seems to work) (Causes Camera Issues)
CPU Input Boost By @sultan (Updated)
DevFreq Boost By @Sultan (Updated)
KLapse V4.0 - A kernel level livedisplay module by @tanish2k09
HZ=1000 (This is for now)
Memory Optimizations
Frame Pointers Disabled
Adreno Booster 2.2 By @tbalden
KCAL Color Control
Sound Control (w/gain Controls)
Touch Boost (W/Dynamic SchedTune Boost)
Boeffla WakeLock Blocker (v1.10)
Backlight Minimun Brightness (int)
High Brightness Mode (On/Off)
Override System VIB Settings (On/Off)
OnePlus Gesture Vibration (On/Off)
USB Fast Charge (On/Off)
Notification LED Fade/Speed/Intensity (On/Off)
Notification Vibration
Call Vibration
Sweet2Sleep Vibration​
Available Gestures​
Double Tap To wake
Sweep To Wake
OnePlus Gesture Vibration
Sweep To Sleep
Available IO/Scheds​
noop
anxiety
deadline
cfq (default)
fiops
sio
zen
maple
bfq
Available TCP Congestion Algorithms​
agilesd
westwood (default)
cubic
vegas
sociopath
Downloads​
OnePlus 6-6T (Nebula)
Links to my other Nebula Kernel Threads​
Nebula Telegram Group
OnePlus 6T Nebula Kernel Thread
OnePlus 6 Nebula Kernel Thread
XDA:DevDB Information
OnePlus 6/6T Nebula Kernel, Kernel for the OnePlus 6T
Contributors
Eliminater74, theknux
Source Code: https://gitlab.com/devoneplus/android-linux-stable-op6t_20190222/tree/oneplus/SDM845_P_9.0_CAF_WIP_20190224
Kernel Special Features:
Version Information
Status: Stable
Created 2018-12-08
Last Updated 2019-02-27

Reserved......

reserved b

??

Patiently waiting for OC.

Hello, nice to see you here.

Man I love to see new development.. patiently waiting on this one.thank you

dennisbednarz said:
Patiently waiting for OC.
Click to expand...
Click to collapse
The chances of OverClocking CPU is 49%, I know I can do it.
but it overwrites the max top freq, rather then add a new freq step..
Code:
if (i >= 27) { // the overclocked freq 2956800
src = 1;
div = 0;
lval = 154;
core_count = 1;
}
<-- This is supposed to see last main freq setting, which in this case is 27 steps,
Code:
struct osm_entry perf_ex = {
.lval = 154,
.ccount = 1,
.frequency = 2956800000,
.virtual_corner = 28,
.open_loop_volt = 1098,
};
<-- This creates the new step, or at least supposed too....
But problem is this, we dont have 27 steps, we only have 24, and looking at the dts file for the sdm845-2.dtsi, it shows a hell of alot more freq's up to 3.4ghrz.......
But I dont see our freq steps anywhere.. as some know, the TrustZone handles all the VDD and Voltage restrictions.. But the Table should still be listed..
But its not the correct table that we use..........
But good news is, I know our CPU can handle 3.4ghrz.. its even written in the dts settings already by default.........
But give me time and ill figure something out, I sent Email to the Original Author of the CPU OC Hack above... waiting to see what he says, he removed it from all his kernels, and another person that tried it
also removed it.. so I wanted to find out why..

I honestly don't think we really need OC on this phone, just my opinion though. The phone is already blazing fast especially with the OnePlus Labratory Boost Mode. I'd rather have Nebula be a stable, balanced/performance based kernel like the OP's previous kernels rather than have it packed full of features that don't really do much.

Stoked. I knew our planets would align again. Haven't been able to use your work since the G3 days.

Eliminater74 said:
The chances of OverClocking CPU is 49%, I know I can do it.
but it overwrites the max top freq, rather then add a new freq step..
<-- This is supposed to see last main freq setting, which in this case is 27 steps,
<-- This creates the new step, or at least supposed too....
But problem is this, we dont have 27 steps, we only have 24, and looking at the dts file for the sdm845-2.dtsi, it shows a hell of alot more freq's up to 3.4ghrz.......
But I dont see our freq steps anywhere.. as some know, the TrustZone handles all the VDD and Voltage restrictions.. But the Table should still be listed..
But its not the correct table that we use..........
But good news is, I know our CPU can handle 3.4ghrz.. its even written in the dts settings already by default.........
But give me time and ill figure something out, I sent Email to the Original Author of the CPU OC Hack above... waiting to see what he says, he removed it from all his kernels, and another person that tried it
also removed it.. so I wanted to find out why..
Click to expand...
Click to collapse
Now, see, you used s lot of words I do not understand. I'm mostly into userland stuff
Wouldn't overwriting the max top freq just modify the highest step to use that as the maximum frequency available for the CPU? Sure, this would cause the system to randomly jump between the next highest step and possibly 3.4GHz but it's a good start.

@Eliminater74 Good to see you on this device been awhile since I used Nebula..

dennisbednarz said:
Now, see, you used s lot of words I do not understand. I'm mostly into userland stuff
Wouldn't overwriting the max top freq just modify the highest step to use that as the maximum frequency available for the CPU? Sure, this would cause the system to randomly jump between the next highest step and possibly 3.4GHz but it's a good start.
Click to expand...
Click to collapse
Yeah I can do it.. but between 2.6 and 2.9 is a huge step, just as 2.6 and 3.4 which is what your talking about...........
the freq that gets overwritten is the 2.8...........
I am working on trying to figure out the deal with it.. as I said, its supposed to add a step which would be the 2.9 above the 2.8, but it didnt.
what it did was take the 2.8 and changed it to 2.9...... I could change the 2.8 to anything really.. even 3.4 ....... but again....... its a dirty hack that I dont feel right with......

Eliminater74 said:
Yeah I can do it.. but between 2.6 and 2.9 is a huge step, just as 2.6 and 3.4 which is what your talking about...........
the freq that gets overwritten is the 2.8...........
I am working on trying to figure out the deal with it.. as I said, its supposed to add a step which would be the 2.9 above the 2.8, but it didnt.
what it did was take the 2.8 and changed it to 2.9...... I could change the 2.8 to anything really.. even 3.4 ....... but again....... its a dirty hack that I dont feel right with......
Click to expand...
Click to collapse
I'm personally just interested in 2.96 so RoG phone users can't bully me anymore

Trying to flash this and it said
unpacking ram disk failed aborting
Update process failed with error: 1
Error installing zip file
Tried uploading a screenshot but to wouldn't let me did I flash it wrong or something or is this a bug

DarkNeo253 said:
Trying to flash this and it said
unpacking ram disk failed aborting
Update process failed with error: 1
Error installing zip file
Tried uploading a screenshot but to wouldn't let me did I flash it wrong or something or is this a bug
Click to expand...
Click to collapse
Using twrp?

zplit said:
Using twrp?
Click to expand...
Click to collapse
ya

@Eliminater74 I don't know if this is a bad question in terms of ones work being separate from another, but have you talked to pappschlumpf about the OC?

Causical said:
@Eliminater74 I don't know if this is a bad question in terms of ones work being separate from another, but have you talked to pappschlumpf about the OC?
Click to expand...
Click to collapse
Yes, they have both talked already. Just have to sit back and wait...

hey @Eliminater74
great to see nebula rise again! I wish you the best of luck for this project!
Also replied in slack to you

[KERNEL] [blu_spark r218 OP8/Pro/T] [A13 Custom]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Kernel features:
Build with custom upstream LLVM 14.x (Clang 14.0.6 + LLD linker + IAS)
Full -O2 build with device and target flags enhanced, build improvements and compiler fixes, etc
Less is more: stockish OP8 builds based on OnePlusOSS/android_kernel_oneplus_sm8250 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 sm8250 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)
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 and backlight scale option
Gamepad support enabled (xbox, ps4, switch)
USB Fast Charge (USB mode up to 900mA with MTP on)
FS fsync toggle on/off
Wakelock blockers available
wireguard support
CDROM emulation on mass_storage (compatible with DriveDroid 0.10.36+)
Compatible with Kernel Adiutor, EXKM, FKM and others
DOWNLOAD KERNEL ZIP
FKM download configs: oos | custom
(No mirrors please)​
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/op8
Don't forget to hit thanks, it's free
OnePlus 8 Pro development unit donated by OnePlus. Big shouts to them
Very proud of being on the OnePlus Developer Program, special thanks to dev relations team.

blu_spark r12 release
All right crew!
It's that time again, 1st build is up :highfive:
This kernel source is unified for OP8/Pro, don't know how it will run in the regular model (can only test in the Pro). Let me know.
At the moment we're maybe at 80% of the usual goodies, get a nice and stable base and go from there.
I'm building with clang currently got some hiccups with gcc. I'll probably revisit this in the future but it will need more TLC.
You can now use FKM download kernel feature, just import the links bellow in the app :highfive:
blu_spark_r12release
FKM download configs: oos | custom
Build with latest Google Clang version 11.0.2 (Android 11) - blu_gcc may come in the future, needs som TLC
Synchronize codes for OnePlus 8 Oxygen OS 10.5.9.IN21AA and OnePlus 8 Pro Oxygen OS 10.5.10.IN11AA
Build errors and warnings fixes
Compiling improving and target optimizations
Goodies: IO and filesystem stuff, priorities and UX, touchboost, zram, wakelock blocker, haptic and gestures level, adrenoboost, etc
wireguard updates (v1.0.20200611)
init adjust for sdm8250
AnyKernel3 latest updates
For root, stable Magisk 20.4 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

ur kernel is great for daily use when I have 6t, it's fast, smoot, and stable. do u plan to build one for oneplus 8?

Great to see your blu-spark here! Kudos

Great job! Any list of the best settings to activate for your kernel in FKM? Can't manage to activate westwood TCP method, it gets stuck to reno, for example. Or any config file to have the best settings selected, maybe? Sorry, I'm not too familiar with FKM yet.

Hey there, welcome. Nice to see you here.
Just one question, why are so many features listed in the OP and many or most not in the sources on GitHub? Isn't this a copy paste error?
Sent from my Pixel 4 XL using Tapatalk

orochi9999 said:
ur kernel is great for daily use when I have 6t, it's fast, smoot, and stable. do u plan to build one for oneplus 8?
Click to expand...
Click to collapse
Has it is doesn't work? idk.
At the moment I'm focused on the bringup.
Surfeur-des-Reves said:
Great job! Any list of the best settings to activate for your kernel in FKM? Can't manage to activate westwood TCP method, it gets stuck to reno, for example. Or any config file to have the best settings selected, maybe? Sorry, I'm not too familiar with FKM yet.
Click to expand...
Click to collapse
I already inject settings I see importanton the background. TCP method is westwood by default, that reno situation is a bug from the app, franco is on it :good:
tbalden said:
Hey there, welcome. Nice to see you here.
Just one question, why are so many features listed in the OP and many or most not in the sources on GitHub? Isn't this a copy paste error?
Sent from my Pixel 4 XL using Tapatalk
Click to expand...
Click to collapse
Hey. WIP and will come soon after.

eng.stk said:
Hey. WIP and will come soon after.
Click to expand...
Click to collapse
great to see ya here mate... i just got my pro... will teat ince i feel like rooting lol

eng.stk said:
Has it is doesn't work? idk.
At the moment I'm focused on the bringup.
I already inject settings I see importanton the background. TCP method is westwood by default, that reno situation is a bug from the app, franco is on it :good:
Hey. WIP and will come soon after.
Click to expand...
Click to collapse
it's not working on regular 8

After installing this kernel I'm getting an option to boost GPU clock to 900 MHz. This also resulted in a much higher compute score. Is this normal? @eng.stk

On8 not working

Cool to see another old kernel dev from the nexus 5 days xD

orochi9999 said:
it's not working on regular 8
Click to expand...
Click to collapse
Smturbo said:
On8 not working
Click to expand...
Click to collapse
Hum too bad. Seems like there's driver differences between the models, we'll see what can be done ib the future.
For now I'll concentrate on the pro.
akshat207 said:
After installing this kernel I'm getting an option to boost GPU clock to 900 MHz. This also resulted in a much higher compute score. Is this normal? @eng.stk
Click to expand...
Click to collapse
Wait, what? Seem like that app is on acid lol
Sent from my blu_spark'd OnePlus

kevp75 said:
great to see ya here mate... i just got my pro... will teat ince i feel like rooting lol
Click to expand...
Click to collapse
hjjiang said:
Cool to see another old kernel dev from the nexus 5 days xD
Click to expand...
Click to collapse
Welcome guys, nice device choices [emoji16]
Sent from my blu_spark'd OnePlus

eng.stk said:
Wait, what? Seem like that app is on acid lol
Sent from my blu_spark'd OnePlus
Click to expand...
Click to collapse
Then how did I get 4351 OpenCL score on Geekbench lol?

akshat207 said:
Then how did I get 4351 OpenCL score on Geekbench lol?
Click to expand...
Click to collapse
You probably still have custom dtb from the kernel that have gpu oc, since this kernel doesn't replace the dtb and you switched kernels without keeping that in mind you ended up with mixed kernel images and dtbs.

acuicultor said:
You probably still have custom dtb from the kernel that have gpu oc since this kernel doesn't replace the dtb and you switched kernels without keeping that in mind you ended up with mixed kernel images and dtbs.
Click to expand...
Click to collapse
So, how is that much GPU OC possible? that's almost double the stock max frequency!
EDIT: You were right, it was from "Evira Kernel". Now my question is, is that much OC safe? That's insane.
Do note that my device didn't get hot when I was running the benchmark even at 900 MHz.

Smturbo said:
On8 not working
Click to expand...
Click to collapse
what was the problem for the regular OnePlus 8? bootloop and what region was ur phone

hjjiang said:
what was the problem for the regular OnePlus 8? bootloop and what region was ur phone
Click to expand...
Click to collapse
At the bootloader unlock screen, after a few seconds, the text turns green and has black lines through it, when it finishes booting, by the screen goes completely black. Vibration and sound still work though. Have to force power off and back to TWRP to restore stock boot.

blu_spark r18 release
All right crew!
New build is up :highfive:
This kernel is only tested for the Pro variant which I have, regular OP8 support may come in the future.
You can now use FKM download kernel feature, just import the links bellow in the app :highfive:
blu_spark_r18 release
FKM download configs: oos | custom wip
Full LLVM tools build (Clang + LLD), add a couple build fixes/improvements
drivers: misc: power: implement usb2 fast charge mode
power: smb5-lib: reset level on removal
drm-msm-dsi: add backlight min option
fs: exfat: version 2.2.0-3arter97
cpufreq: schedutil: make iowait boost optional
remove and disable some debug and logging
defconfig: enable overlay and disable dtb append
init adjustments
For root, stable Magisk 20.4 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