I use navigation on my Android phone to pick out the best route to work each morning. The problem is, it bases time estimates on traffic conditions now — not traffic conditions as they’ll be when I get to each point along the route. I’ve gotten used to the morning drive taking at least 15 minutes* longer and the evening drive taking around 10 minutes less than predicted, but a little more precision would be helpful.

Obviously, Google isn’t psychic. They can’t predict where and when car crashes will happen. But they do have historical traffic data. If you go to Google Maps on the web and display traffic, you can switch between live data and an average for a given time and day of the week.

It would be fantastic if Google used that data to predict how much slower (or faster) traffic will be moving at each point along each projected route, and use that for the time estimates. It would be nice for the “Are we there yet?” factor, but it would be incredibly useful for route planning!

*Sometimes more. This morning, it predicted a 55-minute trip. It took me an hour and 35 minutes.

Android and Me is reporting that all Android phones in the U.S. will get Android 2.1 updates — even the G1 — but that they may be missing some features and some models will need to be wiped as part of the installation.

That makes sense, because it would allow developers to reassign some of the space set aside for over-the-air updates and use it for a larger system instead — and maybe more space for apps.

The possibility that the G1 was headed for obsolescence before my 2-year contract was up didn’t bother me much at first, but I’ve watched as even Google has released high-profile apps that required Android 2. Sure, I doubt the hardware can handle Google Earth, and Buzz turned out to be a dud, but they’re signs that Android 1.6 isn’t going to cut it for much longer.

If it does require a wipe and re-install, I can deal with that. A lot of the key data is either synced with the cloud or stored on the SD card. With luck, T-Mobile and HTC will build a decent backup and restore into the process and I won’t have to reinstall all my apps, bookmarks, etc.

Update August 2010: This is looking less and less likely as time goes on.

So, Google has announced the Nexus One phone. Let’s see how it stacks up against what I want in my next phone:

  • Mainstream Android (i.e., not overcustomized like Motoblur)? Check.
  • Faster than what I’ve got (a G1)? Check.
  • More memory & storage? Check.
  • Better camera? Check.
  • Longer battery life? Check.
  • Less clunky? Check.
  • Available on my current provider? Check.

Sounds great!

Only one problem: there’s no keyboard. Android’s on-screen keyboard is decent enough, but I’m not quite ready to give up that physical keyboard just yet. (OTOH, I don’t want the Droid. I played with the keyboard a little at Best Buy a couple of weeks ago, and really didn’t like it.)

I’ll have to practice with the virtual keyboard on the G1 some more. If I can get used to it, this might be worth the upgrade.