[Q] Very specific problem with voice dialing from bluetooth headsets - Galaxy S 4 Q&A, Help & Troubleshooting

Hi everyone,
First off, I'd like to start by wishing to everyone happy Holidays!
I have been literally searching all over the Internet for any information regarding the issue I am about to describe in detail and since no solutiuon was found, there's nothing left for me to do but ask for help, and hopefully get the right answer. That's why I want to be as specific and informative as I can.
The problem I am having is this; I recently purchased a new Jabra Motion bluetooth headset and decided to start using the voice dialing function on my Galaxy S4, since it works very well (when it works) and is really a breeze, especially while driving.
In short, the problem is that the S4 completely loses audio (other party hears nothing as well) after initiating a call, via voice dial commands through any bluetooth headset (I'll get to that). When that happens, the phone has no in-call audio whatsoever (with headset on or off, with speakerphone or earpiece on), no matter how many times I start or receive a call and nothing brings audio back, except a reboot from the i9505's power button menu. All other audio works, like videos, unlock sounds, ringtone, music, even the little chirp right before the other party's phone starts ringing and the hangup chirp can also be heard. The worst part is, that it occurs completely at random, it can happen on the 1st time I voice dial or the 10th time, for example. The problem has not shown itself, when initiating a call normally or picking up with a headset connected, before audio gets lost.
Before purchasing the Jabra Motion I've been using an earliest model Jawbone Icon and had never even tried the voice dialing feature on any previous phones or the S4. After encountering this problem I tried to test whether or not it would happen when using that headset, the result was yes, so it is safe to say it will happen when using any bluetooth headset, with the same randomness.
This is what both headsets launch on the phone, when attempting to voice dial:
View attachment 2474439
The phone itself is a completely stock and un-rooted 16GB Galaxy S4 i9505, running the latest available Jelly Bean 4.3, build: XXUEMJ7.
The headsets are always connected to 2 devices simultaneously (in case that might shed some light)
What I've tried so far (no difference made, at all):
- Toggled bluetooth off and on
- Tried unpairing and re-pairing both headsets on both phones, or only on i9505
- Tried factory resetting both headsets
- Tried to toggle, while in call, between speakerphone, earpiece, headset, turning off headset and all possible combinations
- Removed Jabra companion app and services app, then reinstalled, then tried without the apps installed.
- Cleared cache from both Jabra apps.
- Cleared cache from system apps such as dialer, bluetooth and Google Search.
- Contacted support of both Samsung and Jabra (huge waste of time)
Sorry for the very long post, but I want to be clear and comprehensive as possible. Any help would be highly appreciated.
Please no factory reset suggestions, I am aware of that possibility, but do not want to go through all the trouble to set up tons of apps and stuff again.
Thanks in advance to anyone willing to help!

Anyone?

Please?

Related

Bluetooth settings for handsfree - without incoming call delay

Hey folks,
I've been struggling with this issue for months now and couldn't find a solution yet. Had the same problem with my Polaris before.
When using BT Handsfree profile, either with my Jabra 250 headset or with my built in car handsfree (Parrot) I get a more or less big delay after accepting a call until the audio stream is transferred from my phone to the BT device.
Meaning, accepting the call in the car results in like 5 seconds delay until I can actually hear what the person on the other end is saying. Until then the voice is still routed via the phones builtin speaker, as if no BT device would be connected.
Same happens with my Jabra headset, though the delay is less there. Maybe 2-3 seconds sometimes.
I tried playing around with Shaps Advanced Config or HD Tweak Bluetooth settings, but no luck so far :-(
Could anyone who is using BT handsfree devices, especially car kits, tell me if you get your audio on your BT device right away, without delay on your BT device? If yes, please tell me exactly what settings you are using for your BT on the phone, e.g. Bitpool min/max, Audio Gateway on/off, Joint Stereo Yes/No etc.
Please let me know if ya using S2U2 as well, I think this could add up to the problem, though for me I still have the issues when I disable S2U2
thanks,
boba
i am using a Bury comfort BT and it rings 2-3 seconds b e f o r e my phone rings! i did not tweaked any settings in my HD. i am not using s2u2.
I also have a Parrot in car hands-free system. Have to say, whilst there are and have been some 'issues' (from time to time) a long delay when an incoming call is accepted isn't one I get.
I don't have the 2 programs you mentioned, as I'd not heard of them before - so I'm running my HD (as far as BT goes at least) in stock trim - FYI I have the auto-answer selected (in 'Settings>Phone>More') set to talk after 4 rings, as a personal pref.
I do have issues with the BT on these phones - I think it's a WinMo thing though, as it's been the same on all the WinMo phones I've had - the BT is pretty retarded unfortunately and it's the one major gripe I have with it and ultimately 'put up with' (very begrudgingly, as it's a feature I use a lot)
Issues are;
Occasionally the phone will answer instead of the car kit (if it's in my pocket - although I may have solved that by having pocketshield 'slide to answer' on there now)
It will NOT auto-answer at all on my BT stereo headphones NOR [more annoyingly] my Scala-Rider motorcycle helmet kit (where every other 'normal' phone I have had has done so with no issues at all)
Every now and again it will freeze the car-kit by showing that there is an active call, when there isn't - and the only way out of it is a soft reset of the HD itself
I only wish there was a fix/tweak for the BT in WinMo - but it seems that most programmers don't see this as a priority area and as such it's not been resolved - maybe 6.5 will address it...but I'm not holding my breath!
Hello, same problem with my Motorola bt350, with and without s2u2.
Same with stock ROM or with dutty's ROM and other.
Its a known win 6.1 BT stack issue.
Regards
T
@ boba23
If you find a fix for that issue please tell me!!! its so annoying
T
Same issues here. Anyone find a fix.
thought it was mine in car blue tooth that has this problem...good (or bad?) to know that it's not an isolated incident.
same issue...
I have parrot MK9000 and HTC BH S100 (stereo). The delay is the same. I do not think there is going to be a solution.
Ι have the transfer delay BT issue here too.... the others person voice is going out from the phone for 2-5 sec and suddenly its transferred to BT heasedet.
Preety annoying, it happens to all my ΒΤ headssets (Jabra , Samsung) the dead seconds just varies.
Plz guys anyone who has solved this let me know
boba23 said:
Bumping this thread up again, since I am still facing the delay issue. I am pretty sure it's not ROM related, since I had this issue with all 6.1 roms I tried. Right now using Topix 2.7.
Played around with Advanced Config BT settings again, but I still have that incoming call delay with my Jabbra BT250. Mostly takes 3-4 seconds, after accepting an incoming call till I hear sound on my headset. I really can't believe that this is an issue that only a few ppl are facing. I have nothing spectacular installed, even disabled S2U2 to see if that helps, but nothing :-(
boba
Click to expand...
Click to collapse
I think this has to do with a combination hands-free / rom version. I have a built in car kit and if I accept the call with phone answer I get the voice right away on the car kit. If I accept it on the radio, it will take 2-4 seconds before sound is transferred to car kit.
I've made another test on a parrot car kit, with same ROM version as before, and it behavior was diferent. If I accept the call on the car kit button, the sound is transferred immediately to the car, if I accept the call on phone button, I get instant sound, but on the phone - private mode....
I made also this test with a plantronics headset, and the sound is transferred right away to the headset either I accept the call on the headset or the phone
so
I am using topix 2.9.4 6.1 rom version - but already tested with several 6.1 roms and 6.5 - behavior is more or less the same
boba23 said:
Bumping this thread up again, since I am still facing the delay issue. I am pretty sure it's not ROM related, since I had this issue with all 6.1 roms I tried. Right now using Topix 2.7.
Played around with Advanced Config BT settings again, but I still have that incoming call delay with my Jabbra BT250. Mostly takes 3-4 seconds, after accepting an incoming call till I hear sound on my headset. I really can't believe that this is an issue that only a few ppl are facing. I have nothing spectacular installed, even disabled S2U2 to see if that helps, but nothing :-(
boba
Click to expand...
Click to collapse
Hi Boba, you're not alone I use BT sometimes as a backup.. and I too have an annoying delay of several seconds... at that very moment I think "hey where's the incoming call", I then hear the sound from the normal phone speaker, and when I switch to the normal phone again the sound is passed to BT ....
Bluetooth Incoming Call Delay
Has anyone come across a solution for this yet?
I have always had a 1-2 second delay in being able to hear the caller using my BT250 headset but, after installing the Orange update ROM, the delay seems to have increased to 3-4 seconds. The caller can hear straight away though.
I have just purchased a BT2020 headset and the delay is still 3-4 seconds.
I am not confident in installing different ROMs (because of my limited knowledge) but would install any that will eradicte this really annoying delay. Any suggestions?
alanu said:
Has anyone come across a solution for this yet?
I have always had a 1-2 second delay in being able to hear the caller using my BT250 headset but, after installing the Orange update ROM, the delay seems to have increased to 3-4 seconds. The caller can hear straight away though.
I have just purchased a BT2020 headset and the delay is still 3-4 seconds.
I am not confident in installing different ROMs (because of my limited knowledge) but would install any that will eradicte this really annoying delay. Any suggestions?
Click to expand...
Click to collapse
Just spoke with Orange Technical Helpdesk and they are sending me a new handset.......will publish result.

[Q] No Sound During Calls

Randomly when I make calls or receive calls I have no sound. I can't hear them and they can't hear me. Rebooting the phone will fix the issue for a short while. I have been able to reproduce this by connecting to my cars blue tooth and making a call. The 1st call works however all calls after the first call I have no sound again. When the phone in the no sound state (Phone Call) Bluetooth media still works just no sound while in a call. The speakers work because I can play music and the mic still works because I can still record sound. This issue seams to be related to the phone app its self???
My phone is a Samsung S4 (AT&T) with Android 4.4.2 (Rooted via Towelroot) with SuperSU by chain-fire installed.
Here is some of the trouble shooting I have already done.
1. Factory Rest the Phone via Stock Recovery (Still can reproduce the issue)
2. Played around with various settings i.e. Google Now Bluetooth options. Un-paired all Bluetooth devices and then re-paired one to try (Still having same issue)
3. Cleaned out all app cache (Still having same issue)
4. Re-installed pre-installed apps that I removed once rooted.
Long story short, this one has be baffled. The only thing that fixes the issue is re-starting the phone.
Thanks in advance for any assistance
AG007
Same Problem Here, I may have figured it out:
After I rooted I used some apps to auto kill some running, supposedly non-essential apps. This caused my phone call problems, same exact issue as you're having. A reboot fixed it for me as well. I will let you know if it happens again without closing any apps.......

[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?

Answering calls via bluetooth issue.

I have a converted T-Mobile OP6T running the latest 9.0.12 OOS.
Whenever I receive a call and have a Bluetooth device connected, either my Jaybird headphones or my car stereo, It's very hit or miss on whether or not I'll be able to answer it with the Bluetooth device.
If I receive a call, it will ring and I'll try to answer it with the button on my earbuds, and I'll get nothing. Sometimes I can pick up my phone and they'll be on the earpiece, other times I can't hear them at all. I have to hang up and call them back. This is the same with my car stereo.
I did not have this problem BEFORE I did a factory wipe last week, which seems odd.
Hopefully, someone has a solution to this, as it pisses me off daily.
Does anyone have any thoughts on this?
I've forgotten and re-added both Bluetooth devices multiple times with the same outcome.
Well, I was hoping someone had some input on this, as it's aggravating me daily. Maybe I'll try another wipe without restoring anything.
Same issue
Krunk_Kracker said:
Well, I was hoping someone had some input on this, as it's aggravating me daily. Maybe I'll try another wipe without restoring anything.
Click to expand...
Click to collapse
I have the same issue. When I have the phone connected to my car stereo bluetooth, I can make outgoing calls via bluetooth just fine, but when I answer the call, it goes to my earpiece. I have to manually switch it back to bluetooth.
I haven't found a solution yet and the issue has plagued me across multiple versions of OxygenOS. When I had the 6T on ASOP, the behavior stopped, so I know this is an OxygenOS issue and not a general Android issue. OnePlus must have the stack messed up.
Since my phone is rooted, I'll take a look at the bluez settings and see if I find something there.
Mine is 100% stock, does the same thing. Plantronics 5200 headset. If the headset is off, phone rings, turn it on, put it on, auto answers fine.
If the headset is turned on, on my ear, hit or miss it will answer, or default to my phone or watch, forcing me to hit the button to switch it to
the headset.

Categories

Resources