K-Squared Ramblings

Android Browser Using Extra Space? Check Gears!

I finally found out what’s been taking up so much space on the Android web browser on my G1: Gears!

Whenever the low-on-space warning* icon shows up on the phone, I open up the list of applications. Then I sort it by size, look for the largest apps that I don’t use anymore, and start uninstalling.

“Browser” is always high on the list, but it’s all data. While I could free up the space by telling it to clear everything, I want to hang onto things like bookmarks. Each time the icon popped up, I’d go back to the app, open up More and then Settings, and clear the cache, or the history, or cookies**, one category at a time.

Then I’d go back to the App list and it would still be using up several megabytes of space.

Yesterday, it occurred to me to check the Gears settings. Months ago, I’d set up two WordPress blogs with Turbo mode, which uses Gears as a permanent cache for the admin area. It’s great on a desktop or laptop with lots of local space and a slow or flaky Internet connection. But it wasn’t helping me much, because…

• WordPress Turbo Mode is only really useful if you use the rich-text editor, which I don’t.
• On the phone, I rarely manage either blog through the browser anyway. I usually use WordPress for Android (formerly wpToGo).
• The files it stores take up a whole megabyte — per blog! (possibly more, depending on how the file system stores them.)

So I removed both sites from Gears, along with a couple of other sites that I’d added, but didn’t need anymore, and freed up about 3 MB.

It should be a while before I see that low-space icon again, and I shouldn’t have to ration my installed apps quite so closely!

*This wouldn’t be a problem if they’d given the G1 enough memory for apps in the first place, or if they’d let us install apps to the SD card (where I still have gigabytes of free space), or if I were willing to root my phone, or if I’d just bite the bullet and buy a Nexus One.

**I’d really like to be able to selectively delete cookies — or rather, to selectively keep a few cookies and delete the rest — but that’s another issue.

Nexus One Thoughts

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.

First Look Through Google Goggles

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.

Up and Down

• Cool: retro posters for Pixar’s Up #
• Interesting: I can call out from T-Mobile to a landline, & have 3G data, but I can’t call mobile to mobile or land to mobile. # (A few hours later, the phone stopped picking up any signal at all. It came back up late in the evening, Pacific time.)

There’s a Slogan for That

“There’s a ___ for that” is the new “Got ___?” #

G1: No Android 2 for You!

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.

Droidmark

I wonder if Lucasfilm will try to assert trademark over the Motorola/Verizon Droid? #

SCOpe

• About time! @brionv reports:
  

  After 6 years SCO finally dumps the exec who ran Caldera’s Linux biz into the ground. #

• Doozy of an update in the copyright case over Shepard Fairey’s Obama “Hope” poster. (via @ThisIsTrue) #
• Backed up, lately? A reminder from @sans_isc. #
• Found a pack of screen protectors while cleaning yesterday & replaced the one on my phone. HUGE difference in clarity! #

Out of Danger

• Good news for Sidekick owners: Microsoft/Danger has recovered “most” of the lost data. (I much prefer auto-sync to cloud-only.) #
• Mozilla Plugin Check helped me figure out why Flash was being flaky on one computer: I had different 32bit & 64bit versions installed. #
• Awesome! Butterfly Boucher’s Scary Fragile is #4 on Amazon’s MP3 Bestsellers! (via @butterflyb) #

Frustrations (And a Few Bright Spots)

• Hard disks should not sound like buzz saws. #
• Slashdot article “FOSS Sexism Claims Met With Ire & Denial”…gets met with ire & denial. *headdesk* #
• Listening to lightsaber sounds from across the office. I think my coworker w/ the new Android phone found an app for that. #
• Vertical Horizon’s Burning the Days is growing on me, but I think Vienna Teng’s Inland Territory is my favorite new album this year #MusicMonday #
• TNT, its nice that your video streams are Mac-compatible, but when your ads require Windows, don’t prevent me from finishing the episode! # (I’ve gone into this in more detail.)

Android FTW!

• Wasn’t aware there was a Sidekick outage. My T-Mobile G1 has been working just fine. Score one for Android! #
• Wasn’t planning to have a donut today, but T-Mobile just sent Android 1.6 to my phone. #

I’ve had this phone almost a year now, and it’s actually a better phone now than it was when I bought it! How cool is that?

Smartphone Radiation

Wow! Glad I didn’t move to a MyTouch! The G1 isn’t in the Top 10 Radiation-Emitting smartphones list, but it’s not exactly low either. # The MyTouch, on the other hand, is #1.

Cliq & Shock

• Android phones: Motorola Cliq might tempt me away from my G1 if storage is good. 5-megapixel camera, headphone jack, still has keyboard. #
• Weird: Routine Coast Guard training exercise spooks press because it’s 9/11. #
• I wonder how many people were freaked out by the shuttle landing’s sonic boom because of the timing? #

Immortal 3G

• Hah! “the only advantage of living forever is having the time to read all of TV Tropes.” #
• T-Mobile’s really expanding 3G lately. We’ve had it for a while, but can’t get a good signal at home. I think the building is a Faraday cage. #

G1 Nearing Upgrade Limits?

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)