yashsingh1/xdaforums huggingface dataset:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] tatoniss:
My uptime is 7 days and 13 hours. Heavily use my device.

:/ $ su

:/ # cat /d/f2fs/status

=====[ partition info(dm-2). #0, RW, CP: Good]=====

[SB: 1] [CP: 2] [SIT: 6] [NAT: 114] [SSA: 111] [MAIN: 56685(OverProv:678 Resv:346)]

Utilization: 47% (13755326 valid blocks, 165082 discard blocks)

- Node: 134984 (Inode: 123123, Other: 11861)

- Data: 13620342

- Inline_xattr Inode: 2059

- Inline_data Inode: 1

- Inline_dentry Inode: 712

- Orphan/Append/Update Inode: 266, 0, 0

Main area: 56685 segs, 56685 secs 56685 zones

- COLD data: 5222, 5222, 5222

- WARM data: 54640, 54640, 54640

- HOT data: 5224, 5224, 5224

- Dir dnode: 5205, 5205, 5205

- File dnode: 5223, 5223, 5223

- Indir nodes: 3670, 3670, 3670

- Valid: 23782

- Dirty: 8390

- Prefree: 1

- Free: 24512 (24512)

CP calls: 63511 (BG: 1359)

- cp blocks : 323737

- sit blocks : 298888

- nat blocks : 830086

- ssa blocks : 52692

GC calls: 4142 (BG: 4142)

- data segments : 2545 (2545)

- node segments : 1597 (1597)

Try to move 72483 blocks (BG: 72483)

- data blocks : 60569 (60569)

- node blocks : 11914 (11914)

Skipped : atomic write 0 (0)

BG skip : IO: 4175, Other: 20675

Extent Cache:

- Hit Count: L1-1:8095251 L1-2:104243 L2:12731

- Hit Ratio: 8% (8212225 / 101129917)

- Inner Struct Count: tree: 1305(0), node: 81

Balancing F2FS Async:

- DIO (R: 0, W: 0)

- IO_R (Data: 0, Node: 0, Meta: 0

- IO_W (CP: 0, Data: 0, Flush: ( 0 0 1), Discard: ( 0 740382)) cmd: 13518 undiscard:49558

- inmem: 0, atomic IO: 0 (Max. 4), volatile IO: 0 (Max. 0)

- nodes: 114 in 1632

- dents: 2 in dirs: 2 ( 26)

- datas: 274 in files: 0

- quota datas: 0 in quota files: 2

- meta: 1 in 782

- imeta: 17

- NATs: 62/ 226

- SITs: 34/ 56685

- free_nids: 1401/ 13143695

- alloc_nids: 0

Distribution of User Blocks: [ valid | invalid | free ]

[-----------------------|------|---------------------]

IPU: 1897863 blocks

SSR: 306031 blocks in 609 segments

LFS: 26695538 blocks in 52140 segments

BDF: 92, avg. vblocks: 188

Memory: 26144 KB

- static: 14856 KB

- cached: 1632 KB

- paged : 9656 KB

:/ #
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] gvsukids:
Is there anything better with April update?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] EMJI79:
That's what I wanted to know too.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] joetheshmo:
https://source.android.com/security/bulletin/pixel/2019-04-01
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] shreyamt:
Yes same thing happens with me. Can't even use any audio mods because of this
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] rspkt:
I've been using ViPER4Android FX 2.7.0.0 with no issues since I got my device and with the April update it still functions perfectly.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] acidspider:
Same here no issues
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Porogami:
Hi, will this idle the CPU to 300 hz like sultan kernel. Also in your experience, which one provides the best battery life out of elemental, sultan and this one? Thanks
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] joetheshmo:
No
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] DvLAx3l:
Thanks, I'll try with a clean flash

EDIT: Also after a clean flash it's the same, so check if it's processing, because I'm pretty sure that any audio mods works correctly with April update.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] QRCode:
Anyone have an idea to as why magisk uninstalls itself I would have to reinstall it via twrp from time to time
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] HiM@L:
it shouldn't.

