Related
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!
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!
Hell of a story, I apologize in advance for the length, but maybe it'll be intriguing to some of you. Pure Nexus rom as of i think april 23rd?
I have a Nexus 6 that I bought 2 years ago in April on Verizon (purchased from verizon). My contract ran out April 27th, went to AT&T with my girlfriend because I was going to get on her plan to save money on our phone bills. Ported over the number to my N6 fine. But I noticed I only got an H+ symbol, no LTE. I asked the guy if that was normal, he said yes. I got data and could make calls so I figured it was fine. Did some speed tests, 2 mb/down at best. My GF was getting 15-20 in the same spot on her Galaxy S7.
Long part of this story short, the tech they put me on the phone with said it was due to it being a Verizon variant and was not capable of full LTE speeds on AT&T. I went to the Verizon store and asked if they could put me back under Verizon after explaining the problem. He said sure, and then worked up pricing to have my GF switch to Verizon with me instead, and to get a Pixel XL.
So far so good, they had to do a temporary number for me because there's issues porting a number twice in a 24 hour span, but they cleared it up, got my real number ported, happy camper, good speeds. Except this one issue.
Now when I'm on the phone (actual phone call), my data drops. The LTE signal actually disappears, and nothing displays except signal bars. As soon as the phone call is over, it comes back. I never had the problem before this whole back and forth mess. I can't seem to figure out any options to make it not do this. I was thinking about reflashing my rom in case that would help, maybe something got messed up in the switch back and forth to GSM and then back to CDMA?
Morpherios said:
Hell of a story, I apologize in advance for the length, but maybe it'll be intriguing to some of you. Pure Nexus rom as of i think april 23rd?
I have a Nexus 6 that I bought 2 years ago in April on Verizon (purchased from verizon). My contract ran out April 27th, went to AT&T with my girlfriend because I was going to get on her plan to save money on our phone bills. Ported over the number to my N6 fine. But I noticed I only got an H+ symbol, no LTE. I asked the guy if that was normal, he said yes. I got data and could make calls so I figured it was fine. Did some speed tests, 2 mb/down at best. My GF was getting 15-20 in the same spot on her Galaxy S7.
Long part of this story short, the tech they put me on the phone with said it was due to it being a Verizon variant and was not capable of full LTE speeds on AT&T. I went to the Verizon store and asked if they could put me back under Verizon after explaining the problem. He said sure, and then worked up pricing to have my GF switch to Verizon with me instead, and to get a Pixel XL.
So far so good, they had to do a temporary number for me because there's issues porting a number twice in a 24 hour span, but they cleared it up, got my real number ported, happy camper, good speeds. Except this one issue.
Now when I'm on the phone (actual phone call), my data drops. The LTE signal actually disappears, and nothing displays except signal bars. As soon as the phone call is over, it comes back. I never had the problem before this whole back and forth mess. I can't seem to figure out any options to make it not do this. I was thinking about reflashing my rom in case that would help, maybe something got messed up in the switch back and forth to GSM and then back to CDMA?
Click to expand...
Click to collapse
Try to unlock bootloader, install TWRP, root the stock rom, then install lastest bootloader (v72.03) and latest radio (v05.45):
https://forum.xda-developers.com/ne...-nexus-6-recovery-flashable-fastboot-t3066052
Use WUG Fresh NRT tool to accomplish above when hooked to Windows PC via microUSB in 2.0 USB port with correct Windows drivers installed (OK for ADB): https://forum.xda-developers.com/showthread.php?t=1766475
HueyT said:
Try to unlock bootloader, install TWRP, root the stock rom, then install lastest bootloader (v72.03) and latest radio (v05.45):
https://forum.xda-developers.com/ne...-nexus-6-recovery-flashable-fastboot-t3066052
Use WUG Fresh NRT tool to accomplish above when hooked to Windows PC via microUSB in 2.0 USB port with correct Windows drivers installed (OK for ADB): https://forum.xda-developers.com/showthread.php?t=1766475
Click to expand...
Click to collapse
I'm already unlocked, rooted, TWRP'd and using the PureNexus that came out end of april (I haven't flashed the one in may yet). I believe I'm also currently using the latest radio and latest bootloader.
Edit - I actually was not on the most recent radio, but I did flash that, no change.
The volte provisioned flag turned on in the testing menu? I have a setting for enhanced 4g lte mode in my settings, wireless networks/more/cellular networks settings. Did they remove the advanced calling from your account? Just throwing some things out there.
Morpherios said:
Hell of a story, I apologize in advance for the length, but maybe it'll be intriguing to some of you. Pure Nexus rom as of i think april 23rd?
I have a Nexus 6 that I bought 2 years ago in April on Verizon (purchased from verizon). My contract ran out April 27th, went to AT&T with my girlfriend because I was going to get on her plan to save money on our phone bills. Ported over the number to my N6 fine. But I noticed I only got an H+ symbol, no LTE. I asked the guy if that was normal, he said yes. I got data and could make calls so I figured it was fine. Did some speed tests, 2 mb/down at best. My GF was getting 15-20 in the same spot on her Galaxy S7.
Long part of this story short, the tech they put me on the phone with said it was due to it being a Verizon variant and was not capable of full LTE speeds on AT&T. I went to the Verizon store and asked if they could put me back under Verizon after explaining the problem. He said sure, and then worked up pricing to have my GF switch to Verizon with me instead, and to get a Pixel XL.
So far so good, they had to do a temporary number for me because there's issues porting a number twice in a 24 hour span, but they cleared it up, got my real number ported, happy camper, good speeds. Except this one issue.
Now when I'm on the phone (actual phone call), my data drops. The LTE signal actually disappears, and nothing displays except signal bars. As soon as the phone call is over, it comes back. I never had the problem before this whole back and forth mess. I can't seem to figure out any options to make it not do this. I was thinking about reflashing my rom in case that would help, maybe something got messed up in the switch back and forth to GSM and then back to CDMA?
Click to expand...
Click to collapse
The tech may not be wrong as Verizon uses band 13 as their main LTE band and ATT uses band 17
http://www.phonearena.com/news/Chea...on-T-Mobile-and-Sprint-use-in-the-USA_id77933
Morpherios said:
Hell of a story, I apologize in advance for the length, but maybe it'll be intriguing to some of you. Pure Nexus rom as of i think april 23rd?
I have a Nexus 6 that I bought 2 years ago in April on Verizon (purchased from verizon). My contract ran out April 27th, went to AT&T with my girlfriend because I was going to get on her plan to save money on our phone bills. Ported over the number to my N6 fine. But I noticed I only got an H+ symbol, no LTE. I asked the guy if that was normal, he said yes. I got data and could make calls so I figured it was fine. Did some speed tests, 2 mb/down at best. My GF was getting 15-20 in the same spot on her Galaxy S7.
Long part of this story short, the tech they put me on the phone with said it was due to it being a Verizon variant and was not capable of full LTE speeds on AT&T. I went to the Verizon store and asked if they could put me back under Verizon after explaining the problem. He said sure, and then worked up pricing to have my GF switch to Verizon with me instead, and to get a Pixel XL.
So far so good, they had to do a temporary number for me because there's issues porting a number twice in a 24 hour span, but they cleared it up, got my real number ported, happy camper, good speeds. Except this one issue.
Now when I'm on the phone (actual phone call), my data drops. The LTE signal actually disappears, and nothing displays except signal bars. As soon as the phone call is over, it comes back. I never had the problem before this whole back and forth mess. I can't seem to figure out any options to make it not do this. I was thinking about reflashing my rom in case that would help, maybe something got messed up in the switch back and forth to GSM and then back to CDMA?
Click to expand...
Click to collapse
In others countries we don't get the same bands management, then I can't say anything about LTE.
But I'm on PureNexus 7.1.1 and I get the same "issue" about network droppin when calling. When the call starts, my phone turns into don't disturb-mode and recover the network only when the phone call ends.. It doesn't really cut my network connection, but it looks like. It may be rom settings.
However I don't care as long as everything works good, it's just an icon. (how a phone call can be done while network is shutted off ^^)
When I was on the stock ROM, this autumn, 7.1 version of Android did the same thing, loosing data connection while being still connected to the network (but at anytime not just phonecalls). Finding it back some minutes later. That was fixed with 7.1.1. Stock.
Hope that might help you (looks not ) if it's the same problem. May be give an eye to the Rom settings..
Have you tried if your device do the same thing with an another Rom ? (stock for example)
Larzzzz82 said:
The volte provisioned flag turned on in the testing menu? I have a setting for enhanced 4g lte mode in my settings, wireless networks/more/cellular networks settings. Did they remove the advanced calling from your account? Just throwing some things out there.
Click to expand...
Click to collapse
I knew something looked like it was missing. I don't have any enhanced 4g LTE settings in that section. Normally there's a tick box to turn it on there. It's missing. Is that due to them not having it turned on in my account?
Also for everyone else, this problem only started when I tried the whole at&t switch. I was on this rom when I switched and it worked fine before then. I didn't factory reset since then though, wondering if I need to try that.
zelendel said:
The tech may not be wrong as Verizon uses band 13 as their main LTE band and ATT uses band 17
http://www.phonearena.com/news/Chea...on-T-Mobile-and-Sprint-use-in-the-USA_id77933
Click to expand...
Click to collapse
The tech is definitely wrong; since it's a Nexus 6 (presumably XT1103) it has all the possible LTE bands used in the US. There should not have been any issue when switching. I had something similar happen to me, when I just switched to verizon and did the "reset network settings" button, it screwed up my phone so I couldn't use LTE period, I had to reflash the modem in order to fix it. I know you already said you reflashed the modem, but I'm not sure what to suggest. There is absolutely nothing physically wrong or incapable about your phone, just some config got screwed up somewhere along the way. I'd just try to flash as many things as you're comfortable with without losing your userdata. Like modem, bootloader, etc. until your data comes back. If nothing else, press the network settings reset button and flash the latest modem. Make sure your twrp is up to date as well.
BlockOfDynamite said:
The tech is definitely wrong; since it's a Nexus 6 (presumably XT1103) it has all the possible LTE bands used in the US. There should not have been any issue when switching. I had something similar happen to me, when I just switched to verizon and did the "reset network settings" button, it screwed up my phone so I couldn't use LTE period, I had to reflash the modem in order to fix it. I know you already said you reflashed the modem, but I'm not sure what to suggest. There is absolutely nothing physically wrong or incapable about your phone, just some config got screwed up somewhere along the way. I'd just try to flash as many things as you're comfortable with without losing your userdata. Like modem, bootloader, etc. until your data comes back. If nothing else, press the network settings reset button and flash the latest modem. Make sure your twrp is up to date as well.
Click to expand...
Click to collapse
I think i'm going to reflash my rom today. I did the modem, twrp is up to date, bootloader is fine. I did the reset network settings (I was sure that was going to fix it, no dice). So I'm going to reflash the rom today and see if that fixes it. After that I have no idea what is left to try other than reverting to stock, which I'd like to avoid.
Yes, it is a feature that needs to be added to your account. Go online and check their website or go into the hidden menu and activate it. If it sticks, it's on your account.
I tried the wifi and video calling flags and they didn't stick. Go figure... C'MON big red...
Larzzzz82 said:
Yes, it is a feature that needs to be added to your account. Go online and check their website or go into the hidden menu and activate it. If it sticks, it's on your account.
I tried the wifi and video calling flags and they didn't stick. Go figure... C'MON big red...
Click to expand...
Click to collapse
How do you enter the hidden menu on the n6? I thought I found it but it wasn't working.
.#.#4636#.#. select the phone info tab. In there, there will be either a drop down menu or buttons to tick and they'll change color
Larzzzz82 said:
.#.#4636#.#. select the phone info tab. In there, there will be either a drop down menu or buttons to tick and they'll change color
Click to expand...
Click to collapse
I got in, VoLTE was not ticked. I ticked it. I got the setting for it then in settings. But making a phone call gave me an error. I rebooted, and it's not ticked now. So does that mean I need to call Verizon to have them flag my account?
You need to add it in your account then. Easy enough to do online. You want to, "manage features."
Larzzzz82 said:
You need to add it in your account then. Easy enough to do online. You want to, "manage features."
Click to expand...
Click to collapse
That did the trick. All fixed. Thank you! That was driving me nuts. I never considered the idea that the setting would be turned off . But since I did leave and come back...
Thanks again!
Glad you're all set. ?
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.
So many people are reporting with the 3/1 sweep by AT&T, that they are blocking almost all Unlocked phones: See: Downdector Link We personally have a S10 (G973U1). AT&T is saying on this list: AT&T approved phone list that it is supposed to work. But like many other people "calls" end immediately, but we can text and data work. It is some sorta ploy by AT&T to force us to upgrade our phones. They want us all to upgrade to S22s. Anyway I was ranting. Anyway, if you look at that link, they are saying that the phone has to be on the latest software. The last update from AT&T or the manufacturer was in January. I checked the firmware site, and Android 11 is the latest in January. I'm wondering if there is some hack to get us on to '12' or something. An update might solve this issue. We know that a new SIM does not work. Calls seem to be rejected on the network, just based on the phone model or Android version.
We are aware that a version 12 is out there for the phone, just that firmware is not for our US-unlocked model yet. But maybe it can be hacked?
Edit: It appears this thread may be linked with this older one... But it is ever more pressing issue now:
S10 Unlocked phone with AT&T Firmware here they explain how, and the problems with flashing. This was back in 2019, so I'm not sure if this will still work. Even then it didn't work for everyone. Some in that forum claimed that it did. AT&T seems to now be blocking from their calling network any phones not enabled with VOLTE and the extended AT&T services that are not present in Unlocked phones.
robertkjr3d said:
So many people are reporting with the 3/1 sweep by AT&T, that they are blocking almost all Unlocked phones: See: Downdector Link We personally have a S10 (G973U1). AT&T is saying on this list: AT&T approved phone list that it is supposed to work. But like many other people "calls" end immediately, but we can text and data work. It is some sorta ploy by AT&T to force us to upgrade our phones. They want us all to upgrade to S22s. Anyway I was ranting. Anyway, if you look at that link, they are saying that the phone has to be on the latest software. The last update from AT&T or the manufacturer was in January. I checked the firmware site, and Android 11 is the latest in January. I'm wondering if there is some hack to get us on to '12' or something. An update might solve this issue. We know that a new SIM does not work. Calls seem to be rejected on the network, just based on the phone model or Android version.
We are aware that a version 12 is out there for the phone, just that firmware is not for our US-unlocked model yet. But maybe it can be hacked?
Edit: It appears this thread may be linked with this older one... But it is ever more pressing issue now:
S10 Unlocked phone with AT&T Firmware here they explain how, and the problems with flashing. This was back in 2019, so I'm not sure if this will still work. Even then it didn't work for everyone. Some in that forum claimed that it did. AT&T seems to now be blocking from their calling network any phones not enabled with VOLTE and the extended AT&T services that are not present in Unlocked phones.
Click to expand...
Click to collapse
I was helped by a user to achieve ascendance onto the AT&T network. I'm not sure if I'm to reveal his name. We 1) go into Developers mode on the phone. 2) Hack the Kernel. 3) Flash the rom to the G973U (model)... with the AT&T firmware. So that the Wifi-Calling and 5G features would work, and AT&T would allow it on their network.
robertkjr3d said:
I was helped by a user to achieve ascendance onto the AT&T network. I'm not sure if I'm to reveal his name. We 1) go into Developers mode on the phone. 2) Hack the Kernel. 3) Flash the rom to the G973U (model)... with the AT&T firmware. So that the Wifi-Calling and 5G features would work, and AT&T would allow it on their network.
Click to expand...
Click to collapse
I've literally been searching for an answer to this for days now. My wife and I have S10's. I work far from home so I really need her phone working in case of emergency. Can you please point me in the general direction? Thanks!
Agreed, I didn't know such a thing was possible, but I'd love to hear more about this!
skrapmetal said:
I've literally been searching for an answer to this for days now. My wife and I have S10's. I work far from home so I really need her phone working in case of emergency. Can you please point me in the general direction? Thanks!
Click to expand...
Click to collapse
At first I had to use the Samsung Band Selector app from the Play store and go into More Network Settings > AT&T > Preferred Network Type and choose 3G. Unfortunately this killed LTE so all data and calls were going through H+. As I was mostly on wifi I could live with it since I could actually use the phone again.
Then Friday morning I checked for updates and there was the update to take me to Android 12. I took the update then when it finished it said it needed to reboot to connect new SIM to carrier services....it wasn't a new SIM. I let it reboot and everything was working with VoLTE again.
Hope this helps.
KennyG123 said:
At first I had to use the Samsung Band Selector app from the Play store and go into More Network Settings > AT&T > Preferred Network Type and choose 3G. Unfortunately this killed LTE so all data and calls were going through H+. As I was mostly on wifi I could live with it since I could actually use the phone again.
Then Friday morning I checked for updates and there was the update to take me to Android 12. I took the update then when it finished it said it needed to reboot to connect new SIM to carrier services....it wasn't a new SIM. I let it reboot and everything was working with VoLTE again.
Hope this helps.
Click to expand...
Click to collapse
I appreciate you getting back to me. Unfortunately I am still on android 11 with a custom ROM and also this is a global phone so that app didnt work for me. I dont receive OTA updatez. I'll update to a new ROM and see what happens. Thanks