yashsingh1/xdaforums huggingface dataset:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Mangtas_666:
This kernel is awesome the battery life of my pixel 3 xl is amazing....thanks a lot hoping for future updates on this.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] luckana:
Flashed 1.3.0 on latest HavocOS and it works as expected. No problems or bootloops, fortunately
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] spddl:
How did you do this? how was the order?

my steps:

#1 fastboot flash boot boot.img (from Havoc-OS)

#2 fastboot --set-active=a/b

#3 fastboot flash boot boot.img

#4 fastboot reboot fastboot

#5 adb sideload Havoc-OS-v3.0-20191206-blueline-Official.zip

#6 reboot

#7 fastboot flash boot magisk_patched.img

#8 fastboot --set-active=a/b

#9 fastboot flash boot magisk_patched.img

Now I can flash Kirisakura_Q 1.3.0 but when I restart I get the message "error boot prepare" and when i reboot into fastboot "Failed to boot into userspace fastboot; one or more components might be unbootable."

How can I flash the ROM over it at this point?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dirtyreturn:
Flashed 1.3.0 over 1.2.6 on Havoc and receive a boot prepare error

edit - flash November

dtbo with previous kernel to boot
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dd805bb:
This is not about this kernel but all custom kernels used on Android 10. The way it is flashed it will take out your Google play system update. In settings there is two places to check, in security tab and in about phone. Whenever I flash a custom kernel, it reverts those dates. Mine is on oct 1st and oct 1st in both places. I noticed after flashing any kernel those dates, one in security tab disappears and the one in about phone rolls back a day to sep 30 play system update. I have brought this up now a few times and it always something else between devs. Well it is an AK3 problem. The way it flashes it doesn't work right. There is no logs to take from flashing. The logcat doesn't have errors. I can literally recreate this by flashing any custom kernel to Android 10. Ex and this one do it. So it's not the kernel but rather the way it flashes. Check before posting. Flash back the stock kernel or just uninstall in magisk, restore boot and reflash magisk before restarting. Then restart and check these dates. Guarantee they will change the next time you check. Been checking this for a few weeks now.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] qualitymove13:
Do you have a kernel manager or just leave it default?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
Interesting. The one in Security tab doesn't disappear for me but it does roll back.

On Dec stock+Magisk I have Google play system update dates of:

Security tab: November 1, 2019

About phone|Android version: October 31, 2019

On Kirisakura I have:

Security tab: October 1, 2019

About phone|Android version: September 30, 2019

[MENTION=4544860]osm0sis[/MENTION] - AK3 or something else?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] osm0sis:
First I've heard of it. I'll look into it, but that's super weird since the boot.img should retain all of its os_patch_level stuff with an AK3 flash. :eek::confused:

Does the date become correct again if you flash back to stock kernel or stock + Magisk?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
Yes. That's how I got it back. Flashed stock+Magisk+stock dtbo. It's possible (probable I'd say) that's it's only a cosmetic glitch somehow, but that's total guesswork on my part.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
Ok - the plot gets more confusing.

I had Kirisakura installed. The dates were showing as rolled back. (See previous images)

I reflashed stock + Magisk + dtbo. Dates rolled forward.

I've now reflashed Kirisakura. This time the dates did NOT roll back. Still showing as Nov 1/Oct 31.

This held through at least one reboot. So I don't know. It's definitely strange. Maybe I'll try Ex to see if it rolls back again. Not tonight though
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] LimitsX:
I don't believe its "rolling" back or changing anything.

I did a complete wipe of phone, even user data. Flashed factory Dec Android 10 rom. The security is at Dec. But the Google Play store was at August 2019. This is for Stock rom, no kernel, no root, nothing. No back restored.

I rooted with Magisk 20.1 and flashed this kernel, the Google Play store security update was at September then.

