CleverBlogName

The Wellington Aero Club had an open day on Saturday. For a little girl who spent happy hours poking around racing cars in Te Papa a few months ago who likes to go to the airport to watch the planes, and her daddy, this seems pretty much like a heaven-sent afternoon, and that’s how it turned out.

As well as the pictured cockpit sessions in the pictured CT-4E and CJ6 Nanchang, Ada got chances to hop into the pilot’s seat of a Sounds Air Cessna Caravan, although we missed out on the Trojan when the owner needed a bio break.

While I attempted to explain the Trojan and Corsair’s features for aircraft carriers—the Corsair had it’s wings up—I don’t think Ada really grasped the idea of planes that land and take off boats.

The only real disappointments of the day were the tiny two-seat plane, whose owners shut up shop just as we arrived to have a look (I suspect Ada may have been so wedded to it because it looked, well, child-sized), and missing out on a chance to go up for a flight in the Catalina, which had run out of seat allocations by the time I asked. She was, however, a little trooper about it; she was really upset, but avoided any kind of tantrum. I need to make it up to her with a trip on a plane when I can afford it.

One not-so-minor irk, though: a few women earlier in the day had heard my plan and suggested that the whole business was about Daddy using Ada as an excuse to do something. Yes, yes, I know it’s a standard cultural trope that men only do things with their kids to have an excuse to buy things for themselves, and that little girls can’t possibly be interested in aircraft. It’s a bullshit sexist trope, too.

So I became acquainted with the “Blue Ring of Death” on my old (and Maire’s current) K850i; the phone doesn’t power on, with the screen staying black, the blue ring on the camera coming hard on, and the keyboard lighting up.

Not a thrilling sight.

A little Googling took my to an initially rather unpromising discussion which explained that:

• The K850 is notoriously unreliable and BRODs under all manner of circumstances and firmware revisions.
• The Sony-Ericsson Updater tool can’t fix the problem.
• Sony themselves can’t, either, and will typically take your phone and fail to fix it.
• There are a number of payware unlocking/reflashing tools that can.

The last was rather irritating. Not because I begrudge the people who developed Davinci or the other such tools, but because this is a perfect example of an anti-feature: like most mobile phones, the K850 is so locked down that when it blackscreens and becomes unusable, not only can I not fix it, neither can Sony, and I need to spend extra money to buy a third-party tool to rescue it.

Fortunately a little more reading about the place provided my salvation: the A2 Uploader, which works with a variety of Sony-Ericsson phones, including the K850i; and TopSony for the images needed to make it work. Download the latest firmware, reflash the filesystem, and then upload the customisation files and lo! The phone works (sans all the on-phone data, but you do make backups, right?).

So, phone restored for free. Hell, A2 Uploader will letme rip the obnoxious Vodaphone branding (useless menu and button items) out of my C903). Win, right?

Well, in one sense, yes. In another, though, not really. This whole thing is a parade of antifeatures:

• SE (and other phone manufacturers) don’t want anyone developing other tools to work with their phones, and go out of their way to make it difficult for third parties to help me, the phone owner, customise the phone I own.
• SE don’t want to allow me to up or downgrade to avoid buggy firmware that makes the phone crap itself. I can only get firmware and filesystem images from third parties of questionable legality.
• I can’t customise my phone to get rid of crapware (Facebooks apps and other rubbish).

Ada with her OLPC

So, I didn’t get to writing anything for Lovelace day proper. This is probably because I was busy writing about Jean Reno for French class (il est pas rasé). Homework first, people. Although I guess if I was less stupified by poor sleep this week I would have thought to write about a famous woman and combined my homework with an educational exercise re: Lovelace day.

So, I don’t have that. I do, however, have this; a picture of Ada playing with her loaner OLPC, which provides her with many hours of entertainment and budding computer literacy.

Pleasantly surprised to note that the Sony-Ericsson PC suite will out-of-the-box sync with any SyncML capable host—Funambol or eGroupware—thereby syncing your phone to the rest of your world. While I’ve got a (tiny) data plan and I’m generally happy to OTA sync, New Zealand belongs to that sub-Third World chunk of the mobile data universe where data is excruciatingly expensive and syncing by cable can be an attractive option.

Anyway, if this is relevant to your interests, it’s pretty straightforward:

Having had a good time getting Funambol working for OTA syncing is great, but it’s one part of a solution; it’s great for backup and multi-device information sharing, but it doesn’t give much in the way of, say, cross-user calender sharing.

Enter groupware solutions. (Look ma, I’m talking like an architect!)

Having poke about a bit, I’m trying eGroupware. It’s an free solution (albeit with a more featureful commercial variant); it supports PostgreSQL (a must-have for me), and it doesn’t require any kind of full stack replacement (other suites of this sort, as I have lamented in the past seem to require you replace your existing mail server, web server, and random other components). This all looks reasonably positive, as does the fact that it’s regularly producing releases and appears to be taking patches from an active community.

I’ve been thinking that iPhone vs Andoid has more than a whiff of Mac vs PC all over again about it, and Apple going after HTC as a proxy for Google just bakes that impression in; I’m not the only one who remembers as far back as Apple’s look and feel lawsuits, although that seems to be rather undercommented upon these days, as is Steve Jobs’ apparent long-forgotten view that people making expansion cards for the old pre-Mac Apple platforms were stealing money that belonged to Apple (which was, presumably, part of the reason why the original Mac was a sealed box).

