Skip to main content
July 21, 2011
Question

Unable to connect to the debugger (5.5 -> Android)

  • July 21, 2011
  • 1 reply
  • 2754 views

I have the problem many have been having with not being able to connect to the debugger on my phone (Samsung Galaxy S2). I've read pretty much all threads I've found but can't seem to find what could be wrong.

What I want to do is to PUBLISH, INSTALL and LAUNCH my Air2.6 app on my mobile device with the debugger running so I can see any traces from the phone.

This is what I've tried so far:

  • Firewall disabled (Both third party and windows)
  • Changed my hosts file to localhost -> 127.0.0.1
  • Tried both IP and hostname
  • Disabled WiFi on my phone (so it's not interfiering)

This is my setup:

  • Windows 7
  • Flash Pro 5.5
  • Air 2.6
  • Samsung Galaxy S2
  • Connected using USB (no WiFi)
  • Drivers and all is working. Everything else is working except the debugger.

Does anyone have any other ideas of what I could try? It's hard to try and develop when not being able to debug on the phone, hehe.

Thank you so much!

This topic has been closed for replies.

1 reply

relaxatraja
Inspiring
July 22, 2011

http://www.groovypost.com/howto/mobile/how-to-enable-usb-debugging-android-phone/

and try with different usb port

July 22, 2011

Thank you for the reply.

My phone is connected via USB and working. But I still get "Unable to connect to the debugger (Computer-PC). Enter IP or Hostname to connect" in my phone when trying to publish, launch and debug on my phone from within Flash Pro 5.5.

I've tried 5 different USB-ports. Same result on all.

Any other ideas?

Thank you

July 22, 2011

I got it working!... sort of.

It works every second time. Every other time I get an "application isn't responding... wan't to wait?" message in my phone. Then I re-compile, launch and it's working (but after some time. takes around 10-20secs to launch on phone).


Do you think this has something to do with my wireless connection?

What I changed from before was to add the port to my computers IP, not the port itself (open in the router). Which shouldn't be a difference, but somehow I guess it was.