It’s become quite customary for Google to release updated Android Platform Stats at the start of every month. These figures show the latest state of fragmentation in the Android ecosystem–valuable information for developers looking to better target their application development efforts.
When we last left off one month ago, we were pleased to note some rather significant progress in the right direction. Android 4.4.x KitKat was up to 13.6% from 8.5% the month before, resulting in a 60% relative growth. This figure kept pace with the 60% relative growth over the month before. Unfortunately, Android 2.x was still hanging around at 15.7% . . . READ ON »
If by now you haven’t already heard of XDA Senior Recognized Developer rovo89‘s fantastic Xposed Framework–well, maybe you’re in the wrong place. But for those of us who are well acquainted with this incredibly versatile and powerful tool, there’s only one question: When Xposed will gain support for ART runtime, and by proxy, Android L.
Two weeks ago when we first learned that the L release would be the first version of Android to remove all traces of Dalvik and make ART the default runtime compiler, many in the comments were quick to complain about how this would “be . . . READ ON »
During the Google I/O 2014 opening keynote, we caught our first glimpses of the radically different Android L. And when Google made an early developer preview available, many end users went ahead and installed L on their own devices. Unfortunately though, intrepid users were quick to find that the developer preview didn’t feature all of the UI goodies that we saw in the Android Design Guidelines and event keynote.
While part of the disconnect between expected and actualized features is due to the incomplete nature of the developer preview, an even larger part boils down to the lack of application support for . . . READ ON »
Android OEM customizations like Samsung TouchWiz and HTC Sense are undoubtedly a love-it-or-hate-it affair. There are certainly users out there who care for the added features that these skins introduce. But on the other side of the coin, there are more than a fair share of users who despise the aesthetic nightmares found in some skins. What’s more, this extensive customization often (but not always) results in Android firmware update delays—and that’s if the bloated firmware doesn’t prevent updates in the first place. Oh, and let’s not forget about how these customizations result in a greater number of security vulnerabilities. . . READ ON »
It’s now been several hours since the release of the Android L Developer Preview Images. Undoubtedly, many of you reading this have already loaded the preview firmware onto your Nexus 5 or Nexus 7 (2013). However, not everyone is lucky enough to own one of these devices–and even if you have an N5 or N7 by your side, you may not be willing to wipe your data in order to flash test images.
In the time since release, we’ve been poking and prodding at the Android L Developer Preview firmware on a Nexus 5 to see how far Google has come with L and where there’s still . . . READ ON »
The first day of Google I/O 2014 has come and gone, and just as we were expecting, Google used the opening keynote to shed some light on the future of Android, Chrome, Android Wear, Android Auto, Android TV, Google Cloud Platform, and Google Play. While the keynote was available for live stream viewing from the comfort of your own home, we’ve boiled down the nearly three hour keynote to its most important highlights for those who lack the time to watch the entire presentation.
Like I/O events of yore, yesterday’s keynote began by discussing the momentum seen in Android. As expected, . . . READ ON »
With the curtain raised on Android L at Google I/O, we thought it was a good time to take a look at what we know about Android L, given the significant user interface changes we are all expecting and have seen. Without further ado, let’s take a look at what changes in Android L that we have uncovered by digging in the updated Android design documentation.
First up, it seems there’s a new style of notification bar in Android L. The new icons seem more rounded and fluid, as opposed to the current ones with delineated . . . READ ON »
We all knew it was coming, and now it’s finally here. Android “L” was officially unveiled earlier today during the first half of the Google I/O 2014 opening keynote. As expected, L packs quite a long list of both user-facing and developer-centric features.
In a surprise turn of events, Google has decided to make the developer preview images of Android “L” available for the Nexus 5 and 7 tomorrow morning. Join us as we take a closer look at what makes L important.
Google I/O 2014 is a mere 35 hours away, and many of us are hoping for the release of the next major version of Android, thus far only known as “L.” Whether or not Android “L” makes its appearance at I/O, we already know quite a bit about it.
At this point, we have a few relatively concrete details about the upcoming Android “L” release. We know that Dalvik will soon be shown the door in favor of ART, and we know that quite a bit of emphasis has been placed in the 64-bit codebase. And through rumors detailing the new Quantum Paper . . . READ ON »
For some time now, we’ve heard rumors suggesting that Amazon was planning on releasing an Android-based smartphone. After many months of rumors, leaks, and hints, we finally have Amazon’s entry into the smartphone world. Earlier today, Amazon officially unveiled the Amazon Fire Phone, which will make its way to consumer hands on July 25, starting at $199 on-contract.
From the outset, Amazon worked hard to differentiate the Fire Phone from the sea of other Android smartphones. It hopes to accomplish this goal with the help of a number of innovative technologies including Dynamic Perspective, Firefly technology, Mayday, and Amazon Prime integration.
Through the . . . READ ON »
If you’ve ever tried to modify and reinstall a system application, you probably encountered application signature checks in one form or another. Either you removed the original app before proceeding, or you gave your modified APK another package name in order to get it to install without first removing the old application. And in either case, you also had to re-sign the application yourself in order to get it to install in the first place.
You can get around all of these behaviors by temporarily disabling application signature checks. But before we get into the metaphorical meat and potatoes of this article and tell you how . . . READ ON »
A few days ago, I wrote an article here discussing some changes in Google Play Store permissions handling, and how these changes may have adverse privacy risks for users. The comments on that article indicated an overwhelming amount of concern from readers as to the permissions being used by applications, with many looking to use App Ops or XPrivacy to protect themselves.
Today, I’m going to take a slight detour and look at the permissions needed by two popular apps: Google’s first party keyboard, and SwiftKey. Both of these are keyboard applications, and both are available for download for free on the Play Store . . . READ ON »
After yesterday’s article about Google’s recent changes to the Play Store that post a number of privacy concerns for users, today we are going to look at the three most popular options for users to protect their own privacy on their Android devices. First though, let’s take a look at how they work, and what they are for.
Since the start, Android has had a permissions system, to allow users to control what apps are able to do on their device. When an application is installed, the user is prompted to agree to the permissions that an app requires. The . . . READ ON »