[KERNELS][8-30-18]-N4N-2DRB1 for 710,810,715,815 - Galaxy Tab S2 Android Development

N4N (Neked 4 Nougat) RB1 Kernel for 710,810,715,815​There's just nothing like good ol' stock. Everything just works. Even after 2 years+ they're still selling these Tabs. And they can still compete with newer ones.
RB1 came out after the Meltdown and Spectre scare. So this is the kernel you should be running. Either Stock or mine.
You flash this at your own risk. I'm am not responsible for anything that happens!!! There's the discaimer.
MAKE A FULL BACKUP IN TWRP!!!!!
These kernels modify your ROM. So you WILL NOT be able to FLASH/RESTORE the stock kernel only.
Synapse is a custom kernel tuner. This Kernel has UCI built in so Synapse can work. It's the only tuner I've found that will tune everything I've built into it. - Get Synapse from the Playstore​
See post #2 for Synapse info
See post #3 for other infos and updates
Install instructions:
You MUST HAVE TWRP installed to flash this!!
MAKE A FULL BACKUP IN TWRP!!!!! YOU HAVE BEEN WARNED!!!!!!!!!
Flash Kernel- it'll wipe cache, dalvic automatically,
Flash SU v2.82, https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.82-201705271822.zip Recommended and Supported
or
Magisk - Fixed now - NOT Recommended and NOT Supported See post #16
Wipe cache and dalvic when SU asks,
Reboot
Profit!!
So whats in this thing?!
V1.3
REMOVED SYNAPSE SUPPORT
Patched to 3.10.11
Wireguard updated to latest - 20180809
Finally built dt.img using UBERTC 4.9
HMP tweak
Complete rewrite to build kernel. Build scripts for each variant. Using AIK now for access to Ramdisks. All Variants using same source now. Thank you Samsung.
V1.2.1
GPU DVFS permissions re-enabled in Ramdisk - I didn't like the stutters it had with them removed
WireGuard updated v0.0.20180708
V1.2
WireGuard VPN built-in - v0.0.20180625
NTFS enabled - still can't WRITE to NTFS
Other kernel and Ramdisk tweaks
V1.1a
"Kernel is not SEANDROID Enforcing" is fixed for Magisk - Thanks to @bonuzzz
Reworked HMP so it's settings will stick now
Stumbled on DVFS for the GPU. It scales better now. The disabler scripts for DVFS will work now. FYI, I saw no difference between using and not using the script. See post #7
V1
SeLinux enforcing-Can be set PERMISSIVE in Synapse
Disabled dm-verity
Adjust HMP
Enabled KSM with tweaks
OC/UC/UV LITTLE 1.5Ghz-200Mhz-Synapse is the only tuner to Under and Overvolt, that I know of
OC/UC/UV big 2.0Ghz-500Mhz-Synapse is the only tuner to under and Overvolt, that I know of
All stock govs enabled
TCP's-Cubic is default. Reno, Westwood+ and HTCP added
CIFS
OTG
Screen Mirroring fix built in- Samsung Connect (now Smart Things)
4.9 UBERTC Toolchain
Other tweaks
Bugs and Root
As of V1.3, using Magisk is supported
SuperSU 2.82 works for everything. Magisk DOES NOT work for everything and slows the System.
So, and regretfully, I will not support Magisk or Xposed. They both slow the system and have issues for me and this kernel. Sorry, I tried. See Post #16
If you have Synapse installed , make all settings to stock and uninstall. It'll probably still give you a "System UI error". Just move on, and reboot after a couple minutes.
Source
https://github.com/engine95
As of V1.3, combined source for all 4 Variants - use/follow the 710 git
Downloads
V1.3 - NO SYNAPSE SUPPORT Use a Tuner of your choice. MTweaks (Free) or EX Kernel Manager(Paid) seem to do the best
710 - https://www.androidfilehost.com/?fid=1322778262903993950
715 - https://www.androidfilehost.com/?fid=1322778262903993953
810 - https://www.androidfilehost.com/?fid=1322778262903993951
815 - https://www.androidfilehost.com/?fid=1322778262903993952
V1.2.1
710 - https://www.androidfilehost.com/?fid=5862345805528050971
715 - https://www.androidfilehost.com/?fid=5862345805528050972
810 - https://www.androidfilehost.com/?fid=5862345805528050970
815 - https://www.androidfilehost.com/?fid=5862345805528050973
V1.2 Read Post #2 about Wireguard and Synapse
710 - https://www.androidfilehost.com/?fid=11050483647474831651
810 - https://www.androidfilehost.com/?fid=11050483647474831650
715 - https://www.androidfilehost.com/?fid=11050483647474833678
815 - https://www.androidfilehost.com/?fid=11050483647474833717
V1.1a Read Post #2 about Synapse "Worse case Scenario" and clear everything-reboot and enter Synapse (may need an extra reboot to get the voltages set right.)
710 - https://www.androidfilehost.com/?fid=13356325061477271414
810 - https://www.androidfilehost.com/?fid=13356325061477271413
V1
710 - https://www.androidfilehost.com/?fid=818222786056041596
810 - https://www.androidfilehost.com/?fid=818222786056041597

