Sprint Hero Crashes on re-boot, Problem App?

[ngc2000]

I have an HTC Hero from Sprint. Twice now in 2 days, i have turned my phone off, and then on again, only to have numerous crash errors (com.android.phone has stopped - force close) etc. When the phone finally starts up, I have no service, and i can't even bring up the dial pad, without it crashing. Everything seems fine, but no service and no dial pad. Wi-Fi connections work. Before the re-boot, everything seemed to be working ok.

A hard reset fixes the problem, but doing that every day is getting annoying.

Sprint thinks its an App i installed, but there were 80 of them, and I don't want to remove them one by one, rebooting between uninstalls.

I'm wondering if anyone else has had this problem. Maybe we can compare apps to figure out the problem.

Or, does anyone know what kind of apps might do this?

thanks

[simms22]

I have an HTC Hero from Sprint. Twice now in 2 days, i have turned my phone off, and then on again, only to have numerous crash errors (com.android.phone has stopped - force close) etc. When the phone finally starts up, I have no service, and i can't even bring up the dial pad, without it crashing. Everything seems fine, but no service and no dial pad. Wi-Fi connections work. Before the re-boot, everything seemed to be working ok.

A hard reset fixes the problem, but doing that every day is getting annoying.

Sprint thinks its an App i installed, but there were 80 of them, and I don't want to remove them one by one, rebooting between uninstalls.

I'm wondering if anyone else has had this problem. Maybe we can compare apps to figure out the problem.

Or, does anyone know what kind of apps might do this?

thanks

how much free memory do you have on your phone ?
also , try this , reboot you phone , let it start up , let it sit for 2-3 minutes after booted without you touching it . then .using taskiller (found on the market free) , kill the background apps 1 by 1 . you might have many background apps starting up at the same time , and when you start using the phone , it becomes unresponsive , forcing those force close errors .

[ngc2000]

had lots of free space. tracked is down to the "Video Player" app

[mikeyrokschicago]

had lots of free space. tracked is down to the "Video Player" app

Hey, which exact video player app was the culprit?

[caguy83]

I'm having the same issue. What program was causing the issue for you?

I would be very interested in comparing installed apps to be sure the culprit program has been identified. I don't remember having a video player app installed.

Please let me know if you continue to have this issue.

Thanks.

[kronium]

I'm having the same problem, but have no video player installed. The problem is not very wide spread, so I'm thinking it may be a faulty phone. I've tried various software configurations, thought I solved the problem, then restart the phone only to get a bunch of force close errors. The phone does not connect to the Sprint network at all. I'm tired of Hard resetting every few days. I'll try a new phone tomorrow and let everyone know the status. Thanks!

UPDATE: Not sure if this is just a temporary fix, but when phone was powered on, I tried booting in safe mode, the phone reset, reboot, no safemode indication, but the phone loaded everything properly!

From HTC to enter safemode: Press the END CALL/POWER button and hold the MENU button until the system boots up to the Home Screen. Then the Safe mode notification will be shown on the bottom left of the display. In Safe mode, all 3rd party applications will not be executed so you can boot up your phone successfully to uninstall any applications which you may have recently installed or which may be stopping your phone from booting correctly.

[ngc2000]

Actually I've tracked down multiple apps now, that give me the same errors on boot up. If you remove them, it goes away. It makes me wonder if there is a major program compatibility issues with the Sprint HTC Hero's.

FYI, I have 70 MB of free internal memory, so I don't think that's an issue.

Here are the Market names for the apps causing problems:

"Java/J2ME Manager"
"Video Player"
"My Coupons"
"Gtaks"
"Handcent"
"CompSMS"
"Taskpanel X"
"Astrid"
"LocA"

Its getting very aggravating now. There must be a larger problem that need solving.

[ngc2000]

I've done 2 factory resets, and still have the problem. Could there be some other app that is indirectly causing these problems? how would I go about finding it?

[ngc2000]

I installed a log collector, and then handcent, and rebooted. I immediately ran the log collector get a message with lots of this:

Jbmm10-26 15:10:25.185 D/IQServer( 50): JavaRequestAlarmSet is failed... Will not release wakelock[ciq-backend]!
10-26 15:10:25.185 D/IQServer( 50): JavaRequestAlarmSet is failed... Will not release wakelock[ciq-backend]!
10-26 15:10:25.185 D/IQServer( 50): Reset the timeout to 3000(ms) for AlarmSet retry...
10-26 15:10:25.185 I/HtcLocationService( 194): onDestroy
10-26 15:10:25.185 D/LocationManager( 194): removeUpdates: listener = com.htc.htclocationservice.HtcLocationServiceAgent $7@434b5830
10-26 15:10:25.195 D/IQJavaJob( 50): JavaRequestAlarmSet: Java job client is not connected now!
10-26 15:10:25.195 D/IQServer( 50): JavaRequestAlarmSet is failed... Will not release wakelock[ciq-backend]!
10-26 15:10:25.195 D/IQServer( 50): Reset the timeout to 3000(ms) for AlarmSet retry...
10-26 15:10:25.195 D/IQJavaJob( 50): JavaRequestAlarmSet: Java job client is not connected now!
10-26 15:10:25.195 D/IQServer( 50): JavaRequestAlarmSet is failed... Will not release wakelock[ciq-backend]!
10-26 15:10:25.195 D/IQServer( 50): Reset the timeout to 3000(ms) for AlarmSet retry...
10-26 15:10:25.195 D/IQJavaJob( 50): JavaRequestAlarmSet: Java job client is not connected now!
10-26 15:10:25.195 D/IQServer( 50): JavaRequestAlarmSet is failed... Will not release wakelock[ciq-backend]!
10-26 15:10:25.195 D/IQServer( 50): Reset the timeout to 3000(ms) for AlarmSet retry...


any ideas???

[kronium]

I installed a log collector, and then handcent, and rebooted. I immediately ran the log collector get a message with lots of this:

Jbmm10-26 15:10:25.185 D/IQServer( 50): JavaRequestAlarmSet is failed... Will not release wakelock[ciq-backend]!
10-26 15:10:25.185 D/IQServer( 50): JavaRequestAlarmSet is failed... Will not release wakelock[ciq-backend]!
10-26 15:10:25.185 D/IQServer( 50): Reset the timeout to 3000(ms) for AlarmSet retry...
10-26 15:10:25.185 I/HtcLocationService( 194): onDestroy
10-26 15:10:25.185 D/LocationManager( 194): removeUpdates: listener = com.htc.htclocationservice.HtcLocationServiceAgent $7@434b5830
10-26 15:10:25.195 D/IQJavaJob( 50): JavaRequestAlarmSet: Java job client is not connected now!
10-26 15:10:25.195 D/IQServer( 50): JavaRequestAlarmSet is failed... Will not release wakelock[ciq-backend]!
10-26 15:10:25.195 D/IQServer( 50): Reset the timeout to 3000(ms) for AlarmSet retry...
10-26 15:10:25.195 D/IQJavaJob( 50): JavaRequestAlarmSet: Java job client is not connected now!
10-26 15:10:25.195 D/IQServer( 50): JavaRequestAlarmSet is failed... Will not release wakelock[ciq-backend]!
10-26 15:10:25.195 D/IQServer( 50): Reset the timeout to 3000(ms) for AlarmSet retry...
10-26 15:10:25.195 D/IQJavaJob( 50): JavaRequestAlarmSet: Java job client is not connected now!
10-26 15:10:25.195 D/IQServer( 50): JavaRequestAlarmSet is failed... Will not release wakelock[ciq-backend]!
10-26 15:10:25.195 D/IQServer( 50): Reset the timeout to 3000(ms) for AlarmSet retry...


any ideas???

Thank you for your work. I didn't get a chance to get a new Hero, but I think we may have faulty units, otherwise reports of this problem would be widespread. I'll try a new Hero tomorrow hopefully, if it keeps happening, I may exchange it for the Moment.