Tag: mobile

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!

Posted on
by

Okay, I get it. By buying the first device of its kind (i.e. an Android-powered smartphone), I’m an early adopter. In a sense I was helping out in a massive public beta as Google, mobile phone carriers, and handset manufacturers worked out the kinks in the design and realized things like, “Oh, we really do need more memory than that, don’t we?”

But it’s still annoying to read the early reports that Android 2.0 “Eclair” won’t fit on the G1.

We have done this dance before, when rumors surfaced that the G1 wouldn’t be able to handle Android 1.6 “Donut.” Fortunately, engineers managed to squeeze it into the space available, and T-Mobile sent out Donut as an OTA (over the air) update to MyTouch and G1 devices alike. But I’ve had time to think about the issue, and my thoughts basically come down to this:

  • New software eventually reaches a point when it can no longer support old hardware. You can’t run Snow Leopard on a G4 or Windows 7 on a Pentium II.
  • When the hardware is usually tied to a fixed-term service contract (in this case, 2 years), the provider really ought to fully support it for the length of that contract. The G1 launched 1 year ago with (in most cases) a 2-year contract.
  • Even if this is the last major update, my phone is still better now than it was when I bought it.

It will be very nice if history repeats itself, and Google and/or T-Mobile finds a way to cram Eclair onto the G1. Even if it means dropping the convenience of OTA updates and instead requiring you to download it to a PC and update over a USB cable. More likely, though, they’ll freeze the G1 on Android 1.6 except for bugfix and security updates, and it’ll be up to unofficial distributions like cyanogen to bring a newer OS to the older phone.

Because I don’t really want to mess with rooting my phone and installing a third-party distribution, if this is the end of the line for the G1, well…Android 2 has some really nice features that I’d really like to be able to use, but nothing that screams “must have!” The only real worry I have at this point is that app developers might start requiring newer versions of Android.

The other option: buy a newer phone. I’ll probably want to do that anyway in a year or so, but I’m not there yet. It still feels like I just got this one.

Update (February 26): It turns out the G1 will get Android 2.1 after all, but will probably require wiping the phone. 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.