Update – In response to queries regarding the technicalities of the post, we’d like to clarify what we’ve released here. We provided build instructions based on the AOSP project under the branch android-m-preview, showing the Android M platform changes so far. That build gives an early preview of Android M for custom ROM developers to play with. Be aware that at this point the API levels are still at Lollipop MR1, what we show is Android M Developer Preview purely from a platform perspective.
Note that the Android M Developer Preview for Nexus devices from Google supports the latest API level. Xperia devices flashed using the build instructions linked from this post, do not support those APIs.
You can now create a test image of Android M Developer Preview and flash that onto any Xperia device in Sony’s Open Device program. The recently released Android M Developer Preview gives developers the necessary tools to prepare for the full Android M release.
With Google’s Android M Developer Preview, it’s worth noting that there are a variety of system changes and some API behavioural changes. This includes a new permission system, where users can directly manage app permissions at runtime. To take into account these changes, you may want to test your apps prior to the M release to ensure compatibility.
If your Xperia device is listed as part of our Open Device program, you can use our easy-to-follow guide to get instructions on building AOSP M Developer Preview and download the necessary software binaries. You can then create your test image, flash it onto your device and explore the Android M Developer Preview platform.
It’s important to note that the AOSP software is not certified or intended for regular use. It’s only available for devices with an unlocked boot loader and comes with some limitations, for example, the modem and the camera are not implemented.
If you have any questions or comments, drop us a line below.