Daniel Micay

Hasn't been merged yet.

@warren-bank Non-Pixel phones rarely update to the latest AOSP releases. There are monthly and quarterly releases of AOSP, not only yearly. They don't increment the main user-facing version number but...

That's not a correct tag for the OS. Bear in mind that tags are made across the entire source tree for everything built from AOSP including platform-tools, the SDK API...

@warren-bank > update: Would the [android13-qpr2-s1-release](https://android.googlesource.com/platform/frameworks/base/+/refs/heads/android13-qpr2-s1-release) tag correspond to v13.2.1 that you mentioned? The android13-qpr2-release branch corresponds to QPR2 (Quarterly Platform Release 2), i.e. what is essentially 13.2.x. The latest...

@warren-bank android13-release was the initial Android 13 stable branch. It hasn't been maintained since Android 13 QPR1 was released in December, which is android13-qpr1-release. That hasn't been maintained since Android...

The reason you think there's Pixel specific behavior is just because other devices aren't shipping current Android 13 but rather a release from months ago with a subset of backported...

It depends on the device and how far behind they are at a given moment. After all, it takes them half a year to migrate to new yearly releases. They...

You should be able to replicate the issue on up-to-date LineageOS 20 as long as the release for the device you test is up-to-date enough.

@warren-bank > I happened to notice that GrapheneOS has (quietly) acknowledged > that this was a bug in their code, and has since fixed it. No, that's not correct. >...