Originally Posted by phedders

My Sony/Ford car stereo does bluetooth. But it's a pain.

Up until two days ago, it would always connect fine when turned on. And HFP worked just fine for calls - very well actually.

A2DP was a different story. First try worked brilliantly. Worked great for a day. Then would only work occasionally - sometimes if I flicked from phone to stream on the stereo it would work. Mostly the phone would be sending data and it would just be silent, or the stereo would silently drop the link.

Two days ago I got Fraud to update the firmware (why can I not do that? It's MY car you theives.)

Now A2DP works more often - normally after flicking from phone mode and back. But it fails to auto connect - or rather it does try to auto connect, but then drops the link (it does now say "link dropped") so I have to dive through menus on the phone to reconnect... it will often fail once more, then work fine.

So I want to write a script that can be called from a DCE button to initiate a connection (and I'll write a dbus-scripts script to do it on failure too!) but how?

Can I send a dbus-command?

dbus-monitor reveals this chain of stuff happenning when I hit connect:

signal sender=:1.37 -> dest=(null destination) serial=1336 path=/org/bluez/1052/hci0/dev_00_1E_A4_FF_D8_BE; interface=org.bluez.Device; member=PropertyChanged
string "Connected"
variant boolean true
signal sender=:1.91 -> dest=(null destination) serial=190 path=/org/kernel/class/bluetooth/hci0/hci0_11; interface=org.kernel.kevent; member=add
signal sender=:1.37 -> dest=(null destination) serial=1337 path=/org/bluez/1052/hci0/dev_00_1E_A4_FF_D8_BE; interface=org.bluez.AudioSink; member=PropertyChanged
string "State"
variant string "connecting"
signal sender=:1.37 -> dest=(null destination) serial=1338 path=/org/bluez/1052/hci0/dev_00_1E_A4_FF_D8_BE; interface=org.bluez.Audio; member=PropertyChanged
string "State"
variant string "connecting"
signal sender=:1.91 -> dest=(null destination) serial=191 path=/org/kernel/class/input/input11; interface=org.kernel.kevent; member=add
signal sender=:1.91 -> dest=(null destination) serial=192 path=/org/kernel/class/input/input11/event4; interface=org.kernel.kevent; member=add
signal sender=:1.37 -> dest=(null destination) serial=1342 path=/org/bluez/1052/hci0/dev_00_1E_A4_FF_D8_BE; interface=org.bluez.Control; member=Connected
signal sender=:1.37 -> dest=(null destination) serial=1343 path=/org/bluez/1052/hci0/dev_00_1E_A4_FF_D8_BE; interface=org.bluez.Control; member=PropertyChanged

Can I use any of that?

Just found and checking: http://maemo.org/api_refs/5.0/5.0-fi...ontrol-api.txt - may help me...

EDIT

Seems like the command I need is:

Code:

dbus-send --system --print-reply --type=method_call --dest=org.bluez /org/bluez/1069/hci0/dev_00_1E_A4_FF_D8_BE.Connect

This page is really helpful: http://wiki.bluez.org/wiki/HOWTO/AudioDevices...

A more full script could be written using:

Code:

devmac=00:1E:A4:FF:D8:BE

adapter=$(dbus-send --print-reply --system --dest=org.bluez / org.bluez.Manager.DefaultAdapter| sed -ne "s/^.*object path //p"|sed -e 's/"//g')
device=$(dbus-send --print-reply --system --dest=org.bluez ${adapter} org.bluez.Adapter.FindDevice string:${devmac}|sed -ne "s/^.*object path //p"|sed -e 's/"//g')
dbus-send --system --print-reply --type=method_call --dest=org.bluez ${device} org.bluez.AudioSink.Connect

(Change the AudoSink to whatever service you want, and the devmac to the mac of your bluetooth headset,stereo,computer,teddybear...)

Originally Posted by rajeshgklm

Hello Phedders

Please let me know how can i achieve this with Desktop Execution Command Widget

Thanks & Regards
Rajesh