Quote:
Originally Posted by arrrghhh
Well since the phone reboots, it's a little complex. First, you must setup adb. Once that is setup, run adb logcat > output.txt - it'll run constantly, outputting to that file. Then the fun begins. You'll have to reproduce the error with this running. Devs may also need a logcat -b radio as well... I guess I should just make a bunch of phone calls to try and recreate the issue.
This project is still very much in testing - not meant for daily use around office meetings  |
Haha ... good point! I wasn't actually in a meeting. But those who were heard my speakerphone at full blast
. I assume I run the adb commands using my PC with DroidExplorer installed? If so I guess I should reproduce the issue with the phone connected to my PC?