The kernel or AK3 flash isn't doing anything...
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] QRCode:
Using havoc 3.0 latest update got the famous error boot prepare did everything right flashing wise, spent an hour getting havoc back online flashed eX Kernal too see if it was the Kernal doing it wasn't it it so I left ex on, something isn't right with your Kernal and I couldn't log cat it either as it completely bricked my phone
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
sorry I can’t help you there.

The kernel is running fine on the stock rom. There were some changes in the December update, which are not compatible with earlier bases.

Make sure your device’s firmware is fully updated to December state, prior to flashing the kernel. That’s the best advice I can give to you. The easiest way to achieve that is by flashing the factory image to both slots. And then install havoc again. I don’t follow development of Havoc, so I’m not familiar with how to flash the rom on Android 10.

Other users reported 1.3.0 to be running fine on Havoc, so if somebody figures out a good sequence to flash make sure to let other people know!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] osm0sis:
I flashed an AK3 custom kernel (blu_spark) to my OP7T running OOS 10 (which is Android 10) and it had zero effect on any of the update/patch dates.

So I can safely say it doesn't seem to be anything directly related to the AK3 Core or Backend.

Edit

: I notice [MENTION=3428502]Freak07[/MENTION] doesn't have the 1.3.0 zip up-to-date with the latest upstream AK3 so it's using older magisk utils... could very well explain the issue. :(

I update things for a reason.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Yes I didn´t update my AK3 zips yet. No point denying that, sorry about that. That´s only a cheap excuse, but I´m currently lucky if I find time to update only the kernels.

That issue isn´t related to AK3, as far as I can see, being outdated or updated.

I uninstalled magisk completely and both security dates stayed exactly the same on my Pixel 3.

under security I have 1st October, under about phone I have 1st October on non rooted stock kernel

Security: 1st October and About Phone: 1st October on a rooted stock kernel

Security: 1st October and About Phone: 1st October on my kernel flashed with an "outdated" ak3 zip

Securtiy: 1st October and About Phone: 1st October on my kernel flashed with an "up to date" ak3 zip

I use exactly the same "outdated" ak3 zip on my Pixel 4 kernel, and both security dates are at 1st December 2019.

I always thought this was due to some Play Services related stuff, which I don´t understand.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] masri1987:
i just flashed 1.3 on dec update earlier today and experienced something supppper sketch.

Phone said it was turning off, i never asked it to, it was doing it as if i asked it to shut down.

I turned it on, it went to a screen saying my android data is corrupt, at this point i'm no where near home and my two options is factory reset and try again, i had to hit try again and it looped 5 times before it finally booted up.

Couldn't grab any logs, and i haven't been keeping up with what's happening in the threads.

I'm on stock rom. No magisk modules.

---------- Post added at 09:31 AM ---------- Previous post was at 09:28 AM ----------

Did it a second time, this time i was playing spotify, screen was on, it said it was turning off, just booted to the same android recovery screen.

Hit try again, i hope it boots up. I'm gonna revert back to stock boot and stock dtbo..... not sure what else to do.

Edit: i clean flash every update. .
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Unfortunately I have no idea, what is happening to you. I encountered this message (corrupt data) on my 1st gen pixel xl a few years back. It was because I messed up the slot system thoroughly.

did the phone change slots, when it was booting again?

If possible can you get me logs from sys/fs/pstore after a reboot happened?

I understand you’re not at home, but I’d try dirty flashing the factory image over both slots with -w removed, when you can. If that solves it, backup your data as soon as you can if possible.

Without logs, this could be anything. My 1st Gen Pixel XL has a unreadable section on the storage chip, which causes the phone to crash, as soon as data is read from there :(

That’s one of the worst case scenarios though.

If that doesn’t help try to completely clean flash the images again.

I’d wholeheartedly recommend to anybody to never flash anything to any A/B device, when not near a computer. No magisk module, no other mods, no kernels just nothing. Even if it works fine for others from reports. In case of a bootloop there is no way to recover without a PC.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] HamsterHam:
Did anyone that had the BSOD issue try that version of the kernel (without the fix) without Magisk installed? I'm thinking this issue must be a Magisk issue. Curious if anyone did try kernel with no Magisk.

