Related
I just assumed that I could use any bluetooth microphone for voip, voice recording etc. I currently do not have any bluetooth device but I tried 3 at a friends and they all paired for sound, but failed to work in using a voice recording app or a voip app. In a voip app the sound went strange (long sounds on the dial tone buttons) and then the sound resumed coming out of the tablet even though the headset device was showing as connected. Only a reboot solved this.
So I assume the bluetooth stack doesn't support recording, but why not? Isn't this a basic thing at this point? If I connect a bluetooth headset with mic that should be my input and output on sound for the time it is connected.
Or has anyone had success with a certain bluetooth model for recording?
No one can provide info on this? Is this the norm for tablets? I would assume even some ancient gingerbread phone would work with bluetooth headset/mic.
Does cyanogen team ever modify the kernel to include more functionality such as this?
I'd check other bluetooth threads around this section, but I've heard several people who've used bluetooth headsets with Nexus tablets. It may be a setting issue (particularly the device setting under bluetooth and the app settings concerning headsets).
-Ara
My Motorola HS850 works perfectly with the N7.
Sent from my Nexus 7 using Tapatalk 2
ExploreMN said:
My Motorola HS850 works perfectly with the N7.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Same here, Plantronics bluetooth headset works perfectly for voip calls using Talkatone.
Thanks for the info. I don't have the model names off-hand but I'll ask my friend what they were. I wasn't aware that once a bluetooth device was paried that there were any additional options. I was under the impression that it was simply pair and use. With the case of a headset/mic I assumed it was inherited as your sound output/input for all apps while paired. The voip I tried is csipsimple and a voice recording app. I'm glad to at least some models work but I hope it isn't hit and miss and you have to be selective of what bluetooth device you use but rather something I was doing.
I didn't expect there to be any settings as well because even with no bluetooth recording device paired, I don't see anywhere in the settings recording recording (like mic volume).
Can't get mine to work. Single ear set I don't even get sound. Just dead air all around. The Southwing SA505 stereo gets sound fine but no mic function and on Groove ip no sound or mic on single ear or stereo. I even checked the settings making sure bluetooth was selected.
I'm from Canada so I can't try talkatone as I can't get google voice. I now purchased a btheadset. It pairs fine and I hear audio in all apps but I haven't found one app yet that works with the bluetooth mic. I wanted a voip sip app. I've pretty much tried all the free ones and other users have posted comments of bluetooth issues as well. There are a couple of paid sip apps that claim to support bluetooth, but I don't want to buy them to only find they don't.
So yes, android supports bluetooth mics, my thread title is inaccurate, but it seems the vast majority of recording apps do not have proper bluetooth support. Can someone name any app besides talkatone, even a voice recorder that works with bluetooth so I can just test it?
I'm actually surprised it's this bad. Bluetooth audio isn't that cutting edge. It should pair and now act as your soundcard so to speak. I initially thought to blame the OS because I thought any app that requests to play a sound or record a sound, would be re-directed by the OS to now use the bluetooth device.
I'm pretty sure it works exactly like this on windows. Or for example, I have a usb headset on my pc. It shows up as a soundcard. I make it the default and every app now uses that. No developer had to code to use a usb headset/mic, it just works.
Again a little disappointed that it's been a little trying just to get a bluetooth headset to function properly. I tried 3 at my friends that all pair fine and work flawlessly on his playbook in all his apps, and now I bought 1 so it's hard to say all of these bluetooth headsets have quirks and don't work properly with android.
Still trying to get this working. It pairs fine, and shows in the bluetooth details as being connected with phone audio and media audio.
It's a Aluratek ABH01F which I've read great things about. It supports a2dp. I'm not too familiar with bluetooth and microphones so I'm not sure if there is anything else to check for android to support a bluetooth microphone.
I don't know why I didn't think of it before but I tried google's voice search and it doesn't work either. I can hear the audio fine, just no mic.
Can anyone confirm if google's voice search works with their bluetooth mic? You probably have to walk out of the room to verify it's not the units mic that is picking it up obviously.
I'm not convinced bluethooth mics work at all on the nexus 7. I could chalk it up to my headset just doesn't place nice with the nexus 7 but again I tried 3 bluetooth devices at my friends. I found this post on another site:
Well, I got around to testing a bluetooth headset. single earpiece, Avantalk AH28. Not the best, but it works fine with a phone. Paired with the tablet fine. I dialed on groove ip - dial tones came from the tablet, the ringing transferred to the earpiece, when phone was answered there was no sound transmission at all- not from the bluetooth earpiece, or from the tablet. Just dead air. Tried it twice.
2nd test- google music played from tablet- not into the earpiece.
I have a stereo bluetooth headset with mic that I can test with but will have to charge that one up first. Will get back to you.
************************************************** ****
Got to my stereo Southwing SA505 bluetooth test. It worked to play music from tablet beautifully. Did not work with groove IP- went in and made sure settings were set for bluetooth- Mic did not work.
Click to expand...
Click to collapse
http://www.nexustablets.net/forum/nexus-tablet-audio/985-does-headset-jack-have-microphone-capability.html
Again, I hear audio fine via bluetooth, so I wonder if some of you were thinking the bluetooth mic was working but it was actually the unit's mic.
This app called tapemachine specifically states it has bluetooth support. It fails for me when I change it to bluetooth in the settings, can someone else try it?
https://play.google.com/store/apps/details?id=com.samalyse.free.tapemachine&feature=nav_result#?t=W251bGwsMSwxLDMsImNvbS5zYW1hbHlzZS5mcmVlLnRhcGVtYWNoaW5lIl0.
So I'm starting to think my thread title is correct. If I am, I'm hoping there is a way to hack some file changing the available audio profiles. I've read others doing something similar with different devices when the manufacturer disable those audio profiles. I would find it doubtful that google/asus would do this though.
Anyway, if anyone can try that app, or confirm that say grooveip is using the bluetooth mic and not the device. An easy test is tap on the unit mic while recording and see if you or the person you are talking to hears that.
No one? I know a couple of you said it worked, but are you sure grooveip is actually recording via the mic? I can hear phone calls using various sip apps with bluetooth, but I know the mic isn't recording. One of the headsets my friend has is a Motorola MOTOROKR S9 Stereo Bluetooth Headphones. Link here: http://www.amazon.com/Motorola-S9-Bluetooth-Headphones-Packaging/dp/B0017KTOJK.
I've only tried stereo headsets, so maybe that is the issue. The Motorola HS850 is a single ear piece, I'm not sure what plantronics set you have.
I'd really appreciate if someone else can verify if bluetooth is working. If bluetooth recording in fact works with the nexus 7, I must be really unlucky with 4 headsets that don't, which I find highly unlikely or nexus 7 has poor bluetooth support. The only thing left is my bluetooth hardware is broken which I find even more unlikely. Aradreamer, you say you've seen several posts saying bluetooth works, but I haven't found one post explicitly stating bluetooth recording works. I found more post on other forums clearly stating it doesn't work.
sark666 said:
I'd really appreciate if someone else can verify if bluetooth is working. If bluetooth recording in fact works with the nexus 7, I must be really unlucky with 4 headsets that don't, which I find highly unlikely or nexus 7 has poor bluetooth support. The only thing left is my bluetooth hardware is broken which I find even more unlikely. Aradreamer, you say you've seen several posts saying bluetooth works, but I haven't found one post explicitly stating bluetooth recording works. I found more post on other forums clearly stating it doesn't work.
Click to expand...
Click to collapse
odd odd ...
first off i have the Nexus 7 16g with it rooted.
heres what i did first i bought the samsung HM1200 didnt thoroughly test that 1 because i figured it just wouldnt work with the device ( or was broken ) once i started to get all this screeching out of it... i heard sound momentarily then all it did was the screeching at different levels. returned it yesterday. then i added a couple more bucks ( about $27 total ) and got the plantronics M20 took it home and crossed my fingers. got it all it paired up and what not and ended up with the same condition except now the mic is working perfectly. i tested this thoroughly now over and over inside and outside and also away from the N7 to be sure the mic is working. this is great BUT i cannot hear any sound at all coming in to the N7 except the same screeching at constantly varying levels. this is with both grooveip and talkatone. i also tried uninstalling beats audio and rebooting but i read somewhere this wont change the drivers back to the originals and i still have the same condition. i just got the N7 about 3 weeks ago and the store where i bought it has a price guarantee so i am today planning to return it and get the N7 again but this time the 32g version. ( they got 2 left so i will be going ASAP. ) so almost all the work i put into setting this thing up is about to be wasted. still i am going to do it anyways. to me its just the point of getting the best i can with my available budget/resources and i can easily see this thing be full and kicking myself in the butt for not doing it. this time around i will test all of what i mentioned here BEFORE i root it. in fact i will only install the necessary apps ( grooveip/talkatone etc.. ) during testing. its a real pain in the butt but it is a MUST i have this thing working as a phone with BT asap. thanks for the input and i will report back later.
update: actually in a more quiet room i was able to hear myself on the BT headset but very very low and in the background behind the screeching. still will report back later with the new unit.
For some reason the Bluetooth headset profile on the n7 is totally broken. I tried MANY headsets and none of them work. It is either the drivers, the hardware or the kernel. I hope it fixable in the 3g version.
Sent from my Nexus 7 using xda premium
yep i am sitting here now with the 32g N7 and the first thing i did was try the BT unrooted and its the exact same thing screeching like mad can hear myself on the mic perfect from the other phone and can hear the other phone low in the background of the screeching on the N7 ugh
i have a temporary solution that should work till its sorted.... i need a new headset for my computer anyways so ill just make sure to grab one that is USB then when my OTG cable arrives i am pretty sure that should work. it will be corded but at least i can use the phone somewhat normally for free. ill let you know. now im off to rebuild the whole thing back to where i had it in the 16.
zip1212 said:
yep i am sitting here now with the 32g N7 and the first thing i did was try the BT unrooted and its the exact same thing screeching like mad can hear myself on the mic perfect from the other phone and can hear the other phone low in the background of the screeching on the N7 ugh
Click to expand...
Click to collapse
Bummer. Hopefully they fix it with 4.2 or with the 3G version.
It also seems that if you try to toggle speakerphone / BT headset in various voip apps the tablet will crash and restart.
I tried with GrooveIP, Talkatone and the build in phone app (After changing the framework-res.apk file).
I also noticed i had better luck getting the BT headset to fully (and randomly) work when doing outgoing calls. It never worked on incoming calls.
Any progress on this?
I've noticed the same problem and just returned a BT headset due to the problems in GrooveIP & Talkatone
As a side note I was able to get the BT headset to work as a MIC with the google voice commands by using the following..
- Soundabout
- Under BT settings set it to force mono BT mic
- Set audio to wired headset
Just as ref, I'm using my N7 in my car, so my setup may be a bit different.
But this worked, I was able to tell my N7 commands and it would read out the response over my car speakers.
Anyone had success with a USB mic? Curious if that will work.
I'm very interested in this thread too.
I have a 32GB nexus 7, rooted and unlocked. I have a Platronics M100 bluetooth earpiece. My goal is to be able to dictate to Evernote through the BT earpiece. It is pairing and under the connect settings it is showing up as "phone audio". But when I speak into it nothing is happening in Evernote. I also do not get media audio through the earpiece.
My Sony xperia Z accepts audio from bluetooth microphones, but only during a phone call.
When the call is terminated the paired bluetooth mic becomes inactive and the phones built in microphone takes over. I have tried many apps but none will accept audio from a BT mic.
I have tried a number of headsets and speakerphones and they all behave in the same way. Sound is not a problem as the BT speaker simply replaces the phones internal one when paired.
The xperia Z has a setting which claims to: " record audio through bluetooth headset if available", but this setting does nothing. I keep retrying the setting at every android update, to no avail. Currently at 4.2.2.
When I plug in a wired headset, the speaker and mic simply replace the ones in the phone. Why doesn't bluetooth behave in the same way?
This issue has been raised in many forums, in relation to many android devices, but never answered.
Hi all.
Here's what I'm seeing and what I'm trying to figure out.
On my new Nexus 4, which in other respects seems just fine, voice over Bluetooth is basically unusable. I first tried testing out voice commands for dialing etc., which consistently failed. A friend happened to call while I was doing this, and could barely make out what I was saying (reported it as choppy, digitized etc.).
This is using a Plantronics Discovery 975. Which works fine with my Nexus One, so isn't a faulty headset (I even had my wife's same model headset and tried it also). I don't have any other headsets handy.
This N4 *has* been upgraded to 4.2.1. After searching a bit, I found numerous reports and a couple articles re many BT features, including voice over BT, being broken to a great extent on many devices with 4.2.1 (or earlier, and getting still worse in 4.2.1). Those reports, however, mostly seemed to reference devices other than the N4 (though perhaps only due to its newness & relative scarcity, hard to know).
I then tried the headsets with my wife's Galaxy Nexus, which also had been upgraded to 4.2.1. On that, however, the voice over BT apparently worked fine, or at least much better -- sounded ok, and VR could recognize contacts to be called.
Thus I could at least conclude it isn't just voice over BT simply broken in 4.2.1 everywhere (which would have made things simple.. ), and it isn't simply voice over BT in 4.2.1 with the Discovery 975 either. So add in the Nexus 4.
I've seen many reports of BT streaming audio issues on the N4 with 4.2.1, but little at all about voice, and certainly some successful reports for voice.
So I'm trying to figure out: What is the likelihood that with all of the 4.2.1 Bluetooth troubles, there is a consequent BT software issue on my Nexus 4 when used with this Discovery 975 headset? Vs., what is the likelihood that my specific N4 has some kind of hardware issue with BT?
- How many folks are using voice over BT successfully? Anyone else having issues?
- What version does your N4 have -- 4.2.1, or earlier?
- If you used it *before* an upgrade to 4.2.1, did it work both before and after the upgrade, or did the upgrade introduce issues?
- Anyone specifically using the Plantronics Discovery 975, or another Plantronics?
Basically, I'd really like to avoid the crap shoot of exchanging the phone (BT voice is a critical feature for me), since it seems fine in all other respects, and with all of the manifest BT issues that appear to have been introduced with 4.2.1, that seems like at least a reasonable culprit.
However, if there aren't widespread issues with voice over BT on the N4 with 4.2.1, then it would seem the only way it would be a software issue, would be if it's the combination with my particular Plantronics headset model. Otherwise, I think I'd have to face the possibility of a hw issue. (Bad timing for me with 4.2.1's buggy BT issues, it really obscures the situation. )
Another useful test for me to try might be to revert back to the prior OS version and test with that, but I gather I have to root to do that, not sure if that also voids the warranty.. (hence preventing me from exchanging it if I did ultimately need to).
TIA
Bump.. help a brother out -- no one using voice over Bluetooth on their N4, or have some perspective on the above?
Seems like a lot more people talking about audio streaming over BT than voice.. not sure if that's because audio streaming is much more widely used, or if people are having issues with audio streaming with their N4 but not voice.
gilgamesh0 said:
Bump.. help a brother out -- no one using voice over Bluetooth on their N4, or have some perspective on the above?
Seems like a lot more people talking about audio streaming over BT than voice.. not sure if that's because audio streaming is much more widely used, or if people are having issues with audio streaming with their N4 but not voice.
Click to expand...
Click to collapse
Yes I've noticed BT broken when trying to use voice commands on a headset. But what's more troubling is BT sometimes just doesn't work at all. Tap to turn on and it immediately turns off. A reboot fixes the issue but I have to do this every other day it seems. Hoping for either a 4.2.2 or 4.3 patch.
SUTHRNFRIED said:
Yes I've noticed BT broken when trying to use voice commands on a headset. But what's more troubling is BT sometimes just doesn't work at all. Tap to turn on and it immediately turns off. A reboot fixes the issue but I have to do this every other day it seems. Hoping for either a 4.2.2 or 4.3 patch.
Click to expand...
Click to collapse
Thanks Suthrn.. sounds also as though, like me, you never tried voice BT prior to 4.2.1. When you say a reboot fixes the issue, you mean just a simple long-press power off and restart? Or some kind of hard reset?
gilgamesh0 said:
Thanks Suthrn.. sounds also as though, like me, you never tried voice BT prior to 4.2.1. When you say a reboot fixes the issue, you mean just a simple long-press power off and restart? Or some kind of hard reset?
Click to expand...
Click to collapse
Oops, just realized, sounds like you mean the reset resolves this other issue you mention with the BT just immediately turning off again after turning it on.
I haven't seen that problem as yet, but of course there's still time.
Bluetooth works great for me... Syncs 2x faster than my galaxy nexus. Using Motorola s11 HD flex stereo Bluetooth headset. I think these things are at least BT 3.0 but everything about them has been alright. The only problem i have is that music over BT is blown out crackling depending on the app (Pandora for instance) This is supposedly a 4.2 issue and not a hardware one.
Sent from my Nexus 4 using xda premium
Jayrod1980 said:
Bluetooth works great for me... Syncs 2x faster than my galaxy nexus. Using Motorola s11 HD flex stereo Bluetooth headset. I think these things are at least BT 3.0 but everything about them has been alright. The only problem i have is that music over BT is blown out crackling depending on the app (Pandora for instance) This is supposedly a 4.2 issue and not a hardware one.
Click to expand...
Click to collapse
Thanks. But it sounds like yours is another case of just audio streaming to your Bluetooth stereo headphones, not using voice over a Bluetooth voice headset (actually just took a look for the headset model you described, and indeed it appears to be just for streaming output, not for voice input). The problem I'm talking about is specifically with voice input to the phone. In fact, with my Plantronics headset, I've been able to hear the VR prompts coming over from the phone without any obvious problems, it's just my voice input to the phone that appears to be getting munged.
I use plantronics back beat 903+ and have less issues than with my iPhone. I stream audio books and make calls. Voice commands are interpreted way better than on Siri. I had a 1 in 5 shot of it picking up "Call Lissa Lu" the first time. I cannot say it is perfect but I haven't had people complaining of not understanding me on a call.
Sent from my Nexus 4 using xda app-developers app
gilgamesh0 said:
Hi all.
Here's what I'm seeing and what I'm trying to figure out.
On my new Nexus 4, which in other respects seems just fine, voice over Bluetooth is basically unusable. I first tried testing out voice commands for dialing etc., which consistently failed. A friend happened to call while I was doing this, and could barely make out what I was saying (reported it as choppy, digitized etc.).
This is using a Plantronics Discovery 975. Which works fine with my Nexus One, so isn't a faulty headset (I even had my wife's same model headset and tried it also). I don't have any other headsets handy.
This N4 *has* been upgraded to 4.2.1. After searching a bit, I found numerous reports and a couple articles re many BT features, including voice over BT, being broken to a great extent on many devices with 4.2.1 (or earlier, and getting still worse in 4.2.1). Those reports, however, mostly seemed to reference devices other than the N4 (though perhaps only due to its newness & relative scarcity, hard to know).
I then tried the headsets with my wife's Galaxy Nexus, which also had been upgraded to 4.2.1. On that, however, the voice over BT apparently worked fine, or at least much better -- sounded ok, and VR could recognize contacts to be called.
Thus I could at least conclude it isn't just voice over BT simply broken in 4.2.1 everywhere (which would have made things simple.. ), and it isn't simply voice over BT in 4.2.1 with the Discovery 975 either. So add in the Nexus 4.
I've seen many reports of BT streaming audio issues on the N4 with 4.2.1, but little at all about voice, and certainly some successful reports for voice.
So I'm trying to figure out: What is the likelihood that with all of the 4.2.1 Bluetooth troubles, there is a consequent BT software issue on my Nexus 4 when used with this Discovery 975 headset? Vs., what is the likelihood that my specific N4 has some kind of hardware issue with BT?
- How many folks are using voice over BT successfully? Anyone else having issues?
- What version does your N4 have -- 4.2.1, or earlier?
- If you used it *before* an upgrade to 4.2.1, did it work both before and after the upgrade, or did the upgrade introduce issues?
- Anyone specifically using the Plantronics Discovery 975, or another Plantronics?
Basically, I'd really like to avoid the crap shoot of exchanging the phone (BT voice is a critical feature for me), since it seems fine in all other respects, and with all of the manifest BT issues that appear to have been introduced with 4.2.1, that seems like at least a reasonable culprit.
However, if there aren't widespread issues with voice over BT on the N4 with 4.2.1, then it would seem the only way it would be a software issue, would be if it's the combination with my particular Plantronics headset model. Otherwise, I think I'd have to face the possibility of a hw issue. (Bad timing for me with 4.2.1's buggy BT issues, it really obscures the situation. )
Another useful test for me to try might be to revert back to the prior OS version and test with that, but I gather I have to root to do that, not sure if that also voids the warranty.. (hence preventing me from exchanging it if I did ultimately need to).
TIA
Click to expand...
Click to collapse
It might be your phone after all. I've been using BlueAnt Q2 and built-in system in my car - have not noticed any issues before or after 4.2.1 upgrade.
I also have a Plantronics Discovery 975 and have experienced the same choppiness/digitized sound you describe.
This has happened on my N4 with my 975, and my wife's N4 with her 975. We both had Nexus Ones before and the 975s worked perfectly.
I have not had a chance to try the N4 with another bluetooth device, and I did not get a chance to use the 975 with the N4 before upgrading to 4.2.1.
Anyway, you are not alone in your frustration with the sound through the 975...
gilgamesh0 said:
Hi all.
Here's what I'm seeing and what I'm trying to figure out.
On my new Nexus 4, which in other respects seems just fine, voice over Bluetooth is basically unusable. I first tried testing out voice commands for dialing etc., which consistently failed. A friend happened to call while I was doing this, and could barely make out what I was saying (reported it as choppy, digitized etc.).
This is using a Plantronics Discovery 975. Which works fine with my Nexus One, so isn't a faulty headset (I even had my wife's same model headset and tried it also). I don't have any other headsets handy.
This N4 *has* been upgraded to 4.2.1. After searching a bit, I found numerous reports and a couple articles re many BT features, including voice over BT, being broken to a great extent on many devices with 4.2.1 (or earlier, and getting still worse in 4.2.1). Those reports, however, mostly seemed to reference devices other than the N4 (though perhaps only due to its newness & relative scarcity, hard to know).
I then tried the headsets with my wife's Galaxy Nexus, which also had been upgraded to 4.2.1. On that, however, the voice over BT apparently worked fine, or at least much better -- sounded ok, and VR could recognize contacts to be called.
Thus I could at least conclude it isn't just voice over BT simply broken in 4.2.1 everywhere (which would have made things simple.. ), and it isn't simply voice over BT in 4.2.1 with the Discovery 975 either. So add in the Nexus 4.
I've seen many reports of BT streaming audio issues on the N4 with 4.2.1, but little at all about voice, and certainly some successful reports for voice.
So I'm trying to figure out: What is the likelihood that with all of the 4.2.1 Bluetooth troubles, there is a consequent BT software issue on my Nexus 4 when used with this Discovery 975 headset? Vs., what is the likelihood that my specific N4 has some kind of hardware issue with BT?
- How many folks are using voice over BT successfully? Anyone else having issues?
- What version does your N4 have -- 4.2.1, or earlier?
- If you used it *before* an upgrade to 4.2.1, did it work both before and after the upgrade, or did the upgrade introduce issues?
- Anyone specifically using the Plantronics Discovery 975, or another Plantronics?
Basically, I'd really like to avoid the crap shoot of exchanging the phone (BT voice is a critical feature for me), since it seems fine in all other respects, and with all of the manifest BT issues that appear to have been introduced with 4.2.1, that seems like at least a reasonable culprit.
However, if there aren't widespread issues with voice over BT on the N4 with 4.2.1, then it would seem the only way it would be a software issue, would be if it's the combination with my particular Plantronics headset model. Otherwise, I think I'd have to face the possibility of a hw issue. (Bad timing for me with 4.2.1's buggy BT issues, it really obscures the situation. )
Another useful test for me to try might be to revert back to the prior OS version and test with that, but I gather I have to root to do that, not sure if that also voids the warranty.. (hence preventing me from exchanging it if I did ultimately need to).
TIA
Click to expand...
Click to collapse
Parrot MKI 9200 here. Works fine for voice calls... in fact, generally people tell me that it's better than my old GNex. Voice recognition on the parrot works as reliably as on the GNex... If the quality was bad, it certainly wouldn't work.
I read a lot of complaints about the new BT stack in 4.2.x so perhaps this is related to the A2DP issues... audio streaming is definitely poor on the nexus 4. Or perhaps it just doesn't like your headset. Have you tried another?
Daern
Sent from my Nexus 4 using Tapatalk 2
I have noticed that compared to my old Galaxy nexus, the quality of the connection to my Camaro is much much worse. Its a 2012 and a I had the dealership do a software update just to make sure it wasn't the car. Any other phone its crystal clear by my N4 is just horrible.
I just noticed this yesterday in my Mazda 3. Music streams perfectly fine, but I was on a call, and the other party could not understand what I was saying. I tried listening from the other side, and it's really distorted and difficult to hear.
fooznugget said:
I just noticed this yesterday in my Mazda 3. Music streams perfectly fine, but I was on a call, and the other party could not understand what I was saying. I tried listening from the other side, and it's really distorted and difficult to hear.
Click to expand...
Click to collapse
Same. Streaming music is fine. But sound is distorted on calls.
I'm using a Plantronics Voyager Pro and also have the phone connected via Bluetooth to my BMW. I've had calls come in where I was unable to hardly hear what they were saying (horrible sounding audio) and they said the same thing about me. This has happened on both my Plantronics headset (I have two, and it's happened to both) and in my BMW. Just now I got a pair of VIZIO VXTHB100 Stereo Headphones and when I first tried to pair them up the phone only showed the MAC address of the headset and came up with an error when trying to connect it... It's worth noting that I did do a reboot on my phone earlier in the day already to.
I turned bluetooth off and back on (without touching my headset) and POOF it found the headset (showing by name this time) and connected right away.
I really, REALLY, hope this is a software issue that will get patched soon. Coming from my Samsung Galaxy Nexus which was PERFECT and now I'm dealing with this... I feel like it's my Nexus ONE all over again.... I'm honestly concerned with the quality of this phone compared to the Samsung Galaxy Nexus (internals wise). I'd go back to my Samsung GNexus if my woman wasn't using it as an upgrade from her old Nexus S... Another thing I've noticed is that 90% of the time I can't get Google Chat/Google + Video chats to use my bluetooth headset OR Skype to use it either... SOOOO damn annoying.
BTW, the sound quality on the VIZIO Stereo Bluetooth headset is okay. Not as good as my gaming headset, but hey, they will do the job well and I can answer a call with them on if need be to.
-Kaz
Thanks for all the replies so far (especially the guy with the also-failing Discovery 975). I had already started to lean toward deeming it a likely software issue, given a) all the apparent general BT issues introduced with 4.2/4.2.1 and, b) I finally was able to try streaming Bluetooth audio, and that worked with no obvious issues. I would think that there wouldn't be anything physically about the BT radio or the way it is situated that would lead it to fail for just voice input but not output, no? I don't really know anything about the hw.
It seems more likely at this point that with the current BT software there are compatibility issues with various devices, but there is also a platform dependency as well (hence the Discovery 975 working ok on my wife's Galaxy Nexus with 4.2.1, but not my N4).
Or else, if it is a hw issue, it sounds like one present on a number of Nexus 4s, given the responses so far.
Of course, if Google would say something about it, we'd not be in the dark. This is a pretty critical feature for a lot of folks. Unfortunately, I've come to be surprised when they announce anything at all. Bugs happen, even severe ones, but it would help a lot to just know what is going on.
I've used seinhessier vmx 100 which worked surprisingly well, as on my old phone I almost threw it out as no one understood me and I could hardly hear them. Now they don't even notice! I'm using stock, not rooted 4.2.1.
Sent from my Nexus 4 using xda premium
jholt1 said:
I've used seinhessier vmx 100 which worked surprisingly well, as on my old phone I almost threw it out as no one understood me and I could hardly hear them. Now they don't even notice! I'm using stock, not rooted 4.2.1.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I am using a Plantronics Voyager and i too have some issues. The problem is hearing what other are saying as most sound distorted and to loud. I dont know what to do and the headset worked perfect with my old Galaxy S2.
Similar poor audio when using LG Bluetooth headset which worked great with iPhone 4s and macbook pro for calls.
Has anyone tried a custom rom, say cyanogen 10 based or aokp?
Wondering if the stacks in the custom roms are any different than stock.
tr2ride said:
Similar poor audio when using LG Bluetooth headset which worked great with iPhone 4s and macbook pro for calls.
Has anyone tried a custom rom, say cyanogen 10 based or aokp?
Wondering if the stacks in the custom roms are any different than stock.
Click to expand...
Click to collapse
I would like to know that as well. Or any other fixes/tricks for that matter...
When I connect the smartphone with the car via Bluetooth, the music is just intermittent suonds. How do I fix this?
I would like to know this too, anyone?
I started having this same issue after the last/first Tmobile update, before it was fine.
Same thing here. The music would either play through the phone's earpiece or sound like a call playing through the Bluetooth speaker. I read YouMail was a cause so I uninstalled and it still happened I force closed the phone app and it worked normally after that. The issue may definitely be from the T-Mobile update tho.
Yeah been having an issue with volume fading after initial connection, drives me nuts since I use the phone for GPS and music streaming. so I use the v30 for bt music and OnePlus for gps
I'm having an issue with the phone trying to automatically connect to a second Bluetooth device and begin playing music on it. This happened tonight while following behind my wife's car.
Every time we stopped at a light it would connect and I would loose audio in my vehicle and play in hers. No way to stop it connecting other than forget the device or turn off all the functions in that device settings.
R800x_user said:
Yeah been having an issue with volume fading after initial connection, drives me nuts since I use the phone for GPS and music streaming. so I use the v30 for bt music and OnePlus for gps
Click to expand...
Click to collapse
I have the T-Mobile 6T and I have this same issue.
It seemed like the previous update fixed it, and was broken by the current update. Anyone know if the international rom has the same problem?
NAB4 said:
I have the T-Mobile 6T and I have this same issue.
It seemed like the previous update fixed it, and was broken by the current update. Anyone know if the international rom has the same problem?
Click to expand...
Click to collapse
I have converted my TMobile 6t to international and those bugs are fixed.
R800x_user said:
I have converted my TMobile 6t to international and those bugs are fixed.
Click to expand...
Click to collapse
I'll be updating this on the weekend. Nothing worse than having the beat drop to have the volume drop...
NAB4 said:
I'll be updating this on the weekend. Nothing worse than having the beat drop to have the volume drop...
Click to expand...
Click to collapse
I feel you, dealt with that for a while until they found a way to convert the phone. anywho hope it fixes your issue.
Bluetooth nightmare
I've been having the same issue since I bought my T-Mobile 6T last year and am pulling out my hair trying to figure out how to fix it. I have a "GTA Car Kit" Bluetooth module installed in my '06 Mazda 3 and I use Android Auto with my phone docked in a CD slot mount to give me hands-free text messaging, navigation and music / audiobooks. My phone is also always connected to my android wear watch, so it's technically connected to two Bluetooth devices at once when I use it.
The problem is that audio playback via Pandora, Google Music and my audiobook app that plays on-device mp3's intermittently stutters or skips. It happens immediately sometimes, other times it will work perfectly for half of my commute and then start stuttering every few seconds until I finally just turn off the music/audiobook completely.
I've tried:
Turning bluetooth on and off
Turning my car radio on and off
Changing the developer mode settings for Bluetooth AVRCP Version, Codec, Sample Rate, Playback quality etc.
Clearing storage/cache for Bluetooth
Switching to the international version ROM for the device
Once I got the Oxygen OS v10 update I really though the problem was fixed, but after a few days of working fine it started skipping again.
Does anyone have any idea what's causing this or other things I can try?
[EDIT] I found one more new thing to try on the OnePlus 6T forums https://forums.oneplus.com/threads/bluetooth-stuttering-solved.1076196/
I'll give this a try and report back
Been experiencing a strange issue with bluetooth in my car (BMW). Phone is paired successfully but when I call someone the audio does not transfer to the car speaker automatically. You have to press the bluetooth button on the call screen and select the car system manually and then audio is heard over the car speakers. Never had this issue with my old OP2.
I've been through all the settings, both phone and car but cannot find anything that could be causing this.
Phone is a rooted 6T McLaren on 9.0.10.
Still facing this issue. I tried both the original (from playstore) and the modded google dialer as well as the stock dialer of course. Phone pairs fine, contacts sync and I can dial using the steering controls.
However, volume is by default routed to the earpiece not car speakers. On the dialer screen it shows that audio is connected to the car. If I change manually from say car back to phone speaker and then back to car it will then work.
I'm using a rooted 6T McLaren. Previous phone was OP2 running AOSiP with basically the same magisk modules and connected perfectly to the same car. Looked through all possible settings in the phone but cannot find the culprit. Not much to mess about incar settings; everything is as it should be.
Any help would be appreciated.
Interesting problem. Everyone would be stuck with it.
ClydeBreton said:
Interesting problem. Everyone would be stuck with it.
Click to expand...
Click to collapse
Same problem with HONDA Pilot and OP6T (and OP5T)
polzovotel said:
Same problem with HONDA Pilot and OP6T (and OP5T)
Click to expand...
Click to collapse
out of curiosity, are you rooted and if yes are you using any magisk modules? i have a feeling it could be related to one of the audio modules although my OP2 had exactly the same modules and did not produce the same issue.
zickler_malta said:
out of curiosity, are you rooted and if yes are you using any magisk modules? i have a feeling it could be related to one of the audio modules although my OP2 had exactly the same modules and did not produce the same issue.
Click to expand...
Click to collapse
No, pure stock on both devices, the bootloader is locked, no root.
I think the problem started after upgrade to Oreo. Now when I am calling from the phone, the call is always routed to the phone first and I need to manually switch to BT. If I call from the Car device - it is routed to BT immediately.
polzovotel said:
No, pure stock on both devices, the bootloader is locked, no root.
I think the problem started after upgrade to Oreo. Now when I am calling from the phone, the call is always routed to the phone first and I need to manually switch to BT. If I call from the Car device - it is routed to BT immediately.
Click to expand...
Click to collapse
ok so it's definitely not the rooting or magisk modules. i did have some problems with my OP2 before, mainly not connecting to the car after pairing. Issue seemed better after changing from RR to AOSiP roms.
but this problem on the 6T is stranger still. would be interesting to see if other people have it. for info car is BMW F20.
Sound>earphone mode>smart answer for Bluetooth? I know you said you checked all settings but just in case...
zickler_malta said:
ok so it's definitely not the rooting or magisk modules. i did have some problems with my OP2 before, mainly not connecting to the car after pairing. Issue seemed better after changing from RR to AOSiP roms.
but this problem on the 6T is stranger still. would be interesting to see if other people have it. for info car is BMW F20.
Click to expand...
Click to collapse
I've not rooted or unlocked my T-Mobile OP6T yet... Still stock OOS. Mine works as it should in my truck using a Kenwood DNN991HD both calling out and incoming calls. Just FYI if you are rooted on the stock OS.
Swimguy14 said:
Sound>earphone mode>smart answer for Bluetooth? I know you said you checked all settings but just in case...
Click to expand...
Click to collapse
pretty sure that at one point that setting was on. i switched if off a couple of days ago to see if it would make a difference (which it didn't). now I have unpaired and re-paired my phone to my car's bluetooth and put that setting on again. will report back.
Swimguy14 said:
Sound>earphone mode>smart answer for Bluetooth? I know you said you checked all settings but just in case...
Click to expand...
Click to collapse
re-tried with this setting on after re-pairing the phone. problem persists. if you manually change from dialer screen from phone speaker back to bluetooth then audio is heard through the car speakers. otherwise, by default, audio comes out of the earpiece.
zickler_malta said:
Still facing this issue. I tried both the original (from playstore) and the modded google dialer as well as the stock dialer of course. Phone pairs fine, contacts sync and I can dial using the steering controls.
However, volume is by default routed to the earpiece not car speakers. On the dialer screen it shows that audio is connected to the car. If I change manually from say car back to phone speaker and then back to car it will then work.
I'm using a rooted 6T McLaren. Previous phone was OP2 running AOSiP with basically the same magisk modules and connected perfectly to the same car. Looked through all possible settings in the phone but cannot find the culprit. Not much to mess about incar settings; everything is as it should be.
Any help would be appreciated.
Click to expand...
Click to collapse
What year BMW?
Different year BMWs have different BT implementation.
I don't have that issue with my BMW. I've got a 2014, it's never had perfect Bluetooth performance but calls always come through on speakerphone. Often phone audio will be connected and I'll have to manually get media audio connected.
Morpheus991 said:
I don't have that issue with my BMW. I've got a 2014, it's never had perfect Bluetooth performance but calls always come through on speakerphone. Often phone audio will be connected and I'll have to manually get media audio connected.
Click to expand...
Click to collapse
I have a 2008 and a 2013 and I don't have any issue with either.
Morpheus991 said:
I don't have that issue with my BMW. I've got a 2014, it's never had perfect Bluetooth performance but calls always come through on speakerphone. Often phone audio will be connected and I'll have to manually get media audio connected.
Click to expand...
Click to collapse
my BMW is a 2012 F series model. when you say speakerphone do you mean calls get routed to the phones speaker by default instead of the car speakers? in my case calls are routed to the earpiece even though phone is connected to the car and I can browse my recents through the steering wheel controls. to listen to the audio through the car speakers I have to manually select phone speaker then back to bluetooth on the dialer screen.
zickler_malta said:
my BMW is a 2012 F series model. when you say speakerphone do you mean calls get routed to the phones speaker by default instead of the car speakers? in my case calls are routed to the earpiece even though phone is connected to the car and I can browse my recents through the steering wheel controls. to listen to the audio through the car speakers I have to manually select phone speaker then back to bluetooth on the dialer screen.
Click to expand...
Click to collapse
Sorry I wasn't clear. My calls always come through on the car stereo but music does not usually. When I look at the connection on my car screen I see the phone signal icon but not the Bluetooth logo. Once I hit the media button the Bluetooth logo pops up (alongside the signal logo) and music streams through the car stereo as well as phone calls.
I'm guessing it's a BMW thing. Car tech is pretty mediocre at best.
---------- Post added at 08:59 AM ---------- Previous post was at 08:58 AM ----------
Couldn't hurt to bring it up in the community feedback forum that OnePlus has...?
Morpheus991 said:
Sorry I wasn't clear. My calls always come through on the car stereo but music does not usually. When I look at the connection on my car screen I see the phone signal icon but not the Bluetooth logo. Once I hit the media button the Bluetooth logo pops up (alongside the signal logo) and music streams through the car stereo as well as phone calls.
I'm guessing it's a BMW thing. Car tech is pretty mediocre at best.
---------- Post added at 08:59 AM ---------- Previous post was at 08:58 AM ----------
Couldn't hurt to bring it up in the community feedback forum that OnePlus has...?
Click to expand...
Click to collapse
Well yes it could be a car issue although my old OP2 worked perfectly in the same car. As you suggested I asked the same question in the Oneplus forums.
I have the issue also with an Audi A3. Anyone has found a fix?
clonfsp said:
I have the issue also with an Audi A3. Anyone has found a fix?
Click to expand...
Click to collapse
since that post I got a newer car (2018) and the issue disappeared even though if I remember correctly it had sorted itself out even on the older car.
This sounds a little like what my girlfriend just reported to me on her 6T. I gave her the phone last week with a factory reset, so no root or anything.
She says it paired fine to her car, but wouldn't automatically connect like her old Android (Moto) did.
I'm 5 minutes into looking into it for her, and this is the first similar thread I've seen.
Hi Everyone
I've been struggling with the bluetooth connection to my Airpods 2 after June update on the Essential phone. The connection is extremely spotty - putting the phone inside my pocket is actually enough for it to disconnect the audio!
The signal is back when I take the phone back close to my face... which is not very practical. Not sure this is actually due to the update but I've started noticing it just after so difficult to think this is not linked.
Anyone experienced issue with bluetooth recently? I've tried playing with the bluetooth options in the developer section to no avail... I have tried with my old bluetooth speaker as well and same problem, putting my hands around the phone or moving slightly from the speaker disconnects the audio! Definitely a problem with bluetooth signal but no sure it comes from.
Thanks for your help
T.
tamaire said:
Hi Everyone
I've been struggling with the bluetooth connection to my Airpods 2 after June update on the Essential phone. The connection is extremely spotty - putting the phone inside my pocket is actually enough for it to disconnect the audio!
The signal is back when I take the phone back close to my face... which is not very practical. Not sure this is actually due to the update but I've started noticing it just after so difficult to think this is not linked.
Anyone experienced issue with bluetooth recently? I've tried playing with the bluetooth options in the developer section to no avail... I have tried with my old bluetooth speaker as well and same problem, putting my hands around the phone or moving slightly from the speaker disconnects the audio! Definitely a problem with bluetooth signal but no sure it comes from.
Thanks for your help
T.
Click to expand...
Click to collapse
I also noticed poor quality bluetooth connection / range recently... anyone else have any insight into this?