yashsingh1/xdaforums huggingface dataset:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] muttonhead411:
Just realized CTS failing on me too. But how do you determine if it's kernel related?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] fonixmunkee:
It's not Kernel-related. I'm on the stock Kernel and am getting the ctsProfile: failure message.

There's a few threads on it in the Magisk forum. Looks like Google is getting sneaky at detecting an unlocked bootloader.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] ffuser1:
After taking the phone off the charger, it freezes and requires a hard reset. Has happened to me 3 times. I think this is kernel related but not sure. Can I just flash the magisk patched boot.img to uninstall the kernel and see if that fixes things (if it's kernel related)?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Lagarde:
No crashes or obvious issues in 1.5.1, but I am getting insane drain since updating. Due to timing, not sure if it's the March update itself or the 1.5.1 kernel update. Will do more testing to see if I can pin it down, but wanted to say something so that if there's others having something similar, we can all start gathering data.

1.5.0 + Feb update: ~2%/hr idle screen off, ~12%/hr idle with ambient display, ~14%/hr active with either screen off or ambient

1.5.1 + Mar update: ~4%/hr idle screen off, ~16%/hr idle with ambient display, ~21%/hr active with either screen off or ambient
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Tekken Lord:
I used "flashall" without -w to flash with every update, so I don't have any issue....I believe Google broke its tradition and released a new kernel with this March build. With that all said and done, I would recommend to be patient and let the dust settle in for a few days. The battery and the system will need time to adapt to a new algorithm.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Lagarde:
Precisely the same method I use. Given that my phone is scalding, it's going to be hard to let it just settle.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] infamous_black:
Running 1.5.1 kernel on pixel 3 using lineageos 17.1 and it's working for me so far. Getting about 4-5 hours of SOT.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] qualitymove13:
I am actually getting both of these issues. Got the dreading "phone is too hot, some settings unavailable" message for the first time since owning the phone. Ill wait a couple more days to see how it shakes out before grabbing a log.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] xuser_:
[MENTION=3428502]Freak07[/MENTION], Guys

We know that google officially removed DSDS feature but if anyone know any workaround for the same in any rom or someway please do share it here for all such users!

Thanks
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] gacky1601:
https://xdaforums.com/pixel-3/development/mod-pixel-3-fast-wireless-charge-t3889374/page5

Why this doesn't work in Android10 ?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Lagarde:
Minor update:

- Connecting bluetooth (any bluetooth), even if it's not in use, causes a huge spike of drain. It always did, but it's a LOT worse now. Idle BT seems to be adding about 5-6%/hr drain. Active BT is only 6-7%...which is funny since the last few updates supposedly lowered BT drain, according to Google.

- Ambient display is draining much more than it used to. I'm used to it adding about 1-2%/hr. Now it's closer to 4%/hr. Phone up, it gets hot and drains fast. Phone face-down, it cools off and drains slower.

- No errors, reboots, or lockups, so the above issues are likely a stock issue, rather than Kiri.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dnsmo:
SAD, no more root for us/
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] KurioHonoo:
What's DSDS?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dd805bb:
https://twitter.com/topjohnwu/status/1237656703929180160?s=19

John is saying end of life for magisk, now. Has nothing to do with this or any kernel. Google is going to be implementing TEE now. Which has been slowly added to Android over the past few years. Now, with the March update they are flipping switches. There is a fail safe in place for now but by Android 11 root will not be able to be achieved. Read his Twitter and the links he shared. A work around is almost impossible unless some vulnerability is found in TEE which is highly unlikely or one chip related. Basically magisk is over. Read for yourself please before quoting me and saying something half cocked.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] xuser_:
Dual SIM Dual Standby(DSDS) which allows users to use multiple sims at a time, but in stable release of android 10 for atleast pixel 3/XL we have DSSS(dual sim single standby) in this case user have to switch the sims as you can add multiple sims(eSims) but at a time only one sim can be used.

There seems to be a workaround mentioned on reddit,

https://www.reddit.com/r/android_beta/comments/cetxng/guide_get_dsds_dual_sim_dual_standby_on_pixel/

I havent rooted so did not try it.

In case anyone tried, please confirm if it works on the latest stable release.

Thanks!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Face_Plant:
My understanding of what I read on his Twitter feed and the XDA article summarizing the situation is Magisk can no longer hide bootloader unlock, not that root is impossible. It sounds like we'll still be able to root, but we can't spoof the bootloader status, which means no more Google Pay, Pokemon Go, or other apps that check SafteyNet status on a rooted device.

To those that rely on and can't live without Google Pay or whatever this might mean no more rooting, not because it's impossible, but because they can't use their phone to buy coffee at the gas station anymore.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] nullness:
I'm seeing 21.84% per hour active, and 2.75% screen off over 4 days on 1.5.1 which pretty much matches exactly what I saw 1.5.0. I do have Bluetooth always on and use it a couple times a day, and haven't noticed any additional drain.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Porogami:
I'm also noticing much higher drain most likely due to the March update not the kernel as I've seen reports in other threads. Active is around 20% up from 15% in Feb and idle overnight is 1.4% compared to 0.8%. Gsam says that Android system is draining a huge amount both active and idle, much higher than kernel drain and looking into wakelocks, mountserviceidler seems to be on the top.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dnsmo:
basically the development scene is dying slowly.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dnsmo:
april patch is out, I am going to try it on that for 1.5.1 and will report back

After checking the change log maybe I should wait.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] qualitymove13:
What about the change log made you pause?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dnsmo:
In fact I did it anyway. So I am running 1.5.1 on April patch right now. So far no problem. I will report back if there is anything.

-------------------------------------------------------------------------------------------------- edit 1,

well, my home dot is gone now, won't show up. I dont know if that is related.

--------------------------------------------------------------------------------------------------edit 2,

It is related, after I flash back the magisk_patched.img to the boot img, my home button is back. So don't flash 1.5.1 because it will break the home guesture.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Yes like I usually post every month it’s always best to just wait a day until I update the kernel. ;)

However your post got me very curious, because this seems to be completely unrelated to the kernel. Especially after I saw what code changed in the April update when I merged it this morning. I’m 99,9% sure your issue is not related to the kernel and rather related to a magisk module or something else entirely and just coincidence.

So I went and flashed 1.5.1 on my April updated Pixel 3 Xl and the home button/gesture works with all 3 gesture modes :)

I’ll post the updated kernel later today though, after I made sure everything works as intended. So just keep an eye out :svetius:

P.S.: To restore stock conditions you need to reflash the stock dtbo.img from the factory image as well.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] gvsukids:
Is this a concern when flashing a new security update? Or only returning the kernel to stock?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dirtyreturn:
I think it's just for returning to STOCK.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dark2099:
If you're manually flashing the monthly updates, both files are dosages automatically, but if you need to return to stock, you need to do this manually.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dnsmo:
with 1.5.2, I have no problem, so I don't know what happen to the home dot, as far as I know, I have the same items in magisk before and after. Just to report back.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] ytgbg:
[MENTION=3428502]Freak07[/MENTION] April's update runs amazing here on my Pixel 3 XL.

One of the reasons switching to Pixel 3 XL was your kernel. Looking forward to it.

Do you have Telegram Group for testers or for your kernel in general?

Did you brickport some features from 4.14 and 4.19. Do you plan switching to PELT?

Thanks for your work, mate!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dnsmo:
new patch is out, should I test the kernel?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Update 1.5.3

Hey guys and girls,

Update time :) Linux-Stable, May Update, Wireguard etc. Detailed changelog below

Just in case:

If you face issues or bugs when running the kernel, please return to a stock environment, only your rom plus magisk root, without any modules, scripts, tweaks or mods and see if you can reproduce the issue.

Tell me the exact steps needed to reproduce.

Then send me a dmesg and a logcat (if the kernel crashes not) or a ramoops (in case the device reboots). Take a look at the second post for a guide on how to obtain these.

My kernel.zip flashes both boot.img and dtbo.img. So if you want to return to stock, you need to extract both from factory image and flash them via fastboot if on stock rom.

If you’re on a custom rom you will need to dirty flash your custom rom or learn how to extract both images from a payload.bin

Special thanks to [MENTION=4487388]jcmm11[/MENTION] and [MENTION=336855]melgar[/MENTION] for testing and keeping up with me!

I wish everybody a nice day/evening! :)

Changelog:

- Update google sources to latest May state

- Linux Upstream to 4.9.220

- update prebuilt Clang to 11.0.1

- update wireguard

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?

Download is below :)

Download:

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

or following the link in the op to the correction version

How to flash the Kernel:

1. Make sure you are rooted and either EXKM or FKM is installed. Download the kernel.zip to your device.

2. Flash kernel zip in EXKM or FKM app. Root will be preserved!

3. Reboot and profit! Before reporting any issues make sure to read the Release-Post of Bluecross_Q_Release_1.1.3!

