Forums - Connection Timedout

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

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

  • Up1
  • Down0
simon
Join Date: 20 Jan 20
Posts: 1
Posted: Fri, 2020-10-09 15:09

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

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

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
eshaw Moderator
Join Date: 12 May 16
Location: San Diego
Posts: 141
Posted: Mon, 2020-10-19 13:41

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
ritesh.patel2
Join Date: 15 Mar 22
Posts: 2
Posted: Wed, 2023-05-03 04:54

I have the same problem.
on ADB it shows below message.  Adb is connected via tcp connect "adb connect <ip address>:5555
what is the problem and can we enable more detailed debug log for you?

05-03 12:15:00.762 12747 12747 I SDP     : SDPCore.Service: Service initialized.
05-03 12:15:00.762 12747 12747 I SDP     : SDPCore.Service: Loading plugins from /data/local/tmp/SnapdragonProfiler...
05-03 12:15:00.762 12747 12747 I SDP     : SDPCore.Service: Found plugin executable '/data/local/tmp/SnapdragonProfiler/pluginGPU-GGPM'.
05-03 12:15:00.762 12747 12747 I SDP     : SDPCore.Service: Found plugin executable '/data/local/tmp/SnapdragonProfiler/pluginCPU'.
05-03 12:15:00.762 12747 12747 I SDP     : SDPCore.Service: Found plugin executable '/data/local/tmp/SnapdragonProfiler/pluginDSP-Sensor'.
05-03 12:15:00.762 12747 12747 I SDP     : SDPCore.Service: Found plugin executable '/data/local/tmp/SnapdragonProfiler/pluginNPUV2'.
05-03 12:15:00.762 12747 12747 I SDP     : SDPCore.Service: Found plugin executable '/data/local/tmp/SnapdragonProfiler/pluginGPU-OpenCL'.
05-03 12:15:00.762 12747 12747 I SDP     : SDPCore.Service: Found plugin executable '/data/local/tmp/SnapdragonProfiler/pluginGPU-OpenGLES'.
05-03 12:15:00.762 12747 12747 I SDP     : SDPCore.Service: Found plugin executable '/data/local/tmp/SnapdragonProfiler/pluginDDRBandwidth'.
05-03 12:15:00.762 12747 12747 I SDP     : SDPCore.Service: Found plugin executable '/data/local/tmp/SnapdragonProfiler/pluginThermal'.
05-03 12:15:00.762 12747 12747 I SDP     : SDPCore.Service: Found plugin executable '/data/local/tmp/SnapdragonProfiler/pluginNetwork'.
05-03 12:15:00.762 12747 12747 I SDP     : SDPCore.Service: Found plugin executable '/data/local/tmp/SnapdragonProfiler/pluginDSP-Compute'.
05-03 12:15:00.762 12747 12747 I SDP     : SDPCore.Service: Found plugin executable '/data/local/tmp/SnapdragonProfiler/pluginNPU'.
05-03 12:15:00.762 12747 12747 I SDP     : SDPCore.Service: Found plugin executable '/data/local/tmp/SnapdragonProfiler/pluginDSP-Application'.
05-03 12:15:00.762 12747 12747 I SDP     : SDPCore.Service: Found plugin executable '/data/local/tmp/SnapdragonProfiler/pluginGPU-Vulkan'.
05-03 12:15:00.762 12747 12747 I SDP     : SDPCore.Service: Found plugin executable '/data/local/tmp/SnapdragonProfiler/pluginSystrace'.
05-03 12:15:00.762 12747 12747 I SDP     : SDPCore.Service: Service attempting connection to client at 10.18.53.226:1000...
05-03 12:15:02.764 12747 12750 I SDP     : SDPCore.NetCommandClient: Client socket 0x00000001 closed
05-03 12:15:02.764 12747 12747 E SDP     : SDPCore.Service: Service failed to connect to the client - terminating...
05-03 12:15:02.764 12747 12747 I SDP     : SDPCore.Service: Service is ready to shutdown.
05-03 12:15:02.765 12747 12747 I SDP     : SDPCore.Service: Service is ready to shutdown.
05-03 12:15:02.765 12747 12747 I SDP     : SDPCore.Service: Service shutdown.
 

  • Up0
  • Down0
ritesh.patel2
Join Date: 15 Mar 22
Posts: 2
Posted: Fri, 2023-05-19 04:30

The issue got resolved by providing access in windows firewall for SDP app.

Realtime capture is working but capture trace and capture snapshot is not working

 

  • Up0
  • Down0
cmfordocuments
Join Date: 11 Dec 23
Posts: 1
Posted: Tue, 2023-12-12 21:48

I faced the exact same issue, but in my case, the problem was that my phone has a 32-bit architecture (armeabi-v7a, as it's a Moto G7 Play), and it seems that newer versions of Snapdragon Profiler do not support that, so I had to go back to using v2022.5 (https://developer.qualcomm.com/downloads/snapdragon-profiler-v20225-wind...). Is there a chance that future versions will support 32-bit again? If not, perhaps some documentation should mention this explicitly? Apologies if I missed any such mention; perhaps one would be able to derive this from the "supported chipsets" table in the reference guide, but I'm not very familiar with Qualcomm's naming/grouping conventions.

More details below in case anyone else is having a similar problem and wants some debugging ideas:

Inspired by meramcacahuete's posting of their logs, I looked at mine (under "Documents/SnapdragonProfiler"). The contents were very similar to meramcacahuete's, but I noticed one message that said: Found local simpleperf binary at '\arm64\simpleperf'

Here, the "arm64" was the first hint that something was wrong. Then I noticed the message: Starting service: adb -s 192.168.1.66:5555 shell LD_LIBRARY_PATH=/data/local/tmp/SnapdragonProfiler /data/local/tmp/SnapdragonProfiler/sdpservice -clientIP 192.168.56.1 -clientIP 192.168.1.64 -cmdNetPort 6500

The logs did not contain anything indicating that this command encountered errors (other than the much later "connection failed") but when I tried the same command from Powershell, the output revealed the problem, that sdpservice was a 64-bit executable: /data/local/tmp/SnapdragonProfiler/sdpservice: not executable: 64-bit ELF file

In other words, if you experience problems and the logs aren't revealing the problem, perhaps running the adb command yourself will help you in the same way it helped me. Best of luck to anyone coming across this and looking into their own connection problems :-)

  • 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.