This isn’t the first time we’re talking about the next Android version that Google making the jump from Android 4.2.x Jelly Bean to version 5.0, dubbed Android Key Lime Pie. The search giant jsut released Android 4.3 Jelly Bean to a number of stock Android smartphones and tablet and the blogsphere has focused its attention towards this rather incremental roll out. Once agin the Key Lime Pie patrol has resumed, and over on Google’s Chromium bug tracker – a series of tests have been uncovred, spotted a number of Android devices running different iterations of the OS. A bug reports an unknown, future build has manifested.
The company in the past has already teased Android 5.0, named Key Lime Pie and today the new software may finally been cinfirmed. The bug report entry lists issues with a notification within the firmware, and a bunch of Nexus 7 and Nexus 4 devices have been in terting the build number KRS36B. Starting with the letter K, it could be the Key Lime Pie 5.0 is in fact out there. Naturally, this could, obviously, be little more than a typo.
The reason behind the letter ‘K’ could be Key Lime Pie. Since all Jelly Bean builds begin with the letter J, a typo would seem likely both reside next to each other on your Standard QWERTY keyboard. For example: The Samsung Note II is running JZ054K, suggesting that the company is rolling out a software update to the phablet in the naer future. And thus, seeing the Nexus 7 and Nexus 4 running KRS368 and KRS365, respectively, that could imply that the devices are running an early version of Android Key Lime Pie 5.0.
However, with talk of Key Lime Pie hitting the shelves before the end of this year and Android 4.3 presumed to be the very last version of Jelly Bean and certainly Android 4.x, the changes are that this is a legitimate sighting.
Currently, we have known very little of Key Lime Pie’s exclusive features and implementations, which will change a lot until we get closer to the official release date. Just in after the release of Android 4.3 JB, and was discovered – said to be supported for profiles, and while the Bluetooth LE implementation was aurgeda long time beforehand, which wasn’t exactly the most exciting of revolutions.
Stay tuned to Grabi, so that we can update more if any suggestions these bug reports about the Key Lime Pie which are probably in motion. What do you think about this report on Key Lime Pie currently undergoing testing over Mountain View? Share your thoughts below if it’s just a case of a typo being blown out of proportion? (Via Redmondpie)