If you’ve got an AOSP build issue, a question about custom ROMs, or you just want to help other community developers using open devices, we now have a forum available for these topics. The Open Devices community is where you can discuss open source issues, and ask (or answer) open device development-related questions. Read more after the jump.
As of today, full device encryption is possible to build from open source code for the devices supported in our AOSP for Xperia project. Together with last week’s addition of functionalities like Wi-Fi, NFC, GPS and audio, this is thanks to the efforts from open source community developers, who spends hours and hours of their free time developing and adding their commits to the SonyXperiaDev GitHub projects.
Today we’ve added Xperia E3 and Xperia T3 to our open device project, which means that developers can now build their own version of AOSP for most* Qualcomm®-based Xperia devices released during 2014. We’ve also updated the source code for Xperia T2 Ultra and Xperia M2 to improve stability.
By unlocking the boot loader of your Xperia device, it becomes possible put a custom ROM on it. Even though we don’t recommend this to standard users, as it is not needed, we know that many of you would like to get more details on how to unlock a device. To explain this further, we have now created this step-by-step tutorial video.
Today we have added Android 5.0 AOSP device configuration source code, pre-built software binaries and build instructions for Xperia Z3, Xperia Z3 Compact, Xperia Z2, Xperia Z1 and Xperia Z1 Compact. If you’re a custom ROM developer, you can now create Android 5.0, Lollipop, AOSP-based custom ROMs for these devices.
You can now find instructions on how to use device configurations from Sony to build AOSP KitKat and flash it on an unlocked Xperia device, in a new guide we’ve created. This guide includes a step-by-step instruction that takes you from preparations of your environment, to what tools you should download and install, and then how to configure the code. At last, we’ll explain how to build an AOSP image and flash it to your device. Please note that you should be familiar with Android development to use the instructions, and that the software created is not intended for daily usage and there are important limitations. Head over to the How to build AOSP KitKat and flash it on an unlocked Xperia device guide to get started!
Recently, I had the opportunity to talk at XDA DevCon in Manchester about Sony Mobile’s approach to AOSP. We’ve seen a lot of engagement on the subject – lots of comments, lots of questions – so we wanted to share more details and clarify a few points about the work we do to provide binaries and source code to community developers. The binaries and source code are then used as a base when community developers are compiling their own custom ROMs.
If you’re an open source developer working with custom ROMs and kernels, or if you’re part of the custom ROMs community, we have some great news for you. As yet another step in our strive for openness, our Unlock boot loader service is now re-launched with improved usability. It will now be easier to go through the steps it takes to unlock a device.
We have now added support for Xperia™ Tablet Z to our flash tool for Xperia™ devices. With this tool, you can flash Sony software on devices with the boot loader unlocked. And now there is software available for Xperia™ Tablet Z (SGP321 and SGP311). Get all the information you need on the flash tool page.