Nexus 4 update: a little more life with Lollipop

One of the key reasons why I bought my Nexus 4 a little over two years ago was knowing that I wouldn’t have to wait for Google’s software updates. And then I waited weeks to install Google’s Android 5.0 Lollipop update after its first appearance on my phone in late November–the slight risk of the update bricking my phone was not something I wished to run during the combined insanity of the holidays and CES.

Nexus 4 with LollipopI should have waited longer. That 5.0 release and the subsequent 5.0.1 update exhibited a freakish and annoying bug: I could hear the other person in a phone call, but they couldn’t hear me.

The workaround suggested in a reddit thread about changing a developer-level setting made the problem go away most of the time, and it’s yet to resurface in Android 5.1. But I’m still completely puzzled as to how a flaw this widespread could have escaped QA testing

I don’t regret installing this update overall, though–not least since Google does appear to have fixed the problem it created.

The best feature so far has been battery life that seems notably longer than under Android 4.4. And seeing a current estimate of how many more hours the phone’s good for–combined with having its Battery Saver option prolong its runtime for a good hour or so–leaves me feeling a little more in control of this Nexus 4’s useful time away from a charger.

After that I’d rank the updated Quick Settings panel you access by swiping down from the top of the screen. This puts my phone’s hotspot feature one tap away–before, it was multiple levels deep in the Settings app–and finally adds the flashlight feature that previously required adding somebody else’s app.

Android Lollipop Quick SettingsThe rest of the Material Design interface Google made so much of a big deal about at last year’s I/O developer conference hasn’t made as much of a difference as I expected. I’ve quickly gotten used to the idea that different apps will turn the menu bar different colors–except when some of these hues get a little too close to Battery Saver’s bright orange.

And I feel like I can zip through open apps much faster in Lollipop’s recent-apps list, or at least I do since telling Android to show Chrome only once in this list instead of including a preview of every page open in that browser.

I wish I could be more enthusiastic about Smart Lock, the option to bypass the lock screen based on your phone’s proximity to a trusted component of one sort or another. But so far, I’ve only set it to trust my desktop computer via Bluetooth–and because that iMac can be iffy about connecting automatically to the phone, I can’t count on this working.

I should explore the other unlock options available. For instance, I happen to have a spare NFC tag or two around that I could stick in our car’s dashboard for an automatic unlock when I tap the phone to it. But haven’t gotten around to that yet.

The important bit about this update is this: Lollipop has breathed a little more life into a two-year-old phone. And that, in turn, means I don’t yet have to choose between continuing with the Nexus line in the form of the unacceptably huge Nexus 6 or going with another Android phone or even (it could happen…) switching to an iPhone.

All of my aging gadgets

As I’ve been plugging away at my taxes this year, one thing’s become blindingly clear: I’m not doing my share to prop up the electronics industry. My Schedule C will show only one gadget purchase for all of 2014, a $35 Google Chromecast.

Old laptop and phoneEvery other device I use for work is older, sometimes a lot older. I have my reasons for not upgrading, and some of them may even be valid… while others probably just testify to my own persnicketiness.

 

The oldest one of the bunch is my late-2009 iMac. I really should replace it–trying to edit a RAW image file taken with a friend’s camera made it painfully apparent how its processor has aged.

But buying a new iMac or Mac mini would require me to get an external optical drive, as if it’s 1997 all over again. (Doing without is not an option: Have you seen the lifespan of a DVD in the hands of a toddler?) One thing’s for sure: Whenever I do purchase a new Mac, there’s almost no chance I’ll pay Apple’s elevated price for an external DVD burner.

My 2011 ThinkPad X120E has not held its value nearly as well–the AMD processor inside was never that fast to begin with, and these days I only run it to test things in Windows 8. What I should do is replace it with a convertible laptop like one of Lenovo’s Yoga series–that’s a kind of device I can’t buy from Apple at any price. Maybe once Windows 10 ships?

The 2012 MacBook Air I’m typing this on shows its age on the outside–I’ve let this laptop pick up so many scuff marks that it’s unclear whether I even deserve a MacBook. But while its battery life has faded a little bit, it remains a great travel companion overall. I suspect I’ll wait to upgrade this one until I can get a new model with that charges via USB-C.

The upgrade calculus is simplest with my first-generation iPad mini. When I can buy a replacement that has not just the Touch ID sensor of the latest iPad mini but the better camera of the current full-sized iPad (or something close to it) and, ideally, a default storage allocation bigger than 16 gigabytes–boom, I’ll be throwing down my credit card.

 

