Database Users

Polaris bluetooth mute issues

I didn't want to open yet another Polaris bluetooth problems but none were like mine.
I have the O2 Orbit 2 and I had bluetooth mute problems which were usually resolved with soft reset, I think that ever since I installed HTC's official bluetooth mute fix the mute problems got worse.
Every couple of calls or when I plug something to the mini usb (ear phone, charging, data, etc') my bluetooth is muted, the connection is established and I think I do hear through it but with extremely low volume (less then a whisper, more like back ground noise) the mute almost never fixes itself, it goes on even if I flash with a different ROM!!, what fixes it is playing with turning on and off the connection to the headset while in call or, while in call pluging and removing the wired headset, once it's back, it usually stays ok until (randomly) when I plug something to the usb, at first I though it will never work again (flashing something like 10 different roms...) but this fix is less then convenient, again, sadly the official fix doesn't help.
Anyone knows the return policy to O2 from Germany? I live at Israel so I think it might be a problem...

Same problem for me.
After the original fix, my bluetooth headset is always mute.
I have ordered a new original HTC M200 headset. I hope it will work............

Original M200 arrived today.
Don't work. Always mute.
I have tried to uninstall the original fix without any resultate.

Did you get yours to work?
You can try the on/off trick, I usually call my voicemail when the mute starts and then goto options and turn handsfree off, then again turn it on, sometimes it works after 4-5 tries sometimes after 2-3 minutes...
Sometimes the voice comes back in slow motion!!, I thought at first that it was garbled, but once I have a voice mail of a woman who talked fast so when the voice came back in slow motion she sounded like a very low voice slow talking man.

no, don't work on any headset......
It's a hardware problem ??

Hey guys...just wondering if you guys found a solution to this problem. I have this problem with my touch pro. The A2DP works, but for some reason handsfree through bluetooth is muted and I can't unmute. Hope you guys found a fix and can help me out.

Topaz + BT hands free (Sony MEX-BT2500)

Hi there,
Can anyone help me solve this problem:
Ik have a Sony car radio with a BT hands free function (MEX-BT2500) in my car. When I make a call, the radio stops and I can speak hands free, hearing the conversation on the car-speakers. All nice, like it should be.
Problem is when I receive a call. The radio stops and I hear a ringtone (not my phone-tone though ). When I awnser the call, the caller can hear me, but I can't hear him, unless I take the phone in my hand and put it on my ear. The sound doesn't come through the car-speakers. So an incoming call can't be awnsered handsfree.
With my former phone (nokia 6230), it was no problem. Anyone knows how to solve this?

If it was the same as my problem, turn up the volume on the phone
My phone was the exact same, for some reason when it connected it was turning the volume right down!
Hope yours as as simple

todd69 said:
If it was the same as my problem, turn up the volume on the phone
My phone was the exact same, for some reason when it connected it was turning the volume right down!
Hope yours as as simple
Click to expand...
Click to collapse
Unfortunately my problem is not that simple. I got an incoming call yesterday when I was driving, but again no sound. When I called back, there were no problems. Does anyone else have a solution?

Well, I don't have the Sony-stereo, but I've got a Pioneer with BT. I have bumped into several issues with it, and the solution is the same every time:
-first, if you have a settings-option called something like "reset BT-memory", try that one, and pair phone again.
-If that doesn't work, next step is full reset of the stereo, meaning you pull it out and disconnect the power. Then plug it back in, and re-pair phone.
This at least did the trick for me, now voice-dial works perfectly, and I even have "BT Audio", meaning I can play my Topaz' music on my carstereo without hassle.

Could also be something else simple, you are using the stereo to answer and not the handset?
If I answer using the phone with my stereo then I get the same issue as you, answer using the stereo and all is well

[Q] Flaky Bluetooth Headset Behavior since KitKat

I have a stock, non-rooted Verizon GN3, which behaved pretty much flawlessly in general, and with Bluetooth Headsets in particular, prior to the KitKat update.
This behavior occurs with both my BlueAnt S4 Visor device, and a Bose Series 2 Headset. When I turn either on, it quickly connects. With the phone locked, screen off, if I initiate the connection from either device, the Voice Dialer comes up, and I can initiate a call. The call connects, and I can hear and speak through the Bluetooth device. Everything works as expected.
But if I then try to make another call, it takes at least 2 additional tries to get the Voice Dialer to come up. The first time, the screen comes on briefly, then turns off, sometimes with the grey screen preceding the Voice Dialer briefly appearing. After a couple of more tries, the Voice Dialer comes up.
But after I have it place a call, the audio send/receive stays in the phone, and doesn't transfer to the Bluetooth device. This pretty much defeats the purpose of having it in the first place!
If I turn off either Device, turn it on and reconnect, the same cycle starts up again. It works properly the first time, but messes up after that.
With the BlueAnt S4, I removed the pairing from my GN3, effectively deleting the device, and then turned off the phone. I then did a complete reset on the S4. Turned the phone back on, re-paired, but this didn't fix it.
This is extremely annoying, to say the least.
I have examined all my settings, and they seem correct. I went to Google Search settings, Voice settings, and tried it with the Bluetooth headset ('records audio through Bluetooth headset if available') both checked and not checked, and observe the same behavior.
I welcome suggestions on how to fix this, and getting it to work consistently and correctly, as it did before KitKat.
I would consider a factory reset on the GN3, if I were convinced this would fix the problem. But I'd hate to go through that hassle, and encounter the same problem again.

I have noticed several anomalies with the kitkat update. I was hoping there was a way to roll back the update
Sent from my SM-900V, unrooted

Well, I've made some progress, and I think the problem originates in a recent update to "Google Search." I found many reports of Bluetooth related problems that were remedied when the update was rolled back.
So, I went ahead and rolled back the Google Search Update, and in fact, went ahead and Turned if Off completely.
I tried out my Bluetooth Headset (the Bose earpiece, haven't tested on the BlueAnt yet), and it works perfectly, as before. And better yet, when I touch the BT button, S-Voice comes up, rather than the plain Voice Dialer, so I can not only place calls, but initiate navigation, send a text, or whatever I would like to do. And it seems to respond each and every time.
We'll see what happens over time, and if there are any unanticipated consequences to turning Google Search off, but so far so good.
If this turns out to be the answer, it will be a Google Search issue (which would hopefully be fixed over time), rather than a KitKat issue as such.

[Q] BT Headset OS problems?

Ok so I'm trying to trace down what might be happening here.
Ive got a LG Tone Pro 750 BT headset which I totally love for the most part (epic battery time for one thing). Bought it about a month ago.
About a week ago, maybe two, something weird starts happening. I'll get a call, pick it up and no sound. Caller may or may not hear me, but if they do, it appears to be garbled (I've done a poor job of asking callers if they could hear me and inquiring about that part of the experience so not very good feedback there).
Since I'd had the BT headset for a couple weeks already, I don't even consider there could be a problemo there. So I take the SG4 to Sprint and have a tech check it out.
He comes out to see me (never happens).
Asks me if I have the LG Tone Pro headset. He then proceeds to tell me that he has the same problem on his LG (!) phone with that headset (although it's a later model than my Tone Pro 750...next one up from that model).
He says that the only way he has been able to fix it is by unpairing and re-pairing the headset. Says he has to do it every other day or so.
That was early last week.
So for the next day or two, I go without the headset being re-paired. All is well with the three or four calls I get.
I pair the headset but don't get any calls. I do listen to some podcasts and that is fine (but was never a problem so no change there).
The next day (this morning) I get a call. Problem is back. I try turning off BT making calls and that doesn't fix it. Have to restart the phone.
So I do and I can now make and receive calls. However, BT is off.
It sure looks like this is a problem with the headset.
But I also noticed a preponderance of SG4 owners complaining about a somewhat similar issue where the mic would suddenly turn off on their phone, mid call. Seems WIFI signals would somehow interfere with it (I tried turning off WIFI though and that didn't fix it).
Is there anything else I can do to diagnose this better and maybe get to the bottom of it?
What could be happening here? Is this the headset not playing well with the OS? Is there a way to tell?
Why would this start happening off a sudden two weeks after I'd been using it heavily with no problems?
Also, I'm trying to find more instances of this issue online but it's tough one to Google.
(As a side note, LG doesn't seem to be a very good company when it comes to customer service. I saw several instances on Android Central where their customers reported issues with the headset and then were told their posting violated the TOS of the forum. WTF is up with that? Have they not realized there is ths thing called the Internet? Do they think people won't eventually catch on? )
I'm seriously considering returning this thing, but the truth is, I really want to keep it if I can get it to work. Probably a pipe dream though, now that I've written all this out. lol
I'm even considering rooting my SG4 and throwing another ROM on to see if that fixes it. That's how much I like the headset.
Happy to receive any feedback from fellow forum members. Thanks in advance.
PS: Just realized I haven't really tried just unpairing and re-pairing more than once so I'm going to test that some more over next few days meanwhile...

I am having the same problem but with different headset (MOW and Jabra).
One thing that I tied worked but I can only use my headset to listen to music. In each headset setting located in the Bluetooth pairing list, I uncheck the CALL AUDIO and leave the MEDIA AUDIO check. This allows me to use my headset for music but not calls.
A complete fix would be great, please?

BT media audio works, phone audio fails
readable said:
I am having the same problem but with different headset (MOW and Jabra).
One thing that I tied worked but I can only use my headset to listen to music. In each headset setting located in the Bluetooth pairing list, I uncheck the CALL AUDIO and leave the MEDIA AUDIO check. This allows me to use my headset for music but not calls.
A complete fix would be great, please?
Click to expand...
Click to collapse
Glad you posted this because I hadn't even thought to try, as part of my troubleshooting, whether I could still play media on the phone through the headset when call audio was not coming through.
Last night I made a couple of calls just fine with my LG Tone Ultra (upgraded to see if this fixed the problem, but no change) and then made a third one. On this third one I could not hear any sound but the call connected (it was to my wife--she later told me she got a call but no sound on her end either).
So this is very strange. Somehow the BT headset is just dropping the call side of the audio.
And, it's doing so randomly.
Sure would like some more insight on what is likely the cause of this situation. I submitted a question to LG through their website but no response. That was days ago.

Chapter 2 of this problem
readable said:
I am having the same problem but with different headset (MOW and Jabra).
One thing that I tied worked but I can only use my headset to listen to music. In each headset setting located in the Bluetooth pairing list, I uncheck the CALL AUDIO and leave the MEDIA AUDIO check. This allows me to use my headset for music but not calls.
A complete fix would be great, please?
Click to expand...
Click to collapse
Just posted a new thread on this issue with some log data that I'm hoping a kindly dev may help decipher.
Letting you know in case you want to keep an eye on that thread as well.

[Q] LG G3 + gwatch: callers can't hear me speak over bluetooth when connected

Hi,
I realize this will sound like a strange issue, but I can reproduce it so it certainly exists.
I have an LG G3 running Android 4.4.2 on Verizon. I just bought it back in Jan '15, and the phone has been working great with no issues. I use my car's built in bluetooth connectivity to place and receive calls while driving and have had no issues doing so.
A few days ago (week of 3/9/15), I acquired a used LG G watch from a friend at work. It's in good shape; he only had it a few months, and it's working well. It connects to my phone, and I can use it to txt, place calls, etc. It's running software version 5.0.2.
I am experiencing an issue for which I cannot find the root cause. My issue is that, when I'm in my car, and both the car and the watch are connected to the phone via blue tooth, and I place or receive a call, folks on the other end cannot hear me speak. I tried it with my wife's cell phone, and can reproduce it every call. My voice is barely audible, yet bluetooth is connected to the car and I can hear the other person's voice just fine over my car speakers. As this is happening, if I pick up my phone and switch the call to the handset from bluetooth, the problem goes away and I can take the call on the handset. But as soon as I put it back to bluetooth, the problem returns. Once this happens, if I hang up and try to call the person back using either bluetooth OR the handset, the voice problem returns and I cannot be heard speaking. I tried putting my mouth up to the watch and the phone thinking maybe it was trying to use another microphone, but I still sounded muffled and far away while I was testing this with my wife's phone.
I have checked all my settings in Android Wear, my phone settings for volume as well as call settings...I cannot find anything obvious. I've googled the issue, but there is little to no information regarding this problem.
Can anyone suggest something to help fix this? I really like the G watch, and I would like to get it to work so I can enjoy it. You would think that the G3 and G watch would play nice since they are both LG!
Thanks for any help,
Nick

Having the same issue....sort of...
First, allow me to apologize for any improper formatting or if I've tendered my reply in the wrong way.
I've literally never replied on a message board in my life. Ugh, I know. How, right? Moving on...
I have an issue very similar to the one you're having, only in place of the car, put a Plantronics WalMart headset and change the G3 for it's predecessor. I notice that people call me when my watch is connected to my phone. When I answer, they claim to not be able to hear or understand what I am saying. The problem persists even if I disconnect my headset and use the G2 in either handset or speakerphone mode. The only fix I've found is to restart the phone and return the call. Even then, if the watch is still connected, only the first call can be completed with no "interference".
I've attempted to update the software and firmware to my G2, with no success. I have no idea why this issue occurs.
Also, is probably noteworthy that regardless of whatever Bluetooth device I am connected, very very often during a call, my caller's voice will shift into "speakerphone" mode without being instructed to do so. I have to open the call screen, turn off the BT, then select it again to turn it back on. The call returns to the headset, but doesn't stay there in most cases. Sometimes I have to do this 5 - 7 times a call. Other times, it remains connected as it's supposed to. Again, I can find no reason why this happens, but it's been an issue for MONTHS with my G2. And it doesn't matter what headset I am using, it just "drops" the sound to my speaker phone, but still says that it remains connected to the headset.
It's a Sprint LG G2, if that matters at all.
PrivateBytes said:
Hi,
I realize this will sound like a strange issue, but I can reproduce it so it certainly exists.
I have an LG G3 running Android 4.4.2 on Verizon. I just bought it back in Jan '15, and the phone has been working great with no issues. I use my car's built in bluetooth connectivity to place and receive calls while driving and have had no issues doing so.
A few days ago (week of 3/9/15), I acquired a used LG G watch from a friend at work. It's in good shape; he only had it a few months, and it's working well. It connects to my phone, and I can use it to txt, place calls, etc. It's running software version 5.0.2.
I am experiencing an issue for which I cannot find the root cause. My issue is that, when I'm in my car, and both the car and the watch are connected to the phone via blue tooth, and I place or receive a call, folks on the other end cannot hear me speak. I tried it with my wife's cell phone, and can reproduce it every call. My voice is barely audible, yet bluetooth is connected to the car and I can hear the other person's voice just fine over my car speakers. As this is happening, if I pick up my phone and switch the call to the handset from bluetooth, the problem goes away and I can take the call on the handset. But as soon as I put it back to bluetooth, the problem returns. Once this happens, if I hang up and try to call the person back using either bluetooth OR the handset, the voice problem returns and I cannot be heard speaking. I tried putting my mouth up to the watch and the phone thinking maybe it was trying to use another microphone, but I still sounded muffled and far away while I was testing this with my wife's phone.
I have checked all my settings in Android Wear, my phone settings for volume as well as call settings...I cannot find anything obvious. I've googled the issue, but there is little to no information regarding this problem.
Can anyone suggest something to help fix this? I really like the G watch, and I would like to get it to work so I can enjoy it. You would think that the G3 and G watch would play nice since they are both LG!
Thanks for any help,
Nick
Click to expand...
Click to collapse

Have you tried going into android settings for voice input and allowing recording using Bluetooth mic?