I present you Unicornblood Kernel as flashable standalone zip.
I built it straight from DU source with AnyKernel script.
This kernel only works with OmniRom, DU and Reaper!
Source Date: 2017-07-13
Features :
To know what's included you have to look at GitHub. I'm just to lazy to make a neat list.
DOWNLOAD:
https://drive.google.com/file/d/1krznYjanLUkwzw-1twPPddW6qfr9s8LX/view?usp=drivesdk
XDA:DevDB Information
Unicornblood Kernel, Kernel for the Nextbit Robin
Contributors
DirtyUnicorns
Source Code: https://github.com/DirtyUnicorns/android_kernel_nextbit_msm8992
Version Information
Status: Stable
Created 2018-01-21
Last Updated 2018-01-21
Thanks a lot to @L3R0N. @L3R0N tested it with CrDroid. Unfortunately, it does not work with LOS-based ROMs.
We have unfortunately bad luck. It is then on the device tree. DU and Omni use essentially the same device tree, but LOS is different. This kernel works only with AOSP-based ROMs. AnyKernel will only make the kernel adapt to the Ramdisk of the ROM, if I get it right.
But hey, I have now learned how to compile a kernel. :laugh:
I'm currently testing out your kernel on omni and it's running pretty nice. Running Hawktail 1.2 governor with greenify and naptime. I've been out most of the day, mostly using data, bluetooth's been on for the past 4 hours with spotify playing for about half of that, 3 hours SOT and I still have about 25% battery left.
demeez said:
I'm currently testing out your kernel on omni and it's running pretty nice. Running Hawktail 1.2 governor with greenify and naptime. I've been out most of the day, mostly using data, bluetooth's been on for the past 4 hours with spotify playing for about half of that, 3 hours SOT and I still have about 25% battery left.
Click to expand...
Click to collapse
That's really nice to hear. Thanks for your feedback.
Any Idea if it would work on CarbonROM? New to this kernel thing but really interested to try out just don't wanna break anything on the first try
[email protected] said:
Any Idea if it would work on CarbonROM? New to this kernel thing but really interested to try out just don't wanna break anything on the first try
Click to expand...
Click to collapse
No sorry, the kernel is not compatible with CarbonRom.
NurKeinNeid said:
No sorry, the kernel is not compatible with CarbonRom.
Click to expand...
Click to collapse
sorry for sounding like a complete noob here, but isn't the kernel supposed to work on AOSP ROMs and I checked on CarbonROM's page and it said that it was based on AOSP. If you could educate on what I'm missing that'd be really appreciated. Thanks
[email protected] said:
sorry for sounding like a complete noob here, but isn't the kernel supposed to work on AOSP ROMs and I checked on CarbonROM's page and it said that it was based on AOSP. If you could educate on what I'm missing that'd be really appreciated. Thanks
Click to expand...
Click to collapse
I tried flashing it on Carbon and it bootlooped so I wouldn't advise it. I guess the kernel will only run on Omni.
[email protected] said:
sorry for sounding like a complete noob here, but isn't the kernel supposed to work on AOSP ROMs and I checked on CarbonROM's page and it said that it was based on AOSP. If you could educate on what I'm missing that'd be really appreciated. Thanks
Click to expand...
Click to collapse
These are more or less semantic details. Strictly speaking, LOS is also AOSP-based. But in this case, CarbonRom's device tree is based on that of LOS. And this kernel only works with device trees that are based on Omnis device trees, for example, DU. I'm just as noob as you are and start to understand everything. This kernel was a kind of proof of concept for me. I am trying a lot to understand things better. Since last week I am testing the new interesting device related changes of LOS and have also now tested overclocking and underclocking.
NurKeinNeid said:
These are more or less semantic details. Strictly speaking, LOS is also AOSP-based. But in this case, CarbonRom's device tree is based on that of LOS. And this kernel only works with device trees that are based on Omnis device trees, for example, DU. I'm just as noob as you are and start to understand everything. This kernel was a kind of proof of concept for me. I am trying a lot to understand things better. Since last week I am testing the new interesting device related changes of LOS and have also now tested overclocking and underclocking.
Click to expand...
Click to collapse
please dont kill me but i have an off topic question:
can you make a kernel based on PA sources with this features:
lastest upstream linux update, lastest upstream cfq i/o scheduler, lastest interactive CAF gov, boeffla wakelock driver, simple thermal driver by sultanxda, power efficient workqueues patches by franciscofranco, westwood as default tpc/ip scheduler, kcal driver and dynamic cpu boost driver by sultanxda?
i can help you with the commits.
DiePirate said:
please dont kill me but i have an off topic question:
can you make a kernel based on PA sources with this features:
lastest upstream linux update, lastest upstream cfq i/o scheduler, lastest interactive CAF gov, boeffla wakelock driver, simple thermal driver by sultanxda, power efficient workqueues patches by franciscofranco, westwood as default tpc/ip scheduler, kcal driver and dynamic cpu boost driver by sultanxda?
i can help you with the commits.
Click to expand...
Click to collapse
No, I do not kill anyone lol. I'm not very experienced in kernel development. I could try it but why you dont share your wishes with @linckandrea? He recently asked for suggestions in his thread.
https://forum.xda-developers.com/nextbit-robin/development/kernel-pop-kernel-t3706069/page5
So I am on Omni. Can I can simply flash this via TWRP and then use Hawktail governor via EXKM?
/root said:
So I am on Omni. Can I can simply flash this via TWRP and then use Hawktail governor via EXKM?
Click to expand...
Click to collapse
Yes.
bootloop!
Hi there,
I tried running this kernel with Omnirom on a Robin/Ether.
Really happy with it, NFC is working and cpu governor is pretty solid.
Today I got a bootloop for a second time in a month.
The first time I haven't had time to look at it and thus recovered from a TWRP backup. This time I try to fix it manually.
Is there a roadmap or any guidelines in doing so?
Anyone else managed to revert it withought the use of restore process?
Why is it happening? Do you have any clues?
Regards,
mod
modestos said:
Hi there,
I tried running this kernel with Omnirom on a Robin/Ether.
Really happy with it, NFC is working and cpu governor is pretty solid.
Today I got a bootloop for a second time in a month.
The first time I haven't had time to look at it and thus recovered from a TWRP backup. This time I try to fix it manually.
Is there a roadmap or any guidelines in doing so?
Anyone else managed to revert it withought the use of restore process?
Why is it happening? Do you have any clues?
Regards,
mod
Click to expand...
Click to collapse
I think there are some things enabled on kernel side which is not present in omni device tree. Like Zram or ksm for example.
[HELP]
Is this kernel compatible with Resurrection Remox or Oxygen OS based ROMs?
Thank you
anuroop_nandi said:
Is this kernel compatible with Resurrection Remox or Oxygen OS based ROMs?
Thank you
Click to expand...
Click to collapse
No.
demeez said:
I'm currently testing out your kernel on omni and it's running pretty nice. Running Hawktail 1.2 governor with greenify and naptime. I've been out most of the day, mostly using data, bluetooth's been on for the past 4 hours with spotify playing for about half of that, 3 hours SOT and I still have about 25% battery left.
Click to expand...
Click to collapse
Hey everyone, thanks for this
I just wanted to find out do you flash the kernel after installing the ROM or before. i have tried flashing it afterwards but it just restarts
I'm running Omni ROM 8.1 for ether
dr_vaice said:
Hey everyone, thanks for this
I just wanted to find out do you flash the kernel after installing the ROM or before. i have tried flashing it afterwards but it just restarts
I'm running Omni ROM 8.1 for ether
Click to expand...
Click to collapse
A. After.
B. This is for Omni 7.1 not Oreo.
Hello,
I flashed this kernel, but I am facing some issues.
So firstly I don't have any backup, I flashed this kernel and then accidentally wiped system storage and data. Then tried to connect it to my laptop to transfer ROM files ( which connects as MTP device usually ), but the laptop is not able to detect the phone ( Unknown device ). I tried to use almost all the drivers available online, only to face failure. Tried using USB-OTG, even that isn't getting detected ( expected ).
Now I am stuck at TWRP Recovery, neither able to flash a ROM, nor flash the stock kernel.
Please help me out, I have no clue how to proceed further.
Thanks
A noob trying to learn.
Related
To God be the glory, It is finally here: Android N kernels!
@malacore had a good suggestion for me to get started on my AKLU kernels while I wait for more ram for my computer to make my own N builds. I started with JDCTeams's CM14, and hope to branch out to AOSP and others soon.
Feel free to comment if you have tried them on another rom, successful or not, or to leave feedback on these kernels as well. These can be flashed on any JF variant of phone, but I have only personally tested them on JFLTETMO.
Post #2: N kernels
Source: https://github.com/alaskalinuxuser/
Kernel Version 3.4.112
Post created: 11/02/16
Last updated: 9/5/17
Nougat kernels!
For AOKP 7:
(AOKP is now based on LineageOS)
https://www.mediafire.com/folder/h3p473al6xstx/kernels
For SlimRoms 7:
http://www.mediafire.com/file/s3v49439d9k5k1e/AKLU-SLIM-N-JFLTE-intelliplug-20170117.zip
For LineageOS 14.1:
http://www.mediafire.com/file/305w1rnap7qj2he/AKLU-LINEAGEOS-N-JFLTE-intelliplug-20160112.zip
For RR 5.8.0:
(RR is now based on LineageOS)
http://www.mediafire.com/file/0nq9p5qq5mx9q8u/AKLU-RR580-N-JFLTE-UPDATE-20170126.zip
For CM14 by the JDCTeam:
http://www.mediafire.com/file/9z097f1aox8pguu/AKLU-CM14-N-JFLTE-iosched-20161110.zip
Change Log:
20170619
-Added Faux Sound! Thanks @faux123
-Added fast charge!
20170524
-Added GPU and CPU voltage controls!
--> Control the CPU through Kernel Adiutor
--> Control the GPU with my GPU Voltage Control App.
https://forum.xda-developers.com/ga...gpu-voltage-control-app-aklu-kernels-t3506985
20170425
-Updated for 7.1.2 compatibility.
20170315
-Update for Substratum compatibility.
20170126
-Fixed WiFi hot-spot issue for AOKP and RR.
20170115
-Updated RR and AOKP kernel with LineageOS base, as they transitioned away from CM.
20161222
+ Added Intelliplug, an alternative hotplugging option made by @faux123.
20161220
+ No feature changes, just cleaning up a few things to help with RR 5.8.0
20161110
+ Added I/O Schedulers:
-->FIOPS
-->SIO
-->VR
20161102
+ Overclocked CPU to 1998 MHz.
+ Overclocked GPU to 487 MHz.
+ Added Governors:
-->SmartMax
-->Wheatley
-->LionHeart
Old Kernels:
http://www.mediafire.com/file/rzt412chq67b3av/AKLU-JFLTE-AOKP-N-20170425.zip
Screenshots!
Some screenshots of Kernel Aduitor with these kernels.
Awesome gonna give it a go and see but I'm sure will run/perform just fine
sent from my SGH-M919 BadAss TinkerToy
---------- Post added at 04:26 PM ---------- Previous post was at 04:09 PM ----------
have u tested with systemless root does it play nice the marshmallow dev worked great just wondering since supersu patches boot.img but I'll test it incase and let u know
sent from my SGH-M919 BadAss TinkerToy
Kernel seems to run fine I noticed no fauxsound or fast charge. Also didn't have all the same governors as other kernels u have. Web apps ran laggy but I think that's something with that rom. Also noticed on boot unlike ur marshmallow dev kernel it show not selinux enforcing. currently back on marshmallow it says only about kernel. Why is that on marshmallow it says permissive when full booted under about phone. I wonder if it's some flag or something supersu patches on marshmallow dev that it can't or isn't patching on the nought kernel. Because both ur rom and cm14.1 are both showing permissive fully booted under about phone with me changing nothing. Even ran getenforce to make sure.
sent from my SGH-M919 BadAss TinkerToy
dtriguero said:
Kernel seems to run fine I noticed no fauxsound or fast charge. Also didn't have all the same governors as other kernels u have. Web apps ran laggy but I think that's something with that rom. Also noticed on boot unlike ur marshmallow dev kernel it show not selinux enforcing. currently back on marshmallow it says only about kernel. Why is that on marshmallow it says permissive when full booted under about phone. I wonder if it's some flag or something supersu patches on marshmallow dev that it can't or isn't patching on the nought kernel. Because both ur rom and cm14.1 are both showing permissive fully booted under about phone with me changing nothing. Even ran getenforce to make sure.
sent from my SGH-M919 BadAss TinkerToy
Click to expand...
Click to collapse
Yes, I am still adding features, so fast charge, fauxsound, etc., are not added yet. Also it is not set to permissive when I made it for their ROM, because their default was enforcing. I can make it default permissive if needed when I make more adjustments. It is somewhat difficult working within their ROM to make my own kernel, so it will take some time to get all of the features put in.
that's funny cause the nought one boots with two errors on sammy logo not seandroid enforcing I think and kernel warranty bit as if is permissive but when boot mm dev kernel only shows kernel warranty bit on sammy screen as if enforcing during boot but permissive when finished boot. Also N shows permissive but did flash supersu before booting maybe it changed it. Steps was
Full wide-after backup of course
flash cm14.1
flash 7.1 micro gapps
flash ur N kernel
flash supersu 2.78 sr3- there rom flash 2.78 sr1
sent from my SGH-M919 BadAss TinkerToy
For now I am satisfied with Alucard kernel in OotCM14 but I'll be keeping an eye on this thread to see how things developed.
I do have one question, is your kernel based on stock cm kernel or Alucard?
Sent from my SGH-M919 using Tapatalk
Xplorer4x4 said:
For now I am satisfied with Alucard kernel in OotCM14 but I'll be keeping an eye on this thread to see how things developed.
I do have one question, is your kernel based on stock cm kernel or Alucard?
Click to expand...
Click to collapse
No worries!
Yes, my kernel is based on stock CM kernel. Alucard kernels are great, I have a lot of respect for Alucard kernels.
AlaskaLinuxUser said:
For CM14 by the JDCTeam:
http://www.mediafire.com/file/9z097f1aox8pguu/AKLU-CM14-N-JFLTE-iosched-20161110.zip
For AOKP 7:
http://www.mediafire.com/file/znzpjieflvb7q9r/AKLU-AOKP-N-JFLTE-iosched-20161110.zip
Change Log:
20161110
+ Added I/O Schedulers:
-->FIOPS
-->SIO
-->VR
Click to expand...
Click to collapse
To God be the glory, another successful addition to the N kernel! Just added a few I/O schedulers.
i see you are making kernels for aokp 7. i am wondering is there even an aokp 7 for us yet and if so where can i test it
gizm0luvsu said:
i see you are making kernels for aokp 7. i am wondering is there even an aokp 7 for us yet and if so where can i test it
Click to expand...
Click to collapse
I am guessing it was a typo and he meant aosp not aosp. No aokp rom yet that I know of.
Sent from my Pixel using Tapatalk
gizm0luvsu said:
i see you are making kernels for aokp 7. i am wondering is there even an aokp 7 for us yet and if so where can i test it
Click to expand...
Click to collapse
Xplorer4x4 said:
I am guessing it was a typo and he meant aosp not aosp. No aokp rom yet that I know of.
Click to expand...
Click to collapse
Actually, there is an AOKP 7.0 teaser download in the AOKP MM thread. No working calls yet.
AlaskaLinuxUser said:
Actually, there is an AOKP 7.0 teaser download in the AOKP MM thread. No working calls yet.
Click to expand...
Click to collapse
ahhh ok
Will u be adding all the goodies u had in ur MM Dev kernel to ur aokp N kernel
dtriguero said:
Will u be adding all the goodies u had in ur MM Dev kernel to ur aokp N kernel
Click to expand...
Click to collapse
Great question!
Yes, I plan to do that eventually, it may take me a while. There are some other pressing phone items that I need to fix first.
For some reason I tried flashing your aokp kernel on your new build and boot indefinitely. Could be me
smartt699 said:
For some reason I tried flashing your aokp kernel on your new build and boot indefinitely. Could be me
Click to expand...
Click to collapse
Hmmm... It did test good here. However, I let AOKP N boot fully, then went back to recovery and flashed this kernel.
However, I have updated it, so try the new one in the OP, if you would. It also tests good here. When flashing, it gave me an error, but still flashes just fine. The error is about the syntax of the META-INF file, not a kernel problem.
Let me know how if you have any more problems. I did not have GAPPS installed when I tested this, just for reference.
Praise God, new kernel is up!
Hey guys, just wanted to let you know that the OP is updated with the new kernel, including intelliplug, an alternative to mpdecision for hotplugging. This controls how many cores are used at once. You have to use Kernel Adiutor or some similar app to control it. Intelliplug has several options that show up in the Kernel Adiutor as well. Let me know what you think!
hi there is a procedure to install this kernel on RR ( like wipe cache), because i tried an get a bootloop
Hi oneplus2 people!
This is my modified kernel with some kernel optimizations and some compiler optimizations.
The goal of abyss is to achieve improved performance/battery without the cost of stability.
I will not be overhauling this project with changes that are not logical to add.
This kernel should work on the latest 7.x.x roms like CyanogenMod.
It might work on other roms, but there will be little support for them.
How does one achieve this?
- build kernel with an optimized toolchain
- use compiler optimization flags (experimental)
- remove redundant code
- improve existing code with more efficient code
- etc. (most are not so easy to explain)
This kernel is built with mdalexca's latest UBER GCC 4.9.
Is there actually a performance improvement?
With all the changes added up, there should be. Whether or not one notices the difference is another thing.
For those interested in how the kernel optimizations will benefit/work, please look at my github source and read the commit messages.
For those interested in how the compiler optimizations/hacks will benefit/work, please look at this article.
Downloads:
Latest release
BasketBuild
Source:
GitHub
This was made by request from dsst22 who also tested this bad boi like crazy.
XDA:DevDB Information
abyss kernel for the OnePlus 2, Kernel for the OnePlus 2
Contributors
kwoktopus, dsst22, OnePlus, grarak, The Flash, arter97, Lord Boeffla, frap129, Linux, Google, CAF, a bunch of other major OEMs
Source Code: https://github.com/abyss-kernels/oneplus2
Kernel Special Features:
Version Information
Status: Nightly
Current Stable Version: 1.20
Stable Release Date: 2016-12-05
Created 2016-12-05
Last Updated 2016-12-13
Key Changes:
- upstream interactive governor (with Flash 1.0 profile by The Flash) (Google and CAF)
- upstream cpufreq driver (Google and CAF)
- upstream cpu-boost driver (Google and CAF)
- upstream random driver from Linux 4.1.31 (performance..!)
- slub/slab/slob/vmalloc patches
- flar2's slightly modified thermal driver
- using Linaro's power efficient workqueues throughout kernel
- using Adreno idler by arter97 to reduce frequency scaling without performance cost
- using power efficient "relaxed" macros throughout kernel (assembler)
- KCAL Control Driver by Savoca
- Android-Keyboard patch, use your device as an external keyboard!
- too many to list here, check out my source
How to install:
Place zip in to your internal storage
Place current ROM zip on to your storage
Boot into TWRP recovery
(If you're coming from a different kernel, dirty flash current ROM)
Flash kernel zip
Reboot
Don't like the defaults?
Use Kernel Adiutor to change the settings!
Frequently Asked Questions:
Is this a custom kernel?
I was asked this question once, and it posed as a real good question. I do not consider abyss to be a "custom kernel" per se, but more so as a modified kernel. The patches and features that go into this kernel do not make it customizable. What they do is improve what has already been implemented. It is like swapping a car's engine for a better one rather than just adding LED flooring lights and fancy car mats.
Can you add [this] and [that] feature?
Something I pride myself with this kernel is that it does not have a bunch of random, useless features or patches mashed into it. Everything put into this kernel is thought out and tested. I see a lot of works being made popular because it has [this] and [that] feature when really, it's nothing revolutionary. As a matter of fact, most things added to any kernel will not make it 5x better than any other kernel. Most of the time, simple is better; and in this case it definitely is!
For me
Thanks! I'll give it a go.
Giving it a go
Yess! Been waiting for this ever since i saw your OP2 repo!
Does this kernel install on a f2fs formatted system?
suraj.das said:
Yess! Been waiting for this ever since i saw your OP2 repo!
Click to expand...
Click to collapse
You can thank @dsst22 for helping with testing, or else you would have waited a very long time :silly:
socialdistortion said:
Does this kernel install on a f2fs formatted system?
Click to expand...
Click to collapse
I have not made any file system changes to the kernel. If the stock CM kernel supports, then this one will too.
Is kcal support present..??
chl1810 said:
Is kcal support present..??
Click to expand...
Click to collapse
unfortunately no.
good to see new kernel for our device, thanks and good luck
suraj.das said:
unfortunately no.
Click to expand...
Click to collapse
I wish it had
chl1810 said:
I wish it had
Click to expand...
Click to collapse
I can remember the YoshiShaPow falcon kernel
chl1810 said:
I wish it had
Click to expand...
Click to collapse
In the future
PeterImmel said:
I can remember the YoshiShaPow falcon kernel
Click to expand...
Click to collapse
You can probably see how much I've grown as a developer since then too :angel:
Works on a f2fs filesystem based rom. Testing it now...
Edit: No obvious bugs at the moment. Is it possible to implement some sort of charging control. The USB charging speed is super slow (on both this kernel and stock CM kernel).
kwoktopus said:
In the future
Click to expand...
Click to collapse
Nice!! thank you!!
Pretty smooth haven't found any bugs. Love the simplicity.
I can't imagine what it would be like with a little over clock.
adame09 said:
Pretty smooth haven't found any bugs. Love the simplicity.
I can't imagine what it would be like with a little over clock.
Click to expand...
Click to collapse
I trust the engineers that designed the chip to choose a safe maximum clock speed. Here's a pretty good article on the risks vs benefits, which outline some strong points.
But, if I were to add it, I would set the max value at boot to stay as stock values; so I'll leave it up to @dsst22 to decide.
I'll try this out for you dude. Impressive what you've done.
Hi OnePlus 5 peeps!
Today (June 27th), I graduated from high school!
In more important news, I finished upstreaming the OnePlus 5 kernel to the latest stable kernel version...
Whoa, what is this?
This is my personal kernel that I run as the OnePlus 5 is my daily driver.
I will not claim my work as the best at anything, but just know that I would not do anything to this kernel that could potentially ruin my own device.
Additionally, this is the kernel that comes built into CarbonROM.
There are three versions of this kernel:
AOSP aka AOSP/LOS build - Flash this on any source built custom ROM except for CarbonROM
CR-5.1 aka CarbonROM build - Flash this on CarbonROM
OOS aka OxygenOS build - Flash this version on OxygenOS
Main features:
Upstreamed Linux kernel version, went from v4.4.21 -> v4.4.79
Backported random driver from Linux v4.12 (latest and greatest)
Backported scheduler from Linux v4.9 (latest android kernel branch)
Upstreamed F2FS driver from f2fs-stable/linux-4.4.y
KGSL driver improvements
MDSS driver improvements
SOC driver improvements
Built using Optimization Level 2
Added maple io scheduler (default) by frap129
Added adreno idler by arter97 with tweaks from frap129
Vibrator motor control by flar2
Kcal control driver from EX kernel
Many wakelocks disabled
Switched to power efficient workqueues across the kernel
Built with Google's latest stable gcc-4.9
Anykernel 2.0 by osm0sis! Compatible with all OxygenOS based roms
Download:
Latest builds
OxygenOS boot.img
How to install:
1. Reboot into the latest stable TWRP build
2. Download kernel zip and make sure it is in your internal storage (/sdcard)
3. Reboot into TWRP
4. Double check here to see if you require any additional instructions
5a. Install -> Install image -> select oxygen-4.x.x-boot.img -> swipe to install
5b. Install -> select CarboniteKERNEL-XXX-Rx-OP5-N.zip -> swipe to install
6. Reboot
DISCLAIMER!
If you don't understand my instructions, that's too bad >
If you are unsure about what this thing is, I highly advise you do some research before going through with installing...
Updates will come as regular as I want them to, don't ask me when I'll release cause you'll know when it comes out >:'D
XDA:DevDB Information
CarboniteKERNEL for the OnePlus 5, Kernel for the OnePlus 5
Contributors
adinkwok, nathanchance, flar2, Lord Boeffla, osm0sis, etc
Source Code: https://github.com/adinkwok/oneplus5-kernel
Kernel Special Features: One of Taylor Swift's exes should write a song called "Maybe You're the Problem"
Version Information
Status: Testing
Created 2017-06-28
Last Updated 2017-08-02
While this reserved post is not being used, enjoy this video! (Find me at 0:50s and twice at 2:54 :silly
For OxygenOS users:
Code:
[B]If you are on OxygenOS and are coming from another custom kernel:[/B]
Download the latest stock.4.X.X-boot.img
You [B]must[/B] flash the boot.img before flashing the kernel!
[B]If you are on OxygenOS are switching to a different custom kernel:[/B]
Download the latest stock.4.X.X-boot.img
You [B]must[/B] flash the boot.img before switching kernels!
For AOSP/LOS/RR/etc users:
Code:
[B]If you are coming from another custom kernel:[/B]
You [B]must[/B] reflash your ROM build before flashing this kernel!
[B]If you are on AOSP/LOS/RR/etc and are switching to another custom kernel:[/B]
You [B]must[/B] reflash your ROM build before flashing another kernel!
Why is it like this?
I have included some ramdisk modifications that set the default settings for this kernel. When you come from a different custom kernel, the ramdisk changes from that kernel may conflict with the changes I intend to have. Likewise when you switch to a different kernel; my ramdisk changes may conflict with the changes they intend to have. When you flash the stock boot.img, it replaces the modified ramdisk with a clean one, removing these conflicts.
And it's here, get it while it's hot folks! First upstreamed kernel for the OP5
Thanks for joining the party :highfive:
Sent from my OnePlus5 using XDA Labs
gz on graduating! and thx for the kernel :=
Congratulations on the graduation buddy,
Just flashed and I had charging cycling on and off (using dash charger in car on freedom v1.1). Flashed EX and charging is fine. Need charge ATM but maybe a little later I can help you get a log.
Sent from my OnePlus5 using XDA Labs
congratulations! awesome... so smart!!!!!!!
rav101 said:
Congratulations on the graduation buddy,
Just flashed and I had charging cycling on and off (using dash charger in car on freedom v1.1). Flashed EX and charging is fine. Need charge ATM but maybe a little later I can help you get a log.
Sent from my OnePlus5 using XDA Labs
Click to expand...
Click to collapse
Hmmm never noticed this... I guess the graduation drinks are getting to me. I'll re-upload a stable build without upstreaming as that's definitely the culprit.
What an amazing day for you (Congratulations!) and the OP5 community!
I was really loving and enyoing all your efforts you did for the OPO (Pure Nexus port) and the amazing Carbon ROM.
adinkwok said:
Hmmm never noticed this... I guess the graduation drinks are getting to me. I'll re-upload a stable build without upstreaming as that's definitely the culprit.
Click to expand...
Click to collapse
I'm the first to report so let's see if anyone else has the same issue. I will also try for logs later on though I do have a lot on today (so might be this evening).
I didn't actually reboot or get to try a different charger to help diagnose so don't want you doing more work that you need to for what could me my issue
Sent from my OnePlus5 using XDA Labs
rav101 said:
I'm the first to report so let's see if anyone else has the same issue. I will also try for logs later on though I do have a lot on today (so might be this evening).
I didn't actually reboot or get to try a different charger to help diagnose so don't want you doing more work that you need to for what could me my issue
Click to expand...
Click to collapse
I can confirm the issue because while I was bringing up the upstream branch I ran into this issue with dash charging and I thought I solved it. Time to debug!
Edit: link updated without the upstreaming, everything else still stands though
adinkwok said:
I can confirm the issue because while I was bringing up the upstream branch I ran into this issue with dash charging and I thought I solved it. Time to debug!
Edit: link updated without the upstreaming, everything else still stands though
Click to expand...
Click to collapse
No problem buddy,
Be good once it's all resolved and we have the benefits of upstream kernel code as well!! Your time and effort is appreciated!
Sent from my OnePlus5 using XDA Labs
@rav101 happy to see u around buddy
dukat0s said:
@rav101 happy to see u around buddy
Click to expand...
Click to collapse
For sure my friend.
How you finding the OP5?
Sent from my OnePlus5 using XDA Labs
rav101 said:
For sure my friend.
How you finding the OP5?
Click to expand...
Click to collapse
Cool my friend !like it.just got rid of my s8+. Was bored
Is DT2W working for you guys?
bartelamo said:
Is DT2W working for you guys?
Click to expand...
Click to collapse
Seems to be a problem among a few custom built kernels, we're looking into it.
bartelamo said:
Is DT2W working for you guys?
Click to expand...
Click to collapse
adinkwok said:
Seems to be a problem among a few custom built kernels, we're looking into it.
Click to expand...
Click to collapse
It's because OOS has a hal that already uses a switch for dt2w.
New update, still looking into the gestures issue.
However, Dash Charging is fixed on the upstream kernel so here it finally is! I also added a bunch of sched patches, a thermal patch, and some other misc stuff from the latest CAF branch.
Adin-Kernel-R2-OP5-OOS-N.zip
Linux 3.10-based kernel for Oneplus One (bacon)
Info:
use this kernel at your own risk. Flashing it the wrong way might brick your device. I'm not responsible for any software/hardware damage.
This kernel is based on top of erorcun's 3.10 kernel. erorcun has spent an enormous time working on this project and he deserves a huge "Thank you" for having succeeded in one of the most difficult tasks in Android development: upgrading a device to a newer Linux release.
Features:
v3 (12th December)
built with O3 optimizations
CAF CPU boosting driver (replaces cpu_input_boost - might be a temporary switch)
kernel code base updated to Linux 3.10.60
sdcardfs updates
minor miscellaneous improvements
old releases:
v2.1
minor stability fix
v2 (12th November)
kernel code base updates reverted, then re-applied only up to 3.10.54
compiled with an improved set of GCC flags
tuned AIO for SSD-only machines
v1 (30th October)
built with GCC 5, UBER Toolchain and the optimal compiler flags for Krait CPUs
kernel code base upgraded to Linux 3.10.88
power-efficient workqueues
sound control by francisconfranco
CPU voltage control
cpu_input_boost by Sultanxda
sdcardfs & f2fs support
support for both LineageOS's and Sultan's camera HALs
Compatibility
The kernel is compatible with all the Marshmallow/Nougat ROMs that use either LineageOS's camera HAL or Sultan's (a.k.a. CAF's). Just make sure you download the right version
Currently, the kernel has been tested only on LineageOS 14.1, but I'm sure the CAF build is safe to flash and works properly as well.
The kernel doesn't work on Oreo (yet)!
Download
The kernel can be download from AFH: 3.10 kernel on AndroidFileHost
Thanks to:
erorcun, franciscofranco, Sultanxda, CAF & UBER, Mecca EL.
XDA:DevDB Information
Tom's Linux 3.10 kernel, Kernel for the OnePlus One
Contributors
Tomoms, erorcun
Source Code: https://github.com/Tomoms/neon_kernel_bacon
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: 3.0
Stable Release Date: 2017-12-12
Created 2017-10-30
Last Updated 2017-12-12
thanks man! any plans on oreo version?
criminality said:
thanks man! any plans on oreo version?
Click to expand...
Click to collapse
Everything will come in due time
It's one of the things I'll work on soon. Be patient, and you'll eventually get what you want
Thank you for this.
Don't know if it's your Lineage rom or this kernel, but video that i record is really stuttery. Like very janky.
I recorded the video with the build-in snap camera.
Fatsodonkey said:
Thank you for this.
Don't know if it's your Lineage rom or this kernel, but video that i record is really stuttery. Like very janky.
I recorded the video with the build-in snap camera.
Click to expand...
Click to collapse
Could you tell me the exact resolution you used?
Tomoms said:
Could you tell me the exact resolution you used?
Click to expand...
Click to collapse
Happens with all resolutions. I already tested Sultans Lineage as well with this kernel and the same thing happens. Don't know if it tries to record it too fast as it seems to be too quick and stutters a lot.
The Los kernel seems to work fine with video recording altough i just dirty flashed it on top of Boefflas kernel.
E:It definetly is the kernel that is causing the stutter.
Fatsodonkey said:
Happens with all resolutions. I already tested Sultans Lineage as well with this kernel and the same thing happens. Don't know if it tries to record it too fast as it seems to be too quick and stutters a lot.
The Los kernel seems to work fine with video recording altough i just dirty flashed it on top of Boefflas kernel.
E:It definetly is the kernel that is causing the stutter.
Click to expand...
Click to collapse
I'll compare the camera driver present in this kernel and the one in Sultan's kernel, then try to fix this. Unfortunately at the moment this is the best thing we can achieve, CAF camera support had always got some small problems even in erorcun's build if I recall correctly, and these problems are inevitably "inherited" by my kernel.
Thank you for working on this, I was looking forward to release since I saw your announcement in erorcun's thread.
Firstly i tried to dirty flash kernel on top of LineageOS build (N) by idprophecy, since i got positive experience changing kernels (3.4 ones) this way even with encrypted phone. So when i tried to boot up with new kernel, unfortunately it did not work and phone says my password is correct but encryption partition is broken and i need to hard reset.
I went to clean install, removed encryption and flash same LinOS build + your kernel. Then i encrypted phone again and everything went fine. However now my TWRP refuses password for decrypting partitions (its was like that in early N development for bacon on many roms).
Overall perfomance is not really smooth comparing with 3.4 kernels, but i didnt bothered to play with kernel setting.
Also i cant get MTP working, phone only charging via usb and PC (Windows) cannot see its memory.
I know this report is probably useless without kmsg logs, but i didnt have time to pull them off, so sorry about that. I try do it later
TbMa said:
Thank you for working on this, I was looking forward to release since I saw your announcement in erorcun's thread.
Firstly i tried to dirty flash kernel on top of LineageOS build (N) by idprophecy, since i got positive experience changing kernels (3.4 ones) this way even with encrypted phone. So when i tried to boot up with new kernel, unfortunately it did not work and phone says my password is correct but encryption partition is broken and i need to hard reset.
I went to clean install, removed encryption and flash same LinOS build + your kernel. Then i encrypted phone again and everything went fine. However now my TWRP refuses password for decrypting partitions (its was like that in early N development for bacon on many roms).
Overall perfomance is not really smooth comparing with 3.4 kernels, but i didnt bothered to play with kernel setting.
Also i cant get MTP working, phone only charging via usb and PC (Windows) cannot see its memory.
I know this report is probably useless without kmsg logs, but i didnt have time to pull them off, so sorry about that. I try do it later
Click to expand...
Click to collapse
Definitely would need a log, to see what the issue is, with your experiences.
I've been alpha and beta testing this kernel, and I'm not experiencing any of the problems you and other users are describing. Clean install @idprophecy LOS14.1, flash this kernel, reboot back to recovery and flash MagiskSU, enjoy an ultra responsive OPO.
TbMa said:
Thank you for working on this, I was looking forward to release since I saw your announcement in erorcun's thread.
Firstly i tried to dirty flash kernel on top of LineageOS build (N) by idprophecy, since i got positive experience changing kernels (3.4 ones) this way even with encrypted phone. So when i tried to boot up with new kernel, unfortunately it did not work and phone says my password is correct but encryption partition is broken and i need to hard reset.
I went to clean install, removed encryption and flash same LinOS build + your kernel. Then i encrypted phone again and everything went fine. However now my TWRP refuses password for decrypting partitions (its was like that in early N development for bacon on many roms).
Overall perfomance is not really smooth comparing with 3.4 kernels, but i didnt bothered to play with kernel setting.
Also i cant get MTP working, phone only charging via usb and PC (Windows) cannot see its memory.
I know this report is probably useless without kmsg logs, but i didnt have time to pull them off, so sorry about that. I try do it later
Click to expand...
Click to collapse
I faced the same MTP problem when I started developing this kernel several months ago. But I'm sure it appeared at a later stage of development. So MTP shouldn't be an issue as of now. Also, according to @Mecca EL, there should be a substantial performance improvement.
Mecca EL said:
Definitely would need a log, to see what the issue is, with your experiences.
I've been alpha and beta testing this kernel, and I'm not experiencing any of the problems you and other users are describing. Clean install @idprophecy LOS14.1, flash this kernel, reboot back to recovery and flash MagiskSU, enjoy an ultra responsive OPO.
Click to expand...
Click to collapse
So can you confirm MTP is working on this kernel? What about video recording? Is it lagging or not? I still haven't had enough time to thoroughly try my own kernel :/
Thank you.
Mecca EL said:
Definitely would need a log, to see what the issue is, with your experiences.
I've been alpha and beta testing this kernel, and I'm not experiencing any of the problems you and other users are describing. Clean install @idprophecy LOS14.1, flash this kernel, reboot back to recovery and flash MagiskSU, enjoy an ultra responsive OPO.
Click to expand...
Click to collapse
What about encryption? Are your TWRP able to decrypt data with this kernel?
Tomoms said:
I faced the same MTP problem when I started developing this kernel several months ago. But I'm sure it appeared at a later stage of development. So MTP shouldn't be an issue as of now. Also, according to @Mecca EL, there should be a substantial performance improvement.
So can you confirm MTP is working on this kernel? What about video recording? Is it lagging or not? I still haven't had enough time to thoroughly try my own kernel :/
Thank you.
Click to expand...
Click to collapse
I'll double check, and do a complete run down on this latest one, in case it differs from the last one you sent me.
---------- Post added at 08:56 AM ---------- Previous post was at 08:53 AM ----------
TbMa said:
What about encryption? Are your TWRP able to decrypt data with this kernel?
Click to expand...
Click to collapse
I've not set encryption. I've seen way too many problems with that across almost all android devices. I'll see if it's not too much trouble to set and test for you, if I'm able to revert to unencrypted easily.
Mecca EL said:
I'll double check, and do a complete run down on this latest one, in case it differs from the last one you sent me.
---------- Post added at 08:56 AM ---------- Previous post was at 08:53 AM ----------
I've not set encryption. I've seen way too many problems with that across almost all android devices. I'll see if it's not too much trouble to set and test for you, if I'm able to revert to unencrypted easily.
Click to expand...
Click to collapse
Well i am using encryption since early MM and not a single problem if developer of rom and kernel did his work fine. Biggest payoff its hit battery.
Unfortunately you cant revert encryption without formating whole internal storage, so its a little bit complicated with backups and etc
MTP is not working for me either, I'm using the CAF kernel on LineageOS by Sultan.
SirSoviet said:
MTP is not working for me either, I'm using the CAF kernel on LineageOS by Sultan.
Click to expand...
Click to collapse
Thanks for your feedback, I'll do my best to fix this issue as soon as possible. Do you face the video recording issue?
Tomoms said:
Thanks for your feedback, I'll do my best to fix this issue as soon as possible. Do you face the video recording issue?
Click to expand...
Click to collapse
I never record videos, so I don't know. I'll check later today.
@Tomoms ,just a heads up: kernel works fine with Marshmallow(los13).
Mr.Ak said:
@Tomoms ,just a heads up: kernel works fine with Marshmallow(los13).
Click to expand...
Click to collapse
Thank you for letting me know. I'll immediately update the thread.
SirSoviet said:
I never record videos, so I don't know. I'll check later today.
Click to expand...
Click to collapse
Nothing wrong with video recording here.
SirSoviet said:
Nothing wrong with video recording here.
Click to expand...
Click to collapse
Hmm... I'll try it myself soon. In the meantime, my main concern will be fixing MTP, and it won't take me too much, fortunately.
Buffcore oreo kernelSamsung Galaxy S4 i9505 (jfltexx)Release 02 - 11th June 2018
Code:
#include
/*
* Your warranty is now void.
* And other random stuff no-one reads.
*/
Intro
I had never intended releasing this as a stand alone, but had always been aware that it would work.
With BB and Side both being busy and AOSP and OptLos stalling for a bit, the kernel from RR-oreo should I think help a bit to alleviate users battery issues.
What is it?
Buffcore 2.04 - this is a fork of BB's AOSP 8.1 kernel with added fastcharge and battery saving features.
It is the kernel supplied with RR-o release 2, so isn't needed for RR users.
Code:
renamed to buffcore;
sdfat enabled;
fastcharge implemented for faster charging (up to 1900 ac / 1000 usb);
bcmhd wakelocks for rx and tx halved;
libmemcopy and libstring sped up;
io readahead to 1024k;
lower min cpu governor frequency (270);
power efficient work queues;
voltage tweaking user interface;
faster vmstat;
autosmp hotplugging replacement;
mmc crc disabled;
allow for lower cpu voltage;
reduce swapiness;
optimise divide / multiply by power of 2;
added tcp optimisation options,;
set westwood default;
force doze screen off helper;
optimise cbfillrect function;
reduce wifi wakelock times;
nohz: reduce overhead under high-freq idling patterns.
What rom is it for?
BB's AOSP oreo
Side's OptLos 15.1
Installation
Dirty (use with current rom flash)
Extract the boot.img file from the zip (It is not a flashable zip!).
Reboot rom into twrp.
Perform a nandroid backup to be safe, incase you need to go back.
Go into Install, then select Install Image for Buffcore kernel.
Reinstall your prefered root solution (Magisk, etc).
Do not wipe caches.
Reboot.
Clean (flash as part of clean install)
Extract the boot.img file from the zip (It is not a flashable zip!).
Reboot rom into twrp.
Perform a nandroid backup to be safe, incase you need to go back.
Perform clean recomended in your rom thread.
Install rom.
Go into Install, then select Install Image for Buffcore kernel.
Reinstall your prefered root solution (Magisk, etc)
Install Gapps.
Do not wipe caches.
Reboot.
Usage
Some features will need to be forced on (IF desired) and set to apply on boot with an app like Kernel Aduitor, EXKM etc. (Fastcharge, Min cpu frquency used, Power efficient work queues, Voltage tweaking, AutoSMP hotplugging).
This kernel should / will not be compatible with stweaks.
There will essentially be no support with this, if it works then it works, or doesn't.
If it helps you then it helps you, if it doesn't tough, don't moan about it.
It has had a little testing with the roms it is intended, boots fine and seems to provide some benefit.
This may not get updated either - see it as a stop gap for the moment.
Thanks
Thanks due to Drrossum, Kesaras, CR4IGY_BOY for testing for me.
BB for original kernel and Side and TsvietOK for picks.
Download
Download from AFH here BUFFcore-o-2.04-release02-20180611.zip
md5sum - d2293a1e623ddcc68946dbea7ea12869
XDA:DevDB Information
BUFFcore-o, Kernel for the Samsung Galaxy S4
Contributors
Buff99, side
Source Code: https://github.com/Buff99/platform_kernel_samsung_jf/tree/aosp-8.1
Kernel Special Features: Fastcharge, battery saving features
Version Information
Status: No Longer Updated
Created 2018-06-18
Last Updated 2018-09-13
Reserved
might as well have one, won't be writing much tho....
Very well done, master!
Perfect. I guess it's my new optlos main kernel
side said:
Perfect. I guess it's my new optlos main kernel
Click to expand...
Click to collapse
Of course, we work better and smarter together.
Since Kernels are/should be backward compatible, any reason why this shouldn't work with RR Marshmallow?
Thx!
<CuriousCat> said:
Since Kernels are/should be backward compatible, any reason why this shouldn't work with RR Marshmallow?
Thx!
Click to expand...
Click to collapse
Backwards compatibility with kernels? Not guaranteed that I know of.
When Oreo kernels use 64 bit binder, it locks out use with ROMs that don't have 64 bit binder defined.
You'd be better trying a sidecore kernel for nougat as an intermediate, if it works then try this. A kernel flash that doesn't work should be easy to recover from if have you stock one on hand ready to reflash. Remember that any mod / root that patches the kernel will need reflash.
SideCore kernel is a no go. A stock RR Nougat kernel also. Do you think some repacking with the boot.img of the RR Marshmallow would help?
<CuriousCat> said:
SideCore kernel is a no go. A stock RR Nougat kernel also. Do you think some repacking with the boot.img of the RR Marshmallow would help?
Click to expand...
Click to collapse
if they don't work, then this is a definite no-go.
I think RR marshmallow used the stock CM13.1 kernel, nothing was changed. Your viable choice would be anything cm13 compatible.
Syzrgy & Alucard spring to mind from back in the day.
Buff99 said:
if they don't work, then this is a definite no-go.
I think RR marshmallow used the stock CM13.1 kernel, nothing was changed. Your viable choice would be anything cm13 compatible.
Syzrgy & Alucard spring to mind from back in the day.
Click to expand...
Click to collapse
Alucard can't be found for MM and Synergy is very old (and not sure how stable).
Is there a way to take the (your/lineage) source and compile it to work with MM?
<CuriousCat> said:
Alucard can't be found for MM and Synergy is very old (and not sure how stable).
Is there a way to take the (your/lineage) source and compile it to work with MM?
Click to expand...
Click to collapse
just change the ramdisk using an image kitchen
side said:
just change the ramdisk using an image kitchen
Click to expand...
Click to collapse
I was thinking the same. Let me try.
Once repacked it boots but it's unstable. After running AnTuTu a few times it restarted every time. Not a good sign.
I flashed it several times on I9505 running the LOS15.1 and everytime I reboot after flash it shows the boot up screen with the phone model and then goes to Download mode. The fix for this non booting condition is to reflash the ROM.
Pecata01 said:
I flashed it several times on I9505 running the LOS15.1 and everytime I reboot after flash it shows the boot up screen with the phone model and then goes to Download mode. The fix for this non booting condition is to reflash the ROM.
Click to expand...
Click to collapse
Where is los15.1? Which rom u mean
I meant the Optimized Lineage OS 15.1 builds Version1 on which I tried to install BUFFcore-o rel02 kernel and it didn't work. But i flashed the Lineage OS 15.1 Version2 and it's all working. Good job
Is it possible to change the max frequency? Before compiling? Or manually with an root Explorer?
Just for fun
M4verick44 said:
Is it possible to change the max frequency? Before compiling? Or manually with an root Explorer?
Just for fun
Click to expand...
Click to collapse
aka overclock.
yes its possible.not suggested though.this thing is really advanced and i dont think that u will have nice results.wont be 'fun' at all
Can you add Boeffla Wakelock Blocker to this kernel? The Wi-Fi wakelocks are still annoying.
side said:
aka overclock.
yes its possible.not suggested though.this thing is really advanced and i dont think that u will have nice results.wont be 'fun' at all
Click to expand...
Click to collapse
Will you add over clocking to this kernel anytime soon? @side @Buff99?, maybe @ripee
---------- Post added at 05:34 PM ---------- Previous post was at 05:33 PM ----------
side said:
aka overclock.
yes its possible.not suggested though.this thing is really advanced and i dont think that u will have nice results.wont be 'fun' at all
Click to expand...
Click to collapse
Will you add over clocking to this kernel anytime soon? @side @Buff99?, maybe @ripee