H2O Mobile and data services: the Profile is not backed up, needs separate restore

A few months ago I discovered that I could enable cellular data on the kid’s iPhones, powered by $40/year H2O wireless [1] …

Gordon's Tech: ptel Real Paygo vs. H2O with data

… H2O now allows data use for iPhones [1]. I believe this is new, I learned of it via chat support as a last step check prior to migrating our daughter to Ptel [2]. The data service requires installing a new carrier profile from an ominous looking and quite mysterious web site: http://www.locusapi.com/pcs/apn.php…

Today I learned that the profile isn’t part of an iOS backup. When I switched my daughter’s iPhone H2O wireless cellular data stopped working.  Reinstalling the profile fixed the problem.

[1] $10 every 3 months covers all the text/voice the boys need. My daughter needs about $80 a year, still very cheap. We enable cellular data for Maps, Messaging, email, calendar and a few other low bandwidth services.

OS X - moving files between users on one machine - how Apple expected this to work (13 years later)

I think my first version of OS X was 10.1 - “Puma” - probably in the fall of 2001, at the dawn of the Forever War. I certainly remember Jaguar.

OS X had roots in BSD Unix, so it was naturally multi-user with UNIX style permissions from the start. The multi-user bit has worked well, the permissions bit not quite so well. Windows style permissions have always been less troublesome than Mac/Unix permissions.

Maybe that’s why it has taken me 13 years to figure out how to share files between users without having to geek-out and explicitly change permissions (which is what I’d always done). Note that I have always kept a single admin user account separate form the accounts I and other family members use and my personal account is non-admin (which partly breaks Google software btw, Google expects Mac users to be admins) [2].

It goes like this:

1. Ted logs into Ted account.
2. Ted creates a folder in /Users/Shared with files for Alice.
3. Alice logs into Alice account.
4. Alice copies folder from /Users/Shared to Alice Desktop.

This is what’s happening to permissions…

1. The folder in Shared, and all files in that folder, are Read & Write for Ted, Read only for everyone else.
2. After the copy operation, the folder and files on Alice’s desktop is Read & Write for Alice, Read only for “everyone” [1].

Note Alice can’t delete the folder in /Shared, only Ted or an Admin can do that. (Since most Mac users run as Admin they don’t know this.)

 

There you go, it’s documented at last. Not that many people will ever need to know! Most Mac geeks run as admin, so they can probably work with the Shared folder directly.  Or, more often, they just use Google Drive or Dropbox to share files [3]. Non-geeks don’t even see the Shared folder — Apple has deprecated its use in Mountain Lion and later; Apple expects file share to be mediated by iCloud rather than a local file system.

- fn -

[1] Except for OS X veterans who have been infected by Apple’s “fetching forever” viral bug. We get someone else called “Fetching” with Read Only access.

[2] This has worked well for me, and I like the extra security layer it provides. It’s also a quick test of cruddy software — if the app won’t run well without admin privileges it’s a shoddy app. Google’s software is the annoying exception - a shoddy bit of Mac software I use anyway.

[3] We are a Google Apps centric family, so we share with Google Drive.

Troubleshooting iTunes misbehavior - move the library

I’ve had an outbreak of iTunes and iOS sync misbehavior lately. I’m not the only one.

While I wait for Apple to fix their bugs [1] I figured I’d try a refresh of my iTunes Library. It’s unlikely to hurt, and I have abundant backups. [2]

It’s a very old trick — so old I’d all but forgotten it. You just move your iTunes Media folder (advanced prefs, organize, etc). I’ve done this a few times over the past 10-12 years and it’s generally worked well. It’s really a copy, not a move, so if everything is fine you can delete your old files [3]. You need a lot of disk space of course, but external drives are cheap these days.

During the move it’s a good idea to turn off backup, especially Time Machine. Otherwise you’ll run into drive churn slowdowns. Just be sure to create a reminder to turn backup on again the next morning. (On my system this takes hours to complete, so I run it overnight.)

I figure if there are any file or database corruption problems this might clear them up. At least it ensures that everything has been touched by the current (icky) version of iTunes and all files have been freshly written to disk.

- fn -

[1] Given all of Apple’s recent software quality problems, I sometimes wonder about industrial sabotage.

[2] I’m at the point where I’m looking for hardware issues. One trick is to switch to WiFi sync — eliminates issues with USB cables, USB hub, USB ports, etc.

[3] I like to rename the original folder and let it sit for a few weeks. I create a reminder to delete it then.

Update 12/6/14

The library move seemed to go as smoothly as ever. Subsequent syncs were quick and trouble free, but only time will tell if anything has truly improved.

One theory on what is so screwed up with iOS 8.1.x and iTunes 12 synchronization

This comment on a thread about the hot mess that is iTunes 12 / iOS 8.1.x sync fits my theory…

Revisiting iTunes/iOS sync issues | The Robservatory: "incomplete syncs due to bad disk sectors in just a couple of songs (apparently when it hit the bad sectors it quit entirely–and silently–rather than moving on to the next song)"

