yashsingh1/xdaforums huggingface dataset:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Gordietm:
When you the bbr tcp congestion control benefits the sender, what do you mean by that?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] galakanokis:
I am new to the Pixel 3XL and lasted about 2 days before flashing a kernel and root. I got

0.6%/hr drain over 6 hrs last night. I was well over 1% on stock. I'll take those numbers and your kernel runs snappy and smooth.

Thank you for your work and quality info you provide in the thread.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Rebel7022:
I can't get sweep to wasn't too work. It's there something I'm doing wrong?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
BBR’s benefits are mostly for a server that sends more data than it is receiving.

Download speed isn’t going to increase magically just by using BBR.

I’m using it currently in conjunction with wireguard and try to evaluate if it affects real world usage at all.

Thank you for the nice words! great to hear it’s well for you.

Have a good ride :)

Activate sweep to sleep or sweep to wake via EXKM or FKM and it should just work fine. :svetius:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Rebel7022:
It works but it doesn't work every time and I really have to try to make it wor. I use the ex kernel app, I have to double tap the screen a bunch sometimes & and I can only get the left swipe to wake the screen up. My question is can you swipe any direction and make the screen up right away no problem? I have a aod set to lift to wake
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] gogoffm:
Same here! Using FKM App .....
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] EMJI79:
If we got good network reception, there's no need to activate a TCP Congestion algorithm, right?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
You'll always have one activated. The default in this kernel (Westwood) is a very good algorithm. For a rundown of most (not all) of the algorithms see https://xdaforums.com/general/general/ref-to-date-guide-cpu-governors-o-t3048957/post67085276

That thread has a lot of good information.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] spuri78:
[MENTION=3428502]Freak07[/MENTION] I'm back :o

I finally got a chance to factory wipe (as I've been travelling for work in the last week or so) and ran your kernel with no battery saving apps (except app ops) and so far it's been sooooooo good. I'm on my second full charge from 20-100. Screenshots attached? What do you think?

Btw, I thought I'd let you know that when i factory wiped and flashed your kernel, my idle drain went up to 3% or so with (Youtube) music streaming on Wifi and that’s to be expected but then the idle drain didn’t come down much even when i had my phone idle for 4-5 hours with no streaming. Maybe that’s normal? So, i restarted the phone and since then even after streaming, my idle and active drain percentages have been pretty good.:fingers-crossed:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Yes AOD is set to wake on lift here is well. I just tested every direction for sweep to wake. All of them are working fine. I can swipe right left up or down and it activates just fine. But mainly I’m using just sweep up to wake.

Double tap is working a bit different on this device. Instead of tapping only a single spot try to “smear” the taps a bit on the screen. [MENTION=4684315]flar2[/MENTION] mentioned that the touchscreen driver needs the “smear” to detect the input properly.

Yes :) it’s like [MENTION=4487388]jcmm11[/MENTION] said. Westwood proved to be a very good all around balanced solution on every kernel I used it so far. For now that’s the reason it stays default :svetius:

yes the partial wakelocks finally look like they should! I’d say just use your device, deactivate the battery monitor, keep bbs installed to see if wakelocks stay good and enjoy good battery life :svetius:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] spuri78:
OMG, if I deactivate the battery monitor, what would feed my OCD lol. Any reason for deactivating it? You've been great Chief and I look forward to keep enjoying a good battery life on a good kernel from a great dev:)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Well in the end it’s just another service using cpu. Even if it works efficiently and is very lightweight. It’s good for monitoring and getting an overview. But once you know the device runs good I disable it.

Personally I check wakelocks once in a while and nothing more. If I have good battery life I just use the device without trying to control/ check everything. After all we spent money on a device that we want to enjoy! :svetius:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dnsmo:
Thank you for the input and I am so agreed with you on this. The kernel works great so far on my xl and thank you for keeping it up.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
about the last few posts and keeping the kernel up to date!

4.9.146 popped up a few hours ago. I´ll release an update probably later today, which will have this included so you guys are on the latest state!

Just want to make sure there are no errors creeping in first!

On another note. I´m testing another round of CAF updates out. So far it looks great. These will probably be in the update after the next update if all goes well! This fixes a lot of small and not so small issues.

Among the patches are a lot of "under the hood" changes but the recent CAF tags released where fairly large. So this contributes to something! So stay tuned everybody!

Have a nice day everyone :)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Sevael:
While most people have been talking about sweep-to-wake, my issue has been with sweep-to-sleep.

It has been working, but it's requires more precision than feels natural. I have to sweep from the very edge of the screen to the other edge or it doesn't work. And the sweep has to be very straight. If I try to do it while holding the phone one-handed, it doesn't work 90% of the time because from that position it's difficult to make a perfectly horizontal swipe. But if I hold the phone with one hand and use the other hand's index finger, then it's fairly consistent. But if I'm holding it in that manner, it's just as easy to press the power button to sleep the phone...

Is there any way to loosen this up a bit? Since it has to be done across the navigation bar, there isn't much chance of an accidental activation even with looser restrictions. It would be great if it only required a swipe of half the navigation bar's length or greater and could be started from anywhere in that half of the bar. Also would be great if the swipe would still be recognized even if it wasn't perfectly straight.

I mostly use it to quickly sleep the screen when the boss walks around the corner and it fails to work most of the time so I keep getting caught. :D

Edit: I guess my issue could be solved with an app that allows one to customize the navigation bar. Can anyone suggest such an app that doesn't actually remove/replace the stock nav bar?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Do you have a XL or a regular model?

I have a XL and to take my attached screenshot as a reference I start on the right outer edge below the Chrome icon and end up below the left border of the hangouts app. It triggers screen off very consistently for me.

They all have to hide the stock navbar in a way and display their own overlay. but I’m not sure if that really interferes with the kernel sweep to sleep.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] smartymcfly:
.

GMD gestures? Requires root it takes a moment to start upon boot but you can make a custom tap or gesture nearly anywhere on the screen to do nearly anything.

There is free liteversion and pro version $5.55

Link is to lite version

https://play.google.com/store/apps/details?id=com.goodmooddroid.gesturecontroldemo
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Sevael:
I have a regular Pixel 3. I have to swipe all the way across. Perhaps it's set at a designated number of pixels that need to be covered by the swipe? The P3 being lower res than the XL, that could account for the difference.

I really miss Gravity Box. I used to set it up with options like long pressing the back button would sleep the phone.

Come to think of it, Tasker recently added nav bar actions. Maybe I could duplicate that behavior with a custom task.

Thanks! I will check it out.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Please send me a pm with your hangouts email. I´ll compile you a build to test something with the wake gestures. Don´t have the regular pixel 3 to test it.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Update to 1.8.8

Hey guys and girls,

As promised here is the next update. It includes upstream to latest stable 4.9.146!

Next release will be a bigger one again :) Maybe I´ll finally bump the kernel to 2.0.0 then!

Important :)

All flashing errors are now fixed. The ramdisk error is fixed if you did the procedure I put in hide tags below.

Kernel is flashable via TWRP or directly in the EXKM App as well as the FKM App. The presence of a custom rom will be detected and the kernel will get patched so it boots the custom rom too!

Root will always be preserved! So happy flashing everyone :)

Procedure to fix the ramdisk issue:

The ramdisk error is now fixed. Please take a look at this post from [MENTION=4544860]osm0sis[/MENTION] for more information:

Big thanks to [MENTION=4544860]osm0sis[/MENTION] and [MENTION=4470081]topjohnwu[/MENTION] for everything at this point here! And everyone else that helped in the process!

Important:

What do you have to do to get finally rid of the ramdisk error?

1. Flash back a stock clean boot.img either for stock rom or the custom rom you´re on. (not a backup from some time ago, a clean stock boot.img)

Link to stock boot.img from Google´s december factory image for convenience

2. REDOWNLOAD(!) either magisk 18.0 or the latest canary directly from magisk manager and delete all old magisk zips on your device. (this is really important!)

3. Optional: Reinstall twrp.zip if you want to.

4. Flash the redownloaded magisk zip in TWRP

5. Flash my kernel either via TWRP, EXKM App or FKM App

6. Profit

Have fun flashing and enjoy your device with latest linux-stable :)

Why is linux-stable important?

I wish you all a nice day/evening!

Changelog:

- Upstream to 4.9.146

For further details please take a look at my github!

Download is below :)

Download:

https://www.androidfilehost.com/?fid=11410963190603877311

or following the link in the op to the correction version

Instructions can be found in the OP!

But look at this post!

Have fun, enjoy the kernel and your phone.

If you like my work please consider a donation.

Donations are not mandatory but very welcome.

If you like my work and want to buy me a coffee: http://paypal.me/freak07
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] SinisterXReaper:
Another great update, from a great DEV. Thanks boss! All went well!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] brandonpa:
Did I mess things up when I initially installed through twrp? Everytime I try to flash in exkm I get the ramdisk error and it aborts. I have to boot into twrp to install updates every time.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] ridobe:
Did you follow the directions to eliminate the problem?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] brandonpa:
That is what I am trying to find. Is it the return to stock boot omg and reinstall everything?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] ridobe:
The release post 3 posts up has exactly what you need.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] brandonpa:
That is what I am trying to locate on how to correct that error. Is it the reinstall boot.img and restart with everything?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
Yes. Short version:

Stock image to both slots. Then Magisk (if you have a saved copy of v18 redownload it - there was a silent update to fix this. Latest Canary is fine). Then custom kernel.

