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.
Related
Hi guys, only few words:
I'm working on a 3.10 kernel just for fun, i dunno if i'm able to make it stable.
If someone want to help any help is appreciated!
it's based on LA.BF.2.1.2_rb1.5 CAF branch
source code is here branch LA.BF.2.1.2_rb1.5 and test_usb
test boot.img is here: http://www58.zippyshare.com/v/eqVBaQhc/file.html
Working list:
- it boots!
- touch screen
- backlight
- sms and call
- audio
- Bluetooth
- NFC
- 3D Graphics
- adb
everything else is not working. use it with a usb cable plugged in or it will not work.
Major issue atm: it doesn't work without usb plugged in.
thanks to @myfluxi for his caf kernel & ROM
thanks to @Sultanxda for some suggestions
That's a good news! Maybe @myfluxi can help?
Inviato dal mio Nexus 5 CAF utilizzando Tapatalk
Very interesting project. I'll keep an eye on this. I'm also available as a tester if you want [emoji5]
Sent from my Nexus 5 using Tapatalk
Interesting.
How did you get past what this guy said?:
Sultanxda said:
Stopped working on it :/ I managed to get modem firmware to load (modem still doesn't work), but 3.10 as a whole has one big problem on the Nexus 5: proprietary TrustZone (TZ) firmware. 3.10 is much, much more reliant on TZ than our 3.4 kernel. 3.10 is so reliant on TZ that the CAF 3.10 branch does not boot with the latest PM (power-management) drivers (I had to use the 3.10 source from the LG G Watch as a base to get this completely booting). There are scm calls to TZ everywhere in 3.10, and in particular all versions of 3.10's PM code are broken to some extreme degree with our ancient firmware (kernel always crashes on CPU idle power collapse). I'm sure it's possible to make everything work with our firmware, but you'd likely need to know things that only Qualcomm engineers know, such as the actual internals of the TZ firmware to see where there are incompatibilities between TZ and the new kernel (TZ firmware source code is confidential/proprietary, so it is not available to the public).
Click to expand...
Click to collapse
nagalun said:
Interesting.
How did you get past what this guy said?:
Click to expand...
Click to collapse
probably because now CAF source has got more patches than 1 year ago! maybe they used patches that already were in lg smartwatch source, who knows... luckily now we have got a booting CAF kernel
Bluetooth seems to work just fine.
3D Graphics work as well.
NFC works too.
(Not sure about hw video decoding & GPS)
Lots of SELinux denials though.
nagalun said:
Bluetooth seems to work just fine.
3D Graphics work as well.
NFC works too.
(Not sure about hw video decoding & GPS)
Lots of SELinux denials though.
Click to expand...
Click to collapse
thanks for the tests, adding to OP
You should REALLY, REALLY get someone involved. This is gold.
Oh and you may find this helping, as we share the same SoC: http://forum.xda-developers.com/son...pment/unified-kernel-msm8974-devices-t2931858
I hope you get the help, collaboration and input you need to succeed!
3.10.x on N5? OMG Yeeees
Thanks for your work, but all my android devices till now had 3.4 kernel, can someone please tell me what are advantages of 3.10 kernel vs. 3.4 on a device like Nexus 5? Thanks.
Creative9170 said:
Thanks for your work, but all my android devices till now had 3.4 kernel, can someone please tell me what are advantages of 3.10 kernel vs. 3.4 on a device like Nexus 5? Thanks.
Click to expand...
Click to collapse
read from here to here, replace the kernel version in the url from 3.4 to 3.10 to get all improvements over the time. yes, backport features from 3.x/4.x to 3.4 will lower the gap between 3.4 and 3.10 but there's a motivation if newer devices use 3.10 instead backport stuff (caf will drop support for 3.4 sooner or later)
blackbird5308 said:
You should REALLY, REALLY get someone involved. This is gold.
Oh and you may find this helping, as we share the same SoC: http://forum.xda-developers.com/son...pment/unified-kernel-msm8974-devices-t2931858
Click to expand...
Click to collapse
i'll take a look
small update:
got adb working (using 3.4 driver), now it's easier to debug for everyone!
http://www58.zippyshare.com/v/eqVBaQhc/file.html
Hi. thx for your project. Maybe n5 users expect your 3.10.x kernel port even they can't write reply.
I test CM13-Caf 20160203.zip nightly with my girlfriend "D821 N5".
1.Rarely can't turn on lockscreen.(but screen was turned on)
-Maybe CM-Nightly's problem but no more happen after once happened.
2.Doesn't work 3g connetion
-I'm not use LTE,only 3g. Can't check LTE is working.
Before flashing kernel, network is working. Now Only work with UMTS. IMEI is fine. Network base is KT in South-Korea.
3.Wifi disconnect
-She don't recognize ip/mac address. Also can't find WIFI (2.4Ghz, 5Ghz)
4.Camera doesn't work.
-She have 3 eyes but only work 1 eye, Front Sensor.
Maybe you already know about it. I just nobody write about this problem in thread so I trying to write that problems.
Your 'Fun' gave us hope which n5 also have 3.10.x kernel. LOL
kwjhgjh said:
Hi. thx for your project. Maybe n5 users expect your 3.10.x kernel port even they can't write reply.
I test CM13-Caf 20160203.zip nightly with my girlfriend "D821 N5".
1.Rarely can't turn on lockscreen.(but screen was turned on)
-Maybe CM-Nightly's problem but no more happen after once happened.
2.Doesn't work 3g connetion
-I'm not use LTE,only 3g. Can't check LTE is working.
Before flashing kernel, network is working. Now Only work with UMTS. IMEI is fine. Network base is KT in South-Korea.
3.Wifi disconnect
-She don't recognize ip/mac address. Also can't find WIFI (2.4Ghz, 5Ghz)
4.Camera doesn't work.
-She have 3 eyes but only work 1 eye, Front Sensor.
Maybe you already know about it. I just nobody write about this problem in thread so I trying to write that problems.
Your 'Fun' gave us hope which n5 also have 3.10.x kernel. LOL
Click to expand...
Click to collapse
Hi!
I already knew that those things are broken, i'm working on it
rmbq said:
Hi!
I already knew that those things are broken, i'm working on it
Click to expand...
Click to collapse
Thx for q~~uick Reply. as i expect, feedback was too late kkk...
Have you ever think about next project which connect with N5 after this project is over?
AS you know, even this project is awesome but unfortunatly it's only work in CAF rom.
So I have curious when this project is over, what will you choose your next activiation.
Get more project like Build AOSP+CAF rom, More fix to work in AOSP, continue fixing this kernel.... or have rest times!
kwjhgjh said:
Thx for q~~uick Reply. as i expect, feedback was too late kkk...
Have you ever think about next project which connect with N5 after this project is over?
AS you know, even this project is awesome but unfortunatly it's only work in CAF rom.
So I have curious when this project is over, what will you choose your next activiation.
Get more project like Build AOSP+CAF rom, More fix to work in AOSP, continue fixing this kernel.... or have rest times!
Click to expand...
Click to collapse
after this project? sounds hilarious! my intention is to maintain CAF CM with 3.10 kernel, if i'll be able to make it stable
rmbq said:
after this project? sounds hilarious! my intention is to maintain CAF CM with 3.10 kernel, if i'll be able to make it stable
Click to expand...
Click to collapse
'hilarious' means...unfamiliar vocabulary to me, but enough to understand your purpose.
I think to consider my main rom as CM-Caf. Good luck to your project!
I'll waiting your work. d=_=b
@rmbq I flashed the Kernel built with your source. It booted fine, but as you mentioned in op, it rebooted the moment I disconnected from USB. Where do we go from here?
rachanta said:
@rmbq I flashed the Kernel built with your source. It booted fine, but as you mentioned in op, it rebooted the moment I disconnected from USB. Where do we go from here?
Click to expand...
Click to collapse
i don't know where is the problem atm, i don't think it's related to USB drivers, sultanxda said it's TZ related... it isn't easy to track, i saved a log with something more than "watchdog bytes". also i don't know if LA.BF.2.1.2 is a good base, some drivers (ex adreno) are older than LA.BF.1.1.3 (our caf 3.4)!! xperiadev are working on LA.BF64.1.2.2 also for msm8974 soc, that branch is very up to date but i can't get it boot on hammerhead, and i don't know if they can get it boot on xperia devices with msm8974 soc...
This release is only tested on the SM-T560NU USA (gtelwifiue).
This kernel is based on vince2678's port of LineageOS, with a couple of updates and optimizations.
This kernel has only been tested with vince's cm14.1 releases.
Flashable zips use a modified version of the AnyKernel2 system. While only tested on cm14.1, it may work on other ROMs, since it does not modify your initrd.
Very special thanks to vince2678.
Without his effort on this device, this release would not be possible.
Updates:
2017-06-10:
First build for CM14.1
Features:
DriveDroid Mass Storage and CD-ROM Support
Built with gcc-linaro-4.8-2015.06-x86_64_arm-eabi toolchain
Additional CPU optimizations
Updated CPU assembly optimizations
Various security patches
XPad (xbox 360 and xbox one) gamepad support
Known issues:
None
How to Install:
1. Download the latest release zip
2. Transfer zip to your device (or skip this step if sideloading)
3. Reboot into TWRP Recovery [Volume Up+Home] (If you need TWRP, first install mine or vince2678's.)
4a. Find the zip in the TWRP install browser, and install it
-OR-
4b. Sideload the zip using adb.
5. Reboot to system and enjoy
How much faster is it with the new optimizations?
Standard Kernel (click for full benchmark):
Noire Kernel (click for full benchmark):
What does "dirty" mean?
Whenever you modify a git repo and do not commit the changes, it will flag the kernel as "dirty".
Rather than forking the git repo, I use a clean copy of vince's repo, then apply my patches over it.
Because this isn't really how git was designed to be used, the build system sees it as "dirty".
It is nothing to worry about, as it is not harmful in any way.
Getting the kernel
Releases can be found on my site. (Check the header on the download page for a link to the source directory for tools to build your own):
https://files.persona.cc/zefie/files/cell/SM-T560NU/kernel/cm14.1
If/when there are more than one release, the most recent release should be on top, but verify the Last Modified date to be sure of the latest release.
Also be aware you will need to reflash anytime you update the main CM14.1 OS, as it will overwrite the kernel.
Bugs and issues
As vince's CM14.1 release is a rolling release, depending on many different sources, unexpected issues may come up in either the upstream code, his code, or my code.
Before submitting any reports to vince, be sure you are using his kernel (reflash the cm zip without flashing mine, preferably with a clean install)
Before submitting any reports to me, be sure the issue is not caused by the current release of CM14.1 (aka doesn't happen when you try the above).
No warranty is implied or provided. Be sure to have backups before flashing. But this is a no-brainer.
bump, because new release and target (was cm13, now cm14.1)
This kernel helped me to finally have USB OTG working by default, great job! :good:
Can you give us more detailed info about optimizations? Does your kernel have any impact on battery life?
jon355 said:
Can you give us more detailed info about optimizations? Does your kernel have any impact on battery life?
Click to expand...
Click to collapse
I haven't tested thoroughly but they shouldn't.
The optimizations are some patches that update the arm assembly functions to use features available in our CPUs that were not previously used.
As well as compiling while telling the compiler that we are using a cortex-a53 (in armv7 mode) (by default it just compiled generic armv7 with old armv5/6 assembly).
In short, they aren't overclocks, just using more of the processor's full potential, which is already sitting there doing nothing. Therefore, it shouldn't have a huge impact on battery life.
The CPU patches are here: https://files.persona.cc/zefie/files/cell/SM-T560NU/kernel/common-source/cpu_opts.patch.xz
Fun fact: Our CPU is actually armv8 64-bit, but we can't use it because we depend on Samsung's proprietary binaries, which are compiled in 32-bit (armv7 mode)
Sm-t560 <> smt560nu
Hey,
I'd like to Install this ROM, but obviously i get the message that it's not supported for my Device (in TWRP on flash attempt)
Mine is from the EU so, probably why..
Any chance to get this ROM to work for it?
Akineesan said:
Hey,
I'd like to Install this ROM, but obviously i get the message that it's not supported for my Device (in TWRP on flash attempt)
Mine is from the EU so, probably why..
Any chance to get this ROM to work for it?
Click to expand...
Click to collapse
No.
Unfortunately, Samsung made several hardware changes, including the CPU, when they brought this device to the USA.
You could almost think of the SM-T560NU as the "SM-T560 New".
It is a newer model with revamped hardware, and thus not compatible with ROMs made for the other.
Sorry.
zefie said:
No.
Unfortunately, Samsung made several hardware changes, including the CPU, when they brought this device to the USA.
You could almost think of the SM-T560NU as the "SM-T560 New".
It is a newer model with revamped hardware, and thus not compatible with ROMs made for the other.
Sorry.
Click to expand...
Click to collapse
Alright, thanks for the Quick follow-up!
zefie said:
I haven't tested thoroughly but they shouldn't.
The optimizations are some patches that update the arm assembly functions to use features available in our CPUs that were not previously used.
As well as compiling while telling the compiler that we are using a cortex-a53 (in armv7 mode) (by default it just compiled generic armv7 with old armv5/6 assembly).
In short, they aren't overclocks, just using more of the processor's full potential, which is already sitting there doing nothing. Therefore, it shouldn't have a huge impact on battery life.
The CPU patches are here: https://files.persona.cc/zefie/files/cell/SM-T560NU/kernel/common-source/cpu_opts.patch.xz
Fun fact: Our CPU is actually armv8 64-bit, but we can't use it because we depend on Samsung's proprietary binaries, which are compiled in 32-bit (armv7 mode)
Click to expand...
Click to collapse
Great info. What optimizations were done on OTG mass storage? On stock LOS 14.1 kernel, USB OTG wasn't working for me while with your kernel it works flawlessly.
Jacsd said:
Great info. What optimizations were done on OTG mass storage? On stock LOS 14.1 kernel, USB OTG wasn't working for me while with your kernel it works flawlessly.
Click to expand...
Click to collapse
Honestly none of my patches do anything USB related, except DriveDroid, but that lets the tablet be a device (by hosting disk images), not anything to do with connecting a device to it. Therefore, I cannot take the credit for that. Vince must have fixed it in his kernel. I built this with the latest code at the time, code that may have been more recent than the last lineage build of his that you tried.
zefie said:
Honestly none of my patches do anything USB related, except DriveDroid, but that lets the tablet be a device (by hosting disk images), not anything to do with connecting a device to it. Therefore, I cannot take the credit for that. Vince must have fixed it in his kernel. I built this with the latest code at the time, code that may have been more recent than the last lineage build of his that you tried.
Click to expand...
Click to collapse
I tried latest build and a few older builds, on every I was stucked in the loop of mounting and unmonting USB device. I only managed to enable USB OTG when I installed StickMount. It seems Drive Droid does the same. Will you continue work on this kernel?
Jacsd said:
I tried latest build and a few older builds, on every I was stucked in the loop of mounting and unmonting USB device. I only managed to enable USB OTG when I installed StickMount. It seems Drive Droid does the same. Will you continue work on this kernel?
Click to expand...
Click to collapse
I'll update it if there are any necessary updates for performance or security, or any issues are found, but for now it seems fairly stable and should be alright for a while.
zefie said:
I haven't tested thoroughly but they shouldn't.
The optimizations are some patches that update the arm assembly functions to use features available in our CPUs that were not previously used.
As well as compiling while telling the compiler that we are using a cortex-a53 (in armv7 mode) (by default it just compiled generic armv7 with old armv5/6 assembly).
In short, they aren't overclocks, just using more of the processor's full potential, which is already sitting there doing nothing. Therefore, it shouldn't have a huge impact on battery life.
The CPU patches are here: https://files.persona.cc/zefie/files/cell/SM-T560NU/kernel/common-source/cpu_opts.patch.xz
Fun fact: Our CPU is actually armv8 64-bit, but we can't use it because we depend on Samsung's proprietary binaries, which are compiled in 32-bit (armv7 mode)
Click to expand...
Click to collapse
Tnx for detailed answer. Btw, I tested your LOS 13 build and it's very smooth and battery life is great. Only issue I encountered so far is when charging offline, screen doesn't go off and there is no charging percents showed. Also, can you sync with the latest LIneage changes? Can you replace stock browser with the Jelly and stock camera with the Snap camera?
jon355 said:
Tnx for detailed answer. Btw, I tested your LOS 13 build and it's very smooth and battery life is great. Only issue I encountered so far is when charging offline, screen doesn't go off and there is no charging percents showed. Also, can you sync with the latest LIneage changes? Can you replace stock browser with the Jelly and stock camera with the Snap camera?
Click to expand...
Click to collapse
The thread for that is over here:
https://forum.xda-developers.com/showthread.php?t=3632745
Also, I am unable to reproduce the issue with the screen not shutting off. There is no percentage, but my screen shuts off while locked when charger is plugged in. Percentage and timeout can probably be configured in settings. I sync with Lineage every update. An update will come sometime this month with July's security patches.
As for replacing stock apps, I'll look into it. As the thread says, this is mostly for my use, hence why it wasn't publicly announced before. If I find the apps useful I will see about integration.
Wondering if this is still supported?
zefie said:
The thread for that is over here:
https://forum.xda-developers.com/showthread.php?t=3632745
Also, I am unable to reproduce the issue with the screen not shutting off. There is no percentage, but my screen shuts off while locked when charger is plugged in. Percentage and timeout can probably be configured in settings. I sync with Lineage every update. An update will come sometime this month with July's security patches.
As for replacing stock apps, I'll look into it. As the thread says, this is mostly for my use, hence why it wasn't publicly announced before. If I find the apps useful I will see about integration.
Click to expand...
Click to collapse
From the title you can tell if this still works. For example will it work with official LineageOS and what not. Hoping to get a response so I can overclock my tablet
Bigority said:
From the title you can tell if this still works. For example will it work with official LineageOS and what not. Hoping to get a response so I can overclock my tablet
Click to expand...
Click to collapse
Should still work. I haven't messed with the SM-T560NU in a while. If I recall the Lineage build system was creating broken builds, I'm running 14.1-20171121-NIGHTLY-gtelwifiue and Noire Kernel still works with that.
As for newer builds, last time I tried (some time between xmas and new years), all of the more recent Lineage builds would not boot, with or without my kernel. If trying newer Lineage NIGHTLYs, try without my kernel first, then try with if it does boot.
Vince has kinda abandoned the SM-T560NU, although I'm not sure it is a fair reason to abandon us, because we didn't test on a completely different device, but his choice is his alone, and as such, without him working on Lineage, the newer builds are likely to stay broken unless either he comes back to fix it, or someone else takes over (don't look at me).
zefie said:
Should still work. I haven't messed with the SM-T560NU in a while. If I recall the Lineage build system was creating broken builds, I'm running 14.1-20171121-NIGHTLY-gtelwifiue and Noire Kernel still works with that.
As for newer builds, last time I tried (some time between xmas and new years), all of the more recent Lineage builds would not boot, with or without my kernel. If trying newer Lineage NIGHTLYs, try without my kernel first, then try with if it does boot.
Vince has kinda abandoned the SM-T560NU, although I'm not sure it is a fair reason to abandon us, because we didn't test on a completely different device, but his choice is his alone, and as such, without him working on Lineage, the newer builds are likely to stay broken unless either he comes back to fix it, or someone else takes over (don't look at me).
Click to expand...
Click to collapse
For it to work properly should I try your port of LINEAGEOS or should I try Vince's port of Cyanogen Mod?
Bigority said:
For it to work properly should I try your port of LINEAGEOS or should I try Vince's port of Cyanogen Mod?
Click to expand...
Click to collapse
This kernel is for vince's 14.1. My 13.0 already uses Noire kernel and this release should not be flashed with that
zefie said:
This kernel is for vince's 14.1. My 13.0 already uses Noire kernel and this release should not be flashed with that
Click to expand...
Click to collapse
Alright thanks
zefie said:
This kernel is for vince's 14.1. My 13.0 already uses Noire kernel and this release should not be flashed with that
Click to expand...
Click to collapse
The link isn't working to download the kernel :l
Edit: It was working just my internet was too ****ty too load it.
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
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.
What is LightningZap! kernel?
It is a lightweight, yet heavily tweaked and optimized kernel geared towards balancing performance and battery life.
Please read this ENTIRE post before downloading and flashing LightningZap! kernel.
Disclaimer: As with all custom kernels, you flash at your own risk. Always make a backup! I nor the associates of LightningZap! kernel, Teamfahq, or the testers group cannot and will not take responsibility for YOUR actions. I cannot always control what works and doesn't work with ROMs other than my own. If there is a bug, feel free to report it with logs, but note that the problem may be due to a conflict with coding int the ROM. If said condition exists, please discuss the concern with said ROM developer. If a bug condition does exist within the kernel and there is a known fix for said bug, please don't hesistate to link me to that fix. Make sure to give credit, thanks, and maybe even a cup of coffee to your developers. If you have a feature request, please feel free to share it as well.
Features:
Based off ElementalX kernel by flar
blue_schedul governor from blue_spark kernel thanks to eng.st
Ondemand gov Optimized for better performance while maintaining battery life
FIOPS ioscheduler by default (suggest leavving it that way)
My insane readahead tweak **** In HDK-Mod kernel manager, it reports "Not in range." This is normal DO NOT adjust. My tweaks optimizes readahead per demand usage.****
LZ4 compression
O3 Optimizations
zram
lz-sysctl tweaks
Sound control (speaker, earpiece and mic)
Backlight min setting
Adjust or disable vibration
Advanced Color Control and K-Lapse
Block wakelocks
NTFS r/w, CIFS and NFS support
WireGuard support
Option to disable fsync
Pass SafetyNet
LightningZap! kernel will work on oneplus 6 and oneplus 6T on stock OOs and most custom roms. There are 2 versions, PIE and NDP.
Diferences
PIE was built for custom roms
STOCK was modified for stock OOS (Does not include commits to fix fps that custom roms need)
NDP was slightly modified for SkyDragonOs by removing wake gestures. Wake gestures are natviely written into SkyDragonOs (and maybe more roms).
I have not tested all roms to see what works and what doesn't. So, I would suggest trying PIE first. If wake gestures (like dt2w) do not work, try NDP. Feel free to report what rom and LightningZap! kernel version you are using.
Bug reporting is HIGHLY encouraged, but please accompany your reports with logs. I cannot do much to fix things without them. Pruning of the logs is deeply appreciated as well.
I feel that if you are here, you already know how to flash a custom kernel. If not, close this page and do some research about it first. This will not erase recovery or root when flashing. But, I would like to quote @eng.stk
Warning: If you come from other kernel or have any issues, you should dirty flash your ROM before flashing LightningZap! zip to avoid problems.
Reflash ROM -> if you want root flash SuperSU or Magisk (default, no plugins/modules) -> flash LightningZap!.
If you are already rooted or upgrading between LightningZap! versions, just flash the kernel zip. Also uninstall or clean data of any kernel control app you're using.
Click to expand...
Click to collapse
Download links:
LightningZap! kernel PIE- Updated 10-07-2019
LightningZap! kernel NDP
LightningZap!-kernel-STOCK
Changelog
XDAevDB Information
LightningZap! kernel for OnePlus 6/6T
Special thanks to:
flar, eng.stk, HolyAngel Kernel Source: OnePlus6T-LZ
Version Information
Status: Stable
Current Stable Version: 2.3
Stable Release Date: 10-05-2019
ROM tracker
Here I will post what version of LightningZap! kernel works with what ROMs. As well as any noted bugs with said rom.
PIE
Most custom roms
NDP
SkyDragonOs
Stock
Stock OOS
It sounds very interesting! But a doubt that not before the SkyDragon rom was running the HolyDragon kernel? This would be the evolution of that kernel?
It sounds very promising! As soon as possible I will try it!
Thank you man!!
thomas.raines said:
Here I will post what version of LightningZap! kernel works with what ROMs. As well as any noted bugs with said rom.
PIE
Stock OOS
NDP
SkyDragonOs
Click to expand...
Click to collapse
Thank you so much. Do you recommend sticking with schedutil, which is default I believe, or do you prefer Onedemand or Blu instead? Thanks again for the kernel, I'm checking it out now.
---------- Post added at 04:18 PM ---------- Previous post was at 04:14 PM ----------
Everything seems great so far except one thing. Has anyone else noticed that their fingerprint sensor stopped working on OOS stable? Or could this just be a coincidence for me?
Ryano89 said:
Thank you so much. Do you recommend sticking with schedutil, which is default I believe, or do you prefer Onedemand or Blu instead? Thanks again for the kernel, I'm checking it out now.
---------- Post added at 04:18 PM ---------- Previous post was at 04:14 PM ----------
Everything seems great so far except one thing. Has anyone else noticed that their fingerprint sensor stopped working on OOS stable? Or could this just be a coincidence for me?
Click to expand...
Click to collapse
Isnt working for me either
fosgate24360 said:
Isnt working for me either
Click to expand...
Click to collapse
Yeah, I tried to reregister my FP but it won't let me.
Ryano89 said:
Yeah, I tried to reregister my FP but it won't let me.
Click to expand...
Click to collapse
It's not going to work on OOS as he's got the FOD hacks required for functional fingerprint on custom ROMs. Doing this breaks fingerprint on OOS, and removing them will break it on custom ROMs. The only way to accommodate both currently is with two separate kernel variants.
Great work Thomas
Riddle5 said:
It sounds very interesting! But a doubt that not before the SkyDragon rom was running the HolyDragon kernel? This would be the evolution of that kernel?
Click to expand...
Click to collapse
Completely different kernel from HolyDragons.
Ryano89 said:
Thank you so much. Do you recommend sticking with schedutil, which is default I believe, or do you prefer Onedemand or Blu instead? Thanks again for the kernel, I'm checking it out now.
---------- Post added at 04:18 PM ---------- Previous post was at 04:14 PM ----------
Everything seems great so far except one thing. Has anyone else noticed that their fingerprint sensor stopped working on OOS stable? Or could this just be a coincidence for me?
Click to expand...
Click to collapse
For governor, use whatever fits your needs the most. I recommend trying all 3 to see which on egives you the most performance and battery life.
return.of.octobot said:
It's not going to work on OOS as he's got the FOD hacks required for functional fingerprint on custom ROMs. Doing this breaks fingerprint on OOS, and removing them will break it on custom ROMs. The only way to accommodate both currently is with two separate kernel variants.
Click to expand...
Click to collapse
Yep... Accidentally merged those commits to the PIE branch. Running new build now. oops...
PIE branch updated. Fingerprint should be fixed now.
The New Update Is Buttery Smooth Bro Great Work Fp Works Better Than Stock Oos the only thing is the gaming performance has came down can experiencing shutter lags, and fps drops any fixes over that rest is just amazing bro .
Dhairya said:
The New Update Is Buttery Smooth Bro Great Work Fp Works Better Than Stock Oos the only thing is the gaming performance has came down can experiencing shutter lags, and fps drops any fixes over that rest is just amazing bro .
Click to expand...
Click to collapse
With your favorite kernel manager app, try using ondemand governor and lowering the up_threshold value adjust the sampling rate.
Using 3D benchmark app with Sling Shot Exteme setting up_threshold at 70 (default value) OpenGL ES 3.1 scored 4632 and Vulkan came in at 4272
Dropping it to 15 (lowest possible value)
OpenGL ES 3.1 scored 4857 and Vulkan came in at 4456
Setting it to 90
OpenGL ES 3.1 scored 4337 and Vulkan came in at 4068
These are overall scores and only an example. Results may very per device.
You can also try raising the sampling_rate as well. But I think the default value is best.
Be aware when adjusting these values, your perfomance vs battery life is effected.
lower up_threshuold will increase performance and decrease battery life whereas higher up_threshold decreases performance but raises battery life. Adjusting these values too high/low can cause the device to become unstable or overheat. Make your adjustments in small increments and if you notice a significant lag or your device is starting to get too hot, you can change them back and avoid complete device failure.
And by battery life, I mean the discharge rate, not the length of time until your battery takes a poop and you have to replace it or your phone.
New download link for pie branch. New branch added STOCK.
So, as pointed out by return.of.octobot , the PIE branch fp worked but became broken after reverting the commit for fp on custom roms. So, I made a new branch for OOS only and the PIE branch is for custom ROMs.
Tried flashing this stock version kernel on OOS 9.0.17 via FK manager app and got the abort message with error as unsupported device. Please see attached screenshot and let me know if there is something I need to change.
deepu458 said:
Tried flashing this stock version kernel on OOS 9.0.17 via FK manager app and got the abort message with error as unsupported device. Please see attached screenshot and let me know if there is something I need to change.
Click to expand...
Click to collapse
Flash in recovery. Since this is not a franko kernel, the franko kernel app won't work...
thomas.raines said:
Flash in recovery. Since this is not a franko kernel, the franko kernel app won't work...
Click to expand...
Click to collapse
Hello dear dev, is it working on 10.3.0 OOS for OP 6?cause the latest build is from October 2019...
James Blode said:
Hello dear dev, is it working on 10.3.0 OOS for OP 6?cause the latest build is from October 2019...
Click to expand...
Click to collapse
The thread title says it all...OOS9/ Pie.
James Blode said:
Hello dear dev, is it working on 10.3.0 OOS for OP 6?cause the latest build is from October 2019...
Click to expand...
Click to collapse
The current released and stable version is for android 9.0/pie.
Thre android 10 version is still in testing.
thomas.raines said:
The current released and stable version is for android 9.0/pie.
Thre android 10 version is still in testing.
Click to expand...
Click to collapse
Thanks for letting me know...ill wait for this great kernel...