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.
If you're idly cruising the Play Store on the web, checking out the most downloaded apps ever, you might stumble onto a little glitch when an install count crosses 1 billion. That's right, billion... We're talking 9 zeros, folks! Hitting this illustrious mark will result in an install range that reads 1,000,000,000 - 705,032,704. Not only does tradition tell us that the larger number should come second, but that is an exceptionally specific amount.
Update [2/12]: It looks like the glitch is over with. Several people are reporting that downloads are working again and everything has returned to normal.
If you've been having trouble with 403 errors while attempting to download new or updated versions of apps from the Play Store, welcome to the club. Reports have been popping up all over the Internet from people experiencing the same issue. Unlike the infamous Package File Invalid Error, the glitch appears to be persistent, preventing any and all downloads from starting.
The Google Cast SDK is only just escaping its confines as a developer preview, so it’s not surprising to see a few bugs turning up in some odd places. A couple of simple, but potentially telling glitches started appearing after Google Play Services 4.2 began rolling out a few days ago. This latest update is causing the list of Cast targets to fill with incompatible DLNA-enabled devices and duplicate Chromecasts.
This contest is now over.
The final results are listed below. If you've won, you will be contacted in the near future. Congratulations!
Any decent bank heist movie always has one common hurdle for the would-be thieves: a regularly changing access code to the vault, and only one person knows what it is.
You remember Everything.me, right? About a year ago it popped up in the Play Store as a homescreen replacement built around search. It aimed to deliver a smarter, context-based experience by generating suggestions using automatically generated themes and suggestions for apps and websites. The project even drew the attention of Mozilla and ultimately became the interface of Firefox OS. Today, Everything.me leaves beta and changes its name ever so slightly to EverythingMe.
Wi-Fi is a staple among most smartphone users. While we tend to talk more about cellular data, it's really just there to sustain us as we travel from one access point to another. We aren't just demanding more data at higher speeds, we're connecting more devices than ever before. The inevitable overcrowding of the 2.4 GHz brought about the expansion into the 5 GHz range. Unfortunately, many Nexus devices (and at least a few others) are having trouble making and maintaining connections to this higher frequency band.
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.