Related
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.
Just wondering if anyone else is having this issue. Whenever I have my Voyage Edge connected to my phone, if I go to enter text on a page using Google Voice Typing the microphone appears but then just hangs. If I disconnect the headset and press the mic on the keyboard again, the icon appears and starts taking my voice input.
Any ideas?
Note: This is on 4.4.2 (stock rooted)
Same thing here but I thought my trigger was that it was in my car dock (but to be fair, putting mine in the dock activates and connects my bluetooth).
Sometimes the first voice input (can be dialer, search, google now etc) will work, then any other attempt just hangs. Undocking allows me to do it but kind of defeats the point.
Hopefully someone can fix this one. I hate when updates take conveniences away (like the audio through usb dock cable issue that seemed to last forever).
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 have 2010 Chevy Cobalt and I tried to take two phone calls on my drive to work today via in car bluetooth. Both times at some point during the call audio stuttered for a few moments and then the GM bluetooth was disconnected. The call switched to handset speaker (not speakerphone).
I just got the phone Friday and it paired fine with my car, but this was the first time I had received any calls. The first call was the longer of the two and I heard it stutter but then thought maybe the person on the other end hung up, but I could still hear him very faintly. I grabbed the handset and finished the call. A few minutes later the phone rang again and I answered it but it was a spam caller about a car warranty so I cut her off and said I wasn't interested and right as I was about to hang up it started stuttering. I hit the hang up button on my steering wheel and the car bluetooth said "call ended" but I think it disconnected from BT before it actually sent the hang up command because the call sat there for a few moments before it ended when she hung up.
It was connected to an A2DP device for streaming music that worked fine before and after the calls (Spotify stopped when the calls came in and resumed after they were done), but I did notice that my Fitbit wasn't syncing today while I was at work so I rebooted the phone and the Fitbit and it synced fine. I will probably try making another phone call tonight on my way home to see if rebooting fixed it.
Lastly I saw that there were two new factory images posted today for the 6p (MDB08L, MDB08M). There is a mention of bluetooth in the security bulletin, so maybe it will help?
Thanks for any advice anyone can provide.
Could be your stereo. I've got a 2014 caravan and the Bluetooth in it sucks. I have no issues pairing, calls, music etc on my Kenwood deck in my other car. I would think about upgrading to an after market deck.
Sent from my Nexus 6P using Tapatalk
It seemed to work OK for an outgoing call last night on my way home with no changes, other than rebooting. I didn't get a chance to flash the new factory image last night because I got home too late, but I'll be doing it tonight. Might have just needed a reboot or something.
having issues with this phone and my 2015 camaro. streaming music skips no matter how good or poor signal. Even streaming internal memory music skips.
Ian B
Whenever I connect to one of my Bluetooth devices it shows that it's "Connected to xxxxx" in the secondary screen.
However, after I disconnect from the Bluetooth device it still says its connected in the secondary screen and the secondary screen just hangs there frozen saying its connected. I can only get rid of it by restarting the device.
Anyone else having this issue?
I'm experiencing this issue. I think it started happening after applying the latest update.
to fix it w/o restarting the device, you can go to settings - display - second screen and turn off 'show when main screen on' and back on.
I have this and all kinds of BT issues with my car.
Bluetooth has given me a lot of problems. Secondary screen stuck displaying the "connected" message, Bluetooth crashing, and high CPU usage when not connected. I've had better experience by toggling Bluetooth off and on with Tasker after disconnecting from my car. Figure it gives it a kick causing it to play nice.
McNutnut said:
Bluetooth has given me a lot of problems. Secondary screen stuck displaying the "connected" message, Bluetooth crashing, and high CPU usage when not connected. I've had better experience by toggling Bluetooth off and on with Tasker after disconnecting from my car. Figure it gives it a kick causing it to play nice.
Click to expand...
Click to collapse
So it's not just me having bluetooth issues lately. I was getting ready to drop by AT&T because of all the problems it''s been giving me lately connecting to things on bluetooth...
Mine has recently started doing the same thing with second screen stuck on connected to vehicle Bluetooth. I do remember updating recently so I am unsure what cause this issue. I am using stock with ATT
peekeesh said:
to fix it w/o restarting the device, you can go to settings - display - second screen and turn off 'show when main screen on' and back on.
Click to expand...
Click to collapse
I tried this trick and it only works temporarily. After an hour or so the same connection message will appear even though I'm not connected. So annoying. Come on LG! I like their devices but there is always some annoying issues with their phones.
Are you guys also experiencing general notification issues?
Example, I click on a Twitter or Kijiji notification and the app won't open or I can't respond within the notification shade any more.
See https://forum.xda-developers.com/showpost.php?p=72734315&postcount=10
I'm wondering if this is the cause of everyone else's bluetooth/notification issues. Worth a shot.
Ever since I upgraded to 10K from 10J on T-Mobile it has started doing this. Once I am connected I never have a problem with Bluetooth but connecting has been inconsistent ever since upgrading. My car stereo for example used to connect automatically now to get it to reconnect I have to turn off the stereo and the Bluetooth radio on my phone and then both back on @ same time otherwise I have to manually connect through the phone BT menu
Been having issues with bluetooth too. I've gotten into the habit of just turning it off after I get out of the car, then turning it on right before I get back in the car. If I leave it on all the time it fails to connect about half the time I turn on the car, if not more. Strangely I don't have the same issue with my Anker speakers, so I sort of assumed the car was the problem, but it seems not from these comments
McNutnut said:
See https://forum.xda-developers.com/showpost.php?p=72734315&postcount=10
I'm wondering if this is the cause of everyone else's bluetooth/notification issues. Worth a shot.
Click to expand...
Click to collapse
This seems to have fixed it for me! I had the same issue after updating my phone to the latest build.
thisisjason said:
Been having issues with bluetooth too. I've gotten into the habit of just turning it off after I get out of the car, then turning it on right before I get back in the car. If I leave it on all the time it fails to connect about half the time I turn on the car, if not more. Strangely I don't have the same issue with my Anker speakers, so I sort of assumed the car was the problem, but it seems not from these comments
Click to expand...
Click to collapse
Same exact issue. It only seems to happen to my car stereo since I upgraded to 10K. But my other speakers and headsets 99% of the time it will connect by itself.
Same issue here. Super annoying. Appears to have shown up around the same time that all my notifications stopped working.
I've been having the same issue. I use Car Home Ultra, and noticed that it was very delayed starting, and would start randomly even after leaving my car/disconnecting bluetooth. I thought it was a problem with that app, but now it appears it's that the phone is delayed in notifying of bluetooth connect/disconnect.
I constantly have the "connected" notification taking up the second screen until I reboot.
I am experiencing this aswell, and , when connecting to my SYNC 3 in my Ford Focus, it says connected, but it isn't. If someone rings me, the hand set rings.
It seems to be the initial handshake, if the phone's bluetooth is off when i turn car on, then i turn blutooth on and select "sync 3" it's all good, but if bluetooth is already on , and i switch car on , i get the message on the radio it's connected to my phone... but i cant access contacts or messages ( even though they are ticked in bluetooth menu )...
lucky for the 2 year warranty...
Disabling the Google app has fixed this issue and fixed my push notifications. Not ideal but doesn't appear any other answer exists.
Anybody have any updates on this issue? I have been having the connected message showing more frequently to my vehicles. I have been turning off second display and back on to remove. Thanks for the suggestion Adam about disabling Google app but like you said it is not ideal.
So on Verizon they just pushed a system update. Post update, I enabled Google app, and everything appears to be working great thus far.
I don't remember when but the issue just kind of went away without any action on my part. Maybe it was an update?