[Kernel][Oreo] NiKernel for Pixel/Pixel XL - Google Pixel ROMs, Kernels, Recoveries, & Other De

- STUFF YOU SHOULD READ -
- I'm not responsible if anything goes horribly wrong but I take measure to reduce the risk of this happening.
- Most, if not all, builds are tested by me personally before they are released.
- This kernel is aiming for peak single-core performance and efficiency while maintaining fair multi-core speeds.
- This isn't just some other kernel in my eyes, it might be to you, but I put a lot of interesting changes in the kernel for benefit analysis.
- I'm still quite young in the development field but I try to learn more and to improve my pieces of work.
- I always use the latest kernel on my personal device to be able to find bugs and it makes it easier to fix issues.
- Have fun, compatible with both the Pixel and Pixel XL. (sailfish and marlin respectively)
- FEATURES -
- Up-streamed to Linux 3.18.71 (CAF AOSP branch)
- Sound control (speaker, headphones, mic)
- Dynamic file sync control 2.0 (@LordBoeffla)
- BFQ I/O scheduling
- Westwood+ TCP congestion algorithm
- Removed most CPU governors
- Wakelock blocker (@FranciscoFranco)
- Adreno idler
- ElementalX sleep/wake gestures
Built with love using Linaro 6.4.1
- TELEGRAM GROUP -
Link: NiKernel Testing/Discussion
- DOWNLOADS -
Link: Google Drive
XDA:DevDB Information
NiKernel, Kernel for the Google Pixel
Contributors
Nick80835
Source Code: https://github.com/Nick80835/NiKernel_marlin
Kernel Special Features: It boots. It doesn't not boot.
Version Information
Status: Beta
Current Beta Version: 2017-10-01:12
Created 2017-09-21
Last Updated 2017-10-01

Reserved

Nick80835 said:
Will add more info later, empty for now.
Click to expand...
Click to collapse
So would you say that this is basically a stock kernel built from source at this point or have you added things to it? No need to list.

uodii said:
So would you say that this is basically a stock kernel built from source at this point or have you added things to it? No need to list.
Click to expand...
Click to collapse
It's not stock, I've been testing things for about a week, it has KCAL, dynamic fsync, backlight dimming, high brightness mode, passes safetynet with SuperSU without SUhide, still working on it and trying to improve some aspects of it.
Edit: Oh, it's also using Linux 3.18.71.
Sent from my Pixel using XDA Labs

I've been running it for almost a day and it's smooth. Battery seems good. Will update as time progresses.

Is there certain steps we need to do for flashing this?

quinejh said:
Is there certain steps we need to do for flashing this?
Click to expand...
Click to collapse
Just like any other kernel

What SuperSu version are you using? I can get the kernel to install, but when I try to install SuperSu version SR3-SuperSu-v2.82-SR3-20170813133244, it goes back to the stock kernel.

redwolves said:
What SuperSu version are you using? I can get the kernel to install, but when I try to install SuperSu version SR3-SuperSu-v2.82-SR3-20170813133244, it goes back to the stock kernel.
Click to expand...
Click to collapse
SuperSU 2.82 SR4, also I recommend reflashing the stock boot image before installing the kernel, then installing SuperSU. It's confusing but it's a quirk SuperSU has.
Sent from my Pixel using XDA Labs

Nick80835 said:
SuperSU 2.82 SR4, also I recommend reflashing the stock boot image before installing the kernel, then installing SuperSU. It's confusing but it's a quirk SuperSU has.
Click to expand...
Click to collapse
I have SR3.....
Edit: With no issues so far any way

S8ntsHaz3 said:
I have SR3.....
Edit: With no issues so far any way
Click to expand...
Click to collapse
It's not really a bug but when you flash SuperSU it creates a backup of the stock boot image. When you flash a kernel and reflash SuperSU, it restores the stock image first basically wiping the custom kernel. The only fix is flashing the stock boot.img for your device in fastboot or TWRP, then installing the kernel and SuperSU.
Sent from my Pixel using XDA Labs

Ok well I guess I'll get sr4 for when I flash the new release tonight??

Nick80835 said:
SuperSU 2.82 SR4, also I recommend reflashing the stock boot image before installing the kernel, then installing SuperSU. It's confusing but it's a quirk SuperSU has.
Sent from my Pixel using XDA Labs
Click to expand...
Click to collapse
That did the trick.
Thanks.

Unfortunately, if I mess around with speaker settings and mic gain settings it restarts after some time and goes to stock recovery asking me to "try again or factory reset"

Glad you posted it
Good work

rohitece06 said:
Unfortunately, if I mess around with speaker settings and mic gain settings it restarts after some time and goes to stock recovery asking me to "try again or factory reset"
Click to expand...
Click to collapse
Hmmm..will look..
Sent from my Pixel using XDA Labs

Same happened with ElementalX kernel but when I installed elementalX with SR4 supersu, things are fine. So it may not be your kernel. I may try your kernel over the weekend with SR4 kernel next week.

Version 2017-09-23:18 is up with several improvements overall to the GPU, battery, CPU, and audio.
Link: https://drive.google.com/file/d/0B9YVqhP7dzbrUEhIaHBubERJOFU/view?usp=drivesdk
Sent from my Pixel using XDA Labs

I wasn't aware that flash fire works so well on are pixel devices I just flash the sr4 update and it worked perfect can I use Flashfire to flash this kernel as well?

quinejh said:
I wasn't aware that flash fire works so well on are pixel devices I just flash the sr4 update and it worked perfect can I use Flashfire to flash this kernel as well?
Click to expand...
Click to collapse
It should be possible, I'm not so sure how SuperSU would react. :silly:
Sent from my Pixel using XDA Labs

