The Musings of Chris Samuel

So it’s just over two weeks since I started with Android on my FreeRunner and it’s time for an update. First of all I’m no longer using the Koolu images, they lack echo suppression support and as soon as I found that Michael Trimarchi’s Panicking port of Android does do echo suppression I switched. The added benefit of changing was that Michaels port has fixed the go-slow feel of the Koolu version and feels responsive and usable in most situations (though the soft keyboard is still a little slow).

Good points:

1. Calls work flawlessly.
2. SMS works flawlessly (and has a nice interface)
3. Contacts can be added as shortcuts on the desktop
4. Wifi works (though WPA2 Enterprise networks need some text file magic)
5. GPS works nicely (I used GPS-status to see how many satellites it can see)
6. Bluetooth works – or at least finds devices when scanning – not gone any further with that
7. Web browser works nicely, even supports Google Gears

Bad points:

1. NO ACCESS TO THE ANDROID MARKET – the Android Market application is not open source (a decision by Google) so you can’t access any applications hosted there. Whilst there are alternative sources they only have a fraction of the applications so this does limit things.
2. The phone seems to stop being able to suspend if you define a APN for GPRS/MMS access. Resetting the APN to the defaults (none) fixes it though.
3. I don’t seem to be able to download MMS/PXT’s – I suspect this is related to the APN issues and I may just not have the right info
4. Accelerometers don’t appear to work – or at least the marble game I had didn’t react to me tilting the phone.
5. Battery life doesn’t seem to be quite as good as Qtopia/Qt-Extended/QtMoko – I have to charge every 24 hours at present. That said the later kernels don’t seem to give me quite as long a lifetime as the 2.6.24 based ones so that may not be Androids fault..

But all in all I’m really quite happy with Android on FreeRunner, it easily outshines my previous favourite of Qtopia/Qt-Extended/QtMoko in terms of overall polish and usefulness as a phone! Thanks to all involved in the porting effort, and especially Michael.

I have been assimilated. Or at least my OpenMoko Freerunner has been! It’s now running the Koolu port of Android 1.5 “Cupcake” on it, and with a *very* helpful hint from Damian Spriggs on the OpenMoko community mailing list it’s able to make and receive calls and SMS’s. For the record you need to get ADB working and grab a root shell on the phone. Then you can use the sqlite command line utility to set the “provisioned” flag in its DB.

# sqlite3 /data/data/com.android.providers.settings/databases/settings.db
SQLite version 3.5.9
Enter ".help" for instructions
sqlite> INSERT INTO secure (name, value) VALUES ('device_provisioned', 1);

I’ve also found a rather nice application called VCardIO for importing my contacts exported in VCard v2.1 format from KDE’s Kontact addressbook. Now we’ll see how it goes over the next few days!

I suspect that the world and its dog will have heard about this by now, but in case you’ve somehow missed the announcement from Google..

Google Chrome OS will run on both x86 as well as ARM chips and we are working with multiple OEMs to bring a number of netbooks to market next year. The software architecture is simple — Google Chrome running within a new windowing system on top of a Linux kernel. For application developers, the web is the platform. All web-based applications will automatically work and new applications can be written using your favorite web technologies. And of course, these apps will run not only on Google Chrome OS, but on any standards-based browser on Windows, Mac and Linux thereby giving developers the largest user base of any platform.

If (and I emphasis if) this takes off then MS might be in for something of a rough ride in the Netbook market. The Netbook vendors have been unable to stand up to the MS monopoly with Linux on Netbooks until now, perhaps Google can start to rebalance the marked a little ?

Google is running a photography competition to develop themes for iGoogle in conjunction with the Saatchi Gallery London for higher education students around the world. You’ll need to submit 5 photos to make up a theme.

36 shortlisted students will get their photos turned into iGoogle themes, 6 finalists will get exhibited at the Saatchi Gallery and the winner will get a GBP 5,000 bursary and a day with the documentary photographer Martin Parr. Entries close 31st May so if you’re interested (and eligible) you’d better get your skates on!

This Flash map is pulling RSS data from the Victorian Country Fire Authority (CFA) onto a Google Map of Victoria.

Note that it can only show fires that the CFA are reporting via their RSS feeds, long running fires may not appear until they are updated in their database and pushed out to the feed.

(Via) (Original Google blog)

Oh well, so much for the dream, this was on the Kogan blog this afternoon:

I’m disappointed to have to tell you that the Kogan Agora has to be delayed indefinitely. This delay comes due to potential future interoperability issues.

Sounds like this was partly due to wanting to keep the device compatible with future Android versions needing better screens:

One of the potential issues is the screen size and resolution. It seems developers will be creating applications that are a higher resolution than the Agora is currently capable of handling. [...] In order to fully appreciate the feature-rich applications Android developers will be creating in coming months and years, the Agora must be redesigned.

I hope that whatever they come up with still has a real keyboard..

The PR company for Kogan has put a YouTube video up of a production sample of the Kogan Agora Android phone that I pre-ordered on New Years Day. Looks quite snappy from what you can see, but it’s not the worlds best produced video.

Via Andy, who emailed me a link to this blog which in turn linked to the original Gizmodo post..

Kogan, an Australian company who usually specialise in LCD’s, are making a mobile handset (the Agora) for Google Android (which uses the Linux kernel) with 3G, quad band GSM, GPS, wifi, Bluetooth, etc… It’s due to start shipping at the end of January and I’ve just pre-ordered mine to hopefully provide a more functional open source phone and let me hack more with my OpenMoko phone without having to worry about not having a working phone.

…not in a malicious way, but in a rather amusing and potentially destructive one..

It seems as though there is a /system/sbin/sh running in the background with
/dev/console as stdin. That could explain why typing “reboot” and then enter (in
ConnectBot or otherwise) will reboot your phone. If you type “telnetd”, telnet into
your phone, and look at the /proc/XX/fd tree for the /system/sbin/sh process, you can
see it clearly.

Until you’ve grabbed the RC30 update that fixes this it’s probably best not to do much sysadmin work from one, especially if that involves rm -rf foo.. This was via LWN, which has the priceless comment:

I wonder how many android phones were running at half speed after someone replied “yes” to someone…

Oops..

At Google, we have a saying: “launch early and iterate.” While this approach is usually limited to our engineers, it apparently applies to our mailroom as well! As you may have read in the blogosphere, we hit “send” a bit early on a comic book introducing our new open source browser, Google Chrome.

The Wikipedia page has more info, apparently it’s based on WebKit. Expect the Windows beta in the next day or so, with Linux and OSX to come. Open source of course.