Android 5.0 Key Lime Pie For Nexus 4 And 7 Spotted In Logs
Earlier on this year, there was much talk of Google making the jump from Android 4.2.x Jelly Bean to version 5.0, named Android Key Lime Pie. But soon after, it was revealed that there would be a stop-gap in the form of Android 4.3 Jelly Bean and thus, the blogosphere has focused its attentions towards this rather incremental release. With the search giant now having begun rolling 4.3 out to a number of stock Android smartphones and tablets, the Key Lime Pie patrol has resumed once again, and over on Google’s Chromium bug tracker, what looks to be a bug report of an unknown, future build has manifested.
The bug report entry speaks of issues with a notification within the software, and a bunch of Nexus 7 and Nexus 4 devices have been listed as testing the build number KRS36B. Naturally, beginning with a K, it could just be that Key Lime Pie 5.0 is in fact out there, but this could, of course, be little more than a typo.
Since all Jelly Bean builds start with the letter J, a typo would seem likely since both reside next to each other on your standard QWERTY keyboard. However, with talk of Key Lime Pie hitting the scene before the end of this year and Android 4.3 presumed to be the very last version of Jelly Bean and indeed Android 4.x, the chances are that this is a legitimate sighting.
At this point in time, we know very little of Key Lime Pie’s specific features and implementations, something that is unlikely to change much until we get closer to the release date. After all, it wasn’t until a couple of weeks prior to the release of Android 4.3 Jelly Bean that we discovered, for certain, that there would be support for profiles, and while the Bluetooth LE implementation was presumed a long time beforehand, it wasn’t exactly the most exciting of revelations.
Still, these bug reports suggest the wheels for Key Lime Pie are probably in motion, so we’ll be sure to keep you updated if we hear any more.
In the meantime, what do we think – is Key Lime Pie currently undergoing testing over in Mountain View, or is this just a case of a typo being blown out of proportion? Share your thoughts below!