View Single Post
  #212 (permalink)  
Old 07-27-2011, 07:34 PM
arrrghhh's Avatar
arrrghhh
Testing Extraordinaire
Offline
 
Join Date: Mar 2007
Posts: 3,604
Reputation: 7360
arrrghhh is a trusted member of the communityarrrghhh is a trusted member of the communityarrrghhh is a trusted member of the communityarrrghhh is a trusted member of the communityarrrghhh is a trusted member of the communityarrrghhh is a trusted member of the communityarrrghhh is a trusted member of the communityarrrghhh is a trusted member of the communityarrrghhh is a trusted member of the communityarrrghhh is a trusted member of the communityarrrghhh is a trusted member of the community
Mentioned: 7 Post(s)
Tagged: 0 Thread(s)
Re: Workarounds/known issues 7/22: Updated for FRX07

Quote:
Originally Posted by Jmz View Post
Which logs would you like and what conditions would you want? Like start capture just before trying to swap till reboot? Or create brand new data.img and do it that way? Just want to get useful information for you without trying multiple times

Sent from my TP2 Android using PPCGeeks app
Well dmesg and logcat at the very least. Radio logcat would probably be useful as well..

The best way would probably be to reboot, and first thing after the system comes up, plug in usb and get all three logs running at the same time. Then recreate the error and *hopefully* the logs will enlighten on what is the problem.

Can you also try the usual crap - update your rootfs/kernel, try a new data.img, etc... I'm not sure what would effect this, but I don't think too many people are going to use this feature.

I was thinking about snagging one of my friend's SIM cards that is on GSM, but then I would have to unlock my SIM slot... hum, crap.

Oh, and be prepared to run this multiple times. Troubleshooting isn't easy, especially when reboots to WinMo are involved (which usually indicates a kernel panic...)
Reply With Quote