I found out I was in a VoLTE market a couple of months ago when I was using the MLG 4.4 link and AT&T's "nxtgenphone" APN worked. Official 4.4 used the phone APN and I left it alone. About a week ago S Voice stopped working when I was using AT&T data but continued working fine over Wi-Fi. I pulled my hair out resetting S Voice and trying different versions; even the one from the SGS5. It still wouldn't work. I manually input the nxtgenphone APN and it started working again. So if you're having trouble with S Voice and are in a VoLTE market you might want to change/update your APN.
BarryH_GEG said:
I found out I was in a VoLTE market a couple of months ago when I was using the MLG 4.4 link and AT&T's "nxtgenphone" APN worked. Official 4.4 used the phone APN and I left it alone. About a week ago S Voice stopped working when I was using AT&T data but continued working fine over Wi-Fi. I pulled my hair out resetting S Voice and trying different versions; even the one from the SGS5. It still wouldn't work. I manually input the nxtgenphone APN and it started working again. So if you're having trouble with S Voice and are in a VoLTE market you might want to change/update your APN.
Click to expand...
Click to collapse
im betting that is what my issue is, can you give me the settings so I can make this apn?
BarryH_GEG said:
I found out I was in a VoLTE market a couple of months ago when I was using the MLG 4.4 leak and AT&T's "nxtgenphone" APN worked. Official 4.4 used the phone APN and I left it alone. About a week ago S Voice stopped working when I was using AT&T data but continued working fine over Wi-Fi. I pulled my hair out resetting S Voice and trying different versions; even the one from the SGS5. It still wouldn't work. I manually input the nxtgenphone APN and it started working again. So if you're having trouble with S Voice and are in a VoLTE market you might want to change/update your APN.
Click to expand...
Click to collapse
EDIT
Here's the Nxtgenphone APN...
I was just out of town in a non-VoLTE market and had to go back to the phone APN. When I got home, I changed to the nextgenphone APN but S Voice wouldn't work again. I have a Gear and I had to completely reset it along with removing Gear Manager in order to get S Voice working again. So whatever's trashing S Voice may have something to do with the Gear, VoLTE, or both. Not having S Voice on your phone over AT&T's data lines (vs. WiFi) pretty much renders the Gear useless. Do any of you having issues also have a Gear running off your phone?
BarryH_GEG said:
EDIT
Here's the Nxtgenphone APN...
I was just out of town in a non-VoLTE market and had to go back to the phone APN. When I got home, I changed to the nextgenphone APN but S Voice wouldn't work again. I have a Gear and I had to completely reset it along with removing Gear Manager in order to get S Voice working again. So whatever's trashing S Voice may have something to do with the Gear, VoLTE, or both. Not having S Voice on your phone over AT&T's data lines (vs. WiFi) pretty much renders the Gear useless. Do any of you having issues also have a Gear running off your phone?
Click to expand...
Click to collapse
Yes. This is what started me on his quest lol. My s voice has been working and then quit which rendered the watch pointless. So I have been trying to fix it for a few days now
I did download the update from here for Svoice,
http://www.sammobile.com/2014/03/24/download-samsungs-s-voice-app-from-the-galaxy-s5/
That seemed to help a bunch with the Svoice issues. But my phone still gets kicked off LTE and stuck at 4g where others that use ATT still show LTE. I can restart my phone and I will then have LTE service.
raiu said:
I did download the update from here for Svoice,
http://www.sammobile.com/2014/03/24/download-samsungs-s-voice-app-from-the-galaxy-s5/
That seemed to help a bunch with the Svoice issues. But my phone still gets kicked off LTE and stuck at 4g where others that use ATT still show LTE. I can restart my phone and I will then have LTE service.
Click to expand...
Click to collapse
It's an odd problem and not easy to isolate. When S Voice first died I thought it was related to the S Voice app itself. I tried the SGS5 update in your link right before the problem started and thought that was it. So I cleared data in the app via Settings and went back to the factory version and the N3-specific S Voice update that came out a few months ago. Didn't solve the problem - S Voice was fine over Wi-Fi but borked on AT&T data.
I remembered I was in a VoLTE market and tried the nxtgenphone APN and that solved the problem. All three versions of S Voice worked; original, N3 update, and SGS5 update. Everything was fine until I had to use the "phone" APN in a non-VoLTE market. S Voice worked fine until I got home to my VoLTE market and it stopped working again. This time, the nxtgenphone APN didn't help. I cleared data on S Voice again and tried all three versions and S Voice still wouldn't work.
Thinking it might be Gear related I deleted the Gear from BT settings, uninstalled Gear Manager from my phone, hard reset my Gear by long pressing the power button and using recovery, and rebuilding it via reset rather than using "restore" to reinstall my previous apps/settings. For some reason, the original and N3 update of S Voice wouldn't work. The SGS5 version did. At some point in the second "S Voice is broken" repair S Voice started to work on my phone but not the Gear.
So some combination of playing with the APN's, installing different versions of S Voice, and resetting the Gear, S Voice is working reliably again. What a pain in the ass. I'm guessing it's AT&T network related because its the only common denominator in both times S Voice started to fail and using the nxtgenphone APN fixed it the first time.
Same issue here (Samsung Note 3), ATT & Samsung are clueless
There is a significant amount of discussion of this issue in the att forums (I can't post links, but it's at https : // forums.att.com/t5/Android/S-Voice-now-Voice-talk-and-non-Wi-Fi-connection/m-p/4053580#M53935). I've been experiencing this for about four days now. S-Voice suddenly stopped working and returned "I can't find a network connection. Please connect to network and try again." This only happens on the AT&T data network; wi-fi works fine. When I called AT&T tech support last night, they actually knew about this issue but had nothing to offer me beyond the fact that it was a "known issue" and that "Samsung is working on a solution." They gave me the number for Samsung tech support, but those folks were less than helpful. At first, they pretended it was an issue with my phone and said I should send it in for repair. He said that there were no other reports of this issue from other users.
Then, when I mentioned that this issue is all over the Internet, the guy said "Well, we have had a 'significant' number of complaints about this, but not a high number." Every time I asked a question ("Do you have an SLA for a resolution?"), he put me on hold for five minutes and came back and asked irrelevant questions. ("So, you say this happened because of a software update?" "No, YOU said that.")
Finally, he said it was an Android issue and that Google is working on a fix.
I have downloaded the S5 version of S-Voice: apart from the ugly colors, it behaves exactly the same as the Note 3 version (i.e, works on wifi and does not work on the mobile network). I also tried changing the APN per the screenshot in this thread, but that did not change the situation.
As a workaround, I'm currently using "S for Switch Voice" (a buggy little app that switches to Google Search every time S-Voice is opened), but I'm really hoping this is fixed soon. Right now, all I'm seeing is finger pointing.
Avi-J said:
There is a significant amount of discussion of this issue in the att forums (I can't post links, but it's at https : // forums.att.com/t5/Android/S-Voice-now-Voice-talk-and-non-Wi-Fi-connection/m-p/4053580#M53935). I've been experiencing this for about four days now. S-Voice suddenly stopped working and returned "I can't find a network connection. Please connect to network and try again." This only happens on the AT&T data network; wi-fi works fine. When I called AT&T tech support last night, they actually knew about this issue but had nothing to offer me beyond the fact that it was a "known issue" and that "Samsung is working on a solution." They gave me the number for Samsung tech support, but those folks were less than helpful. At first, they pretended it was an issue with my phone and said I should send it in for repair. He said that there were no other reports of this issue from other users.
Then, when I mentioned that this issue is all over the Internet, the guy said "Well, we have had a 'significant' number of complaints about this, but not a high number." Every time I asked a question ("Do you have an SLA for a resolution?"), he put me on hold for five minutes and came back and asked irrelevant questions. ("So, you say this happened because of a software update?" "No, YOU said that.")
Finally, he said it was an Android issue and that Google is working on a fix.
I have downloaded the S5 version of S-Voice: apart from the ugly colors, it behaves exactly the same as the Note 3 version (i.e, works on wifi and does not work on the mobile network). I also tried changing the APN per the screenshot in this thread, but that did not change the situation.
As a workaround, I'm currently using "S for Switch Voice" (a buggy little app that switches to Google Search every time S-Voice is opened), but I'm really hoping this is fixed soon. Right now, all I'm seeing is finger pointing.
Click to expand...
Click to collapse
Unfortunately that doesn't work for us with the galaxy gear or gear 2. What ever happened has disabled the ability to use s voice on the gear and the ability to start calls using your voice.
raiu said:
Unfortunately that doesn't work for us with the galaxy gear or gear 2. What ever happened has disabled the ability to use s voice on the gear and the ability to start calls using your voice.
Click to expand...
Click to collapse
Have you completely removed the Gear from your phone and reset it using recovery? That's what fixed it for me the second time I had the issue. It only works with the SGS5 version of S Voice though.
BarryH_GEG said:
Have you completely removed the Gear from your phone and reset it using recovery? That's what fixed it for me the second time I had the issue. It only works with the SGS5 version of S Voice though.
Click to expand...
Click to collapse
mine works with the s5 svoice app update
raiu said:
mine works with the s5 svoice app update
Click to expand...
Click to collapse
I hate the SGS5 version of S Voice; especially in driving mode which I use a lot. It disables saying "Hi Galaxy" when the device is off which I also used heavily. I tried to downgrade again but you're right, the SGS5 version of S Voice is the only one that works. Hopefully a bunch of AT&T employees with N3's complain internally and AT&T's dev group gets off their asses and works with Samsung's dev group on a real solution.
BarryH_GEG said:
I hate the SGS5 version of S Voice; especially in driving mode which I use a lot. It disables saying "Hi Galaxy" when the device is off which I also used heavily. I tried to downgrade again but you're right, the SGS5 version of S Voice is the only one that works. Hopefully a bunch of AT&T employees with N3's complain internally and AT&T's dev group gets off their asses and works with Samsung's dev group on a real solution.
Click to expand...
Click to collapse
check the galaxy app store there a SE update and an Svoice update and it now works on ATT data
raiu said:
check the galaxy app store there a SE update and an Svoice update and it now works on ATT data
Click to expand...
Click to collapse
Thanks for that. I saw the security update yesterday but didn't think it would solve the problem so didn't play with S Voice after I installed it. AT&T must have done something security permissions wise on their network otherwise all carriers would have had S Voice issues which we know isn't the case. The S Voice app in Galaxy Apps is the one and only update the N3 received in January so that's not what fixed the problem.
Got my S7 on 3/9, activated, and everything was smooth. Yesterday, I discovered that my Google Voicemail no longer worked. My wife got a VZW Note 4 awhile back and the same thing happened to it. I fixed it pretty easily, just don't remember what I did. So, I googled it today and found stuff about disabling HD voice and dialing three numbers. The phone automatically activates HD Voice on activation and it cannot be disabled using the handset. I logged into my VZW account and removed it there. Dialed the three numbers: 1) *71(Google Voice Number) 2) *90(Google Voice Number) 3) *92(Google Voice Number) separately and sequentially with no success. Later, I had to remove the SD card, which means the SIM comes out too. When I put them back in, a message appeared in the notification drawer saying that HD voice has been enabled.
Seems like big red is forcing HD voice. Does this mean that using Google Voice for voicemail is no longer an option? Has anyone got it to work on their VZW S7?
Nevermind, I followed the instructions here: http://forum.xda-developers.com/showpost.php?p=60245435&postcount=12 and it now works - with HD Voice enabled.
When I initially dialed the *71(Google Voice Number), I dialed the access number listed. However, when I deactivated and reactivated, it told me to dial *71 & a different number. Apparently, this is where I went wrong.
All is good.
Hello,
Following the update to Android 8.0, Verizon visual voicemail on this Nexus 5X is no longer working. It worked previously. Verizon tech support is of no help. Apparently, they have no information whatsoever for the Nexus 5X. When I realized the Verizon tech was simply searching the internet looking for a solution, I ended the call.
I have uninstalled, and reinstalled the phone app. I've also tried turned visual voice mail on and off, and resetting the app defaults in the phone app settings.
In the phone app settings under the on/off switch for visual voicemail it says that visual voicemail is not yet activated and to try again later. This would lead one to believe this is an issue on the carrier side.
Thanks.
This is the case on LineageOS 16.0, OOS, and H2OS (the latter two the latest versions as of a few weeks ago). The Voicemail tab under Phone reports it can't activate visual voicemail. Does anyone have any suggestions or ideas?
Troubleshooting tried to no avail:
Spamming "Try Again" under the Voicemail tab
Toggling Visual Voicemail from Voicemail settings
Trying various WiFi APs and cellular
Changing Radio Band from Phone info to any other region
Putting the SIM into an iPhone for a minute, and then putting it back in the OP5
Installing the actual T-Mobile VVM app and then removing it
Other info:
This SIM was used in an iPhone SE, a Pixel XL, and then this OP5
I don't recall if VVM worked on the Pixel XL, but it definitely worked on the iPhone
My phone number is de-registered from Facetime/iMessage on Apple's end
IMS registration and both VoLTE and VoWIFI work fine
According to a T-Mobile tech support rep, this is a known issue for many (most) android devices.
Having the same issue. It's a new one (within past couple weeks) that possibly coincides with the super spammy texts I keep getting from T-Mobile telling me there's a new version of the Visual Voicemail app. Could possibly be something on their end.
I had a similar problem getting mine to work. Turns out when I tried Youmail it changed settings on my line. To correct it, within the Youmail app there was a way to deactivate it. That caused it to send three different codes through the dialer. When it was done i was able to use the tmo visual voicemail again
Apology if this has been discussed before as I cant find it when I search it on XDA.
Anyone whether on Global variant or Tmobile
if you use Google Voice the call redirection using the phone dialer apps wont work.
You need to initiate the call using Google Voice dialer itself.
Bluetooth connection with google voice also problematic.
Its been broken since Android 12 and still broken on android 13.
It works on Android 11, HOWEVER under Android 11 the Bluetooth having No connection issues with some devices like TILE Tracker, GLINet router and etc
These problems have been reported numerous time on Oneplus website however still No Fix.
If anyone has root guide to fix it Please feel free to post
Thank you