[KERNEL][GT-I9195][CM-12.1][5.1.1][20150920-4] Chaco - Galaxy S 4 Mini Android Development

Kernel based on arco68's source for CM-12.1. I am using this kernel on my 9195
chaco-20150920-4
merged with latest changes made by arco68
reverted L2 OC to avoid random reboots
zImage compressed with lzo again
crond enabled with a script in /etc/init.d/
fstrim every 12 hours
drop_cache every 2 hours
sqlite3 Vacuum Cleaner everyday at 4am
add your own rules in /data/cron/root
dnsmasq enabled with script in /etc/init.d/
add you own rules in /data/local/dnsmasq-host
chaco-20150603
L2 OC/UV and changes in CPU freq table by @lombartz
CPU UV set -50 by default
Implemented script to autodetect kind of partition. Now you can use ext4 or f2fs thanks @F4k
Disable journal on /system and /cache partition with a script inside flashable zip if you are using ext4
kernel compressed with xz
chaco-20150531-2
changed ro.debuggable=1 to ro.debuggable=0 in default.prop to get Root access in developer options menu again.
chaco-20150531
enabled CPU Overclock (OC) support. I haven't enabled it before because I never use CPU OC, this was a petition made by haloass65.
chaco-20150530
set selinux to permissive
added zram support
added other TCP Congestion control modules, illinois
IO: removed usless test & debug things
merged with last changes made by arco68
chaco-20150528
based on arco68's source
compiled with Christopher83 Linaro GCC 4.9-2015.03 for cortex a15
disable journal on /system, script inside flashable zip
this kernel only works with system(ext4), /data(f2fs) and /cache(f2fs)
added KSM support
enabled bounce for better I/O performance
kernel and ramdisk compressed with lzo
Added some TCP Congestion control modules, veno and westwood, set veno as default
AIO: Don't plug the I/O queue in do_io_submit(). Asynchronous I/O latency to a solid-state disk greatly increased
Disabled GFS and enabled ARCH_POWER
Disabled Adaptive Voltage Scalling (AVS)
Added CPU Undervolt (UV) support
Added CPU Underclock (UC) support
Added Graphite Optimization
Added option for LTO Optimization
Added -O3 and Some optimization flags
Disabled Kernel debugging
Disabled IO stats
Disabled more debugging
Disable some tracers
Added optimized ARM RWSEM algorithm
Optimized SLUB
Add NEON accelerated XOR implementation
Optimize apply_slack() for size and speed
disabled add_random for more performance on SSD's
enabled NOSEC optimization
disabled crc check for 30% extra performance in IO
entropy tweaks
noatime and nodiratime-franciscofranco
some more
To install:
you can use twrp by f4k, that is what I am using or another recovery compatible with f2fs file system.
Root access?
You can use the SuperSu flashable zip in the attachments
Source
https://github.com/chacox/s4mini_9195_cm12.1_kernel
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks to:
-arco68
-f4k
-google
-others

Does your kernel support BLN?

Please add I9192 here

Does your kernel support BLN?
Click to expand...
Click to collapse
Yes, it has bln support
Sent from my GT-I9195

Good job, latest official nightly boots no problem. The only thing is root access isn't showing in developer options, therefore no root..

Tirofog said:
Good job, latest official nightly boots no problem. The only thing is root access isn't showing in developer options, therefore no root..
Click to expand...
Click to collapse
I've never used root under developer options but I don't know why it does not appear, but I will try to check it.
I've always used SuperSu. I uploaded a flahseable zip if you want to try it

Didn´t work for me on latest AICP nightly, ended up in a bootlop. Anyone same problem with latest AICP?

unit999cn said:
Please add I9192 here
Click to expand...
Click to collapse
I won't do it for now, maybe later

A small update (20150531) for a petition made by haloass65.
Recompiled just to enable CPU OC.

Great kernel!
Are there any chances to get in the next version a couple more features?
1. Enable Call Recording
2. Add support for F2FS for /system partition
3. SIO scheduler
4. USB OTG (with Y adapter)
5. GPU OC to 600 MHz / GPU UV

Deluxestar said:
Didn´t work for me on latest AICP nightly, ended up in a bootlop. Anyone same problem with latest AICP?
Click to expand...
Click to collapse
Maybe there are some changes inside ramdisk in AICP. Does it reboot in Samsung's logo?
Runner_cz said:
Great kernel!
Are there any chances to get in the next version a couple more features?
1. Enable Call Recording
2. Add support for F2FS for /system partition
3. SIO scheduler
4. USB OTG (with Y adapter)
5. GPU OC to 600 MHz / GPU UV
Click to expand...
Click to collapse
I want to add a lot of stuff but it's hard and I am trying my best!
I tried f2fs on system in my first release. I mean I can modify fstab file to make it mount system as f2fs partition but the problem is with the recovery or the CM-12.1 flasheable zip. I tried to modify the update-script inside it but it did not work, it changed system to ext4 automatically, so I decided to leave it as ext4 without journal for now. If you or someone can make the CM-12.1 flashable zip work with
f2fs, I can modify ramdisk again.

