reboots on 2.1

[Guest stevebo]

I'm running 2.1 r6 and the phone reboots nothing strange there, but only when I'm in the office when I'm at home it doesn't reboot not a single time, it also seems to be when receiving data like a tweet or gmail

the only difference between home and work is I have a 3g signal at work and not at home, so this morning after it rebooted 3 times in 2 hours i tried turning the 3g off and used the office wifi and I've not had a single reboot all day.

What do you guys think give it a try.

[Guest Simon O]

I'm running 2.1 r6 and the phone reboots nothing strange there, but only when I'm in the office when I'm at home it doesn't reboot not a single time, it also seems to be when receiving data like a tweet or gmail

the only difference between home and work is I have a 3g signal at work and not at home, so this morning after it rebooted 3 times in 2 hours i tried turning the 3g off and used the office wifi and I've not had a single reboot all day.

What do you guys think give it a try.

Yeah I experience this issue also. It seems to be a problem with the radio.

[Guest sbadger]

I'm running 2.1 r6 and the phone reboots nothing strange there, but only when I'm in the office when I'm at home it doesn't reboot not a single time, it also seems to be when receiving data like a tweet or gmail

the only difference between home and work is I have a 3g signal at work and not at home, so this morning after it rebooted 3 times in 2 hours i tried turning the 3g off and used the office wifi and I've not had a single reboot all day.

What do you guys think give it a try.

It's certainly the cause of one of the types of reboot 2.1 has caused. I think the general agreement is that the phone can't manage a situation where the data connection changes from 3G to 2G rapidly, ie in places with a weak 3G signal. Unfortunately it's extremely difficult (for me anyway!) to even diagnose the exact issue as logcat automatically wipes the log after a hard reset.

[Guest gusthy]

It's certainly the cause of one of the types of reboot 2.1 has caused. I think the general agreement is that the phone can't manage a situation where the data connection changes from 3G to 2G rapidly, ie in places with a weak 3G signal. Unfortunately it's extremely difficult (for me anyway!) to even diagnose the exact issue as logcat automatically wipes the log after a hard reset.

To diagnose, start logcat on the phone from a terminal. you can diagnose android with "logcat -v" or radio with "logcat -b radio".

you can tell on the terminal (for example Better Terminal):

su

logcat -b radio >/sdcard/log&

then exit terminal.

after reboot you find the log on sdcard.

[Guest makmondeja]

3G it's the main reason of reboots. That's for sure.

[Guest Josh04]

To diagnose, start logcat on the phone from a terminal. you can diagnose android with "logcat -v" or radio with "logcat -b radio".

you can tell on the terminal (for example Better Terminal):

su

logcat -b radio >/sdcard/log&

then exit terminal.

after reboot you find the log on sdcard.

Do you have any saved logs of this?

[Guest sbadger]