do you by any chance flash anything else.

i had to flash magisk if i do kernel twrp n magisk all together.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] bggold:
Is it saying that it is not installed or does mm disappear?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Hey guys and girls,

Short status update :)

4.9.168 is out. I’ll push out a new build probably this evening!

However this release will have a few more changes than just upstream. The next releases will each introduce a few more changes/improvements by every release, that I’m running on my personal kernel for quite a while now. Then we will be back to the longer release posts, where I tried to give a simple to understand overview of the changes introduced.

I noticed, when trying to merge Q preview 2 on my release branch, that something went wrong back when I merged Q preview 1 source. All history was lost in the merge and commit history seemed to be erased for the complete merge. Code wise it was fine though.

I decided to completely redo it from that point on. That took a while of my Saturday morning, but here we are again. :svetius:

Stay tuned and have a nice day everyone!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] QRCode:
Mm isn't installed and I have go into twrp to reinstall it then it's right for I dunno how long then I get a notification saying to reinstall it
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] yung40oz84:
That has nothing to do with this kernel and there is a fix for it if you read the jamesDSP GitHub. It is baked into audio compatibility patch, called notification helper.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
[MENTION=3428502]Freak07[/MENTION]

Wonder if you have a clue which commits are involved in this. Relevant ( Magisk) bug here: https://github.com/topjohnwu/Magisk/issues/1109

This first appeared on Feb+ stock kernels, and any custom kernels based on those stock kernels. So Kirisakura 2.04 didn't show the bug, 2.05 did.

Current stock still shows the problem. However Kirisakura 2.1.2 and 2.1.3 do not. 2.1.1 does. So some commit between 2.1.1 and 2.1.2 resolved this issue. I'm hoping that if you could possibly identify the probable commits it could help [MENTION=4470081]topjohnwu[/MENTION] fix the issue within Magisk for stock, and other custom, kernels. Thanks.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] shreyamt:
I know that has nothing to do with the kernel, since I tested it both with the stock kernel and this kernel. But I didn't know about the AML patch. Thanks for helping!

Edit: Installed James DSP and AML, bug still exists ☹️
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] MeetFace:
I can never get those to work, fwiw
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] 93ae8074:
That's interesting. I'm using JamesDSP with AML notification_helper patch and it works fine.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] shreyamt:
Do I have to do anything extra for including the notification_helper patch or is it baked into aml?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Release soon :)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] 93ae8074:
Hey, mate. I installed Audio Compatibility Patch for Magisk. Do it from TWRP, this is important as from Magisk Manager it did not detected properly my Volume keys. Do it after installing JamesDSP. It includes notification_helper remover and usb_policy patching. That should do the trick for you, as it did for me.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Hey guys and girls,

As already announced here is the next update. It contains linux-upstream to 4.9.168 as well as Q Preview 2 Source merged.

I redid the complete Q Preview 1 merge and everything that followed, because all commit history was lost.

Detailed changelog can be found below. This kernel works only on Android Pie!

Changelog:

Kernel Base Changes

- Q preview 2 source merged (revert one change that breaks compatibility with PIE)

- Linux-stable Upstream to 4.9.168

- compiled with Clang 9.0.2

F2FS:

- Include latest f2fs changes found on f2fs stable git

- Include rapid GC by [MENTION=4898097]arter97[/MENTION] ( best thing is to read the commit description linked here. I compared GC on stock google f2fs, upstreamed f2fs and f2fs with rapid GC. Rapid GC is the most effective, followed by upstreamed f2fs.)

- Set the bio REQ_NOENCRYPT flag (When lower layers such as dm-crypt observe the REQ_NOENCRYPT flag, it helps the I/O stack avoid redundant encryption, improving performance and power utilization. )

CPU/Scheduler