Apple’s hostility to openness is one of those odd features of the modern computing landscape; they are, to the best of my knowledge, the only company the FSF refused to have software ported to (because of the look-and-feel suit), and their modern-day developer agreements for their sealed platforms are fabulously Draconian. It was one of the weirder aspects of LCA2010 to hear people booing DRM, software patents, overzealous IP law, and Microsoft, while watching them poke at their iPhones and Macbooks. Disconnect much?

There is one thing I must disagree mightily with Harry McCracken on:

So here’s the grim and dystopian scenario, and it’s grim and dystopian for Apple, not for HTC or Google: A few years from now, maybe this new case will end up looking as ill-advised as the 1988 one.[...]Maybe people will see the iPhone as a breakthrough that lost ground to a less inventive but more pervasive competitor. I hope not.

I hope so. I mean, my preference would be for Maemo-MeeGo-whatever the fuck it’s called this week to win out, but I think Nokia’s recent record of shooting its toes off will probably carry over to what is, the bleatings of Google fanboys notwithstanding, the most open phone platform on the market. But as a realist, I’d settle for seeing Android crush the iPhone, if only as a consumer. Consider the iPhone: a sealed unit, no expansion, no replacability, what Apple think I need. It’s Apple 1984 all over again. Andriod, on the other hand—you want an expandable phone? Get an HTC Legend where you have SD card support, rather than paying Apple an extortionate sum for the igger phone option. And a battery you can change. You want to live in the future? How about lobbying Samsung to release their Beam as a product, rather than waiting for Steve Jobs to decide whether you deserve a projecter. That’s the nice thing about the ‘droid; like the PC universe created by the ubiquity of DOS and then Windows, you have multiple manufacturers vying to lure you to their product, and responsive to your niche. You want a better-than-shitty-2 MP camera? There’s a droid manufacturer who’s releasing those. You want a bigger screen? More storage? Longer battery life? Go nuts.

The Android ecosystem is far from perfect; Google are certainly nowhere near as open a company, or as good at playing with the open-source projects they crib from, as their more enthusiastic fans would have you believe. But they are a hell of a lot better than the sealed-hood world Apple would like you to live in. If Apple’s decision to wage patent war against Android backfires and consigned them to the (ultimate) irrelevance of their decisions to prefer litigation and owning a high-priced vertically integrated stack did in the late 80s and 90s, I, for one, will be delighted.

Funambol, formerly Sync4J, is a number of things, but the bit I care about is that it’s a FOSS SyncML server you can download, run on your own server, and appears to be widely supported by all sorts of other FOSS tools (groupware, PIM software, and so on), and offer support for a huge variety of free and non-free SyncML clients. Since I can has data plan the idea of over-the-air syncing to a SyncML host has gained greater appeal, on top of the pre-existing appeal of making it easier to share calendars and the like with Maire.

The out-of-the-box delivery for Funambol is a binary Linux package that contains a JDK, Tomcat6, an RDBMs, and Funambol itself. On the one hand, this makes getting it up and running in a one-clickish fashion kind of easy. On the other hand, if you already have a database server and app server configured (for example) this is a bit of a wasteful duplication of resources; Funambol will let you work with (some) alternatives.

Ada: “I am going to make this a chicken sandwich. Chicken is going in the sandwich. He is in my big car.”

Rodger: “Does chicken want to be eaten?”

Ada: “Nooooo.”

Rodger: “Then perhaps chicken shouldn’t go in the sandwich.”

Ada: “Chicken has to go in the sandwich, because it’s a chicken sandwich.”

Ada then stuffs the toy chicken—the same toy chicken, I note that went to hospital with her when she was seriously ill at 7 months—into the cushions making up the sandwich, ordering him to “push your head in!”, throws a towel over it so the sandwich will cook, and then announces:

“Chicken is making a terrible fuss!”

Rodger: “Is that because chicken doesn’t want to be eaten?”

Ada: “Yes. Now you must eat the chicken sandwich.”

Fortunately I had already been designated a triceratops, so no chicken for me.

I’m far too sentimental to have given her any of this cooking and eating my toys. I blame her mother.

See this? Different (and longer) perspective on what I was getting at here.

Historical romances are an area that tend to be considered under the general rubric of writing for women, not least because of the association with bodice rippers; it’s an association that does the genre no favours, since it becomes synonymous with “crap”.

It’s a rather unfair reputation on two fronts; any genre will be rich in rivers of crap, and it seems a little unfair for fans of one genre to look down their noses at fans of other genres based on the lower echelons of the works in said genre. Moreover, there are no shortage of men who worked in it, including Arthur Conan Doyle (whose White Company and short stories set in post-Roman Britain dovetail neatly with chunks of Cornwall’s work).

Anyway, I’ve had bits of Cornwall’s Arthur series lying around the house since, well, since I got the second on in the series from a reviewer who was clearing out the newspaper’s unwanted review copies in, oh, 1999. So I guess it was time to get around to reading them.