yashsingh1/xdaforums huggingface dataset:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] yung40oz84:
Ya I am running 2.2.0 and it's fixed, lol.

---------- Post added at 08:06 PM ---------- Previous post was at 08:05 PM ----------

It's not really dangerous, lol. If you flash it, it isn't going anywhere unless u flash a rom or update stock. What's dangerous? I've never had an issue, I've been using TWRP since day 1.

---------- Post added at 08:08 PM ---------- Previous post was at 08:06 PM ----------

I use notification helper, that's it. There is also usb audio policy patching and of course the original option for audio compatibility.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
I agree. I wouldn´t flash anything on A/B devices when no computer is nearby, at times I need my phone to be working at all cost.

That´s simply due to the fact that there´s no recovery partition on A/B devices. The recovery now sits inside the ramdisk! So once you cannot boot up, you might also have troubles booting to permanently flashed TWRP.

This can usually be easily fixed by fastboot booting TWRP, but only when a PC is available.

For those interested this is a pretty good summary:

https://www.xda-developers.com/how-...ess-updates-affect-custom-development-on-xda/
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] zandander:
Random... Does anyone have a zip of the stock kernel?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] -iNSiGhT-:
Hi,

Just had a random reboot. Phone was in my pocket, locked.

Couldn't get pstore folder content since I'm not rooted...

Maybe I will root so I could help in those cases.

Can I root by just flashing Magisk or do I need to flash Magisk, then the kernel again ?

Thanks for your amazing work ! (Not an issue since I own my Pixel 3 XL, since 2.1.x releases)

---------- Post added at 01:37 PM ---------- Previous post was at 01:35 PM ----------

You can find it inside the factory image.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Hey thanks for the report!

are you running stock rom? What did you do previously to putting it in your pocket?

Just flash magisk and you’re rooted if you’re on my kernel already. :svetius:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] -iNSiGhT-:
Yes, I'm on April stock. Just your kernel over the top.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] HamsterHam:
Did you find out? Curious as well.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] devam1995:
Hey! Thanks for the kernel just flashed it on the April security update and everything seems to be great so far. Coming from a OnePlus 6t to the pixel 3xl everything on this phone seems to be better than the OnePlus except the battery life. But one more thing I've noticed on all pixel kernels is that somehow nobody has one that is running under locked out of the box ? From what I know running might help us lower temps and boost battery life without affecting performance ! Thanks for the amazing kernel though it's the best one for this phone I've tried yet so far! Have a nice day ?!!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] devam1995:
Continued*
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] joetheshmo:
Are you aware of how links work?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
Freak07 responded at the end of https://xdaforums.com/pixel-3-xl/de...ra-1-0-0-pixel-3-xl-aka-t3864563/post79298645

Based on that response my best guess is that some upstream changes (as in mainline Linux kernel) were responsible for fixing this. But no I don't know for certain. Just glad this kernel has it working as it should be
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] HamsterHam:
Interesting. Don't think it's just upstream that fixes it as other kernels are upstreamed but don't have the fix. Either way, it works with Kirisakura ????.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Paz9:
delete
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
I said it was a guess. If I had a proper computer instead of the junk I currently have I'd track it down but as it stands I'm just happy that this kernel works.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] c_86:
Links!?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Paz9:
search them in magisk downloads

also does this kernel work on android Q preview?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] kaicat:
Search from magisk. They are magisk models;)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] c_86:
Derp. Don't know why I didn't think of that.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Hey :)

Here´s a test zip for you. It has the f2fs updates from f2fs git reverted, which were merged in 2.1.2.

If the issues are present on this build we know that one of these f2fs commits fixes the issue with magisk.

Please report back. Thank you.

https://www.androidfilehost.com/?fid=1395089523397939992
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] HamsterHam:
Just tested and app data with this kernel and magisk still shows up correctly.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
maybe just to confirm.

Uninstall all magisk modules, do a reboot.

Flash magisk uninstall zip, do a reboot, reinstall magisk.zip, reboot, reinstall modules in question, see if it still works correctly.

Just to confirm so we´re absolutely sure.

maybe we´ll notify [MENTION=4487388]jcmm11[/MENTION] too. Then we´re having more devices to test on.

I never saw this issue. I´m just trying to narrow down, which commit fixes it.

You said other upstreamed kernels still show the unwanted behaviour. That really only leaves these f2fs commits as a potential "fix" to this issue. Now that they are reverted the issue might come back.

We´ll see :) thanks for the report! Play with it a bit more and report back in case something happens. :good:

