yashsingh1/xdaforums huggingface dataset:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
I've just been playing with this through a few reboots. I agree that FKM is (still) broken as far as zRam goes. I filed a bug on GitHub if you want to add to it.

EXKM, however, works for me (with the latest kernel). I set zRam compression to zstd and swappiness to 175. Turned on apply at boot for those 2 items. Left enabled/disabled and 2048 as is and didn't turn on apply at boot for them.

Reboot the phone and all settings appear to get applied correctly. You do have to wait a while though. Upon initial boot it'll be set to lz4 (the default). zRam then has to be shut down so the compression (and/or size) can be changed and then started up again.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] geeksammao:
For those who had random app force close, I seem to get rid of it by removing digital wellbeing timer for the app. Not sure it's the real cause, but guess you can try it.

edit: force close still happened but less times.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
it´s exactly like [MENTION=4487388]jcmm11[/MENTION] said. Once ZRAM is initialized it has to be shut down and restarted for any changes to take effect. This takes a while with EXKM.

You can try to create a magisk module or a script [MENTION=7750470]nikhilnangia[/MENTION], that changes it way earlier in the boot process or automates disabling and re-enabling ZRAM with your desired settings.

There were absolutely no changes in the ZRAM code between 1.0.0 and 1.1.0. If ZRAM isn´t initialized on boot and set to 2GB of size and lz4, without you changing a thing there might be something broken on your phone.

Either you have a module interfering or something is not working right. But my suspicion is you ticked the enable at reboot arrow in EXKM for any ZRAM setting, rebooted, and looked right at ZRAM settings in EXKM when ZRAM got disabled (due to you applying to change settings on reboot) and ZRAM was restarted again.

I just checked my phone to be sure, ZRAM is running fine on my phone.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] californicated:
That's no surprise as stock Android 10 also gives me and some others a soft reboot every few days.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
these are no soft reboots, but hard reboots, crashing the phone completely and starting from bootloader screen again.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] tiny4579:
I wish I knew what was causing these issues. I typically reboot my phone roughly daily when I start to see reloads of apps or slowdowns. It wasn't like this on pie for me. My hope is Google does something about this on the October build. The change to zram size increase to 2gb is concerning as they had this change set late last year but only merged it for Q.

It's weird it's inconsistent for people.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] nikhilnangia:
Thank you [MENTION=4487388]jcmm11[/MENTION] and [MENTION=3428502]Freak07[/MENTION]. I've played around a bit more and still have no luck. Changing compression to anything bu lz4 (default) does not stick and in fact, disables the ZRAM completely on EXKM.

I tried moving back to stock img (completely removing magisk) and then re-rooting and installing v1.1.0, but still no luck.

Only if I leave all options to default does ZRAM stay on. By the way, I am not using any modules - just magisk 19.4 (canary build) and apart from that, I'm running stock Android 10.

I am attaching a dump of my /proc/kmsg and a logcat using the following command. Let me know if anything else is needed.

logcat -v time -f /dev/kmsg | cat /proc/kmsg > /sdcard/log.txt
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
I took a look at your logs. ZRAM is working just fine and gets set up correctly when booting.

The problem is not the kernel, but shutting down and restarting ZRAM.

I tried it a few times on my Pixel 3 XL. When the device is running it takes up to 10 minutes to switch the compression algorithm. ZRAM needs to be cleared bit for bit, until it can be shut down and restarted. This is not an instant process. As long as it´s shutting down ZRAM in EXKM, you will see "stopping".

When I set the "apply on reboot" option in EXKM by tapping the arrow, after the algorithm was successfully changed,and do a reboot, the correct algorithm is applied when I check with EXKM after a few minutes.

If you use any sort of encryption like a pattern, you need to unlock once before EXKM starts to apply the settings after the phone started.

I rebooted several times and in the end the compression algorithm was applied fine by EXKM. I tried zstd and lzo-rle. lz4 works as it´s the default.

Sorry, I cannot provide more help :(

I´m not sure what´s going wrong on your side, but the kernel is fine. It´s just tricky to restart ZRAM.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] nikhilnangia:
Thank you! You have already done enough. Honestly, it is not much of a big deal - I just wanted to report it thinking it might be helpful.

