Other Parts Discussed in Thread: WL1837, WL1831
We are still seeing significant audio issues when having an incoming A2DP stream from a cellphone and an outgoing A2DP stream to a speaker: As soon as WIFI traffic is present, there are significant bursts of noise, as lengthily explained in the previous thread.
We have dug into this issue with the help of an external consultancy and analysed what's going on at BT protocol level. As it seems, there are (usually) no dropped packets, but by looking at the RTP protocol headers in the audio stream, we found that the timestamps are jumping occasionaly, p.ex.:
7113 82.767373 Motorola_77:d4:d6 (moto g(8) power) → localhost () SBC 617 ✓ PT=SBC, SSRC=0x0, Seq=15, Time=8960 Frames=5 7114 82.770830 Motorola_77:d4:d6 (moto g(8) power) → localhost () SBC 617 ✓ PT=SBC, SSRC=0x0, Seq=16, Time=9600 Frames=5 7117 82.776478 Motorola_77:d4:d6 (moto g(8) power) → localhost () SBC 617 ✓ PT=SBC, SSRC=0x0, Seq=17, Time=12416 Frames=5
the time difference of packets 16 and 17 correlates exactly to a pop-noise in the decoded audio stream.
Our hypothesis is now that BT master does not assign enough time slots the sender (cell phone), respectively they are assigned too late due to the presence of wifi traffic.
Does the firmware offer any tuning parameters to give BT traffic higher priorities over Wifi, or is there a way to reduce Wifi airtime so that both interleave at a finer temporal granularity?
Jacob B. sorry it took some time to follow up on this.
Simon
P.S. the config we are using is attached