Also yes [MENTION=3428502]Freak07[/MENTION]...I have learnt that the hard way. Flash **** in front of a PC.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] masri1987:
I am reflashing kiri kernel today and just observing, i didn't have a chance to grab any logs as it took several retries to get the OS to boot.

Thank you for getting back to me. It was so strange.

I have my personal laptop on me all day today so , if anything goes sideways
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] masri1987:
So far i haven't experienced what i previously reported, forgive me for causing alarm
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] exile1ck:
So I updated to 1.3.0 and tested it with the default settings (zram disabled) for 3 days. I then enabled it and noticed a big difference in smoothness. Is this some mistake?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
Zram disabled is NOT the default. Default is: zram enabled, zram size 2048MB, compression is lzo (iirc - I'm using lzo-rle), and I forget what the default is on swappiness, I'm using 175.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
no problem. I´d still advice to backup any important data stored on that device. Just to be on the safe side.

[MENTION=4487388]jcmm11[/MENTION] is correct. ZRAM is enabled by default with lz4, not lz0, algorithm. swappiness is at 100 by default. Personally I use 175 like [MENTION=4487388]jcmm11[/MENTION] :)

If it´s disabled on your device, you either used a script or a mod to disable ZRAM. Or something else changes it, like a custom rom or anything of the sorts.

The kernel is intended to be used with ZRAM enabled, because the userspace low memory killer, which definitely improved for me on android 10, expects ZRAM to be enabled and is built around it.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] fuzzgruble:
I've noticed kernel manager apps, namely FKM can sometimes cause zram to disable when changing settings about zram. Example, changed algorithm to lzo-rle and it disabled zram, then re-enableing caused the size to change to 512mb.

Why is it that you prefer swappiness set to 175?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Of course it needs to be disabled when changing the algorithm. ZRAM needs to be emptied and restarted completely for the algorithm to change.

Honestly I’d just leave it at default, if you notice no issues. The answer as to why is in my pixel 3 xl kernel thread, as well as my One Plus 7 pro kernel thread :) :svetius:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] fuzzgruble:
Found it!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
Yeah FKM still has issues overriding the compression algorithm. Franco's aware and there's an outstanding bug filed on GitHub. Exkm works correctly.

If you're using FKM just leave the compression algorithm alone. Swappiness can be changed with no problem.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] exile1ck:
What does changing swapiness do? I just set mine to 200 lol
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
See these release notes

https://xdaforums.com/pixel-3-xl/de...ra-1-0-0-pixel-3-xl-aka-t3864563/post80269185
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] darkstar73:
I updated today to the Dec update and running Kiri 1.3. I'm still dealing with the BSOD issue. I will try to get a log next time it happens.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dnsmo:
maybe you should disable all your magisk mods or even start fresh new, I am using the same build on stock with magisk, kiri 1.3 works wonderful on my pixel, no bsod, no auto reboot.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dirtyreturn:
Same here, sir!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] darkstar73:
Just clean flashed the Dec factory image and Kiri 1.3. So far no issues. However, the bsod usually occurs when I put the phone on charge or haven't used the device for awhile.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dark2099:
Have you tried other kernels? When you're having it happen when charging, makes me think it's hardware based on something with your port or charger, or cable. The other times could be some fault in power regulation, which could be at the hardware level if logs don't end up showing anything.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] darkstar73:
It's not hardware related since I can revert to Pie and it goes away. I'm going to put the phone on the charger overnight. If it works in the morning, then I can safely say the issue is resolved. Phone working great since I cleaned flashed the December factory image.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] darkstar73:
Just had another bsod!! Tired to get a log l, but the folder was empty. I'm reverting back to Pie because I'm over having to force reboot multiple times throughout the day.

Edit: I don't think this is a kernel related issue. Still happens when I ran either Havoc ROM or EX kernel.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dark2099:
I would look through all the apps you run and check the last time they were updated against when 10 came out, wondering if an app that hasn't been updated since 10 launched, or during the beta period, is causing the issue, if that is possible. Also, have you made any adjustments to kernel settings?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] HamsterHam:
You using Magisk? Tried without it?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] vprasad1:
Any chance related to this VPN bug?

