[Q] at&t using google voice voicemail with straight talk - AT&T Samsung Galaxy S6 Edge

I'm using straight talk on an at&t s6 edge. Trying to get the google voice voicemail to work. I've tried the mmi code **004*gmnumber# to activate conditional call forwarding, but I always get "couldn't get server response".. Trying to change the voicemail service provider also gives errors. "Can not read data. Network or sim error"
I have tried the individual mmi codes for different kinds of conditional call forwarding, but get same error:"couldn't get server response".
I have read that at&t controls the conditional call forwarding service, being the original carrier for straight talk, but because I don't have an active account, they can not change features for my number.
The ST rep tells me that there might be a hardware specific mmi code that Samsung may provide?
Does anyone have any solutions?
Thanks guys,
Gozirra

Gozirra, I was having a similar problem with my iPhone 6 (on AT&T) and my S6 (on Cricket). I think it may wind up being these phones (both are AT&T branded). I wound up swapping the sim card into a spare (Cricket branded) Moto G LTE and the MMI code worked without issue.

This exactly what I just did and it works. For months I have been trying to forward my Cricket voicemail to Google Voice, from Samsung S5. I couldn't. I called Cricket, they said there's nothing they can do. I then I saw gm2racer's post, used my sim card in my son's Samsung Prime. Voila.

Same issue here with S6 active + straight talk and with youmail as well.. invalid mmi.. straight talk says they dont support conditional forwarding, however 3 windows phones prior all worked on ST (both att and vzw phones)..
Frustrating enough i'm considering switching to tmobile (not willing to switch phones per say, i just got the s6)

I know this isnt the most hit thread on this topic, but today I resolved my issue... I have an AT&T (unlocked cause its older and paid for) Galaxy S6 (SM-G920A), that I simply plugged in the cricket SIM from my older Cricket phone and started using on their network. I got the immediate system text messages that reconfigured most of the call settings and the phone worked fine but in the past couple months, i keep getting complaints that i dont have voice mail set up from callers.
I did, I do, and I have used my google voice number for years now, and use it for my outbound calling (install the gv app and have it set outbound for all to GV). I also use GV as my mailbox... and I know how to use the **004 string to change forwarding (conditional, as in when you dont answer, cant answer, etc).
But with my AT&T S6 and the MM 6.0.1 (DQC1 official AT&T rom) - that 004 string wouldnt work. Neither would changing forwarding settings from the phone settings. They all state they cant talk to the server... and theres no option in my call settings for voicemail to set voice as the handler (versus your carrier).
So I was kind of stuck.. and here is what I did.
I flashed it using odin to the sm-g920aZ QB2 firmware (as in , the Cricket firmware for the S6, 6.0.1 MM version in March 2017).
I know.. it is taking a risk as some people state it doesent work.. some do.. well.. mine did. And since I have never tried to get root or do a custom OS, i am still official (thats all I have ever flashed, was official ROMs), and galaxy pay works, and the phone works, more or less perfectly from what I can tell. In fact, its got a TON less bloatware running a cricket ROM vs AT&T ROM.
And lo and behold, call forwarding works great now. And I actually got a firmware update notice from cricket 5 minutes after it was flashed.. and, well... all I can say is COOL.
I would probably stay with a MM (6.0.1) version of the ROM or match whatever you have now. I understand once you go to nougat, you cant go back to MM, and that may be true for moving between carrier ROMs also.. (cant go from Cricket 7 to at&t 6).
Anyhow.. Ive done a ton of research on this and thought since XDA helped out immensely (thanks everyone for posting roms and such), I would give ya'll a heads up that this worked for me.
I might go ahead and take those cricket firmware updates OTA. I know its a risk, as my phone is really a 920A (it shows as 920AZ now in settings also), but I really think its the exact same hardware... if I brick it I'll let ya'll know.

Confirmed, updates are good.
24br said:
I might go ahead and take those cricket firmware updates OTA. I know its a risk, as my phone is really a 920A (it shows as 920AZ now in settings also), but I really think its the exact same hardware... if I brick it I'll let ya'll know.
Click to expand...
Click to collapse
I let it go ahead and apply all of the recent Cricket updates to the S6 (920AZ) and confirmed its been running fine for 2 days now with no issues and no loss of functionality.
Makes me wonder what setting was changed by the cricket firmware - that allowed call forwarding to work properly and be set/reset/accessed by the device? The network and device didn't change, just the firmware.. but I dont see anything in the APN settings that relates to voice mail (maybe its something else that needs to change to allow CF settings?)
ANyhow.. your mileage may vary.. and Cricket firmware is WAY less bloated than AT&T for sure!

Related

N900A, T-Mobile ROM, and WiFi Calling/SMS...