Instructions can be found in the OP 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/green tea: http://paypal.me/freak07
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] muttonhead411:
Thanks very much [MENTION=3428502]Freak07[/MENTION]. We don't say thanks enough for keeping consistent with your kernel releases. You are awesome!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Raul Fresh:
Hello sir, Is this kernel good for battery durability and perfomance in the Pixel 3 XL ?

and.. is necessary be root to flash the kernel or it can be flashed via ADB?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dnsmo:
root is required I believe, I loved this kernel, this is all I am going to say. :)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Raul Fresh:
I see... I'd like to try another kernel that stock, but without having to root the device, and Idk..:(
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dnsmo:
I don't believe that is an option, unless some else tell me that is wrong this is as stock as it could be, I am running a stock image from google then just use magisk to root and apply the kernel.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] luckana:
Actually, when i dirty flash the rom updates on the first boot i don't have root but i do have a custom kernel right off the bat. So technically it maybe possible idk. Although, totally pointless and a waste, imo.

Edit: pretty much if you flash a rom that ships with a custom kernel precompiled, then you can rock without root, or at least i think so. Which is again probably not like having the same kernel rooted
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Edit: pretty much if you flash a rom that ships with a custom kernel precompiled, then you can rock without root, or at least i think so. Which is again probably not like having the same kernel rooted

This statement is wrong.

There are a few things that need to be corrected in the posts I quoted.

A kernel cannot be flashed via adb. However a boot.img contains the kernel and can be flashed via fastboot.

The kernel.zip that´s provided here (and contains the kernel, the dtb and the dtbo.img) can be flashed via EXKM or FKM. Once TWRP works correctly it can be used as well. For now we rely on the kernel managers. Both of these require root!

You can repack the boot.img of whatever firmware you are on, doesn´t matter if stock or custom rom, with the kernel and the dtb that´s provided in the kernel.zip yourself. However that requires a bit of work and research on your side if you don´t know how to do this.

You can flash this repacked boot.img in fastboot along with the dtbo.img found in my kernel zip and can use the kernel without root. However you can´t change any kernel settings from its default values.

That means no "switches" for features like KCAL without root.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] djcrystals:
So, specific to this kernel and Crosshatch, I have a question. I've been rooting and flashing for years but when it comes to kernels I feel like I own a Corvette but obey all the traffic laws. I've played with them a bit, specifically with this one I've been adjusting the display settings but that's it. I have FKM installed, which I recently purchased. I'd love some tips/recommendations/suggestions.....I was messing with something with the display earlier and had to stop because the app started crashing. It was fine after a reboot.

Anyway.....I've got more than enough time to mess with this during quarantine.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Tekken Lord:
Someone good members and I use: Compression algorithm at "lze-rle," and Swappiness at 175%. You would have to explore this thread for more info as to why. Good luck and enjoy your time off.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] venkatsrin:
Can I flash this kernel on the developer previews for Android 11?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] djcrystals:
I'll check that out. Thanks!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] qualitymove13:
How do you get this to stick? Once I change over to lze-rle I get the "resetting z-RAM to apply....." message then it sits for a few minutes and ultimately reverts to lz4. TIA
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] djcrystals:
Yea, I noticed that....
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] rspkt:
Works fine for me using FKM on 1.5.3 and latest firmware.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] LimitsX:
How do I flash boot.img and dtbo.img from your zip file? I don't really make any changes to kernel settings. So, i dont need root, just need the kernel.

I extracted files from your zip. I found dtbo.img, and image.lz4. I extracted image.lz4, which gave image. I re-named image to boot.img and flahsed it in fastboot mode and then dtbo, but I get "error boot prepare"

I installed stock May rom and had USB-debugging enabled.

Any help?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
To restore working conditions simply reflash the boot.img of your firmware.

I chose to provide my kernel in the format of a flashable anykernel.zip. That requires root as long as TWRP isn´t fully functional. The anykernel.zip works dynamically and flashes the kernel accordingly no matter if you´re on a custom or the stock rom.

Providing a boot.img for every single custom rom along with the stock rom is simply not practical.

If you want to use it rootless you are on your own as I mentioned before :)

Here´s are some clues that should lead you to what you want to achieve.

The image.lz4 is the zImage. It´s part of the boot.img. You need to unpack and repack the boot.img of your firmware with the zImage and the dtb image found in my kernel.zip.

There are guides on XDA for doing this. However you probably need to do some research if you never did this before. A very good tool is the following one:

https://xdaforums.com/showthread.php?t=2073775&page=13

Alternatively you can do this with the magiskboot binary.

Once the boot.img is repacked successfully you can flash the boot.img via:

