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.

“Damn you OS X autocorrect,” corporate-brands edition

I know, I know: Making fun of autocorrect fails is not new. But the automatic spelling correction in OS X is something else, courtesy of its apparent inability to figure out that my starting a word with a capital letter suggests I might be typing a proper name–say, a reasonably well-known online brand’s name–and that a little more deference would therefore be in order.

OS X autocorrect preferenceYou can argue that autocorrecting “Glympse” to “Glimpse” is fair game. But what about the following replacements I’ve seen OS X make?

“Etsy” to “Easy”

“Roku” to “Rook”

“Waze” to “Was”

“Ooma” to “Roma”

Meanwhile, it took a long time for Apple’s desktop operating system to stop auto-correcting Dulles Airport’s “IAD” code to “iAd,” as in the advertisement-serving system in iOS.

People’s names are, of course, just as much fair game to OS X’s autocorrect. When I was live-tweeting the Federal Communications Commission’s net-neutrality vote, OS X kept trying to change FCC commissioner Mignon Clyburn’s last name to “Cleburne.” Perhaps it has an undocumented fetish for that Texas town of 29,377.

I have to ask: Isn’t this the sort of bossy intrusiveness that an earlier Apple justifiably mocked during Microsoft Word’s Clippy era? And then I must wonder: Why haven’t I shut off autocorrect already–in System Preferences’ Keyboard category, click “Text” and uncheck the “Correct spelling automatically” box–instead of whining about it yet again?

Smartwatch withdrawal

For the first time since last summer, I’m about to depart for a trip without including a smartwatch and its charger in my luggage: I returned the Moto 360 and Samsung Gear Live I’ve been trying out to Google PR on Wednesday.

The 360’s face picks up a lot of glare.(I took advantage of having to go to NYC for the day to hand-deliver those Android Wear watches and a few other loaner devices to a Google publicist–less because of the money I’d save on FedEx, more because I wouldn’t have to find a box and enough bubble wrap for all of these things.)

I don’t miss having to charge a smartwatch–always with a proprietary adapter that’s easy to misplace, not easy to replace–every day. But I do miss the soothing sense that if something important happens in my digital life, a device on my wrist will tell me about it and relieve me of the need to grab my phone.

Somebody used the phrase “digital triage” to describe that aspect of smartwatch usage, and that sounds about right: Unlike a beep or a buzz from a phone, the name and subject of an e-mail flashed across a watch’s face tell you instantly if the message is something that demands quick attention or can wait.

That use case seems as compelling to me as it did after two months of trying the Gear Live–maybe more so after I realize how often I was checking my phone during a dinner Thursday night. Fortunately, I was with other tech types, so I’m sure my fellow diners weren’t offended. Much.

And, sure, I once again have to reach for my phone to tell the time.

This trip will take me to Barcelona for Mobile World Congress, where I expect to see a new crop of smartwatches–Apple’s excluded, as that company doesn’t show off its products at other people’s events.

Some of them should be thinner and lighter and run longer on a charge than the Motorola and Samsung watches. Some may do away with the need for a proprietary charger, either by accepting a standard micro-USB charger or using wireless charging. Some may even look sharp enough to wear with a suit. With each of those advances, the odds of me buying one of these things will tick forward another notch.

4/8/2015: fixed a broken link

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?

Tales from the software-CD crypt

Wednesday’s “worst version of Windows” column for Yahoo Tech was a fun stumble down memory lane, and not just because it allowed me to re-read reviews of Windows Me and Windows XP: I also got to dig out some of my semi-treasured collection of software CDs.

Old and obscure software CDsI started collecting them once I had a desk of my own at the Post, and these things soon became a core part of my cubicle decor there. Beyond the Windows CDs you saw in the photo atop that column, I have:

  • a BeOS CD that I then tried out on my Mac clone and thought was a revelation compared to the Mac OS of 1997;
  • a CD for the Snap online service CNet launched with EarthLink in 1997, and which I’m sure nobody else remembers today;
  • a system CD from the Power Mac Cube I reviewed for the Post;
  • a rectangular CD for Windows Media Player 7 that was supposed to portray that awful music app’s interface, and which would be unusable on any computer with a slot-loading optical drive;
  • a CD of Insignia Software’s SoftWindows, an emulation app that shipped for the first Power Macs.

These obscurities don’t function as any sort of decor now that they’re stashed in an interoffice envelope. But they do help remind me of where the industry’s come (remember when the only way the Mac was going to survive is if you could run Windows programs miserably slowly on it?) and of reviews that I perhaps could have done better.

