In Late 2014, Google - along with Adidas, Polar, and Withings - opened a Google Fit developer challenge, hoping to get more apps into Google's burgeoning fitness ecosystem.
Today, the winners of that challenge have been announced. The twelve grand prize winners will get special promotion in the Play Store, greatly increasing their visibility to potential users. Additionally, winners (grand prize and runners up) will receive the X_CELL and SPEED_CELL from Adidas, an unspecified "new" Android Wear device, a Loop activity tracker from Polar, and a Smart Body Analyzer from Withings. Read More
There's no more waiting for Android 5.1 if you've got a Nexus 4 or either version of the 2013 Nexus 7. Google has posted the full factory images on the dev site, meaning you can flash the new version to get up to date no matter what you've done to your device's software.
Back in November, Google updated its new design guidelines for the first time, adding guidance on the navigation drawer and launcher icons, and - happily - a "what's new" section, which it said would serve as a place to explain future updates to the guidelines.
Yesterday, Google gave the guidelines another sizable update, adding an entire section to guide devs and designers on when and how to use floating action buttons, along with new guidelines for data tables, overall app structure, and guidance on important units and measurements, plus a lot more. Here's Google's full list of changes.
The April 2015 release of the material design spec includes the following new sections:
Additional significant content updates include:
- Typography adds further guidance on style and line height for dense and tall languages
- Cards includes more specs for laying out actions and content
- Dialogs contains additional layout guidance
- Tabs adds guidance around label content and more complete sizing specs
- Scrolling techniques adds guidance for overlapping content
Where Google's last update to the guidelines seemed to be about filling holes, this update is positioned as a response to the community, giving more specific guidance on things that seem to have arisen as points of interest in material design. Read More
It's been, what, five weeks since Google announced Android 5.1? In all that time the update has still not arrived on many of Mountain View's Nexus devices. But at least one more is joining the 5.1 club today, and it's a little unexpected—the LTE Nexus 7 2013. No, the WiFi version still hasn't popped up.
Cyanogen announced today via Google+ that Cyanogen OS 12 (Lollipop) is finally available for OnePlus One users. If you want that Lollipop action right now, we've got the ZIP file. Cyanogen OS 12 features all the material design eye candy one would expect, as well as the more functional changes of Lollipop. In addition to the standard fare, there are a couple of features exclusive to Cyanogen.
Updates get us excited, especially when they involve making the leap to the latest version of Android. But for some Nexus 5 users, the transition has come at the expense of their camera. Following the release of Android 5.1, they've been unable to reliably activate the camera without getting hit by crashes.
This incident occurs once the stock app or any other piece of software tries to access the camera, such as Facebook or Snapchat. Smart Unlock has also been affected by this issue. A bug report has been filed, with the issuer suspecting that the problem concerns android.hardware.Camera._getCameraInfo(). Read More
If you've got a Nexus 4, your days on Android 5.0 are numbered: because you're going to Android 5.1! Assuming you, you know, want to. The OTA link is right here, allowing you to upgrade from LRX22C to LMY47O. The update clocks in at 174MB.
You can check out all of the new Android 5.1 features in our various feature spotlight posts, and there are actually quite a few. 5.1 is also a major bugfix release, so hopefully the inevitable issues you've been running into on Android 5.0 are largely solved with this OTA. Or, more likely, hopefully they will be solved in Android 5.1.1, the bugfix to the bugfix. Read More