Thanks again, man.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] fuzzgruble:
Had a reboot on test version while plugged in. I didn't notice the bootloader warning screen, but it's possible I just missed seeing it. /sys/fs/pstore is empty however.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dd805bb:
For me, on reboot, after I enter the unlock and it actually is finishing boot. I watch for when ex gets applied notification and open the app after it is applied. Open the memory tab and wait to do anything till it actually switches. Reason is if you are opening apps while that is changing it still uses and default kernel setting of zram to lz4 and 2048. Mine switches everytime just fine. Also don't lock the phone right and let it dim itself after first boot. It will light itself back up and stay unlock while it finishes all applied settings it need to. Depending what apps you have.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
If it’s empty it’s either already gone as the reboot happened too far in the past. or it wasn’t caused by the kernel. Without any logs no idea what happened, sorry :(
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Those with reboots while charging on 1.0.0:

is the test kernel 1.1.0 I posted a few days ago fine?

In case a reboot is happening zip up the contents of sys/fs/pstore.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] 123SIT:
All good here. Multiple charge sessions and no reboots.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] stryker09:
Same as well, just did a full charge session and no reboots.

Thanks!!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] fuzzgruble:
No need to apologize! I know you can't do anything without logs. Thanks for your work!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] geeksammao:
All good here, no reboots at all.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] bbender716:
All good here. No reboots, no Spotify issues. Great kernel bud!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Tekken Lord:
W/ version 1 or 1.1?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] bbender716:
1.0.0 q
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] geeksammao:
1.1
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Lagarde:
No reboots yet on 1.1.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jsauder2:
I had another on 1 but have been on 1.1 for a little over a day now and all seems good. :good:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Dark_Eyes_:
Wireguard

Anybody here using the kernel backend for Wireguard? It used to work fine a while back on pie, but since Android Q I keep getting can't connect with error 64. I'm trying to connect to mullvad if that matters.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] spddl:
works for me on stock_Q and Kirisakura_Q 1.0.0

with https://play.google.com/store/apps/details?id=com.wireguard.android
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Donric13:
Didn't try on this kernel. But got this error on despair and ex kernel with official wireguard app. Had to use vpn client pro...
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Dark_Eyes_:
Thanks for the reply. Can you make sure when you go in settings (three dot menu) it says kernel module backend v.0.0.20190913. The stock kernel doesn't have the backend so you must be using the userspace implementation.

Yeah, I think there is something going on with the kernel module on q, but I didn't see much report of this so I was wondering if it was only on my end. Thanks for chiming in.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] spddl:
I do not know what that means but I use the userspace implementation.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] flar2:
This is usually due to an outdated version of AnyKernel2 installer.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] MArtyChubbs:
Just got the failed to create symlink system to...while trying to flash elementalx 1.00. Is that due to AK2 as well?

Cuz it happens so often on many kernels, I just keep a the stock boot image on my device. I just boot up in TWRP to flash boot image, twrp, kernel anf magisk. Reboot and all is well. Thank you [MENTION=4684315]flar2[/MENTION] [MENTION=1037050]freak7[/MENTION]
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] flar2:
No, I don't know what that is. It flashes fine for me. Do you have any Magisk modules?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dnsmo:
I also have the fail to unpack ramdisk error. I will have to boot to twrp and try to flash it that way. I will report back. and I do had magisk 17.4
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] zetsumeikuro:
Hmm is it just me or does high brightness mode not seem as glorious as it used to be? It's been awhile since I've triggered it so it could be me haha.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Have a read at this post.

https://xdaforums.com/pixel-3-xl/development/kernel-pixel-3-xl-elementalx-1-00-t3868373/post78188272
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] zetsumeikuro:
Thanks for the information! I haven't poked into flar2's thread yet :P.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] MArtyChubbs:
Yes, busybox and YouTube vanced. Thanks for clarification
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
could be youtube vanced as it uses the bind_mount feature (AFAIK) which also conflicts with substratum.

my ak2 installer shouldn´t be too much out of date acutally :)

thanks for popping in [MENTION=4684315]flar2[/MENTION]!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] HamsterHam:
For anyone having issues flashing the kernel do this and it will work.

Flash stock boot img in twrp, flash twrp zip, kernel and magisk.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] old_fart:
.

I was curious about your version, so i googled your string and found this.

https://github.com/kantjer/MagiskFiles

And I noticed yours is four days old and this one is nine hours old.

https://github.com/kantjer/MagiskFiles/blob/master/Changelog-2018111907.md

.

v17.4/v6.0.2 rev.17

Magisk

Update busybox

Update external dependencies

Update to 1.29.3

Selinux

Add NDK support to libsepol

Add Android M policy compatibility

.

WOW ! it blows me away that topjohnwu keeps tweaking and tweaking and adding and adding !

