Understanding the Characteristics of Android Wear OS Renju Liu Felix Xiaozhu Lin Purdue ECE Purdue ECE
[email protected] [email protected] User Launch action App UI Abstract touch starts shown Interactive wearable devices bring dramatic changes to apps and Phase 1 Phase 2 1000 hardware, leaving operating system (OS) design in the mist. To this mW end, we thoroughly examine the execution efficiency of Android 500 0 Wear, a popular wearable OS. By running a suite of fifteen bench- Power / marks, we profile four system aspects: CPU usage, idle episodes, thread-level parallelism, and microarchitectural behaviors. We present the discovered inefficiencies and their root causes, together with a Idle Busy with various tasks series of widespread, yet unknown OS design flaws. Towards de- Exec. CPU 177 ms 810 ms signing future wearable OSes, our study has yielded a generic les- son, key insights, and specific action items. 1. INTRODUCTION 28 ms 130 ms 19 ms Interactive wearable, as exemplified by smart watches, is a new- Figure 1: The timeline of launching the “Settings” app on An- comer to the spectrum of mobile computers. Being in close prox- droid Wear, showing both anomalous idle episodes (not due to I/O) imity to users, it further extends the boundary of mobile-cloud ser- and intensive CPU execution vice, integrating computing even tighter with our daily lives.1 In the year 2014, nearly three million of Android Wear and Apple watch devices have been shipped [7]. held [10, 47] for compatibility and engineering ease. There was Wearable, as compared to existing mobile devices such as smart- neither a clear understanding of how such a design choice impacts phones and tablets, exhibits unprecedented characteristics.