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
Runs great! Sooo smooth.
Also has color control and kcal and low brightness and HBM and they are all working well.
Thanks!
New version uploaded.
- Tons of sultanxda changes -- scheduler, cleanups.
- Tweaked defaults
- Upstream 4.9.192 merged.
So, I'm confused, how does this have TWRP support if TWRP isn't working on Android 10 yet? Did I miss the release?
Is there a 3a version or just 3a xl?
jayyskittles said:
So, I'm confused, how does this have TWRP support if TWRP isn't working on Android 10 yet? Did I miss the release?
Click to expand...
Click to collapse
TWRP support just means that you are able to flash it through TWRP using adb sideload or by flashing it once the zip is in data/local/tmp .
jayyskittles said:
So, I'm confused, how does this have TWRP support if TWRP isn't working on Android 10 yet? Did I miss the release?
Click to expand...
Click to collapse
I meant that it will allow twrp installation on custom Q ROMs with LZMA support. For twrp installation, it requires LZMA support kernel side (what that bullet point was for) and LZMA support device tree side (same as Pie did).
HighDesertTrekker said:
Is there a 3a version or just 3a xl?
Click to expand...
Click to collapse
It should work on both devices.
johngalt1 said:
It should work on both devices.
Click to expand...
Click to collapse
Yes, kernel source and virtually all of the device source is the same for both.
New build posted. Many changes (block and optimized sha256/512 crypto), and merged with newly released 4.9.193
New build posted, just merged with upstream 4.9.194 released today.
can't install it on android 10 as TWRP is uninstallable
You should not be so affirmative. TWRP is not the only way to flash a kernel. You have plenty of tools, I use FKU which works flawlessely with Android 10
https://play.google.com/store/apps/details?id=com.franco.kernel&hl=en_US
AJ said:
can't install it on android 10 as TWRP is uninstallable
Click to expand...
Click to collapse
As DarkAdrian said there are other methods. However you can also fastboot boot twrp.img, then either adb push the zip to /tmp/ and flash, or go to sideload in twrp, and adb sideload installzip
Just updated, merged with new C3 release changes.
In the OP you say to flash using FK, is using EX to flash okay too? Are they even different?
Playe said:
In the OP you say to flash using FK, is using EX to flash okay too? Are they even different?
Click to expand...
Click to collapse
I have both FKM and EXKM, I use FKM primarily now and as far as I can tell there are no credits for the flasher in EXKM so I assume @flar2 wrote the implementation by himself. In FKM on the other hand, @osm0sis wrote the flasher. As osm0sis is the developer for AnyKernel2/3 I'd say (without being able to confirm anything, so take my words with a grain of salt) that the flasher in FKM would be more reliable. That's however not to say that the flasher in EXKM is any worse, it's just a different implementation.
But personally I like having the added comfort of knowing osm0sis wrote the flasher in FKM.
Sent from my Google Pixel 3a XL using XDA Labs
Skittles9823 said:
I have both FKM and EXKM, I use FKM primarily now and as far as I can tell there are no credits for the flasher in EXKM so I assume @flar2 wrote the implementation by himself. In FKM on the other hand, @osm0sis wrote the flasher. As osm0sis is the developer for AnyKernel2/3 I'd say (without being able to confirm anything, so take my words with a grain of salt) that the flasher in FKM would be more reliable. That's however not to say that the flasher in EXKM is any worse, it's just a different implementation.
But personally I like having the added comfort of knowing osm0sis wrote the flasher in FKM.
Sent from my Google Pixel 3a XL using XDA Labs
Click to expand...
Click to collapse
I wrote the flasher for EXKM and I believe it to be a superior implementation.
flar2 said:
I wrote the flasher for EXKM and I believe it to be a superior implementation.
Click to expand...
Click to collapse
I've been using the flasher in EXKM for a while now with no issues. The options in the app line up better with the features in this kernel too.
Playe said:
In the OP you say to flash using FK, is using EX to flash okay too? Are they even different?
Click to expand...
Click to collapse
The reason for this wasn't a jab at Flar2 or anything (he's a legend), but early on a telegram user reported that exkm flasher didn't work for them.
Since so many have said it works fine, I'll update the OP.
Related
This is the new refined home for DarkRoom Development. If you submit bug reports without a log, you may be prosecuted...or executed.
Disclaimer:
If your device fails to comply with your standards of what you consider functioning, I am not liable. This is provided free of charge and does not come with a warranty. Although, if you provide a log, I can provide some sort of assurance that I will look into your issue.
Links:
Social:
Twitter - http://twitter.com/DespairDev
G+ Community - https://plus.google.com/u/0/communities/117685307734094084120
Downloads:
Google Drive – https://drive.google.com/drive/folders/0Bwcofov-xyI0ZVhQUWJhMm9PMkU
Source:
Github – https://github.com/DespairFactor/
Github – https://github.com/UBERROMS/
Credits:
faux123
franco
Google
flar2
imoseyon
Cl3Kener
neobuddy89
Star Wars
XDA:DevDB Information
[KERNEL][OOS]Tyranus Kernel, Kernel for the OnePlus 3T
Contributors
mdalexca
Kernel Special Features:
Version Information
Status: Testing
Created 2016-11-26
Last Updated 2017-01-13
TWRP
I have uploaded a beta TWRP to my google drive folder, I currently only recommend booting it, and not flashing.
UPDATE: TWRP fully works(you can flash it to your recovery partition) on the 3.5.3 version of OOS, if you are on 3.5.1, I recommend boot TWRP only.
Code:
fastboot boot twrp.img
Does this require a root?
Download Kernel onto 3T
Download Twrponto Computer
Put 3T into Fastboot
Run Fastboot boot Twrp.img
Reboot bootloader
Use temp Twrp to flash kernel????
ghettopops said:
Does this require a root?
Download Kernel onto 3T
Download Twrponto Computer
Put 3T into Fastboot
Run Fastboot boot Twrp.img
Reboot bootloader
Use temp Twrp to flash kernel????
Click to expand...
Click to collapse
You do not need root, but you can root if you wish. I suggest fastboot boot twrp, then flash sr4 supersu followed by kernel zip.
Nice job,bud
Anything special with the kernel?
c_86 said:
Anything special with the kernel?
Click to expand...
Click to collapse
This is the initial release.Features/improvements will follow.
You can always keep track of the changes made to the kernel here-> https://github.com/mdalexca/OP3/
c_86 said:
Anything special with the kernel?
Click to expand...
Click to collapse
Right now, GCC6, makefile changes, power efficient workqueues, some patches from pixel for using kthreads, kcal, backlight dimmer, frandom, tried to lower load average a bit too. I also added a couple IO schedulers and disabled crc on mmc device.
Thank you very much for this.
3.5.3 has issues with off screen gestures because they updated the panel firmware, I will look for a temp fix until they release the source
Good thing I hate gestures
R3 is up, I am working pretty heavily on this, I literally release a build and remember I forgot something nice
mdalexca said:
R3 is up, I am working pretty heavily on this, I literally release a build and remember I forgot something nice
Click to expand...
Click to collapse
Did you get gestures working?
Sent from my OnePlus3T using XDA Labs
dustin_b said:
Did you get gestures working?
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
I haven't had the time yet. I think we can at least implement a kernel level dt2w on it if we need to. I will try to look in a bit, feel free to contact me on hangouts as well if you use that.
mdalexca said:
I haven't had the time yet. I think we can at least implement a kernel level dt2w on it if we need to. I will try to look in a bit, feel free to contact me on hangouts as well if you use that.
Click to expand...
Click to collapse
I think I know where the fix is. Just have to get home to test it. I don't use hangouts. Can I pm you on freenode later?
Sent from my OnePlus3T using XDA Labs
dustin_b said:
I think I know where the fix is. Just have to get home to test it. I don't use hangouts. Can I pm you on freenode later?
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
Yeah for sure, I am leaving myself on the TWRP channel
I installed the kernel earlier and I miss the off screen gestures, do you have a stock kernel compiled? Thanks, keep up the good work.
antnyhills said:
I installed the kernel earlier and I miss the off screen gestures, do you have a stock kernel compiled? Thanks, keep up the good work.
Click to expand...
Click to collapse
I actually have one compiling with the fix and some other patches
R7 is released
Code drop for 3.5.3
https://github.com/OnePlusOSS/android_kernel_oneplus_msm8996/commit/13ae6c1cc45e1cb845d7c0d18da8a59be824b509
Hi OnePlus 5 peeps!
Today (June 27th), I graduated from high school!
In more important news, I finished upstreaming the OnePlus 5 kernel to the latest stable kernel version...
Whoa, what is this?
This is my personal kernel that I run as the OnePlus 5 is my daily driver.
I will not claim my work as the best at anything, but just know that I would not do anything to this kernel that could potentially ruin my own device.
Additionally, this is the kernel that comes built into CarbonROM.
There are three versions of this kernel:
AOSP aka AOSP/LOS build - Flash this on any source built custom ROM except for CarbonROM
CR-5.1 aka CarbonROM build - Flash this on CarbonROM
OOS aka OxygenOS build - Flash this version on OxygenOS
Main features:
Upstreamed Linux kernel version, went from v4.4.21 -> v4.4.79
Backported random driver from Linux v4.12 (latest and greatest)
Backported scheduler from Linux v4.9 (latest android kernel branch)
Upstreamed F2FS driver from f2fs-stable/linux-4.4.y
KGSL driver improvements
MDSS driver improvements
SOC driver improvements
Built using Optimization Level 2
Added maple io scheduler (default) by frap129
Added adreno idler by arter97 with tweaks from frap129
Vibrator motor control by flar2
Kcal control driver from EX kernel
Many wakelocks disabled
Switched to power efficient workqueues across the kernel
Built with Google's latest stable gcc-4.9
Anykernel 2.0 by osm0sis! Compatible with all OxygenOS based roms
Download:
Latest builds
OxygenOS boot.img
How to install:
1. Reboot into the latest stable TWRP build
2. Download kernel zip and make sure it is in your internal storage (/sdcard)
3. Reboot into TWRP
4. Double check here to see if you require any additional instructions
5a. Install -> Install image -> select oxygen-4.x.x-boot.img -> swipe to install
5b. Install -> select CarboniteKERNEL-XXX-Rx-OP5-N.zip -> swipe to install
6. Reboot
DISCLAIMER!
If you don't understand my instructions, that's too bad >
If you are unsure about what this thing is, I highly advise you do some research before going through with installing...
Updates will come as regular as I want them to, don't ask me when I'll release cause you'll know when it comes out >:'D
XDA:DevDB Information
CarboniteKERNEL for the OnePlus 5, Kernel for the OnePlus 5
Contributors
adinkwok, nathanchance, flar2, Lord Boeffla, osm0sis, etc
Source Code: https://github.com/adinkwok/oneplus5-kernel
Kernel Special Features: One of Taylor Swift's exes should write a song called "Maybe You're the Problem"
Version Information
Status: Testing
Created 2017-06-28
Last Updated 2017-08-02
While this reserved post is not being used, enjoy this video! (Find me at 0:50s and twice at 2:54 :silly
For OxygenOS users:
Code:
[B]If you are on OxygenOS and are coming from another custom kernel:[/B]
Download the latest stock.4.X.X-boot.img
You [B]must[/B] flash the boot.img before flashing the kernel!
[B]If you are on OxygenOS are switching to a different custom kernel:[/B]
Download the latest stock.4.X.X-boot.img
You [B]must[/B] flash the boot.img before switching kernels!
For AOSP/LOS/RR/etc users:
Code:
[B]If you are coming from another custom kernel:[/B]
You [B]must[/B] reflash your ROM build before flashing this kernel!
[B]If you are on AOSP/LOS/RR/etc and are switching to another custom kernel:[/B]
You [B]must[/B] reflash your ROM build before flashing another kernel!
Why is it like this?
I have included some ramdisk modifications that set the default settings for this kernel. When you come from a different custom kernel, the ramdisk changes from that kernel may conflict with the changes I intend to have. Likewise when you switch to a different kernel; my ramdisk changes may conflict with the changes they intend to have. When you flash the stock boot.img, it replaces the modified ramdisk with a clean one, removing these conflicts.
And it's here, get it while it's hot folks! First upstreamed kernel for the OP5
Thanks for joining the party :highfive:
Sent from my OnePlus5 using XDA Labs
gz on graduating! and thx for the kernel :=
Congratulations on the graduation buddy,
Just flashed and I had charging cycling on and off (using dash charger in car on freedom v1.1). Flashed EX and charging is fine. Need charge ATM but maybe a little later I can help you get a log.
Sent from my OnePlus5 using XDA Labs
congratulations! awesome... so smart!!!!!!!
rav101 said:
Congratulations on the graduation buddy,
Just flashed and I had charging cycling on and off (using dash charger in car on freedom v1.1). Flashed EX and charging is fine. Need charge ATM but maybe a little later I can help you get a log.
Sent from my OnePlus5 using XDA Labs
Click to expand...
Click to collapse
Hmmm never noticed this... I guess the graduation drinks are getting to me. I'll re-upload a stable build without upstreaming as that's definitely the culprit.
What an amazing day for you (Congratulations!) and the OP5 community!
I was really loving and enyoing all your efforts you did for the OPO (Pure Nexus port) and the amazing Carbon ROM.
adinkwok said:
Hmmm never noticed this... I guess the graduation drinks are getting to me. I'll re-upload a stable build without upstreaming as that's definitely the culprit.
Click to expand...
Click to collapse
I'm the first to report so let's see if anyone else has the same issue. I will also try for logs later on though I do have a lot on today (so might be this evening).
I didn't actually reboot or get to try a different charger to help diagnose so don't want you doing more work that you need to for what could me my issue
Sent from my OnePlus5 using XDA Labs
rav101 said:
I'm the first to report so let's see if anyone else has the same issue. I will also try for logs later on though I do have a lot on today (so might be this evening).
I didn't actually reboot or get to try a different charger to help diagnose so don't want you doing more work that you need to for what could me my issue
Click to expand...
Click to collapse
I can confirm the issue because while I was bringing up the upstream branch I ran into this issue with dash charging and I thought I solved it. Time to debug!
Edit: link updated without the upstreaming, everything else still stands though
adinkwok said:
I can confirm the issue because while I was bringing up the upstream branch I ran into this issue with dash charging and I thought I solved it. Time to debug!
Edit: link updated without the upstreaming, everything else still stands though
Click to expand...
Click to collapse
No problem buddy,
Be good once it's all resolved and we have the benefits of upstream kernel code as well!! Your time and effort is appreciated!
Sent from my OnePlus5 using XDA Labs
@rav101 happy to see u around buddy
dukat0s said:
@rav101 happy to see u around buddy
Click to expand...
Click to collapse
For sure my friend.
How you finding the OP5?
Sent from my OnePlus5 using XDA Labs
rav101 said:
For sure my friend.
How you finding the OP5?
Click to expand...
Click to collapse
Cool my friend !like it.just got rid of my s8+. Was bored
Is DT2W working for you guys?
bartelamo said:
Is DT2W working for you guys?
Click to expand...
Click to collapse
Seems to be a problem among a few custom built kernels, we're looking into it.
bartelamo said:
Is DT2W working for you guys?
Click to expand...
Click to collapse
adinkwok said:
Seems to be a problem among a few custom built kernels, we're looking into it.
Click to expand...
Click to collapse
It's because OOS has a hal that already uses a switch for dt2w.
New update, still looking into the gestures issue.
However, Dash Charging is fixed on the upstream kernel so here it finally is! I also added a bunch of sched patches, a thermal patch, and some other misc stuff from the latest CAF branch.
Adin-Kernel-R2-OP5-OOS-N.zip
README!!!
I'm in China right now, so won't show up at XDA very frequently. If you encounter any bugs, please leave an issue on GitHub
Introduction
This is a personal kernel for Pixel 2 aka walleye. The central goal for it is to provide overall performance improve without any more power consumption than stock kernel. It also allow you to modify the device in your own style, such as charge control.
Important
I'm not responsible for any damage caused by this kernel. Since I'm not even a XDA recognized developer, this kernel might be potentially harmful to your device.
Featrues
Catch up the latest Linux upstream
Catch up the latest EAS
BFQ added
CRNG random driver (from linux-mainline, 10x+ faster)
Wakelock control
AC Charging current control (current up to 3200mah)
Tunable USB fast charge
Some more TCP algorithms (westwood as default)
Use power efficient workqueues for several subsystems
Force SElinux in Permissive mode
SafetyNet patch included
GPU underclocked (180MHz)
Compiled by clang 5.0
Be able to *see* CPU voltage table
Some misc improve
HBM mode support
Adreno Boost support
WireGuard support
KCAL control
Wakeup Gestures (From EXKernel)
Some guides
Kernel Manager
Personally recommend EX Kernel Manager and KernelAdiutor
AC Charging current control
Google implement a feature to adjust charging current based on battery voltage and temperature, if you want to turn it off, use command
Code:
echo N > /sys/module/htc_battery/parameters/enable_ibat_adjust
Turn it on by
Code:
echo Y > /sys/module/htc_battery/parameters/enable_ibat_adjust
They also capped the max current to 2700ma, if you want to change it, use those two command
Code:
echo Y > /sys/module/htc_battery/parameters/enable_custom_fcc_ma
Code:
echo *the value you want* > /sys/module/htc_battery/parameters/custom_fcc_ma
Haptic strength control
Stock driver supports haptic strength control through altering the voltage like this. (Default value is 165)
Code:
echo *the value you want*> /sys/bus/i2c/devices/i2c-6/6-005a/od_clamp
Gonna map this to the common node so we can use kernel manager like EXKM to control
Changelog
R5:
[*]Linux 4.4.109 code merged
[*]Catch up to Jan's update
[*]Misc changes
R4:
Wakeup Gestures (Kang from EXKernel)
Linux 4.4.107 code merged
R3:
Compile with polly
Fix usb audio
Pick some opt commits from freak97
Linux 4.4.105 code merged
R2.1:
KCAL control added
Fix a derp
R2:
mr1 release code merged
Revert to stock binder
WireGuard support added
Linux 4.4.104 code merged
R1.1:
Fix a bug happen when you flash the kernel with magisk at the same time (if still can't boot when flash together, try flash separately)
mr1 preview code merged
Switch to clang 5
Commits
Download
Google Drive
Install
The kernel is packed with AnyKernel2, so just flash the zip file in TWRP
You can extract the zImage and dtbo.img out and manually flash them if you want
Kernel Source
https://github.com/msdx321/android_kernel_google_wahoo
Credits and Thanks
Too many to list, please check my github commits for credits
Special thanks to @nathanchance for his notes about update to linux-stable (quite useful, encourage anyone who want to compile his own kernel read this)
Bug Report
Leave an issue on my github repo or send me an email
Reserved
Install same as others using magisk to modify boot.img?
Sent from my [device_name] using XDA-Developers Legacy app
gvsukids said:
Install same as others using magisk to modify boot.img?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
It's packed with AnyKernel2 so boot into TWRP and flash it
The more the merrier,??
What's the reasoning for selinux permissive? V4A?
Sent from my Pixel 2 using Tapatalk
joetheshmo said:
What's the reasoning for selinux permissive? V4A?
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
Just a personal flavor, some features rely on permissive such reading GPU loads
Hey,
Plans to add any sort of audio control ?
About time!
Ashray_Vk said:
Hey,
Plans to add any sort of audio control ?
Click to expand...
Click to collapse
Working on haptic and audio control right now
nathanchance said:
About time!
Click to expand...
Click to collapse
:highfive: :highfive: :highfive:
Do I flash the zimage like a boot image? What should I make it? Also I don't see the dtbo image. Or should I just flash twrp at this point?
I just booted into twrp so nevermind haha. Thanks works great so far!
slyr114 said:
Do I flash the zimage like a boot image? What should I make it? Also I don't see the dtbo image. Or should I just flash twrp at this point?
I just booted into twrp so nevermind haha. Thanks works great so far!
Click to expand...
Click to collapse
The zip file is twrp flashable, you can also extract the zimage out and using fastboot manually flash it. For dtbo, R2 doesn't have one since R2 kernel doesn't need it. R2.1 has a dtbo image and need it.
I know it may sound weird, but my headphones aren't getting detected, any logs I can get for that?
Headphone usb Adapter not working
I habe the same Problem, my headphone Adapter wont work, even in save Mode. Maybe it's magisk though or 8.1 and not the kernel. I will Flash Stock kernel with safetynet fix later or timorrow and report back.
Edit: Just flashed the "Flash" Kernel and can report Headphone adapter works again. I'll just stick to flash kernel, because i'm lazy.
Will this kernel work with taimen too?
Ashray_Vk said:
I know it may sound weird, but my headphones aren't getting detected, any logs I can get for that?
Click to expand...
Click to collapse
SeaMax said:
I habe the same Problem, my headphone Adapter wont work, even in save Mode. Maybe it's magisk though or 8.1 and not the kernel. I will Flash Stock kernel with safetynet fix later or timorrow and report back.
Edit: Just flashed the "Flash" Kernel and can report Headphone adapter works again. I'll just stick to flash kernel, because i'm lazy.
Click to expand...
Click to collapse
Sorry guys, it's a bug and has been fixed.:crying:
msdx321 said:
Sorry guys, it's a bug and has been fixed.:crying:
Click to expand...
Click to collapse
Thanks for notifying , is that fix upcoming in the next update ?
Ashray_Vk said:
Thanks for notifying , is that fix upcoming in the next update ?
Click to expand...
Click to collapse
Sorry, just noticed the R3. Testing it out
Ashray_Vk said:
Sorry, just noticed the R3. Testing it out
Click to expand...
Click to collapse
How's it going?
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.
Introduction
Dora kernel is a successor of popular nem0 kernel for A10/A11 ROMs.
Dora Kernel is CAF based kernel aiming to provide great stability and performance while maxing out battery life!
Code:
// Your warranty is now void.
//
// I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
// Please do some research if you have any concerns about features included in this Kernel before flashing it!
// YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
Main Features:
- Unified for OOS 11 and Android 11 Custom ROMs (Check with your maintainer if they have R blobs merged in)
- Based and upstreamed to latest CAF tags for the SD855
- Upstreamed to latest Linux-Stable
- Upstreamed to latest F2FS stable
- Compiled with Clang 13 and -O3 speed optimizations flags
- Compiled with Clang Polyhedral Loop Optimizations (Polly)
- Simple LMK driver from kerneltoast
- BBR2 TCP congestion algorithm
- 675 MHz GPU step
- Custom energy-freq scheduling model for maximizing performance and battery life
- Custom frequencies setup (dropping to CAF default minimums during idle)
- S2idle suspend mechanism with patches from Google P4/P5 kernels
- PELT scheduling mechanism
- Many scheduler backports from mainline and/or 4.19 Google kernel
- Zip made using latest AnyKernel3 release, retains root on flash (Stable Magisk 21.4 or higher reccommended)
- Zip flashable through EXKM/FKM/Smartpack/TWRP
- Integrated OTA updates in Franco's Kernel Manager *(link for the json: JSON)
- Many more features I don't remember right now, check source if you're interested or contact me on Telegram!
Bug reports:
- If you want to report a bug, please provide some sort of logs (logcat, dmesg)
Flashing instructions:
- Just flash it through TWRP or EX or Franco's Kernel Manager apps
- No sorts of configs needed, flash and be happy out of the box
-There are 2 versions per release: one with SDCARD_FS disabled (default) and one with it enabled. Motivation behind this is recent updates to AOSP 11 ROMs (Yaap, Derp, etc.) that have disabled the support for it. And even though that builds with SDCARD_FS could still work, it's not recommended.
So, in layman terms, if you are running OOS or any custom ROM that still hasn't followed the path of those custom ROMs, please use the sdcard-fs zip or update through OTA.
Downloads
Stable and Test builds: Google Drive
Kernel being actively tested in this group: Telegram
Donations
If you would like to keep this project going with more improvements, feel free to support it: PayPal
Thank you to:
@osm0sis for AnyKernel
@nathanchance for help with upstreams
@topjohnwu for Magisk
@idkwhoiam322, @KuranKaname for being good friends
@BobAzzon, @npv12, @Gabyrx7, @Reechings and rest of my dear friends that tested the kernel (really, wouldn't be possible without you guys <3)
Contributors
nem0 aka AnnoyingZlatan
Source Code: GitHub
Version Information
Status: Stable
Created 2021-05-01
Last Updated 2021-07-20
Reserved
Reserved #2
really pru kernel, I like it
my sot tripled
jk, best kernel on here!
Best kernel ever since Nemo,,now Dora,,congrat bro,,awesome kernel,,work perfect with new official PE rom,,,
Best for A11 on OOS11 blobs and OOS11 !!!!
Ex-nem0 Kernel user here, thank you so much @AnnoyingZlatan for this one
I've just installed 1.0 with adb sideload on latest PixelExperience, all good
Love ur kernel looking forward to help u testing hehe
Toutatis_ said:
Ex-nem0 Kernel user here, thank you so much @AnnoyingZlatan for this one
I've just installed 1.0 with adb sideload on latest PixelExperience, all good
Click to expand...
Click to collapse
I'd like to try it on YAAP, but I didn't know how to go back to stock kernel. I read somebody says to restore boot.img & dtbo but not sure how to do it
Zhuang zhuang said:
I'd like to try it on YAAP, but I didn't know how to go back to stock kernel. I read somebody says to restore boot.img & dtbo but not sure how to do it
Click to expand...
Click to collapse
In Franko kernel manager you can make a backup of your current kernel. Then flash this, then restore kernel if you want it back.
Of fastbootd flash boot img from yaap, same as you most likely did when you originally installed it if you used that method. (Ps, make sure it's matching your ROM though, so you're not updated to the latest but flashing a boot image from a previous version..)
Currently using your Nemo kernel. I flashed this kernel via Franco's kernel manager but I get kicked back to my recovery..any ideas? Tia your kernels are awesome
This kernel is awesome. With Dora Freq i've the best UI performance with AOSP like LOS/CrDroid , another world compared to OOS. Thanks Dev.
bushninja07 said:
Currently using your Nemo kernel. I flashed this kernel via Franco's kernel manager but I get kicked back to my recovery..any ideas? Tia your kernels are awesome
Click to expand...
Click to collapse
Yes, this is meant for OOS 11 and A11 ROMs that switched to R blobs, as it's stated in the OP. It won't be compatible with the builds you've run Nemo on
Amazing experience out of the box, super thanks !
tested with OP7 on oos 11.0.0.2
super smooth and really impressive battery
I flashed via FKM on YAAP. Everything started good but just few minutes ago, when the screen turned off, it didn't turn on again & auto reboot. I had it 2 times in just a couple of minutes
Zhuang zhuang said:
I flashed via FKM on YAAP. Everything started good but just few minutes ago, when the screen turned off, it didn't turn on again & auto reboot. I had it 2 times in just a couple of minutes
Click to expand...
Click to collapse
Yaap has a built in logcat, perhaps check to see if there's any traces of the error. It might help Zlatan if you post that..
I have OOS 11 and and currently using a custom kernel. Should I flash OOS 11 again before your kernel? Thanks in advance.
Zhuang zhuang said:
I flashed via FKM on YAAP. Everything started good but just few minutes ago, when the screen turned off, it didn't turn on again & auto reboot. I had it 2 times in just a couple of minutes
Click to expand...
Click to collapse
I am aware of the issue. Will be fixed in next update, just a bit busy atm.
Teso79 said:
I have OOS 11 and and currently using a custom kernel. Should I flash OOS 11 again before your kernel? Thanks in advance.
Click to expand...
Click to collapse
Nope, just flashing a kernel is enough.
I have tried this version of the kernel and it feels very good! But the memory of my phone is too small, I hope there will be swap space in the future. Does the developer have plans to add zram or zswap in the future?