Forums - Connection Timedout

4 posts / 0 new
or Register
Last post
Connection Timedout
meramcacahuete
Join Date: 16 Sep 20
Posts: 2
Posted: Wed, 2020-09-16 10:50
Top

Hello,

I'm trying to simply connect Profiler to my phone with those settings :

- ADB Version 1.0.41

- ADB devices return my device correctly

 

And I have the red link icon in SnapDragon Profiler,

I also tried to put timed out setting to 60s.

Here are the logs I found :

I: SDPCore: Scanning for devices...

I: SDPCore: Started QNX device scan

I: SDPCore: Started Integrity_RTOS device scan
I: SDPCore: Device added: 73ec5aa3 127.0.0.1
I: SDPCore: Device '73ec5aa3' discovered.
I: SDPCore: Device '73ec5aa3' ready.
I: SDPCore: Starting service: adb -s 73ec5aa3 shell LD_LIBRARY_PATH=/data/local/tmp/SnapdragonProfiler /data/local/tmp/SnapdragonProfiler/sdpservice -clientIP 127.0.0.1 -cmdNetPort 6500
I: SDPCore: Server socket 0x00000002 listening on tcp://0.0.0.0:6500
I: SDPCore: Listening for command net connections on port 6500...
E: SDPCore: Device '73ec5aa3' connection failed: Timed out waiting for a connection from the target device. Please try connecting again. If the problem persists, try increasing the connection timeout in File->Settings->Device..
I: SDPCore: Server socket 0x00000002 closed on tcp://0.0.0.0:6500
I: SDPCore: Device '73ec5aa3' ready.
I: SDPCore: Starting service: adb -s 73ec5aa3 shell LD_LIBRARY_PATH=/data/local/tmp/SnapdragonProfiler /data/local/tmp/SnapdragonProfiler/sdpservice -clientIP 127.0.0.1 -cmdNetPort 6500
I: SDPCore: Listening for command net connections on port 6500...
I: SDPCore: Server socket 0x00000002 listening on tcp://0.0.0.0:6500
E: SDPCore: Device '73ec5aa3' connection failed: Timed out waiting for a connection from the target device. Please try connecting again. If the problem persists, try increasing the connection timeout in File->Settings->Device..
I: SDPCore: Server socket 0x00000002 closed on tcp://0.0.0.0:6500
I: SDPCore: Device '73ec5aa3' ready.
I: SDPCore: Starting service: adb -s 73ec5aa3 shell LD_LIBRARY_PATH=/data/local/tmp/SnapdragonProfiler /data/local/tmp/SnapdragonProfiler/sdpservice -clientIP 127.0.0.1 -cmdNetPort 6500
I: SDPCore: Server socket 0x00000002 listening on tcp://0.0.0.0:6500
I: SDPCore: Listening for command net connections on port 6500...
E: SDPCore: Device '73ec5aa3' connection failed: Timed out waiting for a connection from the target device. Please try connecting again. If the problem persists, try increasing the connection timeout in File->Settings->Device..
I: SDPCore: Server socket 0x00000002 closed on tcp://0.0.0.0:6500
I: SDPCore: Device '73ec5aa3' ready.
I: SDPCore: Starting service: adb -s 73ec5aa3 shell LD_LIBRARY_PATH=/data/local/tmp/SnapdragonProfiler /data/local/tmp/SnapdragonProfiler/sdpservice -clientIP 127.0.0.1 -cmdNetPort 6500
I: SDPCore: Server socket 0x00000002 listening on tcp://0.0.0.0:6500
I: SDPCore: Listening for command net connections on port 6500...
E: SDPCore: Device '73ec5aa3' connection failed: Timed out waiting for a connection from the target device. Please try connecting again. If the problem persists, try increasing the connection timeout in File->Settings->Device..
I: SDPCore: Server socket 0x00000002 closed on tcp://0.0.0.0:6500
I: SDPCore: Device '73ec5aa3' ready.
 
 
 

It is simply timing out... My phone (OnePlus 6, Android 10, Oxygen 10.3.5)  is correctly setup with usb debug enabled and connected to my pc by USB.

 

If you have any suggestion, I would appreciate it :)

 

Thanks

  • Up0
  • Down0
Re: Connection Timedout
simon
Join Date: 20 Jan 20
Posts: 1
Posted: Fri, 2020-10-09 15:09
Top

Hi, I'm having the same problem, ADB 1.0.41, any solutions?

  • Up0
  • Down0
Re: Connection Timedout
meramcacahuete
Join Date: 16 Sep 20
Posts: 2
Posted: Mon, 2020-10-19 07:33
Top

Still the same problem... I need it to work for profiling Unity game, can somebody from Qualcomm can help us with that please ?

  • Up0
  • Down0
Re: Connection Timedout
eshaw Moderator
Join Date: 12 May 16
Location: San Diego
Posts: 126
Posted: Mon, 2020-10-19 13:41
Top

The most common cause of this type of issue is something on the host PC using the same network ports that Snapdragon Profiler uses. You can configure the ports used by Profiler in the application settings (File -> Settings -> Device -> Base network port. If that doesn't fix the problem you may have some firewall on your PC that is blocking incoming traffic on those ports.

Eric

  • Up0
  • Down0
or Register

Opinions expressed in the content posted here are the personal opinions of the original authors, and do not necessarily reflect those of Qualcomm Incorporated or its subsidiaries (“Qualcomm”). The content is provided for informational purposes only and is not meant to be an endorsement or representation by Qualcomm or any other party. This site may also provide links or references to non-Qualcomm sites and resources. Qualcomm makes no representations, warranties, or other commitments whatsoever about any non-Qualcomm sites or third-party resources that may be referenced, accessible from, or linked to this site.