Dual eSIM support seems to now be working for some Pixel 7 users! One user reports that the feature "just started working" for them on Android 13 QPR2 Beta 2. Is this working for any other Pixel 7 users? For context, the feature mentioned in the linked tweet, eSIM MEP, enables you to use two eSIM profiles simultaneously. Hence MEP = Multiple Enabled Profiles. Read this for more details.

The Pixel 7 series does indeed declare the android.hardware.telephony.euicc.mep feature, which tells the system it supports MEP. I don't know if any radio HAL changes were made in QPR2 Beta 2 to enable this. I think it's more likely that the SIM Manager app had a server-side update to allow this and that the Pixel 7 was already capable. The version of the SIM Manager app that comes with QPR2 Beta 2 is D.2.1.493483802-google, if you're wondering.

This same user reported that dual eSIMs weren't working for them on Android 13 QPR2 Beta 1. Google Germany previously told Andreas Proschofsky, an Editor at The Standard that the Pixel 7 series will get dual eSIM support via an update that was targeted for March 2023. So we're expecting this feature to land soon regardless!

UPDATE: A 2nd and 3rd user have spoken up and said that dual eSIM is working on their Pixel 7!

Alongside the release of Android 14 Beta 1 for Pixel, Google also released Generic System Images (GSIs) for Android 14 B1! Same build (UPB1.230309.014) and SPL (April 2023) but they're installable on (theoretically) any Project Treble-compatible device - excluding devices with an Android 9 vendor.

In general, it isn't recommended for you to install a GSI through DSU - there's a chance you could brick your phone if the bootloader isn't unlocked because of Android Verified Boot (AVB).

Theoretically you should be able to boot these Android 14 GSIs on Pixels running Android 13 QPR2 WITHOUT unlocking the bootloader since Google installed the GSI keys in the ramdisk, which would let you boot a developer GSI with AVB enabled. This applies to Tensor-based Pixels, coral (Pixel 4 XL), sunfish (Pixel 4a), redbull (Pixel 4a with 5G and Pixel 5).

I don't know if they reverted this change in the QPR3 Beta, so YMMV. Also, the developer_gsi_keys makefile only lists the Q, R, and S GSI AVB pubkeys, not T or U. It's possible they're using the same key now to sign the T and U GSIs, but I haven't tested.

If you want to test booting the Android 14 GSI on your Pixel running Android 13 QPR2+ (again, I HAVEN'T TESTED IF THIS WILL BRICK YOUR PHONE OR WORK), you have to do so manually (or use DSU Sideloader), because Google hasn't updated gsi-src.json to point to the U GSIs yet.

EDIT:

It seems Google literally just updated the gsi-src json to point to the Android 14 GSIs, so they should now appear as an option for you to install in the DSU Loader menu!

(I swear the json didn't have this when I drafted this post, lol!)

According to one user, they were able to boot up the Android 14 Beta 1 GSI on their Pixel 7 which had a locked bootloader and was running the April 2023 Android 13 QPR2 stable release.

The DirtyPipe vulnerability (CVE-2022-0847) is apparently under active exploitation according to Google (H/T @flawedworlddev).

This vulnerability was addressed in the May 2022 bulletin, though, so if your device reports a security patch level of 2022-05-05 or newer it should already be protected against it.