#93 Plantronics 340 locked up after using userspace method
Hi,
I tryied to switch to the new userpace method instead of useing btsco. But everytime I try to play a file (to test if it's working) it locks up my headset, so I can't use it until the battery gets empty (about 3-5 weeks). I can reproduce this. First I thought my headset was broken, because I wasn't able to switch it back on, so I reported it to the shop owner and got a new one, but then again, the same result after trying to play a file. It happens when I get that error which says "access denied: not authorized", after that it's locked up and I have to wait several weeks to get it back to work.
I'd be glad to know what's happening with my plantronics 340 and if there is a solution, besides going back to btsco?
Thanks in advance.
My system:
--------------------------------------------------
Linux bermudahonk 2.6.22.7 #6 SMP Fri Oct 19 13:47:59 CEST 2007 x86_64 GNU/Linux
# dpkg -l |grep blue
ii bluetooth 3.20-1
ii bluez-cups 3.20-1
ii bluez-gnome 0.13-1
ii bluez-hcidump 1.39-1
ii bluez-utils 3.20-1
ii libbluetooth-dev 3.20-1
ii libbluetooth1 2.25-2
ii libbluetooth2 3.20-1
This is what i get from bluetoothd-service-audio:
-------------------------------------------------
Oct 20 00:01:50 bermudahonk kernel: PM: Adding info for bluetooth:acl000389D0FC70
Oct 20 00:01:51 bermudahonk hcid[1513]: link_key_request (sba=00:11:B1:07:A3:97, dba=00:03:89:D0:FC:70)
Oct 20 00:01:52 bermudahonk audio[3485]: Requesting authorization for device 00:03:89:D0:FC:70, UUID 00001112-0000-1000-8000-00805F9B34FB
Oct 20 00:01:52 bermudahonk audio[3485]: State changed /org/bluez/audio/device0: DISCONNECTED -> CONNECTING
Oct 20 00:01:52 bermudahonk audio[3485]: Access denied: Not authorized
Oct 20 00:01:52 bermudahonk audio[3485]: State changed /org/bluez/audio/device0: CONNECTING -> DISCONNECTED
Oct 20 00:01:52 bermudahonk hcid[1513]: link_key_notify (sba=00:11:B1:07:A3:97, dba=00:03:89:D0:FC:70)
Oct 20 00:01:56 bermudahonk kernel: PM: Removing info for bluetooth:acl000389D0FC70
Logged In: NO
Sometimes it is enough to just plug in the headset for a recharge and then after a short while (10sec or so), unplug it and turn it back on.