Related
As the title suggests, is there a kernel for the P605 which will allow SElinux permissive, and therefore allow full linux chroot installs to be completed with relative ease.
I am aware of a permissive kernel for P600, http://forum.xda-developers.com/showthread.php?t=2590311
but assume this will not function for the P605.
If not can the same steps used to make the P600 kernel permissive be applied to a P605 kernel?
Looking for the same kernel
I'm looking for the same SELinux-permissive kernel for P605.
You definitely can't use the P600 kernel as it is for the Exynos variant (P600/01) while ours (P605) is the Quallcom CPU.
Unfortunately the P600/01 was released around the world first with most devs getting the Exynos version. Little developement has been done for the P605 but there has been a little. Just not for an SE-Linux permissable kernel, at least not here on XDA...
Will try to build it myself
I've been thinking of modifying and building the kernel myself. The problem is that there are several kernel source codes on Samsung's website for SM-P605. (I can't post the link here) My device model is SM-P605 without any suffixes so I think it's the first kernel that I should choose.
I think modifying the kernel into SELinux permissive should be as easy as changing a default value in one of the source files and then I can build the kernel using the instructions that come with it. Fingures crossed!
One more thing: in the source code that Samsung provides there are two directories, one kernel and the other platform do I need to build the platform too?
Rhesus007 said:
I've been thinking of modifying and building the kernel myself. The problem is that there are several kernel source codes on Samsung's website for SM-P605. (I can't post the link here) My device model is SM-P605 without any suffixes so I think it's the first kernel that I should choose.
I think modifying the kernel into SELinux permissive should be as easy as changing a default value in one of the source files and then I can build the kernel using the instructions that come with it. Fingures crossed!
One more thing: in the source code that Samsung provides there are two directories, one kernel and the other platform do I need to build the platform too?
Click to expand...
Click to collapse
Hey Rhesus007, just wondering if you have made any progress?
Im really in need of a permissive kernel, however i have no knowledge of how to make it etc.
Thanks.
Just dropping back in the thread, still hoping this will happen, as linux on this tab would be really useful imo.
Someone with some dev experience might be able to use the methods used on the note3, which has the same snapdragon 800 soc to achieve this. The basic steps needed to modify the kernel are described in this thread
http://forum.xda-developers.com/showthread.php?t=2471416
if nobody with experience can do this, I might give it a try, but that might be a recipe for disaster....
patchseven said:
Just dropping back in the thread, still hoping this will happen, as linux on this tab would be really useful imo.
Someone with some dev experience might be able to use the methods used on the note3, which has the same snapdragon 800 soc to achieve this. The basic steps needed to modify the kernel are described in this thread
http://forum.xda-developers.com/showthread.php?t=2471416
if nobody with experience can do this, I might give it a try, but that might be a recipe for disaster....
Click to expand...
Click to collapse
I've got no experience with this, if you could attempt it, I'm sure a lot of people would be grateful!
For those still looking.
Maybe this might work, don't know if it will work on custom ROM's
http://forum.xda-developers.com/showthread.php?t=2765353&page=3
EP005 said:
Maybe this might work, don't know if it will work on custom ROM's
http://forum.xda-developers.com/showthread.php?t=2765353&page=3
Click to expand...
Click to collapse
http://forum.xda-developers.com/gal...rnel-stock-selinux-permissive-kernel-t3232814
For the 5.1.1 update!
Since joshuabg posted his build of AICP, countless other people decided they would continue his mission of bringing AOSP-based custom roms to this wonderful device
however in doing this people started stealing the AICP thread to talk about compile problems(i know im the biggest offender) so im fixing that.
Post all ROM development talk below so we can attempt to help each other and get the rom problems out of the way and finally get development for this amazing, game-changing, sexy slice android off the ground
Hey guys, if anyone is looking for how to build a rom for the nexus 9(and theyre forced to use a prebuilt kernel) i wrote up a tutorial on how to do that at the top of page 5:
http://forum.xda-developers.com/nex...evelopment-thread-t2995510/page5#post58089268
Based on my convo with Josh, he indicated that disabling SELinux in the prebuilt kernel (with help from USBHost) would assist in allowing the build to boot. However, I honestly do not want to disable SELinux AT ALL. I will find a way to make this work without disabling SELinux.
The issues I had with getting the AICP to boot without a Setup Wizard has stopped loop was 100% to blame on SELinux. ROM was disabled kernel was enforcing, and they didn't want to play nicely together. As soon as I used a kernel with SELinux disabled, it booted right up no problems. Should someone maybe ask flar2 with a mention in here to get his two cents?
SwoRNLeaDejZ said:
The issues I had with getting the AICP to boot without a Setup Wizard has stopped loop was 100% to blame on SELinux. ROM was disabled kernel was enforcing, and they didn't want to play nicely together. As soon as I used a kernel with SELinux disabled, it booted right up no problems. Should someone maybe ask flar2 with a mention in here to get his two cents?
Click to expand...
Click to collapse
i dont think thats right...i could be doing something wrong, but im fairly certain that when i compiled by build i set both the ROM and Kernel to SElinux disabled(or at least enforcing) and the kernel wouldnt even try to boot...
however, i do have to say that im not 100% certain how to disable SElinux in the ROM so i did what i thought would work, so maybe thats why mine doesnt boot...once i figure out compiling this kernel and either praise you or stand by my point
also i havent heard anything of flar2 since november 24th so idk what happened there
zawata said:
i dont think thats right...i could be doing something wrong, but im fairly certain that when i compiled by build i set both the ROM and Kernel to SElinux disabled(or at least enforcing) and the kernel wouldnt even try to boot...
however, i do have to say that im not 100% certain how to disable SElinux in the ROM so i did what i thought would work, so maybe thats why mine doesnt boot...once i figure out compiling this kernel and either praise you or stand by my point
also i havent heard anything of flar2 since november 24th so idk what happened there
Click to expand...
Click to collapse
You could very well be right. All I was speaking from was my experience of every kernel I tried using that didn't have SELinux disabled, the build wouldn't boot.
SwoRNLeaDejZ said:
You could very well be right. All I was speaking from was my experience of every kernel I tried using that didn't have SELinux disabled, the build wouldn't boot.
Click to expand...
Click to collapse
what do you mean by not boot? like exacty? because for me, a kernel not booting means stuck at the google splash screen
The ROM does not control selinux
Only the kernel controls it
Well guys, i finally got CM to build without breaking a few days ago but the kernel didnt work so i did a bunch of testing a research and i think ive concluded that theres something wrong with the build process that breaks the kernels, once i figure out what, we'll have the reliable build system that doesnt rely on prebuilt kernels
on a side note i figured out how to build AOSP with prebuilt kernels
SO we finally have a CM build that can stand on its own and run well(shockingly well, i havent found any problems) and it doesnt rely on USBhost's feature-rich kernel or his prebuilt one that no-one really understands...lol no offense intended usbhost, FIK is pretty damn good
@SwoRNLeaDejZ : selinux is currently disabled so im going to see what happens when i renable it @USBhost : is SElinux disabled the same thing as permisive? im guessing no and which one would be the best to set for a custom rom. im guessing permissive?
zawata said:
Well guys, i finally got CM to build without breaking a few days ago but the kernel didnt work so i did a bunch of testing a research and i think ive concluded that theres something wrong with the build process that breaks the kernels, once i figure out what, we'll have the reliable build system that doesnt rely on prebuilt kernels
on a side note i figured out how to build AOSP with prebuilt kernels
SO we finally have a CM build that can stand on its own and run well(shockingly well, i havent found any problems) and it doesnt rely on USBhost's feature-rich kernel or his prebuilt one that no-one really understands...lol no offense intended usbhost, FIK is pretty damn good
@SwoRNLeaDejZ : selinux is currently disabled so im going to see what happens when i renable it @USBhost : is SElinux disabled the same thing as permisive? im guessing no and which one would be the best to set for a custom rom. im guessing permissive?
Click to expand...
Click to collapse
I built a stock kernel that's so awesome that no one can comprehend or understand it
Haha aren't I awesome lol
About selinux if its disabled
It means it was not compiled with the kernel
so you can't simply enable it
I would recommend permissive on the kernel command line
So it would be easier to debug what is preventing stock kernel from not booting
Because you can see what would have selinux prevented from running
on /proc/kmsg or /dev/kmsg
USBhost said:
I built a stock kernel that's so awesome that no one can comprehend or understand it
Haha aren't I awesome lol
About selinux if its disabled
It means it was not compiled with the kernel
so you can't simply enable it
I would recommend permissive on the kernel command line
So it would be easier to debug what is preventing stock kernel from not booting
Because you can see what would have selinux prevented from running
on /proc/kmsg or /dev/kmsg
Click to expand...
Click to collapse
haha well no one could figure out how to use it(but i did I FIGURED YOU OUT!! YOUR A PHONY!!) jokes aside though
so setting permissive in the boardconfig.mk? :
BOARD_KERNEL_CMDLINE := androidboot.selinux=permissive
then make menuconfig and re-enable the options you told me to disable in tha PM(i dont fee like typing them out lol)
zawata said:
haha well no one could figure out how to use it(but i did I FIGURED YOU OUT!! YOUR A PHONY!!) jokes aside though
so setting permissive in the boardconfig.mk? :
BOARD_KERNEL_CMDLINE := androidboot.selinux=permissive
then make menuconfig and re-enable the options you told me to disable in tha PM(i dont fee like typing them out lol)
Click to expand...
Click to collapse
Yep that should do it
If not tell me
USBhost said:
Yep that should do it
If not tell me
Click to expand...
Click to collapse
currently building the boot image(btw im using your flashable zip as a base thanks )
will report back
EDIT: hmm nope it didnt seem to work, i think it might have been my fault ill tryt it again
USBhost said:
Yep that should do it
If not tell me
Click to expand...
Click to collapse
im not sure if its me being stupid or something else but i cant reenable SElinux
im thinking its because i dont know if im specifying the right config file...im not 100%
maybe you could just give me a kernel binary with selinux reenabled but not tonight, i should really get to sleep lol
zawata said:
im not sure if its me being stupid or something else but i cant reenable SElinux
im thinking its because i dont know if im specifying the right config file...im not 100%
maybe you could just give me a kernel binary with selinux reenabled but not tonight, i should really get to sleep lol
Click to expand...
Click to collapse
Lol will do
CM compiles fine for me with prebuilt kernel and a few minor source changes. I have a zip from 1/6/15 if anybody will like to test (I really don't feel like wiping right now lol)
Sent from my SCH-I545 using Tapatalk
joshuabg said:
CM compiles fine for me with prebuilt kernel and a few minor source changes. I have a zip from 1/6/15 if anybody will like to test (I really don't feel like wiping right now lol)
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
yeah what im trying to do now is get it to compile now straight from source(figure out why it wont) and also prepare the kernel for build teams to want to take it
i actually have CM(built on the 5th) and my kernel(no changes but selinux disabled(working on it)) running on my tablet right now and im shocked by how smooth it is! its amazing!
zawata said:
yeah what im trying to do now is get it to compile now straight from source(figure out why it wont) and also prepare the kernel for build teams to want to take it
i actually have CM(built on the 5th) and my kernel(no changes but selinux disabled(working on it)) running on my tablet right now and im shocked by how smooth it is! its amazing!
Click to expand...
Click to collapse
CM android_build currently does not support arm64 kernels
Sent from my SCH-I545 using Tapatalk
Just throwing this out there, but if anyone comes up with any type of test builds, or test kernels, that they need someone to flash and try out, let me know. Always more than willing to give some experimental builds a test drive.
joshuabg said:
CM android_build currently does not support arm64 kernels
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Yeah I know, which is why I'm going to *hackily implement it*(until Steve finishes his implementation) or cherry pick his attempt and see if I can get it too work
I just got off work(I hate training!!!) And I'll see what I can do about it
I will not deny that anything the CM team will cook up, will be miles better than what I can make but I'm just trying to make it build for a single device, not all of the devices it a super efficient manner
Actually I think I might start some unnoficial nightlies for CM if people want, once I finish my build script then I shouldnt have very much difficulty making it each night
SwoRNLeaDejZ said:
Just throwing this out there, but if anyone comes up with any type of test builds, or test kernels, that they need someone to flash and try out, let me know. Always more than willing to give some experimental builds a test drive.
Click to expand...
Click to collapse
lol bold offer, you're so brave, unlucky for you though, this is a nexus device so if know it boots then we pretty much know everything works so the beta testing isnt as necessary as say on a samsung/htc/lg device,
however, ill see if i can find something i need testing
EDIT: device is now selinux status: permissive(apparently i still dont know how to build kernels...lol but i figured it out)
zawata said:
Yeah I know, which is why I'm going to *hackily implement it*(until Steve finishes his implementation) or cherry pick his attempt and see if I can get it too work
I just got off work(I hate training!!!) And I'll see what I can do about it
I will not deny that anything the CM team will cook up, will be miles better than what I can make but I'm just trying to make it build for a single device, not all of the devices it a super efficient manner
Actually I think I might start some unnoficial nightlies for CM if people want, once I finish my build script then I shouldnt have very much difficulty making it each night
lol bold offer, you're so brave, unlucky for you though, this is a nexus device so if know it boots then we pretty much know everything works so the beta testing isnt as necessary as say on a samsung/htc/lg device,
however, ill see if i can find something i need testing
EDIT: device is now selinux status: permissive(apparently i still dont know how to build kernels...lol but i figured it out)
Click to expand...
Click to collapse
Love the unofficial nightlies idea
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.
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.
Those of you who have been around for a while have heard of leanKernel. Well this isn't a leanKernel, in fact, I haven't developed leanKernels in 3 years. This is essentially the stock kernel with some enhancements.
I think google stock kernels are great nowadays, but when I learned that my Pixel 3a came with eMMC rather than UFS, I thought maybe there are some storage related tweaks I can apply to the stock kernel, so that's what I attempted here.
Again, this is the stock kernel recompiled with the following changes (otherwise should work and behave exactly like stock):
Some f2fs backports from latest f2fs/android sources, mostly around discard and garbage collection including Rapid GC implementation from arter97. The f2fs optimizations around GC/discard are designed to alleviate eMMC write performance degredations over time, thus improving performance over time as well.
Compiled with gcc 9.2 (kdrag0n) with some architecture and cpu dependent compile optimizations.
Drivers (including wifi driver optimized by arter97) compiled in rather than loading in as modules.
LZMA enabled for TWRP support.
Use fastboot to install. (TWRP or kernel manager flash should work as well, as long as they support boot image flashing).
Three files: stock, stock-modified-nomagisk, and stock-modified-magisk.
Most of you will probably want to "fastboot flash boot stock-modified-magisk.img". Flash stock when you want to go back to stock.
Install files
Source: https://github.com/imoseyon/pixel3a-kernel
Absolutely awesome news. I was interested to know about eMMc after I heard some people mention it. Anyway, thank you and welcome back.
A couple of quick questions if you wouldn't mind, since a lot of us are new to the "Pixel experience", having come from devices that previously only had one or two new firmware versions within the device's lifetime, and are now enjoying monthly updates, with that bringing its own set of issues...
Is this kernel considered a stock variation that cannot be tweeted by a kernel manager, or custom and is tweakable? What is gained by using this one over some of the other custom kernels?
Since the boot image on this device can contain Magisk, custom kernel, and TWRP, does that mean with every update a new image would have to be built, rooted, and TWRP installed, or is there an easier way to get this accomplished?
Thx and happy to see you back on board with this device...
duh1 said:
A couple of quick questions if you wouldn't mind, since a lot of us are new to the "Pixel experience", having come from devices that previously only had one or two new firmware versions within the device's lifetime, and are now enjoying monthly updates, without that bringing its own set of issues...
Is this kernel considered a stock variation that cannot be tweeted by a kernel manager, or custom and is tweakable? What is gained by using this one over some of the other custom kernels?
Since the boot image on this device can contain Magisk, custom kernel, and TWRP, does that mean with every update a new image would have to be built, rooted, and TWRP installed, or is there an easier way to get this accomplished?
Thx and happy to see you back on board with this device...
Click to expand...
Click to collapse
First, with respect to the kernel manager it will behave exactly like the stock kernel. There may be a few tweakable settings the manager apps can see that are in stock which will also show up for this kernel. This is not a true custom kernel with lots of configurable settings - if that's what you want then definitely go for elemental or despair which are developed by excellent devs.
Regarding boot image, you are correct. However, once Pixel 3A gets an official TWRP I should be able to include that in the boot image along with Magisk (currently only Magisk is included). And as long as I have the device I will provide at least one set of updates for each security update from Google.
Imoseyon said:
First, with respect to the kernel manager it will behave exactly like the stock kernel. There may be a few tweakable settings the manager apps can see that are in stock which will also show up for this kernel. This is not a true custom kernel with lots of configurable settings - if that's what you want then definitely go for elemental or despair which are developed by excellent devs.
Regarding boot image, you are correct. However, once Pixel 3A gets an official TWRP I should be able to include that in the boot image along with Magisk (currently only Magisk is included). And as long as I have the device I will provide at least one set of updates for each security update from Google.
Click to expand...
Click to collapse
Thank for the kind words! I actually took a look at your source and I am grabbing the f2fs changes you have, those are a good find. Have always followed your work and have used some of your contributions as well.
Holy... Haven't seen you around since the days of the Samsung charge iirc...
Imoseyon said:
First, with respect to the kernel manager it will behave exactly like the stock kernel. There may be a few tweakable settings the manager apps can see that are in stock which will also show up for this kernel. This is not a true custom kernel with lots of configurable settings - if that's what you want then definitely go for elemental or despair which are developed by excellent devs.
Regarding boot image, you are correct. However, once Pixel 3A gets an official TWRP I should be able to include that in the boot image along with Magisk (currently only Magisk is included). And as long as I have the device I will provide at least one set of updates for each security update from Google.
Click to expand...
Click to collapse
Is your kernel also working on the 3a XL, or is it only for the regular 3a?
xFirefly93 said:
Is your kernel also working on the 3a XL, or is it only for the regular 3a?
Click to expand...
Click to collapse
I think it might. I have no way to test it though..
Imoseyon said:
I think it might. I have no way to test it though..
Click to expand...
Click to collapse
Well, is the kernel source the same for the 3a and 3aXL, or if not, could you make the same mods to the XL source?
I was wondering if this could be built and installed as a zip file, so we could make use of the the kernel managers for easy switching between different kernels for testing. If not, what makes this different that requires an image? Thx...
duh1 said:
Well, is the kernel source the same for the 3a and 3aXL, or if not, could you make the same mods to the XL source?
I was wondering if this could be built and installed as a zip file, so we could make use of the the kernel managers for easy switching between different kernels for testing. If not, what makes this different that requires an image? Thx...
Click to expand...
Click to collapse
Kernel source and even the defconfig file are identical between 3a and 3axl, so I'm fairly confident that it works on both.
Have you tried flashing the boot image files in your kernel manager? I think some, if not all, should work with image files as well.
Imoseyon said:
Kernel source and even the defconfig file are identical between 3a and 3axl, so I'm fairly confident that it works on both.
Have you tried flashing the boot image files in your kernel manager? I think some, if not all, should work with image files as well.
Click to expand...
Click to collapse
Will give it a try flashing it that way, but wondering is there a technical reason why this particular kernel must be an image, not a zip?
xFirefly93 said:
Is your kernel also working on the 3a XL, or is it only for the regular 3a?
Click to expand...
Click to collapse
Imoseyon said:
I think it might. I have no way to test it though..
Click to expand...
Click to collapse
It will work for both.
duh1 said:
Will give it a try flashing it that way, but wondering is there a technical reason why this particular kernel must be an image, not a zip?
Click to expand...
Click to collapse
No real reason other than i didn't think a zip file was needed especially since this kernel is supposed to be more or less the same as stock. I will add a zip file into the folder soon though.
Imoseyon said:
No real reason other than i didn't think a zip file was needed especially since this kernel is supposed to be more or less the same as stock. I will add a zip file into the folder soon though.
Click to expand...
Click to collapse
Can this can be used on Q beta6?
caballon said:
Can this can be used on Q beta6?
Click to expand...
Click to collapse
Nope sorry. Will be working on Aug updates this weekend. Been out of town.
Aug update is up. Toolchain updated to gcc 9.2 as well.
How can I verify that I am actually running your kernel?
Screenshot of About Phone
EDIT: I guess the build date matches that of your upload date.
benji said:
How can I verify that I am actually running your kernel?
Screenshot of About Phone
EDIT: I guess the build date matches that of your upload date.
Click to expand...
Click to collapse
Yup that's it
Will change the version string in my next build so it's less confusing. Good catch.
Will this let TWRP stay installed or no? Do you have to install a custom rom for that and use the other kernel?
crackedvenom2 said:
Will this let TWRP stay installed or no? Do you have to install a custom rom for that and use the other kernel?
Click to expand...
Click to collapse
Interesting, looks like I may need to enable lzma compression. I haven't tried installing twrp yet, let me give it a shot this weekend. Should be easy enough.