Google has launched a physical development kit that allows Android devices to communicate with external hardware based on Arduino boards . This is the Android Open Accessory , or ADK , an initiative that opens the door for developers to create electronic accessories that interact directly with Android phones and tablets using a standardized USB protocol.
The announcement of this Android Open Accessory Development Kit was made at the annual Google I/O conference , held in San Francisco, USA, as part of the company's strategy to take Android beyond the phone, tablet or even the connected TV.
What is Arduino and why did Google choose it for the ADK?
Arduino circuits emerged in 2006 with the goal of enabling anyone to create interactive electronic products without needing to be an engineer. It's an open-source hardware platform consisting of a microcontroller board, input/output ports, and a very simple development environment . The language used, Wiring/Processing, is similar to the well-known C++ , making it easy to learn for those already familiar with programming. Furthermore, Arduino relies on easy-to-program microcontroller kits, facilitating access for makers and students.
Typical Arduino hardware is based on Atmel AVR microcontrollers and offers digital and analog pins for connecting sensors, actuators, LEDs, motors, relays, joysticks, displays, and more. The software consists of the Arduino IDE , which allows you to write a sketch (program), compile it, and upload it to the board via USB.
Google chose Arduino as the basis for the ADK for several reasons: a huge and very active community, abundant documentation, a multitude of ready-to-use libraries, and the ability to easily adapt the design to compatible boards. All of this made the Android Open Accessory hardware accessible to both novice makers and professional developers.
What is Android Open Accessory and how does it work?
According to the CNET website , with Android Open Accessory on Arduino , Google allows developers to create their own hardware accessories , which can then be controlled by Android devices . The key lies in a specific USB communications protocol , known as the Android Accessory Protocol , which defines how the accessory detects the mobile phone or tablet and how data exchange is established.
In this operating model, the accessory acts as a USB Host (providing power and enumerating the bus), and the Android phone or tablet behaves as a USB device . Many older Android devices could only function as USB devices and could not initiate connections with other peripherals. Android Open Accessory support overcomes this limitation by allowing the accessory itself to initiate and manage communication.
To take advantage of this system, the Android device must support accessory mode . This support was introduced in Android versions 2.3.4 and 3.1 , and later extended to numerous subsequent versions. When accessory mode is available, the phone can recognize a compatible accessory, negotiate the protocol, and automatically launch the Android application associated with the hardware.
In this way, it is possible to create a complete line of "Made for Android" external devices : docking stations, smart exercise bikes, home automation equipment, robots, industrial measurement systems, interactive toys and virtually any hardware that can communicate data via USB or, in later evolutions, also via Bluetooth.
The role of the ADK: Android hardware, firmware, and app
According to information published on the Google I/O conference website , the Android Open Accessory Development Kit (ADK) provides a reference implementation of a USB accessory for Android based on the Arduino platform. This kit includes three main components: hardware , firmware , and a sample Android application.
On the hardware side, the ADK is based on a board similar to the Arduino Mega 2560 , which integrates an ATmega2560 microcontroller and a USB Host Shield . This board is known as the ADK board and has standard input/output pins to which the shields are connected . The ADK demo shield includes a joystick, RGB LEDs, temperature and light sensors, capacitive buttons, and other components for testing communication with a mobile device.
The ADK firmware is written in C++ for Arduino and incorporates the AndroidAccessory library along with the USB Host Shield library . This combination allows the board to act as a USB host, detect a connected Android device, check if it supports the accessory protocol, and, if so, establish communication via bulk input/output transfers .
Finally, the sample Android application (known as DemoKit ) demonstrates how mobile software can read sensor data or joystick input from the accessory and send commands to the Arduino to turn on LEDs, move servos, activate relays, or modify any other connected element. The kit includes the complete code so developers can study, adapt, and use it as a basis for their own projects.
How Android detects and manages an Open Accessory
The typical operating flow of an Android Open Accessory consists of several well-defined steps. First, the accessory is constantly waiting for devices connected to its USB port. When an Android phone is connected, the accessory's firmware reads the device's USB descriptor to check if it is already in accessory mode (using the Google vendor ID and the product IDs reserved for this mode).
If the mobile phone or tablet is already in accessory mode, the firmware simply looks for the appropriate bulk endpoints in the configuration descriptor to send and receive data. If it isn't, the accessory sends a series of USB control requests : the first to check if it supports the protocol ("Get Protocol"), several more to send the identification strings (manufacturer, model, description, version, URL, and serial number), and finally, a request for the device to enter accessory mode.
Once the phone has switched modes, it is re-enrolled on the USB bus with the Android accessory IDs, and the firmware re-analyzes its descriptors to locate the main interface and its endpoints. From that point on, the board can read data from Android (for example, commands sent from the app) and send information to Android (sensor readings, button states, etc.) using very simple binary packets.
This architecture has the advantage of separating the low-level USB logic from the Java or Kotlin code on the mobile device: the app only needs to interpret the data that arrives through the Android USB accessories API, while the Arduino firmware takes care of the fine control of the bus and the management of the connection.
Advantages of combining Android Open Accessory and Arduino
According to the Google I/O conference website , the company expects this development kit to further expand the use of the Android mobile operating system by enabling the creation of new electronic products equipped with the software, beyond traditional tablets and smartphones. The combination of a powerful mobile device with sensors, connectivity, and a screen, along with an Arduino microcontroller connected to physical sensors, opens the door to a highly versatile ecosystem.
For users, this translates into the possibility of interacting with all kinds of external devices : from a stationary bike that records effort and displays personalized workouts on the phone screen, to home automation systems that allow you to turn on lights, open doors or control garden irrigation using your mobile phone as a control center.
For hardware developers, the ADK and accessory protocol provide a standardized way to communicate with Android , simplifying the creation of commercial products labeled " Compatible with Android ." Furthermore, a wide range of compatible boards is available from various manufacturers (official Arduino, third-party boards, PIC-based solutions, etc.), allowing developers to choose the most suitable hardware-cost combination for each project.
In the professional and industrial field, the use of Android as a graphical interface linked to an Arduino or similar microcontroller facilitates the creation of cost-effective control panels , remote monitoring systems, Internet of Things (IoT) solutions , and specialized devices that benefit from mobile connectivity (WiFi, 4G/5G, NFC, Bluetooth) without having to develop that entire communications stack from scratch.
Relationship between Android Open Accessory and the Arduino ecosystem
The adoption of the Arduino platform as the base hardware for the ADK is supported by its large community and abundant available documentation. Beyond the official Arduino Mega ADK board, there are multiple compatible alternatives: boards with USB Host Shields , dedicated boards like the IOIO, solutions based on the PIC24F or other microcontrollers, as well as commercial derivatives created by various manufacturers for robotics, UAVs, or radio control projects.
On a practical level, a typical project with Android Open Accessory and Arduino needs three fundamental elements: a board that implements the accessory protocol, possibly some shields that expand the capabilities (for example, Ethernet ports, Bluetooth modules, SD card reader, motor control or relays) and the ADK package , which includes reference firmware, hardware specifications and examples of Android applications.
The Arduino component is programmed using the Processing/Wiring language , while the Android application is typically developed in Java (or in modern languages compatible with the Android SDK). This separation allows electronics specialists to focus on the microcontroller's firmware and app developers to work on the interface and logic on the phone side.
In addition, there are other tools like Amarino , which offers a simplified way to connect Arduino and Android via Bluetooth, ideal for those who want to focus on rapid prototyping without delving into the details of the ADK protocol. Amarino provides an Android app and an Arduino library that make it easy to send sensor data and control pins from your phone without requiring extensive prior Android programming knowledge.
“I don’t think of it as something we’ve built, but rather as something that can be used to explore what Android can do , ” said Andy Rubin , director of the Android project, referring to the launch of the Android Open Accessory Kit . This statement encapsulates the spirit of this initiative: to offer an open foundation for the community to experiment and bring Android to all kinds of connected physical objects.
Thanks to Android Open Accessory and the Arduino ecosystem, the phone ceases to be just a consumer device and becomes the brain of interactive projects in education, robotics, home automation, research and leisure, with a growth potential that continues to attract developers, makers and hardware manufacturers from all over the world.