“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?

A broken MacBook power adapter and crowdsourced charging

I spent my last two days and change at SXSW without a working power adapter for my MacBook Air, and remaining productive on my laptop was far easier than I could have imagined.

Frayed MacBook Air chargerThe insulation around the cable on my 2012 model’s MagSafe 2 charger had started fraying just off the power brick months ago. Sometime Sunday afternoon I realized that the wiring underneath had become entirely exposed, and the thing would only charge if it fell away from the brick at the right angle. By that night, it wouldn’t charge at all.

It’s a testament to the enormous popularity of Apple hardware that keeping my laptop charged over the next few days was so little trouble. It was nothing at all like the horrendous experience I had after forgetting to pack the charger for a Dell laptop on my way to CES 2007, when compatible power bricks for this model were a lot harder to find than Dell’s popularity at the time would have suggested.

Instead, my biggest hangup was properly spacing out my “hey, can I borrow your charger” requests so each of my SXSW pals with a MacBook Air wouldn’t feel too put upon. The closest I came to genuine inconvenience was when my Yahoo Tech colleague Jason Gilbert and I, sitting side by side with depleted laptops, had to take turns with his power adapter: We’d plug in one MacBook, charge it long enough to get its battery gauge out of the red, then plug in the other.

It also helps that laptop battery life has advanced enormously since 2007: Even after two and a half years of charge cycles, my MacBook can still last for four hours, then retain most of its remaining charge while asleep.

I didn’t even bother going to the Apple Store in Austin, far north of downtown, or looking up other computer stores downtown. I saved that errand for when I got home, when I paid $83.74 with tax for a replacement charger. Oof.

I’m not a fan of the minimalist, mono-port design of Apple’s new MacBook, but at least its use of the compact and crafty USB-C standard for charging means its users won’t have to pay those kinds of monopoly prices if they wind up in my situation.

In the meantime: Is there anything I could have done to the charger before it failed completely? The guy at the Apple Store who sold me the replacement said he sees plenty of charger cables shrouded with electrical tape, and it appears that I could have patched the cord with sugru–but of course I had neither of those things handy when the charger still worked, sort of. Sigh.

Things I would like Apple to fix in OS X (please?)

There’s been a minor surplus of blog posts over the last month or so expressing concern about the state of Apple’s software quality. See, for example, this inventory of issues from my friend Glenn Fleishman, Craig Hockenberry’s open letter to Apple CEO Tim Cook, or the Marco Arment post that got spun completely out of proportion.

Apple logo on iMacI can’t speak to all of the faults people have mentioned; without an iPhone, for example, I don’t see many of the OS X-to-iOS problems folks have been griping about. And I can’t say that this period marks a low in Apple’s software quality: OS X Lion got on my nerves much more than Yosemite has. But look: Yosemite exhibits some baffling and annoying defects that I’d like to see fixed as much as anybody else. Here’s a short list:

AirDrop: This has accomplished the singular feat of making Bluetooth file transfer look elegant and reliable. Because one of my two Macs is a pre-2012 model, I have to tell the MacBook Air to “Search for an Older Mac” for that iMac to get a chance to show up at all. And the advertised ability of AirDrop to send files between OS X and iOS has so far been a bust–and, courtesy of Apple kneecapping Bluetooth in iOS, Bluetooth file transfer isn’t available as a fall-back option.

Mail’s time travel: A round of bug fixes have made Mail much less of a disaster, but the bizarre bug that causes Mail to jump back randomly by months, years or all the way to the oldest messages in a folder when I select it remains intact. Why, Mail, why must you feel compelled to remind me of what people wrote in 2011?

non-transparent volume overlaySemi-transparent toolbars and sidebars: Having Safari’s toolbar turn red when I scroll down a CNet story is one of the dumbest features I’ve seen out of Cupertino. I advised turning that off in my USA Today column but have since reluctantly turned it back on: I couldn’t stand how that change not only rendered the volume overlay opaque but added crude black borders at its rounded corners.

Arrogant autocorrect: The automatic spelling correction in Yosemite seems much more out of control than in prior OS X releases, especially when it interferes with my attempts to write proper names and other capitalized words that a sane autocorrect would know to leave alone.

Non-noteworthy Calendar events: I love how I can mouse over a date or time in an e-mail and have OS X offer to create a new event in the Calendar app based on that information. But at some point (maybe pre-Yosemite?), the events created that way lost an editable Notes field: That part of the event-info window is now locked to a “Show in Mail…” link that opens the message from which you created the event. I can work around this problem by editing the event in Google Calendar, but something tells me that’s Apple’s desired outcome.

Safari tabs with escape velocity: Every now and then, I find that I have somehow launched one of the tabs open in Safari into a new window. I don’t know what the exact sequence of clicks is (it’s not mentioned in Apple’s list of shortcuts) but I would like the browser to not do that.

I’m sure there are other Yosemite issues that have been bugging me, but I can’t think of them at the moment. Remind me in the comments?

