Anno domini 2024 Mon, 20 May 10:05:13 +0200 deloptes via tde-devels scripsit: > > Hello Lesslie, Nik, > we could not test tdebluez on anything else but Debian. In Debian I used > bluez-obexd which provides obexd and is standard. I do not know the other > obexd package. I suspect you use SuSE or CentOS. I'm on devuan ceres :) tdebluez works fine ... as long as you do not need anything bluetooth-audio. If you use pulseaudio instead of bluealsa things basicly work - but audio auto(re)connect does not. For the RPi400 I settled with pulseaudio + blueman-applet + holding-hands-with-bluetooth. Might be that the RPi BT device is a bit unstable ... > If you don't mind we could incorporate your findings in the respective > packages. We have to create CRs in TGW for that. That would be great :) Nik > > > Dr. Nikolaus Klepp via tde-devels wrote: > > > Anno domini 2024 Mon, 20 May 02:33:31 -0500 > > J Leslie Turriff via tde-devels scripsit: > >> I'm setting up a laptop machine for my brother. When I tried to use > >> tdebluez to enable a bluetooth headset I got this response: > >> > > obexd is not required for this operation specifically, but to give you the > ability to transfer files to the PC. I use it to push files from the phone. > > >> org.bluez.AdminPolicyStatus1 > >> | [2024/05/20 00:49:56.685] obexd executable was not found > >> | Set path in configuration file "tdebluezrc" > >> | Variable: obexSrvExe=<path to obexd> > >> | [1]+ Done tdebluez > >> > >> So I searched for the missing component: > >> > >> | zypper se obexd > >> | Loading repository data... > >> | Reading installed packages... > >> | > >> | S | Name | Summary > >> | | > >> Type > >> | --+------------------------+----------------------------------------------+-------- > >> | | bluez-obexd | Object Exchange daemon for sharing binary > >> | | -> | > >> package > >> | | bluez-obexd-debuginfo | Debug information for package bluez-obexd > >> | | | > >> package > >> | | obexd | D-Bus service for Obex Client access > >> | | | > >> package > >> | | obexd-client | D-Bus service for Obex Server access > >> | | | > >> package > >> | | obexd-client-debuginfo | Debug information for package obexd-client > >> | | | > >> package > >> | | obexd-debuginfo | Debug information for package obexd > >> | | | > >> package > >> | | obexd-debugsource | Debug sources for package obexd > >> | | | > >> package > >> | | obexd-server | D-Bus service for Obex Server service > >> | | | > >> package > >> | | obexd-server-debuginfo | Debug information for package obexd-server > >> | | | > >> package > >> | rc=0 > >> > >> Which of these packages do I need to install to make tdebluez work? > >> Shouldn't tdebluez have triggered this as a dependency? > > > > I got it working with bluez-alsa-utils + pulseaudio-utils + blueman-applet > > as everything should work from userspace. > > > > If you use tdebluez you need to start bluealsa from your /etc/rc.local: > > ( bluealsa --profile=hsp-ag --profile=a2dp-source --profile=a2dp-sink > > --syslog) & > > > > ... or with sysv use this startscript: > > > > > > #! /bin/sh /lib/init/init-d-script > > ### BEGIN INIT INFO > > # Provides: bluealsa > > # Required-Start: $local_fs $syslog $remote_fs dbus > > # Required-Stop: $local_fs $syslog $remote_fs > > # X-Start-Before: bluetooth > > # X-Stop-After: bluetooth > > # Default-Start: 2 3 4 5 > > # Default-Stop: 0 1 6 > > # Short-Description: Start bluealsa daemons > > ### END INIT INFO > > > > DAEMON=/usr/bin/bluealsa > > DAEMON_ARGS="--profile=hsp-ag --profile=a2dp-source --profile=a2dp-sink > > --syslog" PIDFILE=/run/bluealsa.pid > > START_ARGS="--background --make-pidfile" > > > > > > ... otherwise the headphone will connect and then disconnect again. > > > > And you need to run a "supervisor" like that to automaically reconnect BT > > audio devices: > > > > > > > > #!/bin/bash > > > > echo "bt autoconnection audio devices ..." > > > > CON=$(mktemp) > > PAI=$(mktemp) > > > > while sleep 3; do > > bluetoothctl devices Connected | sort | cut -d ' ' -f 2 > $CON > > bluetoothctl devices Paired |sort | cut -d ' ' -f 2 > $PAI > > NC=$(comm -3 $PAI $CON 2>/dev/null) > > if [ ! -z "$NC" ]; then > > for i in $NC; do > > if [ $(bluetoothctl info $i | grep -i audio | wc > > -l) -gt 0 ]; then > > bluetoothctl connect $i > > fi > > done > > fi > > done > > > > > > Well, there might be easier ways :) > > > > Nik > > > > The script is not strictly needed (at least on the Debian here), because the > system automatically reconnects when I switch on the audio device. OF > course the visibility should be enabled. > However we could also include the scripts as optional if someone does not > object > > BR > > ____________________________________________________ > tde-devels mailing list -- devels@xxxxxxxxxxxxxxxxxx > To unsubscribe send an email to devels-leave@xxxxxxxxxxxxxxxxxx > Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/devels@xxxxxxxxxxxxxxxxxx > -- Please do not email me anything that you are not comfortable also sharing with the NSA, CIA ... ____________________________________________________ tde-devels mailing list -- devels@xxxxxxxxxxxxxxxxxx To unsubscribe send an email to devels-leave@xxxxxxxxxxxxxxxxxx Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/devels@xxxxxxxxxxxxxxxxxx