Related

[EOL] [KERNEL][G800F][exynos][CUSTOM KERNEL] FOR MOST CUSTOM ROMS [EOL]

Code:
***WARNING***
-READ CAREFULLY!!
YOU FLASH THIS KERNEL AT YOUR OWN RISK.I TAKE NO RESPONSIBILITY FOR ANY DAMAGE THAT MAY OCCUR DUE TO THE FLASHING OF THIS IMAGE.
I WILL NOT BE RESPONSIBLE FOR LOST DATA,BRICKED PHONE,OR ANYTHING OF THE SUCH.(PHONE EXPOLDES,OVERHEATS ETC)
THIS KERNEL IS ONLY FOR THE S5 MINI SM-G8OOF (Exynos) DO NOT FLASH THIS ON ANY OTHER DEVICE!
EOL (End of Life) ​
I will be creating a new thread for my N kernel - Stay tuned!​
UPDATED Linux kernel to 3.4.113 on 27-10-2016​UPDATED to v2.5 on 13-10-2016​
Code:
Changes in version 2.5
*Unlocked CPU frequencies 1500,300 and 200MHZ
*Switched to self built Linaro/Sabermod toolchain
*Added many more optimization flags
*Added DriveDroid support
Features
-Now supports Many different ROMS for the G800F
-Compiled with self built optimized Linaro/SaberMod toolchain ("LinaroMod")
-Unlocked CPU frequencies: 1500MHZ,200MHZ and 300MHZ
-Updated Linux kernel from 3.4.39 to the latest 3.4.113
-Added many optimizations (You can see all of the optimization flags in the makefile on the kernel source page)
-enabled graphite
-Added Drivedroid Support - http://softwarebakery.com/projects/drivedroid
-Fading LED's
-Added I/O schedulers
-zen
-sio
-fifo
-fiops
-tripndroid
-vr
-Added CPU governors
-zzmoove
-hyper
-alucard
-darkness
-nightmare
-wheatley
-smartassv2
-dancedance
-pegasusq
Click to expand...
Click to collapse
You will need Kernel Adiutor (free from the play store) or similar app capable of allowing you to switch I/O schedulers and
CPU governors in order to be able to change and set those.
I can recommend this.
http://forum.xda-developers.com/android/apps-games/kernel-adiutor-mod-singularity-kernel-t3333549
Click to expand...
Click to collapse
Known Issues
Let me know and I will try to fix them
Click to expand...
Click to collapse
Installation
I HIGHLY recommend that you do a full backup before flashing this kernel.I am not responsible if you lose any or all of your data.BACKUP!!
1.Download the "Spookcity_Kernel-MM"
2.Place the zip onto your phones storage
3.Reboot into recovery (Volume-Up + Home + Power button)
4.Select install
5.Flash the downloaded kernel
6.Go back a few times in TWRP.Select wipe -> Advanced wipe and wipe Dalvic/Art cache and the cache partition
If you do not do this you are very likely to experience strange issues.You have been warned.Do not report problems if you did not do this.
7.Reboot and hopefully enjoy.
Click to expand...
Click to collapse
Downloads
Spookcity_Kernel-MM
Click to expand...
Click to collapse
Sources
Toolchain - https://github.com/Spookcity/Android-Toolchains
Kernel - https://github.com/Spookcity/android_kernel_samsung_kminilte
Click to expand...
Click to collapse
Code:
CHANGELOG
[U]18-06-2017[/U]
-Switched to anykernel2
[U]31-10-2016[/U]
-Added zip for Bliss Rom
[U]13-10-2016[/U]
-Unlocked CPU freq 1500,200,300MHZ
-Switched to my self built toolchain
-Added many more optimization flags to the build
-Added DriveDroid support
-Added zip for Zephyr-OS
[U]24-07-2016[/U]
- Added zips to support more custom ROMS
[U]V2 - 23-07-2016[/U]
-Fixed RAMDISK to make it compatible and actually work with newer builds of CM13
-Changed SELinux from disabled to permissive to be in line with the "stock" CM kernel
-Added I/O schedulers
-fiops
-tripndroid
-vr
-Added CPU governors
-pegasusq
[U]V1 - Initial Release[/U]
Thanks to
-hennymcc and CTXz for bringing CM13 to our device! I used their kernel sources to build this.Without them I never would have been able to attemp this.
-DJ_Steve for his custom kernel.Without being able to look at his sources and cherry-pick some things I would also not have been able to do this.
-CurtisMJ Ditto same thing here.His kernel build and sources were very helpful to me.
-frap129 for his amazing toolchains!
-ArchiDroid
Anyone I may have left out sorry.I appreciate you all!
Click to expand...
Click to collapse
I hope you enjoy and please say thanks if you find this at all useful
XDA:DevDB Information
Spookcity_Kernel, Kernel for the Samsung Galaxy S5 Mini
Contributors
spookcity138
Kernel Special Features:
Version Information
Status: Beta
Created 2016-05-26
Last Updated 2017-06-18
Nice, finally some new development for our phone =)
I will test the kernel right away...
One thing that I would really love would be if you have the time to look into adding DT2W :angel:
Thanks for your work so far :good:
*edit*
booting went well. However WiFi doesnt work for me :/ I uploaded the logcat-output filtered for "wifi" to hastebin. If you need anything else for debugging let me know. Thanks to dual boot I will keep your custom kernel on one ROM
log
zaworka said:
Nice, finally some new development for our phone =)
I will test the kernel right away...
One thing that I would really love would be if you have the time to look into adding DT2W :angel:
Thanks for your work so far :good:
*edit*
booting went well. However WiFi doesnt work for me :/ I uploaded the logcat-output filtered for "wifi" to hastebin. If you need anything else for debugging let me know. Thanks to dual boot I will keep your custom kernel on one ROM
log
Click to expand...
Click to collapse
Thanks for trying out the kernel. That's weird about the WiFi. I have never had that happen in the bunch of times I have flashed it. I will def look into it.I'll have a look at the log, although at this point I'm also not that great at interpreting those, so it may not help. I'll see what I can do though
Sent from my SM-G800F using Tapatalk
can you tell me someone what is kernel?
br3acker said:
can you tell me someone what is kernel?
Click to expand...
Click to collapse
http://www.makeuseof.com/tag/linux-kernel-explanation-laymans-terms/
zaworka said:
Nice, finally some new development for our phone =)
I will test the kernel right away...
One thing that I would really love would be if you have the time to look into adding DT2W :angel:
Thanks for your work so far :good:
*edit*
booting went well. However WiFi doesnt work for me :/ I uploaded the logcat-output filtered for "wifi" to hastebin. If you need anything else for debugging let me know. Thanks to dual boot I will keep your custom kernel on one ROM
log
Click to expand...
Click to collapse
OK,well after looking at the log and trying to decipher it and then thinking a bit I have only come up with one possibility.Maybe somehow your wpa_supplicant.conf file located in /data/misc/wifi/wpa_supplicant.conf has the wrong permissions for some reason.If you want you could try to check and possibly change the permissions.If you decide to try this I would backup the file because you never know.
The permissions should be: Owner - wifi Group - wifi...
Owner read and write/Group read and write/ others none.
If your permissions are correct on that file the only other thing I could possibly think of to do if you wanted would be to delete that file,wpa_supplicant.conf.Only after you back it up it though because you will lose all of your passwords,and reboot.It should recreate it.Do that at your own risk though.This is all I have come up with because I have never had that problem,so it's a bit difficult.
I am sorry, I think the error was my fault and not a bug of the kernel. I think the build that I am running at the moment is one I build myself and used sabermod toolchain. I remembered that I had the same problem using DMPKernel on that build. I thought I was using one of hennymmc's builds by now - so, sorry for reporting but thanks for looking into anyways.
Unfortunately I tried both and didnt solve the issue ,the permissions were set correctly btw.
I just installed the CM13 on another partition but - unless I have a flashable zip file - I can not install your kernel on that one. Would it be possible to provide the kernel as .zip?
zaworka said:
I am sorry, I think the error was my fault and not a bug of the kernel. I think the build that I am running at the moment is one I build myself and used sabermod toolchain. I remembered that I had the same problem using DMPKernel on that build. I thought I was using one of hennymmc's builds by now - so, sorry for reporting but thanks for looking into anyways.
Unfortunately I tried both and didnt solve the issue ,the permissions were set correctly btw.
I just installed the CM13 on another partition but - unless I have a flashable zip file - I can not install your kernel on that one. Would it be possible to provide the kernel as .zip?
Click to expand...
Click to collapse
Sure thing.I updated the download section above and added a flashable zip.I think it'll work.
spookcity138 said:
Sure thing.I updated the download section above and added a flashable zip.I think it'll work.
Click to expand...
Click to collapse
Nice, that worked! Thanks for the effort :good:
Will test it over the next few days :fingers-crossed:
zaworka said:
Nice, that worked! Thanks for the effort :good:
Will test it over the next few days :fingers-crossed:
Click to expand...
Click to collapse
Good,I'm glad that worked.You thoughts and feedback are most welcomed.
Any chance this kernel hits the G800H for cm 13 too ?
I can be your tester
sasukesama said:
Any chance this kernel hits the G800H for cm 13 too ?
I can be your tester
Click to expand...
Click to collapse
Hey, I appreciate the offer. That is something I can look into at some point. No promises. In still trying to learn all of this stuff.
Sent from my SM-G800F using Tapatalk
spookcity138 said:
Hey, I appreciate the offer. That is something I can look into at some point. No promises. In still trying to learn all of this stuff.
Sent from my SM-G800F using Tapatalk
Click to expand...
Click to collapse
Sounds good
I think you can do the same (using the cm13 kernel and DJ_Steve kernel stuff) as he has a G800H version of his kernel
I use your kernel , you can repair the wifi ?
Abde77 said:
I use your kernel , you can repair the wifi ?
Click to expand...
Click to collapse
What's the problem with the WiFi exactly? I need to update this anyway. I will at some point.I've had no WiFi probs though.
Sent from my SM-G800F using Tapatalk
spookcity138 said:
What's the problem with the WiFi exactly? I need to update this anyway. I will at some point.I've had no WiFi probs though.
Sent from my SM-G800F using Tapatalk
Click to expand...
Click to collapse
Conducted any work on the development of the kernel? About sound problems and headphones like DJ_Steve , initially had no problems, and then there., maybe it depends on kernel version? Is there a chance to make all the improvements in version 3.4.39 ? (Google translation)
Oleggluk said:
Conducted any work on the development of the kernel? About sound problems and headphones like DJ_Steve , initially had no problems, and then there., maybe it depends on kernel version? Is there a chance to make all the improvements in version 3.4.39 ? (Google translation)
Click to expand...
Click to collapse
I actually haven't touched this recently at all.I've been spending too much time on the mess that is my AOSP build [emoji2]
I give up on that for now though.It's giving me a headache.
I will try to get back to this soon,as I don't even think it works with any of my builds.I don't know.I'm not even using this right now.
I never actually had any real audio issues with this however and I did use if for awhile,so that's strange.
Sent from my SM-G800F using Tapatalk
spookcity138 said:
I actually haven't touched this recently at all.I've been spending too much time on the mess that is my AOSP build [emoji2]
I give up on that for now though.It's giving me a headache.
I will try to get back to this soon,as I don't even think it works with any of my builds.I don't know.I'm not even using this right now.
I never actually had any real audio issues with this however and I did use if for awhile,so that's strange.
Click to expand...
Click to collapse
Also does not have wi-fi access in the new Assembly СМ13 from ayke with this kernel. I took apart your kernel and replace the ramdisk from the new build, wifi now works. (Google translation)
Oleggluk said:
Also does not have wi-fi access in the new Assembly СМ13 from ayke with this kernel. I took apart your kernel and replace the ramdisk from the new build, wifi now works. (Google translation)
Click to expand...
Click to collapse
I kinda remember this issue as well.Good to know about the ramdisk.
Its such a strange thing how only some experience the robotic voice...and you have no microphone problems with ayke's build either? Like it stops working after a phone call?
Sent from my SM-G800F using Tapatalk
spookcity138 said:
I kinda remember this issue as well.Good to know about the ramdisk.
Its such a strange thing how only some experience the robotic voice...and you have no microphone problems with ayke's build either? Like it stops working after a phone call?
Sent from my SM-G800F using Tapatalk
Click to expand...
Click to collapse
Robot voice I have never had. And mute has the same problem that error camera. If you kill the mediaserver, the microphone performance is restored. You can use the long-known app Mediaserver Killer. (Google translation)