How a hidden OS X process made my old employer think my Mac had been hacked

A slow Monday that I’d hoped would ease my way back into a semi-normal workweek was interrupted by a note from an old Post colleague–specifically, somebody in the IT department–with the never-good subject line of “virus?”

The security guys are reporting that someone is attempting to logon to VPN with your old credentials.

I replied saying that it was probably something spurious unless it was coming from the IP address my home currently had assigned from Verizon. He wrote back to say “turns out that IP is what is pinging the VPN server.”

Well, crap.

Little Snitch network monitorI updated my Mac’s ClamXav malware-scanner for the first time in months and got it started on a tedious inspection of my Mac, then downloaded the trial version of a network monitor called Little Snitch.

The virus scan found nothing, and Little Snitch didn’t report any oddball apps trying to send out data either. I also checked the settings of apps that I’d once configured to log into the newsroom remotely, but found nothing there.

Then I thought to try searching for the Post VPN address in Little Snitch’s network monitor. That revealed that Safari–to be exact, its WebProcess component–had pinged it only a few hours ago. A search for that address in Safari’s bookmarks and history located an old bookmark for the site that I’d misplaced in an unrelated, rarely-opened folder. Since deleting that, Little Snitch hasn’t recorded any more access attempts, and I haven’t gotten any other reports of those from the Post’s IT people.

WebProcess itself seems remarkably undocumented on Apple’s customer and developer sites, aside from references to it by users in the company’s tech-support forums. A further inquiry confirmed my initial hunch that this process updates Safari’s “Top Sites” view of pages you’ve visited recently–how else will the browser know to provide current previews of them?

What I still don’t get is why WebProcess would have kept on checking a site I hadn’t visited in close to two years–and which I don’t remember seeing in Top Sites anytime since. But I’ve witnessed enough weird behavior lately from individual Apple apps that I can’t put this past Safari… which is to say, I hope that’s all this is and that I haven’t missed something else.

A CalendarAgent cure

A runaway, memory-eating process in Mac OS X Mountain Lion that I’ve whined about on Twitter and in last weekend’s USAToday.com column seems to have returned to sanity.

At first, this CalendarAgent program had been a mild-mannered citizen on both my MacBook Air and on my older iMac. But a day or two after Discovery News posted my generally positive review of Mountain Lion, the iMac started locking up as CalendarAgent devoured as much as three to four gigabytes until I force-quit it with OS X’s Activity Monitor app.

The problem went away long enough for a cautious endorsement of Activity Monitor in Sunday’s USAT piece, but then it resumed. After a few days of getting bored with killing off this process two or three times an hour, I was trying to remember how to yank its execute privileges when I thought to check the Console app.

The repeated errors listed in this troubleshooting tool indicated that CalendarAgent was choking on my wife’s shared Google Calendar feed. I’d subscribed to that in Lion’s iCal without any issues (parenthood requires a non-trivial coordination of schedules), but Mountain Lion apparently had other opinions. I deleted the subscription from ML’s Calendar app,  added it back in the BusySync software I use to publish my own set of calendars to Google, and was soon treated to the welcome and overdue sight of CalendarAgent’s memory allocation dropping back to normal levels.

I still don’t know what exactly went wrong on the iMac; the MacBook Air didn’t have this problem even after I subscribed directly to my wife’s schedule in its Calendar app. Adding it under the “delegation” option for the Google account I’d already configured in that copy of Mountain Lion–but which I hadn’t set up on the iMac–didn’t result in any memory leaks either.

But if you’re tired of seeing CalendarAgent hold up your Mac, try changing how Google calendars get to the computer. Instead of adding a direct .ics subscription via Calendar’s Edit menu, subscribe to that feed in your Google Calendar, add that Google account in System Preferences’ Mail, Contacts and Calendars pane and you should see the subscription when you click Calendar’s “Calendars” button look under “Delegates.” Or revert from the delegation approach to a direct subscription. Let me know if that yields any better results.

How Windows (may have) killed my laptop

Little-known fact about me: For the past two weeks or so, I haven’t been able to use the ThinkPad I bought last summer. Here’s what happened, in 10 painful steps.

1. Months after successfully installing the Customer Preview of Windows 8 in a separate partition of my  ThinkPad X120E (and somewhat regretting that it required me to wipe out Lenovo’s recovery partition), I finally got around to trying to install the Win 8 Release Preview Microsoft shipped at the end of May.   At the tail end of a seemingly-nominal installation, the Release Preview installer, it got stuck at the “Finalizing your settings” screen. After waiting a few hours, I forced the machine to shut down and got a prompt at startup saying that Windows would undo the RP installation and return me to CP.

2. Because I am an idiot, and because I was getting fed up with some networking problems in Win 8 CP, I decided I’d try installing Release Preview again the night before I was heading out to San Francisco to cover Google’s I/O conference. Once again, the installer couldn’t get past “Finalizing your settings”–which is a funny place for Win 8 RP to halt, since it doesn’t preserve any of your settings in the first place.

