Thursday, May 17, 2012

iOS Restore problems: App Sync failure and missing Google Contacts

Fresh off discovering iOS Restore problems with In-App purchases and video podcasts I was called in to help a friend transition from two 3GS to two 4S iPhones.

He had a different set of problems, some familiar, some weird, some new to me:

  • When restoring Mail, Calendar and Contacts from Google Active Sync, the best option is to delete the Google account and restart. I've run into this several times, and reentering a password on a restored Google Active Sync (Exchange) data set works about half the time.
  • He ran into a real mess with AppleID vs. me.com ID. I think he'd started out with one Apple ID (Store Preferences) on his iPhone, then switched to another. As a result he had apps on his iPhone that no longer matched his iPhone Apple Store ID. They'd run, but they wouldn't sync to the desktop or the Cloud. When we did a restore they were gone. There's no way around this; he either has to switch to his old ID (but it's lost) or repurchase the apps that were owned by the lost ID. Yech.
  • He and his wife share one instance of iTunes, but their apps have different Apple Store IDs. This can be done, but it requires a mixture of Cloud and iTunes sync. Double Yech.
  • To enable email delete on Gmail with Mail.app delete, we had to rediscover the insanely obscure m.google.com/sync setting that makes Gmail behave like a rational piece of software.

Those are the familiar bugs. Yes, Apple Store IDs and App DRM are a mess. Apple isn't a genius every day of the week.

The weird bug was, I think, a Google bug. After we reentered his Google credentials and synchronized, we found several missing entries in his Phone shortcuts. That's because the Contacts were missing. After a few cycles of removing/restoring Contacts Sync I could see the missing entries varied.

Turns out that Google was giving us exactly 100 out of 216 contacts; but the 100 varied. It seems Google was throttling the phone update.

Maybe if we'd waited a while we'd have gotten the rest. Instead I changed Sync from Push to Manual. Tried a few manual updates to no effect, then switched back to Push and we had all 216. A real pain, and I found zero hits on this problem. (Now there is one.)

The iOS user experience could use some work. In particular, the Backup story is pretty feeble.

Monday, May 14, 2012

Start Chrome using a specified "user profile".

I love Chrome's Multiple User feature - aka Identity Management in the G+/Facebook era.

 It's why I switched from Safari to Chrome on OS X. I have a profile for
  • My TrueSelf that only a few shall know.
  • John (Kateva) Gordon
  • My corporate self
I also have profiles I use when I'm assuming my children's identity (ex: Facebook monitoring). All the Profiles sync through Google Cloud including bookmarks, passwords, extensions and so on. So I use the same Profile everywhere.

Even in Darkness, Google does some things well.

I switch my three primary profiles all the time. That's how I know the great weakness of the current implementation. The Profile Google gives me is never the one I want. I frequently have to switch identities, which opens a new window, then hunt that window down ... Meanwhile, the original Window hangs on.

I want some shortcuts that will take me directly to the Profile I want. In both Windows (easily) and Mac (comand line), there are ways to do that as described in SuperUser and Quora:
This is top-secret stuff, these parameters don't show up on the most popular listing of Chrome command line options

The command line parameters are of the form:
  • chrome --profile-directory="Profile 1" -> Kateva
  • chrome --profile-directory="Profile 2" -> Corporate
  • chrome --profile-directory="Default" -> Personal
They match the directory names shown in (Win) C:\Users\[userid]\AppData\Local\Google\Chrome\User Data.

I've created a Windows shortcut for each Profile, now I have to give them unique icons.

Sunday, May 13, 2012

iOS Backup and the Cloud: Problems with Restore

After the 5.1.1 update my son's iPhone developed a crash habit. One photo in particular triggered an immediate restart on editing. Perhaps an iOS bug, maybe another problem. I did a full Restore, which means a backup then wipe then reinstall then restore. That didn't fix the bug, so we deleted the problem image.

That's not what I'm writing about though. During the Restore cycle we ran into some newer limitations with iOS backup. These included:

  • His Pocket God Comics, which are in-app purchases, were not backed up - contrary to Apple's iOS backup document. We were able to re-download them from within the Pocket God app; but that process appeared to rely on Pocket God and its Cloud servers.
  • His video podcasts vanished. We sync through iTunes though, not the Cloud, and they were still in iTunes and could be restored. Some of them aren't available from the Cloud any more.

I don't think there are any workarounds for these problems. Apple could fix this; in the Jobs era it's the kind of thing that tended to get his peripatetic attention. I doubt they will, but I'd be happy to be wrong.

My only recommendation is to distrust the Cloud, and avoid in-app purchases whenever possible. If you are using something that's Cloud dependent you don't own it -- and you don't even rent it. At best you have a fuzzy claim to occasional use that might be revoked at any time.

Saturday, May 12, 2012

Mac: how to make a server photo screen saver work

I wanted to share a common set of screen saver slide show images across 3 of our Macs. First I put them an old G5 with abundant storage. It seemed to work, but if there was any interruption of our wifi network other machines couldn't reconnect. (Disregard the marketing. Wifi is much slower and much less reliable than wired.)

So I put them on our Time Capsule NAS share. That worked, but if a client logged out or a machine restarted the share wasn't remounted.

Sigh. OS X Networking is reliably disappointing. I remember network shares being more reliable in 10.3, and that using a share shortcut mounted the share. Certainly shares worked better in MacOS Classic (albeit a lot more slowly).

What seems to help is mounting the share on startup by adding it to one or more user's login items. After this the screen saver image slide show survives a restart.

(There are ways to mount drives on boot for all users with vifs.app editing of etc/fstab, but it looks risky to me and I read reports of "finder problems".)

iOS In App Purchases - they're not backed up

I restored an iPhone from backup -- and discovered at least In-App Purchases don't restore automatically.

I'm now downloading the set from within the app.

It's a pain to do this across all "In App" purchases. I'm surprised there aren't more complaints about the in-app purchasing system; to me it's a big regression from the original App Store model.

Friday, May 11, 2012

Windows 7: Changing network location after initial connection

I have compared Lion to Vista, but that's really an overstatement. As bad as Lion is, it's better than Win 7 which is better than Vista.

Today's Win 7 problem has to do with Win 7's well intended network location security. When you first connect to a WiFi network Win 7 asks you to choose a network location. If you choose Public some network tools won't work -- including my corporate RSA IE toolbar.

After you connect, however, it's not obvious how to switch from Public to Work. The secret is to

  • Go to Control Panel:Network and Internet:Network and Sharing Center
  • Click on the hyperlink-like text that says "Public"
  • In the new window choose Work or other trusted network

Wednesday, May 09, 2012

Spammers have found a hole in Blogger's comment system

I'm used to getting comment spam with embedded links. Often the spam appears benign, but the links go to bad places.

This one was different however:
I agree. The organization and departments like FDA or BFAD should check the contents of these toothpaste products. This will ensure its safety to the people. Aside from that, other chemicals in the toothpaste formulation should also be checked. According to my dentist, Ron ******, some products may contain melamine which can cause severe damage to the brain. I hope that they will be able to resolve this kind of issue.
It sounds spammy, but it is somewhat related to my blog post and it didn't display with an inline link in Google's Comment review. It even linked to a Blogger profile.

So I approved it. Blogger emailed me a copy and then I saw it had a link. It was spam of course. (I think BFAD has something to do with "Black Friday" sales deals?)

The post was crafted so the link didn't display in the Blogger Comments review UI, but it did display once the post was approved. The senders even invested in a spambot (human or silicon).

Obviously a high class operation! I wonder how long it will take Google to close this loophole. In general their Blogger spam filtering is excellent; most spam isn't even presented to me for review.

Sunday, May 06, 2012

iPhoto to Aperture: Summary and managing the Event/Album problem

Apple's Aperture photo management software was a mistake.

I don't know what they were thinking, or where it came from. Obviously it was intended to be a "professional" alternative to iPhoto, but someone (Jobs?) never thought through how customers would move from one to the other. Migrating complex data between fundamentally dissimilar applications is an impossible problem.

Apple's customers wanted iPhoto Pro, instead we got Aperture 1.0.

Apple must know they made a bad mistake. Over the past three years they've been trying to turn iPhoto into Aperture-lite, and Aperture into iPhoto Pro. Despite the marketing claims, they're not there yet. They may never arrive -- it's almost impossible to change an application's fundamental behavior without producing a smoldering wreck.

Eight weeks after starting down this road I recommend waiting for Aperture 4...

iPhoto to Aperture: My experience: Apple Support Communities

... Several weeks ago I migrated three iPhoto Libraries from iPhoto 8 to Aperture 3.23. (In limited testing iPhoto 9 migration appeared to have similar results).  

.... if you are a demanding sort, wait for Aperture 4.1 and iPhoto 10.x.   My migration process was fraught with traps and errors that resulted in loss of 'metadata' (image descriptions, etc). Video migration was particularly problematic. I spent many, hours experimenting and testing. I had to repeat the imports several times to find the best path.

Some data loss cannot be avoided; Aperture does not store iPhoto Event or Album descriptions. Keyword consolidation is a tedious process.   At the end of the road Aperture gives me many new features, scalability, and a (relative) confidence that I'm committed to an application with a demanding and technical user base.  

On the other hand, I miss iPhoto's many clever features for managing Events/Rolls. Aperture is taking me back to the days of Albums...

It's too late for me though. I've paid the price and made the transition. 

Most of the transition that is. I'm still trying to work around edge issues. Consider the "Event" to "Project" migration.

The two concepts have quite a bit in common. Each photo belongs to exactly one "Event" (iPhoto) or Project (Aperture). Photos can be moved from one Event to another. By contrast, a single photo can appear in multiple Albums.

Even so, there are significant differences. Over the last few years Apple added a lot of clever workflow and UI affordances to Events. They became so easy to work with I came to use Events for many things I'd done with Albums. I went back in time and reworked older Events to fit the new model.

After the migration however, most of those conveniences are gone. Aperture "Projects" are only superficially "Event-like". They'e relatively awkward to work with. I'm back to using Albums again, and I'm looking for an AppleScript method to turn hundreds of Events into Albums.

I'm sure I'll work around a lot of the issues. I wish, however, that Apple had created a true iPhoto Pro rather than go down the Aperture road. I wonder if, in the Cook era, Apple will finally introduce iPhoto Pro, and quietly retire Aperture.

See also

Update: I did work around the issue -- in an illuminating way. In iPhoto Events and Albums live in separate UI views. In Aperture both can be contained in Folders. So I mix my Events and Albums now.

Thursday, May 03, 2012

MobileMe to iCloud - Is Apple getting nervous?

Apple's MobileMe service officially ends on June 30th, almost 8 weeks from now. When it ends we either need to go to iCloud or give up on easy address book synchronization across our iOS and OS X devices and user accounts. (I've already moved the kids over.)