- Change various drivers (WLAN, MM, audio, charger, power, thermal, glink etc) to use power efficient workingqueues. This should work well in conjunction with EAS

Memory managment

- Reap memory of a task that receives sigkill

- fully enable process reclaim from Q preview

- Many more MM patches from Q preview source

Other changes:

- follow kernel/common

- merge latest binder updates

- WQ_HIGHPRI for the IO and crypt workqueues (replaces googles approach with a better upstream one)

- enable all Q defconfig changes compatible with Pie!

- KCAL/KLAPSE: changes safety measures -> allow completely disabling two RGB values (this was requested to only have RED on night dimming)

Important :)

All flashing errors are now fixed. If you experience the ramdisk error please take a look at the FAQ.

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

Why is linux-stable important?

I wish you all a nice day/evening!

Download is below :)

Download:

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

or following the link in the op to the correction version

Instructions can be found in the OP!

But look at this post too :)

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] shreyamt:
I followed the same procedure but it didn't work for me. Which rom are you using? I'm on stock April update. Maybe that has something to do with it?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] 93ae8074:
Same here, stock April update.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] gvsukids:
Is this to keep audio playing after receiving a text or email notification and not lose the sound?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] EMJI79:
Can I flash it over March security update ROM or does it need the latest ROM update from Google?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] HiM@L:
anyone on latest release using gesture app.

i use vivid gesture app and after flashing latest release, my gesture app has stopped working. i tried turning gestures on and off and still nothing.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] 93ae8074:
As a matter of fact it does it.

---------- Post added at 02:52 PM ---------- Previous post was at 02:50 PM ----------

I use GMD root and works fine after updating.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] HiM@L:
i think this issue is specific to Vivid gesture. Fluid gesture seems to be fine.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] muttonhead411:
Thank you! Always a joy reading your change logs!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] swieder711:
Upgraded to the latest kernel and 2 hours later had my first random reboot.

Phone was just sitting on the Pixel stand.

EDIT: Attached are the log files from TWRP.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
post #2 and post #3 ;)

Contents of sys/fs/pstore immediately after the reboot happens please. Maybe they’re still good but they could be overwritten if not take immediately.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] swieder711:
pstore folder is empty. I attached the TWRP log file on my last post.. Does that help?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
No that log has nothing to do with a potential kernel crash.

If the pstore folder is empty, it either means you were to late copying the logs or the the reboot was not caused by the kernel.

If it happens again, quickly navigate to that folder and get me the contents ( if there is anything in that folder). Otherwise I have nothing to work with as I don’t own an pixel stand and have no idea what could have happened.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] HamsterHam:
Vivid with latest kernel works fine here.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] HiM@L:
ya...is working fine now.

earlier i flashed thru Exxm manager and had that issue.... I went back to earlier version and flashed latest thru TWRP and its working all fine now. strange.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] HamsterHam:
Odd. I flashed through FKM. Worked fine. Glad it's all good now.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] yung40oz84:
I didn't say audio modification library, I said audio compatibility patch bud. It gives u several options when flashing using the volume rocker, one is notification helper which will fox that bug But, you still will need AML after flashing everything at the end, u always do.

---------- Post added at 03:07 AM ---------- Previous post was at 03:01 AM ----------

Thanks for ur hard work! I love your in depth explanations!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] yung40oz84:
I don't wanna spam here much, but ya, this is a crappy bug. I managed to figure out that it only happens when I install certain modules and those specific for me are the systemless host module from settings, Ainur audio, and Edge Sense module. Any of them, which stinks because no adblock systemlessly. I am running the ones pictured successfully now. Just gotta wait I guess for the Magisk Mack to figure it out, lol. I would go back to Magisk 18.1 for now, but for some odd reason my play store and Gmail have issues theming with subs on that Magisk version which is odd. 19 and canary works fine, lol.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
Like I said Kirisakura 2.1.2, 2.1.3, or 2.2.0 don't show the bug for me - and I'm running all 3 of those modules. Have I mentioned I love this kernel ❤️
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] shreyamt:
Oh okay thanks! Can you please list the options you chose while flashing Audio compatibility patch? Once again thank you so much!

