Twisted-Kernel 7.0 (F-I) Flat/Edge [OC/UC] Linaro 7.1[Safety-Net] 8/21/2017 - Galaxy S6 / S6 Edge Unified Development

{
"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"
}
Welcome to the Twisted Kernel for the Galaxy S6 920F, and 925F.......These kernels
are based on G920TUVU5FQE1 with all the correct ramdisk merges. Both kernels also come
with Synaspe support.....which will be discussed more below.
I also want everyone to know that I have a 920T, not a F model,etc.....So I have built
these for YOU, not me. All I ask is a little bit of appreciation for the time I had to spend
on bringing this to yall. I dont think I'm asking for too much. Plus, I dont see very many
kernels here, especially with the amount of optimizations as mine do. Or rather, the experience
in building them.
SYNAPSE
Each kernel has Synapse support. Now, before anyone starts *****ing......there is some Java errors
that I still need to fix. They WILL NOT affect performance OR battery life. I just havent gotten around
to fixing them yet. But, I will be addressing them on the next update.
If you are unfamiliar with Synapse I would suggest that you do some reading on it. It can become
the best thing since sweet tea, or the worst like.......well, you get the picture. BUT, Synaspe does
have a safety feature......if you adjust something (like voltage) and either give or take away too much,
Synaspe will cancel out your selections on a reboot.
KERNEL FEATURES
A57 Cluster OC to 2304 MHz
A57 Cluster UC to 200 MHz
A53 Cluster OC to 1704 MHz
A53 Cluster UC to 200 MHz
Live CPU Stats
20 CPU Govs
Interactive Tuning
Touchkey Boost
GPU OC
GPU Live Stats
HMP Voltage Control
Memory Bus Voltage Control
11 I/O Schedulers
I/O Tunable
LMK Profiles
Ultra Kernel SamePage Merging UKSM
UKSM Live Stats
Dynamic Dirty Page Writeback
Virtual Memory
Zswap Memory Pool
Kernel Entropy
Gentle Fair Sleeper Control
Arch Power Control
Randomisation
Freeze Timeout
Google Play Services Battery Drain Fix
Minimal Wake Lock Control (still working on this)
Power Suspend Control
EQ Sound Controls
Thermal Controls ( still working on this )
LED Notification Controls
13 TCP Algorithm
Optimize DataBase Controls
FSTrim Control
Wipe Options
Wipe Junk Folders
Build.prop Control
Logcat Controls
And Info
My kernels provide the best of both worlds, performance and battery life. If you want your
device to be wide open and battery life isnt a issue, you can tune it to fly just as fast as you
want. Or, if your the conservative type, you can tune it in to get you the best battery life you
can possibly have on the S6. The choice is all yours on how YOU want your device to run. All
I did was give you the means to do so........
MAGISK
My kernel comes with all the commits in order for it to pass all Safety-Net restictions. But,
Magisk can also cause issues such as loosing root on a reboot, or causing errors in Synaspe.
This is due to BusyBox which he has implemented in his binary. This is NOT a kernel issue.
So please dont flood my thread with things I cannot control.
SUPERSU
SuperSU works just fine. Only set-back is that it will not pass Safety-Net. BUT, he does have
a Aroma installer that just may help to pass all of Safety-Net bull........I myself uses SuperSU
Just make sure that you flash either Magisk or SuperSU after you flash the kernel. Failure
to do so will make it boot back to TWRP......
ISSUES/BUGS/REBOOTS
If you have any of these problems you need to speak up. I have been on this kernel for awhile
and have yet to run into any issues. Thats not saying that you won't either.....
REMEMBER, I BUILT THESE KERNELS FOR you.........
DOWNLOADS
920F
925F​
XDA:DevDB Information
Twisted-Nougat-Kernel, Kernel for the Samsung Galaxy S6
Contributors
The Sickness
Source Code: https://www.androidfilehost.com/?fid=817550096634793936
Kernel Special Features: Nougat 7.0
Version Information
Status: Stable
Stable Release Date: 2017-08-21
Beta Release Date: 2017-08-21
Created 2017-08-22
Last Updated 2017-08-21

Mine

Mine #2

Will try that, Thx bro!

Sir @The Sickness may i ask if 925F version maybe flash on edge korean version or is any one here have manage to flash it on edge korean version..?

Where is this supersu aroma? I had never heard about an aroma installer for supersu, i'm interested in it

Warrenforfree said:
Sir @The Sickness may i ask if 925F version maybe flash on edge korean version or is any one here have manage to flash it on edge korean version..?
Click to expand...
Click to collapse
You can try. Just make sure have a backup first
erghetto said:
Where is this supersu aroma? I had never heard about an aroma installer for supersu, i'm interested in it
Click to expand...
Click to collapse
Search for Chainfire in XDA...there is a thread on it

The Sickness said:
You can try. Just make sure have a backup first
Search for Chainfire in XDA...there is a thread on it
Click to expand...
Click to collapse
Not that?
https://forum.xda-developers.com/apps/supersu/supersu-aroma-installer-t3414877

rifek4 said:
Not that?
https://forum.xda-developers.com/apps/supersu/supersu-aroma-installer-t3414877
Click to expand...
Click to collapse
Yes, that thread.
I do have Magisk 13.3 working just fine on my end

The Sickness said:
Yes, that thread.
I do have Magisk 13.3 working just fine on my end
Click to expand...
Click to collapse
Me too like it but do I can ask you why 13.3 not newest 13.6? And which kernel you using, Twisted? I asking, because you told in info that Twisted isn't compatible with Magisk. I tried use Magisk 13.6 on NNE5.1 ROM with Twisted Kernel and didn't works

rifek4 said:
Me too like it but do I can ask you why 13.3 not newest 13.6? And which kernel you using, Twisted? I asking, because you told in info that Twisted isn't compatible with Magisk. I tried use Magisk 13.6 on NNE5.1 ROM with Twisted Kernel and didn't works
Click to expand...
Click to collapse
Didn't know about 13.6.
I use my own kernel which is Twisted 920T

