[Atrix 4G General] ryaske:
Holy crap am I happy to see this.

I had to replace my original atrix (purchased new) because the finger print reader stopped working and there was a faint halo around the edges of the screen.

Received "remanufactured replacement" from AT&T. The volume buttons rattle when the speaker is turned up loud. Awesome. However I could probably live with that.

What I cant live with is random rebooting multiple times per day!!! I first thought it was because of an app compatbility issue, but now after factory resetting I have done NOTHING else but turn on SD notiication sounds so I can hear when it reboots. But then it occurred to me .. I was still rooted.

Here are some system logs that capture the issue. This is what I see in the logs EVERY TIME it reboots. I have found the rebooting related to the radio .. If I go downstairs into my kitchen or move around outside .. it is more likely to reboot, and the logs show something going wonky with the radio (modem kernel panic)

03-16 01:42:35.604 1485 1586 E RDS : RdsReadSvrMsg: READ HEADER FAIL 0
03-16 01:42:35.607 1485 1586 E mdm_panicd: connection broken - recreate socket
03-16 01:42:35.607 1485 1586 I mdm_panicd: Subscribed to RDS_MSG_ID_UNSOL_IPC_FAILURE
03-16 01:42:35.607 1485 1586 I mdm_panicd: RDS Socket resd something on gUnsolicitedFd = 4
03-16 01:42:35.607 1485 1586 E mdm_panicd: Unsolicited message too short: expected at least 32 bytes, got 0
03-16 01:42:35.607 1485 1586 D mdm_panicd: Unsolicited thread finished
03-16 01:42:35.607 1485 1485 E mdm_panicd: /data/panicreports/mdm_panicd.log created successfully!
03-16 01:42:35.607 1485 1485 E mdm_panicd: Modem reset detected (BP_STATUS 0). Reboot system!

03-14 10:51:56.041 1545 1560 E RDS : RdsReadSvrMsg: READ HEADER FAIL 0
03-14 10:51:56.041 1545 1560 E mdm_panicd: connection broken - recreate socket
03-14 10:51:56.041 1545 1560 I mdm_panicd: Subscribed to RDS_MSG_ID_UNSOL_IPC_FAILURE
03-14 10:51:56.041 1545 1560 I mdm_panicd: RDS Socket resd something on gUnsolicitedFd = 4
03-14 10:51:56.041 1545 1560 E mdm_panicd: Unsolicited message too short: expected at least 32 bytes, g
ot 0
03-14 10:51:56.041 1545 1560 D mdm_panicd: Unsolicited thread finished
03-14 10:51:56.047 1545 1545 E mdm_panicd: /data/panicreports/mdm_panicd.log created successfully!
03-14 10:51:56.047 1545 1545 E mdm_panicd: Modem power down detected (BP_RESOUT). Reboot system!

This is apparently not an isolated issue if we are all having problems. I thought it was due to my import of previous apps, or the hardware of my replacement phone. I even went as far as requesting another warranty replacement! I now have both in my possession and it must be due to motorola's software update and because I always rooted first in order to import my stuff via Titanium backup.

But what was weird is that I factory reset warranty replacement #1 .. and did not reroot. IT still rebooted with the same error message in the logs!! Maybe some part of the prior rooting hangs around in the file system even after a factory reset? I know that in order to use titanimum backup I would have to go through the motions again after factory reset .. so.. what the heck? I'm going to use this second phone to try and figure out how to "unroot" completely. Since I can almost reproduce the rebooting on command I'll let everyone know if I figure it out..

If not, I'll unlock the phone I'm keeping and try CM7. Maybe that will work without reboots. I'm certainly not going to spend hours re-downloading all my apps and setting them up the same. (sticking with stock firmware and not rooting)

** Also I've devised a method to have the 4 log buffers saved automatically to your SD card in real-time. This is very helpful to capture the logs right before reboot. Let me konw if you want me to share this.. you will need root and shell access whether over adb or on the phone. However, I'm sure your logs are like mine. ONLY motorola's fault... no rooting on the new update. Just terrific..