A few days ago, Android Guy Ray reported that “T-Mo has stopped listing and selling the unit.” He hails the G1 for its place in smartphone history and for its place in his heart. Similarly, Devin at MobileCrunch paid his respects to the “solid” G1.

My G1 is still in good shape. Here’s a photo I took with it this morning. This stack of wood is one of many around Silver Spring after the post-storm cleanup. I won’t force any comparisons between downed trees and discontinued phones.

Early responses to the question (over at GigaOm) tend toward the emphatic no. Some emphasize that it’s only been out for a couple of weeks: good point. Others praise the NexusOne as a good or better smartphone: may be a good point, I’ve yet to use one.

The elephant is a suitable icon, and looks good on a t-shirt. You can see it next to the Android icon in the blog post that announced Evernote for Android.

Hence the new AOL logo: Aol. The case (lower case, not Steve Case) makes it look as though it should be pronounced, rather than spelled out. But how?

I have to agree with Om: it’s lame. Others (e.g. Peter at AllThingsD) are more diplomatic. But I haven’t seen any positive reactions yet.

TypeKit is a web service that allows you access to hundreds of fonts for your websites. The Droid fonts are available, even in the Trial/free plan.

I’ve started using Typekit to put Droid fonts on this blog, starting with Droid Serif for post content. That doesn’t guarantee that you’ll see this in Droid Serif, though. See the note on browser support.

My very early impression of Typekit is that it’s at the stage meriting labels such as: early; very promising; currently frustrating. As an illustration of the last label, I tried to make a support suggestion, but couldn’t because I wasn’t signed in. WTF: I was signed in to Typekit. That’s all it should take. I shouldn’t have to use some other id/password combination.

I tweaked the theme of this blog to use that very green for the blog title. I mean the main theme, PrimePress; I’ve yet to touch the mobile theme. That got me thinking of changing the other colors used in the theme, and about a palette featuring Android Green.

At COLORlovers, I generated a palette comprising Android Green and split-complementary colors (i.e. two colors adjacent to the complementary color). I found that Android Green already had the name misty green, and appeared in two other palettes: jungle and trackside. I like it with the orange in the latter.

I intend to play around some more with palettes including Android/misty green, but this kind of thing can suck you in…

These fonts are available under the Apache license. There will be more about this license, and Android’s use of it, in a future post; for now, I’ll just remark that it’s a free software license.

Ascender Corporation developed the Droid fonts. It continues to work on them. Some versions of Droid fonts will be available under commercial licenses.

The Droid fonts should not be confused with the Android Custom Typeface, which is used in the Android logo. I am prevented from showing you the Android Custom Typeface by two things: first, I like you too much to inflict it upon you; and second, the Android brand guidelines forbid me from doing so.

The Droid fonts are key to the Android experience – yes, even more than the Iconic Android is. And I rather like them.

Brief review so far: good phone, in terms of the device itself and in terms of service from T-Mobile; useful for checking email, and for some other webby things; decent camera; weakest point is the GPS.

There are many other Android phones, with more on the way. I’ll link to TechCrunch’s list, since it includes remarks on each phone, and the promise of updates.

For the photo of a G1, I thank jugglerpm.

The picture is obviously relevant to the Android icon theme. In fact, it’s even more relevant to the Android phone, in that we may well become a two-Android family soon.