Lately Sony has been very “developer friendly” with their Android devices such as the Xperia Z, and that trend won’t stop as Sony recently fully opened up their SmartWatch platform to all developers. Per Sony:
We are now taking the next step to open up SmartWatch. Previously, you’ve been able to create apps for SmartWatch with the Sony Add-on SDK, but now we hope to see even more innovation as we’re making it possible for advanced developers to create and flash alternative firmware, by sharing technical details and instructions.
Doing so does come with some limitations as you will no longer be able to use SmartConnect or any compatible SmartWatch app that’s available in the Google Play Store. So keep that in mind. For more info, hit the source link!
This year’s Smart App Challenge by Samsung has arrived, and will focus on creative usage with its Chord SDK. The Chord SDK features quick peer-to-peer sharing, and allows for collaboration and sharing info/media between multiple devices on the fly.
There’s $800,000 in prize money at stake for 10 different applications. The possibilities are essentially limitless for this new technology, and perhaps the most impressive demonstration of what the SDK can do is featured in the surround sound speaker mode. Samsung will take entries from June 20th to August 31st and the winner will be announced this December.
This adds a fresh perspective to what Samsung is trying to accomplish and it will be exciting to see the outcome of the competition.
Source: Samsung Developer Site
Koushik Dutta has been on a roll lately. First he created Carbon Back Up. Afterwards he released a beta of his Superuser app. The beta has now graduated and is available for all rooted users in the Play Store. Besides proper multi-user support and being open source, the app has the following features:
* Multiuser support
* OPEN SOURCE (https://github.com/koush/Superuser)
* Pin protection
* Manifest permission support
* Per app configuration
* Request timeout
* Proper Tablet UX
For those of you root users that want a superuser app by a trusted name in the Android development world, hit the break for a download link. Enjoy!
It appears as though the highly anticipated and long-awaited OUYA consoles have officially been given a firm ship date of December 28th today, in addition to the news that the console’s SDK, dubbed “ODK”, would be available later that very same day. This announcement means Kickstarter backers can expect to receive the device “within a couple days” of the 28th, effectively kicking off their new year with a bang.
Production units are still expected to ship some time in March of next year, though the company has yet to announce an official release date. On the software side of things, users can expect to set up their units, including account activations by Christmas day. For the full run-down, be sure to hit the source link below.
Google has made a change to the terms and conditions of the Android SDK (software development kit) to explicitly prohibit developers from taking any action that may lead to the fragmentation of Android. This is the first change to the terms since April, 2009.
Section 3.4 of the SDK terms states: You agree that you will not take any actions that may cause or result in the fragmentation of Android, including but not limited to distributing, participating in the creation of, or promoting in any way a software development kit derived from the SDK.
With such a wide variety of Android devices of different specs and sizes, Google and the different Android manufacturers have had a hard time keeping devices updated with the latest OS. The multiple versions of Android in use by consumers makes developing for Android a much more complex and pricey endeavor. This change marks the first overt step Google has taken to combat this issue.
Google released the Android 4.1 SDK today and it is now available for download. Included with the SDK are revised versions of SDK Tools (20.1.1) and NDK revision 8b. The new tools will let developers publish code up to API level 16 using Jelly Bean APIs. As usual, the SDK is available for Windows, Mac and Linux platforms. The SDK and related tools can be installed via an existing installation of the SDK or one can head over to the Android Developers’ web site.
Thanks to LastStandingDroid over at the XDA forums, the Samsung Galaxy S II (I9100) has received an Android 4.1 Jelly Bean SDK port. With any SDK port, the build is fairly rough and one should expect many things to either not work, or not work correctly. Although there is a short list of things that do work:
As we’ve seen over the last few days, folks are hard at work creating Jelly Bean ROMs for a variety of devices. Up to this point, work seems to be limited to smartphones or Nexus tablets. That appears to have changed with some work done by user randomblame over at XDA. He has succeeded in creating an SDK port of Jelly Bean for an Acer Iconia A500. It is not yet ready for daily use as several items are still not functioning, including audio, wifi, sdcard access, and usb mounting of flash drives. While work continues on those issues, users can at least get a taste of Jelly Bean if they are willing to root their device and install the ROM. Hit the source link for instructions and access to the files.
The HTC One X has gotten itself an SDK port of Google’s Jelly Bean firmware thanks to the XDA developer by the name of tgascoigne. At this point it’s nothing you can use as a daily driver, but serves as a great way to get yourself a nibble of Jelly Bean if you’re a One X user. Many things don’t work such as the camera, WiFi, audio, and much more. The developer has stated that he’s already working with the actual Galaxy Nexus OTA of Jelly Bean ported to the One X. If he’s able to get that working that build should be far more superior than the current SDK build. If you don’t mind your phone pretty much unusable but still want to give Jelly Bean a shot, then head on over to the XDA thread and flash away. Of course, needless to say, your One X will have to be rooted and the boot-loader unlocked in order to flash the ROM. You can also watch the video at the bottom to see this port in action.
We all understand there are things we do on our phones that will drain the battery faster. Streaming video, playing games, and using the GPS all cause the juice to flow out faster than we’d like. When we put our phone to sleep though, we expect the battery to drain very slowly. Software glitches can ruin that dream, sometimes emptying the battery in as little as a few hours. Researchers at Purdue have decided enough is enough, and set out to try to identify and mitigate the problems the bugs cause.
Read about what they found, and how they plan to fix it, after the break.