It’s important to note, though, that a vanilla AOSP build is not the refined Android experience you may be expecting. A few clicks and a download later and your device will be on the newest version of AOSP. Once those requirements are met, you can get started with the Android Flash Tool to install either the newest AOSP build or you can enter the build ID you’d like to use from the Android CI. The only real requirements are a Pixel phone (Pixel 2 or newer) or HiKey developer board, a web browser compatible with the WebUSB standard - only Chrome, the new Chromium-based Edge, and Opera for now - a USB cable, and, if you’re on a Windows computer, the Android USB drivers. ![]() This means you can even use this tool to flash AOSP onto your Pixel from a Chromebook, which is a wild thought. In fact, you don’t even need to have any of the usual developer tools installed on your device like adb. Today, Google is taking the next logical step by launching the Android Flash Tool, a new web app that can install AOSP onto your Pixel phone directly from the browser. With the launch of the Android CI, there are far fewer steps involved as developers can now simply download a prebuilt version of the latest AOSP, but they’ll still need to know how to flash it onto their phones. Those with enough experience working with the Android codebase and its tools usually build and flash their own devices with AOSP to keep up with the latest developments and changes. While our first look at the next major version of Android usually comes from an official beta release - typically launched shortly before Google I/O - development on Android continues all year round in the Android Open Source Project. Today, the company has unveiled the Android Flash Tool as a simple way to try any AOSP build on your Google Pixel phone, right from your browser! For over a year now, Google has made the Android Open Source Project’s automatic build process public through a continuous integration (CI) dashboard.
0 Comments
Leave a Reply. |