Last December, Google announced LiquidFun, a cross-platform physics engine developers could use to create realistic gaming experiences. Now, as a part of Google Developer Day at this year's Game Developers Conference, the company has released version 1.0 out into the wild. It's also provided no shortage of videos demoing what the project is capable of.
When Samsung announced the Gear 2 and the Gear 2 Neo last month, the news came with the confirmation that the company was dropping Android from both devices. Instead, both smart watches are powered by Tizen. This may not mean all that much for consumers in the short term, but it does impact developers. For you, Samsung has just shared the first version of the Tizen SDK aimed at wearables. This is what you need to grab if you intend to build apps for the company's two intelligent wristwatches.
It's no mystery that Google has been poking around wearable gadgets for quite some time. The list of projects seems to keep growing as we hear about rumors of an LG-made smartwatch, another prototype watch designed by Motorola, and of course, Google's own Glass. Earlier today at SXSW, Sundar Pichai took to the stage to announce plans to release a brand new SDK for Android-based wearable devices in about two weeks.
Intel's progress into the Android ecosystem hasn't exactly been earth-shattering. The number of high-end and mid-range smartphones equipped with an ATOM CPU still number in the single digits, making the x86 architecture a fairly low priority for app developers. In addition, Intel's emulator images have always lacked support for the Google APIs, leaving developers without the ability to test common staples like Google Maps or push messaging. Fortunately, that issue was recently rectified with KitKat as Google and Intel have finally shipped an x86 system image with Google API support.
If you're a fan of source code (and who isn't?), you might be excited to know HTC has released the code for Power To Give. The Power To Give initiative was officially announced a few days ago at MWC with its corresponding app in the Play Store. Today, the HTC Dev portal posted a full source drop of the project, including the app and various platform-specific versions of the server code.
The recent release of Google Play Services 4.2 brought with it some exciting additions like the official Cast API and significantly improved support for Google Drive. One of the lesser publicized additions is the official launch of GoogleApiClient, a new component intended to simplify setting up and managing connections to Google's assorted API endpoints. Additionally, there is now support for queuing up read-only queries and a choice of executing calls synchronously or asynchronously.
It was only 3 months ago when we first met the brand new Android Runtime, dubbed ART. In that time it has gained a substantial following by enthusiasts throughout the Android community. Given its "preview" status and warnings from the Android team that ART wasn't ready for the general population, it appeared unlikely that it would officially take the place of Dalvik anytime soon. However, a new commit to the Android Open Source Project (AOSP) is strong evidence that ART may become the default runtime in the next version of Android.
Fans of Google in general and Android in particular are still reeling from yesterday's announcement that Motorola is being sold to Lenovo. Google acquired Moto just two years ago, and while its time within Google has been beneficial, it's clearly not going to become the official mobile hardware arm that many had hoped for. But there's no reason to think that the big G is out of the hardware game altogether - in fact, at least one report says that another recent acquisition may be accelerating it.
Shortly after the new Android Runtime made its grand entrance, I ran a pretty exhaustive (and exhausting) series of performance benchmarks that showed ART wasn't really ready to blow us away. At the time, I opted to avoid the topic of battery life because it is so difficult to test accurately and with unbiased, meaningful results. As it turns out, that was dumb. Yup, so many of you have asked, I finally had no choice but to dive in and run a battery of tests on...well, the battery.
Much of Android's development is done out in the open, which is how several Android developers noticed that a recent commit to the Android Open Source Project master tree would break many of your favorite root apps. This is the result of a newly implemented security feature, rather than an active effort to lock things down on Google's part. Nevertheless, it could result in some inconvenience, so developer Chainfire has taken to his Google+ page to detail what will happen if the change is not reverted before the release of a future version of Android.