On the other hand, I’m seriously anxious about how I’m going to replace my Nexus 4. This phone has aged remarkably well, not least since Android 5.0 Lollipop seems to have stretched out its battery life (I’ll write more on that separately). And I’ve somehow only dropped it onto an unyielding surface once, with the damage confined to a small crack on the back that I fixed in place with a bead of Krazy Glue.

But the Nexus 4’s camera remains mediocre in most situations, and the phone doesn’t have enough storage. Unfortunately, I can’t replace it with a newer Nexus model–the Nexus 6 is almost offensively enormous if you value one-handed use. So are most of the other high-end Android phones. If I shattered the screen on my generally-beloved phone tomorrow, I guess I’d buy the second-generation Moto X… which itself no longer ranks as new.

Finally, there’s my Canon 330 HS camera. I bought that bargain-priced model because the Wirecutter liked it at the time–and because the larger-sensor point-and-shoot models I initially coveted all required trade-offs. As far as I know, that’s still the case with the two leading candidates: Sony’s pricey RX100, now in its third generation, still can’t geotag photos from Sony’s smartphone app, and Canon’s S120 and newer G7X can’t take panoramic photos.

Now that I’ve described my intentional technological backwardness at length, I’m sure some of you would like to explain why I’m mistaken or which new gadgets I should be considering instead of the potential upgrades I listed above. Please have at it in the comments.

T-Mobile’s free 2G international roaming is not bad at all

BARCELONA–I did something weird when I got off the plane in Brussels Sunday morning after a horrendously-delayed flight out of Dulles: I took the phone out of airplane mode.

T-Mobile 2G roaming

My usual routine on a trip to Europe has been to limp along on WiFi until I can buy a prepaid SIM (which hopefully will work right away but doesn’t always). But after switching my T-Mobile service from an old small-business plan to a slightly more expensive Simple Choice plan with free 2G roaming, I didn’t have to put up with that workaround.

What I didn’t know before this trip here for Mobile World Congress is if I could stand to spend that much time on an EDGE or slower connection. The limits of T-Mobile’s network in rural areas give me that experience more often than I’d like, and it’s not fun.

But when the alternative is either WiFi alone or having to find a store selling prepaid SIMs–sadly, the one in the arrivals area of Barcelona’s airport seemed to have closed when I arrived Sunday afternoon–slow but free can be not bad.

T-Mobile 2G roaming speed testBy “slow” I’m talking a connection that the Speedtest app clocked going no faster than .13 Mbps on a download, .24 on an upload. That’s nowhere near fast enough for sustained use or for work–Monday, I switched to faster bandwidth.

But in the meantime, that EDGE service provided sufficient bandwidth for my e-mail to arrive in the background, to read and write tweets (and even share a picture on Twitter, slowly), to get directions on Google Maps, to check up on Facebook and check in on Foursquare Swarm, and to browse mobile-optimized Web sites with a certain degree of patience.

I’m not alone in that judgment: Ars Technica’s Peter Bright mentioned to me on Monday that he was relying on T-Mobile 2G roaming, and avgeek blogger Seth Miller wrote in 2013 that this free roaming could very well be good enough for short visits.

And even if you’ll still buy a prepaid SIM at your first opportunity overseas, there’s a lot to be said for getting off the plane and not having to freak out over what it will cost you to exit airplane mode before that point.

Correlation or causation: Verizon, LastPass and last weekend’s USAT column

The reaction to last weekend’s USA Today column has been interesting and a little confusing.

LastPass logoOn one hand, I’ve seen a variety of reader reports–more in reader e-mail and in comments on the post I wrote here first to see if this was a wider problem as well as on the Facebook page post in which I shared the column than in comments on the column itself–of other Verizon login failures.

On the other hand, Verizon is now thinking that this is related to my using LastPass. My PR contact there said that one of his colleagues had noticed the screenshot in my post here revealed that I use that password-manager service and suggested I try disabling its extension in the problematic copy of Safari.

I thought that a somewhat ridiculous suggestion, since each time I’d typed in the password instead of letting LastPass enter it for me. But once I did that, I could log in normally. And when I enabled it again, I got the same login failure as before. There’s correlation here. Causation? I don’t know.

I e-mailed LastPass’s CEO Joe Siegrist (not because I thought this a CEO-level issue, but because we met a few years ago and I’ve always found him quick to reply to a query) to ask his people to look into things.

If they can reproduce and, better yet, document a problematic interaction, that would be good to know and a good thing to add to the column. If they can’t (a distinct possibility considering that the guy I quoted in the column having a similar problem, PhoneScoop editor Rich Brome, told me he doesn’t use LastPass), the mystery will continue.