Tirofog said:
Good job, latest official nightly boots no problem. The only thing is root access isn't showing in developer options, therefore no root..
Click to expand...
Click to collapse
can you try 20150521-2 version?, It's back Root access under developer options menu.

chacox said:
I tried f2fs on system in my first release. I mean I can modify fstab file to make it mount system as f2fs partition but the problem is with the recovery or the CM-12.1 flasheable zip.
Click to expand...
Click to collapse
Nice to see your comments and your own desire to make it even better!
For /system I menat actually to support both ext4 and f2fs, for example as it's done in the f4k's kernel. And yes, of course this means manual modification to every CM12.1 update ZIP - but those, who go the way of /system f2fs migration are normally prepared for that.
As for the schedulers - not only SIO, but also ZEN would be welcome, as well as Lionheart for the governors...

this kernel only works with system(ext4), /data(f2fs) and /cache(f2fs)
Click to expand...
Click to collapse
So, this means that I can't use this kernel with the stock CM12.1 image?

ztoldy said:
So, this means that I can't use this kernel with the stock CM12.1 image?
Click to expand...
Click to collapse
it won't boot if you have all partitions formatted with ext4 like stock ramdisk CM12.1 brings them.
I could try to implement f4k's script which is capable to detec the type of partition and it does not matter whatever your partitions are.

I could try to implement f4k's script which is capable to detec the type of partition and it does not matter whatever your partitions are.
Click to expand...
Click to collapse
it would be great because your kernel sounds good

Thanks, will try 20150531-2 in a couple of days when I get some time and report back then.

Runner_cz said:
Great kernel!
Are there any chances to get in the next version a couple more features?
1. Enable Call Recording
2. Add support for F2FS for /system partition
3. SIO scheduler
4. USB OTG (with Y adapter)
5. GPU OC to 600 MHz / GPU UV
Click to expand...
Click to collapse
correct me if I am wrong but Call Recording is more related with Rom, not kernel, isn't it?
I was taking a look at f4k's source for USB OTG, I won't be able to test it because I don't have the cable but I could try to implement it. I am working now with his script to autodetect filesystem partitions.

chacox said:
correct me if I am wrong but Call Recording is more related with Rom, not kernel, isn't it?
I was taking a look at f4k's source for USB OTG, I won't be able to test it because I don't have the cable but I could try to implement it. I am working now with his script to autodetect filesystem partitions.
Click to expand...
Click to collapse
Call record, to be done properly, should be first correctly supported by the kernel and in most cases needs root (there are of course some exceptions, like Defy Mini default firmware or many China devices, that have it from the stock). Then there are either apps to call this function, or the system (firmware or if you call it ROM) apps, that also may have or may have not this function. But until it's activated in the kernel - apps can't use this function (ok, can't use it properly. There are some cool apps like Boldbeast that are so clever that somehow manage to record calls properly even on the not-rooted devices without standard kernel support for the feature. Don't ask me how they do it' I don't know this secret.. ). BTW the official cm12.1 for serranoltexx has brocken call recording feature since recent nightlies (frm apprs. 20.05.2015), so there is no way to check its internal functionality for now.
For OTG, hence our device don't have the power output on the USB port - we need to use the OTG Y-cable with external power supply. I don't have it atr hand at the moment, but as soon as I get it - will be happy to help testing.
Anyway, so far the kernel is very good and is not over-bloated with too many features. I'd say if we stop on implementing my list of the 5 requested features - this would cover 99.9% needs.
Really, it's great to have a custom kernel that works fine with official CM12.1. Thumbs up for your efforts!

Runner_cz said:
Nice to see your comments and your own desire to make it even better!
For /system I menat actually to support both ext4 and f2fs, for example as it's done in the f4k's kernel. And yes, of course this means manual modification to every CM12.1 update ZIP - but those, who go the way of /system f2fs migration are normally prepared for that.
As for the schedulers - not only SIO, but also ZEN would be welcome, as well as Lionheart for the governors...
Click to expand...
Click to collapse
Absolutely pointless to insert these schedulers and governors.
On this phone ATM the FIOPS and DYNABOOST is the best combo that you can get.
I/O Schedulers
Governors

Related

