-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No connection when connecting through USB developer mode #17
Comments
Just messed around with kdeconnect / sailfishconnect over usb and got a bit further:
Now I got a udp message such as:
I copied that message, turned off wifi, connected the phone via USB and started sailfish connect.
After I got the connection I copied the message into that netcat session and the phone and PC tell me that they're connected. So my Impression is that PC and phone send UDP broadcasts (this is stated in the kdeconnect manual) and those broadcasts don't get forwarded from the phone to the pc or vice versa. Do you have an idea on how to allow broadcast messages on USB? |
Sorry, I'm not familiar with Ethernet USB. The KDE Connect Project is working on using Multicast DNS (MDNS) instead of UDP Broadcasts. Maybe is would help. However, there exists currently only a non-functioning prototype. Also SailfishConnect is missing a option to manually select IPs to connect to. I think that would also solve your problem. Because a TCP connection is possible, right? Currently I'm working on integrating SailfishConnect into the KDE Connect project. So there is less time for new features. |
Haven't checked whether UDP Broadcasts or MDNS packets are forwarded. Will check that next time. Thanks! |
I tested it and it connects at least for me. As a workaround in version 0.6 the IP of the computer can be added in the settings. When searching for devices a UDP packet is send to this IP address. |
It is not fixed. To get this to work one has to directly connect via TCP like GSConnect does. |
When phone is connected by USB to computer through developer mode then no connection is possible.
See https://openrepos.net/comment/26268#comment-26268
The text was updated successfully, but these errors were encountered: