Mountain View-based Internet giant Google is reportedly getting ready for the launch of the next flavor of the Android operating system, and might unveil it as Android 4.3 Jelly Bean, the latest reports on the matter suggest.
Previously, the new OS flavor was said to arrive on devices as Key Lime Pie, but it seems that Google might actually release it only as an incremental update when compared to the currently available Android 4.2.2 Jelly Bean. No official confirmation on the matter has emerged so far, but the guys over at Android Police claim to have found evidence on the platform’s existence over on Google’s servers. An Android 4.3 JWR23B build has started to emerge in server logs, clearly showing that it is still Jelly Bean, though no specific info on what it might include has been provided as of now. The news site also notes that the build emerged from two different IP addresses, both connected to Google, which suggests that the company already has employees working with the new OS flavor.
The JWR23B build was also spotted mentioned in the official Chromium bug tracker, which can be seen as further confirmation on its existence. For the time being, the OS has been spotted online on Nexus 4 and Nexus 7 devices, though it will certainly be delivered to other smartphones and tablet PCs out there as well, should it prove real. Rumor has it that the new Android 4.3 Jelly Bean platform release might be officially introduced as soon as next month during the Google I/O conference, given that it has already assigned a version number to it. Given that some of the recent reports on Google’s plans for the Android OS suggested that the major platform release called Key Lime Pie might have been delayed, the possible launch of Android 4.3 next month sounds increasingly plausible.
For the time being, however, no official confirmation on the platform release has been provided, and we should wait for Google to make a formal announcement on the matter to learn more on what it will have to offer.
Android 4.3 Jelly Bean spotted in logs, could arrive at Google I/O Image credits to Google |
0 comments:
Post a Comment