Ruminations on the launch of the Google Galaxy Nexus

Posted on

Warning: the following is not even remotely entertaining.

I was very tempted to preorder the new Samsung/Google Galaxy Nexus smartphone. I managed to talk myself down from that very expensive precipice, but I did a fair amount of reading and thinking about it. Now that I’ve done all that thinking, I’ll put some of the product up here, just to pretend it wasn’t a total waste of time.

It’s natural to compare the new flagship Google phone with the latest iPhone, but when I came across a post casting the “launch” of the Galaxy Nexus (i.e. the first day’s sales at the first shop to have the GN available in the UK), as a pathetic failure (citing a lack of queues out the door), it (despite striking me as disingenuous) set me thinking.

If Google had intended the launch to really be an event, they’d have made sure there was stock in a lot of locations, that everybody knew where to go and when, and that it would be a fun place to be. As it was, one shop in London had the thing on the announced launch date, and it was difficult to have confidence that even that was going to happen, until it actually did.

I don’t think Google are really trying for blockbuster phone sales – not blockbuster Galaxy Nexus sales, in any case, not right out of the gate.

Apple offers a couple of options (colour and storage) on a standard device. If you want the latest phone running iOS, you know what to buy, and it’s the one phone Apple wants you to buy. Making an event of the launch is absolutely the right thing to do to help capitalize on the pent-up desire for a new iPhone, and to fuel continuing interest in Apple products.

The Android device market is different. There are multiple manufacturers, each with several devices aimed at different user niches. Here, it’s all about choice, and the latest and greatest is regularly knocked off its pedestal by a new, more powerful device.

Maximizing the number of users interfacing with the net via Android, regardless of whose hardware it’s on, prevents other software makers from getting a stranglehold on how content (and what content) is allowed to be consumed on mobile platforms, and using Android fosters a sense of allegiance to Google as a brand. Blowing away the other manufacturers’ Android market share with “THE Android phone” wouldn’t necessarily benefit Google .

In fact, huge initial sales of the Galaxy Nexus could be counterproductive. If masses of people had been inspired to line up and spend iPhone quantities of cash on the Galaxy Nexus on its release, many would now be wondering what life would have been like with an iPhone, while they wait for their favourite apps to all be compatible with ICS, and for Adobe Flash support, and for the volume bug to be sorted. While the volume problem may have been unanticipated, Google would have been perfectly well aware that a lot of software, including Flash, won’t be compatible with the new version of the OS at first.

The Galaxy Nexus is a publicity vehicle and reference device for the thing Google really wants people to care about: shiny new Android 4.0, “Ice Cream Sandwich” (ICS for short), the unification of Google’s phone and tablet operating systems (OS). Google wants the thing first in the hands of the technically-minded; specifically, early adopters who don’t hold a grudge over a few rough edges, and developers who will release apps for ICS.

These two (overlapping) groups will perform the two major services of squashing bugs that would leave a bad taste in the mouth (now there’s a metaphor) of a mainstream consumer, and of developing and adapting apps to work with ICS. This prepares the ground for the manufacturers to release their own devices with a polished ICS on board, and people’s favourite apps ready to go when they upgrade.

OK, that’s all fine. But all that thinking didn’t answer the one really important question: not being a developer, and having plenty of things to spend money on besides a phone, how do I justify getting myself one of these?

Indie kids’ books by Secret Agent Josephine

Posted on

Baby-Without-an-Internet-Handle and I are a dynamic spy duo on a not-so-stealthy mission.

Our cyber-friend Brenda Ponnay has asked for help to spread the word about her Secret Agent Josephine kids’ books. I’m not exactly well-positioned to raise her profile, but I’m happy to take a stab at it from my too-cleverly-hidden lair. Brenda, aka SAJ, is an illustrator and longtime blogger, who’s launching a series of books for young children on the classic subjects of letters, numbers, and colours (aka “colors”). Her design sense is, well, designer-y: uncluttered and clean, but with a vibrance and energy that should appeal to kids as well as adults.

Secret Agent Josephine’s ABC’s, Numbers, and Colors are available as ebooks on Amazon, Barnes and Noble, and iBooks, and at least two of the books can also be had in physical form.

Brenda’s Amazon.com author page

Fixing messed-up metadata with exiftool

Posted on

Just a quick jot to spread the solution to a problem I was having.

I’m really enjoying using Darktable software to process my raw camera files when I’m not happy with the in-camera JPEG. It does happen, usually if the white balance is off or I’ve messed up the exposure, and to me this makes it worth shooting both raw and JPEG, even though it means I store thousands of huge raw files I’ll never actually use. (Aside: if Digikam starts allowing me to treat both the raw and the JPEG as the same picture for the purposes of tagging and rating, it’ll become much more efficient to remove unneeded files.)

I have a BASH script that does various things to my processed photos to prepare them for the web, including resizing with ImageMagick and writing artist info with ExifTool. ExifTool doesn’t like the JPEGs produced by Darktable from my Nikon D90’s NEF files, complaining:

Error: [minor] Bad GPS directory - mypic.jpg
0 image files updated
1 files weren't updated due to errors

I believe this is a manifestation of this known Darktable bug (apparently persisting in v0.9.1).

Just running exiftool -m [...] to tell ExifTool to ignore minor errors doesn’t get it past this error. The solution for me has been to get ExifTool to delete and rewrite the metadata, which is addressed in Question 20 in the ExifTool FAQs. So now I include the line

exiftool -all= -tagsfromfile @ -all:all -unsafe bad.jpg

before my next exiftool command, with the understanding that I may lose some metadata by doing this. I can always get it all back, if I want to, from the original photo file, which I never delete.

Really, it took me longer than it should have to find this, so I’m putting this up as a breadcrumb for sleep-deprived Googlers. Incidentally, my trail to the solution went via this forum thread where someone else with a D90 was having trouble with mangled metadata after processing photos with Picasa 3.8. Edit: I should point out that the forum post was answered helpfully by Phil Harvey, the author of ExifTool, himself, and that ExifTool is available for Linux, Windows, and Mac OS X. Good stuff.