Android is back on the alphabetical codenaming train, but not exactly where it left off.
For those unaware, we were perplexed when Android 16’s codename first came to light in September last year. The tech giant had been following an alphabetical naming pattern up until Android 15, but that changed with Android 16. For example, Android 1.5 was Cupcake, 1.6 was Donut, 2.0 was Eclair, 2.2 was Froyo, and so on until Android 15’s Vanilla Ice Cream. Considering the naming pattern, we had initially expected Android 16’s codename to start with the letter W, but as we know now, that didn’t happen.
Android 16 is codenamed ‘Baklava,’ which essentially resets the alphabetical naming pattern, all while retaining the desert theme. With that history out of the way, it now looks like Android might be hopping back on the alphabetical naming train. No, we’re not going back to W. Instead, we’re going from ‘Baklava’ to ‘Cinnamon Bun.’
For what it’s worth, the codename was leaked back in August too, but at the time, the name was just part of early-whisper rumors. Now, as highlighted by credible Android analyst Mishaal Rahman in an Android Authority report, the name has been found written into the core code of the latest Android Canary build, essentially turning what was once an early rumor into verifiable information.
According to the report, Google’s November Android Canary release (2511) very specifically lists CINNAMON_BUN as a valid Android version, in addition to previous builds like TIRAMISU, UPSIDE_DOWN_CAKE, and VANILLA_ICE_CREAM.
Currently, CINNAMON_BUN has been given the version code “10000,” which will eventually be changed to 37 to highlight the OS’ API level. Android 16/Baklava, for reference, has version code 36. The change will kick in once Android 17’s features and APIs get locked in, and the OS hits platform stability in 2026.
Are you excited about Android 17? Although we don’t know much about the upcoming OS just yet, we know that it could let you see more from apps on your always-on display. Read more about the potential feature here.
