|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.
Hi Richard,
tcpdump option
It worked with a full pathname. I have added a "bad" (adb server port 5615, emulator port 5613)
and a "good" log (adb server port 5613, emulator port 5611)
https://github.com/ITobiI/Android-Problem-Jenkins/tree/master/EmulatorTcpdump.
Wireshark
I recorded some communication and uploaded a "good" (adb server port 5751, emulator port 5749)
and "bad" (adb server port 5753, emulator port 5751)
log too https://github.com/ITobiI/Android-Problem-Jenkins/tree/master/Wireshark.
I tried to look into it but it's hard to comprehend these files. I hope the logs will help.
Edit:
I forgot to say that there are two adb processes at the beginning and after 1 or 2 seconds only 1 left. So there aren't any other adb servers running.