I just wanted to let you guys know that Sprints device operational support has duplicated the issue...
Well, I must have good timing to see this kind of news just as I make my first post. So, Bigge, what is your affiliation with Sprint? And your source for this news? Does the log service note FC's and the processes that start, stop, and exit/crash? I may consider loading it.... Oh, and this theory (of cause) would imply that the Hero is very likely to have this same fault - does it?
BTW, Here is my experience on this phone bug:
Got my Mo' on 12/23 and saw this happen twice, requiring a Power-Down reboot (via the RED-button menu), my first disappointment! Hoped it was me, now know better... Have been on vacation for these two weeks and not near a WF, so I turned it off and had not seen the problem again for all this time.
After reading through this thread, I enabled WF ON/OFF/ON (there is no connection here tho). Listening to podcast for an hour w/ phone on USB charger, I just picked it up (after an hour) and have the X on the bars. This is not Airplane mode, tho, right? Just NO service at all, not even ability to roam. However, airplane mode (via native settings) indicates was ON, so clicked it off (but still no signal) and then did power down and back up. No indication of searching for signal (which is normal), but X went away and signal appears normal.
I have MANY downloaded apps and the "One-Click" widgets for BT, WF, GPS, and Vibrate. Found them to be just what I liked.
I will force the failure a few more times and try the 2G/3G switch as well...
Good to be here and read from the experience of so many other users - thanks for taking the time to describe, vent, explore, and brag...