Over the last few years, few topics have been more hotly contested by Android users and developers than how SD cards are handled by the OS. Back in February, I discussed some of Google's changes during the transition from Android 2.3 to 4.0, and then how more recent policy changes ultimately led to 3rd-party applications losing most of their access to removable storage. By the time I/O came around, Google acknowledged that KitKat's newly added Storage Access Framework still didn't offer enough range for apps to get their work done.
Early yesterday, Google began pushing the complete source code for Android 5.0 Lollipop to AOSP. The code drop was so large that the operation continued to run through the night and into the following day. But, it is finally done. For those that are determined to compile their own build of Android, it's a good time to get your downloads started. However, for the rest of us that are just interested in a more detailed list of changes than what Google has already shown to us, we can turn to the developer changelog generated by Al Sutton of Funky Android.
No release of Android feels complete until it's sitting in AOSP. The time has come and Google is now uploading Lollipop to the Android Open Source Project. That's every line of code, every resource, and every config file – the result of a year of work by Google's crack team of developers. Given the likely size of this release and everything we've seen in the past, this code dump could take several hours to complete.
When it came time to think about writing a “What We Use” post last year, I was still somewhat new to the AP team and I had just learned that I was about to be the new Teardown guy, so I took a pass on attempting to compile my entire toolset in a single article. I can’t say that I’m any more prepared to do one this year, but I couldn’t resist joining in on the fun.
When the 4.4W.2 firmware version began rolling out a few days ago, it became possible to swipe down on the top-most card to show an unobstructed view of your favorite watch face. This still left Wear with the irksome tendency to put a card preview back on top when a new notification came in. Not only did the W.2 update give us the ability to hide that card, but there's also an option to keep new cards from getting in the way.
Have you felt the call of video game development? Maybe you've seen some game featured in the news and thought, "That sucks, I can do way better." Well, put your money where your mouth is and prove it. StackSocial is giving customers the opportunity to name their own price and pick up two courses offered by Udemy on the topics of game development and design, or pick up two additional courses by beating the average price.
Developers have a lot to look forward to with the latest release of Android, but not everything requires Lollipop to run. With the official release of the SDK for API Level 21, Google also included an updated version of the AppCompat Support Library, which contains back-ported versions of UI controls and other features for use on older versions of the OS. Some of the new libraries were first available with the L Preview SDK, but just about everything has received an update, and there are some additions for the official release.
Google is pretty well known for building a fast and (usually) reliable infrastructure that can stand up to just about anything short a certain Nexus launch. This is why it came as no surprise when the tech giant announced its own cloud hosting service during I/O 2012, giving developers a path to tap into some of that power. Since the launch, Google has attempted to make its Cloud Platform product as appealing as possible, but the response has been fairly tepid.
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.