you could also try to flash back 2.1.1 and see if you immediately face the issue? that way we are sure we can reproduce the issue easily!

I´m no big help as I don´t know how to reproduce it exactly.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] HamsterHam:
[MENTION=3428502]Freak07[/MENTION] - it still works on 2.1.1
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Well I only know what [MENTION=4487388]jcmm11[/MENTION] stated in his posts.

Did you have the issue in the past on your phone?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jlee08517:
Just want to report. 2.2.0 had some bad idle battery drain. My sot was around 3 hours from when the battery was fully charges.. Thought it was my apps but I went back to 2.1.3 and everything is back to normal like getting sot of at least 4.

Stock rom +kernel and magisk installed. No magisk module. No difference between apps I own between 2.2.0 and 2.1.3. Just the kernels and observed the drain
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] HamsterHam:
Yeah I did, not anymore as I flash Kirisakura. Don't worry about it.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
Now that's interesting, and confusing.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
So it’s not working for you as it seems on 2.1.1?

I think you know the steps to reproduce. Could you try the 2.2.0 test zip I posted earlier today and see if it’s broken too?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
I'll try it in a bit. Trying something else first. It seems (and somebody posted this somewhere else which is why I chose these particular ones) that it's also dependent on what Magisk modules you have active. Still running 2.1.1 I just deactivated Edge Sense + JamesDSP + AML + Sauron and now it's working correctly. Later kernels work correctly even with those modules active. Going back to try 2.05 again with these modules still disabled. Then I'll try the test file, and re-enable the modules.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
Went back to 2.05 and, with those modules disabled, it works correctly. (2.05 was the first one to be problematic)

Installed test kernel. Re-enabled Magisk modules. Still working correctly (see images). So there's some interaction going on between the kernel, Magisk Hide, and certain installed modules that's causing this issue. Change any one of the three (for some versions of kernel and some modules) and the problem goes away.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
the kernel itself does drain nothing. Services or apps request wakelocks from the kernel and the kernel grants it usually.

There were no changes in 2.2.0 that would cause it as far as I’m aware.

I did a quick 5 minute test run with Better Battery Stats and my phone sleeps perfectly fine.

Maybe flash 2.2.0 and a simple reboot might fix it. I can almost guarantee (99,9%) it’s not the kernel itself.

Use Better Battery stats to get a good understanding what’s happening on your phone during idle. :svetius: let your phone lay idle on a desk for one hour and check wakelocks and alarms. :svetius:

I attached a screenshot from a 5 minute idle screen off period.

Usually everything above 90% deepsleep is very good.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] LimitsX:
I will give that app a try as well. I noticed when using the latest of this kernel, battery seems to be draining. I debloated of google apps as well :\.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] LimitsX:
So I am posting some stats regarding battery drain

I have stock Google ROM with most Google apps removed

I have attached the screen shots.

The kernel and it's wake lock seems to be causing the drain
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
As I said use better battery stats. Power manager service wakelock is a culmination of all partial wakelocks held by userspace (your installed apps). The app you used is extremely confusing to users with no deep knowledge.

More information here: http://asksven.github.io/BetterBatteryStats-Knowledge-Base/howto.html

From the link:

The PowerManagerService wakelock

This wakelock shows as a sum of the partial wakelocks on many phones. If this wakelock is #1 go to the Partial Wakelocks to find out more.

Your screenshots shows exactly what I told you earlier. Apps/Services request a wakelock from the kernel and the kernel grants it (power manager server wakelock). If the kernel would not grant the wakelock the apps/services would not function properly. There is no way for the kernel to know if these wakelocks actually "hurt" your battery life. If an app has gone "rogue" or is poorly written it may need excessive wakelocks and thus drains your battery.

Use Better Battery stats (free on XDA) to determine the cause of the drain. Set a custom reference, let the phone sit on a desk for 1 hour doing nothing. Then check partial wakelocks and alarms. This way you may find the culprit.

If you get 90% deep sleep (or more) of this 1 hour your deep sleep is fine.

There are many social networking apps, like facebook etc that are known to cause background drain.

Also the Better Battery Stats thread is a good starting point to start some research, if you really want to dive in that topic.

If the kernel itself was at fault there would be other symptoms, because sleep would be completely broken in most cases.

Good hunting with BBS! :) [MENTION=3185414]LimitsX[/MENTION] I had to edit this post as it got cut off.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
so if it´s now working with a kernel that wasn´t working previously it isn´t something in the kernel? I´m a bit confused now.

Is there any easy way to reproduce it?

