Review Request 122174: Add initial bluetooth backend implementation.

[Albert Vaca Cintora]

-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/122174/#review76501
-----------------------------------------------------------


For some reason the frameworks branch is not working on my computer even without these changes, so I couldn't test this. I hope I will find some time early this week to fix my problem :/

- Albert Vaca Cintora


On Feb. 14, 2015, 4:50 p.m., Saikrishna Arcot wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://git.reviewboard.kde.org/r/122174/
> -----------------------------------------------------------
> 
> (Updated Feb. 14, 2015, 4:50 p.m.)
> 
> 
> Review request for kdeconnect.
> 
> 
> Repository: kdeconnect-kde
> 
> 
> Description
> -------
> 
> Add initial bluetooth backend implementation.
> 
> This is based on the frameworks branch.
> 
> The `getPairedDevices()` method in the link provider class uses D-Bus to get the list of paired devices, since Qt doesn't have a method giving that information. As a result, that part of the code only works on Linux.
> 
> 
> Diffs
> -----
> 
>   CMakeLists.txt 5b916d929dfa3f3304a8ac84e7ef6c19f9aa4663 
>   core/CMakeLists.txt 17209b1a801b33d99e31a4b19eac45df2fa6fe02 
>   core/backends/bluetooth/CMakeLists.txt PRE-CREATION 
>   core/backends/bluetooth/bluetoothdevicelink.h PRE-CREATION 
>   core/backends/bluetooth/bluetoothdevicelink.cpp PRE-CREATION 
>   core/backends/bluetooth/bluetoothlinkprovider.h PRE-CREATION 
>   core/backends/bluetooth/bluetoothlinkprovider.cpp PRE-CREATION 
>   core/backends/devicelinereader.h PRE-CREATION 
>   core/backends/devicelinereader.cpp PRE-CREATION 
>   core/daemon.cpp 57548e5a671b7694125e733db06a58eebbadd264 
> 
> Diff: https://git.reviewboard.kde.org/r/122174/diff/
> 
> 
> Testing
> -------
> 
> KDE Connect runs, and the bluetooth service gets published in the SDP (service discovery protocol), which other devices use to determine what services are available.
> 
> For me, sending a pair request from KDE to Android results in KDE Connect crashing on Android. It seems it's because the VIBRATE permission is necessary, which I've added on the Android side. In addition, the pairing data doesn't seem to be stored on the KDE side. Not sure if I'm missing something or not.
> 
> # Android as client and KDE as server
> 
> ## BlueZ 4 and Qt 5.3
> 
> My Android (4.1.2) sees the KDE connect service and tries to connect to it, but fails most of the time. Sometimes, it succeeds and creates a connection. I haven't been able to find out why it's failing the rest of the time. Newer versions of Android (4.2 and higher) might have better luck, since the Bluetooth code was changed.
> 
> When it does connect, one time, I was able to pair the devices together (from my Android), and was able to send a ping, use the touchpad, and control my media player from my Android.
> 
> ## BlueZ 4 and Qt 5.4
> 
> Not tested.
> 
> ## BlueZ 5 and Qt 5.4
> 
> My Android sees and at least tries to connect to the KDE connect service. Sometimes, it's successful, sometimes, it fails.
> 
> # Android as server and KDE as client (all versions)
> 
> I was able to successfully connect to the Android and use it.
> 
> 
> Thanks,
> 
> Saikrishna Arcot
> 
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdeconnect/attachments/20150223/d13528b8/attachment.html>