Voice to text issues? - Samsung Galaxy S8 Questions and Answers

Is anyone else having an issue with Bixby voice to text? Where I completely disabled Bixby voice to text, but still leaving Google Voice to Text on. Then a few minutes later Bixby voice to text is turned on again, by itself, automatically. it overrides the Google voice to text, which I realized it when trying to use Google Voice to Text from the keyboard. It will end up opening Bixby voice to text, instead of Google voice to text.
I contacted Samsung about this twice. The first time, they never heard about this issue. Then the second time I called, they told me there is an issue with Bixby, but they don't know what to do to fix this and they don't know if and when a fix for Bixby is comming out.

Go to settings and select apps then hit menu button and select show system apps. Then find Samsung voice input and disable it. It then defaults to google voice to text. It works after reboot too.

mrb6208 said:
Go to settings and select apps then hit menu button and select show system apps. Then find Samsung voice input and disable it. It then defaults to google voice to text. It works after reboot too.
Click to expand...
Click to collapse
That's exactly what I'm doing. But every few minutes continuously it turns Bixby voice to text back on in the same OS settings. When I try to use Google voice to text every few minutes or so, Bixby voice to text comes up instead of Google voice to text. Then when I go to the same settings again Bixby voice to text magically is turned on by itself. This is a repetitive cycle every few minutes.

bigj0110 said:
That's exactly what I'm doing. But every few minutes continuously it turns Bixby voice to text back on in the same OS settings. When I try to use Google voice to text every few minutes or so, Bixby voice to text comes up instead of Google voice to text. Then when I go to the same settings again Bixby voice to text magically is turned on by itself. This is a repetitive cycle every few minutes.
Click to expand...
Click to collapse
When I changed the settings in language & inputs it kept doing what your describing but if your disabling Samsung voice to text there's no way it should be enabling itself. I have an s8 plus on T-Mobile and it works for me. I'd try to swap out your phone before it's been 14 days cuz Bixby sucks. Good luck!

9
mrb6208 said:
When I changed the settings in language & inputs it kept doing what your describing but if your disabling Samsung voice to text there's no way it should be enabling itself. I have an s8 plus on T-Mobile and it works for me. I'd try to swap out your phone before it's been 14 days cuz Bixby sucks. Good luck!
Click to expand...
Click to collapse
I'm on my 3rd device because of multiple bugs. I fixed every bug except the Bixby Voice to Text issue, and a Wi-Fi issue. Till the point, I'm unable to use my Wi-Fi. I made another post on this site about it.
At least for the Wi-Fi and, they want me to send them the phone and remain without the phone for at least 2 weeks minimum. They keep saying they never heard of this issue, except the one representative who got multiple calls about it personally. Samsung has done absolutely nothing for me. I've called Samsung the last 4 consecutive days. Every time I called them about those issues they don't tell me yes, no, maybe, I don't know. They simply just want me to send them the phone. Today though I was able to get somebody show me the wanted to use my phone to figure out the problem because they claim they never heard about this. Even though all over the internet people are talking about this comma and even one Samsung representative confirmed she personally dealt with it on the phone last week.
What's going on with my Wi-Fi is that it connect to any network, the transparent box shows up and everything letting me know that is connected. 10 seconds later the transparent box comes again and tells me that network has been disconnected. And it repeats that non stop. This also happened across the 3 devices I've had. I'm not the only one to have the Wi-Fi issue, a simple Google search of this would indicate that. Even customer of other carriers such as AT&T, Verizon and my carrier T-Mobile are complaining about this as well. Like when I talk to Samsung I'm talking to a brick wall. I'm honestly about to return the phone and ask for a complete refund if I don't get an answer other than sending my phone in!

Thank you soooo much!!!!
mrb6208 said:
Go to settings and select apps then hit menu button and select show system apps. Then find Samsung voice input and disable it. It then defaults to google voice to text. It works after reboot too.
Click to expand...
Click to collapse

