REMOTE ANDROID ON ARM SERVERS
In this demo using ARM servers, we show:
- Android running on two ARM servers in different locations
- A compressed graphical rendering stream created on the server
- Transmission of the rendering stream via a 4G network to an X86 Ubuntu client
- Rendering and display of the graphical interface on the client
Results of Two ARM Servers on Two Continents
The distance to the desktop server, an Odroid C2 ARM processor, is 40 cm.
The distance to the AWS A1 ARM server in Dublin, Ireland, is over 4000 km from the client in Tel Aviv, Israel.
The round-trip latency is 85 ms for a WAN link to the server in Dublin. The 4G network of the demo adds another 50 ms to the round-trip latency giving a combined latency of 135 ms.
Graphical performance of the local server and the remote server is virtually identical despite seven orders of magnitude (ten million times) difference in the distance between the two servers and client.
Edge Computing and 5G Mobile Networks
Edge Computing and 5G Mobile Networks are technologies designed to reduce network congestion and latency. Currently, there is spotty global coverage concentrated in major cities; full deployment of Edge computing and 5G networks will take years. Access to Edge servers are not generally available.
Android in the Cloud can use widely available technologies such as 4G networks and a public Cloud – resulting in a high-quality remote Android solution.
When Edge Computing and 5G become available, performance of Android in the Cloud will only improve.