If you're flashing TWRP to the device (by the way, topjohn recommends against it) do it before flashing Magisk.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Paz9:
I always thought magisk last

Since if you're on stock kernel and want root you just flash magisk instead of stock after magisk
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
It'll work if you do Magisk last but you really want the backup that Magisk takes to be the stock kernel.

Pretty much all custom kernel zips nowadays use AK2 which is meant to preserve any ramdisk changes previously applied (which is why Magisk can be preserved when flashing a custom kernel. It's also why when changing from one custom kernel to another you need to go back to stock first)

Stock doesn't use AK2 which is why it'll wipe out any other kernel changes. Actually any img (as opposed to zip) will act the same way. Stock kernels are (always?) img files rather than zip files.

If you look at the OP in https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 you'll see that topjohn states "If you plan to flash a custom kernel, flash it AFTER installing Magisk"
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] gogoffm:
Last Time i updated through ExKm and brought me to bootlooping ! #heartattack

All future updates only through TWRP....

BTW flashing the boot.img will bring me back to stock kernel? Can I flash through TWRP or through fastboot ? TX for the new update and the support in this thread. Cheers
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] MeetFace:
I don't believe it flashes a stock kernel, but a stock boot image, which Magisk modifies, and somehow the custom kernel when flashed used to break, until the last few versions.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] MeetFace:
Has anyone tried to replace the boot screen while using this kernel?

Done discussion here:

https://r.tapatalk.com/shareLink?ur...share_tid=3863388&share_fid=3793&share_type=t

I guess something changed on photon recently that allowed this, curious if we could do the same on our kernel.

Thanks! I'd love to change out the blinding white boot screen.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] masri1987:
so now that i'm more comfortable with the kernel i'm ready to make some adjustments,

Anxiety I\O seems very snappy and responsive in terms of read write

Any other changes? can I lower the bottom value of mhz any lower than 500mhz~ ?

ANything else to extend battery life?

---------- Post added at 09:21 PM ---------- Previous post was at 08:37 PM ----------

I just tried to drop the min frequency on both clusters to anything besides the default and it doesn't take the requested changes via EXKM
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
What you said is all basically correct.

On A/B devices the boot.img´s ramdisk is actually the recovery now. So the ak2 zip doesn´t modify the ramdisk (which is now the recovery). If you would modify the ramdisk you would only modify the recovery’s ramdisk.

the boot.img contains "more" than the ak2 zip modifies.

this is a good source of info:

https://www.xda-developers.com/how-...ess-updates-affect-custom-development-on-xda/

Yes the stock boot.img always includes the stock kernel amongst other things. You can flash the stock boot.img either via fastboot or flashing it in TWRP!

No you got that wrong. The magisk zip damaged the ramdisk. The damaged ramdisk caused the my anykernel2.zip to error out.

That´s why you all need to redownload the updated magisk 18.0 file as I stated in all the release post! The issue was never in my kernel.zip or anykernel2 zip in general.

I don´t want to disable verified boot.

https://source.android.com/security/verifiedboot

I believe this is what makes changing the bootanimation on stock possible.

No the power hal will change the values back to default. 576mhz/800mhz are the most efficient speeds for our socs. Believe me qualcom did put a lot of effort in this.

It´s really just flash and forget with this kernel. I don´t change anything besides wake gestures to my liking. Everything else is set when I compile the kernel! :good:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
Thanks. Still figuring out some a/b nuances. I knew recovery was now part of the boot image, didn't know the ramdisk was now totally recovery. I did know that there was "more". I was trying to keep things simple ?

Thanks for the link. Will definitely check it out.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] MeetFace:
Thanks Freak, not worth it then ;)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Paz9:
But magisk can remove Verity

Kernels do not check for this
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] bighit101:
Updating from 1.8.4 but getting error in TWRP

[MENTION=3428502]Freak07[/MENTION]

Hi,

Great Kernel!

But have a small issue. I am on 1.8.4 and downloaded 1.8.8 and tried flashing via TWRP but each time it says "process ended in ERROR 1".

I tried downloading the kernel again (just to be sure it wasnt the file), but same issue.

I even tried downloading and flashing another kernel alltogether and the issue persists.

I did not have any issues updating from the version previous to 1.8.4, so not sure whats going on??? And I dont see anyone else having this issue, so dont know what I am doing wrong???

Any suggestions?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] joetheshmo:
Redownload magisk v18, reflash stock boot.img and reflash kernel and magisk.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
Yes it can - if you specifically tell it to. Actually this kernel can also remove verity. If you check an install log you'll see the following line (assuming you're on stock)

"You are on stock, not patching kernel to remove verity!"