And they’re also a type of keepsake that’s been rendered obsolete by the online delivery of almost all software. What am I going to do, take a screengrab of the .zip file that contained my beta download of Windows 10?

Mac settings changes you might miss going from Snow Leopard to Yosemite

One of the major Christmas presents at my in-laws was a shiny new 13-inch MacBook Air that replaced a 2010-vintage MacBook–which meant that one of my major presents was getting apps, data and settings transferred from the old Mac to the new one, then completing the rest of the setup.

Old MacBook and new MacBookThe first hiccups came in OS X’s Migration Assistant: It estimated the data transfusion would take five-plus hours over the home WiFi. But neither machine saw the other over a faster Ethernet link (using a USB-to-Ethernet adapter on the Air), and an ad hoc, computer-to-computer WiFi network didn’t work until I resorted to the un-Mac-like workaround of turning on Internet sharing on the source laptop.

Then I realized the work Migration Assistant had left for me: configuring parts of OS X Mavericks (preloaded on the new MacBook) and Yosemite (promptly installed as a free update) that had no equivalent in the old MacBook’s Snow Leopard, then changing OS X settings that would confuse anybody used to that five-year-old operating system.

Atop the first category: the social-media integration Apple began adding to OS X in 2012’s Mountain Lion release. My in-laws aren’t on Twitter and don’t spend much time in Facebook–but that integration’s ability to share a photo to Facebook from the Finder does address a pain point I’d heard from them.

An Apple ID is far more important in Yosemite than in Snow Leopard, courtesy of so many updates running through the Mac App Store. So I had to verify that hitherto-dusty account worked and had current billing info, without which we couldn’t download the free Yosemite update.

Migration Assistant had siphoned over a few long-ignored PowerPC applications that OS X hasn’t been able to run since 2011’s disappointing Lion, so I had to delete those myself.

OS X Yosemite General system prefsI thought I was done at that point, and then I heard my father-in-law complaining about not being able to scroll. He had bumped into Apple’s foolish decision to make scroll bars invisible until you mouse over them or use a two-finger gesture to move up or down the page. I hadn’t thought to fix that setting (open System Preferences and click “General”) because I’d fixed it on my own Mac after maybe two hours with Lion. Oops.

The last round of settings to change were in the minds of Yosemite users who had been used to Snow Leopard. From that perspective, the Notifications icon at the top-right corner of the screen means nothing (and requires tweaking to avoid info pollution), while Launchpad’s rocketship Dock icon doesn’t exactly shout that you no longer need click around the Finder to run apps that aren’t already in the Dock.

I’ve spent a decent amount of time walking my wife’s folks through those angles, but I suspect I’ll be getting questions about the new computer for months to come. See also: “the gift that keeps on giving.”

Apple Mail malaise (update)

There’s no program on my Mac that’s annoyed me more over the last year than Mail. Which is funny, because for years I held up that program as an example of Apple working to fix customers’ problems while Microsoft let Outlook Express decay.

Apple Mail about boxBut sometime during the development of OS X Mavericks, Mail went off the rails. It shipped with a bug that made syncing with a Gmail account awkward to implausible. Apple fixed that within weeks, but other problems lingered through many or all of its updates to Mavericks:

  • Searching for old messages was intolerably slow, to the point where it would be faster to grab my iPad, log into the relevant account and start the search… after first running up and down the stairs to find that tablet.
  • Switching back to Mail from other apps would leave the insertion point randomly shifted to a point months or years in the past–which, to be fair, is great for cheap nostalgia.
  • Some mailboxes would be shown sorted by subject instead of date, never mind that sorting by subject is a total waste of time unless a mail client can’t handle search (ahem).
  • More recently, Mail began forgetting the custom app passwords Google generates for mail clients and other apps that can’t process its two-step verification codes.

Apple’s updates fixed some of these issues before OS X Yosemite. I don’t think I’ve seen a mailbox randomly sorted by subject in months, and I haven’t had to open Keychain Access to copy a saved Google app password back into Mail since last month.

Yosemite, to judge from its performance on my MacBook Air, has also returned search in Mail to a state of good repair. I can only hope Apple keeps working on these other issues. Because between Web-mail’s issues with offline access and working with other apps and the lack of a compelling alternative client (understandable, given how many people rely on Web-mail or don’t spend as much time in a mail client as me), firing this app just doesn’t seem too practical.

And at least the prominent mentions of Mail in Apple’s product page for Yosemite suggests the company realizes it can’t leave this app in maintenance mode. If only I could say the same for iPhoto…