3. Because I’m an idiot, I then tried wiping the Win 8 partition and doing a clean installation. The results were much worse:

4. After yet another restart that night–which by now counted as “early morning,” I got as far as the setup screens where Windows 8 asks you to set a live.com user account. It said mine was already in use on the machine. Trying different usernames only resulted in yet another stall

5. With no Win 8 system available and less than six hours remaining before my 8 a.m. departure from National Airport, I gave up, reverted to Windows 7, and resented its slower performance all week long.

6. Back home, I took yet another stab at installing Win 8 RP in early July. I got the same failure: a bogus report that somebody else was trying to use my Windows Live account on the system. (By then, I had gotten a few sympathetic e-mails from a Microsoft publicist promising help from people on the Windows team, but I never got more than an initial, friendly “what can I do to help?” response from them.)

7. For reasons I don’t remember precisely, I elected to switch back to Windows 7, saw that the system had a round of updates to install, and thought I’d proceed with them. Bad idea: The installation failed, leaving the computer unbootable in two different versions of Windows.

8. Successive attempts to use the disk-repair tools in Windows 7 failed; a Lenovo troubleshooting utility came up, complained that it needed me to log in, and demanded a reboot with an “Okay” button. No, it’s not okay. The disk-repair tools on the Win 8 installer’s flash drive didn’t do any better.

9. Because I’m not a complete idiot, I had a complete drive-image backup of my pre-Win 8 system (plus incremental backups from mid-July). But I can’t recover it: The Win 8 installer flash drive said it couldn’t restore a 32-bit disk image–even though there’s nothing bit-specific about that job. (Sometimes I think the only way the 32- and 64-bit editions of Windows could get along worse is if Microsoft farmed out the development of each to the Israeli Defense Forces and the PLO.) Edit, 2:43 p.m. And as of this morning, booting up the laptop yields the results you see in the photo above.

10. A 32-bit version of the Windows 8 Release Preview installer then said it couldn’t restore an image from an earlier version of Windows. So now I need to generate a Windows recovery-tools flash drive from a 32-bit version of Windows 7. And thanks to Microsoft’s unwillingness to offer a download of that program, this job apparently either requires a machine with CD or DVD burner or a painful amount of monkeying around with DOS commands.

But things could be worse. Wired writer Mat Honan, one of the smarter observers of technology around and one of the more decent human beings on the Internet, had somebody break into his iCloud account and use its remote-wipe feature to nuke his MacBook Air, iPad and iPhone–while also laying waste to his Twitter and Google accounts. So I’m not going to whine too much about this self-inflicted wound. Besides, I can always install Linux on the machine.

Epilogue, 10/21: In case anybody was wondering how this turned out, I was able to generate a USB-based, 32-bit Windows 7 system-repair volume using Into Windows’ directions. My only hangups involved having to disable Parallels Desktop from sharing USB volumes with OS X, followed by the exceptionally long time it took to format this USB flash disk in NTFS from the command line. Things worked as advertised otherwise, and I once again have a working Windows laptop–ready for me to try out Windows 8 once again when it ships next week.

 

Steve Jobs storytelling and Apple history

I knew I would have to write an obituary for Steve Jobs someday. I didn’t think it would happen this soon–or that the subject would draw so much interest.

But it did, and it has.

I haven’t seen such a rush by people to document What They Felt since… okay, the tenth anniversary of 9/11 last month. But I understand where that comes from: When certain big things happen, if you don’t instinctively clutch for a keyboard or a notepad, you’re not much of a journalist.

So after learning the news–through a voicemail from a local TV producer who wanted to know if I could come on the Thursday morning show to talk about Jobs’ passing–I spent about two hours writing an appreciation of Jobs. Then I spent another two hours rewriting it. Something about an obituary does not tolerate factual errors or even merely inelegant writing.

Every other tech journalist seems to have done the same thing. A few shared stories of getting repeated phone calls from Jobs, sometimes even at their homes–or of visiting Jobs at his home–while others only connected with Jobs in brief interviews.

What’s surprised me since has been the expressions from individual users: the posts on Twitter, Facebook and Google+ (some from users who changed their avatars to Apple icons or pictures of Jobs); the “what Apple products I’ve owned” inventories (mine appears after the jump); the testimonials that have been piling up in front of Apple Stores. The photo at right shows the Clarendon location, where passerby have been leaving messages on Post-It notes (provided by the store, I think). One of my favorites reads “Thanks for ignoring the focus groups”; another simply has the word “Sleep” inside a rounded rectangle, as if it were a button in an OS X dialog box.

It’s all a reminder: These things with screens and buttons aren’t just tools we use and then set aside. They change us. They are part of our culture.

Today’s commemorations of Steve Jobs remind me of another, less pleasant reality: The price of being around at a time when you can meet the inventors of the technologies that changed your world is eventually having to say goodbye to them. There will be other farewells like this, I hope not too soon.

Continue reading