android ADB Connection issue to simulator.

I keep getting the following error after android app and watch app briefly connect and the shuts down.

03-12 19:53:26.324 22157-22196/com.garmin.android.apps.connectiq.sample.comm E/ConnectIQ-AdbConnection: Error reading input stream
java.net.SocketException: Try again
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:151)
at java.net.SocketInputStream.read(SocketInputStream.java:120)
at java.io.BufferedInputStream.read1(BufferedInputStream.java:273)
at java.io.BufferedInputStream.read(BufferedInputStream.java:334)
at com.garmin.android.connectiq.adb.AdbConnection$ServerThread.run(AdbConnection.java:104)
at java.lang.Thread.run(Thread.java:761)
03-12 19:53:26.324 22157-22196/com.garmin.android.apps.connectiq.sample.comm D/ConnectIQ-AdbConnection: Client connection shut down.
03-12 19:53:26.338 22157-22196/com.garmin.android.apps.connectiq.sample.comm I/System.out: close [socket][::/:::7381]

Anyone experienced the same issue?
  • I keep getting the following error after android app and watch app briefly connect and the shuts down.

    03-12 19:53:26.324 22157-22196/com.garmin.android.apps.connectiq.sample.comm E/ConnectIQ-AdbConnection: Error reading input stream
    java.net.SocketException: Try again
    at java.net.SocketInputStream.socketRead0(Native Method)
    at java.net.SocketInputStream.read(SocketInputStream.java:151)
    at java.net.SocketInputStream.read(SocketInputStream.java:120)
    at java.io.BufferedInputStream.read1(BufferedInputStream.java:273)
    at java.io.BufferedInputStream.read(BufferedInputStream.java:334)
    at com.garmin.android.connectiq.adb.AdbConnection$ServerThread.run(AdbConnection.java:104)
    at java.lang.Thread.run(Thread.java:761)
    03-12 19:53:26.324 22157-22196/com.garmin.android.apps.connectiq.sample.comm D/ConnectIQ-AdbConnection: Client connection shut down.
    03-12 19:53:26.338 22157-22196/com.garmin.android.apps.connectiq.sample.comm I/System.out: close [socket][::/:::7381]

    Anyone experienced the same issue?