Hello,
we are currently developing a device based on the nRF5340 using LE Audio.
The device streams audio to a smartphone, where the corresponding Android application can record the incoming audio stream.
Our software is based on the nRF5340 Audio Unicast Server application from nRF Connect SDK v3.1.1.
Due to hardware constraints, the nRF5340 has to operate as an I2S slave. The external I2S source provides a sample rate of approximately 46.875 kHz, while the LE Audio/LC3 pipeline operates at 48 kHz.
To compensate for this difference, we implemented a resampling stage using the ratio 125:128, converting the incoming I2S audio to 48 kHz before passing it to the LC3 encoder.
With a Samsung Galaxy S25, the audio quality is consistently good.
With a Google Pixel 7, however, the behavior is different: after establishing the LE Audio connection, the audio quality is either good or noticeably degraded/“robotic”. Once the connection is established, the quality remains in that state for the entire connection. Reconnecting or restarting the device can result in either a good or a bad connection again.
This makes us suspect that the issue may not be caused by the resampling itself, but rather by something that is configured or initialized during LE Audio stream establishment.
Could this behavior be related to the negotiated BAP/ASE/CIS/QoS configuration, ISO timing, or another Android-specific LE Audio configuration?
Are there any known differences or issues with Pixel devices in this regard, or any LE Audio parameters/callbacks we should specifically check to determine why one connection starts in a good state while another starts in a degraded state?
Thanks in advance for your help.
Best regards,
Raphael