By It looks like Google is planning a surprise with its upcoming Android 16 update. According to a new report from Android Authority, the operating system’s internal codename is “Baklava” (Android 16), a surprising departure from the company’s longstanding tradition of naming Android versions after desserts.
For years, Google has stuck to its alphabetical dessert naming scheme for its Android operating system. From Cupcake (Android 1.5) to Upside Down Cake (Android 14) and Vanilla Ice Cream (Android 15), these codenames have given us a fun way to track the evolution of the Android operating system.
However, according to a new report, Google seems to be planning to switch to using the name “Baklava” (Android 16), a very popular Turkish pastry. So what made Google change the way it names its Android operating system?
We don’t know exactly why yet. But note that Google isn’t completely abandoning desserts, as Baklava (Android 16) still fits the theme. It’s just that people are expecting something that starts with a “W,” like a Waffle Sundae or a Whoopie Pie.
Android 16 will be internally known as Baklava (Android 16)
The name of the next Android version is taken from code references in the Android Open Source Project (AOSP) code.
In AOSP, min_sdk_version is now named “Baklava” (Android 16), which is similar to the “VanillaIceCream” codename for Android 15. Google changed the name from VanillaIceCream to Android 15 when the OS was first released to stable, so it’s likely that they’ll do the same for Android 16.
Interestingly, a Google engineer also accidentally confirmed the Android 16 codename by adding a check to see if the build’s platform SDK codename matches Baklava (Android 16).
Why did Google choose Baklava for Android 16?
This change could be due to Google’s new Android OS development process, introduced with Android 14. For those who don’t know, Google has started using the “Trunk Stable” project to develop new versions of Android.
The first release under this project was Android 14 QPR2 in March, which introduced a new build ID naming system. Instead of starting with a “U” for Upside Down Cake, build IDs start with an “A.” For example, the build ID for the Pixel Tablet’s March update was AP1A.240305.019.A1. The June update, based on Android 14 QPR3, had a build ID of AP2A.240605.024.
The October update, based on Android 15, is likely to follow with a build ID of AP3A.241005.0XX. Similarly, the Android 15 QPR1 update expected in December will have a build ID of AP4A.241205.0XX.
Next year’s Android releases will use build IDs that start with “B,” meaning Android 15’s QPR2 build ID will likely look like BP1A, etc. This explains why Google chose “Baklava” as the codename for Android 16 instead of one that starts with “W.”
FAQs about Android 16 (Baklava)
- What is the codename for Android 16?
The codename for Android 16 is “Baklava,” which is a popular Turkish pastry. - Why did Google choose “Baklava” for Android 16?
While the exact reason is unclear, it seems that Google is still sticking with dessert names for its Android operating system. Baklava (Android 16) fits this theme, even though many expected a name starting with “W.” - Has Google stopped using alphabetical dessert names for Android versions?
No, Google hasn’t completely abandoned dessert names. While Android 16 is named Baklava, which doesn’t follow the alphabetical order, the naming still follows the dessert theme. - Where did the name “Baklava” (Android 16) come from?
The name “Baklava” (Android 16) was found in the Android Open Source Project (AOSP) code, where the min_sdk_version was renamed to Baklava, indicating its internal codename. - When will Android 16 be officially released?
There is no confirmed release date yet, but it’s likely that Android 16 will follow the same release cycle as previous versions, with early previews possibly in 2024. - Will Android 16 bring any major changes?
Details on specific features of Android 16 (Baklava) haven’t been released yet. However, given Google’s history, it’s expected that the new version will include various updates to performance, security, and user experience. - Does the codename “Baklava” (Android 16) appear in any official documentation?
Yes, the codename “Baklava” (Android 16) was confirmed in the AOSP code, where it appeared as part of a min_sdk_version and was further confirmed by a Google engineer. - What was the codename for Android 15?
The codename for Android 15 was “Vanilla Ice Cream.” - Will Android 16 follow the new build ID system introduced with Android 14?
Yes, the build ID system starting with “A,” introduced in Android 14, is expected to continue with Android 16, meaning future updates might start with “B” for Android 16 releases. - What is the “Trunk Stable” project, and how does it relate to Android 16?
The “Trunk Stable” project is Google’s new Android OS development process, first used in Android 14. This project influences how new Android versions are built and named, and it’s likely contributing to the codename and development of Android 16 (Baklava).