[KERNEL][T210/T210R/T211] blackhawk kernel 2.1

First unofficial kernel for Galaxy Tab 3 Marvell PXA988, reported works on T210 and T210R variant (T210 version) and T211 (T211 version)
Kernel source: https://github.com/kumajaya/android_kernel_samsung_lt02
Kernel modules source: https://github.com/kumajaya/android_kernel_samsung_lt02_modules
Features:
Based on my kernel commits and modules commits:
Open source exFAT filesystem driver from Samsung OSRC
Configurable touchscreen orientation, so we can use this kernel as touch based recovery kernel
Override 1MB ramdisk size limitation + xz compressed ramdisk. CWM recovery need > 2MB ramdisk, no blackhawk = no CWM/CWM based recovery
Zram support. Update LZO compression library to upstream version, optimized for arm processor
Linaro gcc compiler. Update Marvell P4JB CPU init routines for linaro
Hardcoded ION carveout memory. Old version bootloader will boot this kernel without blank pop up bug!
Using the latest T210R MJ1 GPU, WiFi, bluetooth, and T211 MI3 telephony drivers. This kernel always bring the appropriate kernel modules inside /system/lib/modules to prevent kernel modules incompatibility issue
Single source for all T21x variants, different kernel config, different flashable zip for T211
Integrated self compiled busybox, fstrim applet included for a lag fix
Auto root, no need to flash any root solution
Init scripts support (/system/etc/init.d, /data/local/userinit.d, and /data/local/userinit.sh)
Kernel module loader template /system/etc/init.d/02modules
Post boot template /system/etc/init.post_boot.sh
Zram manager, over "adb shell" or Terminal Emulator:
Code:
su
setprop persist.service.zram 25
to set 25% memory size zram, persistent.
Code:
su
setprop persist.service.zram 0
to disable zram. Needs reboot.
Samsung Open Source Release Center: http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=sm-t21
Special Thanks:
@gr8nole, @hkjr, @klopeck
Note:
I don't own this tablet myself. This is the side result of my work and @gr8nole, making a working kernel for recovery. For better development support, please consider donating.
Both kernel and kernel modules source on my github account already, feel free to fork it. "Don't reinvent the wheel, unless you plan on learning more about wheels."
Flash at your own risk!
Changelog 2.1 (08/02/2014):
Merge Samsung OSRC T210R MK1 and T2105 MK3 update (platform, framebuffer, battery/charger driver, etc): https://github.com/kumajaya/android_kernel_samsung_lt02/commits/master
Merge Samsung OSRC T2105 MK3 modules update (new WiFi driver, Bluetooth, GPU driver update, etc): https://github.com/kumajaya/android_kernel_samsung_lt02_modules/commits/master
Newer su binary, Supersu.apk removed. Auto root still work, you can install Super SU from Google Play by yourself
Storage swapper script included. To set your external card as internal, type "setprop persist.customboot.sdcard external" over Terminal Emulator or "adb shell" as root, reboot. Type "setprop persist.customboot.sdcard internal" or delete /data/property/persist.customboot.sdcard to restore to default, reboot.
Changelog 1.8.1 (31/10/2013), T211 only:
Fix T211's GPS issue: https://github.com/kumajaya/android...mmit/f0081639f394f5ad287531d09f60bdacb5fe4c85
Merge Samsung OSRC T211 MI3 telephony source code: https://github.com/kumajaya/android...mmit/a7af2e4564f655fe1fe428477a3f64cf2cd5e72b
Update T211 ramdisk
Changelog 1.8 (29/10/2013):
Samsung OSRC SM-T210R MJ1 kernel update
Kernel: https://github.com/kumajaya/android...mmit/654d3f7b60339d6bcc300e96a71baa46d79f85af
Modules: https://github.com/kumajaya/android...mmit/d970d6633c0c942d891edda82493299423735a38
Untested!
Initial T211 support, untested! BUG: GPS fail to start
Changelog 1.7.1 (15/9/2013):
Ramdisk based on 1.6-linaro-tweaks
Kernel compiled using Linaro gcc 4.7, SM-T210R MI1 update applied
Hardcoded ION carveout memory, the new kernel source need "ioncarv" kernel parameter from bootloader. This solution fix blank pop up windows problem
Untested!
Changelog 1.7 (13/9/2013):
Ramdisk based on 1.6-linaro-tweaks
Kernel compiled using Linaro gcc 4.7, SM-T210R MI1 update applied
Untested! BUG! The current bootloader have no "ioncarv" kernel parameter
Changelog 1.6-linaro-tweaks (12/9/2013):
Based on 1.6-linaro, blackhawk standard tweaks applied:
Integrated busybox
Auto root
Init scripts support (/system/etc/init.d, /data/local/userinit.d, and /data/local/userinit.sh)
Kernel module loader template /system/etc/init.d/02modules
Post boot template /system/etc/init.post_boot.sh
Zram manager, over "adb shell" or Terminal Emulator:
Code:
su
setprop persist.service.zram 25
to set 25% memory size zram, persistent.
Code:
su
setprop persist.service.zram 0
to disable zram.
Untested!
Changelog 1.6 (12/9/2013):
Cleancache disabled
Kernel with USB host support in separated package
Kernel compiled using Linaro gcc in separated package
Untested!
Changelog 1.5 (11/9/2013):
Revert Samsung OSRC SM-T210L kernel update
Remove PN547 NFC support, android_vibrator and timed_gpio
Enable USB host and mass storage support, a lot of USB HID drivers (keyboard, mouse, etc), PS3 and Xbox controller, and USB GSM dongle
Untested!
Changelog 1.4 (11/9/2013):
Samsung OSRC SM-T210L kernel update
lib/lzo: update LZO compression
staging: zcache/zsmalloc: change x86 dependency to arm
staging: zcache: always enabled
Full source changelog: https://github.com/kumajaya/android_kernel_samsung_lt02/commits/master
Untested! BUG!
Changelog 1.3 (11/9/2013):
Fix IR LED permission
Disable OTA recovery update
Untested!
Changelog 1.2 (10/9/2013):
Add PN547 NFC support. android_vibrator and timed_gpio as module
Untested!
Changelog 1.1 (10/9/2013):
CIFS filesystem support
Disable a lot of kernel debug (SLUB debug, tracing, and a lot of things from kernel hacking config) for size and performance
Untested!
A screenshot from @hkjr:
{
"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"
}
I hope this is useful.
Last, for more description.
SM-T210[R/L], SM-T211: Marvell PXA988 based platform, 1.2GHz dual core processor
SM-T21x variant information, based on kernel defconfig:
1. lt02wifi: base configuration - T210
2. lt02wifiue: WiFi + IR remote - T210R, US market
3. lt02wifidtv: WiFi + digital TV - T210?, South America market?
4. lt02wifilgt: WiFi + NFC - T210L, Korea market
5. lt023g: WiFi + 3G - T211
6. lt023gdtv: 3G + digital TV - T211?, South America market?
SM-T215: MSM based platform, 1.7GHz dual core processor, LTE
Running well so far. You know I'm here for testing, just let me know when you need something.
gr8nole said:
Running well so far. You know I'm here for testing, just let me know when you need something.
Click to expand...
Click to collapse
Please try 1.1 :good:
ketut.kumajaya said:
Please try 1.1 :good:
Click to expand...
Click to collapse
Boots up fine. :good: Anything in particular you need me to test?
Sent from my SM-T210R using xda app-developers app
gr8nole said:
Boots up fine. :good: Anything in particular you need me to test?
Sent from my SM-T210R using xda app-developers app
Click to expand...
Click to collapse
Not for now. Just use it and report me for any bug. Please try 1.2
ketut.kumajaya said:
Not for now. Just use it and report me for any bug. Please try 1.2
Click to expand...
Click to collapse
gonna give 1.2 a run now.
thanks for continuing development on the 3.7, it's definitely appreciated!
ketut.kumajaya said:
Not for now. Just use it and report me for any bug. Please try 1.2
Click to expand...
Click to collapse
Flashed 1.2 and System Tuner reports that both cores are maxed out (1.2ghz) and do not scale back down. I gave it a few minutes after restart and they remained maxed out. (Wifi off, nothing syncing).
Flashed back to 1.1 and everything looks normal again.
Not sure how reliable System Tuner is.
EDIT: Nevermind...flashed 1.2 again (wiped cache and dalvik) and all is well. Both cores scaling properly now.
gr8nole said:
Flashed 1.2 and System Tuner reports that both cores are maxed out (1.2ghz) and do not scale back down. I gave it a few minutes after restart and they remained maxed out. (Wifi off, nothing syncing).
Flashed back to 1.1 and everything looks normal again.
Not sure how reliable System Tuner is.
Click to expand...
Click to collapse
I'm seeing similar behavior.
does system tuner allow for adjusting settings? i'm using kernel tuner - http://forum.xda-developers.com/showthread.php?t=1719934
& it was showing the 'min' value for both cores was set to 1205Mhz, the same as the max.
i've backed it down to 312Mhz on both cores & all seems to be good.
SOHKis said:
I'm seeing similar behavior.
does system tuner allow for adjusting settings? i'm using kernel tuner - http://forum.xda-developers.com/showthread.php?t=1719934
& it was showing the 'min' value for both cores was set to 1205Mhz, the same as the max.
i've backed it down to 312Mhz on both cores & all seems to be good.
Click to expand...
Click to collapse
Please see the edit to my post above.
I don't think System Tuner does a very good job reporting dual-core devices, but I haven't found a better app yet (still looking).
gr8nole said:
Please see the edit to my post above.
I don't think System Tuner does a very good job reporting dual-core devices, but I haven't found a better app yet (still looking).
Click to expand...
Click to collapse
Trickster MOD much simpler.
running great. Thanks man..
Looks like the IR is not working. I'm going to flash back to stock to make sure it works correctly with that.
Edit: IR blaster works on stock but not on this kernel (v1.2).
Let me know if you need any files from me to get a possible fix.
Does this kernel have more cpu governor or/and I/O governor?
EDIT: Oh nevermind i checked your source.
gr8nole said:
Looks like the IR is not working. I'm going to flash back to stock to make sure it works correctly with that.
Edit: IR blaster works on stock but not on this kernel (v1.2).
Let me know if you need any files from me to get a possible fix.
Click to expand...
Click to collapse
Please try v1.1 to ensure NFC integration not interfere IR.
ketut.kumajaya said:
Please try v1.1 to ensure NFC integration not interfere IR.
Click to expand...
Click to collapse
Just tried 1.1 and IR doesn't work on it either.
gr8nole said:
Just tried 1.1 and IR doesn't work on it either.
Click to expand...
Click to collapse
Maybe just a permission derp, please upload your stock boot.img here.

