Mark Staples

A couple of weeks ago I caught up with the 20th century and got my first mobile phone. I also leaped into the future because my phone is the Google Dev Phone 1 – an unbranded HTC Dream running Google’s Android operating system. There aren’t many Android phones available on the market right now, but a slew of them are due to be released later this year.

The Dev Phone phone is network unlocked and root enabled, but having one is a trade-off. I can upgrade the phone operating system outside the standard HTC Dream path to get access to new/privileged phone features (good), but on the other hand Google won’t give me access to the copy-protected apps in their Marketplace (bad).

My thoughts on the handset aren’t unusual, but here they are anyway. I love the swing-out keyboard and the look and responsiveness of the screen. But the battery life is woeful, even with WiFi, bluetooth, and GPS turned off. I’d also slightly prefer a standard 3.5mm jack instead of having to rely on USB headsets.

On the software side, I’m not ditching my Windows Mobile device yet, because there’s not yet a good free solution for automatic 2-way synchronisation between Android and the calendar and contacts in my work’s Exchange server. I can at least connect with the Exchange secure IMAP interface using the K9 email client (the core Android client doesn’t support this!). Maybe the gmail and google calendar applications are fantastic, but I wouldn’t know because I feel I should use my work’s IT infrastructure for work purposes, and I handle my private email through my own domain and mail server. One can only hope that Android will get more serious native support for business users later this year.

Finally, I should say that the HTC Dream handset is a “patriotic” handset to buy, because the Qualcomm chipset running the phone functionality runs the OK Labs version of the L4 microkernel that came out of NICTA. The phone has two chips – one for the phone functionality, and one for the rest of the OS and applications. This is despite the fact that with L4 it should be perfectly possible to instead have two (or more) isolated virtual machines running on just one chip. Apparently phones like that will be coming out late this year. Maybe they’ll have better battery life!

I said I’d report back on an experiment I started last November.  For the Chilli Lager I made with a 3kg malt kit, I primed half the batch in the normal way, and didn’t prime the remaining bottles.  The theory is that when using a full malt kit, after primary fermentation and bottling, there should be enough residual dextrins left to be slowly enzymatically converted into simple sugars and then be digested by the remaining yeast.  I’ve had a request to report on the outcome of the experiment.  So here is a status report.

A month ago I would have said that the unprimed bottles were basically flat.  My problem is that I don’t how long I should wait for these enzymes to act!  I had basically given up on the unprimed bottles, but last night I tried another sample, and there was some definite fizz going on.  It wasn’t nearly as active as the primed batch, but it certainly had more sparkle than some English beers I’ve had.  So, I’ll wait and see.   In the past I’ve had home brew improve over the course of a year in the bottle.  Perhaps that improvement was due to a similar process.

Nonetheless, my plan for future batches is to keep adding priming sugar before bottling.