In the meantime, I’ll throw this question out there: If you use LastPass, have you seen any other cases of a login with a valid password failing?

The fable of the one-handed phablet

For most of the last three years, I have been fighting a battle against “phablets” and losing it badly. Not only have people flocked to buy supersized phones after each negative review I hand down, the dimensions of these displays have steadily crept up.

Phone size inflationThe 5.3-inch screen of the first Samsung Galaxy Note, the one that I mocked at the time for its enormousness, now ranks as just a bit over medium-sized. And that 2012-vintage hardware seems positively compact next to the 5.5-in. LCD of the iPhone 6 Plus, the 5.7-in. screen of the Galaxy Note 4 and the 5.96-in. display on Google’s upcoming Nexus 6.

Minimum sizes have gone up too. The 4.7-in. touchscreen on my Nexus 4 once seemed quite the expanse of glass but is now approaching minimum-viable-product material.

All along, my core complaint against enormophones hasn’t changed: How do you use these things single-handed? Here are some common situations where it’s difficult or impossible to wield a phone with both hands:

  • Holding a shopping basket at a store
  • Pushing a stroller
  • Wheeling your luggage through an airport
  • Standing in a train or bus and holding on to a handrail or stanchion
  • Eating a slice of pizza or other no-utensils-needed food
  • Standing in a coffee shop, bar or restaurant with a beverage in one hand
  • Holding your child’s hand
  • Walking a pet

And no, wearing a smartwatch doesn’t help unless you’re willing to annoy everybody around you by issuing voice commands to your computer of a chronograph.

But with millions of people choosing to pay what’s often a non-trivial price premium for plus-sized phones, I have to allow for me being the person who doesn’t get it.

So I’ll ask this: If you have a phone with screen that exceeds five inches across, how do you work its touchscreen when you don’t have both hands free? Has the act of tilting the phone in your hand to let your thumb reach a corner become so natural that you no longer notice, do you put down or let go whatever has your other hand occupied, or is there some other trick I’ve been missing?

An individual customer rep is not a reliable source

Twice in the past few weeks, I’ve gotten into debates with readers about whether an option I’ve written about exists. Each time, my source has been a company PR contact, against which the reader has cited a sales or support representative who told them otherwise.

Verizon support chatThe first case came up in my Wirecutter guide to wireless carriers (updated today for the iPhone 6!) when I warned readers that Verizon’s otherwise appealing “Single Line Smartphone” plans exclude tethering.

I noted that I’d seen Verizon reps say otherwise (as in the screenshot here), but that I’d gotten the official word from a Verizon spokeswoman and the @VzWSupport Twitter account.

Then I had a commenter on the story report that two different reps had said  tethering was included. Even though that would make zero business sense for VzW–why offer a plan with the same features as one that costs $30 extra?

Next came last weekend’s USA Today column about buying an unlocked iPhone 6. In it, I cited reports from iPhone 6 purchasers and a confirmation from an Apple publicist as proof that the “no-contract” T-Mobile iPhone 6 for sale at Apple’s site is unlocked and can be used with any carrier.

Big surprise: I’ve since had readers saying Apple and T-Mobile reps told them that this phone is locked to T-Mobile. One particularly anxious shopper wrote that he’d gotten that answer from nine different people at Apple and T-Mobile.

Look: I am not the biggest fan of Apple PR, but they have been honest when I ask a yes-or-no question about an Apple product such as “is this phone unlocked?” (That’s going back many years; the staffer who gave me this answer is somebody I’ve dealt with since at least 2008.) Remember, too, that you’ve got firsthand reports from iPhone customers, including several who commented on the USAT piece.

(T-Mobile’s @TMobileHelp Twitter account did chime in, but its reply only mentions the carrier’s own warranty and “premium handset protection”–neither of which should concern you if you’ll use another carrier–and doesn’t actually say the phone sold by Apple comes locked. Apple said nothing in response because it’s apparently allergic to social-media conversations.)

Meanwhile, customer-service and support reps get the story wrong all the time. They think an old policy still applies, they try to make the customer happy, their boss told them something else, they just guess. This happens so often in travel that FlyerTalkers have an acronym for their preferred workaround for getting reps to do something allowed by policy: HUACA, short for “hang up and call again.”

None of this back-and-forth is necessary when companies post the correct answer on their sites. But I shouldn’t complain too much; their failure to do so opens an information inefficiency that I can exploit for profit… and subsequent reader e-mails explaining how they know I got it wrong.