Have you seen this<http://stackoverflow.com/questions/11300773/error-running-systrace-tool-in-adb-using-a-jelly-bean-4-1-emulator-on-windows-7>? It sounds like the script doesn't play nice on Windows...but that seems like too obvious of an error to go overlooked. Either way, running it in Linux is a good way to sidestep the issue.
On Tuesday, July 3, 2012 9:25:55 PM UTC-4, jlum wrote: > > I'm having problems getting systrace to work on Windows7 64-bit. I > have Python 2.7 64-bit installed on my PC. I have enabled tracing > through Settings > Developer options > Monitoring > Enable traces. > > Here's the output from Command Prompt: > > C:\Android SDK\android-sdk_r07-windows\android-sdk-windows\tools > \systrace>systrace.py > Traceback (most recent call last): > File "C:\Android SDK\android-sdk_r07-windows\android-sdk-windows > \tools\systrace\systrace.py", line 212, in <module> > main() > File "C:\Android SDK\android-sdk_r07-windows\android-sdk-windows > \tools\systrace\systrace.py", line 124, in main > ready = select.select([adb.stdout, adb.stderr], [], [adb.stdout, > adb.stderr]) > select.error: (10093, 'Either the application has not called > WSAStartup, or WSAStartup failed') > > Any ideas? Thanks. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