My theory is that there have always been bugs and problems with iTunes sync, but when an error occurred iTunes moved to the next operation. It didn’t quit or hang. It also didn’t log anything useful to Console.

Now iTunes still doesn’t log anything useful to Console, but it doesn’t continue. It just quits the sync operation (might move to next one).

I hate you Apple.

Aperture Tips: Work around for lack of multiple windows - "Recent Items" filter on Library

One of my biggest Aperture frustrations is the inability to open multiple Projects or Album windows and drag and drop files between them. You can drag images from a Project or Album to another, but finding targets amidst hundreds (thousands) of albums and targets is very hard.

The “Favorites” and “Recent Items” filters in Library search can help:

Right click on an Album/Project to make it a Favorite. Anything you touch/view is “Recent”. Between Favorite and Recent filters it’s much easier to navigate between Projects or Albums in a large image repository.

See also:

• Gordon's Tech: Aperture Tips: Introduction to a series of posts

Bloggers label (category) feeds (and Yahoo Pipes is still around)

I decided today to start writing more about ways to use Apple’s defunct Aperture photo management app. I’ll be using it for years while I wait for Photos.app to mature, and I know it’s not going to change much.

Writing that post I wondered again if Blogger supported feeds on tags (“Labels”). I thought they did; sure enough I wrote about this feature four years ago…

Gordon's Tech: Using Bloggers undocumented label (category) feeds and Yahoo Pipes to create a tech opinion feed out of Gordon's Notes

… To start with, here's the label for "technology"

http://notes.kateva.org/search/label/technology

and here's the feed (Atom) following the above pattern

http://notes.kateva.org/feeds/posts/default/-/technology

The only new development in the past four years is that this is now an official feature. Unfortunately the Feeds still don’t get a useful name.

I wrote about Yahoo Pipes in the same blog post; Pipes was the IFTTT of its day (but far more ambitious). Turns out Pipes is still around; things that are useful but abandoned tend to be stable and cheap to maintain (last Twitter post was 7/2013 though — I wouldn’t build a mission critical operation on Pipes).

Aperture Tips: Introduction to a series of posts

As we all know Aperture has been “sunset”. We think that sometime in 2015 Apple will “ship” something called Photos.app for OS X. It will be a partial regression from iPhoto; it may have some interesting new features.

Assuming Apple gets its decrepit application software division into working order we might get a viable Aperture 3.5x replacement based on an advanced version of Photos.app  sometime in 2018 [1]. We don’t know if Apple will continue to ship Digital RAW compatibility Updates, but we received a Mavericks update just two weeks ago. It’s not inconceivable that Apple will provide Aperture 3.5 compatible RAW updates through 2016. (Aperture is still being sold, and even Apple is likely to provide updates for 1-2 years following end of sale.)

Since there’s no exit from Aperture (or iPhoto) [3] this means I’m expecting to use Aperture for another 4 years. During that time I’ll be still be learning new techniques and workarounds; Aperture is an awesomely power application [2], even if it is now years behind the cutting edge of image processing. In the worst case scenario I’ll buy Lightroom for RAW image development then drop output files into Aperture [4].

I don’t expect Aperture books and web sites to last long though, so I’m planning to put together my own series of tips and tricks based on what I read elsewhere on the web and on a book I’ve just bought. I’ll be going the archives of some old Aperture blogs like:

• The Aperture Blog
• The Photos Expert (formerly ApertureExpert) - it does have feeds, it’s only feed discovery that’s inexplicably broken [5]
• Apple - Aperture - Resources still around
• Aperture 3: The Digital Story

The tips will show up in the Aperture Tag, you can even use a label feed: http://tech.kateva.org/feeds/posts/default/-/Aperture.

- fn -

[1] Based on how long it took Apple to produce a healthy version of Aperture in the first place.

[2] And it’s no longer terribly buggy. The main Aperture bug I run into now is the dangerous Empty Project / Empty Album bug. It’s not that frequent, but  beware deleting Projects that show no images!

[3] Strong data lock. Migration to Lightroom was once laughable, but see Aperture Exporter.

[4] Remember JPEG 2000? Or Windows Media Photo / HD Photo / JPEG XR? DNG (TIFF+XMP metadata)? I might go for DNG assuming I can make Lightroom output TIFF DMG per Aperture’s expectations. Good reference here, note the LOC and several other institutions favor JPEG 2000.

[5] I missed the transition to the new blog! I have to add the current one to Feedbin.

See also

• Aperture Exporter: impressive toolset to facilitate migration or save archive creation. Option to create XMPP side cards for JPEG.
• Gordon’s Tech: Dealing with Time Zones in Aperture across multiple cameras - what I do for now 5/2014
• Gordon’s Notes: Apple kills yet another photo sharing service - and generally screws up iOS photo management 9/2014. Amazing.