[KERNEL][6+] s1mple espresso

I don't like large threads. My old espresso needs an up, so where we go.
It's based on latest omap4 common by unlegancy-android with these changes:
Compiled with custom Linaro GCC by @Christopher83.
CPU underclocked to 200MHz and overclocked up to 1400MHz.
GPU overclocked up to 512MHz. (384 default)
Custom voltages based on user experience.
Touch boost from franco kernel. (default boost set to 1200MHz)
Mini-FAQ:
Q: It works on all ROMs? Nougat?
R: It should work on any recent ROM who use omap4 common by unlegancy-android.
Q: All variants?
R: Due compatibility issues it could be not work on some devices/combinations, test it.
If won't work, please provide the variant, ROM, TWRP and last_kmsg if possible.
Click to expand...
Click to collapse
Q: Is safe 1400MHz on espresso?
R: Yes, passed my stability tests without problems.
Q: Works with ramdisk mods? (Magisk)
R: Yes, by AnyKernel2.
Code:
Change CPU max clock:
# echo 'x' > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
x = 1080000, 1200000, 1300000, 1400000
Change GPU max clock:
# echo 'x' > /sys/devices/platform/omap/pvrsrvkm.0/sgxfreq/frequency_limit
x = 153600000, 384000000, 512000000
Make boot and system backup before installation, download.
XDA:DevDB Information
s1mple espresso, Kernel for the Samsung Galaxy Tab 2
Contributors
dcastro172, Android-Andi, Ziyan, Sam Nakamura
Source Code: https://github.com/dcastro172/android_kernel_ti_omap4
Kernel Special Features:
Version Information
Status: Testing
Created 2018-04-23
Last Updated 2018-05-05
NICE.....Test It Soon
Didn't work for me
Tried to install it over AICP and just boot looped.
Then I installed ResurectionRemix and installed the kernel and had the same results.
Used TWRP 3.2.0.0
Thanks for trying to give us something new for our old Tab2
Skarni said:
Tried to install it over AICP and just boot looped.
Then I installed ResurectionRemix and installed the kernel and had the same results.
Used TWRP 3.2.0.0
Thanks for trying to give us something new for our old Tab2
Click to expand...
Click to collapse
I checked these ROMs and they use omap4 common, should have worked, maybe a ramdisk issue, to be fair I just tested it with recent OmniROM MM and it's working fine, I will try these.
THANK YOUUU FINALLY A NEW KERNEL HERE...does it work on nougat Roms?
Skarni said:
Tried to install it over AICP and just boot looped.
Then I installed ResurectionRemix and installed the kernel and had the same results.
Used TWRP 3.2.0.0
Thanks for trying to give us something new for our old Tab2
Click to expand...
Click to collapse
I tested today with ResurectionRemix by @smart-t78 and works well, the first boot without s1mple taken so much time, then I switch off and powered on, it booted.
Enrico03 said:
THANK YOUUU FINALLY A NEW KERNEL HERE...does it work on nougat Roms?
Click to expand...
Click to collapse
Yeah, tested with latest Lineage 14.1, however, I found an issue about frequency scaling, it boots with max frequency of 300MHz :laugh:
But you can change it using adb/terminal later.
New build up :fingers-crossed:
Now it's compiled with custom Linaro GCC by @Christopher83
Added touch boost from franco kernel :highfive: (interactive governor only, configurable)
Removed 200MHz in attempt to fix frequency scaling issues
OP updated.
Installed latest OmniRom 6 booted and then installed S1mple kernel. Left it to boot for 1 hour and it never booted. turned off and tried again, not luck.
re-installed my AICP backup.
Might try it with Slim6 when I have some time, but would prefer an unrooted rom since I use netflix.
Skarni said:
Installed latest OmniRom 6 booted and then installed S1mple kernel. Left it to boot for 1 hour and it never booted. turned off and tried again, not luck.
re-installed my AICP backup.
Might try it with Slim6 when I have some time, but would prefer an unrooted rom since I use netflix.
Click to expand...
Click to collapse
Doesn't magisk hide solve the Netflix problem? It should actually...
(sorry for the OT)
-------------------------------
Thanks @dcastro172 a new custom kernel sounds like fun, would be very cool to have something more or less stable with this significant OC added, I'll need to check this out when I'm near to my p5110 soon.. :good:
Sent from my Nexus 7 using XDA Labs
Skarni said:
Installed latest OmniRom 6 booted and then installed S1mple kernel. Left it to boot for 1 hour and it never booted. turned off and tried again, not luck.
re-installed my AICP backup.
Might try it with Slim6 when I have some time, but would prefer an unrooted rom since I use netflix.
Click to expand...
Click to collapse
Did you try with Andi's builds or from official Omni website? espresso3g or wifi? It will only work with recent Andi's builds, I'm running it and works well.
Doesn't boot on latest lineageOS and needs restoring boot & system to get back a working device, here's a demsg.log....
https://drive.google.com/file/d/1cJFmLO-e4lKODHTDYCRNDJ7RfGZK50G0/view?usp=drivesdk
dcastro172 said:
Did you try with Andi's builds or from official Omni website? espresso3g or wifi? It will only work with recent Andi's builds, I'm running it and works well.
Click to expand...
Click to collapse
Yep! Used Andi's unofficlal: omni_espressowifi-6.0.1-20180414-2301.zip
---------- Post added at 01:50 PM ---------- Previous post was at 01:45 PM ----------
Sam Nakamura said:
Doesn't magisk hide solve the Netflix problem? It should actually...
(sorry for the OT)
Click to expand...
Click to collapse
"OT response to close": Only been able to get netflix to work by sideloading on ROM that is unrooted no gapps .
Magisk 16 has been problematic for me. 14 was okay. I would use magisk 14 to root to enable OC on s1mple kernel.
Sam Nakamura said:
Doesn't boot on latest lineageOS and needs restoring boot & system to get back a working device, here's a demsg.log....
https://drive.google.com/file/d/1cJFmLO-e4lKODHTDYCRNDJ7RfGZK50G0/view?usp=drivesdk
Click to expand...
Click to collapse
Skarni said:
Yep! Used Andi's unofficlal: omni_espressowifi-6.0.1-20180414-2301.zip
Click to expand...
Click to collapse
There's something very important which I'm missing, probably a very stupid issue since it works on my P5110, I read the dmesg and didn't see much useful logs, tomorrow I will investigate more. Thanks guys.
dcastro172 said:
There's something very important which I'm missing, probably a very stupid issue since it works on my P5110, I read the dmesg and didn't see much useful logs, tomorrow I will investigate more. Thanks guys.
Click to expand...
Click to collapse
FYI, I have a P3113,
The newer (maybe 2018) are default libion and it is said not to flash any custom kernels as they are not compatible.... So is this the reason some people have some trouble?
Excellent! Finally a overclockable kernel for our devices! Thank you very much Mr. dcastro172! Will test and report here ASAP!
drunkbum said:
The newer (maybe 2018) are default libion and it is said not to flash any custom kernels as they are not compatible.... So is this the reason some people have some trouble?
Click to expand...
Click to collapse
Well, recent ROMs with updated repos from unlegancy/lineageos builds with standard libion by default, my fork will only work with standard libion, some outdated ROMs use TI's libion and will not work, I think it's not the issue since @Skarni tried with latest OmniROM from @Android-Andi (which use standard libion) and won't worked for his P3113 while my P5110 woks perfectly.
And the dmesg from @Sam Nakamura is not much useful why it's from his reboot after the bootloop, I thought it has a SELinux issue but it's not, however I looked at second line and it looks like an old official build:
Code:
<5>[ 0.000000] Linux version 3.0.101-gbb24628 ([email protected]) (gcc version 4.8 (GCC) ) #1 SMP PREEMPT Sat Dec 9 09:46:13 UTC 2017
I'm trying figure it by looking at unlegancy/lineageos commits if I'm missing something but no luck yet.
galoneta said:
Excellent! Finally a overclockable kernel for our devices! Thank you very much Mr. dcastro172! Will test and report here ASAP!
Click to expand...
Click to collapse
Make sure do a backup why people are running in boot issues, if you run in boot issue please take a "cat /proc/last_kmsg > /sdcard/kmsg.txt" in TWRP terminal.
dcastro172 said:
And the dmesg from @Sam Nakamura is not much useful why it's from his reboot after the bootloop, I thought it has a SELinux issue but it's not, however I looked at second line and it looks like an old official build:
Click to expand...
Click to collapse
Not sure why the log referenced this old build, as said before I'm actually on the latest official lineageOS build from 11th February 2018 as seen on the screenshot.
I gladly provide more logs if you tell me exactly what could be of use for you...
Edit: the referenced kernel version is the one included in TWRP, check the build dates from official twrp.me and the log reference....
https://dl.twrp.me/espressowifi/
Sent from my OnePlus 3T using XDA Labs
Sam Nakamura said:
Not sure why the log referenced this old build, as said before I'm actually on the latest official lineageOS build from 11th February 2018 as seen on the screenshot.
I gladly provide more logs if you tell me exactly what could be of use for you...
Edit: the referenced kernel version is the one included in TWRP, check the build dates from official twrp.me and the log reference....
https://dl.twrp.me/espressowifi/
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
Oh, this should explain, but you was using a different kernel when you flashed it?