https://issuetracker.google.com/issues/141188490
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Komodoketavaran:
Hey guys, i want to flash this kernel again but the last time i have flashed things were on pie roms..

So i'm a bit lost now. How to get root without TWRP?

Gesendet von meinem Pixel 3 XL mit Tapatalk
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] joetheshmo:
Search is your friend, but the process is like this until we have twrp on 10:

Download stock boot.img to phone

Patch the boot.img with magisk

Transfer the magisk_patched.img to PC

Fastboot flash boot magisk_patched.img

Boot into rom and flash custom kernel with EXKM or FKM
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Komodoketavaran:
Thank you sir. I was overwhelmed. Everything went smooth.

Funny fact: you answered me back in 2016 on my first question to the nexus 5X

Gesendet von meinem Pixel 3 XL mit Tapatalk
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] HamsterHam:
[MENTION=3428502]Freak07[/MENTION] - I did some testing as I had BSOD issues when using unicornblood and I didn't using your kernel (after your fix).

After all the commits from 7th Dec onwards I am getting no BSOD using unicornblood.

https://github.com/DirtyUnicorns/an...=045083b9f9ad36009ca1a1cf00538249cc38f0d5+174

Could be worthwhile you taking a look and seeing what Josh has added. ??
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] infamous84:
are they still making roms? went to their site, did not see anything recent
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Spannaa:
Yes.

They're currently working on DU14/Q/10 but as usual, it won't be released officially until it's finished and stable.

Check progress on their github & gerrit.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Opticuhl:
Great kernel! Is it possible to add support for DriveDroid?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Mrcactuseater:
Drivedroid has been deprecated, so I'd personally recommend just using a disposable USB for the same task!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dnsmo:
Jan patch is out and I am going to try on it with 1.3.0. I will report back in a bit.

edit: Installed 1.3.0 and booted up fine, so far so good. Hope no reboots.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Update with January sources will drop later today when I’m back at home! :)

Already compiled and running nicely on my end.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Cris7ianO:
Can anyone that updated to latest January patch share the kernel version with me? :)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jsauder2:
4.9.185-g9f181f6db9d7-ab6027027
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Cris7ianO:
Thank you for the fast reply :) I was just wondering if all went right due to the added date behind the version of

"#0 Fri Nov 22 18:17:08 UTC 2019". Because it states November. That confused me a bit. But as the version is the same as yours I guess it's fine and all went good ^^
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jsauder2:
Ya, it's weird. That shows Nov 30 for me too, security patch shows Jan 1, and play system update shows Nov 30 but when you click on it you see security patch level Dec 1...
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dirtyreturn:
Looking forward towards your release!

Just curious, anything changed?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] joetheshmo:
Is your fastboot environment up to date?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Homeboy76:
Make sure the USB is not plugged into a charging port.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] -iNSiGhT-:
Was about to say the same.

Had similar issues and all went flawlessly after i change USB port.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] DOMF:
I was on stock for a day or so, was completely smooth. Been on Kiri 1.4 for a couple hours and have had two crashes so far ? Freak07, do you want logs of some sort from somewhere?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jsauder2:
Instructions in the 2nd and 3rd posts about how to get logs.

I just had a reboot while scrolling through headlines in Google and casting a movie with Plex. Logs attached.View attachment logs.zip
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] DOMF:
Third crash ?

dmesg here, next up ramoops
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dark2099:
Was watching Instagram stories and froze/crashed. Logs for ya.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jj20042004:
Crashes with 1.4 kernel + Jan Update

Experiencing crashes using the following:

Stock Android with Jan Update

Magisk version 20.3 (20202)

all modules disabled + reboot

Attached are 2 zips with logcat and pstore.

Experienced crashes when watching stock version of YouTube and during using the Gboard voice dictation.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] DOMF:
Ramoops too large to attach

