[G1 Android Development] Janis:
Wow, that was fast, trying 3.4.2, to solve coma, no go :(

I'm at this moment flashing from 3.4.1, on which I was bootlooping erratically and having the "not waking up" problem. (I'm also enjoying a vegan burrito, which I didn't expect to like that much. I mean vegetarian isn't even my style, much less no dairy or egg & stuff. Hm.)

(OK, why on earth would a wipe alleviate a bootloop? It just appeared to, on 3.4.1.)

Booting to 3.4.2 thinking an app that would store sign-in data and hijack the process would be cool for habitual flashers.

Open Home is there, not data, as expected. Auto downloading the apps I had on before the flash via Edge ('member when we were so excited to get and E icon instead of a G?). Connecting to Wifi WPA2, just like before when it conked. Starting Swapper. Switching off auto-orientation, setting screen time-out to 2 min.

A difference I'm noticing is that I don't have the flashing green LED. When it would not wake up/went comatose, the green LED was always flashing. I think, too, that I had cleared my notifications most of the time. Something to ponder.... or not. But I had both download notification and unread email threads and no LED. I cleared those.

So, I sent myself a text. I'm waiting for it to sleep on its own, since that's as close as I can get to emulating the old scenario. So, green LED flashing from SMS, it hasn't gone comatose.

Can we call this whole won't wake up thing "Coma?" It happens on different devices, seems to pop up here and there, and people are having trouble finding it or calling it something specific. This seems to fit, alive but unresposive. Consensus is all it takes to change language.

OK, I've tried letting it fall asleep on its own twice with the MS light flashing, and all seems to be good.)

Whups. Third time's a charm. I may have waited an additional few seconds. I'm comatose again.

I"ve always been able to get out of it by soft-resetting with the green+menu+red buttons. I've never removed my battery for this, just to get out of bootloader....

On fresh boot, waited 2 min after falling asleep. Powered up fine (menu button). Waiting 5. Powered up fine.

Cleared sms notification. (Wierd to have on sms come up as two entries in a conversation. Not unexpected... like talking to yourself. Does it come out your mouth one way and go in your ears another? Is there a delay?) Sent another.

Waiting 2 again.

(OK,as much as I love glitz in a ROM, I'm a space and speed fiend. I push gadgets with apps to their limit. I need this ROM. I am hooked. Ouch.)

Coma.

Rebooted, waited 2+. Powers up fine.

I'm surmising it has something to do with what happens with a new notification. Android and notification bug? Who knew?

Later: I waited 10 min with the "old" (rebooted over) sms notification and went comatose. Rebooting - there's a new email notification, but I wasn't getting an LED for that before my 1st coma.

I'm so hung up on this ROM that I'll wait and just stay the heck on top of my notifications, or just plug in when on wifi. Other than this it's been so stable, so fast/functional/trouble free, and with apps to SD, roomy. Just what you'd want in a new house, car, or anything else.