I'm a new 770 wooter, fwiw.

I installed 2007HE yesterday, and I love it. Mostly just subtleties, but nonetheless...

Now, my battery life is a joke. Even when the device is off! I flashed the OS yesterday morning, and by late afternoon of light use, mostly with no wi-fi, I had one battery bar. I snapped the cover on, stuck 'er in my pocket, and when I pulled 'er out a little while later, completely dead.

So I charged it up, then did a little mild surfing just before bed. After that, I turned it OFF, set it on the nightstand, and went to sleep. This morning, no power at all.

I saw at least one other person complain about 770 battery life after an OS2007 install, but then someone else blamed it on third-party software, because they had no such problems. Being a new user, I've installed very little software: xterm, becomeroot, ssh, maemopad, and aisleriot. Could ssh be doing this? I noticed yesterday that while ssh'd into the 770, I popped the cover on and was still connected. I didn't try turning it off, because it seemed obvious that it would have disconnected.

Regardless, could ssh be causing my battery problems, or is it OS2007?

Thanks.

It's OS2007, since 2007 is ment for the N800 it doesn't include the automatic offline/lock mode that we 770 users get when we snap on the cover. The closest thing you can do is to set it to Offline mode, then lock the touchscreen.

But why would my battery die while it's OFF?

Okay, maybe it wasn't dead? Maybe I just couldn't turn it on? Because it's been on the charger for half an hour, tops, and I'm getting "Battery Full."

Surely you can't go from 0-100% in 30 minutes, right?

I've seen that a couple of times last year, and I use OS 2006.

I rarely turn it off, but on both occasions I was on flights and wanted to save batteries for video playing. I turned it off before going through security, but once on the flight it was dead. I suspected a crash, but removing and replacing the battery didn't help.

Fanciful theories about the x-ray machines aside, I rarely turn it off usually, so maybe it locks up somehow during shutdown.

Start an xterm and run 'top' to see if there's some process running. It should be at 0-1% CPU while idling (some activity caused by 'top' itself).