Tag: Android

Posted on
by

I’ve never been a fan of actually using GPS navigation. Sure, I’ve always thought it was insanely cool that it was possible, I just didn’t want to use it myself. For unfamiliar destinations I generally prefer researching a route first, and for familiar ones I generally prefer just relying on my local knowledge. But I’ve found something that I do like using it for: Traffic.

I recently started a new job, exchanging a fairly short commute for a ~40-mile trek across the Los Angeles freeway system. Under ideal conditions, it’s about 45 minutes. When the freeways are bogged down (i.e. when I’m actually going to be driving), it can take an hour and a half or more.

When I landed the job, I replaced my phone with a G2. It’s a heck of a lot faster than my old phone, plus it can handle newer software…like Google’s turn-by-turn navigation app for Android. After trying a couple of different routes the first few days, I tried it out…and discovered that it factors in live traffic data when calculating the remaining time.

The upshot: I can walk out the door, start up the app, and figure out which of three main routes will get me there fastest. (Well, least slowly, anyway.)

Of course, it’s not perfect. It’s based on traffic now, and over the course of a predicted hour-plus, the route could easily get more congested. That’s not even counting potential accidents. It does seem to update frequently, though, and knowing I’ve avoided a 100-minute drive in favor of 70 minutes really outweighs the annoyance of a mechanical voice telling me how to get to the freeway from home.

I do have to remember not to rely on it too heavily at the end of the trip, though. I left it on by mistake after selecting my route to the LA Convention Center for Adobe MAX this morning, and instead of turning it off, I let it direct me straight past the parking garage.

Oops.

Posted on
by

Comic-Con International is rapidly approaching, and you know what that means: it means I’m thinking about mobile computing again!

Right now, I’ve got a G1 Android-based phone, and Katie and I share a MacBook. The G1 is showing its age, and it would be nice to have a second computer to do things like manage photos with while traveling.

So. Options.

1. Upgrade the phone. I’d like to stick with T-Mobile, but unfortunately after being the first network to take a chance on Android, they kind of dropped the ball on high-end Android phones. It looks like they’ll be getting the Samsung Galaxy S as the Vibrant, which might solve that problem. (Downside: no camera flash, no physical keyboard, both of which are in the Galaxy S Pro — but I don’t know when or even whether it’ll show up on T-Mobile’s network!)

Also, this doesn’t solve the photo management problem…and if I get a touchscreen-only phone, it’ll really slow down typing until I get used to it.

That and the rumored launch date for the Vibrant is July 21: the day before Comic-Con! That’s not the best time to try to get used to a new device.

2. Get a tablet. As much as I love Apple’s laptops and think that tablet PCs are a great idea, I can’t get behind the iPad. I don’t like the walled-garden approach where Apple gets to choose what you’re allowed to install on your computer. As for other platforms, Windows and Android tablets don’t seem to be comparable just yet.

In short: not gonna happen this year.

3. Get a netbook. I keep coming back to this, don’t I? Last weekend I checked out the selection at Fry’s and Micro Center, and decided on several things:

  • Never, ever buy a netbook without trying out the keyboard first! I found one that was so bad that I’d rather type on my phone for an hour than this netbook.
  • Smaller is better (up to a point). There’s no point in getting a large netbook when I could get a more fully-functional small notebook.
  • A lot of netbooks have truly awful trackpads.
  • While I’d rather get one with Windows 7 than Windows XP, it’s not critical. (Vista, however, is right out. Not that I saw any Vista-based netbooks…)
  • I like the Splashtop instant-on mini-network OS. It’ll be sufficient for 90% of what I’d be doing with a netbook.
  • A big chunk of that other 10% would be photo management! Or at least pulling photos off the camera and uploading them. Managing stuff within Flickr should work.
  • Most netbooks are still above my personal “Oh, just buy it and get it over with” price point, which is $200. MicroCenter had two, one of which was the one with the horrible keyboard, and one of which had Windows XP, didn’t have SplashTop, and had a mediocre trackpad. I really had to think about whether it was worth it or not.

Even so, It’s going to be hard to justify a netbook and a newer phone, and if I have to pick one, it’s going to be the phone. At this rate, by the time I decide to go for it, a tablet may actually be more practical!

Posted on
by

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.

Posted on
by

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.

Posted on
by

