Issue observed on Bob device on 10176.22.0 build

The only cras error in the logs are as follows:
2017-12-18T11:19:49.276637-08:00 ERR cras_server[1773]: AT command AT+BTRH? not supported
2017-12-18T11:19:49.295967-08:00 ERR cras_server[1773]: AT command AT+XAPL=009E-400C-0106,3 not supported
2017-12-18T11:19:49.325832-08:00 ERR cras_server[1773]: AT command AT+XEVENT=Bose SoundLink,158 not supported
2017-12-18T11:19:49.467585-08:00 ERR cras_server[1773]: Bluetooth indicator activation command AT+BIA=0,0,0,1,1,1,0

Joseph. There are lots of bluetooth debug logs. Can you take a look? Is there an existing bluetooth autotest that can show when regression started?


pbathini@ Is this always reproducible? Can you also attach audio_diagnostics logs? Does M63 have this issue on Bob? Does this also happen on Kevin in M64? 

Hi Pramod, how long does it take to repro the issue? Have you observed the issue on other platforms in addition to Bob?

Re #4 , PFA the audio_diagnostics logs

Deleted: audio_diagnostics.txt 581 KB

audio_diagnostics.txt 581 KB View Download

Re #7 , 

It's easily reproducible using Bose soundlink headphones connected.

I have seen the issue on quawks also

I have seen the issue on kevin also on M-64 10176.22.0 

Deleted: audio_diagnostics.txt 565 KB

audio_diagnostics.txt 565 KB View Download

Deleted: debug-logs_20180102-163033.tgz 284 KB

debug-logs_20180102-163033.tgz 284 KB Download

Joseph and Jimmy. Can you take a look?

Issue is also seen on Minnie on 10323.2.0 build when using the Bose QC35 headphones

Friendly ping! Any update on this? 

Hi Hsin-yu or Jimmy, are you able to take over this issue? I have a good number of issues in hand for the time being. If you are also occupied with issues, I could work on it later. Thanks!

Hi Joseph, I think this issue is on BT side so it would be better for you to work with BT chip vendor to investigate this. Maybe you can create an issue in buganizer and track there ?

CRAS sends data to BT socket following the correct schedule, without errors, so there is not much we can do here.

Also, an interesting point is, bob does not have issue, while kevin has this issue.

According to comment #3, bob _does have this issue. Which would make sense if this is a firmware issue since Kevin and Bob have the same BT chip.

Hi Jimmy and Rahul, thanks for your analysis. I will keep this issue with me :-)

Last time I checked with Joseph on bob, we did not find noise on QC35.
Need to double check on it...

Thanks Joseph!

I think I have similar issue.  When I have my QC35 connected to Pixelbook via BT and choose QC35 Microphone, I hear noise and audio quality degrades significantly.  If I switch to Internal Microphone, audio quality goes back to normal.