Hello,
I just retired my venerable Samsung T699 Relay 4G (RIP QWERTY Keyboard) and, just picked up an unlocked, "refurbished" AT&T Note 3 for pretty cheap (it was sold as an "International" model, so I didn't know it was an AT&T version until I got it). I've had T-Mobile service for the last couple of years, and the big draw, for me, is WiFi calling/SMS; I've installed SafeStrap and been trying some T-Mobile ROMs, but can't seem to get WiFi calling to work. Obviously I've got a T-Mobile SIM card, and I've tried changing/adding APNs, and installing different builds of KitKat (some of which won't even boot - NB4 and NF9 seem to work best), but I still can't get it to work properly. I've been racking my brain and searching the Interspace for the last two weeks with no luck... what am I missing? Is it even possible?
Thanks in advance!
Hello,
As a fellow N900A user on Tmobile, I have been trying to get wifi calling as well.
I tried using a tmobile stock rom with wifi calling baked in (tweaked), but that did not work. I was told that I need to add an emergency 911 address, but even doing this did not do it.
I would think that wifi calling is doable, but something tells me that tmobile might be doing something similar to Verizon. Rumor was that Verizon had a list of IMEIs, and if your IMEI was not on their list, you couldn't bring the phone over to Verizon, even if it were CDMA capable (once again, this is rumor as I cannot confirm this is true).
The closest I have been to getting wifi calling through tmobile was having the settings show on the stock tmobile rom, but that was about it. Maybe someone in the forums has an answer/got it working, but I have yet to see one. I'll keep you posted if I somehow get it to work, but something tells me this won't happen for a while.
AresRising said:
Hello,
I just retired my venerable Samsung T699 Relay 4G (RIP QWERTY Keyboard) and, just picked up an unlocked, "refurbished" AT&T Note 3 for pretty cheap (it was sold as an "International" model, so I didn't know it was an AT&T version until I got it). I've had T-Mobile service for the last couple of years, and the big draw, for me, is WiFi calling/SMS; I've installed SafeStrap and been trying some T-Mobile ROMs, but can't seem to get WiFi calling to work. Obviously I've got a T-Mobile SIM card, and I've tried changing/adding APNs, and installing different builds of KitKat (some of which won't even boot - NB4 and NF9 seem to work best), but I still can't get it to work properly. I've been racking my brain and searching the Interspace for the last two weeks with no luck... what am I missing? Is it even possible?
Thanks in advance!
Click to expand...
Click to collapse
gangpe said:
Hello,
As a fellow N900A user on Tmobile, I have been trying to get wifi calling as well.
I tried using a tmobile stock rom with wifi calling baked in (tweaked), but that did not work. I was told that I need to add an emergency 911 address, but even doing this did not do it.
I would think that wifi calling is doable, but something tells me that tmobile might be doing something similar to Verizon. Rumor was that Verizon had a list of IMEIs, and if your IMEI was not on their list, you couldn't bring the phone over to Verizon, even if it were CDMA capable (once again, this is rumor as I cannot confirm this is true).
The closest I have been to getting wifi calling through tmobile was having the settings show on the stock tmobile rom, but that was about it. Maybe someone in the forums has an answer/got it working, but I have yet to see one. I'll keep you posted if I somehow get it to work, but something tells me this won't happen for a while.
Click to expand...
Click to collapse
Yeah, considering I have zero service with any provider where I live (but 4G LTE 100 yards down the street), WiFi services were the single reason I went with T-Mobile. Considering the Unlocking Bill, one wouldn't think a carrier could block IMEIs from being used on another carrier... but I have a hard time reading the fine print, so there is that.
I've tried several of the stock T-Mobile ROMs, and while WiFi calling was there, it simply wouldn't enable; it would try to enable, but never would. Have you contacted T-Mobile and asked if there are any potential fixes? I'm considering doing that, but am worried that they'll say "Oh, that's your IMEI, looks like you can't use it on our network SORRYABOUTYOURLUCK!"
I have contacted tmobile about this before.
Their response was that they did not know why it did not work. They helped me set up the emergency 911 address, but they said when it comes to other hardware they couldn't give me a reason why it wouldn't work.
I remember dwetherill (sp?) mention that some n900a users were able to get wifi calling on their phones. I don't know if the modem can/will affect wifi calling, but at this point it's the easier thing to test.
I'm on the NJ5 modem - I might try testing out NC2.
Have you tried carl's TMB version of the norma stable rom? Check it out if you haven't. Wifi calling is supposed to connect automatically. I haven't seen it work yet, but I'll keep you posted if somehow I get it to work.
AresRising said:
Yeah, considering I have zero service with any provider where I live (but 4G LTE 100 yards down the street), WiFi services were the single reason I went with T-Mobile. Considering the Unlocking Bill, one wouldn't think a carrier could block IMEIs from being used on another carrier... but I have a hard time reading the fine print, so there is that.
I've tried several of the stock T-Mobile ROMs, and while WiFi calling was there, it simply wouldn't enable; it would try to enable, but never would. Have you contacted T-Mobile and asked if there are any potential fixes? I'm considering doing that, but am worried that they'll say "Oh, that's your IMEI, looks like you can't use it on our network SORRYABOUTYOURLUCK!"
Click to expand...
Click to collapse
gangpe said:
I have contacted tmobile about this before.
Their response was that they did not know why it did not work. They helped me set up the emergency 911 address, but they said when it comes to other hardware they couldn't give me a reason why it wouldn't work.
I remember dwetherill (sp?) mention that some n900a users were able to get wifi calling on their phones. I don't know if the modem can/will affect wifi calling, but at this point it's the easier thing to test.
I'm on the NJ5 modem - I might try testing out NC2.
Have you tried carl's TMB version of the norma stable rom? Check it out if you haven't. Wifi calling is supposed to connect automatically. I haven't seen it work yet, but I'll keep you posted if somehow I get it to work.
Click to expand...
Click to collapse
I'm on NC2, and haven't gotten anything to work as of yet... I've been looking for modem threads, but I guess I need to look a little harder. I'll search that ROM out and give it a shot, and let you know if it works with NC2. Thanks for the heads-up! :good:
So I tried NC2 modem, and it is not allowing for wifi calling.
I went to tmobile yesterday to get another line added. Rumor on the tmobile side is that AT&T is working to get wifi calling setup for the n900a's by around April. Take it as a rumor at this point, seeing how it came from tmobile, but the rep made a good point - AT&T tends to follow what tmobile is doing, so who knows.
Here's to hoping they're right.
BTW, I went to the note 4 tmobile forums, and I grabbed a deodexed stock rom. I noticed that there were a few files related to wifi calling (had WFC in the name). I tried playing around with it last night, and I managed to get the settings. It will even go so far as to turn the phone GSM radio off when you select wifi only. It's doing what Tweaked was doing for me (which was keeping the wifi calling option grayed out (enabling). I think I'm still missing a few files to get it to work, but I'll keep playing around with it later and let you know if I have any success.
AresRising said:
I'm on NC2, and haven't gotten anything to work as of yet... I've been looking for modem threads, but I guess I need to look a little harder. I'll search that ROM out and give it a shot, and let you know if it works with NC2. Thanks for the heads-up! :good:
Click to expand...
Click to collapse
gangpe said:
So I tried NC2 modem, and it is not allowing for wifi calling.
I went to tmobile yesterday to get another line added. Rumor on the tmobile side is that AT&T is working to get wifi calling setup for the n900a's by around April. Take it as a rumor at this point, seeing how it came from tmobile, but the rep made a good point - AT&T tends to follow what tmobile is doing, so who knows.
Here's to hoping they're right.
BTW, I went to the note 4 tmobile forums, and I grabbed a deodexed stock rom. I noticed that there were a few files related to wifi calling (had WFC in the name). I tried playing around with it last night, and I managed to get the settings. It will even go so far as to turn the phone GSM radio off when you select wifi only. It's doing what Tweaked was doing for me (which was keeping the wifi calling option grayed out (enabling). I think I'm still missing a few files to get it to work, but I'll keep playing around with it later and let you know if I have any success.
Click to expand...
Click to collapse
I wonder how that would work regarding using a T-Mobile SIM in the AT&T phone, and if it could support cross-carrier features like that.
You're a braver soul than I, that's for sure. If I knew anything about what I was looking at/for, I'd be more than willing to help get this nut cracked... otherwise, I look forward to your findings!

Wifi calling problem

Both my dad and I picked up the Note 8 on launch day. I had zero issue enabling wifi calling out of the box, and in fact it seems to be working quite well for me. He's not had the same success. At first it said it would have to disable Google Voice. We uninstalled the app, and had Sprint de-integrate his number with Google Voice, so that the carrier stock voicemail could be configured. That didn't work initially either, and he spent some time at the store having their tech fix it. I wasn't there, so I'm not sure what they did, but eventually they got the voicemail working. So then he came around asking me to set up wifi calling. I attempted to, only this time the setup prompt insisted that it be allowed to disable Voicemail first. But since that's a system app, I'm not sure how that can be done. And given his problems with voicemail to date, I'm reticent to let it try and disable his voicemail again.
Anybody else run into this problem? Is there some sort of fix that doesn't involve another visit to Sprint?
beerindex said:
Both my dad and I picked up the Note 8 on launch day. I had zero issue enabling wifi calling out of the box, and in fact it seems to be working quite well for me. He's not had the same success. At first it said it would have to disable Google Voice. We uninstalled the app, and had Sprint de-integrate his number with Google Voice, so that the carrier stock voicemail could be configured. That didn't work initially either, and he spent some time at the store having their tech fix it. I wasn't there, so I'm not sure what they did, but eventually they got the voicemail working. So then he came around asking me to set up wifi calling. I attempted to, only this time the setup prompt insisted that it be allowed to disable Voicemail first. But since that's a system app, I'm not sure how that can be done. And given his problems with voicemail to date, I'm reticent to let it try and disable his voicemail again.
Anybody else run into this problem? Is there some sort of fix that doesn't involve another visit to Sprint?
Click to expand...
Click to collapse
If you are having issues with things not working on Sprint, I first had to factory reset...all was well afterwards...make sure you have a brand new SIM for the Note 8...is it a Sprint or Unlocked device (SM-N950U or SM-950U1)
BlueFox721 said:
If you are having issues with things not working on Sprint, I first had to factory reset...all was well afterwards...make sure you have a brand new SIM for the Note 8...is it a Sprint or Unlocked device (SM-N950U or SM-950U1)
Click to expand...
Click to collapse
It is a N950U from Sprint with carrier lock.
beerindex said:
It is a N950U from Sprint with carrier lock.
Click to expand...
Click to collapse
Coolness, factory reset is probably the best...unless it is because of a previously used SIM
I have an unlocked note 8 (US) on Verizon, and no wifi calling at all.
WiFi Calling on Verizon?
bovineyard said:
I have an unlocked note 8 (US) on Verizon, and no wifi calling at all.
Click to expand...
Click to collapse
Same here. I bought mine directly from Samsung and just found out that the option to select WiFi calling is missing! I rely on this at home because we live in a valley with poor cell phone reception (I have to step to a front window to make/receive calls without WiFi calling).
jeffp25 said:
Same here. I bought mine directly from Samsung and just found out that the option to select WiFi calling is missing! I rely on this at home because we live in a valley with poor cell phone reception (I have to step to a front window to make/receive calls without WiFi calling).
Click to expand...
Click to collapse
You can flash Verizon firmware if you want WiFi calling on Verizon...but some users have successfully had it added to the unlocked version by calling Verizon and adding their imei to Verizon database....search the threads if you need...
BlueFox721 said:
You can flash Verizon firmware if you want WiFi calling on Verizon...but some users have successfully had it added to the unlocked version by calling Verizon and adding their imei to Verizon database....search the threads if you need...
Click to expand...
Click to collapse
Thanks. I tried searching the threads but didn't find much. Maybe I need to change how I'm searching. If I do need to "flash the Verizon firmware," where can I find instructions and will it add bloat or reduce the functionality in any way (I wanted non-Verizon because of the way Verizon changed features on my Note 5)? Will flashing the firmware interfere with the Samsung support?
jeffp25 said:
Thanks. I tried searching the threads but didn't find much. Maybe I need to change how I'm searching. If I do need to "flash the Verizon firmware," where can I find instructions and will it add bloat or reduce the functionality in any way (I wanted non-Verizon because of the way Verizon changed features on my Note 5)? Will flashing the firmware interfere with the Samsung support?
Click to expand...
Click to collapse
You can flash Verizon firmware with Odin using this guide:
https://forum.xda-developers.com/ga...k-recovery-odin-recovery-software-t3671615...
Some Samsung features are blocked by carriers...I do not know what Verizon blocks...search is better from pc
BlueFox721 said:
You can flash Verizon firmware with Odin using this guide:
https://forum.xda-developers.com/ga...k-recovery-odin-recovery-software-t3671615...
Some Samsung features are blocked by carriers...I do not know what Verizon blocks...search is better from pc
Click to expand...
Click to collapse
I called Samsung tech support and they confirmed that this feature is not in the based version of Android but the ones distributed by the carriers. The tech suggested calling Verizon and asking them to install the firmware. Anyone know if (assuming they agree) this will be the full package, including all the bloatware, and if this will remove any features from the phone? Would the "upgrade" wipe out the phone so that I have to set everything up again?
When I bought my Note 5 from Verizon two years ago I was upset to find that they had removed the PDF signing capability that was a big feature of the Note 5. I'd really hate to lose any features on my new Note 8, after all that's why I bought directly from Samsung.
jeffp25 said:
I called Samsung tech support and they confirmed that this feature is not in the based version of Android but the ones distributed by the carriers. The tech suggested calling Verizon and asking them to install the firmware. Anyone know if (assuming they agree) this will be the full package, including all the bloatware, and if this will remove any features from the phone? Would the "upgrade" wipe out the phone so that I have to set everything up again?
When I bought my Note 5 from Verizon two years ago I was upset to find that they had removed the PDF signing capability that was a big feature of the Note 5. I'd really hate to lose any features on my new Note 8, after all that's why I bought directly from Samsung.
Click to expand...
Click to collapse
In order for you to remain on unlocked firmware to avoid bloat and keep Samsung goodies you must call Verizon to have the imei # to their whitelist and reprovisioned...I did this for Sprint to enable VoLTE when available...others with Verizon have done the same...call Verizon cs and tell them you bought from Samsung and need to have your imei # whitelisted and reprovisioned to improve network connection...if one rep will not do it, call another...do not mention that it is unlocked version...just state that you got from Samsung on a Note 7 deal...afterwards, all Verizon features will work on unlocked except vvm...Google voice is better anyways
BlueFox721 said:
In order for you to remain on unlocked firmware to avoid bloat and keep Samsung goodies you must call Verizon to have the imei # to their whitelist and reprovisioned...I did this for Sprint to enable VoLTE when available...others with Verizon have done the same...call Verizon cs and tell them you bought from Samsung and need to have your imei # whitelisted and reprovisioned to improve network connection...if one rep will not do it, call another...do not mention that it is unlocked version...just state that you got from Samsung on a Note 7 deal...afterwards, all Verizon features will work on unlocked except vvm...Google voice is better anyways
Click to expand...
Click to collapse
If I get them to add my imei to the whitelist and "reprovision" the phone, when they do that the option for WiFi calling will appear?
I'm slightly puzzled by your vvm comment: will all Verizon voicemail be non-functional or only Visual Voicemail? I have Google Voice set up to provide a second number on my phone. How do I use it to set up voice mail on my phone with my Verizon number?
jeffp25 said:
If I get them to add my imei to the whitelist and "reprovision" the phone, when they do that the option for WiFi calling will appear?
I'm slightly puzzled by your vvm comment: will all Verizon voicemail be non-functional or only Visual Voicemail? I have Google Voice set up to provide a second number on my phone. How do I use it to set up voice mail on my phone with my Verizon number?
Click to expand...
Click to collapse
VVM is only on carrier Firmware...it is baked in...some have gotten it to work on unlocked but I do not know how...regular voicemail works fine...especially with Google voice...to set it up you forward to Google voice...for Sprint it is dialing *73mygooglevoicenumber...I do not know the forward shortcut for verizon but it used to be *71yourgooglevoicenumber...
Your Google voice number is shown in the settings of Google voice.
Yes WiFi calling and VoLTE will work once imei is added...look for WiFi calling in the phone settings...
BlueFox721 said:
VVM is only on carrier Firmware...it is baked in...some have gotten it to work on unlocked but I do not know how...regular voicemail works fine...especially with Google voice...to set it up you forward to Google voice...for Sprint it is dialing *73mygooglevoicenumber...I do not know the forward shortcut for verizon but it used to be *71yourgooglevoicenumber...
Your Google voice number is shown in the settings of Google voice.
Yes WiFi calling and VoLTE will work once imei is added...look for WiFi calling in the phone settings...
Click to expand...
Click to collapse
OK, I'll have to try and reach them. I'll follow up with my results later.
No luck with today's call
BlueFox721 said:
VVM is only on carrier Firmware...it is baked in...some have gotten it to work on unlocked but I do not know how...regular voicemail works fine...especially with Google voice...to set it up you forward to Google voice...for Sprint it is dialing *73mygooglevoicenumber...I do not know the forward shortcut for verizon but it used to be *71yourgooglevoicenumber...
Your Google voice number is shown in the settings of Google voice.
Yes WiFi calling and VoLTE will work once imei is added...look for WiFi calling in the phone settings...
Click to expand...
Click to collapse
First, I found the Google Voice shortcut for Verizon is what you thought: *71yourgooglevoicenumber
Now for my bad news. I spent nearly an hour on the phone with Verizon tech support. After being bounced around a little, I spoke with a woman who kept contacting their "Network Team" for more details, and who tried to be very helpful, but in the end I am no further ahead. In the end, they said that adding my phone to the Whitelist was "Out of Scope" because the phone was already unlocked and functioning on Verizon. She said that all she could suggest was to contact Samsung, and that Verizon tech support would be happy to have a three-way conference call with Samsung tech support (they would call) to see what could be done, and that she'd put a note in my account about this issue.
Now, if I call back and try to speak to anyone else they will see this note that that will be it. So, I'm back to not being able to make phone calls at home.
jeffp25 said:
First, I found the Google Voice shortcut for Verizon is what you thought: *71yourgooglevoicenumber
Now for my bad news. I spent nearly an hour on the phone with Verizon tech support. After being bounced around a little, I spoke with a woman who kept contacting their "Network Team" for more details, and who tried to be very helpful, but in the end I am no further ahead. In the end, they said that adding my phone to the Whitelist was "Out of Scope" because the phone was already unlocked and functioning on Verizon. She said that all she could suggest was to contact Samsung, and that Verizon tech support would be happy to have a three-way conference call with Samsung tech support (they would call) to see what could be done, and that she'd put a note in my account about this issue.
Now, if I call back and try to speak to anyone else they will see this note that that will be it. So, I'm back to not being able to make phone calls at home.
Click to expand...
Click to collapse
You may be stuck with flashing complete firmware...you can always root the complete firmware and debloat...sorry it's not working for you
BlueFox721 said:
You may be stuck with flashing complete firmware...you can always root the complete firmware and debloat...sorry it's not working for you
Click to expand...
Click to collapse
For now, I have a partial solution for the poor phone connection at home: years ago, after we had complained a lot about a poor signal at home, Verizon gave us a free "Network extender," which acts as a mini tower in our house (connected through the house Internet). It is only 3G, so I disconnected it when we had WiFi calling on our phones. Now, I'll reconnect it. The only problem is that is won't connect to a phone with VoLTE calling enabled, so I have to remember to turn off VoLTE calling when I get home, and turn it back on when I leave so that I can keep my Internet access on a phone call.

Nexus 6, T-Mobile and MMS problem

This has been a frustrating issue. My wife and I both have Nexus 6 phones. She has the 32gb & I have the 64gb version. Hers recently started not receiving MMS messages. Anything with a large picture would simply never show up. Anything with a very small graphic or group text would show up as "Non-text content". Here are the steps we've taken to solve this:
1. TMO started by insisting it was an APN issue. So she edited her APN. Didn't help.
2. We then swapped SIMs. Hmmmm. My phone then behaved like hers while hers could then send/receive MMS.
3. TMO said ok maybe it's the SIM. They sent us a new one. SAME result. Her phone wouldn't receive MMS.
4. Out of frustration, I factory reset her phone and reset the APN info. Didn't help. (Cleaned up her phone of some trash programs though. :laugh
5. TMO engineering says they still can't find anything on their end. Elevate to tech supervisor. She tells us to go a TMO store (right near us) to try a THIRD SIM. OK, we do. SAME RESULT. We tried swapping SIMs around again and the same thing happens. My SIM in her phone, everything works. Her SIM in mine, I can't receive MMS.
6. TMO store guy suggests MAYBE (but unlikely) that there is something her account has that's stored on the SIM when its activated that causes the phone to freak. Also says it's above his pay grade .
So now we are again waiting on TMO to poke around further on their end. My question for all you smart types here is:
Has anyone ever heard of this issue? Is there anything you know of that could be causing it? I think it's a bad provisioning somewhere in the dark recesses of TMO. The ONLY change we made to our plans (which seems just coincidental) is that we moved from the 2 lines Unlimited for $100 plan to the over-55 Unlimited plan. We did this maybe 3 weeks ago. But the features are all the same on both plans.
We are both on the same Android 7.0 final OTA firmware updates from Google. NBD92G
Would there be ANY chance that a sideload firmware update would make any difference? We're getting desperate here. Any & all suggestions welcome.
I wonder if her SIM is configured for wifi calling. There has been a conflict between wifi calling and mms for awhile. I've seen it reported several times where this T-Mobile forum post helps in that case
Don't use old firmware... I had issues on certain custom ROMs and old firmware where MMS wouldn't work over WiFi. Never as bad as you were getting.
If you wanna stay stock, sideload the latest OTA to go to NGI55D. Anything older than that is vulnerable to Blueborne exploit, which is a HUGE security concern IMO. I can confirm MMS is working correctly (even with WiFi enabled) on bone stock NGI55D as well as custom ROM Dirty Unicorns v11.7.1 which includes September security patch.
ktmom said:
I wonder if her SIM is configured for wifi calling. There has been a conflict between wifi calling and mms for awhile. I've seen it reported several times where this T-Mobile forum post helps in that case
Click to expand...
Click to collapse
I've had this issue on most LOS roms. i ended up making a custom APN i flash when i try a rom built on LOS.
Yeah, it sure sounds like a problem with account partitioning, or something else with the account that gets associated with the SIM on initial use. What if you try the problem SIM in a phone that is not a Nexus 6? I wonder if you could get a new sim and set it up in a different phone, then transfer it to the problem phone?
OK all, finally got a TMO engineer who agreed with my assessment -- that it was a hidden provisioning problem. She nuked my wife's line and recreated it from scratch. Everything works great now. Frustrating that we had to go through about 15 phone calls and over 3 hours of phone time to get it resolved.
RealSkier said:
OK all, finally got a TMO engineer who agreed with my assessment -- that it was a hidden provisioning problem. She nuked my wife's line and recreated it from scratch. Everything works great now. Frustrating that we had to go through about 15 phone calls and over 3 hours of phone time to get it resolved.
Click to expand...
Click to collapse
Glad they figured this out.

Pixel 5 and Tmobile, don't do it.

3 days ago I received the Pixel 5 for my girlfriend. She had an old iPhone and she was interested in switching to Android. After doing so and activating service I've just come to realize that Sprint/tmobile does not support it. I've spent 3 hours tonight talking to sprints technical support about 2 issues.
1. She cannot send or receive MMS picture messages.
2. Visual voicemail does not work through the Phone, Sprint, or Tmobile apps.
After several hours of troubleshooting the guy on the phone said he was surprised I was able to get any service working at all. We all gave up at that point. My girlfriend is currently on a family plan with her parents and they are moving to Verizon next month. I want her to keep the pixel 5 but she needs to send MMS messages for work. I don't think she will want to wait a month to use her phone as it was intended, also if she does keep the phone I might have to factory reset it, reflash, and reroot the phone with the Verizon boot image provided by Google. I feel bad for her because this is her first experience with Android and it hasn't been fun for her.
Is there anyway to get MMS messages working? I've tried editing the APN settings but it's defined by the carrier and not available in the network settings(you have to dial the carrier code to view them and need a password to edit).
Any suggestions?
JordanFromIT said:
3 days ago I received the Pixel 5 for my girlfriend. She had an old iPhone and she was interested in switching to Android. After doing so and activating service I've just come to realize that Sprint/tmobile does not support it. I've spent 3 hours tonight talking to sprints technical support about 2 issues.
1. She cannot send or receive MMS picture messages.
2. Visual voicemail does not work through the Phone, Sprint, or Tmobile apps.
After several hours of troubleshooting the guy on the phone said he was surprised I was able to get any service working at all. We all gave up at that point. My girlfriend is currently on a family plan with her parents and they are moving to Verizon next month. I want her to keep the pixel 5 but she needs to send MMS messages for work. I don't think she will want to wait a month to use her phone as it was intended, also if she does keep the phone I might have to factory reset it, reflash, and reroot the phone with the Verizon boot image provided by Google. I feel bad for her because this is her first experience with Android and it hasn't been fun for her.
Is there anyway to get MMS messages working? I've tried editing the APN settings but it's defined by the carrier and not available in the network settings(you have to dial the carrier code to view them and need a password to edit).
Any suggestions?
Click to expand...
Click to collapse
I am using my Pixel 5 just fine on T-Mobile, just plugged in my old SIM, and good to go. This might be more of an Apple thing, did she unregister her number with iMessage. Her MMS messages might be going there?
amaddux said:
I am using my Pixel 5 just fine on T-Mobile, just plugged in my old SIM, and good to go. This might be more of an Apple thing, did she unregister her number with iMessage. Her MMS messages might be going there?
Click to expand...
Click to collapse
We tried but it says her number is not linked to imessage.
Can't really offer much here but to say the pixel 5 works perfectly on T-Mobile. Has to be something else on your end that's not working correctly, simple advice you've likely done is check APNs, make sure they are configured properly. You can add a new apn if needed. Take a ride down to the T-Mobile store, grab a new sim just to be on the latest...R15 I believe in case somehow the sprint sim isn't playing nicely plus the R15 you'll be able to access TMobile's SA 5G if it's in your area.
Lastly, your title is BS, you're having an issue, not an issue with the pixel 5 and T-Mobile, as said, they work fine together.
your problem is Sprint, not the phone.
drop Sprint like the bad habit it is. If you need cheap, go with Mint Mobile.
well Tmobile is working like a smooth butter for my pixel 5
T-Mobile works flawlessly for me on the Pixel 5. It sounds like you're using Sprint, though.

SM-G973U VoLTE

I recently bought an unlocked Galaxy S10 SM-G973U on Amazon. Got new SIM card from a Verizon MVNO and activated phone. The phone downloaded Android 12, One UI version 4.0. Firmware Build number SP1A210812.016.G973USQS6HVA1. Service provide Software version SAOMC_SM-G973U_OYN_SPR_12_0007 SPR/XAA/VZW. The problem is there is no menu option to activate/switch on VoLTE which means when I'm on a call there is no internet. I've talked to the MVNO tech support multiple times and was told they couldn't see any problems on their side, or that the SM-G973U does not support VoLTE which is not true. I found on one of AT&T's sites that the SM-G973U needs a software patch to enable VoLTE. I also found a couple of USSD codes but they either didn't work or didn't get me to the right setup screen to turn on VoLTE. I even stopped by a Samsung store and they weren't any help either. They said they could re-flash a stock firmware but it would revert to being locked to a carrier which is apparently also not true based on what I've read on this forum. Anyone know how I can turn on VoLTE or know of an apk file or software patch to enable VoLTE?? Does one of the firmware versions posted online have the patch to turn on VoLTE??
I think the issue is that your phone is showing SPR/XAA/VZW. You say you're on a verizon MVNO (who, by the way?)... but your phone isn't seeing that. It's actually saying it's active for SPRint. The second one, XAA, means it's not able to detect the SIM type... and the third was that it was originally VZW, which you can't change and isn't really relevant. (That's just what the phone was "born" as).
Bottom line, your phone isn't seeing VZW or an MVNO as the active CSC nor the SIM card. In the past, the easy thing was to change the CSC to what you need, but I haven't found a way to do that actively. What's supposed to happen is that the CSC should update based on the SIM card and cell signal you're getting... but this doesn't always happen. I bought two phones - one switched with no issues, the other I could not get it to change no matter what I tried.
That said, the easiest thing is to clean flash the phone with ODIN to a VZW or your MVNO's ROM, so that (hopefully) the CSC updates automatically. You could also consider flashing a U1 (unlocked) ROM, as yours is not technically an unlocked ROM (U means it's a carrier ROM... which may be why it's not switching over?)
Again, I tried all of these on the second phone I bought, and nothing would switch it (my carrier is Total Wireless, which is a VZ MVNO, and actually shows up as Tracfone (TFN). I had to return that second phone and get another with TFN already activated, and that worked fine... so be sure you do this before you drop out of your return period.
Bottom line, you should be able to get this all working... my VOLTE/VOWIFI works fine... just a matter of getting you there.
Thanks. My carrier is Straight Talk which is now VZ. The SIM card they sent me has the wording "Verizon Compatible" written on it. I finally found a document that explains how to interpret the CSC codes and your explanation clarifies my understanding of it. Sound like I'll have to re-flash it. Since it was originally a VZW phone I'm thinking I should flash it back to VZW to see if that works before trying U1.
Dumb question as this is my first time flashing a phone. (I've flashed quite a few other things but never had to worry about CSC codes and bootloader versions, etc.) I don't see VZW firmware on samfirms or sammobile. I see Sprint, T-Mobile, and one listed as USA without carrier info but I don't see one for VZW. Can someone point me to the correct location to download SM-g973U and U1 firmware for VZW? Greatly appreciated and thanks for putting up with my lack of knowledge!
Edited: Found the files on sammobile. Will try the U1 (VZW) first. I'll keep my fingers crossed.
schwinn8 said:
I think the issue is that your phone is showing SPR/XAA/VZW. You say you're on a verizon MVNO (who, by the way?)... but your phone isn't seeing that. It's actually saying it's active for SPRint. The second one, XAA, means it's not able to detect the SIM type... and the third was that it was originally VZW, which you can't change and isn't really relevant. (That's just what the phone was "born" as).
Bottom line, your phone isn't seeing VZW or an MVNO as the active CSC nor the SIM card. In the past, the easy thing was to change the CSC to what you need, but I haven't found a way to do that actively. What's supposed to happen is that the CSC should update based on the SIM card and cell signal you're getting... but this doesn't always happen. I bought two phones - one switched with no issues, the other I could not get it to change no matter what I tried.
That said, the easiest thing is to clean flash the phone with ODIN to a VZW or your MVNO's ROM, so that (hopefully) the CSC updates automatically. You could also consider flashing a U1 (unlocked) ROM, as yours is not technically an unlocked ROM (U means it's a carrier ROM... which may be why it's not switching over?)
Again, I tried all of these on the second phone I bought, and nothing would switch it (my carrier is Total Wireless, which is a VZ MVNO, and actually shows up as Tracfone (TFN). I had to return that second phone and get another with TFN already activated, and that worked fine... so be sure you do this before you drop out of your return period.
Bottom line, you should be able to get this all working... my VOLTE/VOWIFI works fine... just a matter of getting you there.
Click to expand...
Click to collapse
Success! Was able to flash U1. VoLTE is now working. The CSC now shows TFN/TFN/VZW. Much appreciated!!!
Awesome, glad to hear that fixed it easily!
And TFN... I'm a fan there, too!
Hi! I'm having a similar issue with the same model and happy to see someone was able to enable VoLTE. However, most of what you said above is a foreign language to me. Would one of you be willing to give me a crash course in what you did?
Here's my specific situation. Last week (~1/4/23) Tracfone shutdown 3G. My Samsung Galaxy S10 (SM-G973U) says my network is set to LTE/3G/2G. I've read LTE is 4G, but still can't make or receive calls/texts, but data and 911 calls still work. Their tech support is no help.
From reading online it sounds like I may need VoLTE, not just LTE. Hence finding this thread. If one of you would be willing to spare some time to walk me through what you did I'd really appreciate it. In the mean time I'll try to figure out what "flashing" mean in a context that doesn't involve showing body parts
Thank you in advance!!
I'm on Tracfone (they were bought out by Verizon, BTW) - I was on Total Wireless before, which is now Total by Verizon. You might try contacting support again, as they are now VZ, and may have more help to offer.
My S10+ is running 975U1 now, and it works for VOLTE/VOWIFI properly. You may consider getting a U1 ROM installed, and maybe even the VZW (or TFN) version if available - that may get you working.
Did VOLTE ever work for you before on this or any other carrier? What is your CSC right now?
schwinn8 said:
I'm on Tracfone (they were bought out by Verizon, BTW) - I was on Total Wireless before, which is now Total by Verizon. You might try contacting support again, as they are now VZ, and may have more help to offer.
My S10+ is running 975U1 now, and it works for VOLTE/VOWIFI properly. You may consider getting a U1 ROM installed, and maybe even the VZW (or TFN) version if available - that may get you working.
Did VOLTE ever work for you before on this or any other carrier? What is your CSC right now?
Click to expand...
Click to collapse
Thanks for replying! I'm not entirely sure if VoLTE has worked previously. I bought this phone 6/2021 and have only haver had tracfone service for it. I did find in my setting that VoLTE calling is set to on so it seems like it should work. Of note, the 4Glte in my status bar has always been grayed out (I went back and looked at some old screenshots).
My current CSC is VZW/XAA/ATT.
I spoke with tracfone customer service yesterday and they had me reset my network setting and now I don't even have data and the 4Glte in my status bar that was previously gray has now completely disappeared.
Their customer service refuses to talk to me now (literally no one answers when it transfers to an agent) or they hang up on me, and no I haven't been rude, but I have told them I'm recording the call.
I bought a mint mobile package last night because I'm beyond frustrated with Tracfone. I'm worried I'll have the same problems with Mint. I'm not sure if my settings are screwed up or if it's just Tracfone. In any case things are worse now after talking to customer service yesterday.
I also notice there was no APN setting on my phone so I updated it today and restarted but no difference.
Thanks for any input!! Much appreciated. Sorry for the novel.
Ok, so based on your CSC, the phone is not seeing the SIM's carrier - it's showing XAA which means it's using the default settings, which is probably why your not getting VOLTE. The active CSC of "VZW" may be ok... depends on which carrier you're on with Tracfone. I think they're VZW only, but I'm not completely sure.
You may want to just get a new SIM card and get that activated. HOWEVER, the problem you'll likely face is that the phone was born ATT (last CSC). This means the IMEI won't match a "compatible" phone to Verizon, and they will flat out refuse to activate it (even though WE al know it will work fine). If you still want to do that, you will have to activate the new SIM on a VZ "compatible" phone, then you can swap it to the S10. Note that VZ complains about this when you talk to them... so don't tell them you're doing this... but I've done it many times and it works fine.
If your actual behind-the-scenes carrier is ATT, then you can do the activation with your phone without issue.
If none of this works for you, you can switch carriers to an ATT MVNO and you should be good to go.
schwinn8 said:
Ok, so based on your CSC, the phone is not seeing the SIM's carrier - it's showing XAA which means it's using the default settings, which is probably why your not getting VOLTE. The active CSC of "VZW" may be ok... depends on which carrier you're on with Tracfone. I think they're VZW only, but I'm not completely sure.
You may want to just get a new SIM card and get that activated. HOWEVER, the problem you'll likely face is that the phone was born ATT (last CSC). This means the IMEI won't match a "compatible" phone to Verizon, and they will flat out refuse to activate it (even though WE al know it will work fine). If you still want to do that, you will have to activate the new SIM on a VZ "compatible" phone, then you can swap it to the S10. Note that VZ complains about this when you talk to them... so don't tell them you're doing this... but I've done it many times and it works fine.
If your actual behind-the-scenes carrier is ATT, then you can do the activation with your phone without issue.
If none of this works for you, you can switch carriers to an ATT MVNO and you should be good to go.
Click to expand...
Click to collapse
OK some of that was still over my head. I'll see what happens with the Mint Sim... one f/u question now though. You said the ATT means my phone was "born" ATT. I bought my phone off backmarket and it was sold as "unlocked". Was that not true? How can I be sure in the future if I buy a used phone that's not from my carrier that it will actually be compatible?
Unlocked just means it's not locked to a carrier. That is true in your case, otherwise you wouldn't have been able to install ANY non-ATT SIM. So, you did the right thing to get an unlocked phone, and that is what you got.
The issue with compatibility is just the asshole carriers spreading lies. They do this to try to get people to buy THEIR phones, for no reason other than to make money and confuse consumers. The "born" CSC has no bearing on anything, really... neither does the carrier-specified IMEI. In your case, the XAA is good, which means it's a multi-carrier ROM, which works with all USA carriers.
Mint is a good idea - being an ATT carrier (IIRC), that should work and they should help you get it up and running even if they have to activate it. Good luck!
Awesome! Fingers crossed!! Thank you for your time and all the info❣
I'll try to remember to give an update in a few weeks for future readers
Goldie8709 said:
Awesome! Fingers crossed!! Thank you for your time and all the info❣
I'll try to remember to give an update in a few weeks for future readers
Click to expand...
Click to collapse
UPDATE: Switching to Mint worked like a charm! Once my number ported and I put the new SIM card in, service was instantaneous! I've had Mint for 3 weeks now and the service is so much better than with Tracfone! My calls go through nearly as soon as I hit call, the internet is faster.
I didn't need to do a thing either. No making APN settings, etc. I'm betting it has to do with what you said about my phone being born ATT. So funny because the software(?) is Verizon - shows the Verizon when I restart/power up. I still love my bastard phone
So thankful I didn't buy a different phone!!! Again thanks for all your help @schwinn8
Thanks for reporting back and letting us all know, and I'm glad it worked out well!
Yeah, the carriers pull this nonsense all the time... it's BS. The phones are all the same, only the ROM changes. If we can change ROMs (which we can) then there should be no reason to force users to specific IMEIs. But we know why they do this - follow the money. I encourage people to write to the FTC and FCC about this (I have).

Categories

Resources