Cannot see my Android device as a target in Defold Editor (DEF-1928) (SOLVED)

Thibault · October 25, 2016, 12:42pm

Hello,

I’m trying to run my game on my Android phone, but I can’t see it in “Project -> Target” menu

I have installed and launched dmengine.apk, and this is what I get in my logs:

01-31 13:37:47.572: I/art(19546): Late-enabling -Xcheck:jni
01-31 13:37:47.759: V/threaded_app(19546): Creating: 0xb4dfd120
01-31 13:37:47.759: V/threaded_app(19546): Config: mcc=208 mnc=15 lang=fr cnt=FR orien=1 touch=3 dens=560 keys=1 nav=1 keysHid=3 navHid=0 sdk=23 size=2 long=1 modetype=1 modenight=1
01-31 13:37:47.759: V/glfw-android(19546): _glfwPreMain
01-31 13:37:47.836: V/threaded_app(19546): Start: 0xb4dfd120
01-31 13:37:47.836: V/threaded_app(19546): activityState=10
01-31 13:37:47.836: V/glfw-android(19546): handleCommand: APP_CMD_START
01-31 13:37:47.836: V/threaded_app(19546): Resume: 0xb4dfd120
01-31 13:37:47.837: V/threaded_app(19546): activityState=11
01-31 13:37:47.837: V/glfw-android(19546): handleCommand: APP_CMD_RESUME
01-31 13:37:47.862: V/threaded_app(19546): InputQueueCreated: 0xb4dfd120 -- 0xb4dfd260
01-31 13:37:47.862: V/threaded_app(19546): APP_CMD_INPUT_CHANGED
01-31 13:37:47.863: V/threaded_app(19546): Attaching input queue to looper
01-31 13:37:47.863: V/glfw-android(19546): handleCommand: APP_CMD_INPUT_CHANGED
01-31 13:37:47.872: V/threaded_app(19546): NativeWindowCreated: 0xb4dfd120 -- 0xaa355008
01-31 13:37:47.872: V/threaded_app(19546): APP_CMD_INIT_WINDOW
01-31 13:37:47.873: V/glfw-android(19546): handleCommand: APP_CMD_INIT_WINDOW
01-31 13:37:47.873: V/threaded_app(19546): WindowFocusChanged: 0xb4dfd120 -- 1
01-31 13:37:47.874: V/glfw-android(19546): handleCommand: APP_CMD_GAINED_FOCUS
01-31 13:37:48.201: V/glfw-android(19546): _glfwPlatformInit
01-31 13:37:48.244: V/glfw-android(19546): init_gl
01-31 13:37:48.260: I/Adreno(19546): QUALCOMM build                   : 52af4d2, I8366cd0437
01-31 13:37:48.260: I/Adreno(19546): Build Date                       : 10/20/15
01-31 13:37:48.260: I/Adreno(19546): OpenGL ES Shader Compiler Version: XE031.05.13.02
01-31 13:37:48.260: I/Adreno(19546): Local Branch                     : M14
01-31 13:37:48.260: I/Adreno(19546): Remote Branch                    : 
01-31 13:37:48.260: I/Adreno(19546): Remote Branch                    : 
01-31 13:37:48.260: I/Adreno(19546): Reconstruct Branch               : 
01-31 13:37:48.270: I/defold(19546): INFO:ENGINE: Defold Engine 1.2.73 (181bfb1)
01-31 13:37:48.273: D/push(19546): Push started (com.defold.push.PushJNI@9a46930 )
01-31 13:37:48.274: D/defold.facebookapp(19546): sdkInitialize: activity com.dynamo.android.DefoldActivity@48ecf18   appid: 355198514515820
01-31 13:37:48.289: D/defold.facebookapp(19546): activateApp: activity com.dynamo.android.DefoldActivity@48ecf18   appid: 355198514515820
01-31 13:37:48.295: V/glfw-android(19546): _glfwPlatformOpenWindow
01-31 13:37:48.295: V/glfw-android(19546): create_gl_surface
01-31 13:37:48.296: I/defold(19546): INFO:ENGINE: Loading data from: .
01-31 13:37:48.320: I/defold(19546): INFO:ENGINE: Initialised sound device 'default'
01-31 13:38:16.165: E/defold(19546): ERROR:DLIB: No output socket available for ssdp search response
01-31 13:38:18.005: V/threaded_app(19546): Pause: 0xb4dfd120
01-31 13:38:18.010: V/threaded_app(19546): activityState=13
01-31 13:38:18.010: V/glfw-android(19546): handleCommand: APP_CMD_PAUSE
01-31 13:38:18.016: D/defold.facebookapp(19546): deactivateApp: activity com.dynamo.android.DefoldActivity@48ecf18   appid: 355198514515820
01-31 13:38:18.031: V/threaded_app(19546): SaveInstanceState: 0xb4dfd120
01-31 13:38:18.031: V/glfw-android(19546): handleCommand: APP_CMD_SAVE_STATE
01-31 13:38:18.033: V/threaded_app(19546): APP_CMD_SAVE_STATE
01-31 13:38:18.033: V/threaded_app(19546): Stop: 0xb4dfd120
01-31 13:38:18.134: V/threaded_app(19546): activityState=14
01-31 13:38:18.134: V/glfw-android(19546): handleCommand: APP_CMD_STOP
01-31 13:38:22.564: V/threaded_app(19546): WindowFocusChanged: 0xb4dfd120 -- 0
01-31 13:38:22.565: V/glfw-android(19546): handleCommand: APP_CMD_LOST_FOCUS
01-31 13:41:26.866: V/threaded_app(19546): Start: 0xb4dfd120
01-31 13:41:26.866: V/threaded_app(19546): activityState=10
01-31 13:41:26.866: V/glfw-android(19546): handleCommand: APP_CMD_START
01-31 13:41:26.866: V/threaded_app(19546): Resume: 0xb4dfd120
01-31 13:41:26.966: V/threaded_app(19546): activityState=11
01-31 13:41:26.966: V/glfw-android(19546): handleCommand: APP_CMD_RESUME
01-31 13:41:26.967: V/threaded_app(19546): WindowFocusChanged: 0xb4dfd120 -- 1
01-31 13:41:26.989: D/defold.facebookapp(19546): activateApp: activity com.dynamo.android.DefoldActivity@48ecf18   appid: 355198514515820
01-31 13:41:26.990: V/glfw-android(19546): handleCommand: APP_CMD_GAINED_FOCUS
01-31 13:41:46.302: E/defold(19546): ERROR:DLIB: No output socket available for ssdp search response