fastboot flash boot boot.img

and the dtbo.img from my zip (no need to change it) via:

fastboot flash dtbo dtbo.img
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] LimitsX:
Thank you for the explanations and clues. Really appreciate it.

For the stock firmware boot.img:

1.) unpack it.

2.) repack it using zlmage (image.lz4) with dtbo.img from your kernel zip?

There are two dtbo files in your zip, and the original boot.img has following dtbo: boot.img-dtb and boot.img-dtboff.

Do I need to decompress image.lz4 or include it as it is when repacking? As per what you said, If i need to include dtbo.img then I don't need to unpack dtbo.img to be included in the repacking?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
There is only one dtb file inside my kernel.zip and one dtbo.img. Read my previous post again. The dtb needs to go inside the boot.img to replace the stock dtb.

The dtbo.img is to be flashed via fastboot without further editing.

if the zImage inside the unpacked boot.img is compressed, then you can use the compressed file, if it´s uncompressed you should decompress before replacing. :)

you can also try magiskboot binary. It´s a bit more automated and can handle different compressions as well.

Instructions are here:

https://github.com/topjohnwu/Magisk/blob/master/docs/tools.md
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] LimitsX:
Thank you for the clarification. I got it.

I got it flashed without root now :D!!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jj20042004:
Hi [MENTION=3428502]Freak07[/MENTION],

Thanks for your consistent efforts in providing up-to-date Kernel updates! :good:

With that being said, just wondering :fingers-crossed: if you will be supporting the June patch.

Much thanks again!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Tekken Lord:
I bought him a cup of tea a while back, did you?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] nikhilnangia:
I'm sorry, but this is not right. He/she asked a simple question - something that comes with no pre-conditions. I'm sure Freak07 will agree, too, that while it's always a nice gesture, there is no pre-condition to buy him something to ask a question on here.

A simple "don't push the developer, don't ask for ETAs" would have sufficed. Besides, you bought him a cup of tea. That does not make you a moderator of the thread. Let's be respectful towards everyone.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Tekken Lord:
I am sorry, I also asked a simple question. I totally respected that poster when he tried to ask that simple question. Perhaps, I wrote a short sentence, and it might have come across as disrespectful. You, on the other hand, should not put words in my mouth. I've never claimed to be a moderator of the thread.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] nikhilnangia:
:) You're right- the short sentence was probably it!

I'm sorry for the misunderstanding. The perils of online posts and miscommunications! No harm done. Thank you for clarifying!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] crixley:
No you were right the first time. It was pretty obvious his intentions from asking that question.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dirtyreturn:
My intention is not to be sense. Edit-dense

I wanted to get the OTA, but, for whatever reason there's no backup of the stock images from within magisk. So that's not possible for me.

What partitions exactly have to be flashed manually to upgrade fully?

What I'd like to do is patch the latest boot.img from the June firmware before proceeding...

Like, do the product.img , super_empty.img, system_other.img need to be flashed ?

Or, could I get away with boot, bootloader, dtbo, radio and vendor be enough?

Oh, and system.img.

Hope you'd be willing to help, thanks.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Tekken Lord:
No need to beat the dead horse, buddy. We settled it. I hope we won't see anymore of this, or mods will most likely give us a warning.

Thanks,
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dnsmo:
I would just wait for it to drop because that's what happen. thank you
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] joetheshmo:
Download the full factory image, not the OTA
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dnsmo:
get the full image, then edit the flash-all.bat, removed the -w at the last command. There is a very detail how to guide if you just look at the how to guide.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dirtyreturn:
Yes, sir! Got that downloaded

Ahhh, thanks for helping things to click! I patched the boot.img with magisk. I've just gotta flash that via fastboot and I'd be ok, right?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] BostonDan:
No. Be careful. On Android 10 just flashing the patched boot image will leave the boot on the Google G and not proceed.

Please search for updating magisk with OTA security patches. There is a tutorial out there that explains how to add the stock images required to uninstall magisk with the stock images prior to updating with the OTA security images and then reapplying magisk to the inactive A/B slot. Between this process you do NOT want to reboot or you will lose Magisk and have to wipe the phone.

Hope this helps. I will try to find and link the tutorial on how to add the stock images require for magisk to uninstall back to stock.

Edit: found the post that explains how to add the stock images for Magisk.

https://xdaforums.com/mi-a3/how-to/guide-create-manual-backup-stock-boot-t3988345

Cheers,

B.D.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dnsmo:
You always had the stock boot.img in the full image file. Unless you somehow manage to screw the bootloader up, I think you are safe.