Edit: Still not working...

Also, I noticed that the flashing bug is still there on my phone even though I'm on April update. Does this mean something is wrong?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] acidspider:
What substratum theme are u using?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
I don´t know if EXKM stores a log file of the flash.

I´m sorry I probably wasn´t specific enough in my release post. If you flash it via TWRP and lose root after rebooting I need the recovery.log from TWRP while doing the flashing procedure of my kernel in TWRP.

Thanks for the heads up I changed it quickly in the latest release post.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Dacian97:
Sorry for the confusion, shame I couldn't be of any help :/
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
All good! We’ll figure it out :)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Dacian97:
I restored to 1.5, had root . Rebooted to twrp, flashed 1.51, rebooted and didn't have root .

THIS time I'm pretty sure I got it for you lmao

https://drive.google.com/file/d/1ZcA1cXrxEl1XCx-yxzq9r14msOogiV2Q/view?usp=drivesdk

Sorry, I'm new to this stufffff
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Sevael:
I only flashed stock boot.img first because I was on a different kernel and didn't want to run into any potential issues when installing this one. Now I know that this step wasn't necessary. :)

I'm pretty sure I had rebooted after my Magisk flash but I'll keep that in mind for next time. Thanks for the info!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] ridobe:
Sorry I couldn't be more help but 1.5.1 failed to flash for me all together. It was failing at the symlink system....stage. That must have been the underlying problem with retaining root. I ended up having to flash the stock boot.img anyway. 1.5.1 flashed successfully for me now so I'm up and running. FYI: I am using the latest canary build of Magisk: 17.4-89e0be00.

edit: according to [MENTION=6047959]dabug123[/MENTION] on the Frankenkerenel thread, the issues are with the newest Magisk. He thinks it's because Magisk is newer than what anykernel recognizes. So, there. I'll just flash both each time.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Sevael:
I'm using the latest Canary build too, if that affects anything.

As a test, I just flashed 1.51 via EXKM and lost root. :) I'm just going to start flashing Magisk afterward each time just in case. Saves having to connect to the PC and use TWRP to re-root.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] ridobe:
See my edit above yours. Here is the post: https://xdaforums.com/showpost.php?p=78155497&postcount=81
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
could be that this is really the cause.

I’m using the magisk build from the screenshot.

Thanks for troubleshooting with me. I’ll change the OP accordingly.

But now with touchscreen working it’s no big deal to boot into twrp in my opinion. that was my main reason to implement the feature. I changed the method of detecting root in the 1.5.0 zip. I thought this would be better. Maybe I change it back again.

I’ll post a test for those that had issues earlier.

Thanks for the help!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Semtronix:
Weighing in on the whole root loss conundrum. I've flashed every kernel release with FK Kernel Manager's autoflash. Magisk is latest canary build. I don't have or want to use TWRP. Root and Magisk work fine after every flash.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Paz9:
curious guys

just noticed this

if you go into the "files" app and click on the three lines menue do you see a filder named "bug reports"

what is this? i dont remember seeing this before?

its not visible on my stock pixel 3
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Semtronix:
Yeah I have it there. Downloads, bug reports, google drive. Selecting bug reports results in "can't load content at the moment".
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] airmaxx23:
If you capture a bug report that's where it will be stored.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Flyer66:
I know that. I was currently running Franken kernel on my 3XL before I tried to flash your kernel via Franco's Kernel manager app. I auto-flashed it with a reboot because I was already rooted. Unfortunately, after the reboot, my phone was still on Franken kernel. So, I booted my phone to Recovery (TWRP) and tried to flash your kernel via TWRP....it failed again! Not sure why it wouldn't work.