So this is the seventeenth version of his 17.4 alpha ? ? ?

.

I've stuck to the 17.3 beta. . . Oh, by the way, I just flashed the new kernel ( Thank You ! ! ! ) with EXKM and lost root.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] MeetFace:
I believe you have to flash magisk again if you flash kernel?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] bggold:
Just updated to v17 this morning.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] SinisterXReaper:
Flashed update via FX, flashed magisk (just in case) and all is well thus far! I appreciate all your hard work boss!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
You’re very welcome :) enjoy the ride!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Gordietm:
We're you able to flash it over the HTML kernel?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
I updated the OP to better reflect the kernel changes that were already made.

And added a FAQ to the second post! :svetius:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Gordietm:
If I'm coming from a different kernel, the steps I should take are:

In TWRP-

Flash November boot image

Flash TWRP installer

Reboot

Flash kernel

Flash magisk

Is that correct?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
If you want to be absolutely sure or in case you face issues flash the factory image. ( remove the -w from flash all to keep userdata intact.)

However I think

Flash stock boot.img

Reboot

flash twrp.zip

reboot

flash kernel plus magisk.zip in twrp will also work like you said :svetius:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Gordietm:
I ended up flashing your kernel directly over the elementalx kernel with no problems at all. Flashed magisk afterwards and all good.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dnsmo:
.c3 dropped today and I will try to install the q 1.1.0 and report back with results.

edit: all is working fine so far.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] 123SIT:
Working fine here.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Jiggs82:
What was ur procedure to flash , root etc?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] laill:
Assume you want a fresh install

1. Flash the factory image you grabbed

2. Transfer a copy of boot.img to your phone, it should be found inside the factory image

3. Install Magisk Manager

4. Inside the manager app, download magisk (at least version 19.4, beta)

5. Use the downloaded file to patch the aforementioned boot.img inside the Magisk Manager app

6. Transfer the patched boot.img to your computer

7. Flash the patched boot.img in fastboot mode

8. Boot your phone, you should have root permission now

9. Install Franco kernel app/EX kernel app and grant it root permission

10. Inside whatever kernel app you installed, flash the Kirisakura kernel

11. Reboot and check

Some people reported that EX kernel app doesn't worked properly for flashing kernel on Android 10, I personally used Franco kernel app to do that, not sure the problem is resolved or not.

(I personally like EX kernel app better so I switched back to EX after the installation
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Maybe it’s worth to mention that it might be wise to remove the -w from flash-all.bat/flash-all.sh file so your data is not wiped.

I hope I’ll have an update ready later today with that surprise update source merged, which contains only a tiny fix.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] infamous84:
thanks for this!

I followed the steps, dont think i have root tho, EX kernel at least is not recognizing it. How am i suppose to install magdisk when its a zip file?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
Get the stock boot image and place a copy on the phone.

Install Magisk Manager (beta or Canary for Android 10)

From within Magisk Manager click install|install|select and patch a file

Point it at the stock boot image

After it finishes patching the file it'll place it in the download directory. Take the patched file, copy to your computer, use fastboot to install the patched boot image.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] infamous84:
i got it thanks!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] stryker09:
Used FKM and root was preserved
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] laill:
I used EX kernel app for installing 1.1.3. Everything seems okay.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] masri1987:
for some reason i can't get exkm to even recognize the zip to install, nvm had to close exkm and reopen it and it finally picked itu p
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dnsmo:
the mini update much be very urgent since the October update is around the corner.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] luckana:
1.1.3 running great on my end, amazing job man my p3 has never seen better it's like ultra smooth
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] DvLAx3l:
Latest kernel flashed successfully with EXKM on latest Q update QP1A.190711.020.C3, I received the OTA today, they fix something and updated the stock kernel (no changelog so far), anyway if something happen I'll let u know.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] luckana:
I see that this ota is only just above 2mb if i apply it over. Rooted with KK, is it sure to bootloop ?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] DvLAx3l:
I've followed the official magisk ota installation guide and after boot I've flashed the kernel with EXKM

https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation

For me the ota was 1.23gb
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] zizoty:
Anyone wants to share their favorite settings or profile for version 1.3?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] evilryry:
Stock is the best for this phone tbh, really no tweak necessary to make anything better. Very minor tweaks if any at all.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Porogami:
Don't know if this is the right place but will using fde.ai help improve battery life/performance. It says on their page it will work better on a custom kernel but this kernel has so many tweaks I don't know if it would improve on it.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Mao04:
How did you get magisk to restore stock boot (per the guide)? If you flash the magisk-patched boot to get root on 10, magisk doesn't make a backup.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
Actually it does. When you patch a boot image a backup gets created in /data/user_de/0/com.topjohnwu.magisk/install/ (assuming non-hidden Manager).

