I figure there are two reasons it hit now and not earlier.

1. I usually charge my phone overnight and unplug it in the morning, though the last few days I’ve been charging it in the evening and unplugging it when it’s done. And since I usually use navigation to check traffic on the way to work, I tend to recharge it during the day because actually using navigation is a battery hog. You’d still expect it to have hit yesterday or the day before, except…
2. I usually turn off GPS when I’m not using it. Last night I forgot.

My guess: Maps isn’t shutting down properly, and if GPS is enabled, it’s calling out and using up power.

The other weird thing: Before I realized I’d left GPS on, I uninstalled updates to Google Maps. Then I went back to the battery usage report, and instead of 91% Maps and tiny percentages of others, it showed the more typical 30% Cell standby, 30% Wi-Fi, etc. I suspect uninstalling the updates may have removed it from the battery usage report, and I was seeing the remaining 9% blown up to 100%.

Update (Wed): I reinstalled the Maps update and made a point of turning off both GPS and Wi-Fi when I charged the phone that evening. No battery drain during the 8 hours between the time I unplugged it last night and the time I picked it up this morning. Tonight I’m going to try it with just Wi-Fi and no GPS and see what happens.

Update (Fri): Well, that was unexpected. I turned GPS off and left Wi-Fi on last night, and the phone was down to 55% battery when I woke up this morning. Even though I know it had a stable signal since it was sitting 4 feet away from the access point. I would have thought GPS was a more likely culprit, but this suggests otherwise. Tonight I’ll have to try it the other way around.

Update (Sat): Last night I turned off Wi-Fi and turned on GPS before unplugging it from the charger. This morning I forgot to check the battery level, but I looked at it just after noon — and it’s still at 90% after at least 12 hours.

To make matters more interesting, Katie has long had problems with her Vibrant losing battery quickly, but since she turned off Wi-Fi, she’s been able to go several days between charges.

I think we’ve found the culprit. The question remains, though: why now? What is the phone doing over wifi that it wasn’t before?

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.

Admittedly, the process only took that long because their voice recognition system wasn’t getting along with my voice, but still, isn’t the point to route people to the fastest response in an emergency?

Now I know: It’s the lack of space.

Last night I updated Gesture Search, which pushed the phone into low-space territory. I figured I’d deal with it later. This morning, I noticed that it wasn’t reporting new messages on Gmail. Reluctant to uninstall any more apps, I followed Katie’s suggestion of clearing out old text messages…and freed up 1.5 MB. (I figure it’s the pictures. They’d better be worth 1,000 words, because they take up a lot more disk space.) A few seconds later, the @ popped into the notification bar.

You’d think that 7+ MB would be plenty of room to download email and text messages, or tell the notification system to pop up a new icon. As near as I can tell, though, if the “Low on Space” icon is visible, Android won’t sync anything.

Next time, I’ll make a point of cleaning things up quickly.

With luck, this won’t be a problem with my next phone. (Yeah, I’m still on the G1.) Whether I go for a Samsung Vibrant, a G2, or something else, it should have more storage on the phone and the ability to install apps to the SD card.

TweetUp acquires Twidroid and changes its name to Twidroyd “to ensure minimal confusion with products from Lucas Films.” Fortunately no one will mistake Lucas Films for Lucasfilm…

Last month, KTLA reported on a 3.3 earthquake in the Inland Empire. “Dozens of residents” in the region felt it. Dozens! Wow!

I have to agree with @rzazueta: Woot’s Amazon buyout report is an instant classic (via @boingboing)

Chart of the Day presents: What people are actually doing with their cellphones (aside from talking) based on a Pew survey on mobile internet use. (via @ThisIsTrue)

Yesterday, some more email-to-SMS texts vanished into the ether. I figured something must be up with the gateway, so I changed the alerts so that they would also send to my Gmail account, figuring that if the text messages failed, I’d still get a notice.

They didn’t show up either.

That’s when I realized that nothing on the phone was actually syncing: Not Gmail, not the contacts, not the calendar…and it just wasn’t receiving text messages at all.

I tried turning sync off and back on, manually syncing, restarting the phone (both a hard reset cycling the power and a soft reset, sort of the Ctrl-Alt-Delete equivalent using the green, red and menu buttons together), even clearing all the local data for Gmail, Gmail storage, and Calendar storage.

Well, none of that worked. It marked all the apps for syncing, but wouldn’t actually start.

So it was time to backtrack: What had I changed recently?

Well, I’d updated several apps. Off the top of my head I could think of Twidroid Pro and the Weather Channel, but I couldn’t remember what else.

I’d also installed a new app, Layar, an augmented reality app which I’d seen in an ad for some other phone last week, but hadn’t actually gotten around to trying out. Adding it triggered a low space warning, but the phone still had 6.8 MB free, which ought to have been plenty.

Curiously enough, the last successful sync was right around the time that I installed Layar. Hmm…

Okay, what the heck. I uninstalled it. Within seconds, the phone bleeped and picked up the test messages I’d sent to Gmail. Within a minute, several text messages arrived, including my test from this morning and two alerts from last night.

Well, that was certainly suspicious.

So I installed it again, and this time actually opened the app to try it out (making it display the location of pizza places as seen from my desk), and sent myself a test message at Gmail. I can’t say I was surprised when the test message showed up on my desktop, but not on my phone, even when I manually refreshed my inbox in Gmail. Within a minute of uninstalling the app again, the message showed up.

So, no Layar for me. I don’t know if it doesn’t work with the G1, with Android 1.6, or with something else I have on the phone…or if it’s not Layar at all, and the phone just needs more space to sync.

The message is clear, though: If your phone stops syncing, or stops receiving text messages, look at what’s changed. There’s a good chance that the problem is related.

Update: It’s been about half an hour, and the voice mail notice just popped up…for a couple of messages I received on Sunday! It looks like the problem was blocking everything that used the standard sync/notify system on the phone. Twidroid was working, so I guess it must use its own system.

Update 2: I’ve confirmed that it’s just the low space, not the particular app, that causes the problem.

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.

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

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.