Android Oreo carries over Bluetooth issues from Nougat

Since Pixel phones running Nougat have had some issues with Bluetooth connectivity, many people expected that Android Oreo would fix that. Alas, many Pixel and Nexus owners are now taking to Google's product forums to report that the latest version of Android has not fixed their Bluetooth woes.

Many users are complaining about the now-well-known bug where Bluetooth turns off on their device and can't be turned on until the device is rebooted, while others are reporting that connectivity is dropping temporarily while listening to music, causing slow down and weird scratching noises.

As was the case with Nougat, many Bluetooth connectivity issues have to do with Android Auto. Some users of Android Auto are reporting that media content is not displaying correctly, that their Nexus or Pixel phone is shown as "Paired", but there's no audio playing, and that the music is skipping, among other issues.

Some of the users reporting these problems have been on Android Oreo since the first developer preview and they claim that the bugs have been there ever since the first preview build.

Google has now began bug-hunting and is asking users on its product forums to submit the bugs they may have encountered by providing information about their car model and/or accessories that they've been using when the problem appears.



2. jove39

Posts: 2146; Member since: Oct 18, 2011

Looks like google forgot about android auto.

4. Panzer

Posts: 282; Member since: May 13, 2016

And why do I want to Beta test for Google? And people wonder why Android devices take so long to get an update. When the base code is a bug ridden mess when OEM's have to debug it so basic functions work. So glad I moved away from the Nexus line with the release of the PIxel. Very happy with my functioning Bluetooth on my S8. And this is not an Android issue only I am quite certian ios11 will have issues. Rather be late to the party then breaking down on the side of the road 30 times to get there first.

5. Skizzo

Posts: 403; Member since: Jul 14, 2013

Well, back in the days of the Nexus line, you were basically buying in at a cheaper cost to BE a beta tester. You'd get a top tier phone at a cheaper cost, but it was a "developer device" of sorts, so things like this were more forgivable. The Pixel is, or should be, a consumer ready device like any other brand at that price, so this is not excusable.

8. erdilmeet unregistered

The most logical reason people so far don't understand. Nexus line was more sensible but someone at Google messed up big time. Stock Android with few time bound exclusive features at premium price? No way. Agreed iOS too has it's own share of bugs but the restrictive environment saves Apple though their arrogance and premium pricing hardly makes sense but Android is far too open and too wide to cover all price segments to make a case for premium segment. Hopefully this gets fixed soon!

6. Scott93274

Posts: 6038; Member since: Aug 06, 2013

Hmm... I'm not even sure if I'm on the consumer release of Android Oreo yet, I'm probably still on beta to be honest, but thus far I haven't experienced any issues with BlueTooth. Though I use it sparingly and only with 2 devices. I hope they are able to fix the issue soon though, whatever is causing it. Also, I've been having issues with my Google Play Music on my Chrome web browser where it's formatted incorrectly and the text is overlapping with images and other text. I've reported the issue, but it's been a week and I don't even know if other people are experiencing the issue.

7. HansP

Posts: 542; Member since: Oct 16, 2011

I just don't get devs at Google. Both Bluetooth performance and lossless audio playback has been known issues since before 1.0. Yet, they just don't bother fixing either of them. If Google is really going to release a phone without a headphone jack, they first need to clean out their software department.

9. erdilmeet unregistered

Bringing back Nexus line or less premium pricing is the only saving grace for Google. No one wants to pay premium for dollars and expect software like this. They could have extended the testing though. I expect something similar for iOS 11 but more controlled enviroment :)

10. HansP

Posts: 542; Member since: Oct 16, 2011

No thanks, I'd like to control my own environment, thank you very much. :)

11. buccob

Posts: 2968; Member since: Jun 19, 2012

I really don't know why Google dropped the ball so hard with Bluetooth starting with Lollipop. I have had issues with my song's metadata being recognized by bluetooth players... some infrequent sound skips... etc. And it all started with Lollipop, then continue with Marshmallows and I still suffer it with Nougat. I am actually half happy that my bluetooth headphones broke because I have been a bit forced on using my wired sets, including my noise cancelling pair that were collecting a bit of dust... (though my other BT headset SBH52 works wonderfully)... Anyway, Google need to get their sh!t together... Bluetooth is extremely important in 2017

Latest Stories

This copy is for your personal, non-commercial use only. You can order presentation-ready copies for distribution to your colleagues, clients or customers at or use the Reprints & Permissions tool that appears at the bottom of each web page. Visit for samples and additional information.