As Cameron explained in his latest "What We Use" entry, technology can change a lot in just one year. Around this time last year, I was running with a 2012 Nexus 7, a Galaxy Tab 10.1, and an Evo LTE. All of those devices have changed since then, as have my favorite apps and other gadgets. The family of devices I use has grown and evolved significantly since last October, so I thought it may be fun to detail just what I use to get through a normal day.
Every version of Android has launched with at least one headlining feature. As any true fan would know, the 4.2 camera brought with it a very cool new mode called Photospheres. While the initial hype has dropped off, the popularity of photospheres still continues to grow, thanks in part to improvements in image quality and the addition of a Maps-based community designated for sharing the immersive images. We don't always want a location attached to our regular pictures, but it's pretty rare when we don't want our photospheres to be geotagged.
This edition focuses only on new games. The app roundup is coming up soon.
Looking for the previous roundup editions?
My first Android phone was the original Motorola Droid. The day it was released I happened to walk into Verizon to get an issue with my bill cleared up; I had been following the Droid leaks for some weeks before, so I was really excited to check it out in person. I walked in, picked it up (along with the Droid Eris), and played with it for a few minutes before explaining to the salesperson what Android was.
It has only been a couple of weeks since I wrote about the troubles with multi-touch (well, touch in general) on the 2013 Nexus 7. At the time, Paul Wilcox of Google's Product Support forum stated that the issue was being examined, and about a week later he confirmed that the JSS15Q update addressed the problem. While many people are reporting that the OTA has completely cleared up any touchscreen glitches that had been present, some people haven't seen any improvements, and still others are complaining that the problem has grown significantly worse.
Earlier today, Google released a relatively minor update to its keyboard application with only one really useful change: numbers in the top row on tablets. While the update itself is indeed not too significant, it did manage to bring several interesting half-baked under-the-hood bits which aren't quite ready for consumption. These are exactly the kinds of bits we like here in the AndroidPolice teardown kitchen.
Armed with some of Ron's initial findings, my teardown partner Santiago Rosales and I dug into the innards of the v1.1 APK.
The Google Search 2.7 APK teardown is now officially the longest one in the history of Android Police. We find a bunch of interesting things, post about them, continue digging, and what do you know - keep running into new stuff. I'm fairly positive there won't be part 4 this time around, as we've squeezed out every last drop from v2.7, but as they say - never say never.
If you haven't read the first two parts yet, you should do so now to cover the bases.
This is the app roundup. The game roundup from this week can be found here.
Just when you thought we were done with the already rather extensive Google Search teardown, another wild teardown appears. Yup, still the same good old Search 2.7, but this time, we found a hidden feature that you will really want, even more than custom hotwords. At least I think you will.
Turns out, there's a secret flag within Search that lets you use the hotword, set by default to 'Google,' anywhere in search results instead of just the home Activity.
Losing the cellular connection on your phone, even briefly, can be a potentially serious issue. It might come at the moment you need to call for emergency services, or when somebody is trying to call you. Today, we're going to talk about a pair of issues on the Nexus 4 that can send it into radio silence for as little as a few seconds, or as long as it takes for you to notice it.