Obsolete
Status Update
Comments
dn...@google.com <dn...@google.com>
dn...@google.com <dn...@google.com> #2
This issue does not reproduce with dev preview 4.
al...@gmail.com <al...@gmail.com> #3
Closing this issue as per comment #2 from reporter.
dn...@google.com <dn...@google.com> #4
Please provide access to the file shared in comment #3 .
al...@gmail.com <al...@gmail.com> #5
Hi, sorry about that; access provided
dn...@google.com <dn...@google.com> #6
We have passed this to the development team and will update this issue with more information as it becomes available.
ar...@google.com <ar...@google.com> #7
This observation is not correct.
Because of interoperability issues with car kits that in fact CLAIM to support 48kHz, but then do not render audio that is sent, 48kHz AAC has been disabled:
http://r.android.com/408420
This is very unfortunate since the phone cannot tell that the remote device has any problem rendering audio if in it's capabilities the device claims that it can indeed do 48kHz.
Such is the nature of Bluetooth interoperability unfortunately and we've taken the step to disable 48kHz AAC as a result.
Because of interoperability issues with car kits that in fact CLAIM to support 48kHz, but then do not render audio that is sent, 48kHz AAC has been disabled:
This is very unfortunate since the phone cannot tell that the remote device has any problem rendering audio if in it's capabilities the device claims that it can indeed do 48kHz.
Such is the nature of Bluetooth interoperability unfortunately and we've taken the step to disable 48kHz AAC as a result.
ec...@gmail.com <ec...@gmail.com> #8
I'm still seeing exactly the same behaviour described in this bug in the final Oreo release (OPR6.170623.012) on my Pixel XL with my BMW 1 Series. Is it possible that the cause of the problem was misidentified as being an issue with the sample rate by the original reporter? If so, should a new issue be raised?
m....@gmail.com <m....@gmail.com> #9
still the same problem with final 8.0 on Pixel XL and Nexus 5x
sh...@gmail.com <sh...@gmail.com> #10
Same issue on Oreo final. BMW 3 series
ga...@gmail.com <ga...@gmail.com> #11
Same problem with final 8.0 on my BMW 5 series
al...@gmail.com <al...@gmail.com> #12
I think it's been misidentified. When I go to the bluetooth settings, it shows as streaming with 44.1khz. Sound still does not work with OPR6.170623.012 / Nexus 5X and BMW3 series.
ch...@gmail.com <ch...@gmail.com> #13
Same issue here. Pixel XL, on final 8.0 BMW 4 series. Bluetooth audio worked well on 7.1.1, It also was working with a manual override until last week. Now no combination of bitrate or codecs works.
ma...@gmail.com <ma...@gmail.com> #14
Can't pair my w770 citizen bluetooth watch.
It connects and disconnects after about 15 secs
It connects and disconnects after about 15 secs
Description
OPP4.170623.014
* What device are you using? (for example, Nexus 6P)
Nexus 5X
* What are the steps to reproduce the problem? (Please provide the minimal reproducible test case.)
Connect Nexus 5x to bluetooth audio device that does *not* support 48khz bluetooth audio (e.g. BMW/Mini audio systems).
Attempt to play any audio or other media.
* Issue Category e.g. Framework (platform), NDK (platform), Hardware (CPU, GPU, Sensor, Camera), ART (platform), Runtime Permissions etc
Framework
* What was the expected result?
The media profile of Android switches to 44.1khz audio automatically to match the limited sample rate.
* What was the actual result?
No audio plays through the bluetooth device
Additional info----
The report is similar to
Sometimes (not always) it works for a short while if you forget the bluetooth pairing on both devices and pair again; however it fails to work on next connect.