Update: While the message sent out to developers may be new, as it turns out, the information is not. It repeats what Google said back when it announced the availability of the Android 5.0 SDK. Here's the relevant passage.
The final round of Developer Preview images released on Friday left a number of users without root access on their devices, but a lightning fast quick-fix by Chainfire had them back in business the following day. Yesterday, he took to Google+ with a follow-up of how it works and the issues that are making it more difficult to acquire root on the latest version of Android.
Due to increasingly effective security measures and stricter enforcement of SELinux, it seems that many, or possibly all of the available methods for initializing the SuperSU daemon at startup have been rendered ineffective.
On Wednesday, Google teased developers and enthusiasts by officially announcing Lollipop, but chose to delay the release of anything substantial for another two days. Well, we've waited for the obligatory 48 hours, and the SDK is finally available, just in time for the weekend. (Yay?) Developers can finally abandon the interim SDK and move on to the real thing. There's no more pretending 'L' counts as an API Level, Android 5.0 is officially numbered 21.
Developers won't have to put up with that junky "preview" SDK much longer. In just two days (October 17th) the final Android 5.0 SDK will be available for download in the SDK manager.
Back in June, Google announced Android was destined to gain 64-bit support in the coming L release. A few weeks later, Revision 10 of the Native Development Kit (NDK) was posted with support for the three 64-bit architectures that would be able to run the new version of Android: arm64-v8a, x86_64, and mips64. As we close in on the official release of Android L, Google has updated the NDK to revision 10b and added an emulator image developers can use to prepare their apps to run on devices built with Intel's 64-bit chips.
Fire OS is a solid operating system if all you need is the ability to consume Amazon content in various forms, but it just doesn't cut it for the nerdier stuff we pickier types get off on. In some ways, it's a shame, because Amazon puts out solid hardware at affordable prices. On the other hand, there's the option to wipe the slate clean, so to speak, and flash something more exciting onto the tablet.
Google will update developer distribution agreement for the Play Store today, and two significant changes are in store. First, developers of paid apps will now be required to respond to users contacting them within 3 days of receipt of the email. How strictly Google plans on enforcing this is unclear, but it's likely the ominous Google Play ban-hammer will be a motivating (read: intimidating) factor for developers here.
Google is set to institute a new policy in the Play Store, and it has some developers up in arms. A message in the developer console (seen below) has appeared asking developers to add a physical address to their account profile. For those offering paid apps and in-app purchases, this is mandatory as of September 30th. Failing to do so could result in Mountain View pulling the apps.
The monthly Android version distribution numbers are up for September on the Android Developers site, and things appear to be moving just the way you'd expect.
Month over month, we saw a 2.2% decline in share for Gingerbread, a drop of 1% for Ice Cream Sandwich, 1.4% for Jelly Bean 4.1, and small gains of 0.9% and 0.1% for Jelly Bean 4.2 and 4.3, respectively. KitKat was this month's biggest mover, adding 3.6% to its share of the pie, bringing it to 24.5% of all Android devices active in the last week.
Everyone else - keep participating and stay tuned to Android Police so that you don't miss our upcoming giveaway announcements.