When I turn off my screen, I usually can get back to it in the usual way (pressing the End button), Sometimes, especially after several hours in an idle state, turning the screen back on causes the phone to reboot. I don't know whether the phone powers itself off during the idle period and pressing the button just starts it up, or whether the phone remains in standby, but pressing the button causes an unnecessary reboot. The former is far worse than the latter, since the former implies that the phone turns off at random, making it a useless and unreliable instrument. There is no notification that either event has occurred, nor do I get the choice screen (which includes Power Off) when I turn off the screen.
This problem, which I never experienced with my HTC Hero before the upgrade, needs to be resolved quickly!!!
5/24: Here is a little more information I have gathered.
1. The length of time the screen is off apparently has nothing to do with the problem. I just locked the screen then remembered something else I had to check. Clicking the End Button within 5 seconds of the screen lock caused a reboot.
2. Connecting the charger to or disconnecting it from the phone can also, by itself, cause a reboot.
3. Reactivating the screen after a timed-out (as opposed to forced) screen lock sometimes causes a reboot.
The problem actually seems to be the phone turns itself off whenever it feels like it. This morning, I did a screen activation (End buton) and observed a reboot. There were two calls and an email that I had missed. Since I received no notification of any of these while the screen was locked (and the phone was sitting about 2 feet away on my desk, set to maximum ring/notification volume), I assume that the phone was in an off state rather than a simple screen locked state (unfortunately, you can't tell them apart). The battery is good and fully charged. The problem is as likely to occur when AC power is supplied or when running on battery power. The only way I can use this phone now is to turn the screen brightness all the way down, set the timeout interval to never lock the screen, and hope the battery makes it through the day.
Had this issue been a "feature" of HTC Hero from the beginning, I guarantee not a single one would have been sold.
--- 5/24 @ 7:00 PM ---------------
Out of of desperation, I decided to try the recommendation in the fifth post in this discussion, i.e., backup all my data, hard reset the phone (complete erasure of apps and data), then reload the apps and data. I finished this about an hour ago and will let everybody know what happens. If it (appears) to solve the problem, I'll be back in a few days to report this. If it doesn't, I'll probably be back sooner. Here's hoping.
-- 5/26 @ 1:30 PM ---------------
The hard reset didn't fix my problem. I had two unexpected shutdown/reboot events in the 12 hours after reinstalling everything. To help tell if the phone powered itself off, I went to the Market and downloaded a free app called Grandfather Clock. I now get volume-controllable Westminster chimes every quarter hour and the hourly strikes. Since installing this app (which is a pretty neat app), I have not had any unexpected shudowns or reboots. My phone has been up for over 26 hours now, a new record since installing 2.1. The app has a fairly small footprint (900K) and uses no discernible battery power, so if you have having the same problem, try downloading and installing this app (set the chime volume to 0 if you don't want the chimes), and let me know whether that works for you.
Message was edited by: ridgecat
I brought mine in to a Service Center. First they replaced the battery and did a Hard Reset on the phone. Then I went home and the problem happened again. The next day I brought it back and they ordered a replacement.
Since replacing it, I have had no issues.
I took mine into the Sprint repair center yesterday and they tried reinstalling the update - it didn't work. I also have the dust under the screen issue with my Hero, so for both reasons, they ordered me a replacement and it should be in my hands in 2-3 days they said.
I received my replacement phone yesterday. I charged it fully and then performed the upgrade first thing. I have not had the rebooting issue once since I powered up about 12 hours ago. It is looking like this unit does not have the same problem.
During the reinstall and setup I noticed that it went very smooth this time. On my original phone it basically froze when I was going through the Flickr account setup. I think I had to pull the battery to reboot, so I'm wondering if there is any relationship there.
Anyway, I hope everyone else has success resolving their issue as well.
I'm glad to hear/see that you're random rebooting experience is over with thus far! It's so frustrating!
I must say though, I am finding it hard to believe that this program/app that you installed is what saved your phone from the reboot/reset anomaly.
But, whatever did the trick for you, I'm really happy that it's working!!! Way to go yo!
I am far from an expert on the innards of this phone, although I did have a 40-year career as a systems software developer. The reason the app works (IMHO) is that it puts a Partial-Wait Lock on itself when it starts. This forces it to run all the time, but it isn't doing much: just waiting for the next time to chime. If this is done correctly (i.e., asynchronously), it will consume virtually no CPU cycles most of the time, but it will prevent the phone from turning off unless directed to do so by the user. To illustrate, the app has used about 57 seconds of CPU time in the last 30 hours or so, about 0.05% of the available cycles. It doesn't seem to use any between chime periods, so I suppose this represents the effort to create and play the chimes and hourly strikes.
THIS IS JUST A WORK-AROUND, IT IS NOT A FIX!!! There may be a firmware issue, in which case an MR issued by Android/HTC/Sprint will be needed. Or it could be an incompatibility between the new firmware and an older hardware rev level (after all, my phone is about 6 months old) which could be fixed by an MR or a new phone. I'm leaning toward the former because the randomness of this issue suggests to me that an uninitialized variable might be to blame. In any case, I can live with this solution for now.
I would recommend to anyone having problems to redo the update, then ise it for a while with no added programs and see if you are having the same issues. If problems go away, then add your programs back ONE AT A TIME and use the phone for a few hours and see how it is. IF no problems the load ONE more program etc until you find the one or ones causing your particular issue. Then try to reconfigure the offending program to work with your phone better. If it still causes problems get rid of it, and contact the author.
Loading a new operating system, and then dumping several programs into it by restoring backups is asking for trouble. those programs were configured for 1.5 not 2.1
Start bare and work your way up to more apps by reinstalling them from the market.
I went to Sprint and they did a hard reset and reinstalled the update. No need to say that it did not work. I took my cell phone back to Sprint a couple of hours later and they gave me a replacement. Now everything is just the way it should be. Back to loving my phone.
This is beginning to become a well-documented issue. It has nothing to do with the GPS being on or off, installed applications, or any other random thing you can think of. I know because I have tried them all.
Got my replacement phone from Sprint yesterday. It was quite obviously a refurb, because when I opened it to install the battery, there was a pretty good amount of dirt/dust around the lip of the casing and in some of the crevices (documented with pictures). I wasn't too happy to see that, but if the phone worked I would have been okay with it. Sadly, the earpiece on the phone sounds like it has a blown speaker. I took it into a Sprint repair center, the tech listened to it for about 5 seconds and agreed with me. They are now sending me ANOTHER phone which should be in today or tomorrow. Hopefully this one is in better condition than the first. I haven't even bothered to try installing the 2.1 ROM on this one.
I upgraded to 2.1 yesterday and I have the same issue. It rebooted several times since yesterday.
I have yet to find the pattern. I think it is rebooting every other time I unlock it. Also happening when I hang up a call. It is really frustrating. I waited all these months for an update and now I wish I hadn't upgrade to 2.1 . I am going to go to a Sprint store at lunch.