The Sickness said:
Didn't know about 13.6.
I use my own kernel which is Twisted 920T
Click to expand...
Click to collapse
That's for the T-Mobile S6 version? And how u turn it on to working with Magisk? I flashed NNE5.1 and just after that Twisted Kernel then Magisk > Reboot > got "no root" in Magisk window

rifek4 said:
That's for the T-Mobile S6 version? And how u turn it on to working with Magisk? I flashed NNE5.1 and just after that Twisted Kernel then Magisk > Reboot > got "no root" in Magisk window
Click to expand...
Click to collapse
I just looked and now no root...
Back to SuperSU for me

The Sickness said:
Back to SuperSU for me
Click to expand...
Click to collapse
Yes I did it heh... But BTW for now I going to latest N0G33K Kernel

Hmm thanx bro im try it

Any chance to get 925W8 compatibility?

I got G925F and Twisted Kernel is not working for me on NNE5.1.... Its start to boot then reboot and back to recovery.

You must everytime reflash root (magisk/supersu.zip) directly after flashing new kernel.

Awesome work! @The Sickness One question though, is this the same kernel as the one you pulled off in the Original development section?

tiktakt0w said:
Awesome work! @The Sickness One question though, is this the same kernel as the one you pulled off in the Original development section?
Click to expand...
Click to collapse
Yes, but now he's changing few important things and we are waiting for updated version

Related

[UKM for OP2] Install synapse and tune you kernel for your needs! [Works on CM13/HOS]

{
"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"
}
About
Synapse is a kernel tweaking app developed by @AndreiLux that needs the Universal Kernel Manager (UKM) to work and it's developed by @apb_axel. It is one of the most complete choice for kernel management and it lets you fully unleash your kernel power, may it be battery saving, pure performance or a compromise between the two. You can find more information on UKM at this link: UKM xda thread
Screenshots:
What you need to download:
- Synapse
- UKM for Oneplus Two
- Busybox (i recommend this one) [N.B.: Busybox is not strictly required since there is an in-built busybox in UKM, but installing this updated one in my system has usually resolved stability issues with synapse]
- Root is required (use either SU 2.67 or later or in-built cm13 root)
Useful downloads:
View attachment Synapse.zip - flashable synapse that will install the app in /system
UKM uninstaller from official page
Useful links:
Official synapse/ukm thread
Official synapse google+
Instructions:
1. Download UKM from above link
2. Boot into recovery
3. Flash UKM
4. Reboot to system (no dalvik cache wiping required, but you can do it if you prefer)
5. Uninstall any kernel tweaking apps you might have (Kernel Adiutor, Ex Kernel Manager, Aero Kernel Control.....)
6. Install Busybox, open it and install busybox in system
7. Install Synapse
8. Launch Synapse
9. If you get "no UCI support detected" or synapse is not recognizing phone, just force close the app and re open or reboot the phone and you are good to go
10. Happy tweaking!
Click to expand...
Click to collapse
Protip:
If you want to be able to change cpu governors/frequencies you have to leave atleast one big core online in the hotplug section; once you have tweaked governors/frequencies, you can turn it off and restart synapse. You will have "Ssekbar error" but that's only because in MM/CM13 the phone is able to shut down all the big cores and if that happens the kernel tweaking apps are not able to change cpu values.
THANKS TO:
@AndreiLux for Synapse
@yarpiin for putting ukm together on opt
@ak for helping @yarpiin in his work
@apb_axel for starting UKM project
@benschhold for providing a good and stable custom kernel (actually the first working one for CM13)
@yarpiin again for his good kernel for cm13!
CONFIRMED TO WORK ON CM13/HOS, NOT TESTED YET ON OOS BUT SHOULD WORK, FEEL FREE TO TEST AND REPORT​
Disclaimer:
I am in no way responsible for any harm, damage, nuclear fission, universal big bang or you getting fired becaus alarm app didn't work that may occur to your device through the use of this app.
LIST OF CUSTOM KERNELS FOR OUR AMAZING ONEPLUS TWO
Kernels with built-in UKM (CM13):
Yarpiin Custom Kernel
Kernels without built-in UKM (CM13):
Benschhold cm13 kernel
N.B.: i'm putting in kernels still mantained and updated by developers and for latest versions of android only (MM); for anyone of you missing Boeffla kernel, i will include as soon as he develops new kernel for OOS 3 and cm13
Just in case
Just installed this. Upon installing busybox to system, and installing synapse.. Synapse did not recognize.. Restarted phone and then Synapse can be used.
Add in instructions: reboot phone after installing busybox to system
update: working great otherwise Now support for lower max cpu frequencies, only the input boost frequency. Hopefully kernel and synapse will support this ability
Is it possible to make it compatible with boeffla kernel on OOS??
Mohit31 said:
Is it possible to make it compatible with boeffla kernel on OOS??
Click to expand...
Click to collapse
It has been tested for cm13 only, but you can try it on oos with boeffla kernel and report if you had success
tlxxxsracer said:
update: working great otherwise Now support for lower max cpu frequencies, only the input boost frequency. Hopefully kernel and synapse will support this ability
Click to expand...
Click to collapse
Edit in instructions and added a protip section
Mohit31 said:
Is it possible to make it compatible with boeffla kernel on OOS??
Click to expand...
Click to collapse
I think it should work but might be buggy and also in Andis kernel there is more features than in CM 13 kernel im on CM 13 but will try to set OOS and see what can be done still as advised on Boeffla kernel Andis app is best to control his kernel
Awesome can confirm this is working on kingmercians hydrogen mm ROM with the stock kernel. Thanks. Also to the other users using boeffla there is no point in using boeffla and this its actually a bad idea just pick one
tlxxxsracer said:
Add in instructions: reboot phone after installing busybox to system
Click to expand...
Click to collapse
no, just swipe synapse away from recents and reload it, it'll work.
twist3d0n3 said:
no, just swipe synapse away from recents and reload it, it'll work.
Click to expand...
Click to collapse
Just to clarify there is builded in busybox into UKM and it use its own path , Ukm and synapse works regardless of busybox installed or not and regardless of busybox version installed
---------- Post added at 13:33 ---------- Previous post was at 13:31 ----------
And one more thing you have to be either on stock su provided by rom developer or latest supersu 2.67 older versions of su breaking UKM and make device unsupported error in synapse
yarpiin said:
Just to clarify there is builded in busybox into UKM and it use its own path , Ukm and synapse works regardless of busybox installed or not and regardless of busybox version installed
---------- Post added at 13:33 ---------- Previous post was at 13:31 ----------
And one more thing you have to be either on stock su provided by rom developer or latest supersu 2.67 older versions of su breaking UKM and make device unsupported error in synapse
Click to expand...
Click to collapse
I'll add in OP
Awesome work bro. I just love to use synapse for control kernel.
thanx .
As I mentioned on the BlissMallow thread, I had some problems getting UKM and Synapse to work properly with the latest ROM/Kernel (02-18/0.3).
Apparently this should work though, so I might have to give it another try.
Methroix said:
As I mentioned on the BlissMallow thread, I had some problems getting UKM and Synapse to work properly with the latest ROM/Kernel (02-18/0.3).
Apparently this should work though, so I might have to give it another try.
Click to expand...
Click to collapse
It is same zip what was your problem ?
Testing here with H2o skydragon, work perfect, great job
Sent from my ONE A2005 using Tapatalk
I'm unable to change the cpu governor ever since doing this.. I go back into kernel auditor and it doesnt even let me change the governor. Just shows a white box.
My phone will not go into deep sleep, whereas before it would
yarpiin said:
It is same zip what was your problem ?
Click to expand...
Click to collapse
I figured it was the same zip, so I've gone ahead and used the one I downloaded earlier.
I went through the same procedure as last time, apart from not clearing cache this time around.
This time it actually worked out!
I had to give the big cluster some time to cool down before I could tweak it, but this was the issue with AK's Kernel as well.
As to what went wrong the last time(s); I have no idea.
Thank you for bringing proper kernel management to CM13!
Happy that it worked
If i helped just it thanx
tlxxxsracer said:
I'm unable to change the cpu governor ever since doing this.. I go back into kernel auditor and it doesnt even let me change the governor. Just shows a white box.
My phone will not go into deep sleep, whereas before it would
Click to expand...
Click to collapse
Using two kernel management apps simultaneously is a recipe for possible disaster.
Flash UKM and install Synapse. Then uninstall or disable Kernel Adiutor.
Reboot and (possibly) rejoice.
Methroix said:
I figured it was the same zip, so I've gone ahead and used the one I downloaded earlier.
I went through the same procedure as last time, apart from not clearing cache this time around.
This time it actually worked out!
I had to give the big cluster some time to cool down before I could tweak it, but this was the issue with AK's Kernel as well.
As to what went wrong the last time(s); I have no idea.
Thank you for bringing proper kernel management to CM13!
Click to expand...
Click to collapse
Temp is not the issue but hotplug in cm13 all cores are hotplugged it means cpu 0 and 4 can be setted to offline and that make synapse to not pick up values from these two (they control scaling, govs and others).
Thats why ukm on boot triggers all 4cores online and they stay online until you change values in hotplug tab