[Kernel] SMF-KERNEL - RR/AICP/LOS/AOSP - 8.1

Hello!
I want to introduce my first custom kernel for the Essential PH-1. This is based of several sources, I cherry-picked commits to make improvements to the stock LOS kernel. I'm not a developer, but i really like to port stuff over .
Kernel is suitable for AOSP based ROMS such as RR/AICP/CARBON/LOS etc... If you want to request for specific features, let me know and i'll do my best to bring them over.
Special Features:
Updated to lastest LOS Stock Kernel
Added a few governors like: cultivation / impulse
added a few IO Schedulers: Maple
Kcal Color Control driver
USB Fast Charge - pending will be added in R2
SafetyNet Patch (Bypass bootloader unlocked check)
Dynamic Fsync control
a little Overclock - will be added in R2
Motorola Quickwake - Will be added in R2
and manny other small fixes (you can check the commits in the sources)
Download
Disclaimer: I am not responsible if you use this and brick your device or if your device blows up, implodes, flames start shooting from it or it kills your neighbor's dog. Flash at your own risk. I am not responsible.... It was the other guy... I swear....
Latest Release: SMF-Kernel R2
Known issues:
05.17.2018 - CPU Freq don't always stick, known issue caused by other drivers. Phone will eventually set your frequencies, dont' panic.
Installation:
Obviouly you have a Unlocked Bootloader since you're running a custom rom (make sure to never lock your bootloader in this state)
Boot into Bootloader (adb reboot Bootloader)
If you want to root flash the "Magisk" version of the kernel, it's been prerooted with the latest Magisk Beta available.
Code:
fastboot flash boot SMF-Kernel-R1-Magisk.img
reboot
If you want to manually root, first flash twrp, then from twrp flash the 'non magisk' version and after that flash the magisk zip.
Special Thanks to:
jcadduono
franciscofranco
bedalus
lord_boeffla
flar2
sultanxda
...and many others from whom i cherry pick commits... Sorry if I forgot to mention anyone!
XDA:DevDB Information
SMF-KERNEL, Kernel for the Essential Phone
Contributors
jimbo77
Source Code: https://github.com/Jimbo77/android_kernel_essential_msm8998
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: R1
Stable Release Date: 2018-05-17
Created 2018-05-17
Last Updated 2018-05-17
Changelog 05.23.2018
Enabled Motorola QuickWake Driver - This will enable system to do checks or syncs without fully resuming the device, main objective is battery life.
Enabled Dynamic Sync Control by default
OverClock
USB Fast Charge to up 900ma (Original is 500ma)
Disabled Gentle Fair Sleepers
Enabled Boefla Wakelocks - Check the ammount of wakelocks you can block now!
Enabled Wireguard
Enabled several TCP Options - "Westwood" is enabled by default
Min/Max Brightness options is now configurable as well, to avoid the screen go too dim or to bright.
Somehow camera has been fixed! haha
Changelogs 05.17.218
Updated to lastest LOS Stock Kernel
Added a few governors like: cultivation / impulse
added a few IO Schedulers: Maple
Kcal Color Control driver
SafetyNet Patch (Bypass bootloader unlocked check)
Dynamic Fsync control
and manny other small fixes (you can check the commits in the sources)
Reserved
Looks awesome! I'll give it a try soon!
(For anyone wondering about overclocking the CPU, he committed some changes to the github that would apply this and it should appear in the next revision of the kernel.)
Just installed and so far it's buttery smooth.
WARpig5 said:
Just installed and so far it's buttery smooth.
Click to expand...
Click to collapse
I'm glad is running fine for you!
Good stuff, thanks for this! Could you tell me a little more about cultivation? I can't seem to find much information online about it
Also a request, if possible vibration level control would be super appreciated
pantherking said:
Good stuff, thanks for this! Could you tell me a little more about cultivation? I can't seem to find much information online about it
Also a request, if possible vibration level control would be super appreciated
Click to expand...
Click to collapse
I found Cultivation to be really great in terms of perfornance. It's a little bit agressive with the CPU so you get buttery smooth experience with Screen On but it may cost a few % on battery at the end of the day. The good thing is that it has specific tunables and you can set a low cpu freq for when the screen is off.
Specific details from its developer:
-based off of caf 4.4 commits
-uses per-pcu timers
-use state_notifier for screen off timer
option to set different timer rate when screen off
-improrted fastlane with threshold from blu_active
In regards of vibration control. It should be there. I'm using EX Kernel Manager and i can see the vibration option under "Miscellaneous"
jimbo77 said:
I'm glad is running fine for you!
Click to expand...
Click to collapse
Thanks for this. It's running amazing so far. Performance has been great and I'll see how battery life is, but so far it's great.
I can't wait for further updates. I really wanna see what Moto quickwake is haha
jimbo77 said:
In regards of vibration control. It should be there. I'm using EX Kernel Manager and i can see the vibration option under "Miscellaneous"
Click to expand...
Click to collapse
Thanks for the info on cultivation, I don't mind trading some battery life for butter so I'm using it now
For the vibration control, it doesn't actually work/stick. I've tried kernel auditor and EX Kernel Manager. To be fair, so far it has only worked on LOS and I think invisiblek may have rewritten the stock controller or something so no worries if it isn't a high priority haha
pantherking said:
Thanks for the info on cultivation, I don't mind trading some battery life for butter so I'm using it now
For the vibration control, it doesn't actually work/stick. I've tried kernel auditor and EX Kernel Manager. To be fair, so far it has only worked on LOS and I think invisiblek may have rewritten the stock controller or something so no worries if it isn't a high priority haha
Click to expand...
Click to collapse
I'll take a look at the latest commits but I've used the latest los kernel base so I'm not sure why is not sticking maybe it needs rom support too (not sure honestly) hahaha
I've been testing R2 since yesterday. Will update after y he weekend!
Just out of curiosity, was anything involving the camera done to this kernel? I am now able to record videos without the bug, on any of the affected ROMs, with this kernel.
stompysan said:
Just out of curiosity, was anything involving the camera done to this kernel? I am now able to record videos without the bug, on any of the affected ROMs, with this kernel.
Click to expand...
Click to collapse
Nothing related to camera. Are you sure it works with no issues?
What roms have you tested?
jimbo77 said:
Nothing related to camera. Are you sure it works with no issues?
What roms have you tested?
Click to expand...
Click to collapse
So far, AICP and LOS, both with Essential camera app and GCAM port, HD and 4K, 30 and 60 fps where applicable. Issues presented before flashing very consistently, and so far I have been unable to replicate after flashing this kernel.
stompysan said:
So far, AICP and LOS, both with Essential camera app and GCAM port, HD and 4K, 30 and 60 fps where applicable. Issues presented before flashing very consistently, and so far I have been unable to replicate after flashing this kernel.
Click to expand...
Click to collapse
Sp you were right. Honestly don't know what happened but I installed the latest RR (clean install) put R2 on top of it and bam recording works as you mentioned lol..
I guess it was a lucky strike!
after flashing the kernel with magisk, stuck on "AICP is starting"
is this normal?
update: the phone works but no magisk (pre root) after flashing the kernel.....
sinkoo1979 said:
after flashing the kernel with magisk, stuck on "AICP is starting"
is this normal?
update: the phone works but no magisk (pre root) after flashing the kernel.....
Click to expand...
Click to collapse
Hey!
Have you booted once and setup everything before flashing the prerooted image?
I've had that error but having all set and then flashing the image will get me rooted. Try to see if you can find magisk manager in the apps list from the settings if you do, reboot and there will be magisk
Double post... Sorry
jimbo77 said:
Hey!
Have you booted once and setup everything before flashing the prerooted image?
I've had that error but having all set and then flashing the image will get me rooted. Try to see if you can find magisk manager in the apps list from the settings if you do, reboot and there will be magisk
Click to expand...
Click to collapse
Thank you for the reply.
the phone was running AICP and I wanted root so I flash the kernel. I can't find the magisk manager or in the settings about magisk. I guess you have to clean install from the beginning to get the root. Thank you for the Kernel
sinkoo1979 said:
Thank you for the reply.
the phone was running AICP and I wanted root so I flash the kernel. I can't find the magisk manager or in the settings about magisk. I guess you have to clean install from the beginning to get the root. Thank you for the Kernel
Click to expand...
Click to collapse
Shouldn't. If you flashed the prerooted magisk image try downloading the magisk manager app manually from xda and see if magisk works