Thanks gushty. Last few lines of the radio logcat from my last reboot (phone wasn't being used and had sat idle for at least 15 minutes) I can't see anything interesting.

D/RILJ ( 1236): [1852]< QUERY_NETWORK_SELECTION_MODE {0}

D/RILJ ( 1236): [1856]< QUERY_NETWORK_SELECTION_MODE {0}

D/GSM ( 1236): GSMDataConnTrack handleMessage { what=6 when=13137028 obj=android.os.AsyncResult@44ee2b18 }

D/GSM ( 1236): Poll ServiceState done: oldSS=[0 home Telefonica O2 UK Limited O2 23410 UMTS CSS not supported -1 -1RoamInd: -1DefRoamInd: -1] newSS=[0 home Telefonica O2 UK Limited O2 23410 UMTS CSS not supported -1 -1RoamInd: -1DefRoamInd: -1] oldGprs=0 newGprs=0 oldType=UMTS newType=UMTS

D/RILJ ( 1236): [1857]> REQUEST_SET_LOCATION_UPDATES: true

D/RILC ( 1081): [RIL qcril.c 2101] UI --- RIL_REQUEST_SET_LOCATION_UPDATES (76) ---> RIL [token id 1857, data len 4]

D/RILC ( 1081): [RIL qcril.c 2120] Android=>RIL [ label = "RIL_REQUEST_SET_LOCATION_UPDATES - Token 1857" ];

D/RILC ( 1081): [RIL qcril_cm.c 5377] RIL_REQUEST_SET_LOCATION_UPDATES input = 1

D/RILC ( 1081): [RIL qcril.c 3590] RIL=>Android [ label = "RIL_REQUEST_SET_LOCATION_UPDATES - Token 1857, Success" ];

D/RILC ( 1081): [RIL qcril.c 3595] UI <--- RIL_REQUEST_SET_LOCATION_UPDATES (76) Complete --- RIL [Token 1857, RIL_E_SUCCESS, Len 0 ]

D/RILJ ( 1236): [1857]< REQUEST_SET_LOCATION_UPDATES

D/RILJ ( 1236): [1858]> REGISTRATION_STATE

D/RILC ( 1081): [RIL qcril.c 2101] UI --- RIL_REQUEST_REGISTRATION_STATE (20) ---> RIL [token id 1858, data len 0]

D/RILC ( 1081): [RIL qcril.c 2120] Android=>RIL [ label = "RIL_REQUEST_REGISTRATION_STATE - Token 1858" ];

D/RILC ( 1081): [RIL qcril_cm_util.c 1332] Reject cause value = 0

D/RILC ( 1081): [RIL qcril_cm_util.c 1333] Registration status = Registered (Home network)

D/RILC ( 1081): [RIL qcril_cm_util.c 1393] Reject cause value sent to UI = 0

D/RILC ( 1081): [RIL qcril_cm_util.c 426] UMTS System

D/RILC ( 1081): [RIL qcril_cm.c 4643] Registration State: Registered (Home network), RadioTech: UMTS, LAC: 7db0, CID: 005e5dbf, BSID: (null), BSLat: (null), BSLong: (null)

D/RILC ( 1081): [RIL qcril_cm.c 4646] CCS: (null), SID: (null), NID: (null), RoamStatus: (null), PRL: (null), DefRoamStatus: (null), RejReason: 0

D/RILC ( 1081): [RIL qcril.c 3590] RIL=>Android [ label = "RIL_REQUEST_REGISTRATION_STATE - Registered (Home network), Token 1858, Success" ];

D/RILC ( 1081): [RIL qcril.c 3595] UI <--- RIL_REQUEST_REGISTRATION_STATE (20) Complete --- RIL [Token 1858, RIL_E_SUCCESS, Len 56 Registered (Home network)]

D/RILJ ( 1236): [1858]< REGISTRATION_STATE {1, 7db0, 005e5dbf, 3, null, null, null, null, null, null, null, null, null, 0}

D/RILJ ( 1236): [1859]> SCREEN_STATE: false

D/RILC ( 1081): [RIL qcril.c 2101] UI --- RIL_REQUEST_SCREEN_STATE (61) ---> RIL [token id 1859, data len 4]

D/RILC ( 1081): [RIL qcril.c 2115] Android=>RIL [ label = "RIL_REQUEST_SCREEN_STATE - Off, Token 1859" ];

D/RILC ( 1081): [RIL qcril_cm.c 5208] De-registering the RSSI and HDR RSSI events on screen-off request

D/RILC ( 1081): [RIL qcril_cm.c 5210] RIL --- cm_mm_client_ss_reg() ---> AMSS [client_id 23 (0x17)]

D/RILC ( 1081): [RIL qcril_cm.c 5222] RIL --- cm_mm_client_ss_reg() ---> AMSS [client_id 23 (0x17)]

D/RILC ( 1081): [RIL qcril_cm.c 5235] Reply to RIL --> Screen off

D/RILC ( 1081): [RIL qcril.c 3590] RIL=>Android [ label = "RIL_REQUEST_SCREEN_STATE - Off, Token 1859, Success" ];

D/RILC ( 1081): [RIL qcril.c 3595] UI <--- RIL_REQUEST_SCREEN_STATE (61) Complete --- RIL [Token 1859, RIL_E_SUCCESS, Len 0 Off]

D/RILJ ( 1236): [1859]< SCREEN_STATE

D/GSM ( 1236): [DataConnection] Stop poll NetStat

D/GSM ( 1236): [DataConnection] Start poll NetStat

D/RILJ ( 1236): [1860]> REQUEST_SET_LOCATION_UPDATES: false

D/RILC ( 1081): [RIL qcril.c 2101] UI --- RIL_REQUEST_SET_LOCATION_UPDATES (76) ---> RIL [token id 1860, data len 4]

D/RILC ( 1081): [RIL qcril.c 2120] Android=>RIL [ label = "RIL_REQUEST_SET_LOCATION_UPDATES - Token 1860" ];

D/RILC ( 1081): [RIL qcril_cm.c 5377] RIL_REQUEST_SET_LOCATION_UPDATES input = 0

D/RILC ( 1081): [RIL qcril.c 3590] RIL=>Android [ label = "RIL_REQUEST_SET_LOCATION_UPDATES - Token 1860, Success" ];

D/RILC ( 1081): [RIL qcril.c 3595] UI <--- RIL_REQUEST_SET_LOCATION_UPDATES (76) Complete --- RIL [Token 1860, RIL_E_SUCCESS, Len 0 ]

D/RILJ ( 1236): [1860]< REQUEST_SET_LOCATION_UPDATES

Edited May 27, 2010 by sbadger

[Guest thisweb]

3G it's the main reason of reboots. That's for sure.

I am in the US at the moment, I don't have 3g, its disabled, but still get reboots on 2g.