Re: Re: TDE and bluetooth (Bluez 5)

I did following experiment: Goal: test bluetooth with debian jessie and two Nokia phones (5530 and N9) TEST 1 VM HOST: 3.2.0-4-rt-amd64 #1 SMP PREEMPT RT Debian 3.2.68-1+deb7u4 x86_64 This is a server with drives on mptsas. For some reason 3.16 panic on boot (no option to debug) because of this we had to use bluez 4.99 (build deb pkgs from wheezy source with minor change in bluez-4.99/tools/hid2hci.c) VM GUEST: VM player with debian jessie 8.2 in it and base gnome Kernel is debian stock 3.16 Do not enable share usb/bluetooth with the host Enable the bluetooth adapter in the VM player (this was tested also with windows7 - to prove the concept) Ignore warning about BT adapter claimed by btusb on the host After some issues with bluetooth I re-installed all related gnome packages inkl gstream, pulse and finally bluemon. The latter seems to work tight wi th systemd and bluetoothd, which provided the necessary link to the hardware via DBUS. Via blueman applet it was possible to pair and connect to both devices. I think triggering browse device function helped somehow load the appropriate configuration and I was able to browse the content of both phones via OBEX. When trying to reproduce it I found out that to use OBEX one should not use connect but directly trigger browse, which connects (I guess via OBEX). Still to investigate. Follow up: - test syncevolution - copy VM and install TDE and test connectivity from there - find the old kde3 bluetooth code and see what we can use out of it I'm interested in how to enable the obex protocol in konqueror TEST 2: System: debian jessie 8.2 / 4.3.3eko4 #1 SMP No systemd TDE desktop It turned out that blueman is tied to systemd and there is no way to test without systemd (the a2dp profile does not load) I have a good reason to keep systemd off here, so need to work on this part before going on I hope this information helps someone else here regards