Custom ROMs resetting

[Guest Ashbeard]

All the custom ROMs on this site (1.7/1.8/t-mobile/vanilla have a recurring problem for me in that they reset at random intervals. This usually happens while it is asleep in my pocket so I theorised that it might be related to the unlock screen when a button gets accidentally pressed. However it has been the case that a reset has occurred whenever the phone has just been lying on a surface with no external forces to activate the unlock screen. On all occasions however the phone has been asleep.

I tried a couple of programs with log viewers to see if they could provide any clues but the logs seem very long and seem to update too frequently to be able to scroll back far. I have tried with an ext partition and without, tried with rooting and without and the problem still occurs.

Does anybody have other ideas as to what may cause this, or can offer tips on how to troubleshoot. I would be very grateful for any help you can provide, as the custom ROMs seem to be faster, but suffer in stability.

[Guest BigBearMDC]

Sorry, but for me that looks like a harware fault ;)

Greetings,

BigBear

[Guest jonathonf]

This happens with me from time to time. It seems to happen when it's switching connections. I live in a marginal signal area so the GSM radio is constantly registering/deregistering unless I put the phone in a particular place in the house, so the times when I'm using it I have Wifi turned on. The main issues I've had with the ROM is with connectivity - the phone sometimes thinks it's on wifi so doesn't use GSM, sometimes thinks it's still on GSM so doesn't use 3G, sometimes uses GSM or 3G despite having wifi turned on, and with no coverage and wifi connected it still doesn't think it has internet access (and any other combinations you care to come up with).

Oh, plus if I have it plugged in to my PC via USB then turn the PC off the phone doesn't register the disconnect and so stays the whole day thinking USB is connected.

Anyhow - the last time I noticed the phone restart was when I picked it up and it lost network coverage then tried to wake wifi. To me it sounds like a driver issue. I'm waiting for 1.6+.

[Guest Ashbeard]

Sorry, but for me that looks like a harware fault ;)

Greetings,

BigBear

It doesn't happen with the official ROMs though, just the custom ones. I usually have good signal, I don't think it drops out to 2G often.

Edited February 12, 2010 by Ashbeard

[Guest BigBearMDC]

It doesn't happen with the official ROMs though, just the custom ones. I usually have good signal, I don't think it drops out to 2G often.

Maybe it has something to do with your Baseband?

Greetings,

BigBear

[Guest Ashbeard]

This happens with me from time to time. It seems to happen when it's switching connections. I live in a marginal signal area so the GSM radio is constantly registering/deregistering unless I put the phone in a particular place in the house, so the times when I'm using it I have Wifi turned on. The main issues I've had with the ROM is with connectivity - the phone sometimes thinks it's on wifi so doesn't use GSM, sometimes thinks it's still on GSM so doesn't use 3G, sometimes uses GSM or 3G despite having wifi turned on, and with no coverage and wifi connected it still doesn't think it has internet access (and any other combinations you care to come up with).

Oh, plus if I have it plugged in to my PC via USB then turn the PC off the phone doesn't register the disconnect and so stays the whole day thinking USB is connected.

Anyhow - the last time I noticed the phone restart was when I picked it up and it lost network coverage then tried to wake wifi. To me it sounds like a driver issue. I'm waiting for 1.6+.

I think this is my issue here too. I noticed that the wifi signal was low after the reset. I think it must have dropped and tried to switch to 3G. A strange symptom is that when it starts up again, all sorts of programs are running like mixzing music player, the calendar and roadsync. I don't use calendar sync and definitely don't use exchange. Well, only a month or so to wait for our 2.1 update (fingers crossed).