Other than that you can always create your own backup and drop it into /data/
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] fuzzgruble:
This is probably not the right place. Check in the XDA thread for that module or the Telegram group. Both are linked in the Magisk module info.

---------- Post added at 04:01 AM ---------- Previous post was at 03:58 AM ----------

At least none to the kernel. All about disabling Google services!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] MeetFace:
Anyone had issues with K-lapse? I'm on Q and even though all settings are Set, nothing is happening.

Also, astronomy mode doesn't seem to work.

Thanks!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
you´re free to use any module you want. But by doing so you´re basically on your own. If you face issues, don´t come here and report them.

There are quite some changes compared to stock in my kernel. If you use modules, which may introduce other possible changes, which in return introduce random issues don´t come here... :) I´m sure you understand :)

I personally don´t use these kind of mods :)

Just tried astronomy mode and K-Lapse brightness dependant mode and both work just fine over here.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] MeetFace:
Odd, I'm on latest Q, stuck, no other mods that would conflict. Any ideas on how to troubleshoot? Does night mode need to be enabled?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
Don't know about troubleshooting this but I can confirm that they're working here as well.

Maybe look in /sys/klapse/ and see if things are getting set? Try uninstalling and reinstalling EXKM?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] MeetFace:
Odd, reinstall of exkm fixed it, thanks!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] -iNSiGhT-:
Hi,

Had a reboot while wirelessly charging. But nothing in sys/fs/pstore folder (don't know since how long the phone rebooted).

Kirisakura 1.1.3
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
To auto save ramoops

https://xdaforums.com/pixel-3-xl/de...ra-1-0-0-pixel-3-xl-aka-t3864563/post79933175
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] -iNSiGhT-:
Thanks !

Installed, ready for the next reboot, if there is one.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] zizoty:
Have been using Google dock wireless charging for 2 days without any reboot on 1.13
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] zxspectrun:
Not bad, I'm on pixel 3, last update from this date without exk app.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] MrPepperino:
Pretty much the same stats i get on stock rom/kernel
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] MeetFace:
Not me, I've been lucky to get 5hrs SOT since about June/July.

No gaming
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Keyute:
Wireguard

Hi, I would like to report that wireguard is not working for the kernel. Im on 1.13 Q
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
Error code 64? See https://xdaforums.com/android/development/wireguard-rom-integration-t3711635/post80322635
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] shackled:
Hi all. Is there better performance using ZRAM with lzo-rle compression for the latest 1.1.3 kernel for Android 10? Instead of the default settings?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] lukefgoogler:
Based on data that I've seen, lzo-rle seems like it's best for Android use. I use EXKM settings to apply lzo-rle on boot, it takes a few minutes on startup but the recent versions of EXKM eventually get the job done. Would love to see Freak07 switch to lzo-rle as default.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dirtyreturn:
Please forgive me in advance...

Is this compatible with 3 xl? I'm not doing something right that's for sure...

Any guidance would be appreciated
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] MeetFace:
Yes, this is 3XL.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Porogami:
I imagine that thee default kernel settings optimised for a balance of performance and battery. Is there a way to make it lean more towards battery by changing any settings or should I not tamper with perfection. :P
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
Have you looked at zstd at all? I'm torn between zstd and lzo-rle. I've been running zstd (with swappiness set to 175). It's been running fine, but I think I'll try lzo-rle for a while and see if I can notice a difference.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Keyute:
Removing DNS address is counter-intuitive because your DNS will be leaked. This only happens when the app recognizes that the kernel has wireguard commits. (ie: works with stock kernel, doesnt with kirisakura kernel). As such, enabling Magisk Hide will allow the wireguard to work again.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] lukefgoogler:
I'm certainly no expert, but I think zstd, lz4, and lzo-rle can all make an argument for being very good algorithms for Android. I haven't done any benchmarking myself, and have settled on lzo-rle mostly on the benchmarks I've seen posted by others, and a smattering of papers that I've read. It seems to strike a good balance of speed vs. resources for the lengths and types of data we are likely to encounter using Android devices.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] fuzzgruble:
I think the ability for the default algorithm to be set in the kernel was removed in Q. It is set in the vendor partition.