Did you know that SmartEyeglass can be used as a Bluetooth headset for the host smartphone or tablet? In our new SmartEyeglass audio I/O guide, published today, you can learn how your app can send and receive audio data with the SmartEyeglass built-in microphone and speaker. This is actually done by using the Android Bluetooth Hands-Free Profile API (Android BT HFP API), much as you would for any standard Bluetooth headset.
This week, Google released the source code for Android 5.0, Lollipop, and as you can see in the video above, the AOSP (Android Open Source Project) version of Android 5.0 is already running on Xperia Z3, as well as Xperia Z2 and Xperia Z1. Check out the video for a preview of Android 5.0, and read on for details.
Sony’s SmartWatch 3 is now on sale in selected markets, with other markets to follow during the coming weeks. You can start developing apps right away for SmartWatch 3, using the Android SDK together with the extended set of APIs from the Android Support Library and Google Play Services. SmartWatch 3 apps can display notifications, handle voice actions, access innovative sensor technology, and much more.
An update is now available for the Smart Remote Control app for Sony cameras, which adds remote movie recording support to the cameras DSC-HX400 and DSC-HX60, but most importantly, it adds support for the Focus mode feature in the Camera Remote API beta SDK, for compatible cameras. This allows you to develop apps that can control the camera’s focus mode remotely.
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!
SmartWatch 2 is a success among app developers, with over 500 apps available on Google Play. When developing SmartWatch 2 apps developers have until now had to struggle with quite massive PDFs for the API documentation, but that’s about to change. All the documentation have now been revised based on all the requests and input we have received, and we have made the SmartWatch 2 API documentation available online as web pages at developer.sony.com.
Are you interested in trying SmartEyeglass, Sony’s binocular, see-through eyewear with camera, GPS and sensors? Or maybe learn about how to test your apps on Sony devices for free through the newly-launched Remote Device Lab (beta)? Find out about all that Sony has to offer developers at this year’s Droidcon London.
Today we’re happy to tell you that we’ve added Xperia Z2 and Xperia Z1 to our AOSP for Xperia project on the SonyXperiaDev GitHub. In addition, Xperia Z has been updated to the latest Android version. At the same time, we’re starting to use a unified kernel for devices based on the Qualcomm® MSM8974 platform, which will make it easier for all you community developers to adapt the kernel to your needs.
Now you can pack Linux kernels for devices based on Qualcomm® platforms using a dedicated open source tool from Sony: the mkqcdtbootimg tool. The mkqcdtbootimg tool, which is available on GitHub, adds support for including one or more device tree blobs when rebuilding kernels. To reflect this, our recent tutorial How to rebuild kernels for flagship Xperia devices has been updated to make use of the new tool.
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.