[pulseaudio-tickets] [PulseAudio] #612: Native bluetooth module skips bytes

[PulseAudio]

#612: Native bluetooth module skips bytes
----------------------+-----------------------------------------------------
  Reporter:  volkris  |       Owner:  lennart
      Type:  defect   |      Status:  new    
 Milestone:           |   Component:  daemon 
Resolution:           |    Keywords:         
----------------------+-----------------------------------------------------

Comment(by volkris):

 I followed your suggestion to use the gnome-bluetooth connect method to
 activate the BT in PA.

 rtkit message remains, but the SCO messages are gone. Come to think of it,
 the pactl method I was using previously may have created a duplicate
 device in PA, one auto-activated and one forced with pactl. Maybe that
 somehow lead to the SCO error/warning.

 Now dmesg says nothing and syslog has the following:[[BR]]
 bluetoothd[2805]: link_key_request (sba=00:11:67:55:91:B0,
 dba=00:19:1F:00:0A:4D)[[BR]]
 bluetoothd[2805]: link_key_request (sba=00:11:67:55:91:B0,
 dba=00:19:1F:00:0A:4D)[[BR]]
 rtkit-daemon[3218]: Failed to make ourselves RT: Invalid argument[[BR]]
 rtkit-daemon[3218]: Failed to make ourselves RT: Invalid argument[[BR]]
 pulseaudio[3216]: module-bluetooth-device.c: Skipping 8186 us (= 1444
 bytes) in audio stream[[BR]]
 pulseaudio[3216]: module-bluetooth-device.c: Skipping 28601 us (= 5044
 bytes) in audio stream

 This dongle worked fine using the alsa module in the past.

 So let me know what you think I should do. I can talk to #bluez if you
 think it's a problem over there (though I suspect they'd bounce me back
 here), or I can try to dig up a different dongle if you think the PA
 native module may be incompatible while the alsa method was able to work
 around whatever the problem is.

-- 
Ticket URL: <http://pulseaudio.org/ticket/612#comment:7>
PulseAudio <http://pulseaudio.org/>
The PulseAudio Sound Server