I just spent 2 hours on the phone with tech. I get a VM and the notification. When I go to play it through the phone app native to the phone I get an error saying to call tech support and give them code 9999. I can manually dial .86 and enter my pass bit that isn't doing me any good.
Anyone else having issues? I'm going to try Google tech next...
cv123 said:
I just spent 2 hours on the phone with tech. I get a VM and the notification. When I go to play it through the phone app native to the phone I get an error saying to call tech support and give them code 9999. I can manually dial .86 and enter my pass bit that isn't doing me any good.
Anyone else having issues? I'm going to try Google tech next...
Click to expand...
Click to collapse
I am having the same problem, however I started having this problem with my note 7 last night too so it could be something system related and not phone related
Sent from my Pixel XL using Tapatalk
le0.br4zuc4 said:
I am having the same problem, however I started having this problem with my note 7 last night too so it could be something system related and not phone related
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
I'll see tomorrow. If you see any changes let me know. I can bring that up to the rep that other phones are having the same problems.
It does have visual voicemail. I just activated it. You You have to go to the phone app settings
Djmecca said:
It does have visual voicemail. I just activated it. You You have to go to the phone app settings
Click to expand...
Click to collapse
Verified this works
Not to harp here but these settings are like little easter eggs when you get a new phone. It's all part of the ritual. You should go walk about on the entire interface, settings, sub menus etc. Even if that sounds annoying to you, do it and enjoy because in three weeks, it's just your phone and loses its gas like any other toy.
Sent from my Pixel XL using XDA-Developers mobile app
Once you activate it in phone settings it works perfectly.
cv123 said:
I just spent 2 hours on the phone with tech. I get a VM and the notification. When I go to play it through the phone app native to the phone I get an error saying to call tech support and give them code 9999. I can manually dial .86 and enter my pass bit that isn't doing me any good.
Anyone else having issues? I'm going to try Google tech next...
Click to expand...
Click to collapse
I am still having this issue...I have been to the Verizon store twice and tech support multiple times...I love the Pixel, but I cant live without Visual Voicemail.
Did you try manually turning off all call forwarding?
*73
Sent from my Pixel XL using Tapatalk
mdonnelly1127 said:
Verified this works
Click to expand...
Click to collapse
Can you post the step you took to activate?
Thanks
cv123 said:
Can you post the step you took to activate?
Thanks
Click to expand...
Click to collapse
Honestly went into the phone icon, went all the way to right hand side to get to voicemail. There was a box that popped up that said visual voicemail on carrier blah blah and hit turn on or activate or whatever it said
mdonnelly1127 said:
Honestly went into the phone icon, went all the way to right hand side to get to voicemail. There was a box that popped up that said visual voicemail on carrier blah blah and hit turn on or activate or whatever it said
Click to expand...
Click to collapse
Thats exactly what I did and I keep getting an error 9999. Did your show the actual name of the carrier? Which VM service do you subscribe to with Verizon?
Thanks
cv123 said:
Thats exactly what I did and I keep getting an error 9999. Did your show the actual name of the carrier? Which VM service do you subscribe to with Verizon?
Thanks
Click to expand...
Click to collapse
Me, too! Verizon tech support said it is a known issue and will take 3-6 days to fix....I switched from a Samsung Edge...:crying::crying::crying: Also, I have Premium VM Package.
lorimatt13 said:
Me, too! Verizon tech support said it is a known issue and will take 3-6 days to fix....I switched from a Samsung Edge...:crying::crying::crying: Also, I have Premium VM Package.
Click to expand...
Click to collapse
I have mine working but only after dialing *73 which force enables carrier voicemail. After this I went to Visual voicemail tab and they started pouring in. I then had my wife leave a message to verify working and it showed up no problem. Have you tried dialing *73?
I did try that yesterday....thank you!
Just curious -- are you guys talking about the stock VV or Verizon's?
I have a verizon...
calbruc said:
Just curious -- are you guys talking about the stock VV or Verizon's?
Click to expand...
Click to collapse
Verizon VV
calbruc said:
Just curious -- are you guys talking about the stock VV or Verizon's?
Click to expand...
Click to collapse
Verizon's, but it's built into the Phone app loaded on the Pixel and Pixel XL from Verizon
Isn't the built in VVM in the phone app Google's VVM. Even on Verizons?
Sent from my Pixel XL using XDA-Developers mobile app
Related
I have gone thru 2 sim cards, 2 SM-N910A with similar results.
In settings, call, additional settings, it comes up with Network or SIM card error. AT&T has replaced two sim card, one a micro sim, one a nano sim with adapter.
From the keypad, **21*808551999# the error message as attach
The AT&T associate spent an hour with the advanced tech support to no avail.
I have a Nexus 6 and I can access all the above function, so my account is provisioned properly and I'm post paid
Did you ever find a solution? I'm having the same problem.
It's something to do with the phone, as you seem to be aware of, I had a customer come in who wanted to forward his note 4 to his gear s, the same issue happened, from what I can gather it seems to just be an issue with the call app itself, a fix I read but never go to try was taking a sim card from a known working phone that has call forwarding on and inserting it into the unworking phone.
Try stopping the phone app and clear all data. I got a new sim card and then did that and my call forwarding worked. YMMV
I have the same problem. I called tech support today and the lady I talked to didn't even know that the gear app could auto forward you calls. She said she would set it up for me on her end. Not what I wanted. I want this 2 high end devices to perform the way they are suppose to before att got there hands on it.
So what I did was, I pulled out my Note 3. Updated to latest FireKat Rom and problem solved.
My note 4 and gear s worked perfectly when I first got them. THEN WE GOT AN UPDATE--------THE ONLY UPDATE.
That's when I first started having this problem.
Not only do we not have root, but now it isn't doing the cool things it should. I'm sorry for the long winded ***** but I shouldn't have to wait for the chance of a possible maybe sometime in the future if everything goes right update that may or may not correct this problem and could possibly inject more issues. I'm sure someone will correct me if I'm wrong.
Sent from my SAMSUNG-SM-N900A using XDA Premium HD app
thanitos said:
It's something to do with the phone, as you seem to be aware of, I had a customer come in who wanted to forward his note 4 to his gear s, the same issue happened, from what I can gather it seems to just be an issue with the call app itself, a fix I read but never go to try was taking a sim card from a known working phone that has call forwarding on and inserting it into the unworking phone.
Click to expand...
Click to collapse
jrtireman said:
I have the same problem. I called tech support today and the lady I talked to didn't even know that the gear app could auto forward you calls. She said she would set it up for me on her end. Not what I wanted. I want this 2 high end devices to perform the way they are suppose to before att got there hands on it.
So what I did was, I pulled out my Note 3. Updated to latest FireKat Rom and problem solved.
My note 4 and gear s worked perfectly when I first got them. THEN WE GOT AN UPDATE--------THE ONLY UPDATE.
That's when I first started having this problem.
Not only do we not have root, but now it isn't doing the cool things it should. I'm sorry for the long winded ***** but I shouldn't have to wait for the chance of a possible maybe sometime in the future if everything goes right update that may or may not correct this problem and could possibly inject more issues. I'm sure someone will correct me if I'm wrong.
Sent from my SAMSUNG-SM-N900A using XDA Premium HD app
Click to expand...
Click to collapse
I came across this post:
This is a problem with AT&T. I'm running 4.4.4 Android on a new Note 4 and discovered that Google Voice wouldn't run on the phone. I suspect the issue is tied to AT&T's implementation of their Visual Voicemail.
After spending a few calls with AT&T Tech Support, I was able to get my Google Voice to work by using the Call Forwarding Settings of "Forward When Busy", "Forward When Unavailable", and "Forward When Unreachable" to be set to my Google Voice number. The problem is that the Note 4 has the bug you mention. It's not possible for the user to access the settings on the phone without getting the "Network or SIM card error" message.
AT&T Tech Support can manually configure these settings, but this will only help if you don't change the settings often because a call to AT&T is required. I'm hoping they fix this bug in the Lollipop build.
Be careful when calling AT&T Tech Support, the first two times I called, the Tech Support Agent had no idea that this type of Call Forwarding Settings were configurable.
For the 3rd try at calling them, I got someone more knowledgeable who first reset my voicemail to "Basic Voicemail". This is done in the AT&T system, not on the individual phone. Once that had been done, I then had to "activate" the Basic Voicemail by configuring my box. As soon as that was done, the AT&T rep was able to go into the AT&T system and manually configure the three Call Forwarding options that I wanted.
It was a huge pain to go through, especially because all I wanted to do was use Google Voice which has worked on AT&T Samsung phones going back to my first Galaxy SII.
My phone still shows the "Network or SIM card Error" whenever I try to access the Call Forwarding Settings, but at least I was able to get the Call Forwarding configured for my Google Voice to work again.
I don't know if this info helps you out, but I wanted to pass it along.
Went back to AT&T yesterday, this time armed with my Nexus 6. Got a nano sim. Nexus 6 call forwarding function work. Working sim into Note 4. same crap happens.
I just check again this morning, and my Note 3 is working flawlessly. Gear app autofowards my calls as it should and advanced call settings does not show error message. I believe it's a problem with the Note 4 not able to register it's self with the network. If I use another phone it registers fine, call forwarding work as does tethering hot spot. If I try my Note 4 neither wants to work. When I call att they can fix my tethering hot spot but can't fix forwarding. My Note 3 just works by its self without having to do anything such as clear app data or anything with I have tried along with phone reset multiple times. I'm going to use my Note 3 for a while.
Sent from my SAMSUNG-SM-N900A using XDA Premium HD app
Used my Note 3 all day today. Everything worked flawlessly. Got home and started my tethering hotspot and no problems. I'm thinking that I'm getting tired of my Note 4. My Note 3 running Firekat is just as fast. The only thing is the camera and the screen is so good. I wish my Note 4 was as, we'll I'll stop there. Thinking about trading Note 4 in for the iPhone 6 plus. I'll still have my Note 3 that everything works perfectly on. I get bored and like to be able to switch up the experience so if I have android, Note 3 would be note 4 but, and the hated ios witch just works and that can be jailbroken with a lot more help because they are all the same device and dose not have individually locked boot loaders. ????? What to do???
Sent from my SAMSUNG-SM-N900A using XDA Premium HD app
jrtireman said:
Used my Note 3 all day today. Everything worked flawlessly. Got home and started my tethering hotspot and no problems. I'm thinking that I'm getting tired of my Note 4. My Note 3 running Firekat is just as fast. The only thing is the camera and the screen is so good. I wish my Note 4 was as, we'll I'll stop there. Thinking about trading Note 4 in for the iPhone 6 plus. I'll still have my Note 3 that everything works perfectly on. I get bored and like to be able to switch up the experience so if I have android, Note 3 would be note 4 but, and the hated ios witch just works and that can be jailbroken with a lot more help because they are all the same device and dose not have individually locked boot loaders. ????? What to do???
Sent from my SAMSUNG-SM-N900A using XDA Premium HD app
Click to expand...
Click to collapse
Tethering should work unless you have unlimited data, all mobile share plans from att include thethering, also you can pre-order the s6 on Friday, if I remember what our new Sammy rep was talking to me about, got to play with it for 30 seconds before a customer walked in, the ui is nice and smooth and the new octa exynos chip is suppose to run cooler and it seemed, just for ui scrolling, to sail through it all. I like the look and feel, I want it......
Edit: keep in mind that you'll be in the same position you are now as far as root and unlocked bootloader, if you want these things wait to see who sells the phone unlocked then buy it at full retail and use it on your account. I work for att, I know even the nexus 6, the most close to stock phone we sell has bloat ware and is locked down tight. If I get the s6 it's out right and unlocked.
Yes I agree. It should work. If I switch my sim to another phone it works just fine. Everything works as it should, but if I put my sim back in my Note 4 in phone settings advanced settings I get an simcard or network error and call forwarding does not work. Also tethering will fail telling me to call 611 or visit website to register device for tethering. Gear app will fail to forward calls also and I have had problems with network data. If you Google this problem it is a problem with note 4. Some people on the att forums are just hoping for an update soon. That's is not acceptable to me. It worked when I bought the phone then there was an update that was pushed to my phone and now my phone is turned off and I'm using my Note 3. So by the time this gets resolved and I can enjoy my phone it will be old in the world of phone technology. So why should I keep it, hoping it will be updated sometime in the near future which keeps getting pushed back for some unknown to me reason. Don't get me wrong. I love my Note 4 but I want it to work now.
Sent from my SAMSUNG-SM-N900A using XDA Premium HD app
---------- Post added at 11:21 PM ---------- Previous post was at 11:16 PM ----------
The S6 Edge does look nice though.
Sent from my SAMSUNG-SM-N900A using XDA Premium HD app
jrtireman said:
Yes I agree. It should work. If I switch my sim to another phone it works just fine. Everything works as it should, but if I put my sim back in my Note 4 in phone settings advanced settings I get an simcard or network error and call forwarding does not work. Also tethering will fail telling me to call 611 or visit website to register device for tethering. Gear app will fail to forward calls also and I have had problems with network data. If you Google this problem it is a problem with note 4. Some people on the att forums are just hoping for an update soon. That's is not acceptable to me. It worked when I bought the phone then there was an update that was pushed to my phone and now my phone is turned off and I'm using my Note 3. So by the time this gets resolved and I can enjoy my phone it will be old in the world of phone technology. So why should I keep it, hoping it will be updated sometime in the near future which keeps getting pushed back for some unknown to me reason. Don't get me wrong. I love my Note 4 but I want it to work now.
Sent from my SAMSUNG-SM-N900A using XDA Premium HD app
---------- Post added at 11:21 PM ---------- Previous post was at 11:16 PM ----------
The S6 Edge does look nice though.
Sent from my SAMSUNG-SM-N900A using XDA Premium HD app
Click to expand...
Click to collapse
I updated to 5.01, still has the same issue. This is quite possibly the last Samsung phone I'll ever buy
Elpidio said:
I updated to 5.01, still has the same issue. This is quite possibly the last Samsung phone I'll ever buy
Click to expand...
Click to collapse
force stop the phone app and it should fix your issue.
icexshinigami said:
force stop the phone app and it should fix your issue.
Click to expand...
Click to collapse
thanks for the tip, I force stop all three phone apps to no avail.
Elpidio said:
thanks for the tip, I force stop all three phone apps to no avail.
Click to expand...
Click to collapse
I know you tried , the dialer codes.
always call forward setting , **21*808551999# (did you make sure it is 10digits? should be , **21*1808551999# if you are in the us. it might be worth a try.
conditional call forwarding **004*1808551999# (busy, rejected, missed calls)
icexshinigami said:
force stop the phone app and it should fix your issue.
Click to expand...
Click to collapse
icexshinigami said:
I know you tried , the dialer codes.
always call forward setting , **21*808551999# (did you make sure it is 10digits? should be , **21*1808551999# if you are in the us. it might be worth a try.
conditional call forwarding **004*1808551999# (busy, rejected, missed calls)
Click to expand...
Click to collapse
sorry, there's one digit missing in my original post
should have been +18085519959
There's definitely something wrong with how AT&T network supporting this phone. I have no problem with my Nexus 6. It's very frustrating but it's something I have to live with if I want to keep using this phone.
Anyways, thanks for trying to help.
Elpidio said:
I updated to 5.01, still has the same issue. This is quite possibly the last Samsung phone I'll ever buy
Click to expand...
Click to collapse
The upgrade fixed the problem for me. I didn't change anything else besides the OTA update.
scrtsqrrl said:
The upgrade fixed the problem for me. I didn't change anything else besides the OTA update.
Click to expand...
Click to collapse
only thing I have not done is "wipe data/factory reset" from the recovery mode. I'll see if I can back up my data on ODIN
Elpidio said:
only thing I have not done is "wipe data/factory reset" from the recovery mode. I'll see if I can back up my data on ODIN
Click to expand...
Click to collapse
Weird that would have been one of the first things I did.. Assumed you already went that way.. If after all this it doesn't work it seems you may have a defective device and should bring it up with samsung or att for an exchange...
icexshinigami said:
Weird that would have been one of the first things I did.. Assumed you already went that way.. If after all this it doesn't work it seems you may have a defective device and should bring it up with samsung or att for an exchange...
Click to expand...
Click to collapse
I did the "wipe data/factory reset" from recovery and its still the same. You maybe right that the device is defective and since its more than 30 days, either I'll call Samsung for a replacement or claim insurance, however, by looking at AT&T community forum thread, I read that it all worked with N910AUCU1ANIE firmware, when AT&T updated that firmware, all hell broke loose. I'll see if I can have Samsung replace it.
https://forums.att.com/t5/Samsung-D...e-Update-Broke-my-Phone-Settings/td-p/4170378
Elpidio said:
I did the "wipe data/factory reset" from recovery and its still the same. You maybe right that the device is defective and since its more than 30 days, either I'll call Samsung for a replacement or claim insurance, however, by looking at AT&T community forum thread, I read that it all worked with N910AUCU1ANIE firmware, when AT&T updated that firmware, all hell broke loose. I'll see if I can have Samsung replace it.
https://forums.att.com/t5/Samsung-D...e-Update-Broke-my-Phone-Settings/td-p/4170378
Click to expand...
Click to collapse
Its on its way to Samsung Repair Center in Plano, TX
Can anyone get voicemaill to work on Verizon on their 5x? I just get a garbled text message when a voicemail comes in. There is a nexus visual voicemail app but it hangs on authentication when going into it. I guess I can call Verizon and have them switch back to regular dial in voicemail.....
Since the 5X isn't registered on Verizon's network, my guess is visual voicemail isn't going to work.
jntdroid said:
Since the 5X isn't registered on Verizon's network, my guess is visual voicemail isn't going to work.
Click to expand...
Click to collapse
It doesnt show up as an unrecognized device in my verizon. Its shows as LG- LGH790. All seems well. Not like it was when you swapped a sim into the Nexus 6 its first days......
elreydenj said:
It doesnt show up as an unrecognized device in my verizon. Its shows as LG- LGH790. All seems well. Not like it was when you swapped a sim into the Nexus 6 its first days......
Click to expand...
Click to collapse
Oh really? Well I stand corrected. That's good to hear!
*bump*
Any updates to this? Running into the same problem.
Sent from my Nexus 5X using Tapatalk
I've got a thread going about this issue, didn't see this old thread. I've spoken to level 2 tech support, basically we have to wait for an updated voicemail app like the previous nexus had to have.
As a temporary workaround I've setup Google voice to handle my voicemails and it works quite well.
Sent from my Nexus 5X using XDA Free mobile app
Jexx11 said:
As a temporary workaround I've setup Google voice to handle my voicemails and it works quite well.
Click to expand...
Click to collapse
Did you have to do anything manual to set up Google Voice for VM on Verizon? I can't seem to get it working.
Yes, you have to dial some codes. Check out this link and then click on "additional help for Verizon users"
https://support.google.com/voice/answer/165656?hl=en
Sent from my Nexus 5X using Tapatalk
Does anyone know how to enable video calling from withing the phone dialer. I read that the Verizon version has it. and T-Mobile allows it so if I could get it to appear I'd imagine it would work.
My understanding is to get it to show up as an option you have to enable it on your Verizon account. If it isn't enabled then the phone won't show it. I went through the dialer and enabled it but it still didn't show up in the calling app until I enabled it with Verizon. Code for dialer is **#*#4636#*#**
Sent from my Pixel XL using Tapatalk
ahent said:
My understanding is to get it to show up as an option you have to enable it on your Verizon account. If it isn't enabled then the phone won't show it. I went through the dialer and enabled it but it still didn't show up in the calling app until I enabled it with Verizon. Code for dialer is **#*#4636#*#**
Click to expand...
Click to collapse
See I have the one from Google, on T-Mobile and it worked on my note 7. I called and they said it was enabled. I wonder of anyone with T-Mobile has it working and can share their steps.
In that dialer code menu there is a toggle to enable it, just with Verizon it didn't make any difference and actually toggled it back off.
Sent from my Pixel XL using Tapatalk
ahent said:
In that dialer code menu there is a toggle to enable it, just with Verizon it didn't make any difference and actually toggled it back off.
Click to expand...
Click to collapse
Same with T-Mobile, because it actually has to be provisioned.
I enabled HD calling on my Verizon account and the option now shows up
Sent from my Pixel XL using Tapatalk
Legacystar said:
I enabled HD calling on my Verizon account and the option now shows up
Click to expand...
Click to collapse
Hmmmm. I'll call T-Mobile and see if there's an option like that for me. Did you call and do that or is it something you did manually.
For Verizon, you have to have the My Verizon app and then the option shows if to enable it off the call settings menu
Sent from my Pixel XL using Tapatalk
I called TMobile for my Pixel to get the video calling working. They checked menu setting (I already checked) and then told me I'd have to contact Google.
Google Duo
I'm on T-mobile using DU ROM and video calling works. If I pull up contact info I get the symbol for video calling.
spaceman860 said:
I'm on T-mobile using DU ROM and video calling works. If I pull up contact info I get the symbol for video calling.
Click to expand...
Click to collapse
Interesting. I wonder what the change is. This alone will prompt me to root. Although I prefer to manually commit the change than run a ROM.
Sent from my Pixel XL
Also on T-Mobile here with the symbol and tried calling someone using it. That person has an iPhone 7. After answering there was only audio. Do they need to have it enabled or have a different phone. Just curious.
Sent from my Pixel XL using Tapatalk
Persianhawkes said:
Also on T-Mobile here with the symbol and tried calling someone using it. That person has an iPhone 7. After answering there was only audio. Do they need to have it enabled or have a different phone. Just curious.
Click to expand...
Click to collapse
You're correct even on DU it doesn't work. It looks like it works but when the person on the other end picks up the call video turns off.
BlackKnight23 said:
I called TMobile for my Pixel to get the video calling working. They checked menu setting (I already checked) and then told me I'd have to contact Google.
Click to expand...
Click to collapse
Did you have any luck with Google?
Persianhawkes said:
Also on T-Mobile here with the symbol and tried calling someone using it. That person has an iPhone 7. After answering there was only audio. Do they need to have it enabled or have a different phone. Just curious.
Click to expand...
Click to collapse
spaceman860 said:
You're correct even on DU it doesn't work. It looks like it works but when the person on the other end picks up the call video turns off.
Click to expand...
Click to collapse
In my experience the video calling only works when calling someone with a Android phone that also supports video calling on T-Mobile... For instance when I had my note 7 I could video chat my dad who had a s7 edge and my cousin with a V20 and even my cousin with a s7 edge on att.... But no iOS phones or Android phones without native support... This makes me wonder what in the code your ROM changed.
Bruce lee roy said:
Google Duo
Click to expand...
Click to collapse
Th e thread is about native video calling that's not native that's a third party app
nique0201 said:
Th e thread is about native video calling that's not native that's a third party app
Click to expand...
Click to collapse
Apparently there is no native video calling on non Verizon pixels. Duo may be the closest since it is Google
nique0201 said:
Did you have any luck with Google?
Click to expand...
Click to collapse
No, they said to contact TMobile. TMobile tried to assume me to expect it in the future but without any timeframe.
Hi, I just switched from Project Fi to T Mobile and wifi calling is not working on my Pixel 2 XL. If I'm in airplane mode, turn on wifi, and make a call, it gives me an error that says "turn off airplane mode or connect to a wireless network to make a call."
My searches on the net seem to show varying results with it seeming to work for some and not others. Please help! Please respond if you have a Pixel 2 XL on T Mobile and if wifi calling is working for you in airplane mode. I assume that a true wifi call on the Pixel will show a wifi symbol on the call screen, as it did for me when I was on Project Fi.
Thanks!
Just tried. Haven't used the wifi calling as I have a T-Mobile LTE hot spot and haven't needed to at home since. Worked fine though on stock 8.1 no root. Airplane mode active, WiFi on.
Never turned it on until I tested it out, I'm on 8.1 stock unrooted March patch and it works just fine.
fiffan86 said:
Never turned it on until I tested it out, I'm on 8.1 stock unrooted March patch and it works just fine.
Click to expand...
Click to collapse
You guys are giving me hope. Thanks so much for responding. I need to find out what is different about my setup than your two.
Did you get your Pixel 2 XL from Verizon? Mine's straight from Google/Project Fi. I don't THINK there's a difference, is there?
26kick said:
You guys are giving me hope. Thanks so much for responding. I need to find out what is different about my setup than your two.
Did you get your Pixel 2 XL from Verizon? Mine's straight from Google/Project Fi. I don't THINK there's a difference, is there?
Click to expand...
Click to collapse
There shouldn't be a difference, I got mine from Verizon
fiffan86 said:
There shouldn't be a difference, I got mine from Verizon
Click to expand...
Click to collapse
Maybe its a software thing. Ill see if I can post settings page to compare with yours.
fiffan86 said:
There shouldn't be a difference, I got mine from Verizon
Click to expand...
Click to collapse
Same here. It works fine for me. It tells me when it's "HD" and "Wifi."
fiffan86 said:
There shouldn't be a difference, I got mine from Verizon
Click to expand...
Click to collapse
I don't feel like there's anything significant in here. Any ideas, guys?
When you were on a Wi-Fi call that you placed, did you have the little Wi-Fi symbol on the call Page above the name and number? That's what I remember when I would make a Wi-Fi call using project fi on my pixel 2 XL.
26kick said:
I don't feel like there's anything significant in here. Any ideas, guys?
When you were on a Wi-Fi call that you placed, did you have the little Wi-Fi symbol on the call Page above the name and number? That's what I remember when I would make a Wi-Fi call using project fi on my pixel 2 XL.
Click to expand...
Click to collapse
You do know that you enable WiFi calling through your mobile network settings right?
Yeah,
Mine works fine also, I'm using WiFi preferred in settings also if that makes a difference,
Ken
AcidNoteZ said:
You do know that you enable WiFi calling through your mobile network settings right?
Click to expand...
Click to collapse
Yes.
You all are on T Mobile, yeah? There must be something I'm missing.
26kick said:
Yes.
You all are on T Mobile, yeah? There must be something I'm missing.
Click to expand...
Click to collapse
The key for me back when i had tmobile was to register a 911 address on My T-Mobile. (Note: If you skip this step, a REG09 error may be displayed.)
https://support.t-mobile.com/commun...xel-2/topic/wi-fi/turn-on-off-wi-fi-calling/2
26kick said:
I don't feel like there's anything significant in here. Any ideas, guys?
When you were on a Wi-Fi call that you placed, did you have the little Wi-Fi symbol on the call Page above the name and number? That's what I remember when I would make a Wi-Fi call using project fi on my pixel 2 XL.
Click to expand...
Click to collapse
Yes I have that when I used wifi to make a call
mademan420 said:
The key for me back when i had tmobile was to register a 911 address on My T-Mobile. (Note: If you skip this step, a REG09 error may be displayed.)
https://support.t-mobile.com/commun...xel-2/topic/wi-fi/turn-on-off-wi-fi-calling/2
Click to expand...
Click to collapse
Great suggestion, thank you. As I just started my T Mobile service yesterday, I had not entered an e911 address yet, which the store rep had asked me to do. However, I just added it and still have no wifi calling ability. That said, I'm not sure if this takes time to work, in other words now that I've put in the address if it takes 24 hours or something?
The other thing is that based on the error message I get, which I posted on page one of this thread, "turn off airplane mode....", it does not suggest a problem with the e911 address. It feels like a settings issue to me. An advanced settings issue. All I've got is a gut feeling and nothing to back it up. I've asked T Mobile for help on this and they are only somewhat interested because my phone is not a T Mobile device.
And that link you've included is GREAT because it officially suggests the Pixel 2 has wifi calling capability on T Mobile. Not the Pixel 2 XL but...it still might be good ammo for me when asking for help when they're not so interested.
fiffan86 said:
Yes I have that when I used wifi to make a call
Click to expand...
Click to collapse
Thank you for posting this picture! This is exactly what I'm looking for and what I recognize from successful Wi-Fi calling on Project Fi recently. I can tell that you feel my pain here and I appreciate it.
Another indication I'm noticing is that when I'm in airplane mode and Wi-Fi is on, I get a "no connection" indication bar in Android messages. See the attached thumbnail. That should not be happening and further indicates something is amiss. I think when that goes away I will have with Wi-Fi calling capability.
I had to enable the wifi calling within the phone app and it worked.
AndrasLOHF said:
I had to enable the wifi calling within the phone app and it worked.
Click to expand...
Click to collapse
I've definitely done that, and gone through all of the menus.
To add insult to injury, my wife's MotoX4, on the same account and also brand new to T Mobile, has perfectly functioning wifi calling.
Thanks again for all of the responses. I may try going back to the store and having them re-provision my phone, in case something didn't get done right initially.
26kick said:
I've definitely done that, and gone through all of the menus.
To add insult to injury, my wife's MotoX4, on the same account and also brand new to T Mobile, has perfectly functioning wifi calling.
Thanks again for all of the responses. I may try going back to the store and having them re-provision my phone, in case something didn't get done right initially.
Click to expand...
Click to collapse
Whatever you don't, don't let any T-Mobile idiot try to lie to you saying you need a T-Mobile branded phone for wifi calling. When I was having issues getting this setup, one of the Tier 2 IT techs tried selling that line of bull****.
AndrasLOHF said:
Whatever you don't, don't let any T-Mobile idiot try to lie to you saying you need a T-Mobile branded phone for wifi calling. When I was having issues getting this setup, one of the Tier 2 IT techs tried selling that line of bull****.
Click to expand...
Click to collapse
I know, I've received that one already. But there's way too much evidence on here and other forms to suggest that it absolutely works with the pixel 2 and can be done. I just need to find someone at T-Mobile who's willing to work on it with me.
If anyone has a contact at T-Mobile who they like, PLEASE let me know.
Would anyone who hasn't already specified please let me know if your phone is a Verizon specific device as opposed to the Google Store Pixel 2 XL? No one has said that their Google version has wifi calling working yet and that is the only thing I can think of.
Thank you!
I have a pixel 3 xl with the latest December firmware, I'm on T-Mobile and I live in Florida. As I said everything is updated I have the call screen option in the phone app, I even have dark mode. Now when you go to change the voice selection in call screen, the voice part is greyed out and says "ACTIVATING CALL SCREEN REQUIRES WIFI " I connect to both wifi and hotspot and still not activating.I contacted Google like 15 times send bug report, still no help.
Omi755 said:
I have a pixel 3 xl with the latest December firmware, I'm on T-Mobile and I live in Florida. As I said everything is updated I have the call screen option in the phone app, I even have dark mode. Now when you go to change the voice selection in call screen, the voice part is greyed out and says "ACTIVATING CALL SCREEN REQUIRES WIFI " I connect to both wifi and hotspot and still not activating.I contacted Google like 15 times send bug report, still no help.
Click to expand...
Click to collapse
Not sure what's going on. Didn't know u could change the voice for call screening. Mine worked since day one.
I'm wondering if it's my Carrier. It's greyed out
This is a pic of what I am talking about
Omi755 said:
This is a pic of what I am talking about
Click to expand...
Click to collapse
Are you a beta tester of the phone app? I was a beta tester and I had an issue slightly different than yours. I was able to activate it but it didn't work. I opted out of the beta testing and then uninstalled and reinstalled the app and it worked. Maybe try to become a beta tester if you're not one already. Just throwing some suggestions out.
Ok I will try that thank you
Omi755 said:
This is a pic of what I am talking about
Click to expand...
Click to collapse
Did you try to activate using WIFI first?
NICEGYPT said:
Did you try to activate using WIFI first?
Click to expand...
Click to collapse
+1. You don't have any wifi running in that screen shot.
Sent from my [device_name] using XDA-Developers Legacy app