That is Android 16’s codename — and it is not what you are anticipating

Though Google hasn’t publicly referred to Android variations by dessert names for a few years now, that doesn’t imply it’s stopped utilizing them totally. In reality, the codename it makes use of for every new Android model continues to be primarily based on desserts, resembling Vanilla Ice Cream for Android 15. Ever since Google launched Android 1.5 with the codename Cupcake again in 2009, the corporate began a sample of basing the following model’s codename on a dessert that begins with the next letter within the English alphabet. For instance, Android 1.6 was codenamed Donut. Nonetheless, that sample would possibly finish with subsequent 12 months’s Android 16 replace, which could not have a codename that begins with the letter “W.”

Developer teamb58 despatched us a tip over the weekend about some fascinating code adjustments he noticed in AOSP. The primary change provides code permitting any APEX module that launches with subsequent 12 months’s Android launch to be compressed. What’s fascinating concerning the code is the way it refers to subsequent 12 months’s Android launch. Significantly, the min_sdk_version subject is ready to Baklava. In distinction, the min_sdk_version subject for this 12 months’s launch is ready to VanillaIceCream.

In one other code change, a Google engineer brings up how a further test needs to be added to see if the construct’s platform SDK codename matches Baklava. The explanation they gave is {that a} earlier model of the patch checked if both the SDK model is bigger than or equal to 35 — which is the SDK model comparable to Android 15 — or the platform SDK codename matches VanillaIceCream.

Throughout growth on a brand new Android model, Google units the platform SDK model to the codename till the SDK is finalized, which is why in Android 15 Beta 3 — Android 15’s first Platform Stability milestone — the Android model identify was modified to fifteen from VanillaIceCream. Since growth on Android 16 is underway, the identical is true for that launch, i.e., early builds will present the platform SDK codename (Baklava) as a substitute of the platform SDK model (36).

So, that’s two items of proof that recommend the Android 16 codename is Baklava. Based on a supply we spoke with, Baklava has certainly been set as Android 16’s dessert identify. In case you had been anticipating the Android 16 codename to reference a dessert that begins with the letter “W,” you’re not alone. Just about everybody, myself included, thought this is able to be the case given prior historical past.

In spite of everything, for those who have a look at the historical past of Android variations and their codenames, there’s no cause to assume that the sample Google began again in 2009 would finish subsequent 12 months, particularly since there are nonetheless a couple of extra letters left within the English alphabet to base names on.

Nonetheless, for those who’ve been following Android platform growth information these days, you could have heard of one thing known as the trunk secure mission. With out getting too technical, the best way that Google develops Android has considerably modified. The primary Android model to be launched as a part of the trunk secure mission was Android 14 QPR2 again in March, which is why that launch used a really completely different construct ID naming scheme. As an alternative of getting construct IDs that began with the letter “U” for Upside Down Cake, Android 14 QPR2 had construct IDs that began with the letter “A.”

For instance, the construct ID for the Pixel Pill’s March replace was AP1A.240305.019.A1. The construct ID for the gadget’s June replace primarily based on Android 14 QPR3 was AP2A.240605.024. And the construct ID for the gadget’s upcoming October replace primarily based on Android 15 can be one thing like AP3A.241005.0XX. The Android 15 QPR1 replace for the gadget can be one thing like AP4A.241205.0XX, assuming it certainly releases in December.

The construct IDs for subsequent 12 months’s Android releases, although, will all begin with the letter B, so Android 15 QPR2 construct IDs can be one thing like BP1A and so forth. That’s why the dessert identify Google goes with for Android 16 is Baklava and never one thing that begins with the letter “W.”

In case you’re questioning why Android 15’s codename is Vanilla Ice Cream and never one thing that begins with the letter “A,” I can’t say for positive. It’s doubtless as a result of Google had already chosen Vanilla Ice Cream as the inner codename for Android 15 earlier than the primary trunk secure launch, so it didn’t need to return and alter each point out of the codename, particularly since that might break some construct flows.

Regardless, I’m positive the concept that Baklava is Android 16’s codename will shock lots of you, however for those who dig deeper into why it was chosen, you’ll be taught some fascinating details about how Android platform growth has dramatically modified up to now few months.