https://docs.google.com/document/d/14iFp1kpiXppG6Lo0cstp99V8-3CM-BKYUgQVImJx2dU/edit?usp=drivesdk

---------- Post added at 05:37 AM ---------- Previous post was at 04:38 AM ----------

Common factor in all my crashes (5 now) - I'm in Google Play Music every time.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Hey everybody,

so first off all sorry for the inconvenience caused by the update. That slipped through my fingers while I tested the kernel.

I built the kernel yesterday morning, device didn´t crash throughout the entire day, but I did not once use any app for media consumption.

Pushed the kernel in the evening and woke up to all the reports this morning.

I want to thank you all for collecting logs, describing the issue so I could reproduce it myself quite quickly.

It´s truly amazing to see everybody work together so nicely! Not one post with the sadly typical but usual attitude "it´s broken please fix it" without any logs.

Instead all of you provided logs and described the scenarios leading to the crash, which allowed me to reproduce the issue, look through the recent commits and most possibly to find the cause of the crash.

I tried to trigger the reboots for over an hour on the updated kernel now and it hasn´t happen since. On 1.4.0 I could trigger it a few times, without a few minutes on each reboot.

So I really hope it´s fixed.

Relevant section of the logs was here:

[ 1436.556363] c6 27550 Unable to handle kernel paging request at virtual address ffffff800ffe9000
[ 1436.556372] c6 27550 pgd = 00000000dcf41438
[ 1436.556374] [ffffff800ffe9000] *pgd=0000000176c83803, *pud=0000000176c83803, *pmd=0000000173768003, *pte=0000000000000000
[ 1436.556383] c6 27550 Internal error: Oops: 96000047 [#1] PREEMPT SMP
[ 1436.556387] Modules linked in:
[ 1436.556393] c6 27550 CPU: 6 PID: 27550 Comm: writer Not tainted 4.9.208-Kirisakura-Q-Release-1.4.0+ #35
[ 1436.556396] c6 27550 Hardware name: Google Inc. MSM sdm845 B1 DVT1.1 (DT)
[ 1436.556399] c6 27550 task: 000000003029bb09 task.stack: 000000008ae61275
[ 1436.556409] c6 27550 PC is at __memset+0x1ac/0x1d0
[ 1436.556414] c6 27550 LR is at snd_pcm_hw_params+0x5e8/0xad4
[ 1436.556417] c6 27550 pc : [<ffffff866e4884ac>] lr : [<ffffff866fd076c0>] pstate: 40400145

Which lead me to a commit introduced by linux-stable upstream 4.9.208.

If you´re interested the commit in question is linked here

I´ll post 1.4.1 in the next post in a few minutes.

Thank you all again this was truly amazing! Of course it would have been better, if I avoided it in the first place, but waking up to that amount of proper logs and bug reports allowed me to solve it super quick.

Thank you!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dark2099:
So flashed 1.4.1, went into Instagram, watched a bunch of stories with no issues, seems fixed on my end, will update throughout the day if anything comes up. And only those who don't know how to give logs and don't want to explain how they experienced any issues give devs attitude.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] DvLAx3l:
Thanks as always for ur work!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] FcukBloat:
i can see the dtbo.img in the zip, but not the boot.img

is it possible to get also the boot.img [MENTION=3428502]Freak07[/MENTION] ? I prefer flashing things through fastboot rather than installing one of those apps mentioned in OP... tia and either way
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
Part of what happens when you flash the kernel is integrating portions of the existing kernel into the new kernel. That's what enables you to keep root (among other things). Flashing an image would remove root.

It's also checking for things like removing verity, which depends on if you're on a custom ROM or not.

Bottom line is it's not quite as simple as just flashing a generic boot image.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dirtyreturn:
Hey jcmm11, can this be used on December patch stock? The 1.4.0 kernel I mean.

I'm just asking, because, if so, I would be able to make a kernel backup via exkm and fastboot it. Hope to hear from you.