Bluetooth streaming choppy with LG 3 on Lollipop

[bisebaer]

Yesterday, I updated my (European) LG G3 to Lollipop, but since, the bluetooth audio stream in my car (Nissan new Note) drops randomly in songs - it's just a very short drop, but still noticeable. Sometimes it happens several times in one song, sometimes not. I have disabled the experimental NuPlayer in the Developer's options, but to no avail. I have also deleted all bluetooth connections on my phone and in my car, repaired, ... but no luck. Any suggestions?
Thanks in advance!

 

[bisebaer]

OK, one step further: the streaming works fine as long as the screen of my G3 is on, but as soon as it goes to sleep, I get drops ... Any idea how I can solve this? I've been looking around on Google, but haven't found a solution that works ...

 

[queenren]

I think it's a problem with Android overall. I had this exact same problem on my Galaxy Note 2, Note 4, and it was really bad on my S5. I was lurking in this forum because I was thinking of getting the LG G3 hoping that it wouldn't have this issue.

Did you have this problem before the lollipop update?

 

[bisebaer]

Indeed, from what I read, it's an Android- and not LG G3-related problem. But it only started for me after the update to Android 5.0. I hope that 5.0.1 will solve this ...?

 

[queenren]

I read on XDA forums that it may have something to do with having ART on. Try switching to dalvik in developer option and see if that helps. If that's an option on the G3


Sent from my iPhone using Tapatalk

 

[bisebaer]

I read on XDA forums that it may have something to do with having ART on. Try switching to dalvik in developer option and see if that helps. If that's an option on the G3

Unless I've overlooked it, I don't seen that option in the developer settings anywhere ...

 

[queenren]

Well that sucks. I hope that 5.0.1 will fix the problem. Please report back if you are able to fix it somehow.


Sent from my iPhone using Tapatalk

 

[bisebaer]

Will do! German users report the same problem - seems to be firmware-related, indeed.

 

[Nuuq]

Same problem here... Started happening since 5.0. Hope someone will fix this...

 

[stmax]

I also noticed this the other day trying to stream Google play music to my blue tooth speaker. I am on version 5. I don't believe the issue existed before the update.

Posted via the Android Central App

 

[bisebaer]

It seems that it is indeed caused by the ART-runtime. I've read several other complaints about the same issue, but on other devices, and all are on ART. I hope they fix it soon ...

 

[Rayfire]

I really wish they would fix that. I'm running 4.4.2 right now, and I've changed my runtime to ART and so far my Spotify has been seamlessly streaming via bluetooth to my car or my bt headset.

 

[stmax]

Is that why it seems to be an issue with the L update?

Posted via the Android Central App

 

[bisebaer]

I think so, yes. Users who were on 4.4 and switched to ART had the same problems; going back to Dalvik solved it.

 

[Lefty Righty]

Well that sucks. I hope that 5.0.1 will fix the problem.

Still just as bad on 5.0.1 with Nexus 5 and 7.
Here's hoping for 5.0.2.

 

[Oliver Collings]

I was worried I was the only one with this issue.

This could make me stop my Google Play subscription because I use this in my car a lot. I may have to go old school and use an SD card or god forbid a CD!

Posted via Android Central App

 

[kofasetic]

It seems the bluetooth issue is prevalent throughout Lollipop versions.
Even tried bluetooth in a variety of ROMS and they all have this bug.
Quite annoying so I flashed back to KitKat (ROM: Vanir)

 

[Danny Long2]

Joke really that big companies like Google etc can't do basics like bluetooth streaming

Posted via the Android Central App

 

[eagle_23]

same with me i was having bluetooth and nfc connections since updated to android 5.0. hope this gets fixed soon....

Posted via the Android Central App

 

[stmax]

I just received another update to lollipop and the blue tooth music streams clear to my car now! Could it actually be fixed?

Posted via the Android Central App