Use Android SDK Tools CLI To Install And Set Up Emulator

In recent release of Android SDK tools Google decided to remove the previously provided GUI utilities for managing SDK packages and AVDs. If you don’t want to install the full Android Studio, everything now must be done via the command line interface.

In fact, if you try to use previously valid commands, such as

./android sdk

You’ll get output like this

*************************************************************************
The "android" command is deprecated.
For manual SDK, AVD, and project management, please use Android Studio.
For command-line tools, use tools/bin/sdkmanager and tools/bin/avdmanager
*************************************************************************

Invalid or unsupported command "sdk"
Supported commands are:
android list target
android list avd
android list device
android create avd
android move avd
android delete avd
android list sdk
android update sdk

So, if you still don’t want to install Android Studio, how do you install the SDK packages, tools, images, etc. for the emulator? Below are few basic commands to get you started. They have been tested on Linux.

Update installed items in SDK manager:

bin/sdkmanager --update

Install NDK bundle:

bin/sdkmanager --install ndk-bundle

Install SDK tools for the latest API level:

bin/sdkmanager --install "platform-tools" "platforms;android-26"

Install the latest system image:

bin/sdkmanager --install "system-images;android-26;google_apis;x86_64"

Create a virtual device called “pixel” using the installed system image:

bin/avdmanager create avd -n pixel -d 19 -k "system-images;android-26;google_apis;x86_64"

Launch emulator to test:

ANDROID_EMULATOR_USE_SYSTEM_LIBS=1 ./emulator -avd pixel

Amazon Finally Releases Android Kindle

It wasn’t a tough call or anything but back in March I did guess that Amazon was planning a Kindle running on Android. Why else would they start their own app store? Now that their strategy is actually taking shape it unsurprisingly presents Amazon-skinned Kindle Fire Android device geared towards its users consuming more Amazon content, services and products. For this purpose, the tablet is very competitively priced – at the time of writing a full $50 less than Nook Color ($199 and $249 respectively).

One can find many reviews of Kindle Fire online. It has also been a frequent comparison subject against Nook Color. Because of the price difference, it compares favorably. However, if I had to pick between the two I would likely go with the Nook Color because of better specs (double RAM, SD card slot, etc.), better support for standards, and just my general discontent for Amazon and its business practices.

Nokia Going WP7 Not a Surprise

Nokia “picking” Windows Phone for their future is not a surprise. It wasn’t to me, anyway. You don’t pick a former Microsoft big head, Stephen Elop, to lead you anywhere else besides Microsoft. In other words, you don’t buy a screwdriver and expect it to hammer nails.

On a side note, that billion dollar cash deal must spell nice bonuses for some executives. At this point, I’m not entirely sure how serious Nokia executives are about this deal anyway. Nokia Windows phone will not be out for at least another year, which is an eternity in mobile world these days; and, in the meantime, they have to hold on to Symbian, which they will soon phase out; and, start over with Windows. It will be like a giant corporation in a startup company mode. One word – disaster.

Amazon Planning Android Kindle?

Amazon it planning to launch an Android tablet device. There is no other way around it. Why? Because there is no reason for Amazon to launch their Android app store otherwise. There is no incentive for them to do favors to Google, or to any of Android tablet manufacturers, which are also Amazon’s competitors, by the way.

The only real reason to establish the Android app store is to create an “ecosystem” (yes, I did use that buzzword) where their next Kindle would naturally fall in place.