[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

[EOL][KERNEL][STABLE][TW][6.0.1][CPK2][03.01.17][SM-T80X] IronStock-Kernel V3.2

IronStock-Kernel for SM-T800/T805 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 based on 6.0.1
The aim of this kernel is to be as stock as possible with improved performance and up to date linux version. I included this builds in all IronRom versions but most of you probably want to use it as standalone kernel. So here you go with the new kernel
By the way if you want to visit my rom: IronRom.
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 Toolchain 5.3
- Build with CPK2 kernel source!
- Latest Linux version 3.4.113, is always up to date
- Performance and Batterylife improved
- Choose between different CPU governors: performance, powersave, userspace, ondemand, interactiv (default), conservative
- Built with latest ramdisk sources from samsung (CPK2)
- I/O schedulers: CFQ (Default), No-op, Deadline
- Critical TCP bug fixed
- Allow ADB-Insecure
- TCP (Network) control: Bic (default), Reno, cubic, Westwood, Highspeed, Hybla, HTCP, Vegas, Veno, Scalable, LP, Yeah and Illinois
- SeLinux is set to permissive
- UKSM build in
- Init.d support
- Wakelock fixed (google problem)
- All samsung related configs disabled (as knox, tima, restrict rooting)
Download:
V3.2 on AndroidFilehost
All releases on AndroidFilehost
Bugs/Problems:
- None
Instructions:
1. Download kernel
2. Boot into recovery mode
3. Flash kernel
4. Flash any other file which affects ramdisk (such as supersu, xposed, magisk etc.)
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
- dorimanx
- AndreiLux
- halaskz
- neobuddy83
XDA:DevDB Information
IronStock for chagallxx, Kernel for the Samsung Galaxy Tab S
Contributors
Tkkg1994
Source Code: https://github.com/Tkkg1994/IronKernel/
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: V3.2
Stable Release Date: 2017-01-03
Created 2017-01-03
Last Updated 2017-07-14
Reserved
Reserved
Is this kernel integrated in your rom 3.2?
onairda said:
Is this kernel integrated in your rom 3.2?
Click to expand...
Click to collapse
Yes, is integrated.
Testing
Thanks for the kernel!! I'm testing it now and it feels good so far
m.
report
After rebooting the device the subscription to the Wi-Fi network get lost, means I have to reenter the password after every reboot. I don't know if it's the kernel like it is or because I changed the TCP congestion fromm cubic to highspeed. I don't have any experience with this feature. I could change back to cubic and check if the network subscription sticks... .
m.
meduza2 said:
After rebooting the device the subscription to the Wi-Fi network get lost, means I have to reenter the password after every reboot. I don't know if it's the kernel like it is or because I changed the TCP congestion fromm cubic to highspeed. I don't have any experience with this feature. I could change back to cubic and check if the network subscription sticks... .
m.
Click to expand...
Click to collapse
Change in your build.prop secure storage from true to false and it will work again
Sent from my SuperMan powered SM-G930F
Indeed, changed it this way: “ ro.securestorage.support=false “ and it sticks Thanks a lot!!
m.
freaksamael said:
Yes, is integrated.
Click to expand...
Click to collapse
Thanks for the answer
@Tkkg1994 ,
the tab with your kernel is running much smoother then with pure stock - thanks once more!
m.
Anyway to flash back to Stock Kernel?
XDA00000 said:
Anyway to flash back to Stock Kernel?
Click to expand...
Click to collapse
Would a boot.img backup in this case suffice? I haven't flashed the kernel yet but a boot image backup would contain the old kernel as well. The question is mostly if there are any other modifications that are being done.
XDA00000 said:
Anyway to flash back to Stock Kernel?
Click to expand...
Click to collapse
If you don't have the zip file, I would say, you could restore the boot and system partition from your backup, this should bring back the backuped kernel.
m.
Does your kernel support f2fs ?
Claros22 said:
Does your kernel support f2fs ?
Click to expand...
Click to collapse
.... would be nice but I didn't see it in OP ...
m.
Claros22 said:
Does your kernel support f2fs ?
Click to expand...
Click to collapse
I haven't written it to OP but it should at least /data and /cache (untested)
XDA00000 said:
Anyway to flash back to Stock Kernel?
Click to expand...
Click to collapse
Yeah just restore back boot.img backup, nothing else needed
Tkkg1994 said:
I haven't written it to OP but it should at least /data and /cache (untested)
Click to expand...
Click to collapse
Ok nice I will try it then. By the way it is better to use ext4 for other partitions than /data and /cache.
Claros22 said:
Ok nice I will try it then. By the way it is better to use ext4 for other partitions than /data and /cache.
Click to expand...
Click to collapse
All other partitions are simply not supported
Kernel works great so far. No issues and performance feels good.
What's the best way to switch between SELinux permissive and enforcing on this kernel should one want to experiment with that? Some solutions don't seem to like KNOX but it should be disabled on the kernel, too, right? I'm still struggling to get Magisk Hide working so I'm feeling experimentative.

[Kernel] AX7Kernel - STOCK B15 / B19

{
"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"
}
Hello!
I want to introduce my first custom kernel for the ZTE Axon 7. This is based of several sources, I cherry-picked commits to make improvements to the stock LOS kernel. I'm not a developer, but i really like to port stuff over .
We'll have two kernels one based off LOS sources and will try to have updated with each and every commit that is submitted and the other one will be Stock ZTE sources based. If you want to request for specific features, let me know and i'll do my best to bring them over.
Special Features:
BLX (Battery Longevity eXtender) added, check Post#2 for instructions.
Updated to lastest LOS Stock Kernel
Added a few governors like: lionfish / despair / darkness / blu_active / wheatley / ironactive and bioshock
added a few IO Schedulers: Tripndroid / Zen / SioPlus / VR
Kcal Color Control driver
USB Fast Charge
SafetyNet Patch (Bypass bootloader unlocked check)
Dynamic Fsync control
a little Overclock
Motorola Quickwake
Extended battery charge time from 30s to 100s
and manny other small fixes (you can check the commits in the sources)
Download
Disclaimer: I am not responsible if you use this and brick your device or if your device blows up, implodes, flames start shooting from it or it kills your neighbor's dog. Flash at your own risk. I am not responsible.... It was the other guy... I swear....
Latest STOCK Release: AX7Kernel-STOCK-R9
Known issues:
02.13.2017 - CPU Freq don't always stick, known issue caused by other drivers. Phone will eventually set your frequencies, dont' panic.
Special Thanks to:
jcadduono
franciscofranco
bedalus
lord_boeffla
flar2
sultanxda
...and many others from whom i cherry pick commits... Sorry if I forgot to mention anyone!
XDA:DevDB Information
AX7Kernel, Kernel for the ZTE Axon 7
Contributors
jimbo77
Source Code: https://github.com/Jimbo77
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: R9
Stable Release Date: 2017-03-16
Created 2017-03-17
Last Updated 2017-03-22
Reserved
How to Bypass SafetyNet bootloader and/or root checks
* If comming from a clean flash of ROM or GAPS only do the following:
Magisk Approach
Flash the UnSu file from HERE
Flash my latest Kernel
Flash the latest Magisk from this thread:
Donwload Magisk Manager from the Playstore
Enable Magisk Hide in Magisk Manager
Profit, SafetyNet Checks will pass, all green!
SuperSU Approach
Flash the UnSu file from HERE
Flash my latest Kernel
Flash the latest SuperSU from this thread:
Donwload RootSwitch APP from HERE
Unpack the zip and install the apk inside it
Open Root Switch and disable root
Profit! SafetyNet checks will all be green!
Battery Life Extender (BLX) feature
In order to configure the cap you'll have to navigate to:
Code:
/sys/class/misc/batterylifeextender/charging_cap_level
edit the file and put the cap you want the battery to charge to, i won't recommend setting a cap lower than 90% cause then the phone could abruptely stop a fast charging cycle and damage your battery. If you want to have your phone charging to 100% just put 100 in the file and close it. No need to reboot, just plug and unplug your charger.
On a side note, this value will be set at 97% after every boot. So you'll need to manually change it back to 100.
Reserved
AX7Kernel Changelogs:
AX7Kernel R9 - 03/22/2017
Updated Source with ZTE Changes in B19 source code.
AX7Kernel R8 - 03/17/2017
Fixed NFC issue with B19 builds.
Updated WLAN driver to LA.UM.5.5.r1-03800-8x96.0 github from CAF
Fixed the SDCard error shown in R8 version from 03.16
AX7Kernel R8 - 03/16/2017
Updated to newest B15 Source dropped by ZTE a few days ago. This is mainly a Maintenance Update. Keep in mind the Kernel works with 7.1.1 but it breaks NFC, will be fixes most likely until a new sources is dropped by ZTE.
AX7Kernel R7 - 03/16/2017
For both STOCK and LOS Based versions. Upstream Linux Kernel to 3.18.45 thanks to jcadduono patches.
AX7Kernel R6 - 03/03/2017
Cap for battery charging set back to 100% by deffault. BLX Settings, you want to change them, refer to this POST and to this POST. If you want to extend your battery's life think about adding the cap to a 95 or 97%
Fixed the issue where the phone won't go into deep sleep at all.
WQ_POWER_EFFICIENT MODE is enabled by default now.
AX7Kernel R5 - 03/01/2017
Cap for battery charging set to 97% by deffault. BLX Settings, you want to change them, refer to this POST and to this POST. Your battery won't charge beyond 97%.
Added options to manipulate thermal settings, now you can choose when the phone will throtle the CPU or when to start shutting down cores to prevent damage. My recommendation don't push it too high or your phone might get damaged due to the high temps. It's not set to 60 Celcius so i recommend lowering that to avoid damage.
Added WQ_POWER_EFFICIENT MODE ( you'll need EX Kernel manager to get this, it's paid app but it's totally worth it guys)
Enabled the option to 'disable' some wakelocks. Disable them on your own risk. Wakelocks that can be disabled are: Bluedroid, wlan_rx, wlan_ctrl, wlan, IPA_WS, wlan_extscan_wl_ws, qcom_rx_wakelock_ws - You'll also need EX Kernel manager to get this options.
AX7Kernel R4 - 02/24/2017
Renamed both the Folder and Kernel zip file to appoint to the version. Now we'll have 2 versions, LOS and Stock AX7Kernel, make sure to check the zip name correctly to avoid issues when cross flashing kernels. All LOS/RR/AOKP and other LOS Based kernels will have the word LOS in it.
Fixed BLX feature. It should now properly stop the charging process when the battery has reached the cap_level set by users. Charge will resume once the charge drops from the cap assigned.
AX7Kernel R3 - 02/21/2017
Added one more step of OC (pushed just a little bit further)
Added my own and really simple implementation of BLX (battery life extender) based on the work made by bedalus for the OP3 and OP3T
AX7Kernel R2.3 - 02/17/2017
Updated to latest LOS Stock Kernel
Disabled some debugging
fixes to ZEN ioScheduler - highly recommended now.
Disabled color inversion in Kcal - can't be used anyways.
Fixed USB Fast Charge - Should worl properly now.
GPU OverClock - 684MHZ max frequency now.
Adreno Boost added and enabled (should boost GPU a bit)
Updates to interactive governor (should work better when operation are in the background and screen is off - music streaming is an example.
Changes to the Sync
Changes to Random function for IO ops.
Updates to Zram.
AX7Kernel R1 - 02/13/2017:
Updated to latest LOS Stock Kernel
Added a few governors like: lionfish / despair / darkness / blu_active / wheatley / ironactive and bioshock
added a few IO Schedulers: Tripndroid / Zen / SioPlus / VR
Kcal Color Control driver
USB Fast Charge
SafetyNet Patch (Bypass bootloader unlocked check)
Dynamic Fsync control
a little Overclock
Motorola Quickwake
Extended battery charge time from 30s to 100s
Link will still redirect to R7 , androidfilehost is conducting a server maintenance. Once completed I'll upload R8 to the usual file location!
EDIT: STOCK R8 has been uploaded. Again, keep in mind this release is not fully compatible with 7.1.1 it breaks NFC, until we get an updated source it will remain as is.
Happy Flashing!
jimbo77 said:
Link will still redirect to R7 , androidfilehost is conducting a server maintenance. Once completed I'll upload R8 to the usual file location!
EDIT: STOCK R8 has been uploaded. Again, keep in mind this release is not fully compatible with 7.1.1 it breaks NFC, until we get an updated source it will remain as is.
Happy Flashing!
Click to expand...
Click to collapse
Sorry, no download file as of 4:49PDT
amphi66 said:
Sorry, no download file as of 4:49PDT
Click to expand...
Click to collapse
Yeah i'm sorry, i had to take it down. Forgot to add the exfat module and that breaks SDCard support. Will work on this tomorrow morning and will reupload then. For now R7 is there
So this is a kernel for the stock firmware?? I have b19 unfortunately so I can't test, 1 thing I surely want you to add on the b19 version if you make one, aside from all these cool features is f2fs support please make it happen.
Sebastian Fox said:
So this is a kernel for the stock firmware?? I have b19 unfortunately so I can't test, 1 thing I surely want you to add on the b19 version if you make one, aside from all these cool features is f2fs support please make it happen.
Click to expand...
Click to collapse
This works for the B19, only issue is that it breaks NFC. Other than that it works great
jimbo77 said:
This works for the B19, only issue is that it breaks NFC. Other than that it works great
Click to expand...
Click to collapse
I'll give it a try as well as freeza kernel, let's see about f2fs
Sebastian Fox said:
I'll give it a try as well as freeza kernel, let's see about f2fs
Click to expand...
Click to collapse
F2fs is not yet included. I'll see about it this weekend or next week
jimbo77 said:
F2fs is not yet included. I'll see about it this weekend or next week
Click to expand...
Click to collapse
Dang it >_> then freeza is my only solution for now
In case if you're interested about why I'm asking for f2fs, I am doing so to dualboot my stock b19 using @sbr method , unfortunately stock is ext4 and secondary can't be f2fs because it takes part in data, both either have to be f2fs or ext4
it's a bit complicated >_>
jimbo77 said:
F2fs is not yet included. I'll see about it this weekend or next week
Click to expand...
Click to collapse
Why is f2fs so important to people. Back in the day, yes, it was an improvement in speed. Now, with today's storage speeds, it's performance is negligible yet people still demand for it. Doesn't it just complaints things now?
Sent from my ZTE A2017U using Tapatalk
osmosizzz said:
Why is f2fs so important to people. Back in the day, yes, it was an improvement in speed. Now, with today's storage speeds, it's performance is negligible yet people still demand for it. Doesn't it just complaints things now?
Sent from my ZTE A2017U using Tapatalk
Click to expand...
Click to collapse
Exactly what I was thinking too.
Feeling the same. It won't hurt to have support tough. I'll try to add it but I'm afraid it could break the anykernel aprox ah since the support needs to be added Ramdisk wise and for that I'll need to move away from the current kernel approach.
I'll take a look at the lazy flasher scripts from jcadduono to check if I can patch whatever Ramdisk user has
Finished the R8 build... It was a PITA to fix find the fix for SDCARD issue (it was kinda silly what was breaking it lol). Also updated WLAN driver to CAF LA.UM.5.5.r1-03800-8x96.0 version published yesterday and fixed the damn NFC in 7.1.1 builds (this most likely break NFC in 7.0 builds). I'm sorry if you are still in 7.0 and need NFC, move on! ..
I'll push the update once android file host is out of maintenance (around 30 mins from now).
As to F2FS i have enabled the driver in the kernel and stock ramdisk supports data as F2FS so i'm assuming it should work. Although i don't use so if it doesn't i won't fix it
EDIT: LINK IS UP!
I'm not sure if I'm just blind, but I cannot find the link anywhere
EDIT: The file is there, found it in AFH over LOS version's thread. It's here: link removed
EDIT 2: Ok apparently it's in OP and I am blind...
Borias said:
I'm not sure if I'm just blind, but I cannot find the link anywhere
EDIT: The file is there, found it in AFH over LOS version's thread. It's here: link removed
EDIT 2: Ok apparently it's in OP and I am blind...
Click to expand...
Click to collapse
LOL. That's what I was gonna say haha I'm glad you find it
sorry if this is the wrong place to ask but, where can i find the stock kernel that comes with the phone?
pookachee said:
sorry if this is the wrong place to ask but, where can i find the stock kernel that comes with the phone?
Click to expand...
Click to collapse
Download the bootstack of the firmware you have and flash it.
https://forum.xda-developers.com/ax...de-updates-to-stock-files-via-t3469484/page53
So does the stock version suffer from video playback issue like freeza's kernal?

[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

Categories

Resources