The last line seems to be the reason I can’t see my device:

01-31 13:41:46.302: E/defold(19546): ERROR:DLIB: No output socket available for ssdp search response

I’m using a Nexus 6 running Android 6.0.1 and dmengine 1.2.73.

Any help would be greatly appreciated
Thanks

Andreas_Jirenius · January 31, 2016, 2:03pm

I’m been having different kinds of problems with the “target” depending on which router I’ve been connected to.
At home, everything works splendid.
At work SOME networks let me show the target and run the game through wifi.
I guess it’s a matter of security setttings of the router but I’m not sure what.

At least:

Make sure both the computer and the device is connected to the same wifi network.
Restart both the Defold editor and the runtime client on the device.
Make sure that you have signed a build using the latest version of Defoldclient. (You need to do this for each Defold update and download a new runtime on device)

Other than that I honestly dont know.

/Andreas

Thibault · January 31, 2016, 3:00pm

That’s weird. I’ll try tomorrow on another network.

It’d be great if we could enter a target’s IP address manually, instead of just relying on ssdp.

Thanks

Thibault · February 2, 2016, 12:28pm

So after some tries I finally got it to work.

I first tried on a different network but I had the same error on my phone.

I then tried on two other devices and it actually worked, so the issue was specific to my phone.
It runs a custom ROM so I thought maybe that could be the cause.

I ended up installing a new ROM and it worked
I have no idea why it wouldn’t work with my previous ROM though

britzl · February 2, 2016, 10:52pm

Great job figuring out what was wrong! Thanks for letting us know!

CDaniel · March 26, 2016, 11:47pm

I have same issue with 6.0.1, just pushed out last week by carrier.

Now anything that used to connect SSDP does not , a fuji camera would connect prior to update, the defold editor.
Tried multiple things to get it to work, no luck.
I can see the ssdp packets being received on phone.
Highly suspect 6.0.1 has issue.

leifcr · June 15, 2016, 12:52pm

Same issue on Sony Xperia Z5 with 6.0.1

Tried the following variations
Different networks
Different computers
Windows, Linux

Any tips to what to try next?

britzl · June 15, 2016, 4:49pm

@Andreas_Tadic, any ideas?

johnnyezzell · June 15, 2016, 8:19pm

For some reason I can’t see any of my android targets anymore. I thought it was the update, but that doesn’t seem to be it.

My issue is on Kindle Fire HD and Moto E.

britzl · June 16, 2016, 6:58am

@johnnyezzell which Android version are the devices running?

britzl · June 16, 2016, 9:20am

I am unable to discover my HTC One M9 running Android 6.0. Discovering an older Samsung works. Opened a new ticket: https://jira.int.midasplayer.com/browse/DEF-1928

leifcr · June 19, 2016, 9:20am

@britzl thanks for opening a new ticket

johnnyezzell · June 19, 2016, 3:28pm

Oh my, I totally missed this. Apologies for the delay.

Kindle Fire is version 7.5.1… it doesn’t have an android version that I can tell?

Moto E is running Lolipop 5.1

Thanks for opening a ticket!

britzl · October 11, 2016, 6:56am

This will be worked on next week and hopefully completed before the next release (1.2.91).

britzl · October 25, 2016, 12:42pm

Solved in 1.2.91

unity.prefer · November 23, 2016, 9:51pm

Defold 1.2.93
Java 1.8.0_05
dmengine.apk from 1.2.93
Android 5.1.1
No Ethernet
Same WIFI
USB connected

“Waiting for connection…” in dmengine
In Defold editor “Target” only local 192.168…

britzl · November 23, 2016, 9:54pm

Android 5.1.1 has if I’m not mistaken never been a problem for us…

This is not necessary.

I wonder if you have firewall software or some thing in your router that may be blocking the devices from finding each other?

unity.prefer · November 23, 2016, 10:06pm

Firewall - AVG Internet Security on Windows 10 v1607 OS Build 14393.447
But some Defold updates ago it was working fine.

adb devices - now working but still “waiting for connection…”.

Before that in Target I saw name of my desktop besides local

The same on other android devices. 4.4.2/ 4.2.2/ 6.0

britzl · November 23, 2016, 10:02pm

Hmm, @jakob.pogulis, any ideas?

unity.prefer · November 23, 2016, 10:12pm

In Router I have MAC filtering
My Windows 10 PC and Android phone 5.1.1 allowed in Wireless MAC Filtering