While I was still in TWRP, I went ahead and "restored" my stock boot sector (I always make a backup) and then immediately flashed TWRP.zip. I then was able to successfully flash your kernel and then Magisk. After rebooting, I was on your kernel and rooted.

I'm not sure why I had problems flashing a custom kernel directly over a different custom kernel with either FK manager or TWRP. I did not try EXKM.

I've owned the Pixel XL and the 2XL and have flashed many custom kernels directly over a different kernel and never had a problem.

Edit...FYI, I'm on the Canary build of Magisk (v17.4-89e0be00)

Anyways...Thanks again for a great kernel and all the time you've put into it, Freak!! So far it's running fast and smooth! I'm sure you'll figure out the reason why it doesn't retain root after a flash. In the meantime, it's not a big deal to immediately flash the Magisk.zip file either through TWRP or the Magisk app before rebooting. :)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] 93ae8074:
Hey guys,

Kernel is running great. Just would like to check if someone is able to keep Maps running in the background and screen off with this kernel. For me, even when memory management is better and Adaptive Battery is off Maps keeps being killed. I reckon the phone is killing more apps as even my Gear S3 background processes are killed.

Did you have any luck with it?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Paz9:
hmmmm must be root related
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] airmaxx23:
It's staying open in the background for me.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Roll3r:
Maps is fine here.

I don't have a Samsung watch (I'm on Wear), but from what I understand the process uses a *ton* of memory.

Download the Magisk module "Systemize" and install the Samsung app as a privileged system app. That should help with it getting killed.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] 93ae8074:
Never thought of that, this is good advice, going to try it. And maybe cleaning cache just in case. Thanks!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Roll3r:
No problem! I was having issues with Adguard getting killed (uses about 150MB RAM), which in turn would kill my data connection. Using Sytemize on it solved the problem. Also used it for other apps I really want to keep running, i.e. Tasker.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Why don´t you just flash the factory image with -w removed? It´s a matter of 5 minutes once you get the hang of the procedure and will keep all data intact.

But it will most likely work on march update as my kernel had already all April patches from Q preview 1 merge.

It most certainly won´t matter how you flashed the kernel for the app to work. This could have many reasons but I don´t think there´s anything in this update that could interfere with it.

I would have tried it too, but I don´t need the app and it is not free. DU has integrated gestures support and that´s what I´m currently using.

However I´m a big fan of LMT launcher and I´d notice it pretty quickly if a kernel update breaks it.

Glad you got it working! :)

Both of you are very welcome. It´s good seeing someone actually noticing/appreciating it. It consumes quite a bit of time, so thanks for the nice words.

Have a nice day :)

I think I took a look yesterday, but forgot to reply. The only changes were f2fs and upstream changes, from the versions you mentioned.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Maty360414:
After I flash the April update, can I flash TWRP, Magisk and kernel in that order without rebooting the phone one by one?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Portgas D. Ace:
You should always flash the TWRP.zip file after flashing the ROM to be able to keep TWRP available without having to boot it via fastboot/computer. For A/B devices like the Pixel ones it is recommended to boot into the system once, then go back to recovery and flash Magisk, otherwise you'll most likely end up with some kind of issues. Same goes for custom kernels, from what I know. I think the correct order would be kernel, then Magisk.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Flash factory image with -w removed (if you want to keep data intact)

Do a reboot

Then you can boot to twrp and flash twrp, magisk and kernel (in that order)

Afterwards all should be fine.

I personally do a reboot after flashing twrp. Then back to twrp and magisk plus kernel.

There’s also a guide thread :)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] EMJI79:
I don't have TWRP installed on my device, I fastboot to use it every time I need it, is it dangerous?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] DvLAx3l:
It's better without it in my opinion, like this u can update the os directly via settings app https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation

If you need TWRP, just fastboot it, I think that everyone should do "dangerous" operation like flash something only when have a computer near them.