I'm in no rush. iCloud/Mac requires Lion and Lion won't install on the older iMac the kids still use. Worse, I don't even like Lion on the machines it supports. Lion is a disappointment.

I'd prefer to stay with Snow Leopard until early 2013, then switch to Mountain Lion. Except, of course, Mountain Lion won't install on our MacBook.

Yech.

I suspect I'm not the only one who isn't in a rush. Apple seems worried. The last time I used the MobileMe web interface I ran into a fake-out splash screen that tried to convince me MobileMe was already gone (nice try Apple). Recently Apple sent me a free Snow Leopard DVD to reduce the cost of a Lion upgrade (the cost is irrelevant). Today Apple is telling me I can keep my email address even on machines that don't support Lion [1]. Meanwhile, Macintouch, an old-school Mac site, shares ideas  from MobileMe dead-enders and iCloud denialists.

The pushback is strong enough that hard core geeks are coming up with inventive ways to sync Snow Leopard Address Book and Calendar to iCloud [2].

One option, of course, is to go all in with Google. This was more appealing when Google was less evil than Facebook. Worse, it's not clear how well Snow Leopard Address Book did synchronizing with Google. Lion still supports this; I created an empty account and synchronized with Google. It ended up bringing over 598 cards from the group "My Contacts". (All Contact had 2091 members). I've no idea how reliable this is, but iOS synchronization with Google works quite well. So this might be an option for Lion machines, and non-Lion machines would use Gmail (which is evil now, but works well [3]).