Synapse and WireGuard infos
SYNAPSE Kernel Tuner​
Well, because Synapse is built in now, here's some needed info on it:
Synapse is an awesome and custom built kernel tuner. It can do so much more than a lot of other tuners. And because we have Exynos processors, it's about the only one we can use. But it can create a lot of problems getting to work. Hence this post. :silly:
I decided to make this built in instead of a flashable add on. It's actually easier and less invasive to do it this way.
UCI, is what Synapse uses to work. It's built into the ramdisk. I've added a lot of tunables and may add more later.
Now for the fixes and problems you WILL run into:
If you have issues, make sure to check out these threads. As they will probably have better info about Synapse issues. https://forum.xda-developers.com/showthread.php?t=2736986 and https://forum.xda-developers.com/showthread.php?t=3558888
No UCI support detected These are the famous words you WILL run into.
When will this show up?
When Synapse is first installed
On reboot
When you've pushed your Tablet too far
The fixes:
On first install from the Playstore. You will need to go to Settings>Apps>Synapse>Storage. Then select "Clear Cache", THEN "Clear Data. In that order!!
You may have to backout to Settings and do it one or two more times. You want the numbers for cache and data at "0".
On reboot: This usually works unless you've messed up the settings or flash another kernel
On reboot select "Menu" and "Close all".
Open Synapse and hit "CANCEL" to have your last settings applied. (I know it's not normal but it works)
Close synapse, and reopen it to make sure of settings. (If "apply or cancel" don't show up at the top, you're good to go.)
Worst case scenario and for flashing new kernel:
You will need to go select the "MENU" button and Close all. Next go to Settings>Apps>Synapse. Select "Force stop". Select "Storage". Then select "Clear Cache", THEN "Clear Data. In that order!!
You may have to backout to Settings and do it one or two more times. You want the numbers for cache and data at "0".
If you follow the above, Synapse will work. It hasn't failed me in over 50 tests, probably more. :silly:
WireGuard VPN​Read about it here: https://www.wireguard.com/
XDA Thread here: https://forum.xda-developers.com/android/development/wireguard-rom-integration-t3711635
For install and use, read here: https://forum.xda-developers.com/android/general/guide-how-to-wireguard-android-ubuntu-t3723544
Download the "WireGuard" app from the Playstore.
I used Azirevpn. Just follow the link on the install above. Create your account. You'll get an email to confirm. Sign back in and select "WireGuard" for your config. Open WireGuard app, select the + and "create from file or archive" select the config from azire. Done
For now it's FREE so you have nothing to lose. Just be aware that WireGuard is still under development.

715-2CRB1 and 815-2CRA3 source has been requested and will get built when released.
Things to come: (probably)
WireGuard
NTFS - WRITING to. It does everything but WRITE to NTFS USB's
Possibly raise OC on big/LITTLE 2.2Ghz and 1.6Ghz- These were giving some issues on the initial release. Even though the Tab can go to 2.5 and 2.0 respectively, it's just pushing it way too much. Even 2.2 and 1.6 are too much for safety concern.
GPU control - this one is gonna be a bugger. But we'll see
And ?????

@engine95 awesome job sir but as of now my tab is confiscated by my parents due to exams...?
---------- Post added at 07:37 PM ---------- Previous post was at 07:33 PM ----------
engine95 said:
715-2CRB1 and 815-2CRA3 source has been requested and will get built when released.
Things to come: (probably)
WireGuard
I may be able to finally get NTFS to work right. We shall see
Possibly raise OC on big/LITTLE 2.2Ghz and 1.6Ghz- These were giving some issues on the initial release. Even though the Tab can go to 2.5 and 2.0 respectively, it's just pushing it way too much. Even 2.2 and 1.6 are too much for safety concern.
GPU control - this one is gonna be a bugger. But we'll see
And ?????
Click to expand...
Click to collapse
Yeah GPU control is something I personally would love to see because I have heard that the Mali T760 MP6 can go upto 700mhz but in any task whether light or heavy my tab atleast stays at 160mhz the lowest for all the time causing huge lags and TBH OC settings stay on A53 cores for longer amount of time so go ahead and overclock them to 1.9ghz talking about the the A57 cluster those CPUs heat up like insane and suck power like anything on the device so better to leave them at 2.0ghz or maybe like the Exynos 7420 2.1ghz..

Androbots said:
@engine95 awesome job sir but as of now my tab is confiscated by my parents due to exams...
---------- Post added at 07:37 PM ---------- Previous post was at 07:33 PM ----------
Yeah GPU control is something I personally would love to see because I have heard that the Mali T760 MP6 can go upto 700mhz but in any task whether light or heavy my tab atleast stays at 160mhz the lowest for all the time causing huge lags and TBH OC settings stay on A53 cores for longer amount of time so go ahead and overclock them to 1.9ghz talking about the the A57 cluster those CPUs heat up like insane and suck power like anything on the device so better to leave them at 2.0ghz or maybe like the Exynos 7420 2.1ghz..
Click to expand...
Click to collapse
Well that sucks. But these Tabs are addicting. Guess you just got an intervention.
Anyway, when you can, give this RB1 a shot. I think I6 had some tuning issues. (my mistake) It was fine until it was tuned. Mainly in the big, A57 cores. This one should run much better.
A57 tests show that they are more efficient, but can eat power like crazy if needed. I know they can easily be undervolted by at least 2 steps which will help with heat. And/or drop the A57 clock down to 1500-1600Ghz and (I may be wrong on the direction) lower the High HMP from 479 to maybe 400-450. HMP built in is 700, but Samsung has lowered it to 479 with hard numbers. Synapse will allow HMP to be controlled.
It's a big dance configuring these kernels. Between Overclocking, Undervolting, and HMP, it'll just take time to find what works for you.
This kernel, with light use is at 266Mhz for the GPU most of the time. I haven't pushed it to see how much time it'll spend at 350,420,500Mhz. I think it may go to 600 stock, but I'm sure you'd need to underclock the CPU's to get it to run there. Again, heat is the controlling factor. Screen Protectors and cases both retain heat also.
Edit Half hour playing Eternium, all stock settings, 60FPS. Tab was just warm. GPU at 266Mhz most of the time. With tweaking, I'm sure I can get it to run cooler and GPU higher if needed

Edit Half hour playing Eternium, all stock settings, 60FPS. Tab was just warm. GPU at 266Mhz most of the time. With tweaking, I'm sure I can get it to run cooler and GPU higher if needed[/QUOTE]
@engine95 that 266mhz just causes the lag I saw my tab go as far as 600mhz for 3secs which is insane.
---------- Post added at 02:05 PM ---------- Previous post was at 02:05 PM ----------
Really need GPU control

So I found that setting HMP was broken. So I have spent the day working and testing HMP and disabling GPU DVFS. See screenshots.
As you can see, all at stock settings, they run the same. But I've gotten them to use the GPU more now.
BTW, if you've used the DVFS disabler tricks or scripts in the past, they haven't worked. (At least on RB1, and I'm pretty sure I6 also) But they will now. Everything I had to do for HMP and DVFS was in the ramdisk. So there is no source for it.
Look for V1.1 tomorow

engine95 said:
So I found that setting HMP was broken. So I have spent the day working and testing HMP and disabling GPU DVFS. See screenshots.
As you can see, all at stock settings, they run the same. But I've gotten them to use the GPU more now.
BTW, if you've used the DVFS disabler tricks or scripts in the past, they haven't worked. (At least on RB1, and I'm pretty sure I6 also) But they will now. Everything I had to do for HMP and DVFS was in the ramdisk. So there is no source for it.
Look for V1.1 tomorow
Click to expand...
Click to collapse
U mean GPU control is coming soon? Also does this show up that inexpensive looking kernel not senforcing crap?
---------- Post added at 12:59 PM ---------- Previous post was at 12:58 PM ----------
Also I am getting my tab today for an hour so will test this kernel and report back..

Androbots said:
U mean GPU control is coming soon? Also does this show up that inexpensive looking kernel not senforcing crap?
---------- Post added at 12:59 PM ---------- Previous post was at 12:58 PM ----------
Also I am getting my tab today for an hour so will test this kernel and report back..
Click to expand...
Click to collapse
GPU control maybe later. It's not on my priority list and its a lot of work to get it. If we don't get an update in the next month or so, then I'll build a kernel with as much as I can. My git skills aren't the best so merging source hasn't worked well for me. I have to start from scratch with each update. And building 4-5 kernels takes a lot more time. I tried to unify them a while back but there are about 10-15 files that are specific to each Tab.
In the past, I've mainly dev'd on my S2, read, surf, but never games. So I've been trying some games as of late. With V1, everything worked smooth and clear. With V1.1 and it scaling the GPU better, ONE TIME I noticed some artifacts and elements showing up black instead of the normal. It may have been random, but I'm still thinking that controlling the GPU isn't going to help as much as you think. That's another reason I'm not in a hurry to work on GPU.
As for the Seandroid message, yes its just a nuisance. But if you root using SuperSU, as I've posted in the OP, there is no message. Magisk doesn't pack the ramdisk the same way SuperSU does. If anyone knows the fix I'll give it a whirl. Personally, I'm just not a fan of Magisk. And SuperSU has been crap since Chainfire sold it. 2.82 was the last and best SuperSU and works great on this Tab. So that's the one I suggest.
I tried to incorporate WireGuard a few days ago, but it wouldn't build. So that's gonna take some work.
NTFS still won't write to NTFS disks. I don't know what's up with it.
So, I'm just going to try and get all the bugs worked out, which I think I have, then the addons will come later. DVFS just happened to be in the area I was working on for the HMP fix.
I'll get V1.1 uploaded and posted in the next hour or so...
Edit: V1.1 in OP. HMP reworked and DVFS for the GPU can be disabled now with those scripts that change permissions. I saw no difference running without the script. But GPU scales more now either way.

@engine95
fix fo seandroid
echo -n SEANDROIDENFORCE >> boot.img

T810...A OK. After the initial right after flashing battery drain everything is great as usual. Back to great battery life and very stable. Haven't played with any clock settings or Synapse. Probably won't unless I see some need.

bonuzzz said:
@engine95
fix fo seandroid
echo -n SEANDROIDENFORCE >> boot.img
Click to expand...
Click to collapse
Really?! Can it be so simple?! A few months ago I wasted a lot of time to try to fix that. HUGE THANK YOU!!!!!:good:
Anyway, V1.1a is up for the 710 and 810 just fixed the "Kernel is not SEANDROID enforcing" when using Magisk.
715 and 815 will be worked on when I get source.

engine95 said:
Really?! Can it be so simple?! A few months ago I wasted a lot of time to try to fix that. HUGE THANK YOU!!!!!:good:
Anyway, V1.1a is up for the 710 and 810 just fixed the "Kernel is not SEANDROID enforcing" when using Magisk.
715 and 815 will be worked on when I get source.
Click to expand...
Click to collapse
You welcome!
For t715,t815 use sources from wifi model. They don't have any difference.
Just noticed, you have dedicated sources for every models. It's easier to use one sources with several defconfigs. Save your time

bonuzzz said:
You welcome!
For t715,t815 use sources from wifi model. They don't have any difference.
Just noticed, you have dedicated sources for every models. It's easier to use one sources with several defconfigs. Save your time
Click to expand...
Click to collapse
I tried that very thing. I also tried to merge source. But peoples infos keep showing wrong. Or something got broken. I think I tried with Marshmallow and haven't tried since.
Only one time has Samsung released source as 710/810. So I just build them all separate now.
I know on Nougat, I've tried to cherry-pick my own 710 commits and had them conflict with the other 3. Screen, battery, touch and others I can't remember.
Also, on my early commits I used to write them myself. Now I try to find the actual commits and cherry-pick them so that people looking have the infos that might go with them. Cherry-picking saves me a ton of time now.
Thanks for the thought though. :good:
On another note, and now I remember why I don't like Magisk. It's slower than SuperSU. I think Magisk breaks Synapse "Swap" infos. See Pic. It grant SU rights too late to work with Synapse. And I have Synapse starting very early. I guess I may have to rework Synapse again if it is indeed breaking swap info.
So what I need is for someone rooted with Magisk, to go into Synapse and look at the "Memory" page. For me it was blank and said it couldn't read the info. All the writing is red. With SuperSU, it works just like the pic.
Let me know how Magisk looks and I'll go from there. I really hoping it's just my Tab messing up. I need to try Magisk again.

engine95 said:
I tried that very thing. I also tried to merge source. But peoples infos keep showing wrong. Or something got broken. I think I tried with Marshmallow and haven't tried since.
Only one time has Samsung released source as 710/810. So I just build them all separate now.
I know on Nougat, I've tried to cherry-pick my own 710 commits and had them conflict with the other 3. Screen, battery, touch and others I can't remember.
Also, on my early commits I used to write them myself. Now I try to find the actual commits and cherry-pick them so that people looking have the infos that might go with them. Cherry-picking saves me a ton of time now.
Thanks for the thought though. :good:
On another note, and now I remember why I don't like Magisk. It's slower than SuperSU. I think Magisk breaks Synapse "Swap" infos. See Pic. It grant SU rights too late to work with Synapse. And I have Synapse starting very early. I guess I may have to rework Synapse again if it is indeed breaking swap info.
So what I need is for someone rooted with Magisk, to go into Synapse and look at the "Memory" page. For me it was blank and said it couldn't read the info. All the writing is red. With SuperSU, it works just like the pic.
Let me know how Magisk looks and I'll go from there. I really hoping it's just my Tab messing up. I need to try Magisk again.
Click to expand...
Click to collapse
Magisk messes with memory tab in synapse I can confirm that I use magisk just because of its systemless modules

First off, I need/want to apologize for the direction this kernel is going to go. In all my years (Cupcake) of building ROM's, Kernels, and Theming, I have never chosen a hard line. I've always given people what they wanted. And adjusted things to everyone else's wishes.
My work has been for me, and shared with you. So I need to go in that direction.
Magisk just isn't allowing me to do that. And it slows the system down, but not as bad as Xposed. Yes, it may be the latest and greatest, but that's not always a good thing. IF we, by some chance, get Oreo, then there's no choice.
So as of now, I will not support Magisk or Xposed on this kernel. I will still make sure the "Kernel is not SEANDROID Enforcing" is removed for those of you chosing to use Magisk. But if you have issues, I may not be able to help. Sorry....
I'm gonna be quite busy for the next month, so my work will be slower coming out. But it will still continue.

V1.2 is in OP for 710 and 810!!! See/Read changelog
WireGuard VPN is built-in, in this version - See/Read post #2 for install
Also, if you use Synapse, you probably need to clear all its data. That's in Post #2 also
I had to modify WireGuard for it to work for us. Maybe because it's built-in and not a module. So far it seems to be working fine and right with the basic tests I've done. But I've never used a VPN before now.
The nice thing, and/or bad thing about WireGuard is it's still under development. All the reviews rave about it though. And for now, It's Free!!!
I may have made mistakes with WireGuard. So if you use VPN, or have some knowledge of them, make sure to thrash and test it out.
Just a little side note, but I'm starting to notice that anything built as a module, Magisk, xposed, ntfs, etc really seem to slow this Tablet down. That's why I'm just building things in and using SuperSU.

715 2CRB1 V1.2 is in the OP!!!!!
It is untested, so I'm calling it BETA. Make a full backup before install!!!
It should boot up just fine. Really, I just need to know that it works. SuperSU is Recommended. Magisk breaks Swap info in Synapse
Let me know if it works.
815 was just being uploaded so I couldn't DL it completely. I'll get to it when I can. Maybe tonight, maybe a few days. But I will get it built.
Enjoy
Edit: @Skulldron give this one a go.
Edit #2:815 2CRA3 V1.2 is in OP-same info as above with 715 Just wanted this done and out before the holiday.

Can "Adiutor" tune this kernels or is Synapse the only tool that works?

v00d007 said:
Can "Adiutor" tune this kernels or is Synapse the only tool that works?
Click to expand...
Click to collapse
It's in the OP.
Synapse is the only tuner that will do it all. But only with SuperSU.
Magisk and/or any other Kernel tuner will work, but won't do everything I've built in.

Related

[MOD] IncrediControl - Easy GUI Voltage Control

Please read this post through thoroughly before downloading.
This app allows you to control your CPU voltages with an easy to use interface. You can increase or decrease voltages (undervolt or overvolt) for all frequencies or fine tune voltages for each individual frequency.
! HTC DEVICES, currently only single core devices are supported !
! ROOT is Required !
! Kernel that supports HAVS or SVS voltage adjustment REQUIRED !
Get it over at http://www.incredikernel.com
IncrediControl is now also available in the market:
IncrediControl
IncrediControl - Ad Free
Additionally, all donators are eligible to receive the Ad Free version. It doesn't matter how much or how little you donate or have donated. If you don't want to purchase the app from the market, you may donate using the button on this page. Please register on the site first and include your username in the comments box.
All previous donators, please register on the site if you have not done so and contact me with your username!
NOTE: The settings in the general tab are only functional in kernels that have implemented the simple sysfs interfaces for usb fast charging and audio boost. The tab will not show up if your kernel does not have these features. If you would like your kernel dev to implement the interfaces, please direct them to these two commits:
https://github.com/Chad0989/android_kernel_common/commit/a7c21fa0391c225900f93960362535179c0cecc9
https://github.com/Chad0989/android_kernel_common/commit/41dc138bae23dc7582de72a4d9895aaa8e1f8b2d
NOTE2: It is a requirement of the voltage adjustment that the kernel you are using has either the HAVS or SVS sysfs interface implemented. If it does not, it will not work.
NOTE3: Before using, please delete any boot scripts you may have in /etc/init.d that toggle any of the settings this app controls.
Get it at http://www.incredikernel.com
Restore script - use this if you went too low and find yourself in a boot loop. Flash through recovery:
http://www.incredikernel.com/?p=229
Thanx for sharing!
Keep up the good work!
IncrediControl v1.3
Major changes include:
Ad Free has now been turned into a key that removes the ads from the free version. This allows donors who have downloaded the ad free version from the site to update through the market.
HAVS voltage checking. Minimum voltages can no longer be set higher than maximum voltages.
Boot voltages are now stored in the application’s data directory. Boot settings will now persist if you update your ROM or restore the application and data from a backup.
Been having trouble with this app...
The voltages dont Stick.
Nor is there any real way to see if your adjustments are stable or not...
Also... I am getting values that are not shown in setcpu.
Maedhros said:
Been having trouble with this app...
The voltages dont Stick.
Nor is there any real way to see if your adjustments are stable or not...
Also... I am getting values that are not shown in setcpu.
Click to expand...
Click to collapse
You have to click apply to set the voltages. If you want the voltages to be applied on boot, you have to check set on boot and then click apply. The check on boot box will never be checked when you start the app. Instead there is text that tells you if you have boot settings or not. This is a failsafe so users don't habitually leave the box checked, adjust voltages too low, click apply and end up in a boot loop.
It's impossible to see if the adjustments are stable or not without running them on your phone. Every phone is different, even two phones of the same model. The only test for instability is stressing your phone at each frequency and seeing if it locks or not.
The SVS adjustment shows all frequencies the phone can support. Whether or not your phone ever uses the frequency is dependent on the governor and kernel that you are using
IncrediControl v1.4:
This is mostly a bug fix release but I have also added:
Automatic detection of the minimum and maximum voltages supported by your kernel
Unless any more bugs arise, the next release will have some new goodies to play with...
http://www.incredikernel.com or from the market.
We don't have any havs kernels for now.
Sent from HydrOG3N MOD DHD.
also supports the DeamonOC?
Paradoxxx said:
We don't have any havs kernels for now.
Sent from HydrOG3N MOD DHD.
Click to expand...
Click to collapse
Yeah, it seems only qsd8x50 processors have HAVS, others seem to all be SVS. The app supports both though.
DubelBoom said:
also supports the DeamonOC?
Click to expand...
Click to collapse
I'm unfamiliar with DeamonOC, can you clarify what it is for me?

[KERNEL] Discontinued: FusterCluck Kernel (39a) CM/AOSP/Stock

Disclaimer:
I'm not responsible for any damage caused to you or your device. If you lose your job because your phone fails to wake you up, I'll sympathize, but take no responsibility. If your phone turns into a transformer and destroys the world, don't point the finger at me. You are flashing this AT YOUR OWN RISK.
Click to expand...
Click to collapse
This should work on all CM/AOSP based roms, stock support has been re-implemented. Use of UKM for synapse to work (at all) requires init.d. Most stock based roms should have this, but a rooted OTA won't unless you added it (lots of methods, Google around a bit).
Hi Everybody. Since I haven't seen anyone making custom kernels yet for us for the 39A base, I decided I'd try pulling in some features that I use on a regular basis into the kernel source.
Most everything in this is pulled from ( in no particular order ) Faux123, Showp1984, flar2, Renderbroken, Dorimanx, Jackpotclavin, xdabbeb, Rashed, Myfluxi, franciscofranco, tsunamical and other sources. So, all credit goes to them.
I've switched over to Synapse/UKM for this, seems that most everything works properly in it. I've changed francosound slightly, so you'll need to use the modified UKM linked at the end of this post, then install synapse from the playstore.
Features:
Added Intelliactive, Intellimm, Smartmax, ElemantalX, Bacon, Imupulse, ZZmove, and Yankactive governors.
Added Intelliplug (Set as default through
Added FrancoFranciso's sound driver. (Mic, Headphone, Speaker, Camera Mic volume control)
Added 389Mhz GPU step
Enabled Extra I/O schedulers and TCP congestion methods
Enabled Kernel Same Page Merging.
All builds are permissive.
Added Bricked Hotplug
Added Bricked Thermal
Added UserSpace CPU Frequency Voltage Table
MsM Limiter from NeoBuddy89
FastCharge from Dorimanx
Added a post boot script that will provide tweaked defaults (basically what I use minus undervolting)
Exposed PVS and SPEED bin values to Synapse for informational purposes.
Misc Tweaks/Optimizations/Battery Saving Optimizations
Screen turn on bug fixed courtesy of JackPotClavin
Stock Builds should work correctly now. (bluetooth and back led issues should be corrected)
F2FS support
Known Issues:
None
I'll work on things as I get time, but I'm not promising anything as this is simply a kernel that I'm making for the features I typically use. A lot of code has changed in the new kernel source making it hard to import features, so it's slow going. Also, sorry for the kernel name, I didn't have anything creative at the time.
Source: Github
CONVERTING DATA TO F2FS WILL WIPE YOUR SDCARD DATA AS WELL. Ensure that you have a backup of everything on your computer before doing so as this is unrecoverable. For R3, with F2FS you'll want this repacked TWRP. It has this kernel packed into it, with better f2fs support libraries (thanks XDABBEB). Also, be aware that encryption is not currently enabled with F2FS partitions in the way that I have it configured.
Downloads:
R3 - Fixed Bluetooth and PowerManagerService.Display Wakelock
CM-R3-B3
Stock-R3-B3
*Caution with R3, I've been running F2FS on the CM build for a couple days now with now issues. Stock booted and mounted for me, but I couldn't find a tester to evaluate it.*
CM-R3-Build1
Stock-R3-Build1
UKM has also been updated (link below). No new functionality, just cleaned up some of the stuff that didn't apply to our phone.
Old Builds:
CM-R2-Build3
Stock-R2-Build3
Modified UKM: 3.8.1-Mod6-Fustercluck (Source) - Apb_Axel's Original Thread Huge Thanks to him for his work making UKM.
Remember to hit the "Thanks" if you're enjoying this kernel.
For anyone who wants to build from this, I've included the toolchain , ramdisk, and a build script in the github repo. As long you have a build environment setup, you should get a flashable zip in the zips folder just from running the included build.sh script.
*edit*
I've removed the toolchain and all git references to it. It was causing the repo to be far larger than it needed to be. It's easy enough to find a toolchain (I've been using sabermod) and place it in the directory the build script expects. The one I use is Sabermod 5.1
Edit:
Development will be halted as my g2 digitizer is failing and I'm likely to upgrade to a nexus 6.
This kernel is SORELY needed. Constantly torn between being on 5.1 vs. 5.0.2 or JB vs. KK aboot, etc. And now I finally feel like I can have it all. Thank you! Working great so far on Euphoria ROM.
Only suggestion would be making the kernel default to be selinux permissive, especially with Google pulling an Apple and banning many of the selinux modifying apps from the playstore.
Thanks again!
bbender716 said:
This kernel is SORELY needed. Constantly torn between being on 5.1 vs. 5.0.2 or JB vs. KK aboot, etc. And now I finally feel like I can have it all. Thank you! Working great so far on Euphoria ROM.
Only suggestion would be making the kernel default to be selinux permissive, especially with Google pulling an Apple and banning many of the selinux modifying apps from the playstore.
Thanks again!
Click to expand...
Click to collapse
Yeah, I'll put up a build that's permissive. But d-h.st is being a pain right now and not actually letting me upload.
I was going to write up a post about the dangers of permissive kernels, then saw avc denials for an init.d script, netmgrd, sensors.qcom, and busybox in my dmesg (of course I was going to check before I posted)...
Just remember though enforcing stops things from running out of context. It's a security features and that's why google's removing the apps that let you change it. Permissive lets everything do whatever it wants and just logs that it should have been denied (dmesg | grep "avc"). So essentially, it's like installing an antivirus on your computer then disabling it but letting the system tray icon give you a warm fuzzy. Antivirus is a bad analog because it's really more like user policies, but you get the point.
*edit*
for now, I'll just attach the permissive build to this post. I'll need to wait till d-h.st gets it together. Maybe, I'll look for a better file server.
Does this have Bacon or smartass? If not is it a possibility in the future?
Yeah, I'll work on grabbing them. I'll need to find a good version of bacon from somewhere though that hasn't been too tweaked/modified.
Also, I'm moving to androidfilehost. for hosting. d-h.st just wasn't working out. I'd like to find somewhere that gives ftp access so that I could just upload builds at the end of my build script, but I guess that's not a huge deal.
Anyway, the new folder will be: https://www.androidfilehost.com/?w=files&flid=29865
The build numbers are just there to help me keep track of what file I'm on and need to flash for testing, don't let them get you confused if there are missing numbers in that folder... they just weren't worth uploading, or the build failed.
Also, how is the fauxsound stuff working out for everyone? I feel like it's pickup up the register values wrong or something... I'm not quite sure yet. But the sound seems too quiet on the low-end, but at least boosting the high-end works.
Just gonna throw this out there since you arm like a hands on dev, what are your personal settings? Default? I'm super excited for this kernel but after using dori for a while, the feature creep became somewhat mind boggling.
BOY_ said:
Just gonna throw this out there since you arm like a hands on dev, what are your personal settings? Default? I'm super excited for this kernel but after using dori for a while, the feature creep became somewhat mind boggling.
Click to expand...
Click to collapse
I'm not really comfortable being called a dev, I have some understanding of what's going on but the real devs are the guys that I gave credit to in the OP. Really, I'm just pulling in their work and making little changes here and there to make it work.
Personally, I run intelliactive with intelliplug and westwood with zen set to 1024 (why I added those) but I don't tweak the settings. I've never really seen a reason to, the governors are pretty smart. Of course, if you know what you're doing you can always fine tune them some based on your personal use types.
As far as feature creep... Read up on the different things. Figure out what works for you, ignore the rest. Really, it's just there because ya know... different strokes for different folks.
That's exactly the answer I was looking for. Thank you!
New build (30) up, sorry for the number jump... took a good few build tries getting the governors to play nice.
This added Smartmax, ZZmove, and Yankactive.
Should also fix GPU freq reporting. Previously, it wasn't reading correctly.
*edit*
Seems some of these new governors don't play so nice under use, at least not for me. They govern, but it seems like my device is locking up or not turning the screen back on with them. Looks like they need a little polishing.
I am using Intelliactive as well, on Euphoria v1.1, which sticks, but Intelliplug does not.
Also, only Smartmax worked for me with the new governors, but the others rebooted my phone almost instantaneously.
~ Sent from my VS980 ~
360Razir said:
I am using Intelliactive as well, on Euphoria v1.1, which sticks, but Intelliplug does not.
Also, only Smartmax worked for me with the new governors, but the others rebooted my phone almost instantaneously.
~ Sent from my VS980 ~
Click to expand...
Click to collapse
Thanks for the feedback.
Yeah, I ended up just removing zzmove and yankactive for now but added bacon and impulse. I'm not sure what exactly is going on with those two, but they kept trying to switch the devfreq governor to one that I shouldn't have included to begin with, the calls it used I don't think are present anymore. Which could very well be the reason they were freezing.
The intelliplug is a little weird too depending on which tuning app you use. Synapse lets it stick, but never shows that mpdecision turned off. Kernel auditor shows both on, but trickstermod shows that it correctly. ...kinda weird and I don't trust the apps to be honest. The sysfs values for intelliplug is toggling and the mpdecision binary stops running (at least with trickster) so those apps could be doing any number of things wrong.
Thanks for continuing to tinker and your analysis. I just did a reboot and checked Kernel Adiutor and even the governor is not sticking. I will try Trickster, as I am used to that app, but agree with you, each can be doing something wonky with your kernel.
~ Sent from my VS980 ~
Phone feels faster after this kernel, loving that. As for synapse, it tells me no UCI support and that's the end of that. I found kernel adiutor and it seems to be alright. The headphone amp doesn't seem to want to change which is annoying since I really want that. I think I'm just gonna clean flash the next euphoria build. Congrats on the first kernel for 39a roms.
joedajoester said:
Phone feels faster after this kernel, loving that. As for synapse, it tells me no UCI support and that's the end of that. I found kernel adiutor and it seems to be alright. The headphone amp doesn't seem to want to change which is annoying since I really want that. I think I'm just gonna clean flash the next euphoria build. Congrats on the first kernel for 39a roms.
Click to expand...
Click to collapse
Yeah, the headphone poweramp is buggy. I still think it's an issue because I pulled Shamu's (Nexus 6) fauxsound. But you still get the volume boost with the headphone volume choice. For synapse to work at all on most kernels now you need to download and flash teh UKM script.
But yeah, there are still things that are buggy. Which is why I'm leaving this labeled as an alpha for awhile.
I've been working on governors most of the day, I'll reply here when I get an update posted.
Yeah, FauxSound thru the speakers just cuts in and out, mostly out.
Xdabbeb's 982.5 on ART for VZW LG G2
jesssiii said:
Yeah, FauxSound thru the speakers just cuts in and out, mostly out.
Xdabbeb's 982.5 on ART for VZW LG G2
Click to expand...
Click to collapse
That's odd, I listened to my phone through the speakers for a good few hours yesterday moving my inlaws. Didn't notice any cutting in and out.
Can you tell me what values you have in: /sys/kernel/sound_countrol_3/gpl_speaker_gain ?
I have "2 2" at the moment, but I have my speakers down... typically I've been holding them at "5 5"
Also, are you using anything like viper? Are you using this on a CM12.1 based 39a rom?
*edit*
Also, New build up. https://www.androidfilehost.com/?fid=96039337900114170
Removed a few of the unused Devfreq governors (for gpu).
Added ElementalX, Bacon, and Impulse Governors. Removed ZZmove and Yankactive
Changed some compile flags, might give better performance.
Misc tweaks.
Another Build: https://www.androidfilehost.com/?fid=96039337900114287
Added in Bricked Hotplug and Bricked Thermal.
I may be a bit slower on adding things and building the next couple days... weekends over.
Yoinx said:
Another Build: https://www.androidfilehost.com/?fid=96039337900114287
Added in Bricked Hotplug and Bricked Thermal.
I may be a bit slower on adding things and building the next couple days... weekends over.
Click to expand...
Click to collapse
You've been busy! So what is your setup now?
~ Sent from my VS980 ~
360Razir said:
You've been busy! So what is your setup now?
~ Sent from my VS980 ~
Click to expand...
Click to collapse
No different, I just prefer bricked thermal over the normal one. I usually set the temp limits 2 or 3 below the defaults.
I'm just trying to get the features added so that people have options. I sent faux a message, I don't really expect a reply because I'm sure he's pretty busy.... But figure is give it a shot to see if he can help with the faux sound issues.
Once that's worked out, everything should be fairly stable. Then I can try to figure out what's up with some of the tuner apps not recognizing things correctly.

CPU load with custom CM13 kernels

Guys.. With every Android since the 2.x, you could activate the "Developers Options" and activate an option called "Show CPU usage".
"The numbers show the average load of the CPU in different time intervals. From left to right: last minute/last five minutes/last fifteen minutes"
My doubt: When I install any CM13 ROM (now I'm with Exodus) on my S5 (G900M), the load, after some minutes, are always near 10. Now I'm staring at it, with many apps installed (whatsapp, facebook, uber, maps, messenger, firefox, mx player, es file explorer, foursquare, traceroute, wifi analyzer, gmail, imo, os monitor, tinder, fing, poweramp, mindroid, remote desktop, 99, youtube, andsmb, diskusage, soundhound, photos, dropbox, goseek, instagram, juicessh, google now, picsplay, speedtest, skype, swiftkey, stabilitytest... just to name some...) and it's 11.32 / 14.37 / 23.11
Now the problem: whenever I install Boeffla Kernel or CrazyKernel, the load is ALWAYS higher.. always nearing 20. With default options, or trying to tweak the cpu options in both kernels.. and the bigger problem is that I SENSE that. The phone seems to RUNS SLOWER.
ps: If you LOCK your device (or let it lock by the timeout), this "load" value will raise because the cpu will also run slower.. it doesn't mean it's working more, just that more work is queued to the cpu, as it doesn't NEED to work on it (because it's locked/screen turned off, etc)
Hi,
I guess everyone will have that. So the poll is quite useless.
The reason for it, as I tracked down:
Two governors (intellimm and slim) are adding overhead to the system, even when they are not used.
Why? I do not know, as I am not the developer of these governors.
But for a test, I removed them from beta11 and compiled it as a beta11test1 version, attached here.
Let me know if removal of these governors lowers the cpu utilization for you down to stock levels almost.
Andi
Lord Boeffla said:
Hi,
The reason for it, as I tracked down:
Two governors (intellimm and slim) are adding overhead to the system, even when they are not used.
Why? I do not know, as I am not the developer of these governors.
But for a test, I removed them from beta11 and compiled it as a beta11test1 version, attached here.
Let me know if removal of these governors lowers the cpu utilization for you down to stock levels almost.
Andi
Click to expand...
Click to collapse
Wow that was fast. I'm testing right now and yes, the CPU load is *finally* down to ~11 like it were with vanilla CM13 kernel (which I think is what Exodus uses).
Still I get a little lag here and there mostly when "loading" stuff (like when clicking in a group chat on whatsapp, which needs to open a huge .db to display the history.. I think).....
But nice work.. I wonder what more could be optimized.. it's strange to a vanilla kernel be snappier than a custom .. given the experience you have..
Thanks
fbs said:
Wow that was fast. I'm testing right now and yes, the CPU load is *finally* down to ~11 like it were with vanilla CM13 kernel (which I think is what Exodus uses).
Still I get a little lag here and there mostly when "loading" stuff (like when clicking in a group chat on whatsapp, which needs to open a huge .db to display the history.. I think).....
But nice work.. I wonder what more could be optimized.. it's strange to a vanilla kernel be snappier than a custom .. given the experience you have..
Thanks
Click to expand...
Click to collapse
I am not sure vanilla stock kernel is more snappy. I feel it is the other way round personally. But this is about expectations and perception. Also it is about what is important for one. A custom kernel gives you many other goodies that might of course compromise in other areas. Nothing is for free.
And I personally prefer some other features over pure performance.
But well, that's it. I will not do more, having in mind the s5 kernel is only my #5 kernel in terms of priority. Sorry.
Andi
Lord Boeffla said:
I am not sure vanilla stock kernel is more snappy. I feel it is the other way round personally. But this is about expectations and perception. Also it is about what is important for one. A custom kernel gives you many other goodies that might of course compromise in other areas. Nothing is for free.
And I personally prefer some other features over pure performance.
But well, that's it. I will not do more, having in mind the s5 kernel is only my #5 kernel in terms of priority. Sorry.
Andi
Click to expand...
Click to collapse
Now I'm on boeffla-config trying to tune "interactive" governor and it says it's not tunable. it was before this test version. Maybe the removal of that other governors screwed up boeffla-config listing of whats tunable or not.. ? check this out too please..
fbs said:
Now I'm on boeffla-config trying to tune "interactive" governor and it says it's not tunable. it was before this test version. Maybe the removal of that other governors screwed up boeffla-config listing of whats tunable or not.. ? check this out too please..
Click to expand...
Click to collapse
Well, not such an issue here. I can enter tunable mode.
Reset your app via the apps maintenance menu.
But you know, you are on a completely unsupported test kernel. Just to say that again.
Andi
Lord Boeffla said:
Well, not such an issue here. I can enter tunable mode.
Reset your app via the apps maintenance menu.
But you know, you are on a completely unsupported test kernel. Just to say that again.
Andi
Click to expand...
Click to collapse
Right, but given the test was a success, you'll remove these governors for good, right?
fbs said:
Right, but given the test was a success, you'll remove these governors for good, right?
Click to expand...
Click to collapse
Yes, already announced everywhere (here on xda, as well as on Twitter and on my site).
Andi

[KERNEL][OPX][LineageOS] FrancoKernel - r11 - 12th Dec

Hi all.
Compatibility:
Builds starting with r5 compatible with Android Nougat 7.1.1 LineageOS or roms built from LineageOS sources.
Download:
From my webserver choose the Kernel with the most recent version number. Older releases for older Android versions are in the parent directory:
https://kernels.franco-lnx.net/OnePlusX/7.1.1/anyKernel/
or from my Updater app. It's just easier and more convenient:
https://play.google.com/store/apps/details?id=com.franco.kernel
Installation:
Flash the zip in your recovery
or
Auto-flash from Franco Kernel Updater app
Features:
1 - Legendary battery life
2 - Flash & forget
3 - Typical interfaces like display adjustments, sound control, vibration control, and all that boring stuff
4 - Idle power consumption reduced to the absolute minimum (if you have wakelocks from 3rd party apps you're obviously on your own)
5 - Support for FKUpdater's Performance Profiles
6 - Magical support, I'm here every day, checking posts almost hourly, ready to help anytime (well, unless you fail to read the OP, which contains most info you need)
7 - Seemless integration with my app FKUpdater
8 - No crap placebo patches, or "magical" optimizations
9 - Probably more, check my github for all the details - the code speaks for itself
Changelog:
https://kernels.franco-lnx.net/OnePlusX/7.1.1/appfiles/changelog.xml
Source:
https://github.com/franciscofranco/onyx
Follow me on the interwebs
Google+
Twitter
Google+ FK community
https://plus.google.com/u/0/communities/117966512071636110546
Franco Kernel: Manager & Updater demo
Disclaimer to moderators:
Slight OT is fine, but when users decide to act stupid they should be dealt with with the appropriate means - its really annoying for me when OT turns crazy. Please put the warning/ban hammer anytime any of you think there's lack of respect and/or too much unwanted OT crap - but if it doesn't meet this criteria let the OT posts alone. Thank you.
Cheers!
Good to see you around here!
Thought I would add more to this and make it useful for a few users.
The reason behind why Mpdecision is disabled by default is due to the fact that it is highly inefficient in the sense that hotplugging on Linux, put simply, sucks. Why? The hotplug acts as a front-end to the scheduler to provide a means of plugging and unplugging cores in exchange for a high amount of latency. This means that even though a core may be plugged, there is a delay of several milliseconds before this is actually processed causing microstutters that are hard to notice, but do disrupt performance. The same can be said for the thermal driver and how it Aries frequencies.
Now that that is over with, I'd just like to thank Franco. My device has never been faster. Even with an undercooked, it is still performing better than ever. Especially love the ZRAM tweaks, and how you properly configured CPU boost. Some people make it way too aggressive... It's the little things, and the huge steps forward in the source code that make your work so great! Best of luck
My apps have been updated to support the One Plus X too, both free and paid apps.
Damn legendery dev with his awesome kernel is here. Thank you!
Wish you're kernel for CM13/14 [emoji1]
Flash it, all fine, better later than never,
Didn't work for me coming from LOS (17/03/02 build) with Boeffla kernel. Wiped cache and dalvik, flashed fk r1 and bootloop. Phone kept returning to the boot splash screen and then straight to recovery. Looking forward to solving. Thanks for now.
Sorry, I was clearly not fully awake when I posted this. I read OxygenOS and interpreted as LineageOS.
Still, I hope someday we can run FK kernel on LOS.
Thanks anyways.
Omg .....Dream come true....Thank you franco
Thanks for the kernel, Franco!
It's a shame that it only supports OOS.
FYI I installed it on Sultan's CM13 and everything works fine except dt2w. The switch in settings does nothing and there is no switch in Kernel Adiutor. I hope that your kernel will be compatible with CM/AOSP based roms in the future.
Edit: Wifi is also not working.
franciscofranco said:
Hi all.
Compatibility:
Builds starting with r1 compatible with OxygenOS or roms built from OxygenOS sources.
Download:
From my webserver:
https://kernels.franco-lnx.net/OnePlusX/6.0.1/anyKernel/
or from my free Updater app:
https://play.google.com/store/apps/details?id=com.franco.kernel.free
Installation:
Flash the zip in your recovery
or
Auto-flash from Franco Kernel Updater Free app
Features:
1 - Legendary battery life
2 - Flash & forget
3 - Typical interfaces like display adjustments, sound control, vibration control, and all that boring stuff
4 - Idle power consumption reduced to the absolute minimum (if you have wakelocks from 3rd party apps you're obviously on your own)
5 - Support for FKUpdater's Performance Profiles
6 - Magical support, I'm here every day, checking posts almost hourly, ready to help anytime (well, unless you fail to read the OP, which contains most info you need)
7 - Seemless integration with my app FKUpdater
8 - No bull**** placebo patches, or "magical" optimizations
9 - Probably more, check my github for all the details - the code speaks for itself
Changelog:
https://kernels.franco-lnx.net/OnePlusX/6.0.1/appfiles/changelog.xml
Source:
https://github.com/franciscofranco/onyx
Google+ FK community
https://plus.google.com/u/0/communities/117966512071636110546
Franco Kernel: Manager & Updater demo
Disclaimer to moderators:
Slight OT is fine, but when users decide to act stupid they should be dealt with with the appropriate means - its really annoying for me when OT turns crazy. Please put the warning/ban hammer anytime any of you think there's lack of respect and/or too much unwanted OT crap - but if it doesn't meet this criteria let the OT posts alone. Thank you.
Cheers!
Click to expand...
Click to collapse
shatteringlass said:
Didn't work for me coming from LOS (17/03/02 build) with Boeffla kernel. Wiped cache and dalvik, flashed fk r1 and bootloop. Phone kept returning to the boot splash screen and then straight to recovery. Looking forward to solving. Thanks for now.
Click to expand...
Click to collapse
Read OP's first post again...
Facing heating issue...
Everything else is buttery smooth.
Hello bro i need permission regarding your kernel on one plus x i have ported a one plus x rom and i wanna use it one plus one the kernel is working fine in one plus one( I skipped the device checking and made it work)
would be great if you allow me to use it
Thanks
Why are always 4 cores online?
Edit: Got answered on Franco's twitter
shatteringlass said:
Didn't work for me coming from LOS (17/03/02 build) with Boeffla kernel. Wiped cache and dalvik, flashed fk r1 and bootloop. Phone kept returning to the boot splash screen and then straight to recovery. Looking forward to solving. Thanks for now.
Click to expand...
Click to collapse
Not compatible with LineageOS yet. It's written in the OP.
Kolio_xda said:
Thanks for the kernel, Franco!
It's a shame that it only supports OOS.
FYI I installed it on Sultan's CM13 and everything works fine except dt2w. The switch in settings does nothing and there is no switch in Kernel Adiutor. I hope that your kernel will be compatible with CM/AOSP based roms in the future.
Edit: Wifi is also not working.
Click to expand...
Click to collapse
It won't work on Sultan's, he uses a very specific Kernel with specific changes that only work on his specific rom build.
W!ld said:
Facing heating issue...
Everything else is buttery smooth.
Click to expand...
Click to collapse
There's no heating issue. The device throttles just fine when under stress. I run several CPU stability tests before I push a new Kernel...
Dhairya said:
Hello bro i need permission regarding your kernel on one plus x i have ported a one plus x rom and i wanna use it one plus one the kernel is working fine in one plus one( I skipped the device checking and made it work)
would be great if you allow me to use it
Thanks
Click to expand...
Click to collapse
I don't understand what you're asking. Use what where?
@franciscofranco Thanks for this!
Waiting for LineageOS 14 (and all based ROMs) support. Most people don't really use OxygenOS since it's slow and buggy
Calvin2394 said:
@franciscofranco Thanks for this!
Waiting for LineageOS 14 (and all based ROMs) support. Most people don't really use OxygenOS since it's slow and buggy
Click to expand...
Click to collapse
It's not slow with FK, at all. I made sure of that. There was a specially bad issue that I reported to OP 1 year ago, which makes the device have a gigantic stack of uninterruptible threads after a while on screen off. My record was a load average close to 200, 200, 200 which is insane and destroyed the device's performance. That's fixed on FK. Also all cores are online at all times, there's no need to shut down 2 cores, and mpdecision is disabled so that it doesn't mess with the devices performance.
thanks finally the great franco kernel is here damn really appreciate your work
Something really worth for the OnePlus X after a long time. I have been waiting for this day. Thank you.
franciscofranco said:
It's not slow with FK, at all. I made sure of that. There was a specially bad issue that I reported to OP 1 year ago, which makes the device have a gigantic stack of uninterruptible threads after a while on screen off. My record was a load average close to 200, 200, 200 which is insane and destroyed the device's performance. That's fixed on FK. Also all cores are online at all times, there's no need to shut down 2 cores, and mpdecision is disabled so that it doesn't mess with the devices performance.
Click to expand...
Click to collapse
yeah really i underclocked the cpu to 1957 ghz and input boost enabled to 652mhz, the phone literally flies on oxygen os. Also the antutu score is 55222,literally made my day thanks a lot
One wierd thing though, kernel auditor shows my battery capacity to 3000mah, is it true?? or is it after the kernel, anyways its buttery smooth.. magical
Androidoo said:
yeah really i underclocked the cpu to 1957 ghz and input boost enabled to 652mhz, the phone literally flies on oxygen os. Also the antutu score is 55222,literally made my day thanks a lot
One wierd thing though, kernel auditor shows my battery capacity to 3000mah, is it true?? or is it after the kernel, anyways its buttery smooth.. magical
Click to expand...
Click to collapse
Battery size is 2525mAh.
Hi, I flashed your kernal yesterday, all great and the device is buttery smooth but just one thing I noted. When ever the phone goes into to deep sleep the device doesn't wake up on pressing the power button. Have to restart the phone by long pressing the power button. And I haven't changed anything using the kernal adiutor app, just using your default settings.
Can you kindly guide me if something is wrong from my side. May be if you want a log I'll try to pull out a log tonight.
Thanks alot for your work.

[KERNEL][FORK]Radioactive Kernel V2.2.5 [2021.07.28][OOS/CUSTOM ROMS][UNIFIED OP8/OP8Pro/OP8T] 295-920Mhz GPU + WL Blocked + Adreno Boost

str8str said:
Can I get a link to try this? Tia
Click to expand...
Click to collapse
Updated 7/31/2021 rebased on Acuicultor's v2.2.5 rebase (OOS) and rebase_custom (custom ROMs).
[NOTE: Bug reported - with a Magisk Module I created to fix it. For some strange reason (code looks fine), some systems are setting the default GPU frequency to 920mhz and default power level to 0 (max). I have posted a small Magisk Module that waits 5 seconds then corrects these values (295mhz default and power level 8). It's on the GitHub release page - MOD-GPU-Set-Min-Freq.zip. Just install with Magisk Manager as a module / install from storage after downloading.]
This is a tweaked version of RadioActive kernel by acuicultor modded for higher performance and lower idle drain. All source commits and releases are on my GitHub fork:
https://github.com/mrslezak/Radioactive_kernel_oneplus8/releases/tag/v2.2.5-MOD
PLEASE read the Readme as well as the disclaimer. Whenever you flash a custom kernel, you do so at your own risk. I recently rebased on the dev's work (GPU_OC OOS branch, never released) and set the wakelock blocks up myself (lower idle drain, tested over a week with no loss in functionality), dropped the base GPU frequency to 295mhz and raised the top ones (800/920mhz) acuicultor you're an awesome dev, great to have you around! All credits should go to him other than my tweaks.
I also merged all the same changes into the Custom ROM branch which didn't have GPUOC or AdrenoBoost - several people are using it now but it's marked as a BETA since I am on OOS (latest Global) and can't test it myself. NOTE: many people on the TG channel I posted to have tried it and have had no issues on Op8, Op8 Pro, and Op8T.
Note if you are one of the rare people who see artifacts in games or benches, the easiest fix is to go into your kernel manager and set the max GPU frequency to 800mhz and apply on boot. Not all 865 Adreno GPUs are created equal. I haven't seen one that couldn't handle 900mhz to date, but enough people have had no issues at 920mhz so that's where I put it.
Be sure to flash Magisk before installing, then use EX Kernel Manager or FK Kernel Manager to Flash the kernel zip. It has all the same optimizations of RadioActive kernel, just modded for really nice performance and low battery drain. Adreno Boost is set to low on default which makes it react faster as the GPU scales. If you already have Magisk installed, there is no reason to reinstall it - the AnyKernel 3 zip installer will use what's installed already.
I put one out there you can just flash from: fastboot flash boot 4.19.110.RadioActive-WL-295_UC-920-GPU-2.2.5.img (OOS only) as it saved my a$$ a couple times when flashing or trying to apply an incremental update when rooted (no success, although I posted the incremental update on TG, the payload just won't extract properly to update using fastbootd scripts)... Maybe I'll post it here on XDA and see if anyone can extract the latest Op8T update.
Also someone sent me a PM about using KonaBess app to change frequencies even more, or change regulators, or change the DDR clock speeds. Yes, it works. Note you probably should only play with that if you have a fastboot image available in case it doesn't boot! I did just upload one for OOS to the repo as I mentioned above. Be warned, you're on your own there.
Hope you all enjoy!
- MattOfTheDead / Red Magic 5G MOD kernel (Q) / Xiaomi Mi9 / Mi9T Pro MOD kernels (Pie/Q) / next in line is probably a 2022 device - 888s didn't make the cut
mslezak said:
Join the Telegram group called OnePlus 8 | 8T Series and you'll find that and my modded versions there as well. Just search for 920 the latest one will pop right up. Actually about to rebase on the dev's excellent work and set the wakelock blocks up myself, dropping the base frequency and raising the top one. acuicultor you're an awesome dev, great to have you aboard! - MattOfTheDead / Red Magic 5G MOD kernel (Q) / Xiaomi Mi9 / Mi9T Pro MOD kernels (Pie/Q) / next in line is probably a Realme GT.
Click to expand...
Click to collapse
Kernel for custom A11 or OOS only?
jamescable said:
Kernel for custom A11 or OOS only?
Click to expand...
Click to collapse
I built both just moved some commits over from the GPU_OC branch and added my own to custom. I have no way to test it but several others did already. All I've heard is great feedback and running faster than OOS. Of course it depends on the ROM.
mslezak said:
I just built the OOS one... custom I don't think there's a GPU_OC branch to rebase on. I deleted my other repo with changes and just switched to the dev's work since it was nicely done. I'm always running OOS I don't really care to run a custom ROM. Although I imagine it would be pretty easy to add his commits from the OC branch to the custom one, you never know what issues you'll encounter when doing so... And I don't really feel like building a kernel I won't use. I already converted it over from a carrier locked phone. Happy enough it runs on Global OOS ROM. I've run a few custom ROMs before like Lineage, Evolution-X, I always end up back on OOS. Just like having a fast phone with no lag where I can open any number of apps and get work done quickly without waiting for anything to load.
Click to expand...
Click to collapse
Thanks for this man. Will be looking for your kernel edit on telegram.
jamescable said:
Custom kernel for A11 or OOS only?
Click to expand...
Click to collapse
mslezak said:
I just built the OOS one... custom I don't think there's a GPU_OC branch to rebase on. I deleted my other repo with changes and just switched to the dev's work since it was nicely done. I'm always running OOS I don't really care to run a custom ROM. Although I imagine it would be pretty easy to add his commits from the OC branch to the custom one, you never know what issues you'll encounter when doing so... And I don't really feel like building a kernel I won't use. I already converted it over from a carrier locked phone. Happy enough it runs on Global OOS ROM. I've run a few custom ROMs before like Lineage, Evolution-X, I always end up back on OOS. Just like having a fast phone with no lag where I can open any number of apps and get work done quickly without waiting for anything to load.
Click to expand...
Click to collapse
I mainly wanted the wakeloxk blockers, and other battery saver stuff lol. Don't care about OC
jamescable said:
I mainly wanted the wakeloxk blockers, and other battery saver stuff lol. Don't care about OC
Click to expand...
Click to collapse
You can also underclock.
str8str said:
Can I get a link to try this? Tia
Click to expand...
Click to collapse
Release Radioactive Kernel V2.1.4 OOS Op8/Pro/8T Modded (+Custom BETA) · mrslezak/Radioactive_kernel_oneplus8
GPU underclocked to 295 base frequency, overclocked to 670/800/920mhz. Default Boeffla Wakelocks blocked to reduce idle battery drain. Default Adreno Boost set to low. A personal build based on ...
github.com
Just anyone who uses the modded kernels please read the disclaimer first. Readme on GitHub and releases page.
Modded Custom BETA is out with the same features of the OOS kernel in the post above. 295/800/920Mhz GPU, Adreno Boost with Low default, default Wakelock block list. Go to the same location to download if you'd like to try it out. And please, please read the DISCLAIMER there. Whenever you flash a kernel, you do so at your own risk. I am liable for nothing. If you want to see what I changed, switch to the custom branch. So far I have 5 people that have said "it's awesome" on Telegram, no issues reported as of yet.
Release Radioactive Kernel V2.1.4 OOS Op8/Pro/8T Modded (+Custom BETA) · mrslezak/Radioactive_kernel_oneplus8
GPU underclocked to 295 base frequency, overclocked to 670/800/920mhz. Default Boeffla Wakelocks blocked to reduce idle battery drain. Default Adreno Boost set to low. A personal build based on ...
github.com
mslezak said:
Modded Custom BETA is out with the same features of the OOS kernel in the post above. 295/800/920Mhz GPU, Adreno Boost with Low default, default Wakelock block list. Go to the same location to download if you'd like to try it out. And please, please read the DISCLAIMER there. Whenever you flash a kernel, you do so at your own risk. I am liable for nothing. If you want to see what I changed, switch to the custom branch.
Release Radioactive Kernel V2.1.4 OOS Op8/Pro/8T Modded (+Custom BETA) · mrslezak/Radioactive_kernel_oneplus8
GPU underclocked to 295 base frequency, overclocked to 670/800/920mhz. Default Boeffla Wakelocks blocked to reduce idle battery drain. Default Adreno Boost set to low. A personal build based on ...
github.com
Click to expand...
Click to collapse
RadioActive-WL-295-920GPU-custom-2.1.4-BETA.zip is the file for custom ROMs BTW if you don't read the notes (which you should). As I mentioned to the unhappy user you can always drop the max GPU in any kernel manager to 800mhz and set on boot if you got an inferior 865 although artifacts have only been reported by 1 person period. A more productive approach rather than bad mouthing someone trying to provide a free service is "can you build a version that maxes out at 900mhz?"... Respect please in the forums.
jamescable said:
I mainly wanted the wakeloxk blockers, and other battery saver stuff lol. Don't care about OC
Click to expand...
Click to collapse
Well I put up custom and OOS just use a kernel manager to set the high frequency you want it to stop at on boot. But before you do, here's a day of basically using the phone a lot at 120hz with many apps open. Note someone here didn't look at the SOT DRAIN which is 100/8.27 = 12hrs SOT. I didn't start it with a full battery. I do that on purpose start at 60% or so to see how it drains in the middle of the discharge. So I'd advise those that are quick to criticize, make sure you actually calculate something before saying it's "horrible" when it's as good as stock.
mslezak said:
Well I put up custom and OOS just use a kernel manager to set the high frequency you want it to stop at on boot. But before you do, here's a day of basically using the phone a lot at 120hz
Click to expand...
Click to collapse
That's horrible, considering auto gives me 9-12 hours screen on time, depending on what I am doing obviously
jamescable said:
That's horrible, considering auto gives me 9-12 hours screen on time, depending on what I am doing obviously
Click to expand...
Click to collapse
What is your setup I can only dream of these nos
jamescable said:
That's horrible, considering auto gives me 9-12 hours screen on time, depending on what I am doing obviously
Click to expand...
Click to collapse
You do realize that this is 12 SOT if you never let it sleep and use it all the time, look at the stats and do some math. 100%/8.27% = 12hrs SOT. Idle went up because I was on phone calls for an hour, and the screen turns off. It's usually 0.6%/hr if you're using it (on WiFi), 1%/hr on cell, turning it on and off every few minutes will cause more drain. I was using my phone a lot today that way. I would say that's amazing to get the same SOT on a modded kernel. I haven't optimized a thing in the ROM or notifications, just used the kernel. I don't care if you use it, do as you wish.
The best way to get help, or to find me is on the TG group. There are people there that can help you out if need be.
mslezak said:
You do realize that this is 12 SOT if you never let it sleep and use it all the time, look at the stats and do some math. 100%/8.27% = 12hrs SOT. Idle went up because I was on phone calls for an hour, and the screen turns off. It's usually 0.6%/hr if you're not using it, turning it on and off every few minutes. I was using my phone a lot today that way. I would say that's amazing to get the same SOT on a modded kernel. I haven't optimized a thing in the ROM or notifications, just used the kernel. I don't care if you use it, do as you wish.
Click to expand...
Click to collapse
mslezak said:
Anyway I'm tired of people requesting things and then getting completely incorrect information and yelling at me because they either can't do math or they don't know how to use a kernel manager. I can be reached on the TG group but you all are on your own now. All I hear are complaints for doing free work for people I don't even know, some of you need to learn some manners.
Click to expand...
Click to collapse
Ignore the haters and complainers...
I just flashed (RadioActive-WL-295-920GPU-custom-2.1.4-BETA.zip) over CR_Droid (CR 03/08 and 03/26 builds 8Pro) and it made a HUGE difference in smoothness, snappiness and performance. I don't worry too much about battery drain as we can top off our phones in less than 20 minutes a day. The under-clocking is also wonderful. I remember back in the G2 days we not only underclock, but would under-volt ALL the frequencies just a few ticks away from unstable for more battery life (dependent on the cpu bin ver), but not really that necessary anymore with larger batteries and super quick charges.
Much respect and appreciation and hope to see more tweaks and builds in the future
Agimax said:
Ignore the haters and complainers...
I just flashed (RadioActive-WL-295-920GPU-custom-2.1.4-BETA.zip) over CR_Droid (CR 03/08 and 03/26 builds 8Pro) and it made a HUGE difference in smoothness, snappiness and performance. I don't worry too much about battery drain as we can top off our phones in less than 20 minutes a day. The under-clocking is also wonderful. I remember back in the G2 days we not only underclock, but would under-volt ALL the frequencies just a few ticks away from unstable for more battery life (dependent on the cpu bin ver), but not really that necessary anymore with larger batteries and super quick charges.
Much respect and appreciation and hope to see more tweaks and builds in the future
Click to expand...
Click to collapse
Thanks bud, glad to hear good results with the kernel. On TG everyone has been full of compliments. Let's hope it stays that way here as well. We can conduct everything in a respectable manner.
Now if you REALLY want to save battery and your cell provider supports Voice over WiFi, Google Messages enable enhanced chat features and keep it on WiFi only (i.e. Bluetooth only on while you're using it, Location off unless you're navigating somewhere, NFC off unless you're using GPay, mobile data off), here's what I get being on my phone all day today (started under 60% battery) at 120hz: 7% active drain, 0.84% inactive. If you're asleep it's more like 0.4%. You won't miss any calls or texts either.
great, zero! drain during the bedtime that's awsome! thanks for the kernel upgrade

Categories

Resources