[Google Pixel 7 Pro] Jon8RFC:
Would some of you smarter people please help figure out what's going on? I/you can then file a bug report which won't result in it being closed due to their misunderstanding.

The primary issue is that music stops playback when a USB-C adapter is used, once the screen locks. I've used three different ones, which I can't identify the differences between with my skillset of linux, but they all produce the issues and one does treat the microphone differently.

It's not related to screen off timeout, only lock screen timeout. If I lock the screen, music stops. If I set the lock timeout 30 seconds after the screen off timeout, music stops 30 seconds after the screen is off.

The secondary and deeper issue is that if fingerprint or face unlock are enabled, it causes a 7+ second delay in unlocking, or it "breaks" screen unlocking entirely (until the adapter is removed), or can even result in a hard crash or "soft" (yeah?) crash of the OS. However, this is only if a certain type of audio session is running with Android (which I don't understand anything about), until the headphone adapter is removed. If left in, it can cause the phone not to unlock or even crash and reboot.

The broken lock screen does not occur if using an app such as Simple Music Player, although the music does still stop when the screen locks. It doesn't do the same type of audio session with the operating system that Amazon Music, Audible, or Podcast Addict do. I know this only because Wavelet doesn't detect the audio session, so it's very likely not an app issue but an OS issue with how the audio session type causes this problem.

The broken or delayed lock screen does not occur if I turn off face and fingerprint unlocking. It works normally with entering a PIN and there's no delay.

The fingerprint scanner is broken, no matter what, if face unlock is also enabled.

If I delete the stored face scan, the fingerprint scanner works but with the big delay.

After playing music and locking the screen, if I turn on the screen and wait about 7 seconds, it will unlock the screen using my face. If I try to use the fingerprint reader, it'll often, but not always, break unlocking entirely until it crashes or I remove the adapter.

If I successfully unlock it, the music is shown to be "still playing", although it's silent. If I lock it again, it's definitely broken and cannot be unlocked via fingerprint or face, and will not fallback to PIN.

If I let it sit a while (not more than 90 seconds) after that, it becomes unresponsive and the screen will not turn on again. It doesn't hard crash all the way to the bootloader, but when I unplug the adapter, the "G" loading logo is shown and then the lock screen asks me for my PIN.

I can't say how I managed to get it to hard crash to the bootloader twice, but I think those times I was quickly using the fingerprint scanner numerous times, turning the screen on and off, and I don't THINK I had a successful unlock first, during the hard crashes to bootloader.

EDIT:

Enabling "allow wired headset requests with device locked" in the Google App doesn't resolve the issue. The headset doesn't work then, either, and gets disconnected. I guess I could file a bug report on that alone and maybe the fix would trickle down to everything else...but I'd rather not.

Sorry for the wall of text, but it's not a simple scenario since I don't know what's actually going on and what's important. Hopefully one of you can help figure out the stuck process and reduce it down to two sentences for a bug report. I don't recall having this issue with my Pixel 6 Pro, but the times I used a USB-C headphone adapter with it was probably only in the first few months it was released, if at all, so a specific Android update may be to blame, but I don't know which/when.