Database Develop

Getting Bluetooth Headset microphone working?

Any chance of one of the Devs having time to look into why the microphone input is not recognised or enabled on bt headsets in CM7?
Great progress has been made getting BT enabled, but I'd love to be able to Skype or record audio via BT...

Ill put a +1 on interest in this; but i know realistically, there are more critical things being fixed right now, so i am ok waiting..

I'm sure down the road, more devices will work, but I'm interested in the range issue. Is it a hardware issue (antenna) or is it a software?

sark666 said:
I'm sure down the road, more devices will work, but I'm interested in the range issue. Is it a hardware issue (antenna) or is it a software?
Click to expand...
Click to collapse
software. the wifi shares the antenna with the BT.

I'm sure it's just a matter of time before the bluetooth is able to handle a microphone. That's what I'm waiting for. I am loving the latest CM7 stable 4-11-11.
That's the only thing my nook is missing.... mic. I've been through all the ROMS and nothing beats the CM7 ...IMO. I will be more than happy to test any kernels for bluetooth stacks that the developers may come up with. I'm not familiar with what all they have to overcome to make it work but I am rooting for them. All the hard work that has already gone into this is AMAZING!!!!!!!
"We need more Cowbell"

Unresolved Bluetooth issues since 4.2

The issue of Bluetooth devices not connecting and speakers dropping out was a hot topic when the 4.2 OTA came out, and to the best of my knowledge, the 4.2.1 update did nothing to fix it. Since then, I've read dozens for reported "Bluetooth fixes" for various Nexus devices (and I've tried most of them), but this is still a major unresolved issue for a lot of people. My gamepad and mouse refuse to hold a connection since the update, so after banging my head against the wall for a few weeks I reverted to 4.1.2.
Has anyone found an actual fix for the Nexus 7, or have there been any reports of when Google might respond (I've read several reports that Google tech support claims to not even be aware that a problem exists)?
For the record, I've tried the following:
- Fix permissions
- Disable all devices, clear Bluetooth Share cache... reconnect devices
- Perform a full wipe and install the 4.2.1 OTA.
- Install custom ROMs or kernals
- Disable wifi when establishing the initial device conection.
- Sacrificed a young goat at midnight on the winter solstice.

ED2O9 said:
- Sacrificed a young goat at midnight on the winter solstice.
Click to expand...
Click to collapse
Did you check and make sure it was a virginal young goat before you sacrificed it? :angel:
Sent from my Nexus 7 using Xparent Purple Tapatalk 2

I also had big bluetooth issues in stock 4.2.1. I have since changed quite a few things on my nexus7. Somewhere along the way, something I did seems to have fixed the issue. I didn't do any tests along the way, so I can't tell with any certainty which changes had any affect. All I can say is stock 4.2.1 bluetooth was completely and utterly broken, and what I have now doesnt have any bluetooth issues that I've noticed. I am able to stream music over Pandora (WiFi) and listen to it over bluetooth now without any interruptions.
So, here's a brief description:
CM10.1 nightlies + gapps, using the default kernel, no over/underclocking or anything like that.
wifi is always turned on, gps is always on, nfc is always turned off
About half of the gapps and a few of the default apps I have disabled. I have no proof to back it up, but I believe constant syncing and phoning home from these apps may have something to do with the issue. Calender, Exchange Services, Face Unlock, Calender Sync, One Time Init, Partner Setup, Play Movies & TV, and Play music are all the apps I disabled.
I also purposefully avoid other apps that run constantly chewing up battery and sending data to the internet like the facebook app.

Nope, nothing fixed it for me, aside from downgrading to 4.1 (which uses the Bluez bluetooth stack, rather than the Broadcom one in 4,2)
It's possible that CyanogenMod 4,2 (CM10.1) uses Bluez, and not Broadcom. I asked in the dev section, but nobody knows it seems.

bsoplinger said:
Did you check and make sure it was a virginal young goat before you sacrificed it? :angel:
Sent from my Nexus 7 using Xparent Purple Tapatalk 2
Click to expand...
Click to collapse
The goat said she was a virgin, but you never know.
I'd be very interested to see exactly how widespread this issue is. Are the people reporting issues the small minority, or are they just the only ones attempting to use a bluetooth device? If you're reading this and are running 4.2.1, but have never connected a Bluetooth device, please try to do so in the near future and post your results. Based on the number of forums claiming that Bluetooth is flat-out" broken, I'm thinking that most people don't even realize that it's a problem.

ED2O9 said:
The goat said she was a virgin, but you never know.
I'd be very interested to see exactly how widespread this issue is. Are the people reporting issues the small minority, or are they just the only ones attempting to use a bluetooth device? If you're reading this and are running 4.2.1, but have never connected a Bluetooth device, please try to do so in the near future and post your results. Based on the number of forums claiming that Bluetooth is flat-out" broken, I'm thinking that most people don't even realize that it's a problem.
Click to expand...
Click to collapse
I have had success with an old Dell XPS bluetooth mouse. Scrolling was fast and paired immediately.
No luck with Plantronics M100 headset. Nexus 7 could see it but no joy...
Maybe we need a list of what really works after 4.2.1?

More bluetooth
ED2O9 said:
The goat said she was a virgin, but you never know.
I'd be very interested to see exactly how widespread this issue is. Are the people reporting issues the small minority, or are they just the only ones attempting to use a bluetooth device? If you're reading this and are running 4.2.1, but have never connected a Bluetooth device, please try to do so in the near future and post your results. Based on the number of forums claiming that Bluetooth is flat-out" broken, I'm thinking that most people don't even realize that it's a problem.
Click to expand...
Click to collapse
Got my N7 2 weeks ago. Never had a chance to run on anything but 4.2.1 since first thing it updated. My bluetooth is not usable. If trying to stream video the audio is so bad that you cannot decipher anything. With music it is better but will start stuttering and becomes unusable. Same devices work fine with my Verizon Galaxy Nexus running 4.1.1.

ED2O9 said:
The goat said she was a virgin, but you never know.
I'd be very interested to see exactly how widespread this issue is. Are the people reporting issues the small minority, or are they just the only ones attempting to use a bluetooth device? If you're reading this and are running 4.2.1, but have never connected a Bluetooth device, please try to do so in the near future and post your results. Based on the number of forums claiming that Bluetooth is flat-out" broken, I'm thinking that most people don't even realize that it's a problem.
Click to expand...
Click to collapse
I for one was completely unaware of the 4.2 bluetooth problem until I got a pair of bluetooth stereo earbuds from Audiosynq for Christmas. I got them paired and working, but the audio kept dropping out, only to come back a few seconds later. Very annoying when you are trying to listen to music But the earbuds worked flawlessly when I used them with my Samsung Galaxy Player running Gingerbread. That was my first clue that something was amiss....

Same stuttering for me with my jambox. Clearing blue share data helps it and seems to keep the problem away for a while.
Sent from my Nexus 7 using Tapatalk HD

The issue is widespread enough to have 400+ comments on the bug tracker.
http://code.google.com/p/android/is...ed&colspec=ID Type Status Owner Summary Stars

I've been using Paranoid Android with my Bluetooth controllers and my new Motorola stereo headset.
Honestly I expected problems with the audio and have not. In fact I'm very impressed by the range. I can pretty much walk anywhere in my house without the music skipping. Of course this is streaming Pandora... so the bitrate may be lowered for streaming but whatever. Still impressed.
I'm not saying Bluetooth doesn't have its problems with 4.2 but perhaps a wipe will fix it. They did change Bluetooth protocols and there could be some remnants leftover screwing with us.
My moga controller had lag but I found that problem being caused by the Moga Pivot app. Using the universal driver fixed it right up.
Sent from my Nexus 7 using XDA Premium HD app

I had the same problems with stuttering Bluetooth over audio, then I thought it was fixed with the latest update - but I was wrong.
In my case at work I have a very weak WiFi signal, and it drops in and out and that's when my Bluetooth over Audio plays up. If I disable WiFi it's better a lot better but still not 100%. I get better results in the same environment with my Desire HD running ICS than the Nexus, which is quite disappointing

gianptune said:
The issue is widespread enough to have 400+ comments on the bug tracker.
http://code.google.com/p/android/is...ed&colspec=ID Type Status Owner Summary Stars
Click to expand...
Click to collapse
People should click the star and leave it at that, rather than whinging, complaining, and making **** up. But yeah, 620+ stars on that bug.

4.1.2 works, had to go to that

Marshmellow Bluetooth Phone Issues?

As soon as I updated to Marshmellow I instantly starting having issues with my audio quality via bluetooth car. On 5.1.1 voice quality was fine, but now it sounds almost like it's out of phase and skipping badly. Is this a known issue, if so, is there a fix?
Thanks!

I use BT in my truck every day. I haven't had any skips that are consistent. Every once in a while, I might hear the audio drop for a split second, but I don't find that it's worse than it was before. I use mine for music and voice calls. I never have any trouble with voice calls. I've always had those little random split second drops with any phone I've had, so I figure it's my stereo.

This sounds more like someone put the whole car underwater and is trying to speak with their mouth full of water as well. I had no problems before when I was on 5.1.1. I've tried a customer 6.0 rom and it has the same problem. I'll try going back to a 5.1.1 rom and see if still does it.

sirianthe3rd said:
This sounds more like someone put the whole car underwater and is trying to speak with their mouth full of water as well. I had no problems before when I was on 5.1.1. I've tried a customer 6.0 rom and it has the same problem. I'll try going back to a 5.1.1 rom and see if still does it.
Click to expand...
Click to collapse
The Bluetooth bug is a known bug in MM, Google it and you'll find out.

DrakenFX said:
The Bluetooth bug is a known bug in MM, Google it and you'll find out.
Click to expand...
Click to collapse
I saw issues where there were bluetooth connection issues where there would be no audio, but not specifically my problem. Do you have any documentation so I know what to look for in the future?
Audio streaming from something like Spotify is not affected, just when the car is used as a headset.

sirianthe3rd said:
I saw issues where there were bluetooth connection issues where there would be no audio, but not specifically my problem. Do you have any documentation so I know what to look for in the future?
Audio streaming from something like Spotify is not affected, just when the car is used as a headset.
Click to expand...
Click to collapse
i don't remember the Doc. about the issue, i remember reading about it few months ago and yeah was about Car Bluetooth connection but not every car by the way.

DrakenFX said:
i don't remember the Doc. about the issue, i remember reading about it few months ago and yeah was about Car Bluetooth connection but not every car by the way.
Click to expand...
Click to collapse
Thanks for trying. I went back to Lollipop and the issue is gone. Definitely a bug in Marshmallow.

My experience was opposite. Bluetooth sound quality was horrible on 5.1. After updating to 6.0 all problem went away. I was extremely happy with their fix.

All Mate 10 Pro have Crippled Bluetooth

I have noticed this is a widespread issue and I've decided to raise it. This needs to be fixed and Huawei should stop ignoring this problem. The Bluetooth is basically crippled and locked to SBC. I've tested multiple devices and all exhibited this behaviour. Why is it ignored? Are all the reviews fake?
https://www.youtube.com/watch?v=x-sifkojUqw

i read that Bluetooth options in pixel dont stick too. so it must be some wierd oreo crap. you cant even change gpu renderer. it always defaults back. best way to handle that is to chat with huawei support and check it out.

I don't use Bluetooth very much but it appears to be the same for the regular Mate 10 as well. I'm currently using my virtual desktop so I could not test if after changing the setting in developer mode does it stick after a reboot?

this confusion is due to a lack of follow-through. all oreo devices have this "issue". it's not an issue at all. if a connected bluetooth device supports these codecs, the best one will automatically be selected. it is not limited to huawei devices. this is normal and does not affect functionality. you should take down this thread so no one throws any fits for no reason.

Well mine switches to aptX automatically when I connect to aptX-compatible devices. However you are correct that I cannot manually change it in developer settings.

Further testing has shown this issue not to be an issue, I've managed to successfully connect to an APTX device and the codec was selected. Video removed. Apologies for this confusion.

perrin21 said:
Further testing has shown this issue not to be an issue, I've managed to successfully connect to an APTX device and the codec was selected. Video removed. Apologies for this confusion.
Click to expand...
Click to collapse
Doesn't matter, it will still randomly switch to loudspeaker and the quality will still be terrible.

tr1cky1 said:
Doesn't matter, it will still randomly switch to loudspeaker and the quality will still be terrible.
Click to expand...
Click to collapse
I don't have any issues regarding Bluetooth for now, haven't really tested aptx I think, but it worked fine otherwise. And never switched to loudspeaker or so
Sent from my HUAWEI BLA-L29 using XDA Labs

perrin21 said:
I have noticed this is a widespread issue and I've decided to raise it. This needs to be fixed and Huawei should stop ignoring this problem. The Bluetooth is basically crippled and locked to SBC. I've tested multiple devices and all exhibited this behaviour. Why is it ignored? Are all the reviews fake?
https://www.youtube.com/watch?v=x-sifkojUqw
Click to expand...
Click to collapse
It's not crippled, it's buggy.
SBC and aptX have high noise floor and specially on SBC, it causes some deformations to the Audio.
AAC is totally broken.

DeeZZ_NuuZZ said:
I don't have any issues regarding Bluetooth for now, haven't really tested aptx I think, but it worked fine otherwise. And never switched to loudspeaker or so
Sent from my HUAWEI BLA-L29 using XDA Labs
Click to expand...
Click to collapse
Good for you, people here all have Bluetooth problems:
https://www.android-hilfe.de/forum/...oth-problem.853624-page-19.html#post-10970173

I have no issues with my Bluetooth headphones, the Sony WH-1000NX2
The highest quality of transmission is selected automatically, LDAC, that's 990 kbit/s
It's the best Bluetooth can do in the Audio section.
The Sony headphone App confirms the LDAC connection

i am trying my friend's MDR 1000x. i tried both SBC and LDAC. Now I can't go back to LDAC. Help please

Aac not working on p20 pro, works fine on the pixel 2

Bull****.
AAC No longer works on my head unit and my Bose QC35 Headphones.
It worked perfectly before 8.0.0.128 update.
Factory Reset does not work, nothing works. It refuses to use anything else than ****ty SBC.

tr1cky1 said:
Good for you, people here all have Bluetooth problems:
https://www.android-hilfe.de/forum/...oth-problem.853624-page-19.html#post-10970173
Click to expand...
Click to collapse
they are reporting issues with many devices on that forum. android has always had some issues with bluetooth. huawei is no exception. my samsung and sony devices were the best by far. i think it's because of improvements that they make to the android system.

Anyone on b142? Can you comment on if the Bluetooth audio quality is better?

Can anyone confirm if b142 solved sbc problem? I think aac is stilo broken, but sbc quality?

Kekkolekko94 said:
Can anyone confirm if b142 solved sbc problem? I think aac is stilo broken, but sbc quality?
Click to expand...
Click to collapse
Solved.

I don't have a clue what you guys talking about with all those 3 and 4 letter/digit combinations of names but i feel I've gotta share i use Bluetooth all day long for different kinds of profiles and i mean all day long, and to say this doesn't fail nearly as much as nougat did would mean i imply it does fail to a certain, however small, degree, which isn't even close to being the case, so... But i do notice the in band ringing settings don't stick just like they don't stick in my Oreo S5...

I've had Android phones since 2012 and the Huawei mate 10 pro is the only one with Bluetooth issues. Constantly dropping parts of songs when connected to my mazda 6. Infuriating to say the least. The most expensive phone I've ever had....

Can CC audio be played to a different device?

I am trying to get the audio from my CC with GTV to play to another source. My preference would be to cast the audio from CCGTV to another Google speaker because that would be the most elegant solution. But I do not think this is possible. I know you can include the Chromecast in a speaker group but as far as I can tell that is only so the same audio can play from your speakers and your TV simultaneously.
The other option that could work is to pair an external speaker with CCGTV via bluetooth. But according to this thread this is not a great solution because you have to forget and then re-pair the speaker every time. The thread has nearly 150 upvotes but Google closed it a month ago. There was no solution to this issue at the time but I wonder if the recent firmware update made bluetooth connections more stable?
Shortly after posting this I discovered that you can access the Play store directly on the Chromecast. I wonder if there is an app I could install that would let me cast audio from the CC to a Google speaker?

uscpsycho said:
I am trying to get the audio from my CC with GTV to play to another source. My preference would be to cast the audio from CCGTV to another Google speaker because that would be the most elegant solution. But I do not think this is possible. I know you can include the Chromecast in a speaker group but as far as I can tell that is only so the same audio can play from your speakers and your TV simultaneously.
The other option that could work is to pair an external speaker with CCGTV via bluetooth. But according to this thread this is not a great solution because you have to forget and then re-pair the speaker every time. The thread has nearly 150 upvotes but Google closed it a month ago. There was no solution to this issue at the time but I wonder if the recent firmware update made bluetooth connections more stable?
Shortly after posting this I discovered that you can access the Play store directly on the Chromecast. I wonder if there is an app I could install that would let me cast audio from the CC to a Google speaker?
Click to expand...
Click to collapse
I am not experiencing any issues with using my UE Megaboom as an external BT speaker on our CCwGTV. No need to forget and re-pair it every time, I just switch on CC, switch on speaker and they connect automatically.

jbmc83 said:
I am not experiencing any issues with using my UE Megaboom as an external BT speaker on our CCwGTV. No need to forget and re-pair it every time, I just switch on CC, switch on speaker and they connect automatically.
Click to expand...
Click to collapse
How long have you been using the bluetooth speaker this way? Have you tried any other BT speakers prior to the Megaboom?

uscpsycho said:
How long have you been using the bluetooth speaker this way? Have you tried any other BT speakers prior to the Megaboom?
Click to expand...
Click to collapse
Hmm, let's see...I think we started using it regularly around maybe end of Jan/beg of Feb? Might be related to the latest system update that was rolled out in Feb, but not sure on that.
Haven't tried other speakers yet, since this is our go-to big boy for sound. If you want I can try my BT headphones and our smaller Xiaomi BT speaker to check and see on their functionality with Sabrina.

jbmc83 said:
Hmm, let's see...I think we started using it regularly around maybe end of Jan/beg of Feb? Might be related to the latest system update that was rolled out in Feb, but not sure on that.
Haven't tried other speakers yet, since this is our go-to big boy for sound. If you want I can try my BT headphones and our smaller Xiaomi BT speaker to check and see on their functionality with Sabrina.
Click to expand...
Click to collapse
Yes, please. I would really appreciate that. If possible, leave the bt device powered on and turn the cc off for several hours before turning the cc back on. This is my use case, the bt speaker will always be on and I need cc to connect to it right away when it is turned on.
Thanks in advance!

jbmc83 said:
Hmm, let's see...I think we started using it regularly around maybe end of Jan/beg of Feb? Might be related to the latest system update that was rolled out in Feb, but not sure on that.
Haven't tried other speakers yet, since this is our go-to big boy for sound. If you want I can try my BT headphones and our smaller Xiaomi BT speaker to check and see on their functionality with Sabrina.
Click to expand...
Click to collapse
Any update on this?
I'm really surprised that you aren't having to re-pair your speaker every time. I discovered two more threads on reddit where people complain about this happening to them to. I have a feeling you are the exception rather than the norm:
https://www.reddit.com/r/Chromecast/comments/lmfya1
https://www.reddit.com/r/Chromecast/comments/lbd3yn
(point #1)

uscpsycho said:
Any update on this?
I'm really surprised that you aren't having to re-pair your speaker every time. I discovered two more threads on reddit where people complain about this happening to them to. I have a feeling you are the exception rather than the norm:
https://www.reddit.com/r/Chromecast/comments/lmfya1
https://www.reddit.com/r/Chromecast/comments/lbd3yn
(point #1)
Click to expand...
Click to collapse
Haven't forgotten about this yet, gonna have a look this weekend with the different speaker / headphone.
Last night I was watching a show with my lady via the CC and I switched on our UE Megaboom to connect. I forgot to switch off my phone's BT (had them paired before for workout), so they connected automatically.
I then switched off my phone's BT and also restarted the speaker, it automatically paired with the CC without us having to go into settings.
btw @"norm" vs. "exception": hope you are aware that you would most likely only find threads of people who have troubles with this others without issues are less likely to post and are thus far less visible.
edit: by the way, i noticed one big difference between your experience and the two threads you posted vs. my case: we are using the CC with a computer monitor without in-built speakers. so could be that CC somehow detects those inbuilt speakers and resets to a default that routes audio automatically to the inbuilt system.

jbmc83 said:
Haven't forgotten about this yet, gonna have a look this weekend with the different speaker / headphone.
Last night I was watching a show with my lady via the CC and I switched on our UE Megaboom to connect. I forgot to switch off my phone's BT (had them paired before for workout), so they connected automatically.
I then switched off my phone's BT and also restarted the speaker, it automatically paired with the CC without us having to go into settings.
btw @"norm" vs. "exception": hope you are aware that you would most likely only find threads of people who have troubles with this others without issues are less likely to post and are thus far less visible.
edit: by the way, i noticed one big difference between your experience and the two threads you posted vs. my case: we are using the CC with a computer monitor without in-built speakers. so could be that CC somehow detects those inbuilt speakers and resets to a default that routes audio automatically to the inbuilt system.
Click to expand...
Click to collapse
Thanks for the update. I don't know why sometimes I have brain damage and didn't think about how easily I could have tested all of this out myself with a pair of BT headphones.
Anyway, if you are an "exception" than I am too because I tested with my headphones and they paired up every time without any problem. So then I used the bluetooth dongle that I want to use with my AV system and it works fine too. I have turned the CC off and on multiple times and it connects every time, plus I have zero audio delay like many others reported.
Solution achieved.

hmmm....so then what was different with your speaker?