This issue is still an ongoing issue for me. Every so often randomly, I would have to go into the settings like it's described here and turn off Bixby voice to text in the OS setting. For some reason Google Voice to Text can't seem to stay on without Bixby voice to text turning itself back on in the settings. Which then, even though Google voice to text is still on, Bixby voice to text overrides that, once it's turned on.
I reported this to Samsung like a month or 2 ago. All they want me to do is send in my phone, and remain without a phone for 2 weeks minimum(which I'm refusing to do). They claim there's nothing else they can do to help me, other than that.
I mean I'm getting upset, because I spend a lot of money on the device and I'm still having issues with this, and the Wi-Fi issue I stated above. Even after 3 exchange devices the same exact issues are occurring.

To bigj0110 - I can't thank you enough! I just got my S8 a couple days ago, and I hate the Samsung voice input. I couldn't figure out how to make it go away, and I thought I was stuck with it. Your suggestion worked! I'm so happy to have Google voice input back! You made me a very happy woman! Thanks! Jo Ann

Use Twiter
If you tweet using #Samsung or support they are quick to get back to you because they don't like the bad publicity on social media. I am having the same issues and think its time for everyone with a note 8 that is having issues demand a fix by blowing up twitter with bad publicity. What else can we do at this point?
I'm on my 3rd device because of multiple bugs. I fixed every bug except the Bixby Voice to Text issue, and a Wi-Fi issue. Till the point, I'm unable to use my Wi-Fi. I made another post on this site about it.
At least for the Wi-Fi and, they want me to send them the phone and remain without the phone for at least 2 weeks minimum. They keep saying they never heard of this issue, except the one representative who got multiple calls about it personally. Samsung has done absolutely nothing for me. I've called Samsung the last 4 consecutive days. Every time I called them about those issues they don't tell me yes, no, maybe, I don't know. They simply just want me to send them the phone. Today though I was able to get somebody show me the wanted to use my phone to figure out the problem because they claim they never heard about this. Even though all over the internet people are talking about this comma and even one Samsung representative confirmed she personally dealt with it on the phone last week.
What's going on with my Wi-Fi is that it connect to any network, the transparent box shows up and everything letting me know that is connected. 10 seconds later the transparent box comes again and tells me that network has been disconnected. And it repeats that non stop. This also happened across the 3 devices I've had. I'm not the only one to have the Wi-Fi issue, a simple Google search of this would indicate that. Even customer of other carriers such as AT&T, Verizon and my carrier T-Mobile are complaining about this as well. Like when I talk to Samsung I'm talking to a brick wall. I'm honestly about to return the phone and ask for a complete refund if I don't get an answer other than sending my phone in![/QUOTE]

mrb6208 said:
Go to settings and select apps then hit menu button and select show system apps. Then find Samsung voice input and disable it. It then defaults to google voice to text. It works after reboot too.
Click to expand...
Click to collapse
Thanks MrB. this saved me lots of aggravation. voice to text works much better now.

Can't disable Samsung voice, the disable button is grayed out.

on my note 8 for turning bixby off, this what i did and not sure if this is what you want....
settings
general management
language input
on screen key board
+ manage keyboards
then on "Samsung voice input" toggle off
>>>>>>>>>>>>>>>>>>>>>>>>>>
hit back arrow twice
>>>>>>>>>>>>>>>>>>>>>>>>>
text to speech
then touch the radio button on "Google Text_to_speech Engine"
>>>>>>>>>>>>>>>>>>>>>>>>
hit arrow back as much as you can then go to main screen, then try texting using voice.... for me, no more Bixby!!! YAY!!!!
I tried training Bixby but there was always a freeking probelm. I have patience, but this thing got to me.... bye Bixby.

Related

Enabling Visual Voicemail on T-Mobile

Just Contacted t-mobile to get the Visual Voicemail activated.
The rep was really nice but had no idea how to do it.
Eventually she figured it out:
Change the regular data plan to a Android web data plan
There is no difference and no cost difference except for the Android Web Data plan has the Visual Voice mail function.
Once this is done you will receive a sms confirmation.
Go and download the visual voicemail app from the market, or download the t-Mobile app pack and get it through there.
Cheers!
Edit: They said that it would take upto 24 hours for the vv to work, i tried it 1 minute after the call, and it seems to have found the service, but taking a long time to connect. I will update this as soon as it works!
Edit2: OK IT'S up and running. AWESOME. Even picked up my old voicemails and used my contact list to name them etc.
got it as well... pretty damn cool
Just took a few minutes on the phone and it's activated and works.
Just dial '611' and ask to activate visual voicemail. They'll put you on hold for a couple of minutes and activate it. Afterwards, you should be able to use it without much delay.
Sadly had to call because i am on a family plan w/unlimited sms
Took 5 minutes total to switch my 2 G1's
EDIT: I can hear all the CSR's in the room talking about it. LOL
Interesting note: I left myself a "test voicemail", used Visual Voicemail to listen to it, deleted it, and ended the call. Seemed fine. Later, I went into my voicemail and it was marked as a "saved message". Uhhh... that's NOT what I wanted
Anyone else notice this?
(Note: just tested this again... same thing!)

Weird incoming call/voicemail error

We have 8 lines on our business account from Sprint. Here is what is happening:
When Line 1 calls Line 2, the call goes through, the phone rings, and everything works like normal. When we switch it around and Line 2 calls Line 1, the phone on Line 1 never rings. Line 2 gets Line 1's voicemail. This has been going on since March. It never changes. Line 1 will never ring when Line 2 is calling it. All other phones can call Line 1 and it rings perfectly and acts like normal.
Line 1 and Line 2 are both HTC EVO's with Cyanogenmod 7 on them. They were working perfectly for two months, and then it changed. When the problem first started happening, sometimes instead of getting voicemail when calling Line 1, I would sometimes get a message that said: "This is channel 47 4".
Around the same time when this started happening, it also started with another phone on our plan. Line 3 on our plan cannot receive phone calls from one certain Verizon cell phone number. The Verizon phone is a Samsung Fascinate that is rooted. Line 3 on our plan is a Sprint HTC Hero running Cyanogenmod 7. The same thing happened here. At first the Verizon Phone calling in would here a message that said "This is channel 47 4", but now all they get is voicemail immediately.
All of the phones use Google Voice voicemail, but I tried disabling it and then they just got the Sprint voicemail immediately.
I called sprint about it but they said they need to troubleshoot it in a repair store. We do not have corporate stores in our area, and I don't trust the repair stores that are here. Last time my old Touch Pro was in to them, it came back severely damaged. Also, I don't want to risk losing the root on my phones and having them upgraded to Gingerbread which hasn't been rooted yet.
Has anyone ever heard of an issue like this, or does anyone have any idea what I should do?
Thank YOU!
I did check and make sure that in the contacts the phone was not set to forward the call to voicemail immediately.
I am on AT&T with an HTC Tilt/Kaiser and have the same issue with my step-father who has an EVO. And yet my Mother, who is on the second line on that account with another EVO, can receive them from me. Not just you. Except none of the phones have mods and we don't get the "47 4" thing.
If anyone ever has this problem, the solution for me was to completely wipe the phone, install a cm7 again, and NOT restore any backed up applications.
Sent from my PG86100 using Tapatalk
UPDATED INFORMATION:
I misposted. My problem has not been fixed. All that was solved was that I can now log into my ATT voicemail myself from my own phone - prior to that, by pressing "1" to access my voicemail, I got the message: "This is channel 47-4"
Now though my voicemail seems OK on my end, people calling in still receive the message "This is channel 47-4"
I am in Los Angeles but I have found a newspaper article about a whole community in Norfolk, VA whose phones are supplied by a Time Warner subcontractor, Intrado Communications in Longmont, Colo and the panic it has caused that they were unable to reach Emergency Services on their phones.
(I have not posted enough to post a link. I cannot seem to post even the unlinked URL but here is the article title and newspaper - it was printed in several local newspapers, it's easy to find.)
Phone Service Trouble Remains
Watertown Daily Times
A quote from the article:
"Most of the time, the phone rings busy," Mrs. Michaud said. "Sometimes, it says this is channel 47-4."
Still nowhere can I find anyone who knows what is going on. And back in January, apparently even Time Warner had no idea, they fixed the cable but not the phones.
A NEW TEST: I have just deactivated Google Voice again and tested - my ATT voicemail IS reachable. My problem is gone. Unless I want to forward to Google Voice. I have searched Google and Google Voice Help up and down and have not found a reference to "channel 47-4"
But at this point - in my situation anyway - Google Voice is the culprit. Or possibly the target.
ORIGINAL POST:
I just finished spending 2 hours with ATT in 2 different tech support attempts for this same 47-4 message problem - only mine was slightly different. I fixed the problem but I can't let it go. I am curious how the same recording could be reached across different carriers, ATT and Sprint.
Blow by Blow to maybe help someone figure it out:
I have an unmodded Galaxy S2 SGH-i777
I have been using Google Voice for this and my previous 2 phones all with the same ATT Wireless account.
Today, when people called my number they got the same weird message as everyone - weird for the message and loud background noise.
"This is channel 47-4"
I called my phone from a landline and got the message.
Clicking the hook switch makes the message repeat without hanging up.
(I tried it 4 times)
Google Voice should have intercepted an unanswered call, right?
The first tech support advice:
Reboot the phone, they would send a voicemail reset signal and then I should reset my password.
(I took it upon myself to deactivate the Google Voice account first.)
When I pressed the "1" key to access ATT Voicemail and set the password, I got "Unable to perform this action contact customer service."
I then tried to access my voicemail account online and got ERROR E1018
I called tech support again and they weren't interested in the error code.
They called me back on my landline and asked me to reset my password using "1"
I held the phone up for her to hear. This time when I pressed "1" I immediately got the recording "THIS IS CHANNEL 47-4"
What I found fun is that the message freaked out the tech support. She had never heard anything like it, she said.
Here is the new oddity:
When she came back on the line she was more freaked out! There was no record of any voicemail on my line. Voicemail isn't an "option," she said, it comes with every account. She knew of no type of account without voicemail. Having no voicemail account on my number was impossible, she said.
Regardless, I popped out the battery and restarted while she sent a "reset" signal and everything is now back to normal. I enabled Google Voice and all is as it was before today.
I've searched online and there is a lot of recent 47-4 issues and a lot of good solutions only no one seems to know what the message is or how it got there. I have the added piece of information that somehow my ATT record of any voicemail account was wiped out in the system.
The same message across carriers means what? That it's in the shared data lines? Shared towers?
If someone knows what this message is and who it originates from, I'd like to know. If I find out, I'll come back here and leave an update.

Persistent voicemail notification

I know I saw someone mention this either on here or another forum, but I'll be damned if I can find the solution.
I'm on T-Mobile's 100 minute plan and disabled carrier voicemail long ago. After moving everything over to my Nexus 4 yesterday I've been getting a persistent new voicemail notification. Of course it can't find my mailbox when it calls voicemail; it doesn't exist.
I can't see any way of clearing this. Anyone else run into this?
Headcase_Fargone said:
I know I saw someone mention this either on here or another forum, but I'll be damned if I can find the solution.
I'm on T-Mobile's 100 minute plan and disabled carrier voicemail long ago. After moving everything over to my Nexus 4 yesterday I've been getting a persistent new voicemail notification. Of course it can't find my mailbox when it calls voicemail; it doesn't exist.
I can't see any way of clearing this. Anyone else run into this?
Click to expand...
Click to collapse
I had to call my T-Mo Voicemail leave a message, give it about 5 minutes. Hit the icon so it calls the voicemail then delete the one I made. Then switched to Google Voice lol. If you don't know your voicemail number, call your number from your phone. Assuming you didn't change any settings it should take you directly to T-Mo voicemail.
timskyline86 said:
I had to call my T-Mo Voicemail leave a message, give it about 5 minutes. Hit the icon so it calls the voicemail then delete the one I made. Then switched to Google Voice lol. If you don't know your voicemail number, call your number from your phone. Assuming you didn't change any settings it should take you directly to T-Mo voicemail.
Click to expand...
Click to collapse
Well that's the rub. I called T-Mobile long ago and had them turn off voicemail altogether. I use Google Voice exclusively.
Edit: I should mention that it did this on both the stock ROM and CM10.1, though on CM it didn't start until after I rebooted the first time.
I had the same problem and I also had this problem with my Galaxy Nexus. The solution I found on both phones was that as soon as I rooted and flashed a new ROM I immediately installed Google Voice after performing the initial setup (before doing anything else). On both phones this prevented that persistent notification from ever returning.
Many others had this problem on the Gnex as well and all agreed that this solution worked.
sn0warmy said:
I had the same problem and I also had this problem with my Galaxy Nexus. The solution I found on both phones was that as soon as I rooted and flashed a new ROM I immediately installed Google Voice after performing the initial setup (before doing anything else). On both phones this prevented that persistent notification from ever returning.
Many others had this problem on the Gnex as well and all agreed that this solution worked.
Click to expand...
Click to collapse
So once it's there I'm kind of out of luck? Do I have to do a factory wipe and reflash CM10 for a chance at getting rid of it?
Go to your google voice account on a computer and mark EVERY voicemail that is not marked as read, read.
Solves your problem.
darkamikaze said:
Go to your google voice account on a computer and mark EVERY voicemail that is not marked as read, read.
Solves your problem.
Click to expand...
Click to collapse
I haven't had any GV voicemails at all since powering on the Nexus 4 for the first time, either old ones or new.
I did change the voicemail setting to Google Voice in dialer settings then cleared data on the dialer app. That made it disappear... for now.
Headcase_Fargone said:
So once it's there I'm kind of out of luck? Do I have to do a factory wipe and reflash CM10 for a chance at getting rid of it?
Click to expand...
Click to collapse
I had exactly the same problem after swapping SIM card to my nexus. My voicemail was disabled. Every time I call it I was forced to press * key and enter 10 digit number. I had to call T-Mobile to solve notification icon problem. They set up my voicemail again and left a message. After that I called and listened it, so the problem is gone now. Hope this will help you
Sent from my Nexus 4 using xda app-developers app
Headcase_Fargone said:
So once it's there I'm kind of out of luck? Do I have to do a factory wipe and reflash CM10 for a chance at getting rid of it?
Click to expand...
Click to collapse
Wipe cache and dalvik cache then fix permissions. After rebooting I bet it will be gone.
OP, any luck getting this sorted? I got an N4 for Christmas and I'm seeing the same thing as you.
I'm on the $30 prepaid plan, and had previously disabled my T-Mobile voicemail. Once I got a new micro SIM and popped it in my new phone, I received the persistent voicemail indicator. I called T-Mobile on Monday and all I could get them to do was to "create a report" of my issue - even after I suggested that they re-enable my voicemail to let me leave and clear a message. I'll try calling today to see if I have better luck stumbling across the magical combination of words to get them to do what I want, but figured I'd check in and see what sort of success you may have had.
I have the same issue, I am on Fido (Canada). I have the persistent icon every-time my phone reboots... I do have a voice mail, and I have no messages on it. I even tried calling myself from another phone, leaving a message and using my N4 to delete it, but it still there and persistent. I don't recall having that issue on my previous phone... (Gnexus)
I've also noticed that if gapps aren't flashed, the icon isn't there...the moment I flash google apps...it appears..
Any solution would be highly appreciated...
I've ran into this a few times and it's not always google voice, sometimes it's your carrier voice mail, you can also try setting your phone back to carrier voicemail, calling and leaving a message and then deleting it. It's fixed an issue on my work phone a few times.
codesplice said:
OP, any luck getting this sorted? I got an N4 for Christmas and I'm seeing the same thing as you.
I'm on the $30 prepaid plan, and had previously disabled my T-Mobile voicemail. Once I got a new micro SIM and popped it in my new phone, I received the persistent voicemail indicator. I called T-Mobile on Monday and all I could get them to do was to "create a report" of my issue - even after I suggested that they re-enable my voicemail to let me leave and clear a message. I'll try calling today to see if I have better luck stumbling across the magical combination of words to get them to do what I want, but figured I'd check in and see what sort of success you may have had.
Click to expand...
Click to collapse
Quick follow-up: My second attempt with T-Mobile support was much more successful. Within about ten minutes I had gotten my voicemail turned back on, a test message cleared (along with the notification), and the voicemail service disabled again.
From some reading around the web, it seems that new SIM card activations with T-Mobile default the Message Waiting Indicator (MWI) to On, I guess in an attempt to get you to set up your voicemail service ASAP. They unfortunately didn't have the foresight to automatically disable that if the SIM is activated on an existing line with no voicemail service. Oh well, that was easy enough to fix
I'm topping this thread because it's the first one that popped up in my Google search on how to resolve my issue.
AT&T Galaxy S4
Google Voice voicemail
Just got my phone in and I didn't set up the voicemail properly I guess.
Got a notification of a new voicemail.
The message wouldn't go away.
When I dialed the number it told me to dial, that just went to my Google voicemail which said there were no new voicemails.
I tried a BUNCH of things. Here is what finally worked for me.
1) I went to https://www.google.com/voice
2) I disabled my Google Voice on my phone from that link.
3) Rebooted my phone.
4) Now when I called my voicemail, it went to my AT&T voicemail instead of Google.
5) From there, I was able to delete my voicemails.
6) Then I re-enabled Google Voicemail on my phone from the link above and now all is good again. No more notifications that don't go away.
This thread was a huge help in me troubleshooting the problem.
CZ Eddie said:
I'm topping this thread because it's the first one that popped up in my Google search on how to resolve my issue.
AT&T Galaxy S4
Google Voice voicemail
Just got my phone in and I didn't set up the voicemail properly I guess.
Got a notification of a new voicemail.
The message wouldn't go away.
When I dialed the number it told me to dial, that just went to my Google voicemail which said there were no new voicemails.
I tried a BUNCH of things. Here is what finally worked for me.
1) I went to https://www.google.com/voice
2) I disabled my Google Voice on my phone from that link.
3) Rebooted my phone.
4) Now when I called my voicemail, it went to my AT&T voicemail instead of Google.
5) From there, I was able to delete my voicemails.
6) Then I re-enabled Google Voicemail on my phone from the link above and now all is good again. No more notifications that don't go away.
This thread was a huge help in me troubleshooting the problem.
Click to expand...
Click to collapse
Hate to resurrect an old thread but go to your dialer and clear data/cache and the notification will go away.
ohiog said:
Hate to resurrect an old thread but go to your dialer and clear data/cache and the notification will go away.
Click to expand...
Click to collapse
Do you mean in Settings / Application Data?
I tried that and it did not clear the indicator.
I needed to call T-Mobile, have voicemail turned back on, clear the indicator, and then call back and have them disable my voicemail service again so my calls would be redirected to my GVoice mailbox.
You should cancel it at your mobile operator. I had the same problem
Sent from my Nexus 4 using Tapatalk 4

