Related
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?
I had an issue with my LG G2 where people can't hear me when I call them. If I turn on speakerphone, they can usually hear me then. So I exchanged my G2 for a new one. Same problem now. About every 5th call or so, people can't hear me. It's driving me nuts. Could there be some software that's messing things up? I have google voice installed, and while most of the calls in question are GV calls, not all of them are. Just called someone now from my regular number and they couldn't hear me. Anyone have any tips or even advice on how I can tackle this?
Running latest Android updates and apps always, no root. Verizon. Calls placed from random locations (and even different states).
I am having the same issue. There are a couple of things I have tried. The most promising is to turn off Google hotword detection on every screen.
You can also try turning off the Privacy Keeper and Voice Enhancement in Call Settings. If any of this works for you, or you find and answer, let me know!
eepyikes said:
I had an issue with my LG G2 where people can't hear me when I call them. If I turn on speakerphone, they can usually hear me then. So I exchanged my G2 for a new one. Same problem now. About every 5th call or so, people can't hear me. It's driving me nuts. Could there be some software that's messing things up? I have google voice installed, and while most of the calls in question are GV calls, not all of them are. Just called someone now from my regular number and they couldn't hear me. Anyone have any tips or even advice on how I can tackle this?
Running latest Android updates and apps always, no root. Verizon. Calls placed from random locations (and even different states).
Click to expand...
Click to collapse
Having the same issue with 2 lines, same LG G2 phone. Called Verizon, was told it sounds like a hardware issue. I'm thinking it's something to do with their Android update personally.
Had exact same issue and took phone to repair center. They said it was mic issue. They ended up replacing the entire phone but guess what - issue is still there on new phone.
Sent from my LG-D802
I've seen this issue on many forums and with the number of people that are having the problem, it has to be either LG flaw or a software issue. I'm trying turning off the ok google, noise cancellation, and privacy keeper. But I'm pretty sure I tried those on the last phone with the same results.
Just to make sure we're all having the same issue, you can be heard once you turn on speakerphone, correct?
Update on this: Still having the issue after disabling ok google hotword..
eepyikes said:
Just to make sure we're all having the same issue, you can be heard once you turn on speakerphone, correct?
Click to expand...
Click to collapse
I read your reply some time ago but didn't answer because I had no answer.
Today the bug appeared again so I turned on speakerphone like you said. Guess what, they could then hear me!
Thanks for the tip @eepyikes, its a good workaround but lets hope for a proper solution.
Sent from my LG-D802
Any of you with this issue also have a Pebble or other type of smart watch?
I've noticed the same problem but the issue goes away when my Pebble isn't actively paired.
cahiatt said:
Any of you with this issue also have a Pebble or other type of smart watch?
I've noticed the same problem but the issue goes away when my Pebble isn't actively paired.
Click to expand...
Click to collapse
-Correction- I hadn't had this issue since I disconnected my Pebble about 10 days back. It came back today when I made a call. What I noticed today is.......
When I switched to the speakerphone the person still couldn't hear me very well. Switching back to mic the problem is still there. But when I turned on my BT headset the audio was fine. Switching back to the phone mic from the BT the problem cleared up.
Did a test call initiating the call on the BT headset and had the same audio problem through BT. Switching back to the phone mic or speakerphone cleared it up.
Initiated another call on the speakerphone. Same audio problem. Switched to BT and it cleared up again. Switched back to the phone mic and it was still fine.
Seems the issue is there when initiating the call on BT, mic or speakerphone but switching from BT to the phone or phone to BT clears it up. I'm on a D801 (TMO) and first noticed this about three weeks back.
Rebooting the phone seemed to clear it up at least for the short term. I just noticed that the Google search app updated on the phone about two/three weeks back. Seems about the same time I started noticing the issue.
I had a backup of Google search 4.1.29 from back in January. Just restored that version and blocked it from updating to see if the issue comes back again.
Interesting to see this is also on the d802. Mine is the VS980.
The 13qcelp trick does not fix it. So tired of this!
Any other tricks out there??
Happened twice in one day. New record for me. Sick of people saying "hello?? Anyone there??? Hello??" until i turn speakers on. With speakers sound is horrible so really annoying! Wonder if issue will happen with AOSP/CM roms.....
Sent from my LG-D802
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.
Not sure why but after the last system update the phone will only come out of black screen sleep mode if I use the fingerprint sensor when theres an incoming call.
Any Ideas ?
This happened to me today too.
Hello, me too! Oreo Beta 2
Anyone ?
going_home said:
Anyone ?
Click to expand...
Click to collapse
Not me, I've never experienced this issue since I got the phone from N then updated to OB2, and now OB3.
Sounds like the proximity sensor may have an issue.
Do you have a screen protector or case?
I don't have that issue with a screen protector and Tudia case and B3.
It's a bug in the latest Google Dialer app. I fixed it be deinstalling the new version/updates then clearing cache and data in the dialer app. It's affecting the Pixel2 XL running 8.1 also. Fixed my issue and I won't let it install the newer dialer version from the play store
In Beta 3, I haven't experienced that problem. I did heavily on 7.1.1
Just got another update and still having black screen on incoming calls....
I'm about ready to ditch this phone and get a Pixel 2 XL.
I read where Essential is skipping the 8.0 update because of instability and going straight to 8.1.
going_home said:
Just got another update and still having black screen on incoming calls....
I'm about ready to ditch this phone and get a Pixel 2 XL.
I read where Essential is skipping the 8.0 update because of instability and going straight to 8.1.
Click to expand...
Click to collapse
happened to me last week too.. it only happened after I locked the phone, 5-10 minutes later incoming call or when unlocking the phone the phone shows back screen only for a few seconds then it went back to normal.
the problem went away after I turned off the bluetooth radio.
I've been having this issue for a while now and just today I figured out the cause. At least the cause of my specific issue. I came here to see if anyone else is having similar issues so I'll explain exactly where I'm at.
If a Bluetooth headset is connected to my phone, when a call comes in the screen stays black and I can't see who's calling. If I turn off, or disconnect the BT device, when a call comes in the screen lights up with caller ID like normal. This also affects the missed call notification that happens after a missed call. With a BT device connected, the missed call notification will not show until I wake the phone with the power button, though the notification LED will light.
I'm on stock 7.1.1 and I verified that this is also an identical issue with two other phones which were not on a stock ROM, though I can't remember what they were running. This started happening to me before the NMK24B update. I remember because I was hoping that the update would fix it. I believe it started with NMJ88C because I got my phone on NMJ32F, it updated to NMJ51B shortly after and it was fine in the beginning months.
DrvLikHell said:
I've been having this issue for a while now and just today I figured out the cause. At least the cause of my specific issue. I came here to see if anyone else is having similar issues so I'll explain exactly where I'm at.
If a Bluetooth headset is connected to my phone, when a call comes in the screen stays black and I can't see who's calling. If I turn off, or disconnect the BT device, when a call comes in the screen lights up with caller ID like normal. This also affects the missed call notification that happens after a missed call. With a BT device connected, the missed call notification will not show until I wake the phone with the power button, though the notification LED will light.
I'm on stock 7.1.1 and I verified that this is also an identical issue with two other phones which were not on a stock ROM, though I can't remember what they were running. This started happening to me before the NMK24B update. I remember because I was hoping that the update would fix it. I believe it started with NMJ88C because I got my phone on NMJ32F, it updated to NMJ51B shortly after and it was fine in the beginning months.
Click to expand...
Click to collapse
I had the black screen issue as well for incoming calls. I just switched to Drupe Dialer from the Play Store and set that as my default dialer. Now my screen lights up with the incoming caller ID and works as it should. By the way, hate to sound like an add, but Drupe Dialer is just awesome and has a ton of functionality, give it a shot. I know that's not the perfect answer as we would expect the native Android dialer to work out of the box with our OS, but it is what it is.
Jank4AU said:
I had the black screen issue as well for incoming calls. I just switched to Drupe Dialer from the Play Store and set that as my default dialer. Now my screen lights up with the incoming caller ID and works as it should. By the way, hate to sound like an add, but Drupe Dialer is just awesome and has a ton of functionality, give it a shot. I know that's not the perfect answer as we would expect the native Android dialer to work out of the box with our OS, but it is what it is.
Click to expand...
Click to collapse
I tried two other dialers and it didn't make a difference on my phone. Drupe did work to make the screen show who's calling again, but wow, Drupe has too much.... just, everything. All I want in a dialer is basic functions in a standard format. Drupe is like a carnival of a dialer. I'll keep trying dialers though, since that one did work, maybe another one will too. Thanks for the suggestion.
Yeah, if you just take the Drupe dialer phone icon and put that on your home screen, whenever you select it you'll go right to the normal looking dialer. :good:You may want to try ExDialer. That used to be one I'd use a lot.
Jank4AU said:
I had the black screen issue as well for incoming calls. I just switched to Drupe Dialer from the Play Store and set that as my default dialer. Now my screen lights up with the incoming caller ID and works as it should. By the way, hate to sound like an add, but Drupe Dialer is just awesome and has a ton of functionality, give it a shot. I know that's not the perfect answer as we would expect the native Android dialer to work out of the box with our OS, but it is what it is.
Click to expand...
Click to collapse
Before using Drupe...
There should be a warning that goes out to all your contacts saying "I'm about to completely betray you and share EVERYTHING about you online with a company I know nothing about... Please enjoy these spam calls on me"
Sent from my PH-1 using Tapatalk
rignfool said:
Before using Drupe...
There should be a warning that goes out to all your contacts saying "I'm about to completely betray you and share EVERYTHING about you online with a company I know nothing about... Please enjoy these spam calls on me"
Click to expand...
Click to collapse
10 million downloads...good enough for me. I've used it for a long time and it's been better for me than the stock dialer. Just my opinion, no one has to use it but it sure beats a black screen when the phone rings.
I have the same problem on the pixel 2 xl. And so do lots of others. I uninstalled the phone update from the play store, and turned off auto update. So far so good. And I am on 8.1 But we will see. And it only happens when I'm on Bluetooth. Unfortunately I use it all the time for work
Sent from my Pixel 2 XL using Tapatalk
I read about some people being able to fix it by uninstalling dialer updates. Unfortunately, the Essential doesn't have any to uninstall. I'm working around it by using Drupe as my default dialer, but setting the stock dialer as the default app for dialing, if that makes any sense (When an event pops up that requires the dialer, it asks which dialer to use, I selected the stock dialer and told it always use that.) This way incoming calls trigger Drupe, which acts the way it's supposed to on Bluetooth, but I can still use the stock app for making calls and missed calls and such.
bricky23 said:
I have the same problem on the pixel 2 xl. And so do lots of others. I uninstalled the phone update from the play store, and turned off auto update. So far so good. And I am on 8.1 But we will see. And it only happens when I'm on Bluetooth. Unfortunately I use it all the time for work
Click to expand...
Click to collapse
Yeah, I'm thinking there's a Bluetooth issue (yeah,I know, news flash). But it's been widely reported that some folks are having trouble connecting to their cars Bluetooth. I use a Bluetooth adapter in my car and wireless headphones in the office. No real big issues connecting, but it can be finicky. However, once an event triggers Bluetooth, like streaming a song with Google Play to the adapter, my phones volume buttons become unresponsive. I can only change volume by going into the settings menu or from the Bluetooth device. Sucks. Waiting for the 8.1 beta to do a total clean install. Just bought the device used from Swappa and it came with beta 3 installed, not 100% sure the steps it took getting here. I guess what I'm asking is, does anyone else experience issues with their volume buttons not working occasionally?
Jank4AU said:
Yeah, I'm thinking there's a Bluetooth issue (yeah,I know, news flash). But it's been widely reported that some folks are having trouble connecting to their cars Bluetooth. I use a Bluetooth adapter in my car and wireless headphones in the office. No real big issues connecting, but it can be finicky. However, once an event triggers Bluetooth, like streaming a song with Google Play to the adapter, my phones volume buttons become unresponsive. I can only change volume by going into the settings menu or from the Bluetooth device. Sucks. Waiting for the 8.1 beta to do a total clean install. Just bought the device used from Swappa and it came with beta 3 installed, not 100% sure the steps it took getting here. I guess what I'm asking is, does anyone else experience issues with their volume buttons not working occasionally?
Click to expand...
Click to collapse
My volume buttons always work fine, BT or otherwise. Stock 7.1.1. Your issue could very well be related to OB3. I had a little bit of an issue connecting/reconnecting to some BT devices at first, but not lately, so it must have been fixed in the last few patches.