Jon Sims

I am seeing this myself too: ``` - BROWSERMOB_PORT=7500 - ./browsermob-proxy-2.1.4/bin/browsermob-proxy -port $BROWSERMOB_PORT >> $DEVICEFARM_LOG_DIR/browsermob.log 2>&1 & - >- start_proxy_timeout=0; PROXY_PORT=$(curl -X POST http://localhost:$BROWSERMOB_PORT/proxy | grep "port" | cut -d":"...

+1, I am seeing this exact same issue in some code I am running, where the newCommandTimeout is being set high (e.g. 300 seconds), but commands which wait around 60...

Hey @soppag, I'm not sure if this is the same issue. My S6 edges and edge+s, as well as S7s have never frozen during a test case. Try looking into...

Unfortunately, that fix didnt solve my original issue :( The APK is probably installing correctly for me, but the issue is in the APK starting and communicating with ADB over...

Also did some other platform debugging, and replicated the error with Python2.7 and on macOS, so it's definitely an issue isolated to the ADB-UIAutomator stack

Thanks for the suggestion. I've ran into some problems with adb's curl command where it doesnt parse the command line option for data properly: ` $ adb shell curl -d...

Got it working! I enclosed all the arguments in a big single-quotes quote, and it works fine. The non-working phone returns a response just as quickly as a working phone:...

I've found that, when running an instance of uiautomator, I get the following results when trying to ping() ports: working phone: | | pinging the local port | pinging the...

@yanglikai0806 Unfortunately I've already tried this. From another thread about the RPC server not starting, they mention some ADB commands to manually uninstall and reinstall the uiautomator apk and other...