UPDATE: Uninstalling Open Garden resolved the issue.
Anyone have these and if so do they work OK with your GS4? I have a pair and they worked great until around the time I updated the firmware to MF9, then they couldn't hold a connection to my GS4 for more than a minute or two while streaming music. I wasn't sure what the problem was as all my other bluetooth devices still paired fine with my GS4 (including another stereo headset) so I RMA'd the Bluebuds. I just received my new pair of Bluebudsx X and they have the exact same problem.
I have 3 sets of them and they all work perfectly. I do use them with poweramp pro, MX player pro and for phone calls occasionally. I am also running ViperFX.
SGS4 Sent
ifly4vamerica said:
I have 3 sets of them and they all work perfectly. I do use them with poweramp pro, MX player pro and for phone calls occasionally. I am also running ViperFX.
SGS4 Sent
Click to expand...
Click to collapse
Thanks for the reply. That's odd. Are you running stock MF9? I'm unfamiliar with ViperFX, is that just like an equalizer program or does it alter the bluetooth stack somehow?
On a hunch I decided to uninstall Open Garden after trying a few other random things. Open Garden is a connection sharing app that uses bluetooth. Seems that did the trick, the Bluebuds are working flawlessly now. Open Garden didn't seem to work anyway, it seems Sprint has successfully blocked it through the firmware. Will update original title. Thanks again for the response iflyforVA, it prompted me to dig a little deeper.
cbaronne has posted a set of compiled binaries to change the default bitrate of the Bluetooth SBC codec to increase A2DP audio quality on the Nexus 4 over on this thread. It seems that the 2013 Nexus 7 suffers from the same issues, but can also be fixed with the same binaries.
I've very lightly modified itlnstln's update script to work on the Nexus 7 and have tested these files as flashable under TWRP. The binaries in the flo-4.3-BTFix-googledefault.zip file are from the ParanoidAndroid 3.94 ROM (which I would highly recommend) should you experience troubles with your Bluetooth devices.
I would recommend trying the 328kbps version first, and would expect it to provide the best quality in most situations since it matches the sampling rate of most MP3 files. Most Bluetooth stacks for other devices have 328 as the maximum quality. Of course, test with your devices and ears.
For device testing, I've used it to great success with a BlackBerry Music Gateway (still stuck at low volume, but that's an AVRCP volume control issue) and a Philips AEA2000/37 Bluetooth receiver. I also have an eBay/Chinese receiver which identifies itself as DMZmusic where this change causes continuous popping noises from both my Nexus 4 and Nexus 7. That device is perfectly fine when paired with my other devices that stream at full quality with A2DP SBC (BlackBerry Playbook, WP7 phone, and Windows PC using the Toshiba stack), so clearly Google still has some work to do. Until then, hopefully these files prove to be useful.
Install
random_n said:
cbaronne has posted a set of compiled binaries to change the default bitrate of the Bluetooth SBC codec to increase A2DP audio quality on the Nexus 4 over on this thread. It seems that the 2013 Nexus 7 suffers from the same issues, but can also be fixed with the same binaries.
I've very lightly modified itlnstln's update script to work on the Nexus 7 and have tested these files as flashable under TWRP. The binaries in the flo-4.3-BTFix-googledefault.zip file are from the ParanoidAndroid 3.94 ROM (which I would highly recommend) should you experience troubles with your Bluetooth devices.
I would recommend trying the 328kbps version first, and would expect it to provide the best quality in most situations since it matches the sampling rate of most MP3 files. Most Bluetooth stacks for other devices have 328 as the maximum quality. Of course, test with your devices and ears.
For device testing, I've used it to great success with a BlackBerry Music Gateway (still stuck at low volume, but that's an AVRCP volume control issue) and a Philips AEA2000/37 Bluetooth receiver. I also have an eBay/Chinese receiver which identifies itself as DMZmusic where this change causes continuous popping noises from both my Nexus 4 and Nexus 7. That device is perfectly fine when paired with my other devices that stream at full quality with A2DP SBC (BlackBerry Playbook, WP7 phone, and Windows PC using the Toshiba stack), so clearly Google still has some work to do. Until then, hopefully these files prove to be useful.
Click to expand...
Click to collapse
Thanks for this post I am having issues with Audio when listening to Netflix movies. Can I just flash this using TWRP?
comptech81 said:
Thanks for this post I am having issues with Audio when listening to Netflix movies. Can I just flash this using TWRP?
Click to expand...
Click to collapse
Yes, just flash with TWRP. Note that this only affects A2DP Bluetooth audio (ie: wireless headphones and stereo receivers) in situations where it sounds like Internet radio from the year 2001 and won't do a thing for the static noise when using the onboard speakers at low volume.
328K did seem to help with Netflix + BT but it certainly wasnt perfect. Its rather disappointing that such a powerful tablet cant even BT + netflix properly.
Thanks much for sharing.
Aren't any Android Tablets/Phones out there which support BT-MP3/AAC Codec? Maybe those can be ported to Nexus devices?
volwrath said:
328K did seem to help with Netflix + BT but it certainly wasnt perfect. Its rather disappointing that such a powerful tablet cant even BT + netflix properly.
Click to expand...
Click to collapse
I don't think you can blame the Nexus 7. I reverted to the previous version of the netflix app and the audio is fine. It appears netflix broke something with the latest update.
random_n said:
cbaronne has posted a set of compiled binaries to change the default bitrate of the Bluetooth SBC codec to increase A2DP audio quality on the Nexus 4 over on this thread. It seems that the 2013 Nexus 7 suffers from the same issues, but can also be fixed with the same binaries.
I've very lightly modified itlnstln's update script to work on the Nexus 7 and have tested these files as flashable under TWRP. The binaries in the flo-4.3-BTFix-googledefault.zip file are from the ParanoidAndroid 3.94 ROM (which I would highly recommend) should you experience troubles with your Bluetooth devices.
I would recommend trying the 328kbps version first, and would expect it to provide the best quality in most situations since it matches the sampling rate of most MP3 files. Most Bluetooth stacks for other devices have 328 as the maximum quality. Of course, test with your devices and ears.
For device testing, I've used it to great success with a BlackBerry Music Gateway (still stuck at low volume, but that's an AVRCP volume control issue) and a Philips AEA2000/37 Bluetooth receiver. I also have an eBay/Chinese receiver which identifies itself as DMZmusic where this change causes continuous popping noises from both my Nexus 4 and Nexus 7. That device is perfectly fine when paired with my other devices that stream at full quality with A2DP SBC (BlackBerry Playbook, WP7 phone, and Windows PC using the Toshiba stack), so clearly Google still has some work to do. Until then, hopefully these files prove to be useful.
Click to expand...
Click to collapse
I don't know if this is related to the problem of BT keyboards working properly (interference on the 2.4 Ghz band between WiFi and BT), but if it is, would you know how to fix that problem as well? Only reason I ask is that I was under the impression that BT audio also suffered from the interference issue, and would especially make sense if paired up with netflix streaming (which would be sending data over WiFi simultaneously).
SubMatrix said:
I don't know if this is related to the problem of BT keyboards working properly (interference on the 2.4 Ghz band between WiFi and BT), but if it is, would you know how to fix that problem as well? Only reason I ask is that I was under the impression that BT audio also suffered from the interference issue, and would especially make sense if paired up with netflix streaming (which would be sending data over WiFi simultaneously).
Click to expand...
Click to collapse
I haven't dealt with that issue specifically on the Nexus 7, but I have had nothing but terrible luck with most Bluetooth HID devices for PCs and now just recommend using sets from Logitech or Microsoft with proprietary RF USB dongles. Apple's devices tend to work OK though. As for interference, I have no trouble streaming BT audio while also pulling HD video over my 2.4GHz WLAN, but then again I'm not in a very RF saturated area and also have automatic channel hopping disabled on my WiFi AP. If you're in a highrise or something like that, the only possible solution is going to be to get your WLAN onto 5.8GHz to try and free up some spectrum.
I don't think I've heard of any Android devices that do MP3 or AAC BT audio, but there are quite a few that can do AptX. As far as I know, only the manufacturer ROMs provide the codecs for this (ie: flashing CyanogenMod to an SGSIII will kill AptX), and receiver compatibility is pretty low. It's a shame that there are so many cooks in the Bluetooth kitchen that we end up with this metaphorical beef and Cheetos stew.
gramig said:
I don't think you can blame the Nexus 7. I reverted to the previous version of the netflix app and the audio is fine. It appears netflix broke something with the latest update.
Click to expand...
Click to collapse
Ill have to try that. Nonetheless there are some bt issues relating to 4.3. I was attempting to watch a youtube via bt headphones and my vz hotspot on my SGS3 and it stuttered along, but when I turned off bluetooth it streamed fine. This is rather aggravating.
tried btfix 328kbps didn't help me i use my sony nfc headphone but doesn't work properly when using Netflix sounds get cut. well anyone mind sharing old version of Netflix apo please
Sent from my GT-I9505 using xda premium
gramig said:
I don't think you can blame the Nexus 7. I reverted to the previous version of the netflix app and the audio is fine. It appears netflix broke something with the latest update.
Click to expand...
Click to collapse
Thanks posting your fix. I just reverted to a previous version of netflix and now I have absolutely no audio issues over bluetooth.
Old neflix can be found here: http://forum.xda-developers.com/showthread.php?t=2305091
:good: Huge thank you to OP. Ever since I got my nexus 4, it always had crappy bluetooth audio playback. For a while I wondered if my speakers in the car were damaged also but I tried your fixed and it worked flawlessly. Crystal clear and rich sound now. This is confirmed working on the latest stock nexus 4 jwr66y
-- Post deleted -- web site didn't load that other people had asked my question. It just did and I see it. Can't find 'delete' option here.
You know, I downloaded a Beats Audio APK and that did the trick. Just google BeatsAudio07.02.zip and the first link will where you can download it. I noticed a big difference on my N7 I use at home and definitely the N7 I have installed in my car. The sound thru my Infinity System sounds like crap. Once I downloaded and flashed this zip, it was a huge improvement. :good:
Just got a netflix update last night (3.0.1 build 1016,) fixes the bt issues I had with it =]
Can't update
Does anyone have the default audio.a2dp.default.so, after applying this fix I can no longer OTA.
SireSalty said:
Does anyone have the default audio.a2dp.default.so, after applying this fix I can no longer OTA.
Click to expand...
Click to collapse
Same here...
Error: Unfortunately, Bluetooth share has stopped
Hi Guys, I'm new to N7 and first thing I wanted to do is to upgrade BT audio q. After causing endless bootloop (X), I had to restore device to factory settings using Nexus Root Toolkit v 1.7.8 and loading Android 4.4.0 - Build: KRT16S. Only after that, I tried again to flash "flo-4.3-BTFix-328kbps-2013-08-18.zip" and everything looked ok until boot when there was a pop up message with an error: "Unfortunately, Bluetooth share has stopped". Same with other zip (345kbps). Any idea where might be the problem?
EDIT: Obviously I was trying to use 4.3 fix for 4.4. build When I realized it, I loaded again 4.3 system, flashed zip and seems to be ok now!
So anyway @random_n, could you please update this fix so it would work for 4.4 as well. It would be greatly appreciated!
Has anyone found a kitkat audio fix yet? I justvtried my BT headphones with my n7, and the sound is ungodly bad compared to my galaxy s3.
Since the tablet gets longer battery life, I'd prefer to use it for my wireless audio instead of the s3.
Hey everyone!
I'm having an issue that I can't seem to resolve. I have a Galaxy S5 that recently received the lollipop update. Prior to this update when playing music from Google Play Music the track/artist metadata would pass and show up on my car's stereo display. Post update I can still connect, play music over bluetooth, and control the music with steering wheel/dash controls, but the metadata no longer displays (using Google Play Music).
I did some different tests and if I play a mp3 file from the stock music app the metadata is passed. I also connected my wife's phone ( Moto X still on KitKat) and tried streaming music though GP Music and the metadata shows up as expected. I've tried deleting/pairing my phone again and even did a factory reset on my S5 last night, but nothing seems to resolve this.
I know there seems to be hit or miss with AVRCP. I haven't been able to find much in terms of actual information and thought I'd check in to see if anyone has had a similar experience or would possibly have a solution.
Thanks!
I am also having the same issue. Sprint basically told me that it isn't their problem and to wait it out. I've downloaded suggested apps and everything else except doing a hard reset.
MP3 metadata not showing over Bluetooth in car - T-Mobile
I just updated to the latest release for my Galaxy S5, Lollipop, and everything seems to work like a champ, except the streaming of music from my phone to my car's in-dash receiver. Prior to the upgrade, everything worked great. All metadata was passed along, as well as the track progress, and skip forward and backward. After the update, the music will play just fine, but I cannot skip tracks from my car stereo or steering wheel controls any more, I have to do it from my phone. Also, none of the metadata is passed along to my stereo.
I use the stock music app on my phone, but I also tried the Google Play Music app, and it does the same thing. The MP3 files are all stored locally on my SD card.
I'm hoping someone else out there has had this problem, and has solved it. Thanks.
Galaxy S5 SongTitle/Artis Display Problem
blinduvula said:
Hey everyone!
I'm having an issue that I can't seem to resolve. I have a Galaxy S5 that recently received the lollipop update. Prior to this update when playing music from Google Play Music the track/artist metadata would pass and show up on my car's stereo display. Post update I can still connect, play music over bluetooth, and control the music with steering wheel/dash controls, but the metadata no longer displays (using Google Play Music).
I did some different tests and if I play a mp3 file from the stock music app the metadata is passed. I also connected my wife's phone ( Moto X still on KitKat) and tried streaming music though GP Music and the metadata shows up as expected. I've tried deleting/pairing my phone again and even did a factory reset on my S5 last night, but nothing seems to resolve this.
I know there seems to be hit or miss with AVRCP. I haven't been able to find much in terms of actual information and thought I'd check in to see if anyone has had a similar experience or would possibly have a solution.
Thanks!
Click to expand...
Click to collapse
I have exactly the same problem. After the lolipop upgrade of S5 I was not able to see the track/artist name on the display of my car anymore. However the there is no problem with streaming of music to car speakers. I'm using spotify but I tried playing mp3 files and different applications. None of them worked. Car display only shows the device name of the S5. I contacted Samsung support with the hope to get an answer and the first thing they asked was whether I tried the device with another bluetooth capable device. No way! I have another car but no bluetooth capability. Recently Samsung deployed another update after lolipop upgrade but the same again.
Having the artis/track name; does it contribute too much? won't make you fly but it was there when we had the kit kat on S5 and missing at the moment. Yes I have the same problem but don't have a resolution... Would be great to hear different ideas or a workaround from Samsung!
Thanks.
Same problem here on my Galaxy S5 with TW Lollipop. I'm so disappointed about all the stuff that changed (e.g notifications) or does not work like Bluetooth avrcp. I start to regret the update to LP. And I wated over a year...
A temporary fix could be to download Music mate from the app store, (it can pull songs from play music onto your device). Not sure if this would help you guys as it seems some of you have already got local access to the mp3s etc.
Just thought I'd say anyway just incase.
Good luck
Shaolin36 said:
A temporary fix could be to download Music mate from the app store, (it can pull songs from play music onto your device). Not sure if this would help you guys as it seems some of you have already got local access to the mp3s etc.
Just thought I'd say anyway just incase.
Good luck
Click to expand...
Click to collapse
Thanks for the suggestion. Music Mate needs a Google Play account which I don't have. I tried another suggested app which should fix this temporary (Bluetooth something) but it did not work. Which I had suspected because the root cause seams to be AVRCP 1.5 inside Android Lollipop instead of older backward compatible versions 1.3 or 1.4. The suspicion is that Google's engeenier didn't have older / legacy / enough different Bluetooth car cits to test. Compiling the source code with a compiler switch, which disables AVRCP 1.5 leads to working meta information. Because Bluedroid is a new proprietary stack newly build by Google it doesn't help to have its source open. There is no APK which we can exchange with a working older version. Instead it seams to be compiled into core components of Android. So the only two chances seams to be:
1. Samsung / Your Handset provider pushes an update which fixes this
2. somebody finds a way through XPOSED to patch the relevant stuff into a life Lollipop.
Help troubleshooting Nexus Player
I got my player about a month ago. After about a week, I started to get the audio drop issue. I contacted support, and they just had me RMA it. So I got my new device, and no Audio drops. However I have other problems. I can not cast to the device, it doesn't show up in my list of devices in my browser, and when I try from my phone, it instantly disconnects. Also every time I try to watch a video on Netflix I about 1 second of video before an error says it can't play this title, try again later (AIP-703). I worked with Nexus support and got no where, so I went rogue. Downloaded 6.0 marshmallow and flashed my device, it loaded up, but The Netflix app wouldn't load, and I did not try casting. So I wiped the device and installed 5.1.1 again, and back to the same issue. Looking for any advice. to help clear this up as phone support is next to useless.
There was a very recent update that does some system improvements and tweaks. Reportedly fixes casting, not sure what else. Go into settings, about, and check for updates.
As far as Netflix, the most recent app works fine for me. I would check to see if yours is fully updated. If it's still problematic, remove it and try side loading the Sony version with ES File Explorer http://forum.xda-developers.com/showpost.php?p=60723403&postcount=24
I couldn't cast to my nexus player after i updated the "google cast receiver app". I unistalled the update and everything went back to normal. I'm on 5.1.1.
Casting netflix on nexus player sucks. It will cast only if the profile selected on the nexus player is the same as the one on your phone or tablet( and the same netflix account of course ).
I will update to 6.0 if anyone confirms that sixaxis is working since i'm using my ps3 controllers.
update ?
Did you ever get this fixed i recently RMA mines and am having the same issues. They told me they changed the motherboard when i asked.
Hi Guys,
i have some troubles with my new 6P...
Everythings works fine. Almost everything. I have a good internet connection but i can't watch Netflix or Youtube the way i want.
Netflix Problem:
With my Chromecast 2 everything works fine, but if i want to watch a episode on my phone, there's only sound but no video...
Youtube Problem:
Since the last update of the Youtube app i can't stream HD Videos without buffering every 10-15 seconds. As I said, my internet is quit good (10+ MB/s).
My Device:
Nexus 6P 64GB
CyanogenMod 13 Nightlies (newest)
FrancoKernel
Xposed
Thank you for your help, Manuel
So I have been having this problem only occur on the Netflix application. Youtube is working just fine. I have tried casting Netflix using the Microsoft Wireless Adapter and it doesn't play like it should. I don't have any other casting devices to test it. I can see the subtitles and hear the sound but the image itself is not showing up on the screen at all.
I tried turning off all the themes from CMTE and reboot the phone so that it is back to stock and it still isn't working. So it may not be theme related.
My Device:
Nexus 6P 32GB
PureNexus CMTE version 3/15/2016 (Clean Install)
ElementalX Kernel (No device changes, all basic config)