@GrapheneOS Is there a timeline for when desktop mode newly announced by Google for a Pixel Drop is coming to GrapheneOS? I've been very excited for desktop mode reading GA. I'm not knowledgeable enough about GrapheneOS release cycles to tell if I should be able to figure out the timeline on my own.
@GrantJoseph Android's 1st and 3rd quarterly releases are now exclusive to the Pixel stock OS. They're no longer available for use by other OEMs. For Android 16 and later, they stopped pushing Pixel exclusive code to AOSP so the monthly and 1st/3rd quarterly releases are no longer pushed to it. There are 2 major releases per year for other OEMs so that's what gets pushed to AOSP along with the security backports. It's a regression but that's the way things are now and will be from now on.
@GrapheneOS If I'm following, that means it will reach AOSP at the time of the 2nd quartly release?

@GrantJoseph The next release is Android 17 which will be received by AOSP.

The standard cycle is a yearly release in June, 1st quarterly release in September, 2nd quarterly release in December and then the 3rd quarterly release in March.

The yearly release and 2nd quarterly release are the ones intended for use by other OEMs and pushed to AOSP. Security backports are provided for the yearly release and 2nd quarterly release which is what the security preview releases we make are based on.

@GrapheneOS Ah, okay. I forgot this was already the Q3 release. I appreciate the explanation!
@GrapheneOS
Is that even legal, considering they use other people's open source in it?
@GrantJoseph
@mattesilver @GrantJoseph Yes, they provide the GPLv2 code for the Pixel stock OS releases upon request which is useful but mainly covers the kernel and all of the kernel drivers. QPR1 and QPR3 are stock Pixel OS exclusive so that's not available via the OEM OS on non-Pixel devices anyway. Those features are only delayed when compared to the stock Pixel OS. Their OEM partners should be quite upset about many things they've been doing including this. Android really needs to be split from Google.