I don't have a Magisk log handy but I think it does something similar.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Yes verity needs to be disabled in order to allow custom roms to boot. My kernel.zip checks if you´re on a custom rom or not. If you are on a custom rom verity gets patched out.

To be exactly clear about this: My kernel does not remove verity, but my ak2.zip makes use of the magiskboot binary. The magiskboot binary (which is also included in the magisk.zip ;) ) is able to remove verity.

See here under "magiskboot" for documentation:

https://topjohnwu.github.io/Magisk/tools.html

do what [MENTION=7037416]joetheshmo[/MENTION] told you :)

Alternatively look into the release post from 1.8.8 for more information about this error and detailed instructions.

You can find a link to this post linked in the OP! :)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Paz9:
That's for ROM

I wanna stay stock and disable Verity

I can only do with magisk last
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
if you want to disable verity maybe this is helpful for you?

https://xdaforums.com/android/software/universal-dm-verity-forceencrypt-t3817389
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
Assuming a stock kernel, if verity was disabled via Magisk, before flashing your kernel, will you turn it back on or will you leave it off?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Flash the zip every time you update the kernel.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
I guess I need to release a christmas edition to break the silence in here? :)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] ART:
Lol. Silence is good. Means no one has any major issues anymore.

Not that I would say no to a Christmas edition of the kernel ?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] blaze9090:
I'm want to see snow flakes and raindeers in my twrp command line!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dukat0s:
Maybe a Christmas extreme edition like the old days , my friend ?? hope you doing well.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] masri1987:
don't tease us please us LOL
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] chewy74:
Can I flash this over another custom kernel? Or do I need to be on the stock kernel before flashing?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
You should be able to just flash over. :)

If you face issues flash stock boot.img.

If you face the ramdisk error while flashing look at the latest release post for a solution. It’s linked on the OP!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Hey guys and girls,

So here´s the Christmas update for you guys :)

It includes an update to latest linux-stable.

Some upstream patches from kernel/common to crypto.

Latest CAF tag included many fixes to various drivers. A few more memory leaks are fixed! EAS machinery is updated.

Display driver is now in line with latest CAF release. Quite a significant update. Memory leaks are fixed, other issues and touch responsiveness seems to be improved.

Maybe I´m imagining this (could be placebo as I´m biased of course) but please feel free to judge for yourself!

The installer includes a small Christmas surprise! Flash via TWRP or FKM to see it. EXKM won´t display it properly!

I wish everyone that celebrates it Merry Christmas! :)

Important :)

All flashing errors are now fixed. The ramdisk error is fixed if you did the procedure I put in hide tags below.

Kernel is flashable via TWRP or directly in the EXKM App as well as the FKM App. The presence of a custom rom will be detected and the kernel will get patched so it boots the custom rom too!

Root will always be preserved! So happy flashing everyone :)

By now most people will have their ramdisk fixed. But keep this here just in case.

Procedure to fix the ramdisk issue:

The ramdisk error is now fixed. Please take a look at this post from [MENTION=4544860]osm0sis[/MENTION] for more information:

Big thanks to [MENTION=4544860]osm0sis[/MENTION] and [MENTION=4470081]topjohnwu[/MENTION] for everything at this point here! And everyone else that helped in the process!

Important:

What do you have to do to get finally rid of the ramdisk error?

1. Flash back a stock clean boot.img either for stock rom or the custom rom you´re on. (not a backup from some time ago, a clean stock boot.img)

Link to stock boot.img from Google´s december factory image for convenience

2. REDOWNLOAD(!) either magisk 18.0 or the latest canary directly from magisk manager and delete all old magisk zips on your device. (this is really important!)

3. Optional: Reinstall twrp.zip if you want to.

4. Flash the redownloaded magisk zip in TWRP

5. Flash my kernel either via TWRP, EXKM App or FKM App

6. Profit

Have fun flashing and enjoy your device with latest linux-stable :)

Why is linux-stable important?

I wish you all a nice day/evening!

Changelog:

- Upstream to 4.9.147

- Follow kernel/common -> Updates to crypto

- massive update to display driver (memory leaks, improvements to responsiveness and stability)

- updates to EAS

- other CAF patches to tackle various issues!

- Feel free to take a look at my github!

For further details please take a look at my github!

Download is below :)

Download:

https://www.androidfilehost.com/?fid=11410963190603881186

or following the link in the op to the correction version

Instructions can be found in the OP!

But look at this post!

Have fun, enjoy the kernel and your phone.

If you like my work please consider a donation.

Donations are not mandatory but very welcome.

If you like my work and want to buy me a coffee: http://paypal.me/freak07
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] hilla_killa:
Just flashed up and running!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] rohmbd:
Anyone tried LKT?

https://xdaforums.com/apps/magisk/xz-lxt-1-0-insane-battery-life-12h-sot-t3700688/page38