summaryrefslogtreecommitdiff
path: root/posts/g1.mdwn
diff options
context:
space:
mode:
Diffstat (limited to 'posts/g1.mdwn')
-rw-r--r--posts/g1.mdwn40
1 files changed, 40 insertions, 0 deletions
diff --git a/posts/g1.mdwn b/posts/g1.mdwn
new file mode 100644
index 0000000..4bd0d78
--- /dev/null
+++ b/posts/g1.mdwn
@@ -0,0 +1,40 @@
+[[!meta title="A(n) Droid…"]]
+[[!meta author="Daniel Silverstone"]]
+[[!meta date="2009-01-19 11:44:28 +0000"]]
+[[!tag tech]]
+
+This weekend I took the plunge and got an
+[android](http://code.google.com/android/) based phone (The T-Mobile
+HTC-manufactured
+[G1](http://www.t-mobile.com/shop/phones/Cell-Phone-Detail.aspx?cell-phone=T-Mobile-G1-with-Google-Black)
+in black).
+
+Unfortunately it turns out that the man in the shop lied when I asked if
+it would work with my Tomtom — It has no ‘dund’ support out of the box.
+However, following the ever so useful instructions on the [Android
+Wiki](http://android-dls.com/wiki/index.php?title=Main_Page) I managed
+to downgrade the phone, jailbreak it, and re-upgrade to a chap’s
+modified firmware which has the bluetooth binaries etc in it.
+Unfortunately that wasn’t quite enough and I couldn’t get the Tomtom
+talking to it.
+
+I am assured that there’s an update to the firmware due soon, although
+it’s not clear whether that’ll fix the missing features. Also there are
+rumours of a large firmware upgrade due in the first quarter of this
+year, but that’s even more woolly since only one person (who I **do**
+trust) has mentioned it to me as yet.
+
+I have started to get a feel for coding for Android. Having pooh-poohed
+it when the emulators and SDKs first happened, I must say that I was
+pleasantly surprised. The Android stack is well thought out and quite
+pleasing to write for. Unfortunately I appear to be writing something
+which isn’t typically attempted by the sorts of people who write
+tutorials, so I am stuck trying to grobble through the source for the
+phone’s main apps, and small bits of examples I find lying around on the
+net.
+
+If anyone has a small, clean, example of an application which combines
+tabs, bound services which may optionally be started to make them
+persistent, threading for the service to run code in the background, and
+asynchronous callbacks for status updates from the service to the app
+frontend, then I’d be interested in seeing code.