Closed Bug 966246 Opened 11 years ago Closed 11 years ago

Not able to connect to a Hamachi device

Categories

(DevTools Graveyard :: WebIDE, defect)

29 Branch
x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: arcturus, Unassigned)

Details

With adb helper addon, I cannot connect to the phone again. This error is flashing, from time to time it works, but in certain situations, don't know when, is impossible to connect to the phone. I already checked that in developer options remote debugging is enabled for adb and Devtools Here is the log that I have in the console next to the connnect buttons: 13:53:14: connecting to localhost:62961 13:53:14: connection error. Possible causes: USB port not connected, port not forwarded (adb forward), wrong host or port, remote debugging not enabled on the device. 13:53:14: connecting to localhost:62964 13:53:14: connection error. Possible causes: USB port not connected, port not forwarded (adb forward), wrong host or port, remote debugging not enabled on the device. 13:53:15: connecting to localhost:62967 13:53:15: connection error. Possible causes: USB port not connected, port not forwarded (adb forward), wrong host or port, remote debugging not enabled on the device. 13:53:15: connecting to localhost:62970 13:53:15: connection error. Possible causes: USB port not connected, port not forwarded (adb forward), wrong host or port, remote debugging not enabled on the device. 13:53:15: connecting to localhost:62973 13:53:15: connection error. Possible causes: USB port not connected, port not forwarded (adb forward), wrong host or port, remote debugging not enabled on the device. 13:53:16: connecting to localhost:62976 13:53:16: connection error. Possible causes: USB port not connected, port not forwarded (adb forward), wrong host or port, remote debugging not enabled on the device. 13:53:16: connecting to localhost:62979 13:53:16: connection error. Possible causes: USB port not connected, port not forwarded (adb forward), wrong host or port, remote debugging not enabled on the device. 13:53:16: connecting to localhost:62982 13:53:16: connection error. Possible causes: USB port not connected, port not forwarded (adb forward), wrong host or port, remote debugging not enabled on the device. 13:53:22: connecting to localhost:62987 13:53:22: connection error. Possible causes: USB port not connected, port not forwarded (adb forward), wrong host or port, remote debugging not enabled on the device. 13:53:23: connecting to localhost:62990 13:53:23: connection error. Possible causes: USB port not connected, port not forwarded (adb forward), wrong host or port, remote debugging not enabled on the device. 13:53:23: connecting to localhost:62993 13:53:23: connection error. Possible causes: USB port not connected, port not forwarded (adb forward), wrong host or port, remote debugging not enabled on the device.
Which version of Firefox OS runs on the device?
What debug option is selected exactly? "Adb Only"?
Flags: needinfo?(francisco.jordano)
@Paul, it's selected the option: ADB & DevTools Cheers!
Flags: needinfo?(francisco.jordano)
Is there any error showing up in "adb logcat | grep Gecko" by any chance? On device startup and/or when trying to connect?
Flags: needinfo?(francisco.jordano)
Unfortunately not able to reproduce it again. Closing as worksforme, since in latest builds I'm not able to reproduce it.
Status: NEW → RESOLVED
Closed: 11 years ago
Flags: needinfo?(francisco.jordano)
Resolution: --- → WORKSFORME
Product: Firefox → DevTools
Product: DevTools → DevTools Graveyard
You need to log in before you can comment on or make changes to this bug.