[Q] Not answering incoming call - galaxy s5 - 4.4 kitkat

First off, I didn't find this anywhere on the forum, so I hope it's not a dupe - but it's a very annoying problem. I have a Galaxy S5 on KitKat. Here's the issues (pretty much all related):
Often times, I'll answer an incoming call successfully but the person on the other line simply hears a continuous ring cycle.
(Same as #1), but instead of hearing ring cycles - they get voicemail.
On other occasions my phone will be face up on a counter, I'll get a phone call, and when I walk over to the device it will "automatically answer" but the person never connects on the other line.
For all of these occasions, this seems to happen more frequently the first time someone tries to call me. Sometimes additional incoming calls from that number will go through with more success, but not all the time. Restarting the phone and pulling out the SIM card and battery not only do not fix the issue, but seem to consistently re-create the problem.
I should also note that I had Google voice as my provider for voicemail, but I have temporarily disabled that and set up my voicemail through Verizon - still doesn't help. Also 3rd party dialer apps like Dialer One do not make a difference.
Here are my settings:
Android Version 4.4.4 - Kitkat, no updates available (non rooted)
Blocking mode disabled
Motions and Gestures disabled
S-Voice disabled
Preferred network mode: LTE / CDMA **This seemed to solve the problem at first, but it came back immediately. (It was set to 'Global')
I've spent hours trying to fix this and contemplated rooting my device to try to get it to work, but to be honest I'd rather just exchange the phone for a new one before I did something like that. I also have not restored to Factory Default... but again that is preferably a last resort.
Any thoughts? I need a 100% working phone for my job and missing phone calls and having to call people back just isn't cutting it.
rmarq423 said:
First off, I didn't find this anywhere on the forum, so I hope it's not a dupe - but it's a very annoying problem. I have a Galaxy S5 on KitKat. Here's the issues (pretty much all related):
Often times, I'll answer an incoming call successfully but the person on the other line simply hears a continuous ring cycle.
(Same as #1), but instead of hearing ring cycles - they get voicemail.
On other occasions my phone will be face up on a counter, I'll get a phone call, and when I walk over to the device it will "automatically answer" but the person never connects on the other line.
For all of these occasions, this seems to happen more frequently the first time someone tries to call me. Sometimes additional incoming calls from that number will go through with more success, but not all the time. Restarting the phone and pulling out the SIM card and battery not only do not fix the issue, but seem to consistently re-create the problem.
I should also note that I had Google voice as my provider for voicemail, but I have temporarily disabled that and set up my voicemail through Verizon - still doesn't help. Also 3rd party dialer apps like Dialer One do not make a difference.
Here are my settings:
Android Version 4.4.4 - Kitkat, no updates available (non rooted)
Blocking mode disabled
Motions and Gestures disabled
S-Voice disabled
Preferred network mode: LTE / CDMA **This seemed to solve the problem at first, but it came back immediately. (It was set to 'Global')
I've spent hours trying to fix this and contemplated rooting my device to try to get it to work, but to be honest I'd rather just exchange the phone for a new one before I did something like that. I also have not restored to Factory Default... but again that is preferably a last resort.
Any thoughts? I need a 100% working phone for my job and missing phone calls and having to call people back just isn't cutting it.
Click to expand...
Click to collapse
First try a data factory reset, if that doesn`t help refash the stock rom with odin 3.09 and after that factory reset/wipe cache in recovery.
rmarq423 said:
First off, I didn't find this anywhere on the forum, so I hope it's not a dupe - but it's a very annoying problem. I have a Galaxy S5 on KitKat. Here's the issues (pretty much all related):
Often times, I'll answer an incoming call successfully but the person on the other line simply hears a continuous ring cycle.
(Same as #1), but instead of hearing ring cycles - they get voicemail.
On other occasions my phone will be face up on a counter, I'll get a phone call, and when I walk over to the device it will "automatically answer" but the person never connects on the other line.
For all of these occasions, this seems to happen more frequently the first time someone tries to call me. Sometimes additional incoming calls from that number will go through with more success, but not all the time. Restarting the phone and pulling out the SIM card and battery not only do not fix the issue, but seem to consistently re-create the problem.
I should also note that I had Google voice as my provider for voicemail, but I have temporarily disabled that and set up my voicemail through Verizon - still doesn't help. Also 3rd party dialer apps like Dialer One do not make a difference.
Here are my settings:
Android Version 4.4.4 - Kitkat, no updates available (non rooted)
Blocking mode disabled
Motions and Gestures disabled
S-Voice disabled
Preferred network mode: LTE / CDMA **This seemed to solve the problem at first, but it came back immediately. (It was set to 'Global')
I've spent hours trying to fix this and contemplated rooting my device to try to get it to work, but to be honest I'd rather just exchange the phone for a new one before I did something like that. I also have not restored to Factory Default... but again that is preferably a last resort.
Any thoughts? I need a 100% working phone for my job and missing phone calls and having to call people back just isn't cutting it.
Click to expand...
Click to collapse
Im having the same issue, i cleared the cache, did a factory reset and made sure s voice was turned off, it cleared the issue up for about a month. Recently i have been having this issue happen more and more. Im starting to think it may have something to do with the Bluetooth or the visual Voice mail / voice mail. Anyone else have any ideas on what else to try or do ? The only problem is recreating the environment to cause it to happen. Right now its completely random.

sprint s8 immediately drops calls when answered

I can't even get past 2 seconds when trying to answer a call. I can make calls with no problem.
I did a factory reset once and that fixed it however i don't want to keep going through that to fix it.
I tried from a land line, when i answer, it ends the call on the phone after 1 second. The land line stays connected with no sound or feedback.
I'm having voice call issues with my sprint s8 as well. It ends the call almost immediately. Can't make or receive any voice calls. Text and data is working fine though.
Sent from my SM-G950U using Tapatalk
adrand said:
I'm having voice call issues with my sprint s8 as well. It ends the call almost immediately. Can't make or receive any voice calls. Text and data is working fine though.
Sent from my SM-G950U using Tapatalk
Click to expand...
Click to collapse
I can make make calls but not receive them...I called samsung, and they just said to send in the phone...
I dropped sprint a few years ago due to poor coverage, slow lte and dropped calls. I live right between DC and Baltimore and should be in a very very good coverage area but sprint just plain sucks but I didnt have the issue you describe. My calls would drop during almost every call but could go for a few minutes or more before they dropped. I am wondering if maybe your phone isnt provisioned correctly or something. I would be calling sprint and having them work with you on the issue. Good luck I hope you get the problem sorted out!
ProStreetCamaro said:
I dropped sprint a few years ago due to poor coverage, slow lte and dropped calls. I live right between DC and Baltimore and should be in a very very good coverage area but sprint just plain sucks but I didnt have the issue you describe. My calls would drop during almost every call but could go for a few minutes or more before they dropped. I am wondering if maybe your phone isnt provisioned correctly or something. I would be calling sprint and having them work with you on the issue. Good luck I hope you get the problem sorted out!
Click to expand...
Click to collapse
Yeah sprint isn't always the best for everyone but I've had them for over 15 yrs now with great coverage in my area. I've been holding onto my unlimited legacy plan.
I agree, I think the provisioning might be an issue. I'm planning a call to them this afternoon. I think it started after an update yesterday but not positive.
Sent from my SM-G950U using Tapatalk
adrand said:
Yeah sprint isn't always the best for everyone but I've had them for over 15 yrs now with great coverage in my area. I've been holding onto my unlimited legacy plan.
I agree, I think the provisioning might be an issue. I'm planning a call to them this afternoon. I think it started after an update yesterday but not positive.
Sent from my SM-G950U using Tapatalk
Click to expand...
Click to collapse
I don't think it's the coverage, it's like automatically hanging up after i hit answer. If i make a call, it won't hang up during a call. It's really frustrating that phone doesn't work as a phone is intended to work as.
Yes, this is happening to me. It will stay connected about 2 seconds every time. Then drop. I can make calls fine.
I was just starting to investigate. I went to Sprint store and they said check Google Voice integration. I had to leave because I only had a short time, but I am going to check that first.
pinetreehater said:
Yes, this is happening to me. It will stay connected about 2 seconds every time. Then drop. I can make calls fine.
I was just starting to investigate. I went to Sprint store and they said check Google Voice integration. I had to leave because I only had a short time, but I am going to check that first.
Click to expand...
Click to collapse
After factory reset it worked, and that was after google voice was installed. I tried uninstalling google voice and it still does the same thing. Never had any trouble with voice before...so annoying.
Man.... Don't tell me. I just got everything freaking set. And without root.... No Titanium Back-up! ??
okay, i just factory reset it twice, now it won't answer a call at all. I can only make a call.
adrand said:
I'm having voice call issues with my sprint s8 as well. It ends the call almost immediately. Can't make or receive any voice calls. Text and data is working fine though.
Sent from my SM-G950U using Tapatalk
Click to expand...
Click to collapse
I think i found the issue. There is a new version of google voice. I was on google voice legacy. I unlinked my phone number with sprint with the legacy page. I linked the new google voice, it seems to be working now.
Fix: Sprint drop calls after two seconds.
jkluczyk said:
I think i found the issue. There is a new version of google voice. I was on google voice legacy. I unlinked my phone number with sprint with the legacy page. I linked the new google voice, it seems to be working now.
Click to expand...
Click to collapse
jkluczyk, Thanks for posting your fix. It worked for me on my Sprint network phone. Here is how I did it -
- Open Google Voice on your desktop.
- Select Settings - Phone number - Under "Linked numbers" - Unlink your phone number or delete it.
- At top of the page it should say "Try new Google Voice". Select this and go to the new page.
- On the new Google Voice. Repeat steps above and reLink your number again. Should be fixed. Worked for me.
This is the only method that worked for me
Symptom: (All incoming calls hang up right at or just before the 2 second mark). The problem appears to be the association (or lack of) between Sprint and Google Voice.
1st I tried just un-associating/deleting my sprint number with google voice completely and removing my google voice account. This sort of worked, I could answer my phone normally but there was still one big problem. Now I had no voicemail and it would go to busy signal when trying to access it. Also, the phone would ring forever on the callers end if I didn't answer and never go to voicemail. Still no good.
Here's how I fixed it. This method worked for me.
Go to your google voice account - go to legacy mode if you are already in the new version (You must go to the legacy screen to completely remove your account) - go to settings - go to the "phones" tab - deactivate/delete your sprint association and email with your google voice account (In other words, remove everything as if you're starting all over.) You can't do this from the new version, only the legacy version! - give your phone time to update (sometimes up to 15 minutes) - Now setup your Google voice account again but ONLY USE THE LIGHT VERSION and setup voicemail only. This worked for me as my voice mail works fine through google with text and email transcripts and I can actually answer my phone. I did this several times trying the full version vs the light version and every time the full version caused the same issue hanging up with incoming calls, but the light version worked fine.

Categories

Resources