Android on Chrome OS: Updated Information
Courtesy of a Google employee who reached out to me, here are some updates on the Android-on-Chrome-OS development process.
-
You no longer need to run a
bashscript on your developer machine to enableadbaccess, as you needed earlier. This simplifies setup a lot and makes it much easier for Windows developers. -
If, however, you followed those earlier instructions, a recent Chrome OS update might have broken your
adbaccess. If so, try turning off, then on, the Developer Options, via the switch in the action bar of the Developer Options screen. Then, try reconnecting viaadb connect. You should get the standard Android debugging authorization dialog on the Chrome OS machine. After accepting that, you should be good to go to useadb. -
AlarmManagerandJobScheduler, which previously did not work, are now working. The exception is if the Chrome OS device is asleep (e.g., lid closed) — in that case, alarms and jobs will not fire. This includes any_WAKEUPalarms. -
Chrome OS should remember whether you have enabled Android apps on the device even after a reboot. This used to not work, forcing you to re-enable Android app access after every reboot.
-
You are supposed to be able to file issues related to Android-on-Chrome-OS via this link, which redirects to the Chromium issue tracker, using a template that sets up some appropriate labels. As always, the more information that you can provide to replicate any bugs, the better off you will be.
