Monday, December 17, 2018

Android development

There are a few models for Android development... traditional PC or Mac development computers with emulated targets, USB connected targets and WiFi connected targets.  Recently Google selectively added linux containers to it's ChromeOS lineup and made it possible to run Android Studio.

Unfortunately there is little consistent parity between the ChromeOS and traditional development environments. That means in order to get some development going on my ChromeOS Pixel Slate I'm relegated to put the target in developer mode and connect it with WiFi or BETA USB.  Crap!

Since I do not have a target to test and I do not want to convert my personal phone as it creates other security challenges I'll have to purchase a dev phone... but then my next question is how does the WiFi bonding work when in a hotel or a place where WiFi is not that available?

No comments:

Post a Comment

Fire OS and Android

The relationship between Amazon's FireOS and Google's Android OS is probably very complicated. And while there is probably some very...