[KERNEL] [10/Q] Galts Gulch Kernel [4.9.206]

This is a kernel for Q. Can be flashed in FK, sideloaded in booted TWRP, or pushed to /tmp/ and flashed in booted TWRP.
- Q source with upstream Linux kernel 4.9.x merged and elementalX by flar2 merged. Upstream Linux kernel updates merged regularly.
- Many optimizations by sultanxda, kdragon, and many others. Idle frequency scaling also improved.
- HBM, Klapse, KCAL, backlight dimmer, and all features of elementalX. Note: some defaults changed from elementalX, such as CFQ back to default for overall performance, and also reverted the kgsl high priority commits as they do more harm than good.
- Westwood tweaks + set as default.
- Unlike many others, kept LTO and CFI enabled.
- LZMA supported (for twrp installation on Q custom roms)
Installation. For updating, just follow last point:
- Recommend having stock magisk patched boot image prior (magisk will be kept through all updates).
- Flash in FK or EX app using manual flasher, or flash in booted TWRP through one of the methods listed in first sentence.
NOTE: Will work on stock or any AOSP December build. Any LineageOS build or build by Stebomurkn will not work, and if it does, will not be supported.
Links
Telegram Group for Support and Faster Releases
Kernel Install Zip
Source
Any reports on functionality of kernel?
oranget said:
Any reports on functionality of kernel?
Click to expand...
Click to collapse
Check Github.
New build posted, just merged with upstream 4.9.194 released today.
Hey can you get me a boot.img of this? Is that all thats required to flash in fastboot? TWRP isn't working for Android 10, or so I heard...
Thanks!
Magnetox said:
Hey can you get me a boot.img of this? Is that all thats required to flash in fastboot? TWRP isn't working for Android 10, or so I heard...
Thanks!
Click to expand...
Click to collapse
You can use Franco Kernel Manager to flash it.
Sent from my Google Pixel 3a XL using XDA Labs
Skittles9823 said:
You can use Franco Kernel Manager to flash it.
Sent from my Google Pixel 3a XL using XDA Labs
Click to expand...
Click to collapse
You can also use ElementalX app to flash it.
Just updated, merged with new C3 release changes.
oranget said:
You can also use ElementalX app to flash it.
Click to expand...
Click to collapse
True, but FKM is more reliable since osm0sis (the guy who made AnyKernel2/3) helped implement the auto flasher in FKM. I'm not sure about the EX one whether osm0sis helped him too or if flar did everything himself.
Sent from my Google Pixel 3a XL using XDA Labs
Skittles9823 said:
True, but FKM is more reliable since osm0sis (the guy who made AnyKernel2/3) helped implement the auto flasher in FKM. I'm not sure about the EX one whether osm0sis helped him too or if flar did everything himself.
Sent from my Google Pixel 3a XL using XDA Labs
Click to expand...
Click to collapse
EXKM is fine. I even have this device.
Support Havoc OS?
a1234kitkit said:
Support Havoc OS?
Click to expand...
Click to collapse
I was wondering the same.
Can flash but no wifi
Seeing as the AFH/XDA builds were like 10 releases behind, I finally updated on here. Also added a note about LOS or stebomurkn builds.
For faster releases and better support, you may join the Telegram group posted in OP.

