Related
So, I have searched all over these forums, and cannot find a difinitive answer or solution. I have problems with A2DP when connecting w/ the BT in my car, since installing a 2.1 ROM (currently DC 2.09.01). When connected, the music plays about twice as fast as it should, then slows down, then speeds up again. Conversley, Android 1.5 worked fine. There has been a lot of talk of BT issues, but it doesn't appear there are any solutions. Am I correct, or has someone found a solution? THanks.
ZenEXP works if you dont mind switching.
I have had those problems occasionally with all 2.1 ROMs I have tried. Usually, if I pause and then unpause it solves the problem. Sometimes I have to do it more than once.
I'm currently running ZenEXP and I've had the problem a few times, but it has been significantly less than with other ROMs. However, AVRCP hasn't been working with ZenEXP, whereas it has worked on other 2.1 ROMs, such as DC.
So, with the unrooted stock Sprint 2.1 software, A2DP works?
The Darchdroid ROM actually fixes this problem! I had the exact same problem as you with playing audio in my 2010 Mazda 3 and Darchstar's ROM fixed it for me, it's the only ROM I have found so far that fixes the bluetooth
I have a problem with my bluetooth headset when I'm playing music, the music stutters alot, I almost have to hold my phone a certain way with very little movement in order for it to play decently. Any solutions on that problem?
I have a problem with my bluetooth headset when I'm playing music, the music stutters alot, I almost have to hold my phone a certain way with very little movement in order for it to play decently. Any solutions on that problem?
Click to expand...
Click to collapse
Turn off/disconnect headset while playing music fixes studdering for me in settings under bluetooth for the connected device. Disconnect the ' phone' while playing. Haven't really tested this on anything but my kenwood head unit.
-------------------------------------
Sent via the XDA Tapatalk App
here's a reply I received from HTC support:
Hello, I understand that you have had issues with your bluetooth since the update for your Hero. With the update, the entire bluetooth stack was updated, and thus some bluetooth devices that previously worked are unfortunately no longer compatible. While we have not heard any information about nor made announcements about any upcoming patches to address this, it is not at all out of the realm of possibility. Otherwise, you may want to try a different bluetooth headset. I do apologize for any inconvenience you may have experienced. If you have any other questions, feel free to contact us again. You can find additional support at support forums at community.htc.com. There is also a customer satisfaction survey for you to take if you are interested. Philip HTC Technical Support www.htc.com www.twitter.com/htc
Bluetooth Stack?
So is it possible for one of the developers on this site to rewrite the bluetooth stack or copy the old one from 1.5 that worked?
I have a Panasonic TH12 bluetooth home phone that worked fine before 2.1. I recently bought an AT&T bluetooth phone and it does the same thing. Will pair but not connect.
aschlect said:
Hello, I understand that you have had issues with your bluetooth since the update for your Hero. With the update, the entire bluetooth stack was updated, and thus some bluetooth devices that previously worked are unfortunately no longer compatible. While we have not heard any information about nor made announcements about any upcoming patches to address this, it is not at all out of the realm of possibility. Otherwise, you may want to try a different bluetooth headset. I do apologize for any inconvenience you may have experienced. If you have any other questions, feel free to contact us again. You can find additional support at support forums at community.htc.com. There is also a customer satisfaction survey for you to take if you are interested. Philip HTC Technical Support www.htc.com www.twitter.com/htc
Click to expand...
Click to collapse
I have to call BS on this. (Not on the post, on the reply)
Why would any company not support legacy hardware as simple as Bluetooth. Especially since most devices aren't even Bluetooth v3/v4 standard yet. And Bluetooth 2.1 is 1. Not very old and 2. What 90% of Bluetooth device still manufactured are! and its been around since 2006!
I honestly can't believe a company is going to just say "Oh its to old" instead of fixing their crap. as far as I know v3/v4 is fully backwards compatible to 2.1 because they include "Classic Bluetooth" protocols!
Not to mention I doubt the hardware in our phone is even capable of v4 stuff. I'll have to do some more research on what BT chip is in the phone. Utter BS.
Either Phillip or HTC is a moron.
CDMA Hero Specs for BT:
Supported Profiles: HSP 1.1, HFP 1.5, A2DP, AVRC, (OPP, PBA)
version 2.0+EDR / possibly upgradeable to 2.1+EDR, plus OPP and PBA profiles
2.1 FULLY backwards compatible to v1. Meaning HTC built the crappiest BT Stack allowable by law to say it includes it. May as well have not bothered.
Someone could probably redo things with AOSP and a newer bluez stack.
Kcarpenter said:
<snip>
2.1 FULLY backwards compatible to v1. Meaning HTC built the crappiest BT Stack allowable by law to say it includes it. May as well have not bothered.
Someone could probably redo things with AOSP and a newer bluez stack.
Click to expand...
Click to collapse
Yeah, I just bought a BT USB adapter so I could exchange files and synch and stuff. I got it to work ONE time and all it did was pass 200 of my contacts to my phone from my PC. Like it was just waiting to upchuck on me. After that, nothing.
There's three hours of my life and $8.99 I'll never get back.
Bluetooth is pretty much the #1 complaint that users have been posting on the Sprint Community Forums (here's the HTC Hero section). Nearly all of those complaints say that Bluetooth now doesn't work at all or just plain sucks on the stock 2.1 Sprint/HTC release. Which probably also means that any ROM here based on 2.1 stock will also suck it up bad with Bluetooth compatibility. Known problem, no one has done anything about it yet. It sounds like AOSP ROMs don't have this issue, so at least that's good.
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.
There are threads that discuss the problem with different releases of android releases that are missing bluetooth capability over 2 years ago, nothing since Dec. 2011.
That said I have had a Motorola Photon running 3.2.2 gingerbread that would sync with my ford MySync for audio and display and read SMS txt messages.
So getting a brand spankn new Nexus 4 with Jelly Bean, I was very disappointed to see that all I can sync via bluetooth is the phone and directory.. so old hat now days, they all do that.
It seems that this should be a big enough problem that it would have been fixed long ago, but I can notspelling understand why going from an older version that works, is broken or missing in a much later version.. :crying:
Does anyone know what is going on?
Same here, I would have thought the Nexus 4 would have sent the metadata for the music that I was streaming via bluetooth to my car as well. But nope, just the music no artist info, name and or the ability to browse my playlist.
I use poweramp and poweramp supports this feature as well. Guess we have to wait for custom roms to support this.
same here but at least the disconnection issue has been fixed
xdviper said:
Same here, I would have thought the Nexus 4 would have sent the metadata for the music that I was streaming via bluetooth to my car as well. But nope, just the music no artist info, name and or the ability to browse my playlist.
I use poweramp and poweramp supports this feature as well. Guess we have to wait for custom roms to support this.
Click to expand...
Click to collapse
Oh and I did forget a Charge only setting. When I connect it by USB to the car, I have to set it to picture mode only as the music player setting is not recognized.. never had that problem with gingerbread,
eastrader said:
Oh and I did forget a Charge only setting. When I connect it by USB to the car, I have to set it to picture mode only as the music player setting is not recognized.. never had that problem with gingerbread,
Click to expand...
Click to collapse
what do you mean charge only setting? how do you get that?
eastrader said:
There are threads that discuss the problem with different releases of android releases that are missing bluetooth capability over 2 years ago, nothing since Dec. 2011.
That said I have had a Motorola Photon running 3.2.2 gingerbread that would sync with my ford MySync for audio and display and read SMS txt messages.
So getting a brand spankn new Nexus 4 with Jelly Bean, I was very disappointed to see that all I can sync via bluetooth is the phone and directory.. so old hat now days, they all do that.
It seems that this should be a big enough problem that it would have been fixed long ago, but I can no understand why going from an older version that works, is broken or missing in a much later version.. :crying:
Does anyone know what is going on?
Click to expand...
Click to collapse
I get the same thing, but since BT 4.0 is relatively new, there is an update for my car to support this bt version. Im waiting to change the oil to ask my dealer to update my BT software.
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.
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.