Hi, sorry for bugging you all, but now I'm trying to catch up what I missed in the past 4+ years.
Unfortunately I did find out that the mess around bluetooth is getting even bigger now with Bluez 5.
http://askubuntu.com/questions/440386/bluetoothd-bluez-5-wont-connect-with-a...
What is your experience with BT and is someone using it with phones?
After couple of hours I was able to pair my old symbian phone, but bt-agent (bluez-tools) is segfaulting (kernel 4.1.6)
bluetoothctl worked after executing the proper sequence of commands and catching the phone in good mood.
How would one pair the phone (or any BT device) from within TDE?
regards
http://www.lightofdawn.org/blog/?viewDetailed=00031
laugh and cry in the same time
Am Freitag, 18. Dezember 2015 schrieb deloptes:
http://www.lightofdawn.org/blog/?viewDetailed=00031
laugh and cry in the same time
You can continue the list ... udev, dbus, systemd ... windowz folk has finally arrived.
Dr. Nikolaus Klepp wrote:
Am Freitag, 18. Dezember 2015 schrieb deloptes:
http://www.lightofdawn.org/blog/?viewDetailed=00031
laugh and cry in the same time
You can continue the list ... udev, dbus, systemd ... windowz folk has finally arrived.
Thanks Mr. Klepp, you are speaking from my heart. I actually see the KDE approach behind all of it. Actually I am not sure if it is a social illness - I observe same pattern in politics and social life. Are we getting old ... or our world goes too far left (ideologies) ... or both. It is simply sad sad sad. Things that were working before just stop work without replacement.
I'm just wondering what would be the best approach - keep the Bluez 4 or skip it for the next 4+ years ... by looking into KDE - I am even not convinced that it will ever work :)
regards
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
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
- copy VM and install TDE and test connectivity from there - it works with blueman and OBEX - it needs a lot of gnome related stuff to work
-
deloptes -
Dr. Nikolaus Klepp