Tag: Mobile Devices

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 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

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.

Posted on
by

I love my T-Mobile G1, but it’s no secret that the phone has way too little internal memory. Now Engadget reports that the limited memory could prevent the G1 from running future versions of the Android operating system.

You can add plenty of data storage (images, music, app data) by dropping in any size Micro-SD card (IIRC it came with 1 GB. I’m currently running it with an 8 GB card). But the phone system, all the apps, and the cache for updates all have to share the measly 256 MB internal storage. Android and Me breaks down the partition structure, and points out that the current system, Android 1.5 “Cupcake,” already fills 99.5% of that space. Since software usually gets bigger with each successive version, it’s been challenging for Google to keep the OS within that limit.

It seems like it would be easy to just move the update cache to the SD card and double the size of the system partition…except that it would require reformatting the phone. Doable, but risky.

Before we get too gloomy, T-Mobile has stated:

We plan to continue working with Google to introduce future software updates to the T-Mobile G1. Reports to the contrary are inaccurate.

Now, this may simply mean that they’ll continue issuing bugfix/security updates. Or it may mean that they’re working out ways to squeeze newer Android versions onto the phone.

Now, Some Perspective

Let’s face it: the G1 is a first-generation device. It’s right there in the name (Generation One). All of us who bought it are early adopters, and that carries a certain degree of risk. Just like all those people who paid, what, $600 for the first iPhone only to see the price drop heavily less than a year later.

Even so, with Cupcake, Android is already quite a capable OS. Whether the G1 hits the wall at Cupcake, Donut, Eclair or Flan, the phone won’t stop working just because it can’t get major updates. Whatever happens, it’ll still be usable for the duration of a 2-year contract (and presumably beyond).

I do worry about incompatible apps, but that’ll start happening anyway as more devices with varying hardware specs appear on the market.

Really, though: this is the first phone I’ve ever owned that had software updates of any substance. I think one of the two RAZR variants had a bugfix release that came out before I even bought the phone, but that’s it. The fact that my G1 is actually a better phone now than when I bought it is pretty damn cool!

(via TMONews)

ยปAll pages site-wide with this tag