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
FYI - Make sure you go to a Sprint Store that have a Service Center. Most of their locations are just sales hubs, and can't actually service your phone or provide replacements. I had to go through that hassle.
Call ahead if your not sure.
Thanks for the tip.
This is crazy now, I am ready to go to Sprint store to show them the issue and now my phone doesn't do what it did all night last night and this morning. I was not able to duplicate the issue in last hour or so. If I go to Sprint store now I am pretty sure they think I am crazy. I hate these intermittent problems.
The reboot as you hang up on a call was especially annoying. It actually disconnected on a call (to Sprint) in order to reboot which just added more fuel to the fire.
In other news, I just installed the 2.1 software on Hero #2 (replacement #1 that has a bad earpiece) as an experiment since I will be getting another one from them today or most likely tomorrow. In my experience, the RUU is generally stable for around 1 hour before it starts rebooting randomly. I will let you all know how it goes.
Message was edited by: dctex777
Print this thread, and I'm sure they will listen to you.
I didn't have to reproduce the issue, they simply took my word for it. I'm sure it's a pretty well known issue at their locations already.
Just to update everyone...my replacement Hero has not rebooted once since I received it, upgraded, and reloaded software.
It really appears that replacing the phone is the solution. Something is getting corrupted during upgrades that doesn't seem repairable. Just my two cents.
I agree. There have been a lot of irrelevancies introduced here. At this point, I am convinced that the update image itself is flawed. A lot of people got new phones, but were not helped. Others seemed to get it fixed on the first replacement. I wonder if the latter group is getting phones with the 2,1 release already installed at the point of manufacture, or the people updating are using a different image than the one we peasants download from the net. I've always been a big fan of posting SHA1 (or at the very least, MD5) checksums for critical downloads so we can verify them once they are received.
Anyway, I redownloaded the executable installer and reinstalled the update, did a hard reset afterward, and am now waiting to see what happens. I haven't installed any of my apps nor have I setup my Google mail accounts. If the platform remains stable, I'll do that later. The Grandfather Clock app work-around was effective simply because that app runs under a self-imposed PartialWait lock, which prevents the phone from ever sleeping. It does chew up battery life, however, because the awake time and up time are always the same. Normally, the awake time is a small fraction of the up time, so the phone spends most of its life snoozing, waiting for some external event to occur.
Next step after that is a phone replacement. I hate to do that if they are handing out refurbs. I take good care of my stuff, and I'm not interested in trading with somebody who doesn't!
The replacement phone I received from Sprint was refurbished, and loaded with the 1.5 software. I updated to the 2.1 ROM almost 2 hours ago and it seems like everything went well as I have not experienced the reboot issues as before. That being said, I will be giving this phone back to Sprint in the next 24 hours as soon as my next replacement comes in.
My theory is that there is a hardware fault of some kind that is marginally common amongst the HTC Hero phones...the phones that fall victim to this hardware fault are experiencing the reboot issue and those who do not have the hardware fault are not. That's just my .02.
Notes to add to the loose ends ridgecat brought up...
I did the first 2.1 update from a computer at the my office, and immediately updated a co-workers phone as well. Same image, same application same computer.
After having my phone replaced, it came with the 1.5 OS, so I had to upgrade that to 2.1 when I got it home. Did the update at home and havent had a problem.
So I believe its probably a flawed memory location in the actual hardware (only on some phones) of the phone that just was never accessed by the previous OS. Just my thought.
Could very well be something along those lines. Just for clarification, when you did the update at the office, did your phone exhibit the problem, but your coworker's did not? If so, that makes the marginal hardware possibility very, very plausible.
It would be interesting if Sprint, or more to the point, HTC, would ring in with a policy statement on this issue. There has been a lot of time and effort expended by the user community on identifying and isolating this major failure. I've heard nothing official from the guys making the $$$.
After putting up with the problem for 24 hours, I took my phone to the Sprint store on Monday and they tried doing a hard reset and reinstall of the update. It still did the same thing. They ordered me a replacement phone. It came already yesterday (Wed) and they performed the update to 2.1 at the store when I picked it up. I've had it now for about 36 hours and it has not restarted itself even once. I've installed several of the apps I use and still no problems.
For those of you who are trying to "solve" this problem yourself or use some wacky workaround, I would recommend giving up and just going to Sprint and getting a new phone - apparently there was a bad batch from HTC or something because it does seem like many of the people who are having this problem got their phone around the same time as me - Nov. 2009. While I do suspect that my replacement is a refurb, it looks brand new to me and I see no flaws whatsoever with it ... and I'm pretty picky when it comes to that kind of thing. I take very good care of my phones and they usually look like they haven't even been used after a year or two.
I am experiencing the same random reboot issue. My wife and I have the same models purchased at the same time (early Jan 2010). I ran the update on my phone first to evaluate it as she is less tolerant of issues . Luckily, I have not updated her phone yet!
So in summarizing what I have seen online, there are workarounds which keep your phone active but drain the battery. If you choose not to use a workaround, you are stuck with the power issue until the next update (after waiting so long for 2.1, I won't hold my breath) or talk to Sprint and get a replacement phone. In regards to the replacements coming out, are they being received with 2.1 already installed or is it still up to the user to perform the upgrade? It sounds like most of the contributors to this thread are leaning towards a hardware batch issue instead of an issue with the RUU release, correct? The closest Sprint service center is 1.5 hours from my residence, and I hate to drive that with out a good chance that things will work out in my favor...