opensuse 13.1 x86_64 , kde 4.12.1 kdeconnect 0.4.2-2.3 i have not a wifi network i use only ethernet cable if i understand well to use kdeconnect i must add a wifi adapter in my pc and create with this wifi adapter a wifi ap then internaly connect my pc to this ap and connect my smartphone to this ap to avoid this please add a bluetooth compliancy to kdeconnect with bluedevil 1.x (bt 2) and 2.x (bt 4) we can create a bluetooth local network if i understand well bluetooth technology you have just to use this lan with kdeconnect it is also useful for those using cpl network an advantage of bt 4 : saving energy technology , usefull for smartphone battery thanks Reproducible: Always
Initial support for bluetooth added to reviewboard.kde.org by "Saikrishna Arcot" https://git.reviewboard.kde.org/r/122174/ https://git.reviewboard.kde.org/r/122020/
great , thanks to all .
KDE Connect works by sending packets over the LAN- it doesn't matter if the PC is not using a wifi connection. I can see how bluetooth support could be helpful as it would allow a machine to interact with a phone even if the phone isn't permitted on the LAN, such as at some workplaces and schools
*** Bug 349196 has been marked as a duplicate of this bug. ***
hello what is the status of the bluetooth backend , thanks
Nobody is working on it and it's not even clear that we want it.
(In reply to Aleix Pol from comment #6) > Nobody is working on it and it's not even clear that we want it. Why would we not want it? With currently 81 votes, it is the most wanted new feature according to this bug tracker. Only bug 339367 has more votes. Or are you only refering to the developers not wanting this? The lack of this feature is a deal breaker for many potential users, including me. Is there any workaround to establish a connection between desktop computers in restricted LANs and a smartphone? Will there be one?
Hi Denis, We know this is important, but in the short term we are prioritizing other features. The reality is that neither Aleix nor me (currently, the two main developers) are Bluetooth users, but that doesn't mean that we think this is not a useful feature for some users. That's why the bug is not closed :) Albert
Albert, Would it help if I put a small bounty on bluetooth support? I don't have a lot of money, but I'd be willing to pay 15 USD if this were implemented - maybe there are others willing to donate as well. Let me know. Best, Garland
Yes, I would love to add my contribution (I could afford 30 USD) to have this implemented at last. It would make my life easier at work, where I cannot have my smartphone and my computer connected to the same wifi.
This is, indeed, a must-have for the "No LAN access" policy places and I wanted it for ages (since I've known about kde-connect). However, the status of the bluetooth KDE stack is really in a poor state...
This feature is really useful at work where there is no way to connect the cellphone to the LAN
There is a "bluetooth" branch in git developed by
There is a "bluetooth" branch in git developed by Saikrishna Arcot with this kind of link implemented. I had to adapt it to the current kdeconnect API but it should work. I haven't been able to test it myself because I think my computer bluetooth is not properly set up, but you might want to give it a try and provide feedback. It would be nice if you can try it connecting two PCs between them and two phones between them so we can know any platform-specific issues.
For the record, remote filesystem browsing will not work over the bluetooth backend because it uses SSHFS, which uses an IP network. It should be possible to implement FUSE in kdeconnect and transfer file information and payloads through kdeconnect itself.
For now, you can workaround this missing feature, by enabling network sharing on you phone (enable hotspot via bluetooth). This will give you an networkstack on the bluetooth connection.
The bluetooth code on the desktop side and the code on the Android side is using different protocol versions, and therefore syncing is not possible. Can you merge/rebase the code on both sides to include the changes made on the master branches?
In the latest code, connecting via Bluetooth works (albeit there maybe a crash due to a timing issue (fix submitted) and it may take a while for some reason), sending and receiving messages via Bluetooth works, and sending from Android to KDE works, but the KDE side doesn't see the transfer as successful for some reason.
We merged the changes that Saikrishna made to add support for Bluetooth to the master branch of both the Android and the desktop apps. It still needs polishing and it's not compiled by default, but if you want to give it a try you can compile your own KDE Connect and enable it. To enable it in Android: Uncomment the BLUETOOTH permissions in the AndroidManifest.xml and the line 'linkProviders.add(new BluetoothLinkProvider(this));' in BackgroundService.java To enable it on the desktop: Set the CMake flag BLUETOOTH_ENABLED to ON. Feedback and patches welcome!
(In reply to Saikrishna from comment #15) > For the record, remote filesystem browsing will not work over the bluetooth > backend because it uses SSHFS, which uses an IP network. It should be > possible to implement FUSE in kdeconnect and transfer file information and > payloads through kdeconnect itself. I don't know if that's possible under Android but just for reference: Apple’s Continuity negotiates things via Bluetooth LE but for actual file transfers etc. is opens an Ad-hoc WiFi network.
(In reply to kmi from comment #20) > (In reply to Saikrishna from comment #15) > > For the record, remote filesystem browsing will not work over the bluetooth > > backend because it uses SSHFS, which uses an IP network. It should be > > possible to implement FUSE in kdeconnect and transfer file information and > > payloads through kdeconnect itself. > > I don't know if that's possible under Android but just for reference: > Apple’s Continuity negotiates things via Bluetooth LE but for actual file > transfers etc. is opens an Ad-hoc WiFi network. I actually was able to implement a read-only FUSE filesystem (writing will take some work), but it's very buggy/rough (in particular, you may need to do manual cleanup after exiting KDE Connect on the desktop side).
*** Bug 389865 has been marked as a duplicate of this bug. ***
So is there any progress on this becoming stable? Thanks to the reliance on UDP broadcasts I can't use kdeconnect at work, and bluetooth would largely solve that, so I've been anxiously awaiting this!
(In reply to Keith Zubot-Gephart from comment #23) > So is there any progress on this becoming stable? Thanks to the reliance on Me too!
For those interested about Bluetooth development: https://www.reddit.com/r/linux/comments/6ggb36/kde_connect_works_over_bluetooth_now_please_help/ https://phabricator.kde.org/T7447 https://nicolasfella.wordpress.com/2018/07/31/kde-connect-new-stuff-ii/
*** Bug 453019 has been marked as a duplicate of this bug. ***