This is a controller written by Go to create, delete a Android emulator based Android SDK on Mac OS, Linux Desktop, or Linux Server.
AWS EC2: free tier (t2.micro)
Linux Ubuntu: Linux ip-172-31-16-251 4.4.0-53-generic #74-Ubuntu SMP Fri Dec 2 15:59:10 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
This doc instructs how to install the controller on a Ubuntu Server. The big chanllenge in this installation is the Android SDK part since it is usually installed in a machine with graphic device via GUI. But in this case, all the installation need to be done via command line becasue a server does not provide GUI interface.
Follow this post to install Android SDK on headleass Ubuntu server http://sblackwell.com/blog/2014/06/installing-the-android-sdk-on-a-headless-server/
The sdkmanager is a command line tool that allows you to view, install, update, and uninstall packages for the Android SDK. If you're using Android Studio, then you do not need to use this tool and you can instead manage your SDK packages from the IDE.
https://developer.android.com/studio/command-line/sdkmanager.html
$ sudo apt-update
/* check whether java is installed or not */
$ java -version
/* Install java sdk */
$ sudo apt-get install default-jdk
/* check java path*/
$ sudo update-alternatives --config java
There is only one alternative in link group java (providing /usr/bin/java): /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java
Nothing to configure
/* set JAVA_HOME */
$ sudo vi /etc/environment
JAVA_HOME="/usr/lib/jvm/java-8-openjdk-amd64"
/* install Android SDK tool */
$ mkdir /usr/local/android-sdk-linux
$ cd /usr/local/android-sdk-linux
$ wget https://dl.google.com/android/repository/tools_r25.2.3-linux.zip
/* install unzip */
$ sudo apt install unzip
/* unzip Android SDK tool to android-sdk-linux/ */
$ unzip tools_r25.2.3-linux.zip android-sdk-linux/
$ ls /usr/local/android-sdk-linux/
tools
/* set environment */
$ sudo vi /etc/profile
"/usr/local/games:/usr/local/android-sdk-linux/tools:/usr/local/android-sdk-linux/platform-tools"
/*
- install SDK packages via /tools/bin/sdkmanager
- The sdkmanager is a command line tool that allows you to view,
- install, update, and uninstall packages for the Android SDK.
- If you're using Android Studio, then you do not need to use
- this tool and you can instead manage your SDK packages from the IDE.
- link: https://developer.android.com/studio/command-line/sdkmanager.html#usage */
/* list all available SDK package */
$ cd /usr/local/android-sdk-linux/tools/bin
$ ./sdkmanager --list
/* install the platform tools */
$ ./sdkmanager "platform-tools"
/* install the Android 2.3.3(API 10)
- Why API 10?
- No special reason, just because we tested it from beginning */
$ ./sdkmanager "platforms;android-10"
Create AVD In this case, we create 10 AVD for 10 emulator.
The AVD is stored at this user's home directory, like '/home/ubuntu/.android/avd/android-api-10-5555.avd'. It's very important to notice that creating emulator will automatically find .avd file to the user's home directory. If the avd is created by different user, it will failed with the following error when creating emulator.
emulator: ERROR: unknown virtual device name: 'android-api-10-5558'
$ android -s create avd -n android-api-10-5556 -t android-10 --abi default/armeabi
Android 2.3.3 is a basic Android platform.
Do you wish to create a custom hardware profile [no]no
Created AVD 'android-api-10-5555' based on Android 2.3.3, ARM (armeabi) processor,
with the following hardware config:
hw.lcd.density=240
hw.ramSize=256
vm.heapSize=24
Delete AVD
$ android -s delete avd -n android-api-10-5555
Deleting file /home/ubuntu/.android/avd/android-api-10-5555.ini
Deleting folder /home/ubuntu/.android/avd/android-api-10-5555.avd
AVD 'android-api-10-5555' deleted.
List AVD
$ android -s list avd
Available Android Virtual Devices:
Name: android-api-10-5555
Path: /home/ubuntu/.android/avd/android-api-10-5555.avd
Target: Android 2.3.3 (API level 10)
Tag/ABI: default/armeabi
Skin: WVGA800
/*
- Add lib to PATH
- Why?
- some dynamically linked libraries were moved around with the new Android emulator.
- All you need to do is:
- add the folder with the libraries to the search path
- before you launch the emulator from command line. / / set environment */
$ sudo vi /etc/profile
export LD_LIBRARY_PATH="$ANDROID_SDK_HOME/tools/lib64:$ANDROID_SDK_HOME/tools/lib64/qt/lib:$LD_LIBRARY_PATH"
$ source /etc/profile
$ echo $LD_LIBRARY_PATH
/usr/local/android-sdk-linux/tools/lib64:/usr/local/android-sdk-linux/tools/lib64/qt/lib:
/*
- create emulator */
$ emulator64-arm -avd android-api-10-5554 -wipe-data -no-window -no-boot-anim -noskin -port 5554
emulator: WARNING: the -no-skin flag is obsolete. to have a non-skinned virtual device, create one through the AVD manager
emulator: WARNING: Classic qemu does not support SMP. The hw.cpu.ncore option from your config file is ignored.
emulator: warning: opening audio output failed
emulator: Requested console port 5556: Inferring adb port 5557.
emulator: Listening for console connections on port: 5556
emulator: Serial number of this emulator (for ADB): emulator-5556
/*
- connect emulator */
$ adb devices
In the EC2, AWS has already installed go, so nothing to do here.
$ go version
go version go1.6.2 linux/amd64
$ sudo git clone git://github.com/kanaka/noVNC
$ git clone https://github.com/tianhongbo/controller.git
- install.sh
- deviceinstall.sh
- repo.go
$ cd /home/ubuntu/controller/src/github.com/tianhongbo/node
get dependency packages
$ go get
build bin file
$ go install
check the bin file
$ ls -l ~/controller/bin
total 8640
-rwxrwxr-x 1 ubuntu ubuntu 8846224 Dec 14 19:15 node
$ sudo vi /etc/profile
- add emulator tools to PATH
- add dynamic lib path for Android SDK
- add GOPATH
Here is one sample
$ cat /etc/profile
# set environment for MTaaS
export PATH="$PATH:/usr/local/android-sdk-linux/tools:/usr/local/android-sdk-linux/platform-tools"
export JAVA_HOME="/usr/lib/jvm/java-8-openjdk-amd64"
export LD_LIBRARY_PATH="$LD_LIBRARY_PATH:/usr/local/android-sdk-linux/tools/lib64:/usr/local/android-sdk-linux/tools/lib64/qt/lib"
export GOPATH="/home/ubuntu/controller"
- to support remote machine to connect the emulators via "adb connect :"
- use iptables to implement port forwarding
- use iptables-persistent to persist the rules
configure
$ sudo iptables -t nat -I PREROUTING -p tcp -i eth0 --dport 5555 -j DNAT --to-destination 127.0.0.1:5555
$ sudo iptables -t nat -I PREROUTING -p tcp -i eth0 --dport 5557 -j DNAT --to-destination 127.0.0.1:5557
$ sudo iptables -t nat -I PREROUTING -p tcp -i eth0 --dport 5559 -j DNAT --to-destination 127.0.0.1:5559
$ sudo iptables -t nat -I PREROUTING -p tcp -i eth0 --dport 5561 -j DNAT --to-destination 127.0.0.1:5561
$ sudo iptables -t nat -I PREROUTING -p tcp -i eth0 --dport 5563 -j DNAT --to-destination 127.0.0.1:5563
$ sudo iptables -t nat -I PREROUTING -p tcp -i eth0 --dport 5565 -j DNAT --to-destination 127.0.0.1:5565
$ sudo iptables -t nat -I PREROUTING -p tcp -i eth0 --dport 5567 -j DNAT --to-destination 127.0.0.1:5567
$ sudo iptables -t nat -I PREROUTING -p tcp -i eth0 --dport 5569 -j DNAT --to-destination 127.0.0.1:5569
$ sudo iptables -t nat -I PREROUTING -p tcp -i eth0 --dport 5571 -j DNAT --to-destination 127.0.0.1:5571
$ sudo iptables -t nat -I PREROUTING -p tcp -i eth0 --dport 5573 -j DNAT --to-destination 127.0.0.1:5573
check the configuration
$ sudo iptables -t nat -L
Chain PREROUTING (policy ACCEPT)
target prot opt source destination
DNAT tcp -- anywhere anywhere tcp dpt:5573 to:127.0.0.1:5573
DNAT tcp -- anywhere anywhere tcp dpt:5571 to:127.0.0.1:5571
DNAT tcp -- anywhere anywhere tcp dpt:5569 to:127.0.0.1:5569
DNAT tcp -- anywhere anywhere tcp dpt:5567 to:127.0.0.1:5567
DNAT tcp -- anywhere anywhere tcp dpt:5565 to:127.0.0.1:5565
DNAT tcp -- anywhere anywhere tcp dpt:5563 to:127.0.0.1:5563
DNAT tcp -- anywhere anywhere tcp dpt:5561 to:127.0.0.1:5561
DNAT tcp -- anywhere anywhere tcp dpt:5559 to:127.0.0.1:5559
DNAT tcp -- anywhere anywhere tcp dpt:5557 to:127.0.0.1:5557
DNAT tcp -- anywhere anywhere tcp dpt:5555 to:127.0.0.1:5555
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
Chain POSTROUTING (policy ACCEPT)
target prot opt source destination
persist the rules by installing iptables-persistent
$ sudo apt-get install iptables-persistent
Reading package lists... Done
- iptables for Ubuntu
- ip for mac
For example(for ubuntu):
$ sysctl -w net.ipv4.conf.eth0.route_localnet=1
or
$ sudo vi /etc/sysctl.conf
# port forwarding for adb connect
net.ipv4.conf.eth0.route_localnet = 1
$ iptables -t nat -I PREROUTING -p tcp -i eth0 --dport 5921 -j DNAT --to-destination 127.0.0.1:5921
$ sysctl -w net.ipv4.conf.wlan0.route_localnet=1
or
$ sudo vi /etc/sysctl.conf
# port forwarding for adb connect
net.ipv4.conf.eth0.route_localnet = 1
$ iptables -t nat -I PREROUTING -p tcp -i wlan0 --dport 5921 -j DNAT --to-destination 127.0.0.1:5921
$ adb forward --list
$ sudo iptables -t nat -L -n -v
on the mobile phone user: "test" / password: "test" ssh [email protected] -p 5921
It seems the behaviors in MAC and Ubuntu are different. For example, VNC launch.sh only create listening port on the external interface in MAC. However, it will create listening port on all the interfaces including localhost.
- /etc/rc.local
$ cat /etc/rc.local
#!/bin/sh -e
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#
# By default this script does nothing.
# create emulators as ubuntu because of avd file path
su ubuntu - -c /home/ubuntu/controller/bin/create_emulators.sh
# run controller as root because of port:80 permission
/home/ubuntu/controller/bin/node &
# print done message for debugging
echo "initialization is done"
exit 0
http://www.41post.com/5003/programming/android-adb-remote-emulator-access
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent