If your device is running Android 7.1.1 and having problems with Bluetooth on your phone when trying to pair it to your car, you haven’t been alone. In fact, an issue thread over at the Android code repository has been brewing for months and Google finally marked it as FutureRelease.
The issue in question is an inability to stay connected to in-car Bluetooth systems, reported by multiple Huawei Nexus 6P, Google Pixel, and Google Pixel XL owners who had updated to Google’s latest Android 7.1.1 Nougat build with the build number NPF10C . Users reported that their device would connect to a vehicle’s built-in Bluetooth systems without much issue, but would then disconnect a few seconds later with no warning, error message, or indication as to why it was happening.
Few users also said that the issue only affects vehicle systems, leaving Bluetooth audio capabilities with devices like speakers and headphones perfectly intact. The fairly widespread issue affected a large number of users, garnering 161 posts on the Google bug tracking forum alone.
Thankfully, the wait for a fix may soon be over. A Google project member has confirmed that the development team has fixed the issue.
The only matter now is figuring out when it’ll be made available. They were only willing to share that they will have it in a “future build.” We assume the build would be one of the monthly security updates coming out and we’d hope it’s the very next one, but there’s the possibility that it could come at a later time.
In any case, knowing the bug has been squashed offers some nice peace of mind for those who were suffering.
Source : AOSP Issue Tracker
The issue in question is an inability to stay connected to in-car Bluetooth systems, reported by multiple Huawei Nexus 6P, Google Pixel, and Google Pixel XL owners who had updated to Google’s latest Android 7.1.1 Nougat build with the build number NPF10C . Users reported that their device would connect to a vehicle’s built-in Bluetooth systems without much issue, but would then disconnect a few seconds later with no warning, error message, or indication as to why it was happening.
Few users also said that the issue only affects vehicle systems, leaving Bluetooth audio capabilities with devices like speakers and headphones perfectly intact. The fairly widespread issue affected a large number of users, garnering 161 posts on the Google bug tracking forum alone.
Thankfully, the wait for a fix may soon be over. A Google project member has confirmed that the development team has fixed the issue.
The only matter now is figuring out when it’ll be made available. They were only willing to share that they will have it in a “future build.” We assume the build would be one of the monthly security updates coming out and we’d hope it’s the very next one, but there’s the possibility that it could come at a later time.
In any case, knowing the bug has been squashed offers some nice peace of mind for those who were suffering.
Source : AOSP Issue Tracker