Since the OTAs for KRT16S started rolling out in the middle of last week, some Nexus 4 owners updating from Jelly Bean are experiencing really troubling behavior after installing the new version. There are reports of issues with core interface functionality like a non-working Home button, Quick Settings toggle, a broken dialer, and various other issues. Not all affected devices have had exactly the same results, and many weren't hit, but some unusual complications have definitely started turning up.
In the haze of excitement over getting the latest and greatest from Android, sometimes we forget that some people actually depend on their phones and tablets for work. Within the professional world, mobile access to email tends to be vital. For better or worse, an overwhelming number of businesses and organizations rely on servers running Microsoft Exchange (or other software implementing the protocol) to handle their email and calendar needs. Unfortunately, a minefield of bugs in KitKat's Exchange support are leaving many stranded without access to their employer's servers.
Sometimes relatively insignificant software bugs come together in what can only be described as a perfect storm, wreaking havoc and leaving the victims without recourse. Only a few days after the KitKat announcement, complaints of some rather odd behavior on Nexus devices (mostly Nexus 4s) running Android 4.3 started popping up around XDA, the Google Product Forum, and the AOSP Issue Tracker. People were waking up to find alarms failing to go off and most of their apps crashing instantly.
If you've recently updated your Nexus device from Jelly Bean to KitKat, there's a chance you're already being notified of an OTA update to KRT16S. If you're wondering what's changed, the collected list of source commits has been posted by Al Sutton. Most of the tweaks are pretty minor, including an improvement to the backup service, a few updated APNs for assorted carriers, and code to handle rare issues with the 3G Nexus 7 (2012) radio.
Last time I checked, most phones couldn't make it through a long weekend without a little time tethered to an outlet. If you find your gadget batteries regularly hitting the red, or just simply dying, it might be time to invest in a battery pack. Newegg might have the perfect solution for anybody in need of some extra juice when they're out and about, the RAVPower 10,000mAh Power Bank. It's on sale today for just $24.99 with free shipping.
Earlier today, a post on the Chrome Releases blog announced Chrome 31 is moving from beta to the stable. The update is coming in with a number of exciting features, including: printing from Chrome on devices with KitKat, support for requestAutocomplete to auto-fill payment details with online stores, 'Add to home screen' for web apps, and more.
If you've been following along with the beta channel, you're probably already familiar with a few of these changes.
Google Now is pretty amazing, and it just keeps getting better as Google finds new ways to expose knowledge from its massive data repository. It's hard not to become addicted to everything that Now can offer. But what if you just got your hands on Google's latest flagship phone, went through the setup process, and then discovered Google Now doesn't work? Not only have some Nexus 5 owners had this experience, a few of them have even seen Google Now stop working across all of their other devices.
By now you've probably heard about ART and how it will improve the speed and performance of Android, but how does it actually perform today? The new Android Runtime promises to cut out a substantial amount of overhead by losing the baggage imposed by Dalvik, which sounds great, but it's still far from mature and hasn't been seriously optimized yet. I took to running a battery of benchmarks against it to find out if the new runtime could really deliver on these high expectations.
Did you know it's possible to unlock your Nexus 5 bootloader without wiping user data? If your device has already been rooted and relocked for optimal security, then unlocking is just a button tap away thanks to the latest update to BootUnlocker. Support for Google's latest flagship phone was just added with an update to version 1.4 of the app from XDA member segv11. Sadly, both generations of the Nexus 7 from ASUS remain unsupported.
It's fair to say that Android went through some chaotic years in the beginning. The pace of development was frantic as the operating system grew at an unprecedented rate. An as-yet undetermined future led to decisions that were made to conform to existing hardware and architectures, the available development tools, and the basic need to ship working code on tight deadlines. Now that the OS has matured, the Android team has been giving more attention to some of the components that haven't aged quite as well.