One of the trademark highlights of Chrome OS gadgets is their capacity to run Android applications, presently took care of by a variant of Android Pie. Since the Android 11 Developer Preview period has started, Google has openly started chip away at carrying Android 11 to Chrome OS.
A month ago, Google gave us our first gander at the following cycle of Android longer than a month sooner than expected with Android 11 Developer Preview 1. Notwithstanding, even before its discharge, another venture started preparing inside Chrome OS source code with the name “eve-bend r.”
Separating that, they have “eve,” which is the inside codename for the Google Pixelbook, “arc” which means “Android Runtime for Chrome,” lastly, “r,” which is the following letter after a year ago’s “Android Q,” which in the end became “Android 10.” From this by itself, they get a really clear picture that Google is taking a shot at Android 11 for Chrome OS, beginning with the Pixelbook.
Investigating other code changes from a similar designer, they locate a couple of references to “RVC” that is by all accounts Google’s codename for Android 11, much the same as “QT” is Android 10’s codename.
Past that, they likewise find that the Pixelbook won’t be distant from everyone else in getting Android 11, as two more Chrome OS codenames are additionally being given “circular segment r” Android 11 forms. The first, “Kukui,” is the base board for Chrome OS gadgets dependent on the Mediatek MT8183 processor found in any semblance of the Lenovo IdeaPad Duet tablet.
In the mean time, the second, “Hatch,” is the reason for Chromebooks based on the tenth era of Intel Core processors. That implies the profoundly foreseen Samsung Galaxy Chromebook might have the option to exploit Android 11 in due time.
The main other fascinating goody they’ve revealed so far is that the old strategy for running Android inside Chrome OS, which includes a “container” that sudden spikes in demand for the Chrome OS inner Linux part, is finishing with Android Pie.
For Android 11 ahead, Chrome OS will switch over to utilize the more current “ARCVM” strategy that runs Android in a different virtual machine with its own part to all the more likely ensure the center Chrome OS bit. The change will make running Android on Chrome OS predictable with the way that Linux applications can run on Chromebooks today, and ought to likewise make sideloading applications more secure.
Tragically, in light of the fact that testing is increase, they can’t expect that Android 11 will really show up on our Chromebooks. Google made comparative moves a year ago to test Android 10 on Chrome OS, however this work never worked out into the real world. Actually, Chrome OS’s Android 10 help “has been abandoned.”
Alternately however, Chrome OS recently skipped Android Oreo, going straightforwardly from Nougat to Pie. On the off chance that that timetable were to proceed, it could bode well for Chrome OS to skip Android 10 and update legitimately to Android 11.
Whatever the case might be, considering Android 11 is still in Developer Preview and this work on the Chrome OS side has just barely started, we may not see this update for many months, if not into one year from now.
What highlights from Android 10 and Android 11 would people need to exploit on Chrome OS? Tell us in the remarks!
Disclaimer: The views, suggestions, and opinions expressed here are the sole responsibility of the experts. No Digi Observer journalist was involved in the writing and production of this article.