And you´re not able to reproduce the issue with the test kernel I sent you earlier today?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] LimitsX:
Thank you! I will look into it, but when I am using my phone, I literally lost 5% for texting purposes within 20 minutes? I tend to lose battery very fast while using for browsing (5% loss less than 30min of use). Which is strange.

let me observe further though! Kernel is smooth though, no lag whatsoever.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] HiM@L:
[MENTION=3428502]Freak07[/MENTION]

got one reboot and log.

i am pretty sure this might be from magisk module i installed but this is second time so i am getting this log, hope there's no other cause.

this happened after i installed magisk module and rebooted after which i unlocked but screen hung and become unresponsive and rebooted automatically.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Face_Plant:
Deleting Google apps could be your issue. If app "A" or the OS relied on app "B" for a certain task, then the phone will often get held awake while app "A" or the OS waits for a response from app "B". Did you fully delete all Google apps or just disable them?

How bright is your screen while you're doing these tasks? Screen brightness is generally considered the number one battery drainer. What apps do you use for texting, browsing, etc? If they're poorly written then they will put a larger strain on your phone's resources and drain your battery faster.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
No, I can't reproduce it with the test kernel. Let's see if I can explain this.

As near as I can tell there's 3 components that are required for the problem to appear.

1 - Magisk Hide needs to be active (enabled by default).

2 - kernel has to be, or be based on, Feb 2019 stock or later. The only exception I know at the moment is Kirisakura 2.1.2 or later. Kirisakura 2.05 through 2.1.1, inclusive, do show the problem.

3 - the final component is that you also need to have a Magisk module installed that triggers the problem. Not all modules trigger it. The initial report that mentioned this ( https://github.com/topjohnwu/Magisk/issues/1109#issuecomment-480601046 ) states that (at least for him, don't know all the modules he has installed) any one of Systemless Hosts, Edge Sense, or Ainur audio will trigger it. When I tested I didn't remember that he had also mentioned Systemless Hosts and didn't disable that. That didn't appear to trigger in my case. I did disable Edge Sense plus all audio mods that use AML and that did make a difference.

I don't know if it also happens on the Pixel 3 or if it's specific to the XL. If you want to try and trigger it install the Active Edge module and the stock kernel. That should be enough.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] 21cdb:
On the latest AOSiP with Kirisakura 2.2.0, the flash doesn't work in video mode in the camera. It says the device is too hot and the flash has been disabled. It works fine with the AOSiP included kernel, so it seems to be a Kirisakura kernel issue.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] flipflop1:
It's not, the problem is from aosip, use stock rom instead of custom.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] HiM@L:
if your phone gets too hot, system automatically shuts down some functionality and i am guessing this might be it. what have you been doing when the got that. was it to exposed to sun?

i have got this when i was driving and charging my phone and it was really sunny and hot.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] 21cdb:
It's not hot at all, it's always disabled no matter what the temperature. If I flash AOSiP and not Kirisakura, it works fine. Flash Kirisakura and it's disabled again. Flash AOSiP again and it works.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] HiM@L:
hmmm... this kernel works perfectly fine with stock and DU.

you should probably check with AOSIP dev.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Dark_Eyes_:
From stock ROM... And no, the phone isn't hot at all.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
No kernel crash in this log. So it´s probably the module as you suspected.

Okay, I might look into this again.

That slipped through all of my testing as it seems. It affects only video mode, which I never used in combination with flash until now it seems.

Thanks for the report :)

I´ll see if I can figure it out :)

EDIT:

I think I figured it out. Currently building new kernel.

Next release will include the fix for the camera flash when in video mode issue :)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Alright it’s fixed!

Thanks for the report [MENTION=5445418]Dark_Eyes_[/MENTION] and [MENTION=4331285]21cdb[/MENTION]
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] #Teampixel:
Any noticeable battery improvement over stock with this kernel? Have really seen much feedback about it lol
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Spider_Pig27:
Question for those of you who have been using this kernel with DU. After how long did battery performance get better for you? What type of set ups did you guys use?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] c_86:
Looking forward to it!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
It depends entirely on your usage. Just give it a try, it´s easy to return back to stock :)

I mentioned it a few times already. I won´t cripple the speed of the phone, by restricting frequencies etc, just to get 10 minutes more SOT at the end of the day.

Somebody already mentioned it in one of the last posts: The screen needs the most power and no kernel change will ever change this.

The phone has an in built power saving mode, that does exactly what it´s called.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Hey guys and girls,

I hope everyone is doing well. This is the hotfix release, which allows the flash to be used in GCAM´s video mode again.

