![\"We](\"https:\/\/www.newsbeep.com\/uk\/wp-content\/uploads\/2025\/08\/1754760428_216_gsmarena_002.jpg\")
<\/p>\nWe won\u2019t keep you in suspense: Android 17 has the internal codename \u201cCinnamon Bun\u201d. The information comes from a trusted source within Google and was originally reported by Android Authority. Here\u2019s a convenient table breaking down all the previous dessert codenames for you to check out.<\/p>\n
\n
\n Version number
\n Codename
\n Year of release
\n
\n
\n 1.0
\n No codename
\n 2008
\n
\n
\n 1.1
\n Petit Four (internal)
\n 2009
\n
\n
\n 1.5
\n Cupcake
\n 2009
\n
\n
\n 1.6
\n Donut
\n 2009
\n
\n
\n 2.0, 2.1
\n \u00c9clair
\n 2009
\n
\n
\n 2.2
\n Froyo
\n 2010
\n
\n
\n 2.3
\n Gingerbread
\n 2010
\n
\n
\n 3
\n Honeycomb
\n 2011
\n
\n
\n 4
\n Ice Cream Sandwich
\n 2011
\n
\n
\n 4.1, 4.2, 4.3
\n Jelly Bean
\n 2012
\n
\n
\n 4.4
\n KitKat
\n 2013
\n
\n
\n 5.0, 5.1
\n Lollipop
\n 2014
\n
\n
\n 6
\n Marshmallow
\n 2015
\n
\n
\n 7.0, 7.1
\n Nougat
\n 2016
\n
\n
\n 8.0, 8.1
\n Oreo
\n 2017
\n
\n
\n 9
\n Pie
\n 2018
\n
\n
\n 10
\n Quince Tart (internal)
\n 2019
\n
\n
\n 11
\n Red Velvet Cake (internal)
\n 2020
\n
\n
\n 12, 12L
\n Snow Cone (internal)
\n 2021
\n
\n
\n 13
\n Tiramisu (internal)
\n 2022
\n
\n
\n 14
\n Upside Down Cake (internal)
\n 2023
\n
\n
\n 15
\n Vanilla Ice Cream (internal)
\n 2024
\n
\n
\n 16
\n Baklava (internal)
\n 2025
\n
<\/p>\n
But, we see you scratching your heads through the screen, wondering how and why Cinnamon Bun. Why not something with \u201cW\u201d to follow Android 16 \u201cBaklava\u201d? Wait, Android 16 \u201cBaklava\u201d? It actually makes perfect sense. You can head on over to the source link for a more in-depth explanation, but here\u2019s the gist of it. Google relatively recently switched Android development from the old branch-based model to a new \u201cTrunk Stable\u201d model. Instead of merging new release branches back into the stable one like before, the new model has a constantly ideally stable single main code branch with all new features, fixes and APIs developed behind \u201cfeature flags\u201d to keep them disabled until they are ready.<\/p>\n
You still with us? Good. The important bit here is that Google completed the migration to the new trunk-based dev model with Android 14 QPR2, and to mark the change, the build ID scheme was reset, so Android 14 QPR2 became build ID AP1A and QPR3 got build ID AP2A. The first time Google released a trunk stable build was in 2024, hence the use of the letter \u201cA\u201d to preface the build ID. However, presumably by that time Android 14 already had its \u201cUpside Down Cake\u201d name and Android 15 its \u201cVanilla Ice Cream\u201d moniker, so it was too late to \u201crestart\u201d the names and call Android 15 something with \u201cA\u201d. Once the year turned over to 2025, however, the build IDs started coming out with the letter \u201cB\u201d and Google decided to call Android 16: \u201cBaklava\u201d. The next letter for build IDs is \u201cC\u201d and hence a dessert with \u201cC\u201d \u2013 enter \u201cCinnamon Bun\u201d, presumably since \u201cCupcake\u201d was already taken.<\/p>\n
<\/p>\n
Of course, ultimately, the dessert name doesn\u2019t really matter that much, especially since Google decided to move away from it as a public branding. Nowadays, it is a remnant on the development side of things. Still, it is interesting to see what sweets the Google team chooses now that it is essentially the second time around for each letter. As for Android 17, we expect it to land around June 2026.<\/p>\n