running android 5 and disabling the settings noted above didn't really help 
do you have any other ideas?
do you have any other ideas?
No Sound on Phone Calls after using Bluetooth
- Thread starter Rirruto
- Start date
Try disabling Google Now's "OK Google" Detection 'From any screen'.
Open Google Now
Go to Settings
Select 'Voice'
Select '"OK Google" Detection'
Turn off 'From any screen'
Restart Phone
Hope this helps!
Open Google Now
Go to Settings
Select 'Voice'
Select '"OK Google" Detection'
Turn off 'From any screen'
Restart Phone
Hope this helps!
Thank you very much Rirruto, you made it! This issue was bugging me for so long I can't remember when. I even did a factory reset because of it, and finally gave up using my earpiece. But now that I've purchased a Gear S, I had to look it through. This post made it.
Well, I really loved the "OK Google" command I often used it. I'll have to get used to my Gear S's S Voice then. I can only hope Lollipop solves it.
Well, I really loved the "OK Google" command I often used it. I'll have to get used to my Gear S's S Voice then. I can only hope Lollipop solves it.
Still very frustrated. I continue to have this problem resurrect itself. A week ago I did a fully hard factory reset...cleared everything! And reloaded most of my apps. No luck. I can't find any commonality among apps or settings that might be triggering this. oh well, as others have mentioned, maybe Lollipop will solve it, or a new phone this Fall...probably not a Samsung product :-(
So glad I found your post. I finally got a headset I like and was so eager to use it but kept running into this exact same problem. I called tech support, we did some diagnostics, even booted the phone up in safe mode and the issue persisted. The tech determined that the device was defective. I did the whole replacement process, had one good day with the new phone then it started all over again. On my own accord I did a factory reset and did a controlled install of all my apps, making calls to my wife's phone after each install. The problem started again so I uninstalled the last two apps loaded and the problem persisted... I forgot that I had also configured the "OK Google" in the time frame.
I've now disabled the "any screen" option and it's all working fine. I'm bummed like the others that I can't use my OK Google though. I'm going to be calling TMobile back seeking compensation for my $5 replacement fee and insist on more off my bill since they took me through this 3 ringed circus unnecessarily. If they don't want to compensate me I'll be turning it over to my "Legal Shield" law firm. Someone has to be held accountable.
I've now disabled the "any screen" option and it's all working fine. I'm bummed like the others that I can't use my OK Google though. I'm going to be calling TMobile back seeking compensation for my $5 replacement fee and insist on more off my bill since they took me through this 3 ringed circus unnecessarily. If they don't want to compensate me I'll be turning it over to my "Legal Shield" law firm. Someone has to be held accountable.
Thanks I had the same problem with Galaxy s4. Returned the phone. Verizon never heard of the issue. Hope disabling Google Anywhere works.
Thank you Thank you Thank you..................!! This was driving me crazy. After disabling the 'OK Google from any screen', the problem went away.
I feel whole again!
I feel whole again!
I'm like you Simmon. Thank you Thank you Thank you..................!! This was driving me crazy for months. I too have a Samsung phone and was frustrated because I couldn't hear my calls anytime bluetooth was on not just in the car. But music and everything else bluetooth works fine. I do remember setting up the 'OK Google from any screen', a while back ago so hopefully the problem will go away when I try that. Thank goodness I found this because they were just about to do a phone replacement!
Looking forward to feeling whole again!
Looking forward to feeling whole again!
Last edited:
Hi everyone,
Thank you for your efforts, and congratulations to all who have succeeded in eliminating this issue. Unfortunately for me, it is still a big problem. There's a lot to read here, but I'm trying to be thorough. Maybe some saint of a geek will take the time to read it all and we can help the world somehow, lol.
The history on this goes back just a little too far for me to provide great detail, and I honestly can't remember when/why it first started to happen. But it started on my old phone, a Galaxy S Blaze from T-Mobile. I can't remember if I was having this problem before I bought my 2013 Ford Focus or not. I'm beginning to suspect that this may be heavily involved. For whatever reason, the phone would intermittently have no sound (both ways) during calls. Once the phone got in that state, it didn't matter if I tried bluetooth, speakerphone, wired headset, nothing worked!
Whatever the case, it must have started quite a while after I first got the S Blaze, because I remember deciding to root it and go custom firmware (Cyanogenmod 10.1) to see if the problem would stop. I was considering doing the CM switch anyway, so this pushed me into it, rather than doing a bunch of other troubleshooting to find the root (pun intended!) of the issue. This makes me strain my brain to try and remember if there was any correlation between when the problem started and when I got the new car. Can't remember! All I know is, it wasn't ALWAYS a problem on that phone.
Bummer was after rooting the phone, installing CM10.1, getting my apps back on there and blah blah, problem didn't stop occuring. Again, it was rather intermittent (maybe once a week) and fairly easy to recover from (reset phone repeatedly until a call to voicemail works again). Since I don't do a lot of voice calls and the recovery wasn't too difficult, I decided to live with this little issue until I could afford a new phone... which ended up taking longer than I thought. By the way, I will never buy a non-flagship, carrier-exclusive device again! What a dumb move.
Finally out of frustration with the Blaze more than anything (battery life was real bad after 2.5 years, and it was starting to freeze OFTEN), I broke down and bought a refurbished Galaxy S4 LTE from the T-Mobile website last week, and it arrived preloaded with the newest 4.4.4 Kitkat firmware. I'm thinking, okay finally I'll have a perfectly working device again, after living with this buggy junker for so long. Don't know what was wrong with it, don't care, never looking back! I took great fun in smashing the worthless Blaze to bits Sunday night once my awesome new S4 was all set up and seemingly working flawlessly.
I just about cried the first time this same damn problem happened on my newly refurbished S4!
Now I'm really irritated. What could this problem be? across two devices, completely different firmware, what are the commonalities? I have googled this to the ends of the internet and tried everything under the sun on my new S4 (except haven't done a new firmware/ROM yet because it didn't help on the Blaze so I better try EVERYTHING else first this time). More on that below.
Sidenote: On the GS4 the problem is much more persistent. It first happened on Monday at work, and Monday night I got it working again by restarting the phone a bunch (maybe 7 or 8 times) with a test call to voicemail after each restart. It happened again at work today, and for the life of me I cannot get the thing working again now. Really bummed.
Here's what I have done with my brand new device leading up to the problem:
1) Installed my Sony 32GB SD card from my old phone as well as the new smaller-sized SIM card.
2) Activated the new SIM card online, and turned on the GS4 for the first time.
3) Set up my Google account for Gmail/Play Store, and set up the built-in email app with my Hotmail credentials.
4) Imported my contacts from the SD card.
5) Installed a bunch of stuff like Nova launcher, PDF reader, QuickPic, CapturePro, Torch, a fairly long list of other apps/utilities, etc (again, I thought this loss of sound was a unique problem with my old phone so I wasn't shy about putting all my favorite apps right back on the new device).
6) Tweaked the look and feel a bunch and configured the device to my liking, including disabling several of the included apps.
7) Paired with my 2013 Ford Focus and did some bluetooth calling on Sunday.
8) Took the phone to work Monday morning (this problem seems to always actually START while I'm at work. the first time it happened on this new device was on Monday, AT WORK. It is more or less just an observation, because I can't think of any sensible reason for this to be a problem. Is it because I just drove my car? Well I drive my car all the time, all over the NW).
Troubleshooting notes:
I don't use anything special with my phone at work, no company email or VPN or anything like that. It just rides in my pocket or sits on my desk connected to a charger all day, and doesn't even have data or wifi enabled (I rarely use/enable mobile data). I rarely make/receive a few texts or voice calls with it throughout the day. Could it be getting messed up by something at work because the bluetooth is left on, and then my phone gets somehow stuck in that state? I don't know what it could be, but the correlation is hard to ignore.
I have never used any kind of voice search, nor did I even have any of those previously mentioned apps (S Voice or Google Now) installed on my hacked Galaxy S Blaze. Further, Google Now was one of the the built-in apps that I disabled on the GS4 when I first set it up on Sunday (I simply don't use voice search/voice commands/speech to text, any of that).
I do not Bluetooth stream audio nor did I have the phone paired with anything else, just my car.
After reading a lot of info online I did the following to try and get the GS4 working again tonight so I can call my brother back:
1) Took out my SD card (and left it out) and rebooted. No fix (To truly eliminate this as a culprit, I left the SD card out through out all other steps below).
2) Uninstalled every app that I had added to the device, including any app updates, and restarted phone. No fix.
3) Triple-checked every setting! Touch sounds, noise reduction, extra volume, silent mode, call sound, voice control, voice search, wifi calling, bluetooth settings, network mode/settings, etc. No fix.
4) Unpaired the device from my car (also deleted the device from my car's memory/menu). No fix.
5) Did a hard reset (from powered off state, hold up volume + home key + power key for a few seconds to boot into recovery mode. navigate through the menu to factory reset the phone). No fix! Unbelievable! How can it still persist? Hardware problem maybe? No, i doubt it... because I had this problem on my old phone too, even after root and custom ROM install!! Same intermittent hardware issue on both devices? EXTREMELY unlikely!
6) From fresh factory reset, no SD card installed, no new apps installed, no bluetooth paired, I disabled every single app the device would let me disable (this DID include both S Voice and Google Now). No fix.
7) Even though Google Now was completely disable, I thought maybe it was a weird bug, so I turned Google Now app back on, turned the Google Now from any screen option off, and restarted phone just to fully test this proposed solution on my device. No fix.
Now WTF do I do? Here's my plan:
1) Do factory reset again, no SD card, no account setup, leave phone stock, no app updates, nothing. Just reset and that's it. Again, I tried this already and the problem persisted, but I will do it again to get back to a neutral starting point.
2) Pair the phone with my Samsung Bluetooth headset, which should hopefully be compatible with my Samsung phone, durp durp.
3) If the problem is fixed by doing that, I will adjust my approach to investigate why that fixed the problem, but I don't expect this to solve it, so from here I will do another factory reset and repeat this process a few times to see if the phone will start working again. My theory is that there could be some sort of hysteresis in memory regarding the paring of the phone with my car (which it might not be real compatible with?), and I might be able to flush it out by pairing it with a different, more compatible device a few times? I'm no software engineer, but hell it's worth a try.
4) If the problem still persists, I will make one last ditch effort to work around it by installing custom firmware and setting up the phone very carefully, leaving bluetooth disabled and not pairing it with ANYTHING, to eliminate that as a culprit (that is, IF I can even get the thing to work correctly again after rooting it and installing the custom firmware).
5) Last and final option if all of that fails is to restore to stock firmware, reset the warranty flag and return the thing to T-Mobile. Maybe it is time to explore options outside of T-Mobile and Samsung, as my last two devices provided by them have been quite problematic. It sucks when one of my customers calls me and I don't know if I should try to answer or not because my phone might be in this stupid state. I certainly never had this problem with my Nokia 5190 back in the day, lol. All the technology in the world and these new smart phones can't even work right as a PHONE.
I'll send an update if anything good happens. If you don't see an update from me within a week or so, it means nothing above fixed my problem and I have likely abandoned the device, and possibly the carrier as well, depending on their support. If I have this issue crop again in the future with yet another device, I will try to get on here again and provide another update.
Good luck, and keep fighting the good fight!
-Kyle
Thank you for your efforts, and congratulations to all who have succeeded in eliminating this issue. Unfortunately for me, it is still a big problem. There's a lot to read here, but I'm trying to be thorough. Maybe some saint of a geek will take the time to read it all and we can help the world somehow, lol.
The history on this goes back just a little too far for me to provide great detail, and I honestly can't remember when/why it first started to happen. But it started on my old phone, a Galaxy S Blaze from T-Mobile. I can't remember if I was having this problem before I bought my 2013 Ford Focus or not. I'm beginning to suspect that this may be heavily involved. For whatever reason, the phone would intermittently have no sound (both ways) during calls. Once the phone got in that state, it didn't matter if I tried bluetooth, speakerphone, wired headset, nothing worked!
Whatever the case, it must have started quite a while after I first got the S Blaze, because I remember deciding to root it and go custom firmware (Cyanogenmod 10.1) to see if the problem would stop. I was considering doing the CM switch anyway, so this pushed me into it, rather than doing a bunch of other troubleshooting to find the root (pun intended!) of the issue. This makes me strain my brain to try and remember if there was any correlation between when the problem started and when I got the new car. Can't remember! All I know is, it wasn't ALWAYS a problem on that phone.
Bummer was after rooting the phone, installing CM10.1, getting my apps back on there and blah blah, problem didn't stop occuring. Again, it was rather intermittent (maybe once a week) and fairly easy to recover from (reset phone repeatedly until a call to voicemail works again). Since I don't do a lot of voice calls and the recovery wasn't too difficult, I decided to live with this little issue until I could afford a new phone... which ended up taking longer than I thought. By the way, I will never buy a non-flagship, carrier-exclusive device again! What a dumb move.
Finally out of frustration with the Blaze more than anything (battery life was real bad after 2.5 years, and it was starting to freeze OFTEN), I broke down and bought a refurbished Galaxy S4 LTE from the T-Mobile website last week, and it arrived preloaded with the newest 4.4.4 Kitkat firmware. I'm thinking, okay finally I'll have a perfectly working device again, after living with this buggy junker for so long. Don't know what was wrong with it, don't care, never looking back! I took great fun in smashing the worthless Blaze to bits Sunday night once my awesome new S4 was all set up and seemingly working flawlessly.
I just about cried the first time this same damn problem happened on my newly refurbished S4!
Now I'm really irritated. What could this problem be? across two devices, completely different firmware, what are the commonalities? I have googled this to the ends of the internet and tried everything under the sun on my new S4 (except haven't done a new firmware/ROM yet because it didn't help on the Blaze so I better try EVERYTHING else first this time). More on that below.
Sidenote: On the GS4 the problem is much more persistent. It first happened on Monday at work, and Monday night I got it working again by restarting the phone a bunch (maybe 7 or 8 times) with a test call to voicemail after each restart. It happened again at work today, and for the life of me I cannot get the thing working again now. Really bummed.
Here's what I have done with my brand new device leading up to the problem:
1) Installed my Sony 32GB SD card from my old phone as well as the new smaller-sized SIM card.
2) Activated the new SIM card online, and turned on the GS4 for the first time.
3) Set up my Google account for Gmail/Play Store, and set up the built-in email app with my Hotmail credentials.
4) Imported my contacts from the SD card.
5) Installed a bunch of stuff like Nova launcher, PDF reader, QuickPic, CapturePro, Torch, a fairly long list of other apps/utilities, etc (again, I thought this loss of sound was a unique problem with my old phone so I wasn't shy about putting all my favorite apps right back on the new device).
6) Tweaked the look and feel a bunch and configured the device to my liking, including disabling several of the included apps.
7) Paired with my 2013 Ford Focus and did some bluetooth calling on Sunday.
8) Took the phone to work Monday morning (this problem seems to always actually START while I'm at work. the first time it happened on this new device was on Monday, AT WORK. It is more or less just an observation, because I can't think of any sensible reason for this to be a problem. Is it because I just drove my car? Well I drive my car all the time, all over the NW).
Troubleshooting notes:
I don't use anything special with my phone at work, no company email or VPN or anything like that. It just rides in my pocket or sits on my desk connected to a charger all day, and doesn't even have data or wifi enabled (I rarely use/enable mobile data). I rarely make/receive a few texts or voice calls with it throughout the day. Could it be getting messed up by something at work because the bluetooth is left on, and then my phone gets somehow stuck in that state? I don't know what it could be, but the correlation is hard to ignore.
I have never used any kind of voice search, nor did I even have any of those previously mentioned apps (S Voice or Google Now) installed on my hacked Galaxy S Blaze. Further, Google Now was one of the the built-in apps that I disabled on the GS4 when I first set it up on Sunday (I simply don't use voice search/voice commands/speech to text, any of that).
I do not Bluetooth stream audio nor did I have the phone paired with anything else, just my car.
After reading a lot of info online I did the following to try and get the GS4 working again tonight so I can call my brother back:
1) Took out my SD card (and left it out) and rebooted. No fix (To truly eliminate this as a culprit, I left the SD card out through out all other steps below).
2) Uninstalled every app that I had added to the device, including any app updates, and restarted phone. No fix.
3) Triple-checked every setting! Touch sounds, noise reduction, extra volume, silent mode, call sound, voice control, voice search, wifi calling, bluetooth settings, network mode/settings, etc. No fix.
4) Unpaired the device from my car (also deleted the device from my car's memory/menu). No fix.
5) Did a hard reset (from powered off state, hold up volume + home key + power key for a few seconds to boot into recovery mode. navigate through the menu to factory reset the phone). No fix! Unbelievable! How can it still persist? Hardware problem maybe? No, i doubt it... because I had this problem on my old phone too, even after root and custom ROM install!! Same intermittent hardware issue on both devices? EXTREMELY unlikely!
6) From fresh factory reset, no SD card installed, no new apps installed, no bluetooth paired, I disabled every single app the device would let me disable (this DID include both S Voice and Google Now). No fix.
7) Even though Google Now was completely disable, I thought maybe it was a weird bug, so I turned Google Now app back on, turned the Google Now from any screen option off, and restarted phone just to fully test this proposed solution on my device. No fix.
Now WTF do I do? Here's my plan:
1) Do factory reset again, no SD card, no account setup, leave phone stock, no app updates, nothing. Just reset and that's it. Again, I tried this already and the problem persisted, but I will do it again to get back to a neutral starting point.
2) Pair the phone with my Samsung Bluetooth headset, which should hopefully be compatible with my Samsung phone, durp durp.
3) If the problem is fixed by doing that, I will adjust my approach to investigate why that fixed the problem, but I don't expect this to solve it, so from here I will do another factory reset and repeat this process a few times to see if the phone will start working again. My theory is that there could be some sort of hysteresis in memory regarding the paring of the phone with my car (which it might not be real compatible with?), and I might be able to flush it out by pairing it with a different, more compatible device a few times? I'm no software engineer, but hell it's worth a try.
4) If the problem still persists, I will make one last ditch effort to work around it by installing custom firmware and setting up the phone very carefully, leaving bluetooth disabled and not pairing it with ANYTHING, to eliminate that as a culprit (that is, IF I can even get the thing to work correctly again after rooting it and installing the custom firmware).
5) Last and final option if all of that fails is to restore to stock firmware, reset the warranty flag and return the thing to T-Mobile. Maybe it is time to explore options outside of T-Mobile and Samsung, as my last two devices provided by them have been quite problematic. It sucks when one of my customers calls me and I don't know if I should try to answer or not because my phone might be in this stupid state. I certainly never had this problem with my Nokia 5190 back in the day, lol. All the technology in the world and these new smart phones can't even work right as a PHONE.
I'll send an update if anything good happens. If you don't see an update from me within a week or so, it means nothing above fixed my problem and I have likely abandoned the device, and possibly the carrier as well, depending on their support. If I have this issue crop again in the future with yet another device, I will try to get on here again and provide another update.
Good luck, and keep fighting the good fight!
-Kyle
So you guys know, you can avoid this problem by disabling media audio support on your bluetooth menu. This way, the google now will not work from your headset. It will work from any screen but only if you speak into the phone. This options works a lot better for me than disabling the google now detection since I only use the headset for talking while driving.
I've had the AT&T Lollipop update for about a week. After the update, I enabled "OK Google Detection...from Any Screen" and....I haven't had any problems!! <knock on wood>
Has anyone else had similar success?
Has anyone else had similar success?
jamaica168
Well-known member
- Aug 4, 2013
- 50
- 0
- 6
What seemed to work for me on kit kat is disabling the option to record audio through Bluetooth headset in the Google now voice settings. I was able to still have OK google from any screen.
Have you upgraded to Lollipop and tried this. I just upgraded (Verizon) but don't want to go through the hassle if you gurus out there have already done it and determine it doesn't work. Sure would like to have OK Google on all the time...
I'm having a similar issue with my Samsung Galaxy S5 & my 2015 nissan altima s......everything works great, except incoming & outgoing calls...i know it works because i made 1 voicecall out while practicing & i heard the phone dialing through my speakers. I can tell it to call, then name of contact, then dial..BUT after i say dial, my screen on car says dialing but i hear nothing and no response on phone...also when someone calls me, i hear and see nothing on either car or phone....when phone & car are paired of course. I would appreciate any advice or suggestions, thank you.
The Lollipop upgrade did fix the problem. Though I only have OK Google after I select Google. Am very happy with the S4 now.
Similar threads
Trending Posts
-
-
Google wallet not working after latest update
- Started by AJ69
- Replies: 21
-
-
OneUI 8 beta coming week of August 11, 2025- Started by Laura Knotek
- Replies: 0
-
Facebook
Twitter
Instagram