[Kernel] [4/2] [MM] Momentum Kernel for WI501Q

{
"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"
}
Momentum Kernel​
Hello everyone! How are you doing?
Today I give you Momentum!! A somewhat minimalistic kernel that will drive your watch to perform with the least amount of lag possible with decent battery life.​
Momentum Features:​
Option to enable all 4 cores
Has performance, powersave, userspace, ondemand, smartmax, and interactive governor options
CPU Underclock to 96Mhz
Features IntelliPlug along with a CPU Profile for how the cores are enabled
And has noop, deadline, row, cfq, and fiops for I/O scheduling
More exciting features to come!
Momentum Release Versions:​
2/28/16 Initial release v0.1A :
Lightly modded!
4/2/16 First update v0.5
Added underclock to 96mhz.
Momentum Downloads:​
Marshmallow release {NEW}
LOLLIPOP VERSION {OLD}
Recommended Files and options to use with Momentum:
Download Kernel Auditor to change kernel settings. This one is modified for Wear. You will need SuperSU and busybox for it to open! Install Kernel Auditor by typing adb install KernelAuditor.apk in the CMD
Kernel settings that I recommend changing are, CPU Governor to Interactive, Go into CPU Hotplug and turn on IntelliPlug, and scroll down to the second option below IntelliPlug to Profile, Change that to Eco Conservative. But experiment to see what options work for you! Your watch should run with very low to no lag now!
XDA:DevDB Information
Momentum , Kernel for the Asus ZenWatch 2
Contributors
T10NAZ
Source Code: https://github.com/PharaohsCurse/Momentum-Kernel
Kernel Special Features: Intelliplug, SmartMax Governor, 2 cores enabled while touching the display
Version Information
Status: Alpha
Created 2016-02-29
Last Updated 2016-04-02
Reserved
Thank you @mammothjojo88 and @matze19999 for giving the Kernel a spin before I released it!
Reserved
Future of Momentum:​
I will keep this Kernel updated whenever new kernel versions drop, and will work with any and all OTA's that will drop to make sure it runs good with them.
Add anything that I find that will benefit the watch, and what the users suggest!
Overall nice kernel! Thank you!
Any significant impact to battery life?
Rockwig said:
Any significant impact to battery life?
Click to expand...
Click to collapse
there isnt a horrible impact, I can manage to get under 3 days
Is there a way to tweak the hotplug settings or the amount of cores?
Just like using kernel adiutor or synapse on the smartphone but on the watch?
Does the watch react faster to user input with this kernel?
Does the watch wake up faster from always-on-display-sleep-mode?
r0tati0n said:
Is there a way to tweak the hotplug settings or the amount of cores?
Just like using kernel adiutor or synapse on the smartphone but on the watch?
Does the watch react faster to user input with this kernel?
Does the watch wake up faster from always-on-display-sleep-mode?
Click to expand...
Click to collapse
Kernel Auditor download You need SuperSU and busybox, I used the wear 5.0.1 su and I think i found a wear busybox somewhere on xda
The watch totally performs better, scrolling through menus and overall using the watch feels like it should and it wakes up about the same from screen on sleep!
T10NAZ said:
there isnt a horrible impact, I can manage to get under 3 days
Click to expand...
Click to collapse
Wow, 3 days? I can't even get close to that on stock, I assume ambient display off, but is there anything else you do to get that battery life?
I think you should specify supported device is only for WI501Q. I don't think this works for WI502Q. I have tested with tethered boot, and same with recovery, "booting...FAILED (remote: dtb not found)"
DDz_1888 said:
I think you should specify supported device is only for WI501Q. I don't think this works for WI502Q. I have tested with tethered boot, and same with recovery, "booting...FAILED (remote: dtb not found)"
Click to expand...
Click to collapse
Ahh alright, would you mind being a tester for me? When I get home I can produce a kernel for the 502
Since you're taking suggestions, maybe you could add lower frequencies and maybe even higher frequencies just for the lulz.
T10NAZ said:
Ahh alright, would you mind being a tester for me? When I get home I can produce a kernel for the 502
Click to expand...
Click to collapse
Sure thing. But since I would like to keep my watch as stock as possible before getting working recovery, could I be a tester for the recovery first? I really cannot afford to ruin system partition I don't feel safe before backing up stock boot and system partitions first. And my watch just updated itself to Android system 6.0.1, hence kernel compatibility issues may be a problem.
So, I finally got my watch up and going fully. In short, like OP is suggesting, you'll need to be comfy with adb commands. I've gone ahead and zipped up the Wear BusyBox, Wear SuperSU, and KernelAuditor.apk, all flashable within recovery once you get up and going with tethered boot.
https://drive.google.com/open?id=0B3yTF2VrLVv8cW82Wnl4REdYZTA
Maybe OP will want to grab these files and put them in the OP so others won't have to hunt them down like I had to lol!
*edit* Oversight on my end. The Kernel Auditor apk is in my zipped file, but I forgot I got the apk from OP lol.
tzbigworm said:
So, I finally got my watch up and going fully. In short, like OP is suggesting, you'll need to be comfy with adb commands. I've gone ahead and zipped up the Wear BusyBox, Wear SuperSU, and KernelAuditor.apk, all flashable within recovery once you get up and going with tethered boot.
https://drive.google.com/open?id=0B3yTF2VrLVv8cW82Wnl4REdYZTA
Maybe OP will want to grab these files and put them in the OP so others won't have to hunt them down like I had to lol!
*edit* Oversight on my end. The Kernel Auditor apk is in my zipped file, but I forgot I got the apk from OP lol.
Click to expand...
Click to collapse
You can flash the kernel, its just twrp thats all weird
Sorry, yeah, flash the kernel through TWRP. That's what I did lol. I actually had posted differently just wanting to confirm flashing the kernel to the boot sector lol, but I just hit the button and it works. I don't believe you're at the point yet where you want to release an untethered recovery to flash on the watch as of right now. Thank you for your work on getting the modding started.
if i flash this now what do i need to do to get the 6.0.1 ota on my W501Q ? make a backup of everything prior to rooting kerneling busyboxing etc and restore that when the ota is finally live? would sideloading or installing the ota also require restoring everything to stock? always had custom roms on my phone so im a total ota noob
will this kernel work with the new MM update that was just released? I'd love to try this since I'm noticing some lag now that im using the watch a lot more with the speaker playing.
slothdabski said:
will this kernel work with the new MM update that was just released? I'd love to try this since I'm noticing some lag now that im using the watch a lot more with the speaker playing.
Click to expand...
Click to collapse
It will not, it looks like I'll have to update the kernel here soon
got the update sideloaded by now. havent done any modifications before. so the kernel is out of order but that was expected.
does the supersu-2.40-wear.zip still work? since its required by kernelauditor (and i want to finally root it)

