View Single Post
Helmuth's Avatar
Posts: 1,259 | Thanked: 1,341 times | Joined on Oct 2009 @ Germany
#44
I had a SE MW-600, too. And I had the same issues while reconnecting. So I created a Bug report: Bug 11916

Sadly, the headset was also defect. (the amplifier whooshed after some hours and this was annojng in quiet passages) So I sent it back to Amazon as long as I was able to do. Sadly, I missed in the chaos after the 11.2. a question from Andre Klapper at my Bug report.

Could someone with a MW-600 help to fix this bug?

There are two different logs that would be useful. The first is bluetoothd
debug logs and the second is a HCI-level trace.

For the first you'd need to:

1. install the klogd and sysklogd debian packages (and probably reboot the
device afterwards)
2. after booting and before doing anything with bluetooth do "killall -USR2
bluetoothd" (as root) to enable bluetoothd debug logs
3. after reproducing the issue "grep bluetoothd /var/log/syslog >
bluetoothd-log.txt" and attach the file here.

For a HCI trace do:

1. install the bluez-hcidump debian package
2. (as root) run "hcidump -B -w hci-trace.log while reproducing the issue
3. attach the hci-trace.log (or whatever filename you chose) here

See http://wiki.maemo.org/Documentation/devtools/maemo5 for more information on
how to install the requested packages.
It would be great if someone could help!
 

The Following User Says Thank You to Helmuth For This Useful Post: