3 ms·
KDE Connect requires both devices to be connected to the same network, which means you have to connect your devices to the same VPN if you're on a wifi network
by ggreer 3y ago
KDE Connect requires both devices to be connected to the same network, which means you have to connect your devices to the same VPN if you're on a wifi network with client isolation (most public wifi). If you're away from wifi, you'll have to configure one of the devices to be an access point and join everything else to that device.
Apple's clipboard/handoff/continuity automatically works as long as the devices are within wifi/bluetooth range.
- michaelmrose 3y agoThis is a good point and a good reason to propose an improvement to KDE Connect but users point was that integration would be awful if not done by the same party and it seems to my eyes to be pretty good despite one being created by a party with literally a billionth of the resources of the other.
- smoldesu 3y agoFor what it's worth, Connect does have a Bluetooth backend that supposedly works: https://invent.kde.org/network/kdeconnect-kde/-/tree/master/core/backends/bluetooth https://invent.kde.org/network/kdeconnect-kde/-/tree/master/... It doesn't seem to be enabled by default though. I'm not totally familiar with the situation, but I'd assume it's a problem with multi-device handling and switching to the best backend. For most people/situations, the Wifi Direct option will be faster and lower-latency.
- michaelmrose 3y agoIt also wont magically stop working 30 feet away if you want to use the multimedia remote functionality. Graceful degradation seems like a useful feature but if you aren't careful the result might be flaky