[KERNEL][10.0] nysa's pixel 3 kernel

nysa's pixel 3/3xl kernel builds​
- Based on latest Android security patch from Google (30/06: 4.9.210)
- TCP BBR backports
- RCU, QoS and other subsystem backports
- 4.19 PELT load tracking
- Static image display power saving features
- Mainline scheduler backports to fix CAF mess
- CAF boosting removed
- kerneltoast's Simple Low Memory Killer
- Built with Proton Clang 11
- Other things that I can't remember
I'd highly recommend you use my Magisk module with this kernel to improve battery life and task placement: https://github.com/nysascape/pixel3-xl-powerhint
Be sure to join my Telegram channel: https://t.me/nysascapetg
Feel free to donate me a coffee: https://paypal.me/nysa17
Downloads:
Google Drive (boot.img, fkm zip)
My server
Franco Kernel Manager config for auto updates
Source:
https://github.com/nysascape/kernel_google_msm-4.9
Prebuilts:
https://github.com/nysascape/device_google_crosshatch-kernel
how do you install the magisk module?
and best way to install kernel?
thanks
BHermes21 said:
how do you install the magisk module?
and best way to install kernel?
thanks
Click to expand...
Click to collapse
Magisk patch the image through Magisk manager then use fastboot to flash it, using fastboot flash boot (name).img
When you've installed Magisk, just download the module and go into Manager and add it to modules.
does it support hbm?
high brightness mode
Your magisk module helps pixel 3 cool down a lot and save more power
I really appreciate.
gacky1601 said:
Your magisk module helps pixel 3 cool down a lot and save more power
I really appreciate.
Click to expand...
Click to collapse
Is the module for use with nysa kernel only?
mgp53 said:
Is the module for use with nysa kernel only?
Click to expand...
Click to collapse
you can use it on any kernel : )
gacky1601 said:
you can use it on any kernel : )
Click to expand...
Click to collapse
i doubt this is the case. the kernel would need to support the tuning parameters of the magisk module
drdrewdown said:
i doubt this is the case. the kernel would need to support the tuning parameters of the magisk module
Click to expand...
Click to collapse
Not true. The magisk module affects the powerhint.xml file which tells your power HAL what frequencies to boost your cpu/gpu to on certain tasks. It can be used with any kernel, I don't tweak anything that isn't part of the stock kernel
Edit: even this was misworded slightly, this tweak is completely independent of the kernel itself, and actually touches nothing inside the kernel.
hi there flashed your kernel with fkm....rebooted fine.....but now the screen does not respond to my touches. so i cant login with my passcode now what reflash a whole new system? help please
wulfgarfang said:
hi there flashed your kernel with fkm....rebooted fine.....but now the screen does not respond to my touches. so i cant login with my passcode now what reflash a whole new system? help please
Click to expand...
Click to collapse
That's strange, well just reflash Google's stock kernel. I haven't had this issue to be honest, if you're not using a June dtbo that could be the issue
nysascape said:
That's strange, well just reflash Google's stock kernel. I haven't had this issue to be honest, if you're not using a June dtbo that could be the issue
Click to expand...
Click to collapse
I have the same issue with the factory firmware. Flashing the regular boot.img did not solve the issue. Edit: flashing dbto.img as well did.
---------- Post added at 04:13 PM ---------- Previous post was at 03:44 PM ----------
wulfgarfang said:
hi there flashed your kernel with fkm....rebooted fine.....but now the screen does not respond to my touches. so i cant login with my passcode now what reflash a whole new system? help please
Click to expand...
Click to collapse
Did you flash 17-5-20.img, I did too by accident?
RagedElimanator said:
I have the same issue with the factory firmware. Flashing the regular boot.img did not solve the issue. Edit: flashing dbto.img as well did.
---------- Post added at 04:13 PM ---------- Previous post was at 03:44 PM ----------
Did you flash 17-5-20.img, I did too by accident?
Click to expand...
Click to collapse
Try flashing the dtbo found in the FKM zip.
Same issue as above, PixelDust CAF july 2020.
No touch in system or recovery, flashed via FKM bc TWRP boots and nothing else lol
unixandria said:
Same issue as above, PixelDust CAF july 2020.
No touch in system or recovery, flashed via FKM bc TWRP boots and nothing else lol
Click to expand...
Click to collapse
I had this same issue so, I decided to dirty flash the stock rom and touchscreen started working, flashed using FKM and once again touchscreen did not work.
I dirty flashed the stock rom once again, grabbed the IMG file and flashed it in fastboot and everything worked.
webleeper said:
I had this same issue so, I decided to dirty flash the stock rom and touchscreen started working, flashed using FKM and once again touchscreen did not work.
I dirty flashed the stock rom once again, grabbed the IMG file and flashed it in fastboot and everything worked.
Click to expand...
Click to collapse
I'm sure that works great on stock
However I'm not on stock as I already said
unixandria said:
I'm sure that works great on stock
However I'm not on stock as I already said
Click to expand...
Click to collapse
The point was to not use FKM but fastboot flash instead
webleeper said:
The point was to not use FKM but fastboot flash instead
Click to expand...
Click to collapse
Fastboot flash the boot image that won't work? Sounds great! I'll get on that
Hi is the kernel support android 11 ? Could this kernel use swap function?
unixandria said:
I'm sure that works great on stock
However I'm not on stock as I already said
Click to expand...
Click to collapse
Yeah most other kernels on here have one for stock an one for custom.
But works great for stock.

Categories

Resources