[KERNEL][MM][DRM FIX] EliteKernel v3.4.33 [UB]

Elite Kernel
Unleash the beast
for Xperia Z3 Compact
First of all, I have spent a lot of hours on this project, trying to obtain the true power of this great device.
This Kernel is designed for optimize battery life and give more performance than stock kernel.
Features
Based on lastest sources, 23.5.A.1.291
DRM injection inside the Zip, you don't need flash DRM Fix, just kernel
OC up to 2,7Ghz
UC for better battery life
Optimized voltage tables and voltage control
Thunderplug v5.4, a load based hotplug and optimized for multi-core devices and it is very battery friendly with a great performance
IntelliThermal v2, a custom thermal control better than stock one
GPU overclock up to 657Mhz
Kcal control
More I/O schedulers like FIOPS, Zen, VR, BFQ...
init.d support
Power suspend driver v1.5
Build with UBERTC 4.9 and some optimizations
More stuff that I don't remember
ToDo
Add more governors
Share interactive governor tuned settings for battery and performance
More GPU optimizations
F2FS support
More battery life optimizations
Maybe Quick Chargue 2.0 support.
Maybe sound optimizations
Installation
Install my lastest TWRP (go here)
Make a backup of the partition System (MUST DO, because the kernel change some modules on system)
Select a version according to your needs. (See below)
If you have a TA partition backup:
Download EliteKernelZ3c-(current version).zip and extract the boot.img on your pc.
Use the ta_poc tool by munjeni with your TA partition backup.
Rename the new_boot.img to boot.img and replace it on the EliteKernelZ3c-(current version).zip
Boot on FOTAKernel recovery, with the phone power off, press at the same time power key and vol- until the phone vibrates.
Flash your EliteKernelZ3c-(current version).zip with the boot.img patched.
Enjoy!
Click to expand...
Click to collapse
If you don't have a TA partition backup (so you need DRM FIX):
Boot on FOTAKernel recovery, with the phone power off, press at the same time power key and vol- until the phone vibrates.
Flash EliteKernelZ3c_D-(current version).zip
Enjoy!
Click to expand...
Click to collapse
Usage with eXistenZ 5.6.5 (or similar Stock based ROMs) and Magisk
eXistenZ 5.6.5 includes a TWRP recovery inside the rom, and we don't need it since we have some options for recovery here, so for remove it download this file and flash it on recovery.
eXistenZ 5.6.5 also includes SuperSU on the rom and for correclty install magisk we need to remove it, so first of all update the SuperSU app on the Play Store, after go to the app and on settings there is an option for uninstall SuperSU and unroot the System, so tap it (Sometimes if it takes more of 3 mins, close the app and do it again), after that reboot the phone and done, SuperSU uninstalled.
Now the installation/upgrade of magisk using my kernel.
Download the lastest magisk zip and magisk uninstaller zip here, put they on SD card.
Reboot on recovery, uninstall magisk with the uninstaller zip if you have it, flash the kernel zip, flash magisk and reboot to system, and done, enjoy magisk.
Download
Z3c
Credits
@AndroPlus
@Myself5
@DooMLoRD
@pec0ra
@dorimanx
@faux123
@Doom Slayer a lot of thanks to this great dev
@dontbelive great dev and my Z3 tester
@BlackSoulxxx
@savoca
Source
https://github.com/ShadowElite117/Xperia-Z2-Z3
Changelog
v1
First release
Click to expand...
Click to collapse
v2
Based on new 23.5.A.1.291 sources
Click to expand...
Click to collapse
v3
Added missing conservative GPU Governor
Added Simple GPU algorithm
Added Adreno idler for battery saving
Added Fauxsound v3.6
More optimizations
Click to expand...
Click to collapse
v3.4.13
Kernel made from scratch, so no special features for now (Sorry guys I do this for a better kernel).
Implemented last_kmsg for a correct bug report.
Updated linux kernel version from 3.4.0 to 3.4.13 (Correclty done and free of strange bugs).
QC 2.0 enabled (don't expect miracles, it is limited on Z3 so it works with some QC 2.0 chargers)
Full compatibility with Magisk, eXistenZ and ta_poc tool.
Click to expand...
Click to collapse
v3.4.33
Updated linux kernel version from 3.4.13 to 3.4.33.
Enabled a kernel flag for try to enable Assertive Display on Z2 (It just give me logs that help me to know what is happening).
Dropped TWRP inside the kernel, since I have build newest TWRP for aries, for FOTAKernel partition. It has more features and it is more bug free than recovery inside the kernel.
Click to expand...
Click to collapse
FAQs
Q. How I can report a bug?
A. Give me a last_kmsg, tell me your ROM, if you have Magisk, Xposed Framework or similar things and describe me the problem.
Q. How I can contact you?
A. Please don't spam me with PMs, you can contact me on Telegram: ShadowElite117
This looks amazing, flashing now, thanks heaps!!!
I run slim 2.3, it based on 23.5.A.1.238. can I flash this kernel?
dddestiny said:
I run slim 2.3, it based on 23.5.A.1.238. can I flash this kernel?
Click to expand...
Click to collapse
Probably yes, since it is based on .575 and other kernels on this base work with .238.
Well guys how it is working on Z3c??
This is strange, guys...
Once we had no stock custom kernel - now we have three - which came out almost at the "same" time
@ShadowElite: Big thanks for this! Looks very prommissing! :good:
Especially build in DRM fix is nice as well as OC and UV.
I guess its time to move to MM
fluffi444 said:
This is strange, guys...
Once we had no stock custom kernel - now we have three - which came out almost at the "same" time
@ShadowElite: Big thanks for this! Looks very prommissing! :good:
Especially build in DRM fix is nice as well as OC and UV.
I guess its time to move to MM
Click to expand...
Click to collapse
Thanks, please feel free of test and report feedback
Finaly a reason to unlock my BL again
Testing in SLIMM 2.4 now doing very well and the performance is excellent the only problem I had is that I do not appear intellithermal in kernel auditor otherwise it's great and I threw AnTuTu score of 65884 xd thanks for your work
What does drm fix mean?can v unlock bootloader without loosing drm keys...
Edit-got wat it is.
One q...does this mean can use custom ROMs with camera quality as the stock?
subinsg said:
What does drm fix mean?can v unlock bootloader without loosing drm keys...
Edit-got wat it is.
One q...does this mean can use custom ROMs with camera quality as the stock?
Click to expand...
Click to collapse
It only works on stock based roms
Someone the same problem? Max Frequency is 2265, when I try to push it up it goes alone down to 2265. Don't know what to do? I tried the kernel auditor and some other tools. All the same?
{
"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"
}
Worked on slim rom .238
Cz this rom based on .575
Sorry for my bad english
alex20877 said:
Someone the same problem? Max Frequency is 2265, when I try to push it up it goes alone down to 2265. Don't know what to do? I tried the kernel auditor and some other tools. All the same?
Click to expand...
Click to collapse
For avoid bugs please make a clean installation
I made clean install and I have the same problem. It seams that frequency is lowered when the temperature increase
I flashed on 23.5.A.1.238_R5D_SLiMM_2.4 ROM and it isn't booting my device up now, what do i do?
Essyy786 said:
I flashed on 23.5.A.1.238_R5D_SLiMM_2.4 ROM and it isn't booting my device up now, what do i do?
Click to expand...
Click to collapse
If you can boot into recovery, try installing another kernel .
Essyy786 said:
I flashed on 23.5.A.1.238_R5D_SLiMM_2.4 ROM and it isn't booting my device up now, what do i do?
Click to expand...
Click to collapse
Is your bootloader unlocked?
Is IntelliThermal on kernel? Maybe I forget to enable it, please tell me

[KERNEL][6.0.1][J5 2015/H][Sabermod 4.8] The Dark Kernel V1.0

{
"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"
}
Hey guys! This kernel is only for SM-J500H as of now. I will add support for other variants soon. Now lets talk business
Features:
Built using Sabermod 4.8 toolchain
Latest J500HXXU2BPK4 sources
Patched with SuperSu 2.79 (Systemless)
Patched Linux version to 3.10.104
KCAL advanced colour control
SELinux permissive
MSM Hotplug enabled
Mild CPU Undervolt (Beta experimental values)
Compiled with -03 flag for better optimization and speed
Fixed memory leak in alloc_pid
Free memory optimizations
Tuned XZ for ARM processors
NEON and VFP float enabled
Init.d support
Busyboxed
Insecure boot
Patched to boot Note 7 roms
ADB enabled by default​
To do list:
New CPU governors
New I/O Schedulers
Overclock and Underclock (I Dont find this neccessary because the phone works properly without overclock as well)
Add support for other models
Please note that i am a beginner in kernel development. I learn and keep learning so that i can bring out something different. Lastly if you got some features on your mind then my ears are always open. However i can't assure you that it will be added or implemented but i can give it my best shot within my capabilities. Further development on this project is dependent on the response i get from you guys. Lack of response will bring an end to this project. Enjoy the kernel guys.
Instructions:​1. Take a backup of your boot partition using TWRP first.
2. Navigate to the zip and flash.
3. Reboot and enjoy.
Downloads:​Don't forget to hit the thanks button. It will hardly take a second:good:
SM-J500H​
Sources
Contributors:
@KingRaheel
Credits:
@Me ofcourse :P
@BlackMesa123 For Ramdisk edits
Status:Testing
Created on: 31/12/16
For changelog
For further plans if any
Seems cool! Can't wait for the FN model :silly:
Good job!
Good!
i'm happy to see this thread,
You just opend o door for new oportunities!
you have all my consideration for this.
if i understand well, this is for MM botloader?
can you share the wlan.ko(pronto_wlan.ko) from J500HXXU2BPK4 'till you make it to work with all versions?
Of course if you are agree with your kernel to be using in other rom ports!
Thanks!
EDIT:
Thanks...again, i didnt checked the zip archive.
i just see the wlan.ko in it!
@KingRaheel
Congratulations!
I see that you've chose Sabermod, a nice choice. Did you try 4.9+ toolchain (including 4.9) ? I'm curious if it works on stock kernel.
@KingRaheel
I don't have the knowledge, but after looking at other kernel, it seems that the change you've made for Linux kernel 3.10.104 is not enough! Other files must be changed too, not only that. I think you have to cherry pick or merge the Linux kernel changes.
Take a look at the changelog of 3.10.104: https://cdn.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.10.104 .
Also, I'm not sure, but I think the kernel version must be updated one by one, with it's changes/patches. E.g.: from 3.10.49 to 3.10.50, then 3.10.51 (I don't know if .50 and .51 versions exists, I just gave an example).
Waiting for J500F ???
vaserbanix said:
Good!
i'm happy to see this thread,
You just opend o door for new oportunities!
you have all my consideration for this.
if i understand well, this is for MM botloader?
can you share the wlan.ko(pronto_wlan.ko) from J500HXXU2BPK4 'till you make it to work with all versions?
Of course if you are agree with your kernel to be using in other rom ports!
Thanks!
EDIT:
Thanks...again, i didnt checked the zip archive.
i just see the wlan.ko in it!
Click to expand...
Click to collapse
Thank you sir. Yea its for MM bootloader. . As of now i am trying to figure out how to make the sources of j500h to work on other models. I know that it can be done using different defconfig files and i had got the zImage as well but i think there is something more to it. Hopefully once its out for other models, people can use it to port or build some rom. If they do then my work paid off
#Henkate said:
@KingRaheel
Congratulations!
I see that you've chose Sabermod, a nice choice. Did you try 4.9+ toolchain (including 4.9) ? I'm curious if it works on stock kernel.
Click to expand...
Click to collapse
Thank you buddy. Yeah i had tried with uber 4.9 and it worked but the kernel was kind of creepy lol. Random reboots for some reason. I solved that today and i think ubertc is way better than sabermod in terms of stability and most importantly battery life.
#Henkate said:
@KingRaheel
I don't have the knowledge, but after looking at other kernel, it seems that the change you've made for Linux kernel 3.10.104 is not enough! Other files must be changed too, not only that. I think you have to cherry pick or merge the Linux kernel changes.
Take a look at the changelog of 3.10.104: https://cdn.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.10.104 .
Also, I'm not sure, but I think the kernel version must be updated one by one, with it's changes/patches. E.g.: from 3.10.49 to 3.10.50, then 3.10.51 (I don't know if .50 and .51 versions exists, I just gave an example).
Click to expand...
Click to collapse
Yes you are right. The whole thing has be changed. Thats why i simply changed the version as its initial. Lol. I am getting many compilation errors with the patches made for linux 3.10.104 as i think its due to some config mistakes . So i am doing a lot of research on it and getting the errors solved one by one.
1 overclock is necessary for gaming..The games (World of Gunship) i play lag but PBS by zonik was awesome the games didnt lag..I think at least overclock the GPU to 700 MHZ
2 why dont you just add overclock? i mean if people doesnt want overclocking they can just use app to use normal frequency. can someone tell me this if you put 2.1GHz frequency and i still use 1198MHz frequency will there be any difference if you dont put overclocking and use 1198MHz?
i will explain further if you dont understand 2nd question....
I use J500F currently using Resurrection remix
Sehab084 said:
1 overclock is necessary for gaming..The games (World of Gunship) i play lag but PBS by zonik was awesome the games didnt lag..I think at least overclock the GPU to 700 MHZ
2 why dont you just add overclock? i mean if people doesnt want overclocking they can just use app to use normal frequency. can someone tell me this if you put 2.1GHz frequency and i still use 1198MHz frequency will there be any difference if you dont put overclocking and use 1198MHz?
i will explain further if you dont understand 2nd question....
I use J500F currently using Resurrection remix
Click to expand...
Click to collapse
No need of explaining further. Not all people think the same way as you have said. Overclock to high frequencies will cause high temperature shoot up which will cause lag sometimes. Speed thrills but kills. PSB was smooth because it was using DJSteve kernel which ofcourse had all overclock capabilities. I will add overclock later once i add support to other variants.
KingRaheel said:
Thank you buddy. Yeah i had tried with uber 4.9 and it worked but the kernel was kind of creepy lol. Random reboots for some reason. I solved that today and i think ubertc is way better than sabermod in terms of stability and most importantly battery life.
Yes you are right. The whole thing has be changed. Thats why i simply changed the version as its initial. Lol. I am getting many compilation errors with the patches made for linux 3.10.104 as i think its due to some config mistakes . So i am doing a lot of research on it and getting the errors solved one by one.
Click to expand...
Click to collapse
May I know what was the cause of ubertc random reboot and how you fixed it? It is related to flags?
I'll try myself on stock kernel and I guess I'll run into same problem. Anyway, when I tried ubertc on cm kernel, phone was stuck at Galaxy J5 logo.
Regarding Linux kernel version, did you upgrade it one by one till 3.10.104?
#Henkate said:
May I know what was the cause of ubertc random reboot and how you fixed it? It is related to flags?
I'll try myself on stock kernel and I guess I'll run into same problem. Anyway, when I tried ubertc on cm kernel, phone was stuck at Galaxy J5 logo.
Regarding Linux kernel version, did you upgrade it one by one till 3.10.104?
Click to expand...
Click to collapse
Yes flags. If any soft freeze then reboot. Lol. Actually the case should be opposite that is if any hard freeze then reboot. When i reported to samsung they changed it immediately. Like within 30 mins. Stupid samsung. I changed mine using menuconfig. Thats how i got sabermod also to work . No fault in toolchains
Ofcourse one by one and compile or else you will get 2 pages of errors :laugh: .So i am on 3.10.99 now and i got many errors for 3.10.103 . So just trying to figure out where is the bug
UPDATE:
Wifi confirmed working on most of the basebands. Thanks to all my testers out there
KingRaheel said:
UPDATE:
Wifi confirmed working on most of the basebands. Thanks to all my testers out there
Click to expand...
Click to collapse
Keep up the good work !! :good:
Your J500H tester ...
Wishing a Happy New Year!
One advice would be to provide all other modules too!
Since Kernel is optimized from Toolchain, all modules are affected too.
This will provide a performance increase and stabilization.
You will see that module sizes are much bigger now.
Good luck!!
Gongratulations for the nice work..This device needed a kernel for M6.0.1.. I hope & for other models in the future if you can ofcourse .. Happy New year I wish ! (sry for english)
New update coming soon guys. Support for FN model also added. The kernel will be built again from the scratch with many changes to sources.
Regards
Raheel
Can someone help me to compile the wlan module.
---------- Post added at 03:19 AM ---------- Previous post was at 03:10 AM ----------
#Henkate;70323406 [user=7716560 said:
@KingRaheel[/user]
Congratulations!
I see that you've chose Sabermod, a nice choice. Did you try 4.9+ toolchain (including 4.9) ? I'm curious if it works on stock kernel.
Click to expand...
Click to collapse
I have used uberTC and linaro version 4.9. On my computer linaro compiles a bit slower than uber but has better stability

[KERNEL][Cedric][underclock][block wakelocks]

{
"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"
}
Radium Kernel
This is the ONLY custom kernel yet for Moto G5 Cedric. Proudly brought to you by the team behind Radium kernel, @CodeZero, and @infixremix, this kernel supports many features.
Features
Code:
[LIST]
[*]Display tweaks
[*]Wake lock blocker
[*] Battery optimisations
[*]Better IO bfq , deadline
[*]Sound tweaks
[*]Fsync switch on and off
[*]Fast charge compatible
[*]Underclockable
[*]Kernel version 3.18.48
[/LIST]
Known issues
VDD does does not work with underclock
Please report Bugs to me on telegram @infixremix
Downloads
Kernel
XDA:DevDB Information
RADIUM kernel for Moto G5 (Cedric), Kernel for the Moto G5
Contributors
infixremix, CodeZero
Source Code: [url]https://github.com/infixremix/android_kernel_motorola_msm8937-1[/URL]
Kernel Special Features: [*]Display tweaks [*]Wake lock blocker [*] Battery optimisations [*]Better IO bfq , deadline [*]Sound tweaks [*]Fsync switch on and off [*]Fast charge compatible [*]Underclockable [*]Kernel version 3.18.48
Version Information
Status: Beta
Current Beta Version: 1.0
Beta Release Date: 2017-10-29
Created 2017-10-29
Last Updated 2017-10-29
RESERVED
infixremix said:
RESERVED
Click to expand...
Click to collapse
Awesome Job!
(nice Logo )
Hope this kickstarts the development of other kernels for our device too!
Great Job! Since I am already running the kernel the whole weekend I can say that it runs rock solid. Now let's see if we can get hotplugging going.
Great work, our first Motorola G5 Cedric kernel. ? Thanks a lot lad's.
Just a few things iv noticed
please change the updater script - I know its meant to be a joke but its not really in the spirit of XDA
Onto the kernel itself
Can you explain the following
The big is set to a default of 652mhz yet in kernel Adiutor it doesn't show this in the options but it does show an entry for 249Mhz
The little is still set to a min of 768MHz - can this be underclocked?
Here are some screenshots to explain the points above
TheFixItMan said:
Just a few things iv noticed
please change the updater script - I know its meant to be a joke but its not really in the spirit of XDA
Onto the kernel itself
Can you explain the following
The big is set to a default of 652mhz yet in kernel Adoitor it doesn't show this in the options but it does show an entry for 249Mhz
The little is still set to a min of 768MHz - can this be underclocked?
Here are some screenshots to explain the points above
Click to expand...
Click to collapse
Why would we under clock small it calls for big if the frequency is over used there fore big cluster wouldn't need under clock , the reason why its not avalible is because that's what the voltage table picks which in this case was the mid value . I will be looking too fix this , personally I don't see a problem with the update-binary .
But I will Change thanks for your advice !
infixremix said:
Why would we under clock small it calls for big if the frequency is over used there fore big cluster wouldn't need under clock , the reason why its not avalible is because that's what the voltage table picks which in this case was the mid value . I will be looking too fix this , personally I don't see a problem with the update-binary .
But I will Change thanks for your advice !
Click to expand...
Click to collapse
it also showing core 1 to be permanently offline and it fails to load big frequencies report chart so its hard to run an analysis so I can compare with lineageos kernel
So far in the reports it shows the little to be stuck on 1094mhz and the big at 960mhz but im not sure if that is accurate due to the reporting not working
TheFixItMan said:
it also showing core 1 to be permanently offline and it fails to load big frequencies report chart so its hard to run an analysis so I can compare with lineageos kernel
So far in the reports it shows the little to be stuck on 1094mhz and the big at 960mhz but im not sure if that is accurate due to the reporting not working
Click to expand...
Click to collapse
Umm testers never seemed to have this , I think I'm gonna close the thread then that's not normal
infixremix said:
Umm testers never seemed to have this , I think I'm gonna close the thread then that's not normal
Click to expand...
Click to collapse
keep it open so others can test it as it boots fine so theres no harm to anyone testing
Have a look at kernel Adiutor and see if its the same on yours
TheFixItMan said:
keep it open so others can test it as it boots fine so theres no harm to anyone testing
Have a look at kernel auditor and see if its the same on yours
Click to expand...
Click to collapse
Its not one other guy had it , but do u have core control and vdd and thermal soc on ? If you do only keep one on I suggest core control never had a problem 3 or 4 people didn't have it the one that did didn't know what he was doing he restored bootimg re installed kernel and after 3 days he never had the problem again
infixremix said:
Its not one other guy had it , but do u have core control and vdd and thermal soc on ? If you do only keep one on I suggest core control never had a problem
Click to expand...
Click to collapse
I ran it with its default settings - What i'll do is i'll reset kernel Adiutor and test it again
TheFixItMan said:
I ran it with its default settings - What i'll do is i'll reset kernel Adiutor and test it again
Click to expand...
Click to collapse
If u have again I'd suggest reverting and installing again if this happens again I will close the thread
infixremix said:
If u have again I'd suggest reverting and installing again if this happens again I will closa the thread
Click to expand...
Click to collapse
so I flashed back the lineageos kernel
Kernel Adiutor reported all cores running with the big at 960mhz and little at 728mhz
Turned off all my start at boot options (although when I first tested I stopped it applying them on startup but just to make sure)
Flashed your kernel
It seems to be working now however
little is stuck at 1049mhz - this is because your little gov is set to performance - Changing this to interactive means the little now runs at 768mhz
also big keeps jumping up at 1401mhz where on lineageos kernel it was a stable 960mhz
TheFixItMan said:
so I flashed back the lineageos kernel
Kernel Adiutor reported all cores running with the big at 960mhz and little at 728mhz
Turned off all my start at boot options (although when I first tested I stopped it applying them on startup but just to make sure)
Flashed your kernel
It seems to be working now however
little is stuck at 1049mhz - this is because your little gov is set to performance - Changing this to interactive means the little now runs at 728mhz
Click to expand...
Click to collapse
OK thank you for helping
infixremix said:
OK thank you for helping
Click to expand...
Click to collapse
gone back into Kernel Adiutor and all the big cores are offline - I doubt they actually are its just it cant get the reporting
So theres something wrong with the reporting of the frequencies which needs to be fixed
TheFixItMan said:
gone back into Kernel Adiutor and all the big cores are offline - I doubt they actually are its just it cant get the reporting
So theres something wrong with the reporting of the frequencies which needs to be fixed
Click to expand...
Click to collapse
Ok I'm gonna close the thread till further notice
infixremix said:
Ok I'm gonna close the thread till further notice
Click to expand...
Click to collapse
like I said - no harm leaving it open as people on xda can contribute and those with better kernel knowledge than I have can suggest things
get your testers to use Kernel Adiutor and wait for about 5mins after the phone has booted and then keep opening kernel Adiutor closing it wait a min turn the screen off and so on and then check kernel Adiutor again and see what the reporting says
---------- Post added at 10:15 PM ---------- Previous post was at 09:55 PM ----------
oh and just so people know - this kernel is using a different wifi module to what lineageos uses so if people do test this kernel and then revert back to lineageos kernel please make sure if you replace the wifi module with the one from lineageos or you wont be able to turn on wifi
I have none of the mentioned problems. I set big and small to "interactive" and everything is fine. Scaling seems normal. No core is ever offline.

Categories

Resources