View Single Post
Posts: 141 | Thanked: 313 times | Joined on May 2012 @ Czech Republic
#45
Originally Posted by sirpaul View Post
But i tried today a call and the connection headset-phone was interrupted after 6mins (it lasted a few days ago 20mins without any problem).
Isn't the problem it too much noisy environment (I mean too many wifi and bluetooth connection so there is problem with connection).

Originally Posted by sirpaul View Post
now i have added "Disable=Media" directly under [General] in the file (what about "Enable=Socket" which was also suggested?)
Enable=Socket is already in the config file (at least should be):
http://talk.maemo.org/showpost.php?p...4&postcount=41

Originally Posted by sirpaul View Post
deleted content of /var/lib/bluetooth, rebooted and re-paired it (would it have changed anything if i have killed/stopped the processes from above?).
I'm not sure if bluetoothd write something to the /var/lib/bluetooth during exiting. So that's the reason I suggested to kill the processes.

Originally Posted by sirpaul View Post
does /etc/event.d/bluetoothd: exec /usr/sbin/bluetoothd -n -d enable bt debugging or just gives the results? and how to disable it (when it is "debugged")?
No exactly. It's old syntax. The new one is:
Code:
exec /usr/sbin/bluetoothd -n -d '*'
I stop debugging the opposite way as enabling it. Change the /etc/event.d/bluetoothd (remove -d '*') and reboot. If it's enough to stop writing logs I stop the sysklogd: stop sysklogd.

BTW from source code it should be enough to just send SIGUSR2 signal to bluetoothd process to start/stop debugging.

Originally Posted by sirpaul View Post
result: auto connection does still not work (as described above); phoning is still being tested.
I don't get it. You're able to call using BT headphone (so you have to be able to connect) but you're not able to autoconnect. What does exactly autoconnect mean? It seems I never tested autoconnect.

I'll appreciate if you upload logs from bluez 4.99.