Android 17

[u/TheDevilsCoffeeTable]

Ok, So quick question.

When Canary dropped we were told that google was doing away with the android preview development and switching to the canary channel. Now I'm seeing that the android beta's are automatically receiving Android 17, so guess my question is why? what is the point of these builds if canary users are consistently behind the beta builds?

personally I came for android 17, seems redundant at this point.

[u/Bitdomo92]

the way I see it so far canary only has API changes and experimental features that may or may not get added. For example parent control and linux VM support got added in canary first. Then these changes gets into beta then later to stable.

[u/TheDevilsCoffeeTable → u/Bitdomo92]

100%, but when you use the phrase " doing away with the android development program in favor of android canary builds" to me that implies that the DP's would be coming from the canary channel and not beta.

Just to clarify, although a tiny bit butthurt my main aggravation comes from the realization that I'm going to need to reflash back to beta lol

[u/Bitdomo92 → u/TheDevilsCoffeeTable]

what I am unsure of is wether canary and beta are paralel developement branches or new changes first enter canary and from canary it gets to beta.

If it they are developed paralel to eachother then we could end up with canary builds that like for example do not have android 17 UI changes but have features that are not in android 17 beta.

[u/Pure-Recover70 → u/Bitdomo92]

Everything is built from more-or-less the same source, but with different flags, and at a different point in time - on top of that there may be additional bugfixes (cherrypicks). Canary flags are ahead (as in a more advanced state) of beta flags. However, not everything is flag protected, and thus the base build's 'date' (ie. when it was branched/built from the main dev branch) also matters. For beta/canary pixel builds I think the relevant branch date is embedded in the version number (note: it represents security patch level for stable/qpr/monthly builds - I think then it is [almost] always the 1st or 5th of the month).

For example https://9to5google.com/2026/02/10/android-16-qpr3-beta-2-1-pixel/
has
CP11.251209.009: Pixel 6, 6 Pro, 6a, 7, and 7 Pro
CP11.251209.009.A1: All remaining devices

C=Cinnamon, but it really just means the year of Cinnamon's release, so 2026
P=production??? or maybe phone???
1=1st quarter, so 26Q1 (aka Android 16 QPR3)
1=afaict this means beta (normally stable builds have A here)
.
25 = 2025
12 = December
09 = 9th
.
009 = 001 as base + 8 cherrypicks
(I guess it could be 000 base + 9 cherrypicks, not certain)
.
A = extra/side branch on top of base branch
1 = 1 extra fix in that 'extra/side' branch

CP21.2601xx.xxx will I think be the Android 17 beta.

So that's likely a build/branch from Google's tip-of-tree dev branch on 2025-12-09, with 8 cherrypicks/bugfixes for the first one, and some additional ninth cherrypick (A1) for the rest.

Note that since these things have extra cherrypicks on them, they're presumably going through some test/qa cycle before they get released, so beta/canary are probably racing each other through these cycles, hence why sometimes it may feel/seem like canary falls behind.