Has anyone had issues with bluetooth staying connected consistently through a call?
I'm new to the Epic about a week or so ago. My bluetooth connects fine and stays paired. But during the call I will lose caller for about 5-7 seconds and they eventually come back. But I will miss part of the conversation.
I've had people tell me they can hear me during the silence but I can't hear them. It seems to happen maybe every third of fourth call. I didn't know if anyone knew of an issue or fix to the problem.
Related
I just wanted to ask whether anyone else was having problems making calls. Sometimes when receiving or making calls I have the problem that the person on the other end is not able to hear me. I however can hear them perfectly and crystal clear. Is anyone else having this issue? The issue is usually resolved when I redial, but it's pretty annoying at times.
I'm on Vodafone UK.
The first call I made this happened to me, I think my head pressed against something to place the call on hold. The only indication you get that the call is held is a little pause icon in the task bar.
I've had this a number of times when the Hero has been connected to my Bluetooth car kit.
Even once its disconnected, I dial out and the caller hears me but I do not hear their ring tone or voice.
Turning Bluetooth off and then on again seems to cure it.
Random, does not happen all the time.
The Hero will also think its still connected to the car kit even after the car is turned off and I'm a long long way from it.
Same cure as above releases the 'connection'.
I've also noticed I get a pop up that says 'Bluetooth Headset Disconnected' when it was not or had not been connected for a long time.
Seems confused.
Hello, does anyone experience this? You call someone and then it doesnt ring.. I tried like 3 people and it does the same thing.. eventually it disconnects...
this happens to me sometimes, eventually the other person on the line will hang up because im still thinking its trying to connect. i usually put it on speaker so i hear the ringing then turn it right back off. but yes, i do have this issue.
yes i have this issue with CM5b3....if you set it to speaker then back to regular it will work, im not sure if this is a CM issue or just a n1 issue....i also noticed it happens mainly when the call previous was on speaker phone when the call ended, seems to be a problem in the sound routing subsystem
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?
Hello,
I have not seen a thread on this nor has Google searches helped but I have an issue I wanted to post to see if anyone else was having the issue.
I use my phone for work and often have it on speaker phone, out of no where the call goes quite and the person on the other end of the call can not hear me anymore. Upon looking at the phone the speaker phone seems to get disabled and the call goes back to the handset. This happens often when using the speakerphone but certain calls are worse then others.
In one call I had the speaker phone get disabled about 10 times which was close to every 30 seconds or so. This is very very annoying, I have also rebooted the phone. At this time I am not modded and have less then ten apps installed and I am pretty sure none of the apps I installed are causing the issue.
I will note that I do have the phone connected to bluetooth a lot and when the issue happened I tried to disable the bluetooth while on the call but the issue persisted.
Is anyone else experiencing this issue?
Speaker phone and Bluetooth turning off at random
I am having the exact same problem. But for me this happens with Bluetooth and speakerphone. This is getting really frustrating for me and potentially dangerous when I try to switch back to Bluetooth while driving.
Have you figured out a solution for this yet ?
Does anyone have this issue? When ever I am dialing out, there are times it seems like the call is going through, but I have to "end" the call so the call initiates... Its odd, but generally after that my calls are fine. Doesn't matter if its through Bluetooth, wifi calling, or regular calls through the phone itself.
How can I fix this if there is a fix? Running latest OTA, NMJ51B via Sprint.
~~Tito~~ said:
Does anyone have this issue? When ever I am dialing out, there are times it seems like the call is going through, but I have to "end" the call so the call initiates... Its odd, but generally after that my calls are fine. Doesn't matter if its through Bluetooth, wifi calling, or regular calls through the phone itself.
How can I fix this if there is a fix? Running latest OTA, NMJ51B via Sprint.
Click to expand...
Click to collapse
I've had this happen across a couple of phones with the Google Dialer... And actually with a Samsung just before I got my PH-1...
Happens every day to me
~~Tito~~ said:
Does anyone have this issue? When ever I am dialing out, there are times it seems like the call is going through, but I have to "end" the call so the call initiates... Its odd, but generally after that my calls are fine. Doesn't matter if its through Bluetooth, wifi calling, or regular calls through the phone itself.
How can I fix this if there is a fix? Running latest OTA, NMJ51B via Sprint.
Click to expand...
Click to collapse
Nope
I've had happen several times where after dialing (regular phone app) and it shows the call "connected", it takes about 5 to 10 seconds or so before there is any audio. Once the other end had already answered before the audio comes on, but usually I hear the ringing after the delay. Doesn't happen all the time. I don't make many phone calls out.
I usually see the app hang at the end of the call. Not all the time about once every day or two.