In a post to its official blog that's sure to excite users across the globe, Google has just announced that Voice Search is now available in thirteen new languages. The list of newly included languages, which range from Basque to Swedish, brings the total number of supported tongues up to 42.
In the post, Product Manager Bertrand Damiba explains just what it takes to add a new language to Voice Search – first and foremost, Google must collect "hundreds of thousands of utterances" from volunteers to bring speech recognition up to par.
TeamViewer, the company behind a widely popular collaboration/remote support software solution, has brought to market a new app specifically aimed at Samsung devices, releasing QuickSupport to Google's Play Store today.
The app is essentially a remote control app meant just for Samsung devices – it allows access to Samsung mobile devices from Mac, Linux, or Windows computers running TeamViewer's software. While TeamViewer already has an Android app, this is the first app under the TV name allowing control of a mobile device from a computer and not vice versa.
The Nexus Q, unveiled at this year's I/O conference to a somewhat unsure audience, is a device that looks to unify your living room's media experience, allowing the streaming of all your Play Store content to connected speakers and TVs, while also allowing for remote control from your (or your friends') Android devices.
One of the Nexus Q's main claims to fame is that it allows anyone in the room to connect and share Play Store content quickly and easily.
With everyone anticipating the introduction of fabled CM10 builds, the CyanogenMod team is still hard at work bringing official CM9 support to even more devices. The latest additions to the list are the Galaxy Tab 2 7.0 (p3100, 3110, and 3113) and Tab 2 10.1 (p5100, 5110, 5113), each with their own nightlies ready for download and flashing.
It's worth noting, of course, that since these devices are just receiving their first nightlies, you may run into a bug here or there.
OK, OK, that's actually Linus Torvalds expressing his feelings about NVIDIA, but there's no better way to articulate the continued frustration with the complete lack of Sprint Galaxy Nexus support in AOSP. Verizon is [almost] there. Sprint, however, is not. Try finding it (hint: its codename is toroplus) - specifically, the CDMA/LTE binaries.
If you still have doubts about the above notion so eloquently conveyed by Linus' gesture, Jean-Baptiste Queru's comment confirms:
As far as toroplus, the situation is unchanged: there are no plans to support it as a target device for custom AOSP builds.
It means that ROMs that are built from AOSP, like CyanogenMod, can now start integrating the Jelly Bean code and release the first true JB nightlies. Not broken ports from the Galaxy Nexus builds - real ROMs.
In a post to the Android Building group earlier today, Jean-Baptiste Queru announced that Samsung's Nexus S 4G has officially and fully been brought into the AOSP fold. The device is now fully supported by AOSP, meaning its CDMA – and WiMax – binaries can now be "properly" distributed. Here's the full text of the announcement:
We've been able to resolve the issues around Nexus S 4G, and we can now properly distribute its CDMA and WiMAX binaries.
In a post on their blog, the company has explained that devices which have been certified to run Flash will still continue to do so, and updates will be made available just for those devices. Any devices that have not been certified to run Flash will be unable to install or update it from the Play Store from August 15th.
VLC is one of those tools that's in every geek's toolbox. The video player that supports every video format known to man still doesn't have an official, finished Android version, though. In the meantime, however, developer cvpcs, has done us all the courtesy of setting up an hourly build server for the alpha of VLC for Android.
The builds come in both NEON and non-NEON flavors. So, folks with older phones, or devices with the Tegra 2, for example, should probably download the non-NEON version.
After the long-awaited launch of Google Drive, it was only a matter of time before users began seeing integration with Android apps. While there's no official Android API for Google Drive just yet, many devs suspected that Drive's Java API would work just fine, despite a confusing statement on Google's developer site:
Warning: Apps will not have any API access to files unless the app has been installed in Chrome Web Store.