A nice weekend to everybody :)

Changelog:

- Revert a Q Preview 2 change, which breaks the thermal hal and renders flash unusable in GCAM´s video mode on PIE roms

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=1395089523397942774

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] 21cdb:
Appreciate the quick fix! Thanks!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Horoscope:
wht is the procedure to flash the latest build on existing Kira kernel with root
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] rspkt:
1. Download the latest build

2. Boot TWRP

3. Select install and navigate to the new kernel version you downloaded and install it

4. Reboot system

5. Profit

:good:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] DvLAx3l:
Or flash It through EX Kernel manager app ?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] kaicat:
Do we actually need these magisk modules after installed this kernel?

1. Swap Torpedo(zram, memory tweaks or something)

2. Ram management fixed

3. Sysconfig patches

I think the kernel has already tweaks the memory stuff, but I'm not sure if these modules will improve more
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
No I never said they are needed and I don’t recommend it :svetius:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] kaicat:
Thanks
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] HiM@L:
[MENTION=3428502]Freak07[/MENTION]

had another reboot but this time while trying to open an article.

i have attached files inside /sys/fs/pstore/.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] 21cdb:
I'm not sure if this is a kernel issue or an AOSiP issue, but I have this problem where I keep getting kicked back to the lock screen and my connection resets. If I unlock my phone, the app I was in is still there exactly as it was, and my connection (wifi or mobile data) reconnects and things are fine for a while. I have no idea what triggers it, it's really inconsistent. It's really annoying if I'm watching a video and I keep getting kicked to the lock screen every couple of minutes. Sometimes it can be hours between when it happens, and there doesn't seem to be any rhyme or reason to it. Any thoughts? Latest stable AOSiP and latest Kirisakura.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Drewski_1987:
Same thing happened to me on scorpion rom
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
I’m on DU for months now and did never encounter this behaviour.

Does it happen only with videos or all apps?

You can try to immediately take a logcat and dmesg via EXKM app right after you pass the lockscreen again.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Drewski_1987:
It happened when I casted YouTube to my TV. I switched to stock Q beta now.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] 21cdb:
It happens with all apps, I can be in the middle of typing a text and the next second I'll be on the lock screen. Unlock with fingerprint and see I have no connection for a second or two, but my app is right where I left it (except if I'm playing video, that will have stopped.)

I'll try getting a log next time.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jstoik:
I had experienced similar behaviors on stock on my XL, but it happened with and without Kiri (and with and without Magisk). Given the corresponding dropped network connections, I wondered if perhaps Project Fi was to blame.

The issue has fully vanished since switching to DU, though, so it is hard to say. :confused:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] 21cdb:
I'm going to try DU again now that they have weeklies. That was one of my favorites back in the day, hopefully it's still good. I assume they are on April security patch and work great with the latest Kirisakura? It's hard to find info on their blog.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Spannaa:
DU 13.1 is on the April patch and it works really well with Kirisakura 2.2.1

As a bonus, TWRP 3.3.0 has been fixed so that it can flash DU officials and weeklies on the Pixel 3 (and MTP works now too).
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Gordietm:
What do you TWRP 3.3.0 has been fixed?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
There is no kernel panic that’s causing the reboot. Did you play with memory management at all?

Or some app/module that alters it?

I don’t think it’s the kernel at this point, but you can continue to send me logs and I gladly look at them. Maybe we’ll find something.

It would be nice if you somehow find a way to reproduce the issue and could take logcat as well as dmesg (with dmesg -w) while the crash happens.

There’s nothing in that log that shows the kernel panicked :(

Thanks for the report though!

Well if it happens regularly to you it’s most likely not a kernel issue as I would have noticed it definitely too.

As I said logs would be good. (dmesg and logcat immediately after it happened)

Maybe he’s talking about blueline not crosshatch. Since this is a unified thread.

Just a guess :) maybe there’s an updated crosshatch build up, I didn’t check since yesterday.

I wish everyone a nice day!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] MArtyChubbs:
It's up :)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] 21cdb:
TWRP 3.3.0 doesn't seem to decrypt the internal storage on my 3XL, not sure what's wrong. It's working on the regular Pixel 3?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Spannaa:
Yep, I was talking about blueline - TWRP 3.2.3-0 for Pixel 3 couldn't flash roms signed with private keys like DU official & DU Weeklies but TWRP 3.3.0-0 can.

Apparently TWRP 3.3.0-0 for crosshatch can't decrypt data so, Pixel 3 XL users should stick to 3.2.3-5 for now.