Google just published a major update to the Play Store Developer Content Policy, and whether you're a user or developer, you need to be aware of these changes. The content policy is basically Google's "this is what we don't allow on the Play Store" list. As such, you can understand why it's important. Google periodically updates this policy, but this is the biggest change I think we've seen yet - tons of areas have been touched on and modified, and there are significant ramifications to these changes.
The Chrome team is pushing out an update to all the good little Chromecasts of the world. This one doesn't come with any changes to the UI or new features, but it does promise to improve the stability for Google Play Movies playback, and should make Chromecast devices discoverable on more networks. You won't need to do anything to get this installed on your end, the OTA will automatically download and install when it's your turn.
HTC Americas President Jason Mackenzie just tweeted the following.
Lots of questions re 4.3 release for One. We r wrking hard (needs cert) to release 4.3 across all US, Canada skus by end Sept. DNA as well.
— Jason Mackenzie (@JasonMacHTC) August 19, 2013
And there you have it. Just a day after 4.3 was promised for the developer edition HTC One by Mr. Mackenzie, he's clarified that statement to include all US and Canadian Ones (and the Verizon DROID DNA) with a deadline before the end of September.
Update: The Nexus 7 2013 build (codename "Flo") has now been posted. It's the first official CM build for the new Nexus 7.
ROM addicts, the time has come. The CyanogenMod team has been working diligently on version 10.2 of the popular ROM family, the Android Jelly Bean 4.3 update. Tonight the first batch of nightlies are being posted to the download page, Get.CM. There are only a few devices with updated builds at the moment, but that should change as the night progresses.
Ready for some more Android Open Source Project woes? In addition to the Nexus 7 drama over AOSP builds in the last couple of weeks, it looks like there are some issues with the Nexus 10 as well. Don't worry, the Android 4.3 factory image for the N10 is sitting on the Google Developers page, proud and happy, but the binaries and drivers for some individual components on the tablet seem to be missing, most notably the graphics driver.
In the greater history of computer gaming, Linux is a relative newcomer, still missing out on quite a few AAA titles and only recently gaining access to Steam. While the library of games is growing for the open-sourced OS, the actual development process is still locked in to Windows. Most of the tools used for designing 3D models (e.g. Blender), landscapes, and other graphics have made the transition to Linux, but the primary coding tools are mysteriously absent.
A little bit of connecting the dots has revealed that Qualcomm is the reason behind the new Nexus 7's lack of factory image / driver binary support. This has long-time AOSP maintainer Jean-Baptiste Quéru pretty upset. Upset enough that he is "quitting AOSP."
It's not clear if this means JBQ is quitting his job at Google (though the fact that he even wrote this kind of suggests he may be quitting / has quit), or that he's moving to a different part of the company / Android group.
Update: Looks like we were right.
ROM developers and Android tinkering enthusiasts alike have probably noticed at this point that the new iteration of the Nexus 7, unveiled two weeks ago, does not yet have factory images or driver binaries posted on the appropriate Google Developers page. A similar issue plagued the Nexus 4 in its early days, though eventually images were posted. At the time, legal issues were speculated as a possible reason for the delay, and Android build maintainer JBQ - largely responsible for the images / binaries - said only this in response: "I can't comment."
With the new Nexus 7, JBQ has not outright said that legal problems with Qualcomm are preventing the factory images (and possibly the driver binaries) from being published, but a quick look at the relevant evidence makes it pretty duh-obvious that's what's going on.
Just like last year, the Google I/O app's source code has been released in an effort to get developers acquainted with Android best practices.
In a post to Google+ today, the Android Developers page outlined some of the things the source code has in store for those curious. Among them are techniques to implement responsive design across phones and tablets, use content providers and implicit intents in app navigation, using sync adapters to provide new content "in a battery-friendly way" and loads more.