Google has released the first beta of Android 17, marking a shift in its development process with the introduction of a continuous “Canary” channel. This new approach aims to deliver features and APIs to developers more quickly, improve stability through early testing, and streamline the testing process with over-the-air updates.
Getting Android 17
Android 17 is now available for developers and enthusiasts through several avenues, including Google Pixel devices and the Android Emulator.
On Google Pixel
Users with compatible Google Pixel devices can check for and install the Android 17 beta wirelessly through the phone’s settings. Supported devices include the Pixel 6, Pixel 6 Pro, Pixel 6a, Pixel 7, Pixel 7 Pro, Pixel 7a, Pixel Tablet, Pixel Fold, Pixel 8, Pixel 8 Pro, Pixel 8a, Pixel 9, Pixel 9 Pro, Pixel 9 Pro XL, Pixel 9 Pro Fold, Pixel 9a, Pixel 10, Pixel 10 Pro, Pixel 10 Pro XL, and Pixel 10 Pro Fold. While a full data reset is generally not required for the update, Google recommends backing up data before installation as a precaution.
For those who prefer a manual installation, the Android Flash Tool is recommended for flashing the system image. Alternatively, system images can be downloaded from the Pixel downloads page and installed following the provided instructions. This method is particularly useful for automated or regression testing scenarios where greater control is needed.
Configuring the Android Emulator
The Android Emulator provides a flexible environment for exploring new features and APIs, and testing behavioral changes in Android 17. Developers can configure virtual devices to emulate various screen sizes and device characteristics.
Setting up a Virtual Device (Phone)
To set up a virtual device emulating a typical phone, developers should first install Android Studio Meerkat | 2024.3.1. Within Android Studio, navigate to Tools > SDK Manager and ensure the latest version of the Android Emulator is installed. Then, using Tools > Device Manager, add a new device and select “Create Virtual Device.” Choose a Pixel device definition from the Phone category and select the Android 17 system image, labeled “Baklava,” downloading it if necessary. Finally, configure any remaining device parameters and launch the virtual device.
Setting up a Virtual Device (Tablet or Large Screen Device)
For emulating tablets or large-screen devices, the process is similar. After installing Android Studio and the Android Emulator, use the Device Manager to create a new virtual device. Select a tablet definition (like the Pixel Tablet) or the Pixel Fold from the Phone category. Again, choose the Android 17 “Baklava” system image and complete the configuration. Repeating this process allows developers to create multiple virtual devices with different screen sizes for comprehensive testing.
Resizable Emulator
Android 17 introduces a resizable emulator configuration. When using a resizable device definition with the Android 17 system image, the Android Emulator allows toggling between phone, foldable, and tablet reference devices. The foldable reference device also allows switching between folded and unfolded states. This feature simplifies validation of responsive layouts and behavioral testing across different form factors. To create a resizable emulator, use the Android Studio Device Manager and select the “Resizable” device definition in the Phone category.
What’s New in Android 17
The first beta of Android 17 focuses on privacy, security, and performance refinements. It builds upon work for more adaptable apps, introduces enhancements to camera and media capabilities, provides new tools for optimizing connectivity, and expands profiles for companion devices. The shift to the Canary channel represents a fundamental change in how Google delivers updates to developers.
The new Canary channel offers three key benefits: faster access to features and APIs, improved stability through early testing, and easier integration with continuous integration workflows. The Android 17 schedule indicates a quick move to the Platform Stability milestone, targeted for March, which will deliver final SDK/NDK APIs and largely final app-facing behaviors.
Further Information
Developers can find more information about the changes in Android 17 and how they might affect their apps by consulting the Android 17 features documentation. This includes details on new APIs and functionalities available in the latest release.
