Openmoko Bug #1656: Bad A2DP performance

Openmoko Public Trac bugs at docs.openmoko.org
Wed Aug 6 15:07:17 CEST 2008


#1656: Bad A2DP performance
---------------------+------------------------------------------------------
 Reporter:  Mercury  |        Owner:  openmoko-devel
     Type:  defect   |       Status:  new           
 Priority:  normal   |    Milestone:                
Component:  unknown  |      Version:                
 Severity:  major    |   Resolution:                
 Keywords:           |     Blocking:                
Blockedby:           |  
---------------------+------------------------------------------------------

Comment(by andy):

 Clipped means that it got decoded / amplified / filtered beyond + or -
 32767.  It will cause a little "tick" sound usually.  So this is enough to
 make the problem... try using switches in your decoder to "amplify" to
 -1dB or somesuch and see if it helps.

 But the datarate for your raw data in the second case is pretty high,
 1.4Mbits/sec sustained.  I don't know much about Bluetooth to say if it
 makes trouble, EDR BT seems to provide 3Mbits/sec raw bandwidth so it
 isn't crazy if that is what we provide.

-- 
Ticket URL: <https://docs.openmoko.org/trac/ticket/1656#comment:6>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac


More information about the buglog mailing list