[KERNEL] Nebula OOS/AOSP: (OP 6 & 6T) Latest on TG, Or Official Latest on sourceforge - OnePlus 6T ROMs, Kernels, Recoveries, & Other Dev

{
"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

Related

[KERNEL][04-02][Radon Kenzo V6.3][STABLE][CM-AOSP-MIUI]

{
"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 am not responsible for bricked devices, dead sd cards, explosions, nuclear wars, alarm applications getting failed, please read the first 3 posts (features, faq, settings) carefully before flashing this kernel to make sure everything goes well with your installation.
This kernel will focus on quality over quantity, I will add only those features which don't cause instability and really improve performance or battery life of our device. I like to test my changes properly before release and keep stability the topmost priority, I don't guarantee weekly or nightly builds, updates will be given whenever required.
Some Kernel Features-
Cpu Improvements -
Balanced, Battery and Gaming modes available for interactive governor
Mild undervolt for our cpu, reduces heat, helps battery backup
All basic governors and relaxed governors available, default is interactive
Toggles for wakeup boost, hotplug boost, touch boost
IO & Memory Improvements -
Added fiops, bfq, zen, maple, sio io schedulers
Disabled io crc check for more performance
Zram with lz4 & lz0 compression support available
NTFS, exFAT, F2FS, EXT filesystems support
Gpu/Display Improvements -
Fixed wrong gpu frequency reflected in sysfs
Optional enhanced color profile, choose while flashing
Adreno idler and adreno boost are available, off by default
Savoca's kcal color control, full control over colors
Wake gestures, dt2w, s2s and s2w for all panels
Charging/Battery Improvements -
Option to select 2000mA or 2400mA charging rates
Tuned interactive governor for better battery backup
Mild stable undervolt for both cpu and gpu
Optimizations for better load and power management
Other Improvements -
Sound control for speaker, earphones, mic etc
Option to select selinux mode while installing
Compiled with aosp 4.9.4 aarch64 toolchain
Fsync toggle available, enabled by default
Custom vibration intensity control available
Confirmed working or not working on -
Works on all lineage and aosp based nougat roms
Works on all lineage and aosp based marshmallow roms
Works on all MIUI 8+ marshmallow roms
Flashing Instructions -
Prefer flashing over your rom's stock kernel for best results
Read post #2 for some frequently asked questions
Download correct version of Radon kernel
Make backup of system, boot in twrp
Now, wipe dalvik cache and cache
Flash the kernel zip and reboot
Note - In case the kernel doesn't boot for you, restore your system and boot partition from twrp and you will not lose any data.
Stable build downloads -
Radon V6.3 Stable Builds ( Android 8.1.0, 7.1.2 & 6.0.1 )
Kernel control app -
Radon kernel control
If you like my work, consider donating -
Paypal
XDA:DevDB Information
Radon Kernel For Kenzo, Kernel for the Xiaomi Redmi Note 3
Contributors
Umang96, TheStrix, Balika011, ktomov, abhishek987
GuneetAtwal, MOVZX, franciscofranco, flar2
alex9yust, billchen1977
These are not in any specific order, please pm me If I missed anyone
Version Information
Source: Github
Status: Stable
Current Stable Version: V6.1
Created 2016-07-09
Last Updated 2017-12-10
Frequently Asked Questions -
Q ) I like this kernel, can I be a part and contribute to this project ?
It takes many hours to maintain this kernel, If you are a user then donations are appreciated. If you want to contribute to development then you can create your pull requests on my github or pm me with your patch.
Click to expand...
Click to collapse
Q ) I flashed this kernel, what next ? How and where do I configure kernel related settings ?
Recommended app is Radon kernel control, it offers very easy to use custom profile based tweaking, you may check post #3 for some tuning tips if you like to tune kernel settings yourself.
Click to expand...
Click to collapse
Q ) Read mode in miui is not working after flashing this kernel ?
Xiaomi hasn't provided the opensource code for this feature, so read mode is not going to work on custom kernels, but you can try going into display tab of radon kernel control app and make a custom profile with R,G,B(254,234,195) and saturation 40 for very similar experience to miui read mode.
Click to expand...
Click to collapse
Q ) My fingerprint doesn't work, what to do ?
Kenzo comes with two different sensors, fpc and goodix, all nougat roms have fixed support for both sensors, but if you use miui rom and you have goodix sensor then you might need to flash the patch from post #6196.
Click to expand...
Click to collapse
Q ) I flashed this kernel, but I want to return to my stock kernel, how to do that ?
If you read flashing instructions in first post, you will see that I asked you to make backup of boot and system partitions before flashing my kernel, now you can restore that backup and you will have your stock kernel back. In case you didn't take a backup, just dirty flash your rom zip without wiping data and that will restore stock kernel and modules.
Click to expand...
Click to collapse
Q ) How much battery backup does this kernel give ? Will it give me x hours of SOT ?
The battery backup depends a lot on your usage, like screen brightness, wifi, 3g/4g data. Changing your kernel or rom will not make battery backup double. If you are just wifi user, your device can give 9+ hrs screen on time. Heavy 3G, 4G, Bluetooth users shouldn't expect huge battery backup. Regarding battery consumption when display is off, I normally lose 2% battery for about 8-9 hours of standby, but if you you keep wifi and data off in night, then you should get 0-1% drain per night.
Click to expand...
Click to collapse
Kernel tuning tips -
Cpu -
Governor: Interactive for all kind of users, select battery/balanced/gaming mode while installing according to your need, balanced and gaming modes are totally smooth but battery mode might have little lags.
Users who wish to further push battery backup can try using relaxed cpu governor on small cluster, reducing max frequency of small cluster will also improve battery backup.
By default, I use these min cpu frequencies 691Mhz (small cluster) and 883Mhz(big cluster), there is also 400Mhz option but I don't recommend using that since it saves negligible battery.
Input boost and touch boost should be kept on by balanced/gaming users, battery biased users can consider turning them off.
Memory -
Adaptive lmk should be enabled by all users
Z-RAM 512MB with at least 40 swappiness
Z-RAM will increase battery consumption a little bit
Keep Z-RAM off if you need extra battery backup
IO Scheduler -
FIOPS for good performance and battery
Read ahead at least 512 KB on both internal and external
Screen -
Adjust this yourself, I don't know what you like.
Gpu -
Adreno idler - only battery biased users should keep this on.
Adreno boost - gamers or performance biased users should keep this on.
Misc -
Fsync -Enabled for more stability, disabled for more performance.
Vibration intensity - I use 60, select whatever you like here.
Note - All settings are compatible with Radon kernel control.
I am using RADON Kernel From very first Build and to be honest ,
RADON is Awesome In Performance , Super Smooth and Fully Stable Kernel.
It Rocks Redmi note 3 Development :highfive:
please bring the Over clock feature
Will try to boot it on mokee! Will update !
Edit : Doesnot boots on Mokee
Sent from my Redmi Note 3 using Tapatalk
biku123 said:
please bring the Over clock feature
Click to expand...
Click to collapse
Our phones performance is already great
No point in over clock.
Sent from my Redmi Note 3 using Tapatalk
picarito said:
Our phones performance is already great
No point in over clock.
Sent from my Redmi Note 3 using Tapatalk
Click to expand...
Click to collapse
Right, overclock is not useful unless you are using a low end or outdated device.
Umang96 said:
Right, overclock is never useful unelss you are using a low end device.
Click to expand...
Click to collapse
Are you using the stock frequency table?
Umang96 said:
Right, overclock is never useful unelss you are using a low end device.
Click to expand...
Click to collapse
Yes so please don't add over clock lol maybe any sound changes like faux sound or Franco sound? If it's possible of course.
Sent from my Redmi Note 3 using Tapatalk
Pls add Exfat support
Please consider adding color control and Intel gov and if possible Westwood TCP algorithm, since data is not stable in bsnl sim and radio of our device is also not perfect it would be useful.
Sent from my Redmi Note 3 using Tapatalk
Its the any posibility to add manual features to the camera by kernel?
Enviado desde mi Redmi Note 3 mediante Tapatalk
please add color saturation control support ,is it already there?? if not please add .Then only i will be able to use cm13 roms.:good:
@Umang96 Can u share the voltage for each frequency?
shubham tech said:
please add color saturation control support ,is it already there?? if not please add .Then only i will be able to use cm13 roms.:good:
Click to expand...
Click to collapse
That should not be the only reason to switch to cm13.cm13 is way superior than miui.
Sent from my Redmi Note 3 using Tapatalk
Umang96 said:
Cpu Big -
400 - 1747 Impulse
Cpu Small -
400 - 1401 Impulse
IO Scheduler -
BFQ on both external and internal
Read ahead 1024 on both
Click to expand...
Click to collapse
In official RR....minimum frequency is not staying in CPU small.....its coming back to 1305
Add qnovo fast charging in a future update please
sanjeev7 said:
In official RR....minimum frequency is not staying in CPU small.....its coming back to 1305
Click to expand...
Click to collapse
That is fine, it shows wrong, it's cm feature, cpu is boosted in input, it will jump from 400 to 1305 sometimes but will come back.
Was Expecting Cyanpro :3 Btw cool u rocket In Yu forums Man hatf off !
Sent from my Redmi Note 3 using Redmi Note 3 Forums

[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?

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] MALAKAS KERNEL r189 [GCC10][UPDATED❯ *9-8-13* ]

[size=+2]DISCLAIMER[/size]
Code:
[I][center]* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards, dead dogs, or cats,
* but I'm very interested in thermonuclear war, so if you point the finger
* at me for messing up your device just because of this kernel,
* I will send you to mars on a nuclear rocket. Act accordingly.
* I know this paragraph is conspiracy-related,
* so don't ask about it. Welcome...[/center][/I]
{
"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"
}
[size=+2]ABOUT[/size]
[size=+1]The Malakas Kernel or MLX, is a balance between speed & efficiency with all latest patches optimized to take full advantage of your device.
It is made off Lineage source to ensure optimal working state. The MLX kernel is one of the most patched kernels adapting work from famous developers like Sultan for example.
Work on this kernel is very serious and will continue to improve even further.
Works on both MIUI and custom roms.[/size]
[size=+2]PREREQUISITES[/size]
1. Unlocked bootloader.
2. Working TWRP/Recovery. (CLEAN FLASH IF YOU HAVE ISSUES)
[size=+2]FEATURES[/size]
Toolchain used self compiled GCC 10 snapshots
Upstreamed from android-linux-stable/msm-4.9 (+ f2fs-stable + android-4.9)
Merged latest LineageOS 16.0 updates
Merged CAF tag LA.UM.7.3.r1-07900-sdm845.0 (+ other CAF cherry picks)
Touchscreen drivers always updated to the latest versions
Touch/Input lag reduction and increased touch smoothness
Dt2w/Dt2s
Fast charging
USB Fast charge control
Sultans simple low memory killer
Kcal Display color control
Klapse v5.0 Livedisplay kernel module
Backlight expanded limits of minimum/maximum brightness control
Sound control
Fsync control
Swap
Zswap
Zram (deflate, lzo, lz4, lz4hc, zstd)
Support added for F2FS, NTFS, SDFAT, VFAT, EXFAT
MAC address randomization
Wireguard Support
300 Hz scheduler tick
GPU 180-710Mhz / optional GPU OC manually 180-820Mhz (preconfigured in MLX tweak)
Non Display OC / Display OC TIANMA panels 69hz - EBBG & JDI panels 65hz
Many more patches and improvements, check commits
TCP Congestion Algorithms :-
Code:
westwood, reno, cubic, bbr, bic, cdg, dctcp, highspeed, hybla, htcp, vegas, nv, veno, scalable, lp, yeah, illinois
CPU Governors :-
Code:
conservative, ondemand, userspace, powersave, performance, schedutil, blu_schedutil, pixutil
GPU Governors :-
Code:
compute, mem_latency, bw_hwon, msm-vidc-llc, msm-vidc-ddr, gpubw_mon, bw_vbif, msm-adreno-tz, cpufreq, userspace, powersave, performance, simple_ondemand
I/O Schedulers :-
Code:
noop, deadline, cfq, fiops, sio, bfq, anxiety, zen, maple, tripndroid
Zram compression algorithms :-
Code:
deflate, lzo, lz4, lz4hc, zstd
[size=+2]CHANGELOGS & ADDITIONAL INFO[/size]
Because I will not be updating this thread regularly you can keep an eye out on the original kernel thread from beryllium for changelogs and more updated info.
Original updated thread for additional info: here
Changelogs: here
Frequently Asked Questions: here
[size=+2]INSTRUCTIONS[/size]
1. Have a clean setup. (rom, boot.img & vendor)
2. Install magisk & reboot to rom.
3. Reboot to recovery (clean) flash the kernel & DON'T wipe dalvik/cache. (wiping cache will give bugs in MIUI and most likely give you the app open delay bug)
4. Power on the device and boot to android.
These steps only need to be repeated if you update your setup.
[size=+2]SOURCE CODE[/size]
Kernel: https://github.com/thanasxda/malakas_kernel_xiaomi_sdm845
[size=+2]DOWNLOADS[/size]
Below...
[size=+1]❯❯DOWNLOAD HERE[/size]
[size=+2]SUPPORT[/size]
This is my personal project and am working alone on this, if you appreciate my work you can help by getting me a beer.
[size=+1]❯❯Click here to buy me a beer[/size]
Make sure to hit the Thanks button if you appreciate this! :good:​
reserved
thanas said:
reserved
Click to expand...
Click to collapse
you checked this kernel? which result in geekbench and antutu?
@thanas great kernel name....hahahaha most here will never understand
mikekote666 said:
@thanas great kernel name....hahahaha most here will never understand
Click to expand...
Click to collapse
i mean seriously xD?
@thanas Had a reboot today and I have attached a log cat. I believe it was around 16:48. It may not have been kernel related but wanted to share with you in case it was. I was part of the testing guys on telegram. Hope it helps. Running havoc 2.7
Runs smooth
Flashed this kernel 10hrs ago with new xiaomi.eu 9.7.11 and had no issues so far.
Good work, keep it up and thank you for your effort.
Heres some Antutu and Geekbench scores.
mikekote666 said:
@thanas great kernel name....hahahaha most here will never understand
Click to expand...
Click to collapse
Great, now you made me Google it. [emoji38]
Sent from my Mi MIX 2S using Tapatalk
Best Kernel !!! Over 318k
thk !!! Best Kernel !!!
updated
cool
thk !!! Best Kernel !!!
haha didnt expect this warm welcome. thank u guys, constantly improving. make sure to read the faq.
i will mention the most important things though.
if facebook opens slower than half a second dont ever wipe cache because there is an app open speed bug which makes apps open even slower than stock kernel, otherwise it is extremely fast.
never wipe cache for miui as well otherwise you face even more bugs.
dont use viper4audio because it makes scores suffer. neither use LKT nor lspeed because you will get bugs.
also evaluation thermals are not anymore on by default.
read the faq despite.
hope everyone enjoys. thanks
I experience charging disconnections.
Inviato dal mio MIX 2S utilizzando Tapatalk
yet again. minor update
mikekote666 said:
@thanas great kernel name....hahahaha most here will never understand
Click to expand...
Click to collapse
A$$h0l3 kernel ..Greek word with Latin characters. Smart? No, funny? Yeah
updated
thanas said:
updated
Click to expand...
Click to collapse
Hello thanas! Thank you for your work ! Can u add support iptables in the kernel?
So far, I like newest build and with blu_schedutil I get very good bb. Thank you and keep up the good work
i install latest version over miui rom and it erease everything on my phone :/

[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