I tried out Google’s new Goggles app. Basically it lets you use the camera on an Android phone to do an image-based search. The examples include landmarks, book covers, artwork, logos, contact info, and places.

So I played with it for a bit at home tonight. It’s good at picking out book covers and logos, if you’ve got good lighting and a clear image. 50-50 at landmarks, at least when taking pictures of my monitor. In a couple of cases, it actually picked out the exact photo as a match. It’s not so good at objects, even obvious ones like a Coke can. I’ll have to try it out in the real world next.

Posted on
by

I briefly considered doing a fresh install on the old PowerBook to see if it could be used as a second laptop, instead of just wiping it to recycle, but quickly remembered that the reason we replaced it was a hardware problem.

Still, it would be nice to have two portable computers for when we travel. I have a horrible tendency to hog the laptop when we get back to the hotel.

The thing is, we don’t need a second laptop for normal use. So getting another MacBook, or even a full-size Windows laptop, is overkill. Would a netbook do the trick? What do I use a computer for when traveling?

  • Reading/writing email.
  • Managing & uploading photos.
  • Blogging & managing blog comments.
  • Twitter (and more recently Facebook).
  • Web access.

Yeah, I could easily get by on a netbook, freeing up the MacBook for Katie to use.

But do I even need the netbook?

Almost everything on that list is something I can do with my Android phone, assuming WiFi or a decent 3G signal. Not as quickly, perhaps. I type a lot more slowly on the G1 than a full-sized keyboard, and even at 3G speeds web browsing can be slow, especially on sites that don’t optimize for mobile use. And websites that require Flash still won’t work.

The real deal-breaker is (still) photo management. I can upload photos I’ve taken with the phone, but only one at a time — and I can’t transfer photos from the regular camera. The small screen size also makes it harder to look through a set of several similar photos and pick out the best one.

So I could manage with just my phone if I had:

  • A way to transfer photos from my camera to my phone. (The hard part. Android issue 738 is an enhancement request to be able to connect USB devices. It’s not clear whether the G1 hardware supports USB On-The-Go or not, but the drivers and Android OS don’t — at least not yet.)
  • An app to mass-upload photos to Flickr. (They exist, I just need to research and try a few out.)

I guess for now the best way to handle it is for me to just upload photos on the laptop, without taking the time to label them, then hand it over and move to the smartphone. Though if the network connection is particularly slow, like it was at Comic-Con International this year, that would still be problematic.

Of course, we don’t have any travel plans at the moment until next spring. Who knows? By then a netbook (or a newer phone) may be more practical.

Posted on
by

One minor rant, and one success story, sort of connected.

The rant: My internet connection is acting kind of flaky tonight. Actually, the connection is fine, but it isn’t talking to some content delivery network(s). All the small-time websites load perfectly, but a lot of the larger ones either aren’t loading at all or are taking ridiculously long. I can load the Facebook timeline, for instance, since that’s dynamically generated…but it took 20 minutes for it to load a handful of static 16×16 pixel buttons for things like sharing links. *grumble*

On the other end of things, I had a great experience with Best Buy’s mobile website earlier today. I’m not sure I’ve ordered anything from BestBuy.com in years. The last thing I can think of was my first decent digital camera…in 2003. Usually if I’m going to buy from them I just walk into the store.

Meanwhile, despite owning my G1 for almost a year, I’ve never actually used it to buy anything that I can recall. Lots of research (ShopSavvy, plus various stores’ websites), but no actual purchases. I decided I wanted to see if I could place an order using just my phone, and it was extremely easy to:

  • Find the item
  • Add it to the cart
  • Select a store for local pickup
  • Update my billing address
  • Place the order

The only real sticking points were:

  • Store locations only listed cities. Fortunately, I could just hit a “map” button and they loaded in the phone’s Google Maps app.
  • I had to reset my password, since it had been so long. Since I have POP access to that account, that meant waiting a few minutes for the whole mailbox to download before I could open the message with the new temporary password. Then I had to write it down because K-9 doesn’t seem to support copying text from incoming mail.

Other than that, everything was not only possible using the Android browser, it was streamlined. If I hadn’t needed to update my address and reset my password, I could have been done in two minutes flat. Maybe three once you factor in typing in the credit card info.

I had a harder time posting a link on Facebook tonight — on my desktop — than ordering something on my phone!