Lastly there's Spanning Sync - an alternative Mac Address Book to Google Contacts option for those who want to abandon MobileMe for Google Apps. (It's an expensive option for a family however.)

Alas, these days I don't want to get closer to Google; I'm trying to move the other way.

So I'm stuck, waiting to see if anyone else comes up with something better. Maybe if I wait long enough Apple will make Mountain Lion run on my old MacBook.

[1] Sort of. Apple botched this half-measure, even by lowest of standards. There's no way to tell from Apple what this means.. What it really means is email and calendars currently in MobileMe will be accessible on iCloud via the web UI.Unofficially Snow Leopard Mail.app may also be able access this email via IMAP.

[2] I doubt this will work all that well; synchronization is hell even when it's supported.

[3] iCloud's web apps are better than MobileMe's -- but an earthworm could clear that bar. iCloud Contacts, for example, is even more awful than Lion Address Book.

Thursday, April 26, 2012

WordPress Import Blogger tool failure

A few months ago I was impressed by how well WordPress.com managed importing a copy of notes.kateva.org.

Today I tried an import from my Dreamhost [1] version of WordPress 3.3.2 using the "Import Blogger" tool. This time it failed; Google rejected the authentication request with a cryptic message:

The page you have requested cannot be displayed. Another site was requesting access to your Google Account, but sent a malformed request. Please contact the site that you were trying to use when you received this message to inform them of the error. A detailed error message follows:

The site "http://kateva.org" has not been registered.

I couldn't fine any fix for this, though I did come across many reports of the error with various half-fixes. I wonder if this is because both my Blogger blog and the WordPress blog are on kateva.org. Or perhaps this is another sign that WordPress is problematic; I think if I do move to WordPress I will pay for WordPress.com and the associated support.

[1] If you use the promo code of KATEVA you get $50 off the 1st year fee and I get an equal credit (50/50 split).

Tuesday, April 24, 2012

Google Drive: Google's 20% price hike

With the debut of Google Drive, Google has increased their storage plan costs:


My old plan cost me $20 a year for 80GB (without Google Drive). It's no longer offered, but I can continue with it if I wish.

The equivalent new plan would cost me $60 a year for 200GB (extra storage largely for Google Drive).

My per GB costs would therefore increase from 0.25$ to 0.30$; a 20% price hike. [1]

Curious. For now I'll stay with my old plan and the "free" 5GB of Google Drive storage.

[1] The numbers are better if you consider what I would actually use if I committed to Google Drive. I am using 20GB and thus paying $1/GB for storage I truly use. It may be that Google's prior prices were only profitable when most of the storage was not in use, which was likely given limited use options (primarily Picasa).

Wednesday, April 18, 2012

Apple fixed Message.app (iMessage) in iOS 5.1 -- and nobody noticed

I give Apple a lot of hurt, but here they fixed something big and nobody else seems to have noticed. Even better, by fixing it they put more hurt on a deserving AT&T.

A few months ago I wrote about iMessage use on an AT&T iPhone without a SIM card (iPod Touch mode) using .me accounts. Problem was Message/iMessage 5.0 wouldn't let me enter a .me account in the iMessage app, nor would it show .me email addresses. I could only iMessage my son from the Contact UI. From Message.app, since he's on H2O wireless rather than AT&T, I could only initiate a conversation using SMS (20 cents for me, 5 cents for him).

I'm still on iOS 5.0 on my phone [1], but my son is on 5.1. So I could see than on his phone I can enter email addresses (the keyboard has a '.' now) as well as choose a .me address -- all from the Message.app UI. I've now updated my phone to 5.1 and it works there too.

It's a significant enhancement, but I don't think anyone else noticed ...

[1] I was concerned it wouldn't work with MobileMe, and I've yet to switch to the inferior and problematic iCloud alternative.

Monday, April 09, 2012

The post-Flashback era: removing Java and Flash from OS X

Decades ago, my SE/30 caught a Mac Classic virus. There was a fine freeware antivirus app for the Mac then, maintained by an academic and Mac geek. I used that until OS X came along. After OS X there was no great need for antivirus software, and none worth using.

Alas, as had been long expected, those days are back. There is money to be made now preying on Mac users, and Windows 7 is not the soft target of XP or 95. All Mac geeks have been reviewing the two important articles on Flashback:

I've run the 'defaults read' test on the admin account on four machines:

  • defaults read /Applications/Safari.app/Contents/Info LSEnvironment
  • defaults read /Applications/Google\ Chrome.app/Contents/Info LSEnvironment
  • defaults read ~/.MacOSX/environment DYLD_INSERT_LIBRARIES

I suspect the last needs to be run on every user account, which is the sort of tedious job antiviral software was built for. So far I haven't found any problems.

I haven't put antiviral software on our Macs yet (OS 10.5, 10.6, 10.7) but i'm taking these measures:

  • Uninstall Flash Player and switch default browsers to Chrome (sandboxed Google-owned Flash)
  • Uninstall Adobe Acrobat (done long ago)
  • Never run as admin user (done long ago)
  • Disable Java on all Macs (Java Preferences - delete cache, uncheck JVM)
  • Don't install Microsoft Office

I'll move my two Mountain Lion capable machines to the new OS later this summer, and I'll be watching to see what happens with OS X antiviral software. My Win 7 experience with antiviral software means I'll think hard before I take that road.

Update: Flashback may be the worst virus-specific malware infection ever.

Sunday, April 08, 2012

AT&T's SMS spam - blocking the email route

I am sure AT&T is doing everything in its power to reduce the amount of spam that hits my text plan [2], even though they earn money from each spam [1]. They're just that kind of company.

As best I can tell there are three sources for the AT&T carried text spam I get. One source has an 8 digit number; I forward those to AT&T's spam service and, annoyingly, have to send a second text with the number retyped. I have no idea if this does anything, or if it even reverses AT&T's charge.

The second source has a "short code". AT&T says I'm to to reply "STOP" to these. I assume these are AT&T "approved" and are never classified as spam, even when they sell criminal scams.

The third source is via an email gateway to my "device default email address" of "your-10-digit-wireless-number@txt.att.net":

AT&T Wireless- Block spam text messages on your wireless phone

[To] Block all email messages sent to your device's default email address (i.e., your-10-digit-wireless-number@txt.att.net). Create an email alias for your phone in Messaging Preferences, then change the Mobile Number Control settings so that only those text messages addressed to your email alias will be delivered to your wireless device.

I had no idea that it was possible to send email to my SMS service -- we were never part of the SMS era. What a perfect scam setup.

Sounds like the "fix" is to create an SMS email address that is then kept secret. This isn't done through AT&T's usual mobile site, it's a separate service with its own password (max 8 character?!) and registration process: http://mymessages.wireless.att.com

I'll look at doing this for our phones.

[1] Thanks to iMessage, and H2O Wireless and old AT&T-locked iPhones for the kids, our family does very little SMS. So it's cheaper to pay 20 cents/text than to sign up for AT&T's desperately overpriced text plans.

[2] Obviously I'm joking. If AT&T were serious about blocking spam they'd let us block all short code text.

Update: I recommend this reference: http://www.howtogeek.com/howto/41123/how-do-you-block-annoying-text-message-sms-spam/. As I half-suspected, the STOP approach is not the best. I'm surprised to learn that as bad as AT&T is, everyone else is worse. Blocking email gateways also blocks many notification services (airlines, Google Calendar, etc) -- but I can live without those. Also Android phones have some pretty good SMS blocking methods, iPhones have none.

Update 2: Weird coincidence -- or not. NYT article on the topic today. They mention Cloudmark's emerging "7227" service, but nothing about providing options to block all short codes, or all email gateway spam, and nothing about the revenue carriers make from text spam. Sigh.

Update 4/9/12: I blocked all email text or multimedia messages and all MOBILENUMBER@txt.att.net and MOBILENUMBER@mms.att.net messages. There are also block and allow lists I might play with later, but for now I blocked everything. I didn't set up an alias.

Unfortunately (cough) AT&T doesn't implement similar blocking for SMS:

Text messages sent via email can also be blocked directly from your handset. When you receive an email that you wish to block, simply reply to the email with the word "block" in the body of your message. The sender's email address will be added to your Block List. Note: this does not apply for mobile-to-mobile text messages.

I suspect these blocks won't make much difference, but I'll see.

Update 4/13/12:

How to stop text spam: Why cellphone spam is on the rise and what you can do about it. - Slate Magazine

... they use customized computer programs to generate and send hundreds of messages in a matter of minutes, varying the wording, capitalization, and punctuation to evade the phone companies' rudimentary spam filters. And thanks to a fiendish device called a SIM box, the spammers can plug dozens, even hundreds, of SIM cards—each representing a different mobile phone number—into a single phone. By the time you’ve received a text and reported the number, there's a good chance it has been used hundreds of times and discarded...

... Blocking messages from the Internet is also unlikely to cut down on the volume of spam you receive. Sending texts from the Web used to be a popular method for mobile spammers, who could try endless random combinations of numbers in hopes of a few hits. But unlimited texting plans made that approach less attractive to spammers, who know that such messages can easily be blocked. Though it’s still worth doing, don’t expect a magic bullet...

... a third of all text messages in China today are spam...

... They knew unlimited texting plans were in the pipeline. They should’ve known that unlimited plans mean seemingly unlimited spam...

I think my son has been responding to some of these spams, that may explain the 200 texts he's received. The only solution seems to be to turn off SMS service altogether. Interesting observation that the spam deluge is a result of unlimited texting plans (free spam), and that China saw it first.

Saturday, March 31, 2012

iPhoto to Aperture migration: movie support is weak in Aperture, but missing thumbnails are no longer a problem

In the final stage of my iPhoto 8 to Aperture 3.23 migration I imported my a 62 GB iPhoto Library of about 18,629 "Photos", of which, by keyword, 259 were actually "Movie".

Yes - iPhotos support of Movies is half-hearted.

In iPhoto all but one of the 259 videos displayed with a preview image.

After the 8 hours of importing and processing were done I had a 66GB Aperture Library. The first thing I did was check the Movies.

This time there were 270; 259 with the keyword iPhoto Original and 11 with keyword iPhoto Edited. Aperture stacks them as it does photos (option-;).

Of the 270, 36 showed icons indicating they could not be played within Aperture -- though they could play in QuickTime. Another 43 could play in Aperture, but they had no thumbnail (black thumbnail). There didn't seem to be anything different about these movies. Another two had incomplete thumbnails.

There's nothing to be done about the unsupported video formats -- they area  good reminder that the 2010 video format situation is a bloodymess. I will put these on my list of videos to transcode to a modern format -- hopefully without too much quality loss. [1]

The missing thumbnails seemed likewise intractable. I couldn't find any web resources on fixing them. Aperture Help was more ... helpful. Turns out there's now a menu command to generate thumbnails (new in 3.x), that took care of the problem.

Alas, there's no fix for a much more severe problem. Aperture imports iPhoto image Titles and Descriptions, but not iPhoto Movie Titles and Descriptions. The Aperture "Captions" for these movies were empty.

[1] The more I learn about transcoding video, the more terrible it seems. To do it well seems to be dark magic involving several pre-compression processing steps. Maybe I'll transcode to Motion-JPEG and be done with it.

Update 4/2/2012: The Title and Captions for the movies appears to be tied to the "Version Name" bug that can affect importing of iPhoto Titles from images. When I set Version Master = Master Filename on iPhoto import I got Aperture.VersionName and Aperture.Caption values from iPhoto. I also noticed that the Built in "Videos" smart album doesn't show videos Aperture can't manage internally -- so it's misleading (another bug).

The unsupported video format may be from our Canon SD camera, and there are some odd bugs there too. I can open the unrecognized video in QuickTime, save it as .MOV (same data, only the metadata changes) and import it back in -- and now Aperture will recognize and play it. So the problem isn't a codec issues, it's packaging/metadata problem. During the export/import process The Version Name was lost (not to surprising), but in addition the prior version name was set to the Date Created (bizarre beyond words).

Update 4/3/2012: I'm still trying to understand what Aperture is doing with movies imported via browser vs via iPhoto Library import. I think both methods are unforgivably unreliable and buggy, but they have different bugs. I'm experimenting with combining both, then reviewing metadata in list view to decide which to keep.

I recommend using the list view and adjusting metadata to show file size, project name, file name, version name, caption, rating, date and so on. I discovered that several videos were tagged as "iPhoto Externally edited", but they were in reality JPEG thumbnails.

See also