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.
Related
All,
Does anybody have any fixes regarding the sound quality when using Bluetooth A2DP protocol? I use my Evo to mate with a Bluetooth receiver so I can listen to Rhapsody over my home stereo. The sound quality is flat. The high frequencies are not present. It sounds like a bad quality MP3. I know that its the A2DP causing the quality issue as directly connection (through 3.5 jack) is awsome.
The Apple 3GS A2DP sound quality was awsome. I am not sure why the Evo is not sounding good. Any help would be most appreciated.
Thanks,
Lance
use the cyanogen rom--this uses a bitpool of 53 giving you the best bluetooth quality possible. the stock/sprint/htc bluetooth drivers are set for a bitpool of 32
Is there any other ROM that has the bit pool set to 53?
Lance
Nope all Sense roms use HTC's ****ty low bitpool setting. This is why I'm running CM as well it's the only rom I can A2DP to my Sony Head unit and get good audio. I attempted to contact HTC about this issue here's the juicy details
Here's my initial question
I have terrible static when streaming music over A2DP on my HTC EVO to my sony mex-bt2800 car radio. If I use CyanogenMod 6.0 which uses a open source bluetooth stack my A2DP is crystal clear to my radio. I have used logcat to look at whats going on I dont know if its a bitrate problem or a bitpool problem or if my radio isn't in your acoustic database.
http://forum.xda-developers.com/showthread.php?t=708265&highlight=bluetooth+bitrate
Here's the response I received
Although the android software has been updated to be more compatible with Bluetooth headsets and car kits. Most of the time a Bluetooth manufacturer will have a list on there website stating devices they have found compatible, but this is not always the case. From the information on your issue it seems that your device is simply not fully compatible. The only thing we would be able to recommend would be to try another headset.
Then my response back
I would like an Engineer to read my question if possible since I don't think you fully grasp what I'm saying here. First My EVO's Bluetooth A2DP WORKS 100% clearly when using a Open Source ROM which implements Bluez Bluetooth stack http://www.bluez.org/
When I run your Sense UI ROM the Stock ROM you release which uses your own proprietary Bluetooth Stack I get static in the background so you cant really say its my phone now can you? Its your implementation that's not working properly. I'm not about to try every car stereo till I find one that works with the EVO when I know my stereo can work perfectly with my phone when using a properly coded open source Bluetooth stack.
Here is some extra info from a logcat that shows how your Bluetooth makes a connection through A2DP and what I believe is too low of a bitrate or bitpool setting
http://forum.xda-developers.com/showthread.php?t=708265&highlight=bluetooth+bitrate
PLEASE DON'T GIVE ME A ANSWER THAT YOU JUST READ FROM A SCRIPT. I would like a true response from someone who understands and can grasp my question fully like an engineer or a developer, when you give me a generic response of oh your Bluetooth headset isn't compatible keep buying new ones till you find one that works, that really makes me upset since you didn't even read my question it's a car stereo and there not cheap.
I await your educated answer.
And there final bull**** reply
We apologies for any inconvenience you may be experiencing. We will document your concern for review in development of our upcoming devices and future software updates. The situation is still an incompatibility with our device and your car kit weather on software or a hardware level. Unfortunately at this we have no further information beyond what has already been provided.
P_Dub_S said:
Nope all Sense roms use HTC's ****ty low bitpool setting. This is why I'm running CM as well it's the only rom I can A2DP to my Sony Head unit and get good audio. I attempted to contact HTC about this issue here's the juicy details
Here's my initial question
I have terrible static when streaming music over A2DP on my HTC EVO to my sony mex-bt2800 car radio. If I use CyanogenMod 6.0 which uses a open source bluetooth stack my A2DP is crystal clear to my radio. I have used logcat to look at whats going on I dont know if its a bitrate problem or a bitpool problem or if my radio isn't in your acoustic database.
http://forum.xda-developers.com/showthread.php?t=708265&highlight=bluetooth+bitrate
Here's the response I received
Although the android software has been updated to be more compatible with Bluetooth headsets and car kits. Most of the time a Bluetooth manufacturer will have a list on there website stating devices they have found compatible, but this is not always the case. From the information on your issue it seems that your device is simply not fully compatible. The only thing we would be able to recommend would be to try another headset.
Then my response back
I would like an Engineer to read my question if possible since I don't think you fully grasp what I'm saying here. First My EVO's Bluetooth A2DP WORKS 100% clearly when using a Open Source ROM which implements Bluez Bluetooth stack http://www.bluez.org/
When I run your Sense UI ROM the Stock ROM you release which uses your own proprietary Bluetooth Stack I get static in the background so you cant really say its my phone now can you? Its your implementation that's not working properly. I'm not about to try every car stereo till I find one that works with the EVO when I know my stereo can work perfectly with my phone when using a properly coded open source Bluetooth stack.
Here is some extra info from a logcat that shows how your Bluetooth makes a connection through A2DP and what I believe is too low of a bitrate or bitpool setting
http://forum.xda-developers.com/showthread.php?t=708265&highlight=bluetooth+bitrate
PLEASE DON'T GIVE ME A ANSWER THAT YOU JUST READ FROM A SCRIPT. I would like a true response from someone who understands and can grasp my question fully like an engineer or a developer, when you give me a generic response of oh your Bluetooth headset isn't compatible keep buying new ones till you find one that works, that really makes me upset since you didn't even read my question it's a car stereo and there not cheap.
I await your educated answer.
And there final bull**** reply
We apologies for any inconvenience you may be experiencing. We will document your concern for review in development of our upcoming devices and future software updates. The situation is still an incompatibility with our device and your car kit weather on software or a hardware level. Unfortunately at this we have no further information beyond what has already been provided.
Click to expand...
Click to collapse
Well I commend you for trying. This is something that makes me want to tear my hair out so I would love to see this resolved as well.
good on ya mate.
anyone know how to get another bluetooth stack on stock rooted 2.2?
I asked Flipz a while ago but I don't think he's looking into it. I also asked Netarchy he said he would look into it sometime but that i shouldn't hold my breath since he hadn't even looked at the code yet. HTC has released the source for their Bluez implementation so all we need is a dev willing to look into adjusting the bitpool setting.
This is a HUGE problem. I am flashing CM6 right now. HTC I am very disappointed with you..
The cyanogen rom also has great dsp equalizer
CyanogenMod will also make you a tropical island than transform your EVO into a jet plane and take you there ;-)
But in all seriousness, yeah, CM6 has BT fixed. One of my friends nagged Cyanogen about it last month, and he patched it right away.
I wish somebody could help us by increasing the bitpool on the Bluetooth driver. The Evo would be so much more enjoyable (for me at least) if the sound quality was better thru A2DP.
lancer123 said:
Is there any other ROM that has the bit pool set to 53?
Lance
Click to expand...
Click to collapse
It would be nice if there can be a patch of some sort...
Just an update today I got a call from HTC customer service since i gave a poor review of my experience on a survey they sent me. Talked in great detail about our problem with the Bluetooth stack told him about the bitpool setting how its 53 on CM and 35 on there roms. So hopefully on the next update well get a fix for the Stock Sense UI rom.
^^LMAO!!! dont blv the hype
I read that the CM6 ROM has this issue fixed. I have also read reports that the ROM email client doesn't support word wrapping (which I really do need). Can anybody confirm this?
Also,
Can anybody in ROM land please create a patch or an update to their ROM which increases the Bitpool to 53? I understand that the Bluetooth driver code has been released.
Thanks
bump............
any roms address this yet?
greenail said:
any roms address this yet?
Click to expand...
Click to collapse
maybe:
* Added DSP Manager (Digital Signal Processing) to boost audio and equalize sound for Headset, Phone Speaker and Bluetooth devices.
wont let me post links, but you know what to do:
forum.xda-developers.com/showthread.php?t=793471
I am using the latest OTA, rooted, along with the latest pandora and the bt audio quality is much better. I have the motorola t605.
With the initial 2.2 update bt quality sucked but now it's better.
Sent from my PC36100 using XDA App
mchlwvr614 said:
I am using the latest OTA, rooted, along with the latest pandora and the bt audio quality is much better. I have the motorola t605.
With the initial 2.2 update bt quality sucked but now it's better.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
That was a streaming issue, not a bitpool issue.
The BT audio was a lot better on my TP2 when I updated the registry bitpool to 48 from 32.
I wish they would fix it.
Trying to connect the N4 to a car Bluetooth audio (2012 model car, relatively new, only 9 months old).
(1) I had a very hard time getting the two paired: lots of "connection failed" attempts until they finally connected.
(2) The phone does not send artist/track info which is surprising as I have an older LG phone running Android 2.3.4 and that sends all the info.
(3) Without any music being streamed to the car audio, if I make a phone call via the car bluetooth, when the call ends the music player on the N4 starts automatically. This is very annoying, not sure if it's a problem with the car implementation sending a "play" command at the end of the call or the N4 doing something weird. I tend to blame the N4 as two other phones, an iPhone and the older LG mentioned above do not do this.
(4) The car has a play/pause toggle that it can send to the bluetooth player. Pause works, the player on the N4 pauses, but then play doesn't work, I have to hit play on the device.
(5) After I use bluetooth on the N4, I find that sometimes the widget toggle can no longer turn bluetooth on/off until I reboot the phone.
(6) After I use bluetooth on the N4, the phone sometimes randomly reboots. Not sure if it's really related or just a coincidence. Given (5) above I suspect something is going on.
Anyone else having such a hard time with the bluetooth part? Potential hardware issue or simply buggy software that we can hope to get addressed at some point?
I have experienced the issue with track information not being sent. Also random changes in volume during playback. Seems there's still some work that needs to be done in 4.2 regarding blue tooth.
Sent from my Nexus 4 using Tapatalk HD
sirxdroid said:
(2) The phone does not send artist/track info which is surprising as I have an older LG phone running Android 2.3.4 and that sends all the info.
Click to expand...
Click to collapse
Is this an issue that can be addressed by flashing a custom ROM or perhaps using a different music player than stock or is there more to it, deep down in the bluetooth drivers and it would need a fix from Google in the form of new drivers?
Yeah I have had a few issues too. My track/artist/album names do not send where my S2 sends them. Also the headunit I have has buttons for shuffle and repeat and these do not show up at all (I assume because it detects they aren't supported). I haven't taken a call yet or tried turning BT off after streaming but I'll give it a shot and see.. My nexus 4 also randomly shuts down for no apparent reason sometimes (rarely atm). I think it's just 4.2.1 problems - I doubt a different music app will fix it (I tried one), custom ROM may work though..
My N4 is paired with an Alpine 135BT and it's worked very well so far. I initially had some trouble connecting but once they were paired I didn't have any additional connection issues. The N4 does automatically play as soon as it connects to the unit. I've got BeyondPod and Spotify installed and for whatever reason it always defaults to BeyondPod instead of Spotify even if I had BeyondPod closed and Spotify open. Not a big deal to me though.
Are you running the stock rom or a custom rom? I had my EVO LTE hooked up to the same head unit. It worked perfectly on the stock software but gave me all kinds of trouble when I started using custom roms. Otherwise, it could just be that the N4 and your particular head unit just don't play nicely together.
sirxdroid said:
Trying to connect the N4 to a car Bluetooth audio (2012 model car, relatively new, only 9 months old).
(1) I had a very hard time getting the two paired: lots of "connection failed" attempts until they finally connected.
(2) The phone does not send artist/track info which is surprising as I have an older LG phone running Android 2.3.4 and that sends all the info.
(3) Without any music being streamed to the car audio, if I make a phone call via the car bluetooth, when the call ends the music player on the N4 starts automatically. This is very annoying, not sure if it's a problem with the car implementation sending a "play" command at the end of the call or the N4 doing something weird. I tend to blame the N4 as two other phones, an iPhone and the older LG mentioned above do not do this.
(4) The car has a play/pause toggle that it can send to the bluetooth player. Pause works, the player on the N4 pauses, but then play doesn't work, I have to hit play on the device.
(5) After I use bluetooth on the N4, I find that sometimes the widget toggle can no longer turn bluetooth on/off until I reboot the phone.
(6) After I use bluetooth on the N4, the phone sometimes randomly reboots. Not sure if it's really related or just a coincidence. Given (5) above I suspect something is going on.
Anyone else having such a hard time with the bluetooth part? Potential hardware issue or simply buggy software that we can hope to get addressed at some point?
Click to expand...
Click to collapse
(1) Haven't had any connection issues so far on my vehicle or my wife's.
(2) Currently stock Android uses AVCR v1.0 which only only allows you to control via Bluetooth (play, pause, etc) but not send track info. Other manufactures that customize Android (LG, Samsung, etc) will sometimes use v1.3 that supports track info. That's why your old phone did it.
You could install a custom Rom that has v1.3. I think cm10 does.
(3) Again, not happening on my two cars. The only time the music starts after a call is if it was playing before the call. I'm wondering if you have another music/podcast player that is taking over Bluetooth controls and causing problems. I use the stock player and Player Pro. If I don't disable the headset/BT controls in Player Pro I have control issues.
(4) I have the same issue. To get around this I cheat and push the track advance button on the radio to play the next track.
(5) This is an issue I've had on all of my previous android phones. I haven't noticed I my N4 because I never toggle off Bluetooth anymore.
(6) Not having this problem but maybe try solution in (3).
Sent from my Nexus 4 using xda premium
got the sony mw600 for bluetooth audio.. no id tags on display.. on every musicplayer (play music, poweramp, cm musicplayer..) the same.
dont know why, but today even the start/stop, forward and prev. buttons didnt work! the only thing i can use is volume control..
anyone an idea?
Any luck with this?
I want to buy one but couldn't find it in Sri Lanka so planning to order one via ebay & need to check if it works. Running cyanogen mod 10, heard that the bluetooth stack was updated on CM which supports most of the features since stock rom only has older stack version which can have issues!
clsmn said:
got the sony mw600 for bluetooth audio.. no id tags on display.. on every musicplayer (play music, poweramp, cm musicplayer..) the same.
dont know why, but today even the start/stop, forward and prev. buttons didnt work! the only thing i can use is volume control..
anyone an idea?
Click to expand...
Click to collapse
dark5un0 said:
... that the bluetooth stack was updated on CM which supports most of the features since stock rom only has older stack version ...
Click to expand...
Click to collapse
using the actual cm10.1 nightly with franco r53
Wow, maybe I'll wait for a few weeks & see if it works out for you..
Sent from my Nexus 4 using xda app-developers app
dark5un0 said:
Wow, maybe I'll wait for a few weeks & see if it works out for you..
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Well.. Sound and controll works.. even headset-function works for telephone calls.. only thing not working now is id for tracks
Awesome! Thanks for the reply! I hope it worked out soon!
Sent from my Nexus 4 using xda app-developers app
I also have the track name issue. This is a massive let down. I like to just get in my car and flip through tracks with my phone in my pocket. My iPhone did this, my s3 did this. Why not the nexus 4? Come on Google. Sort it out
TrickyTree1984 said:
I also have the track name issue. This is a massive let down. I like to just get in my car and flip through tracks with my phone in my pocket. My iPhone did this, my s3 did this. Why not the nexus 4? Come on Google. Sort it out
Click to expand...
Click to collapse
my impression is that almost nothing involving Bluetooth functions as it should currently on the N4. I can't even get a mouse to work. what a shambles! it's not as if BT is some new technology. this all better get sorted out in 4.2.2.
If I'm not mistaken Google moved to a new Broadcom b/t stack. Yeah, good move! And I agree, b/t has been around for like what at least 10 years now? You'd think that getting track info should be a given by now. I have a crappy old LG phone running Gingerbread and it has no issues at all.
Bluetooth
When I got the N4, I connected my helmet headset to it and everything seems to work fine. My headset supports ad2p music and phone. Both connected and both worked, including play controls. Not sure about the audio quality, I didn't test it long enough After I flashed Jellybro (CM 10.1 Kang) Music connects, but phone goes on a connect/disconnect loop. Audio needs further testing, can't tell if the left side is off because of the bluetooth or not. Controls work most of the time, every now and again playback will decide to pause itself and sometimes the play command doesn't work. Haven't had a chance to flash stock CM 10.1 nightly yet either.
Play/Pause Works Inconsistently
Has anyone had this issue?
I am on stock 4.2.2, I connect with my car stereo no problems. I use to be able to just hit play/pause on my car stereo and it would just play music from Google Music. Now, sometimes when I hit the play/pause button on my stereo, it won't play. I have to manually hit play from my phone. After initially doing that, then I can hit play/pause and the control is there. I haven't had the problem since I got my phone on Nov 14th, this issue just started to happen. I notice this after installing Light Manager, but I have uninstalled it and still the issue is there. It is inconsistent, but the issue is more often than not.
Thanks in advance for your input.
Just reiterating, stock Android does not show artist/track info, it is not in the protocol, but you can skip tracks or go back to previous tracks. If it is important to you, you should root and get a custom ROM, not sure which ones for N4 has it though, been too happy with stock to root.
About time, Google:
http://www.androidpolice.com/2013/0...vrcp-1-3-coming-to-android-with-api-level-18/
Is anyone else having problems wit Bluetooth audio streaming in car? My music sounds like it's speed up a tiny bit. Kinda like chipmunks voices. Is this a ROM issue?
Sent from my Nexus 4 using xda app-developers app
Hi fellow xda'ers
I got the 4.3 OTA today for my Nexus 4 and the problem of stuttering bluetooth audio persists for me.
This is in reference to the bug described here: http://code.google.com/p/android/issues/detail?id=39633
I also unpaired my phone and re-paired it but still facing the same problem.
So, just wanted to ask around...
1. Is anyone still facing this same bluetooth audio bug like me in Android 4.3?
2. Can anyone who had this bug in 4.2.2 confirm that it got resolved for them in Android 4.3?
Thanks..
mailrachit said:
Hi fellow xda'ers
I got the 4.3 OTA today for my Nexus 4 and the problem of stuttering bluetooth audio persists for me.
This is in reference to the bug described here: http://code.google.com/p/android/issues/detail?id=39633
I also unpaired my phone and re-paired it but still facing the same problem.
So, just wanted to ask around...
1. Is anyone still facing this same bluetooth audio bug like me in Android 4.3?
2. Can anyone who had this bug in 4.2.2 confirm that it got resolved for them in Android 4.3?
Thanks..
Click to expand...
Click to collapse
Mine is great..plus the track name is one there now....but i never had problems in 4.2 either so.
what do you have for a stereo?
I use mine in my car (sony stereo) and i also have a bluetooth radio for my patio i got at home depot that works just fine
Every thing is fine with mine too
Sent from my Nexus 4 using XDA Premium HD app
Never had suffer stutter
Sent from my Nexus 4 using Tapatalk 4 Beta
I am using my phone with a Clarion car stereo.
The issue now is much rarer than it was before.
I guess I need to test it out for a few more days.
Thanks..
Worked fine for me in 4.2.2 .... now in 4.3 LOTS of stutter and occasional drops. Very annoying and probably related to the change of Bluetooth in 4.3 ... hope someone comes up with a fix, otherwise I'll need to go back to 4.2.2 as I use Bluetooth for music lots. Anyone that can help ... ??
I was excited to see that as soon as I upgraded from 4.2.2 to 4.3 my bluetooth streaming worked flawlessly in my car for a 2 hour drive into the mountains. However, a couple days later the stuttering came back, just as you described.
This was the one thing I was looking forward to for 4.3 but it looks like we've been let down.
mailrachit said:
I am using my phone with a Clarion car stereo.
The issue now is much rarer than it was before.
I guess I need to test it out for a few more days.
Thanks..
Click to expand...
Click to collapse
Odd, I also have a Clarion stereo. I'll be curious to try it out in another car with a different brand of stereo to see if it may just be that our phones don't play well with Clarion...
I've never had issues...I have a Sony stereo and I also play in my buddies new toyota truck and plays fine. I would try on other devices..my guess would be your problem is with the stereo than the phone
Sent from my Nexus 4 using xda app-developers app
sn0warmy said:
I was excited to see that as soon as I upgraded from 4.2.2 to 4.3 my bluetooth streaming worked flawlessly in my car for a 2 hour drive into the mountains. However, a couple days later the stuttering came back, just as you described.
This was the one thing I was looking forward to for 4.3 but it looks like we've been let down.
Odd, I also have a Clarion stereo. I'll be curious to try it out in another car with a different brand of stereo to see if it may just be that our phones don't play well with Clarion...
Click to expand...
Click to collapse
I'm not really sure, what's happening.
I tried earlier on with Poweramp Player (third party app) and Google Play Music, I had stuttering in both the apps.
Then I decided to unpair the phone/stereo, change the phone name and then re-pair. Just wanted a fresh start..
After that, I had the stuttering problem whenever I used Poweramp player. The problem happens within 5-7 min. However, when I use Google Play Music, it seems to work fine. However, I haven't tested it for long. Maybe 1 hour max, so can't say if my hypothesis is correct but I'm keeping my fingers crossed. After 7 months with this phone, I really need to get Bluetooth working.
mailrachit said:
I'm not really sure, what's happening.
I tried earlier on with Poweramp Player (third party app) and Google Play Music, I had stuttering in both the apps.
Then I decided to unpair the phone/stereo, change the phone name and then re-pair. Just wanted a fresh start..
After that, I had the stuttering problem whenever I used Poweramp player. The problem happens within 5-7 min. However, when I use Google Play Music, it seems to work fine. However, I haven't tested it for long. Maybe 1 hour max, so can't say if my hypothesis is correct but I'm keeping my fingers crossed. After 7 months with this phone, I really need to get Bluetooth working.
Click to expand...
Click to collapse
I'm in the same boat. But I really am wondering if looking at the software/apps used is the wrong method. I've been doing the same thing. Over the past 7 months I've tried various ROMs, kernels, radios etc. and nothing changes it. I've talked about it with various friends with Nexus 4's and none of them seem to have any issues.
At this point my money is on the Clarion stereo being the issue but I still have not tested the phone with another stereo. This weekend we are visiting my parents. I will try using the phone with the bluetooth on my Mom's 2013 4Runner and my Dad's 2010 F150 to see if I can replicate the problem. If it works with both their cars then I will be in the market for a new stereo. :laugh:
sn0warmy said:
I'm in the same boat. But I really am wondering if looking at the software/apps used is the wrong method. I've been doing the same thing. Over the past 7 months I've tried various ROMs, kernels, radios etc. and nothing changes it. I've talked about it with various friends with Nexus 4's and none of them seem to have any issues.
At this point my money is on the Clarion stereo being the issue but I still have not tested the phone with another stereo. This weekend we are visiting my parents. I will try using the phone with the bluetooth on my Mom's 2013 4Runner and my Dad's 2010 F150 to see if I can replicate the problem. If it works with both their cars then I will be in the market for a new stereo. :laugh:
Click to expand...
Click to collapse
At the same time have you checked the reverse? Any other phones that work fine with your stereo?
I have and I can say all other phones have worked fine with my Clarion stereo.
If N4 continues to have problems with the Clarion stereo, it could be easier for me to sell the N4 and get another phone, unfortunately a non-Nexus one
mailrachit said:
At the same time have you checked the reverse? Any other phones that work fine with your stereo?
I have and I can say all other phones have worked fine with my Clarion stereo.
If N4 continues to have problems with the Clarion stereo, it could be easier for me to sell the N4 and get another phone, unfortunately a non-Nexus one
Click to expand...
Click to collapse
sn0warmy said:
I'm in the same boat. But I really am wondering if looking at the software/apps used is the wrong method. I've been doing the same thing. Over the past 7 months I've tried various ROMs, kernels, radios etc. and nothing changes it. I've talked about it with various friends with Nexus 4's and none of them seem to have any issues.
At this point my money is on the Clarion stereo being the issue but I still have not tested the phone with another stereo. This weekend we are visiting my parents. I will try using the phone with the bluetooth on my Mom's 2013 4Runner and my Dad's 2010 F150 to see if I can replicate the problem. If it works with both their cars then I will be in the market for a new stereo. :laugh:
Click to expand...
Click to collapse
I was wrong btw. The problem came back for Play Music too :crying:
Don't know what to do...
Using all stock 4.3 and btooth working perfectly. Using it right now. I just have a $50 lg headset but have no issues.
Not sure what's up with your device man
Sent from my Nexus 4 using xda app-developers app
@sn0warmy
It seems the problem is with our Clarion car stereo indeed. A lot of Clarion stereos have bluetooth issues:
http://www.fixya.com/support/t12082313-bluetooth_audio_streaming_breaks_up
http://community.crutchfield.com/car_audio_and_video/f/27/receivers/t/22006/clarion-cx501-bluetooth
Phones like iPhone 4, Lumia 920 and Moto Razr also seem to have these problems.
My stereo CX501 doesn't have any bluetooth firmware upgrade too. Though, they have provided some firmware update for some other stereos like NX501 and so on. So you should check out on their site for a firmware upgrade.
http://www.clarion.com/us/en/support/compatibility/bluetooth/index.html
I really think you're right. I tried streaming music through my girlfriend's car stereo last night and had absolutely no issues. I've also read the threads you linked to as well as a few others and the consensus is that Clarion keeps trying to pin the blame on the phones and not their receivers. Looks like it's time to change stereos...
sn0warmy said:
I really think you're right. I tried streaming music through my girlfriend's car stereo last night and had absolutely no issues. I've also read the threads you linked to as well as a few others and the consensus is that Clarion keeps trying to pin the blame on the phones and not their receivers. Looks like it's time to change stereos...
Click to expand...
Click to collapse
You should at least check if there is a firmware upgrade available for you on Clarion's support site before spending on a new stereo.
Unfortunately, it's not available for my stereo CX501.
I have stuttering too on both my A2DP devices. Both are cheap: one is from DX, th eother is from a local 'dollar store' (where it was 10 euro or so).
The one from the dollar store seems to work fine after pairing, but not when connecting again.
The one from DX (z nice plug for the aux in of the car, with a mic and henadsfree speakers through the car audio) seems to stop stuttering after a few minutes. The audio level is a lot better with 4.3.
But no difference in stuttering beween 4.2.2 and 4.3.
Problems remain
I have found no improvement with my Nexus 7 with Android 4.3. I get stuttering every minute or so. I've done a bit of reading and found that Bluetooth is hellishly complex - and would be very difficult to debug. For instance to set up audio streaming, both devices need to agree on a codec to use. There is a default base level codec. As I have found that the issue is worse on some bluetooth receivers than others, I can only guess that the issue relates to Android's selection of a codec or other parameter on some devices. I certainly have no issue with any device streaming from my windows laptop (no matter how busy it is).
I have the exact same issues with bluetooth stuttering.
Using 4.2.2 PACman rom on my Note 2 with a Sony MW600 bluetooth adapter, the audio would switch off for a second every minute or so, whether using Google Play music or PowerAmp, but it seemed to happen less on the former.
Updating to 4.3 has made it worse, the audio now switches off for at least 5 seconds to the point where i have to check if the phone or app has crashed each time.
I never had an issue with the Revolution HD rom (I think its called?) but I believe that's mostly stock?
It kinda feels like the bluetooth can't handle the bandwidth depending on the size of the file. I think there's less stuttering on lower quality files - could just be in my head though.
I have a Galaxy S3 i747 running latest 4.3 CM10 rom. My audio stuttering actually got worse when upgrading from 4.2.2. Using platronics 903+ and a bluetooth stereo unit for my motorycle helmet.
Very disappointed. My work iPhone doesnt skip a beat.
Hi guys. So I've searched about everything I can and can not find a fix for this. At first, my Bluetooth headset wouldn't connect but I've recently fixed that. Now it seems that if I travel more than 2 feet from my phone, the music stops playing. Even if I hold my hand over my phone or put it in my pocket, the music stops and once I take it back out and hold it close to my phone, it works again. Is this a Pie thing or what? I've went to developer options and changed the AVRCP to 1.6 but it doesn't help that much. I love this phone but this is almost a deal breaker for me. Really thinking of returning it and getting a Pixel 2XL if there is no fix. Can anyone help? Thanks in advance!
Contact Essential support with this. They're aware of the issue but unsure if they can fix it. I don't know if this is new with Pie or not. I didn't get my Bluetooth headphones until late in the Pie beta.
gk1984 said:
Contact Essential support with this. They're aware of the issue but unsure if they can fix it. I don't know if this is new with Pie or not. I didn't get my Bluetooth headphones until late in the Pie beta.
Click to expand...
Click to collapse
Thanks. I emailed them. Hopefully this is something that can be patched up. How did your headphones do? Any issues? If not, what kind do you have?
Topdroid01 said:
Thanks. I emailed them. Hopefully this is something that can be patched up. How did your headphones do? Any issues? If not, what kind do you have?
Click to expand...
Click to collapse
I've been using Munitio NINES for like 5 years (they seriously are in awesome condition after all this time and sound amazing). But I've gotten frustrated a couple times not being able to charge while listening or forgetting the dongle at home. So I grabbed Marshall Major II's in June. These are my bluetooth headphones. They don't sound nearly as good as the Munitio's, but wireless is convenient.
So my experience? I was on Android Pie beta when I got them. Day 1 with the bluetooth headphones and on, if the phone is in my hand at waist level or higher, they work fine. Put it in my pocket or step away, it's like it's buffering constantly. Oddly, at home (suburb), the "buffering" is almost non-existent (key work "almost"). But I haven't tried stepping away from my phone with BT on. In the city where I work, it's almost unusable unless I hold my phone. I think it's interference with so much wifi since BT and most WiFi broadcast over 2.4 Ghz.
I changed my default Bluetooth version in the developer options and it seems that pairing goes quicker as well as device pickup. Have you messed with that?
Koncrete said:
I changed my default Bluetooth version in the developer options and it seems that pairing goes quicker as well as device pickup. Have you messed with that?
Click to expand...
Click to collapse
Yeah. I changed it to 1.6, 1.5, 1.4, default, etc... With no luck. You said you have yours set on default? Is it working perfectly? It's not that mine won't connect, it the range. I just do get it. The more I research it, the more I think it's a Pie issue. I've got on some pixel forums and they have the same issue. I'm in touch with the essential support team so maybe they'll tell me they'll have a update out soon to fix this.
Ever since pie my phone's Bluetooth has stuttered in my car, also have issues connecting sometimes. Plus noticed issues with WiFi as well. It didn't do it until pie.
Bluetooth AVRCP Version = 1.6
Bluetooth Audio Codec = Qualcomm Aptx (not the hd one)
Bluetooth Audio Sample Rate = 48k
Bluetooth Bits per Sample = 32/sample
Bluetooth Audio Channel = Stereo
Bluetooth Audio LDAC = Balanced 660/606
Those are the settings I'm using and I never have any issues except my car stereo takes longer then I like to initialize...
Factory reset always does the trick! This phone is weird like that especially after a major update.
I'm wondering if anyone has issues with and solutions for bluetooth connectivity problems. Specifically, constant dropouts and stuttering.
Background of problem
I recently purchased my phone, which was already on Android 10 (Build QP1A.190711.122). From the start, bluetooth has been unbearable: if I move the phone in any way, or I move the connected bluetooth device (headphones, earbuds, speakers, etc.) it stutters and cuts out momentarily. Sometimes the stuttering continues incessantly. In short, my bluetooth is useless for listening to audio, making phone calls, etc. I basically have to be next to be perfectly still and right next to the phone, and even then it may act up.
Failed troubleshooting efforts
I installed the September update, rooted the phone and tried various options many times, including:
*Hard resetting the phone
*Flashing and re-flashing the stock rom several times (even after full wipes)
*Wiping the cache in recovery
*Clearing the bluetooth cache
*Playing with the bluetooth options in Developer Options
*Unpairing and re-pairing various bluetooth devices
I'm lost and wondering if the gyroscope is messing with bluetooth connectivity in someway. I have no idea whatsoever.
Thoughts and comments appreciated.
@droctii
I have not had an issue like this, sounds like a low power/weak signal issue or interference or conflicting devices
Which sounds like this
https://forum.xda-developers.com/essential-phone/help/awful-bluetooth-connection-t3713280
users report 2 or 3 fixes scanning through thread
Same here. bluetooth connectivity has rather worsened since android 10.
however the recent ota updates on android 9 have been a hit or miss since march 2019. Before that, bt was working perfectly fine.
Coming back to android 10, as an example, the link with my bose soundwear with minor exceptions had been really strong bt -wise but since the update I get even with it random disconnects, and infrequent stutter/cuts etc. The same for my sony wh1000x m3, it behaves a little better but only using sbc codec, so i stick to that. However, older devices such as my car's bt, tv soundbar or even google mini when phone's just next to it are unusable with this phone. Also, the more crowded an environment (interference-wise) more likely to experiment issues.
For comparison, all other older phones I have still work fine within same parameters
I haven't taken my PH-1 to A10 yet, but my pixel 3XL had been struggling with Bluetooth. Today is the first time it's been useable, but I made a bunch of random changes in developer options. I haven't worked out which had helped. FWIW, I'm attaching a screen shot of the settings I'm using.
ktmom said:
I haven't taken my PH-1 to A10 yet, but my pixel 3XL had been struggling with Bluetooth. Today is the first time it's been useable, but I made a bunch of random changes in developer options. I haven't worked out which had helped. FWIW, I'm attaching a screen shot of the settings I'm using.
Click to expand...
Click to collapse
A lot of Bluetooth devices don't implement the protocols properly, especially on the cheaper side. You disabled A2DP so that probably helped.
You should be able to enable A2DP but use the highest version of AVRCP available, yours seems rather low. Should work fine.
Verlog5454 said:
A lot of Bluetooth devices don't implement the protocols properly, especially on the cheaper side. You disabled A2DP so that probably helped.
You should be able to enable A2DP but use the highest version of AVRCP available, yours seems rather low. Should work fine.
Click to expand...
Click to collapse
What makes you think A2DP is disabled? The hardware handoff is disabled. Not the same thing. And that is the solution to my stuttering and disconnect issues. Toggling that makes the problems come and go.
Same problem on my car with 1+7pro and android10, music is discontinued, or freezed, stuttered...
But for me line with disable bt ad2p hardware offload is greyed and swith is to left
salva52 said:
Same problem on my car with 1+7pro and android10, music is discontinued, or freezed, stuttered...
But for me line with disable bt ad2p hardware offload is greyed and swith is to left
Click to expand...
Click to collapse
You would be better served looking/posting in your own device forum. This is the Essential PH-1 and your software is very different.
I have had such problems with various devices and while disabling A2DP offload always solved the problem, so did playing around with the AVRCP versions.
My essential phone has been sitting on my desk for the last 3 months due to these insolvable bluetooth issues. Neither AVRCP nor A2DP solved the issues, the bluetooth is stuttering constantly when I move my phone around and not in direct sight of my receiver(s).
I tried 3 different wireless earbuds and they all suffer from random stutters or disconnects if I'm actively walking with my phone. The closer the phone is to my upper body, the better the signal is (most of the time). If I connect my phone to any Bluetooth device at home or in the car where the phone isn't moving, the connection is perfect. I've tried the different methods mentioned in this thread and nothing fixes it. I've given up and just hoping my next phone doesn't suffer from the same thing.