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!
Related
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
Has anyone noticed that WiFi assistant blocks outgoing email when using a third party app?
Better wording for better results...
NWTSCL said:
Has anyone noticed that WiFi assistant blocks outgoing email when using a third party app?
Click to expand...
Click to collapse
I have a 3rd party app named.....
When ever i am using Wifi Assistant i cant sent email.
Does anyone else experience the same issue?
---------- Post added at 12:38 AM ---------- Previous post was at 12:37 AM ----------
parakleet said:
I have a 3rd party app named.....
When ever i am using Wifi Assistant i cant sent email.
Does anyone else experience the same issue?
Click to expand...
Click to collapse
Sounds like you app is having a problem with the securing of teh tunnel.
Could be any number of reasons.
NAT Translation, packet changes.
You might want to check out there support
I do not have that issue but I use to have problems with wifi assistant blocking open wifi networks as the open networks would connect but show no internet connection so I just learned to not use the wifi assistant at all.
I first reported this to Google when the Pixel was released. I spoke with them again today. After a rather lengthy call, the tech finally said that he was aware of my initial call, but that it is difficult for them to fix because it is "very uncommon". Happens to me every time the Assistant is connected.
NWTSCL said:
I first reported this to Google when the Pixel was released. I spoke with them again today. After a rather lengthy call, the tech finally said that he was aware of my initial call, but that it is difficult for them to fix because it is "very uncommon". Happens to me every time the Assistant is connected.
Click to expand...
Click to collapse
I had reported my issue also and verizon got google on the phone with us and just discussed what the issue was and said they would get back with me but did they ? Answer is of course not nothing ever back and that was back in early November.
Yeah their cs sucks. I even upgraded to a 128 xl and had same issue on it and back then my open wifi would not work at all would connect but list no internet and the sign in accept screen for all the open networks the phones would not load them fully to hit accept.
Up until about a month ago I could not get any open wifi to work at all and still have issues at times and I have to hit forget network and re add sometimes even multiple times and even turn on or off wifi assistant and turn wifi on and off and even toggle airplane mode numerous times. And all these times my Unlocked Htc 10 would work great on the same open wifi networks.
And the stupid thing was these pixel xls always worked great on wifi networks that require a password, go figure they try to add more protection and just lock us out from using open networks so we have to use our data plans yeah verizon likes that part lol more money for them lol.
NWTSCL said:
I first reported this to Google when the Pixel was released. I spoke with them again today. After a rather lengthy call, the tech finally said that he was aware of my initial call, but that it is difficult for them to fix because it is "very uncommon". Happens to me every time the Assistant is connected.
Click to expand...
Click to collapse
Does it happen with any other VPN service?
What is the app?
M9guy said:
I had reported my issue also and verizon got google on the phone with us and just discussed what the issue was and said they would get back with me but did they ? Answer is of course not nothing ever back and that was back in early November.
Yeah their cs sucks. I even upgraded to a 128 xl and had same issue on it and back then my open wifi would not work at all would connect but list no internet and the sign in accept screen for all the open networks the phones would not load them fully to hit accept.
Up until about a month ago I could not get any open wifi to work at all and still have issues at times and I have to hit forget network and re add sometimes even multiple times and even turn on or off wifi assistant and turn wifi on and off and even toggle airplane mode numerous times. And all these times my Unlocked Htc 10 would work great on the same open wifi networks.
And the stupid thing was these pixel xls always worked great on wifi networks that require a password, go figure they try to add more protection and just lock us out from using open networks so we have to use our data plans yeah verizon likes that part lol more money for them lol.
Click to expand...
Click to collapse
I did some reading back when I first got a Nexus 6P, and it stated that the secure assistant feature will keep you from using unsecured networks that have low reception or strength. I don't know of the legitimacy of this, and the only reason I researched it was because I had the issue of connected but no internet. I idea I walked away with was that the connection was not good enough for the VPN to actually do it's job? When I don't use the Secure Assistant on the network(I work at a hospital), the connection often drops off or I often get the sit and wait for things to load issue.
parakleet said:
Does it happen with any other VPN service?
What is the app?
Click to expand...
Click to collapse
I don't know about any other service. My app is called AquaMail Pro
NWTSCL said:
I don't know about any other service. My app is called AquaMail Pro
Click to expand...
Click to collapse
Hey have you ever tried Blue mail or type mail ? I have tried most including Aquamail and Blue mail and Type mail seem to be some of the best, they are some of the very few apps that have a lot of downloads and have a 4.6 and 4.7 rating. I just thought you might have an interest, if not and if you are happy with that app more power to ya
I have a Magisk rooted Pixel 2 XL running Android Pie and had no problem editing the buildprop (net.tethering.noprovisioning=true) and adb settings (tether_dun_required 0) to enable the native hotspot and bypass the carrier tether check. Or so I thought...
Yesterday I received a dreaded text message from my carrier (Cricket): "our records indicate you have used your Cricket phone as a 'mobile hotspot' without the Cricket Mobile hotspot feature..." threatening to throttle me due to terms of use violation.
Am I mistaken that the tether_dun_required 0 adb setting disallows the carrier from being able to differentiate between tethered data usage and normal data usage by the device itself? Could this be something that is no longer working as expected in Pie? (I had tethered with this method for a while on Oreo and hadn't received a warning from Cricket until upgrading to Pie. Could be coincidental...)
Any insight is appreciated, thank you.
nobaddreams said:
I have a Magisk rooted Pixel 2 XL running Android Pie and had no problem editing the buildprop (net.tethering.noprovisioning=true) and adb settings (tether_dun_required 0) to enable the native hotspot and bypass the carrier tether check. Or so I thought...
Yesterday I received a dreaded text message from my carrier (Cricket): "our records indicate you have used your Cricket phone as a 'mobile hotspot' without the Cricket Mobile hotspot feature..." threatening to throttle me due to terms of use violation.
Am I mistaken that the tether_dun_required 0 adb setting disallows the carrier from being able to differentiate between tethered data usage and normal data usage by the device itself? Could this be something that is no longer working as expected in Pie? (I had tethered with this method for a while on Oreo and hadn't received a warning from Cricket until upgrading to Pie. Could be coincidental...)
Any insight is appreciated, thank you.
Click to expand...
Click to collapse
Before I joined ProjectFi when I received these I told them to pound sand.
Every conversation I had with them was based on amount of usage, but they could never tell how the data was being consumed.
I wouldnt worry until I was given something in writing, hell even an email.
The carriers have multiple methods of detecting tethering, and there is no way to effectively hide your activity. Where you were caught tethering, I would take the threat seriously. For more details, read this: How can phone companies detect tethering, including a WiFi hotspot?
parakleet said:
Before I joined ProjectFi when I received these I told them to pound sand.
Every conversation I had with them was based on amount of usage, but they could never tell how the data was being consumed.
I wouldnt worry until I was given something in writing, hell even an email.
Click to expand...
Click to collapse
I was thinking it may be a bluff based on spiked usage. I haven't nearly hit Cricket's stated throttle point of 22GB, but I would say my typical usage over the last year was maybe 4GB/mo where as this month I'm over 15GB. However, before my Pixel 2 XL I have used FoxFi on an S4 for years without a single peep from Cricket, so the instant warning after using my new Pixel 2 XL gives me pause. I definitely don't want to go back to my antique S4 but I can't be without hotspot capability. Thanks for the reply.
nobaddreams said:
I was thinking it may be a bluff based on spiked usage. I haven't nearly hit Cricket's stated throttle point of 22GB, but I would say my typical usage over the last year was maybe 4GB/mo where as this month I'm over 15GB. However, before my Pixel 2 XL I have used FoxFi on an S4 for years without a single peep from Cricket, so the instant warning after using my new Pixel 2 XL gives me pause. I definitely don't want to go back to my antique S4 but I can't be without hotspot capability. Thanks for the reply.
Click to expand...
Click to collapse
I'll be in a similar situation ( BTW, would you share a guide on how to edit the build.prop mate? I can't find any),
the difference is that I'd lose my GUDP, that's a NO NO. I don't know if I'm destined to keep using my Note 4 and FoxFi...
Any help is greatly appreciated guys.
The_Forastero said:
I'll be in a similar situation ( BTW, would you share a guide on how to edit the build.prop mate? I can't find any),
the difference is that I'd lose my GUDP, that's a NO NO. I don't know if I'm destined to keep using my Note 4 and FoxFi...
Any help is greatly appreciated guys.
Click to expand...
Click to collapse
If you're rooted, install BuildProp Editor and follow these instructions to unblock your native hotspot.
If you aren't yet rooted, this is the best guide I have found.
ON A SIDE NOTE, regarding my original post, I have decided to push on with tethering in spite of the warning text from Cricket. Long story short, this is my 3rd Pixel 2 XL (been searching for "the right one") and in the process of rooting my latest one, I recalled that when restoring the first one back to the stock image to return the device, I had a TYPO in my adb settings to set the DUN requirement to 0. So I am thinking that any tethering I did ON THAT FIRST DEVICE was detectable, and it may have taken Cricket some time to get around to warning me about it. Now, all settings being verified on my keeper 2 XL, I am going to "keep calm and tether on" to see if I am in the clear.
I have also applied TTL 64 using TTL Editor as an additional protection measure. Tough to say whether it's truly effective, but it's an added measure none the less.
nobaddreams said:
If you're rooted, install BuildProp Editor and follow these instructions to unblock your native hotspot.
If you aren't yet rooted, this is the best guide I have found.
ON A SIDE NOTE, regarding my original post, I have decided to push on with tethering in spite of the warning text from Cricket. Long story short, this is my 3rd Pixel 2 XL (been searching for "the right one") and in the process of rooting my latest one, I recalled that when restoring the first one back to the stock image to return the device, I had a TYPO in my adb settings to set the DUN requirement to 0. So I am thinking that any tethering I did ON THAT FIRST DEVICE was detectable, and it may have taken Cricket some time to get around to warning me about it. Now, all settings being verified on my keeper 2 XL, I am going to "keep calm and tether on" to see if I am in the clear.
I have also applied TTL 64 using TTL Editor as an additional protection measure. Tough to say whether it's truly effective, but it's an added measure none the less.
Click to expand...
Click to collapse
You know what, I was thinking... Maybe using a VPN could help? This might be a good chance to find out. Do you have a VPN account? BTW, thanks for the help. I'll go try it today. I've been looking for this for weeks.
nobaddreams said:
I have a Magisk rooted Pixel 2 XL running Android Pie and had no problem editing the buildprop (net.tethering.noprovisioning=true) and adb settings (tether_dun_required 0) to enable the native hotspot and bypass the carrier tether check. Or so I thought...
Yesterday I received a dreaded text message from my carrier (Cricket): "our records indicate you have used your Cricket phone as a 'mobile hotspot' without the Cricket Mobile hotspot feature..." threatening to throttle me due to terms of use violation.
Am I mistaken that the tether_dun_required 0 adb setting disallows the carrier from being able to differentiate between tethered data usage and normal data usage by the device itself? Could this be something that is no longer working as expected in Pie? (I had tethered with this method for a while on Oreo and hadn't received a warning from Cricket until upgrading to Pie. Could be coincidental...)
Any insight is appreciated, thank you.
Click to expand...
Click to collapse
I've had cricket for about 4 years, always use the buildprop trick for hotspots, bluetooth tethering, and usb tethering and have never received a message like this. That being said, I have the 2.5gb plan so I throttle much sooner than you. If they aren't bluffing, its likely I haven't received a warning just because I have so little LTE data.
The_Forastero said:
You know what, I was thinking... Maybe using a VPN could help? This might be a good chance to find out. Do you have a VPN account? BTW, thanks for the help. I'll go try it today. I've been looking for this for weeks.
Click to expand...
Click to collapse
I am considering using a VPN. Have you done this with success? I have no experience with VPNs but I am thinking they are becoming more of a good idea...
nobaddreams said:
I am considering using a VPN. Have you done this with success? I have no experience with VPNs but I am thinking they are becoming more of a good idea...
Click to expand...
Click to collapse
I'd like to try it as soon as I can enable tethering. I hope I'm not too dumb not to understand the steps.
nobaddreams said:
I am considering using a VPN. Have you done this with success? I have no experience with VPNs but I am thinking they are becoming more of a good idea...
Click to expand...
Click to collapse
I'm sorry, it's been almost three weeks but I'm too stupid to be able to figure this out. Just can't find any answer/help in this forum anymore. What happened to this place?
The_Forastero said:
I'm sorry, it's been almost three weeks but I'm too stupid to be able to figure this out. Just can't find any answer/help in this forum anymore. What happened to this place?
Click to expand...
Click to collapse
I'd like to know too. I asked this a couple weeks ago. No response
If you're rooted with magisk, there's a module for tethering.
Larzzzz82 said:
If you're rooted with magisk, there's a module for tethering.
Click to expand...
Click to collapse
Do you know what it's called?
Are you using magisk? If so, go into the downloads and search tethering. It'll pop up.
Larzzzz82 said:
Are you using magisk? If so, go into the downloads and search tethering. It'll pop up.
Click to expand...
Click to collapse
Which one?
The one I'm using is called tethering enabler, by stangri.
vpn should work, but it is tricky to get the vpn to pass through to the wifi hotspot.
there is a seperate app to get it to work. its possible they could notice the vpn usage (unless you try obfuscated servers) but i dont know how hardcore they are going to be about this
fixxxer0 said:
vpn should work, but it is tricky to get the vpn to pass through to the wifi hotspot.
there is a seperate app to get it to work. its possible they could notice the vpn usage (unless you try obfuscated servers) but i dont know how hardcore they are going to be about this
Click to expand...
Click to collapse
VPN automatically counts as tethering even if your not tethering and gets throttled.
---------- Post added at 02:30 AM ---------- Previous post was at 02:26 AM ----------
I've been looking through every forum and cannot find a viable solution. TTL editor doesn't seem to make a difference. Changing build prop doesn't work. WiFi tether router is a bust. And when I even turn on my VPN before I even try to tether I am throttled.
That being said, I have made progress. In no pro but I understand a little... I have just stated tinkering with "netguard" and tweeking settings then turned on "VPN Hotspot" S it's seems like in getting throttled less than normal. I'm still not happy but it's an improvement.
Anybody found a solution for that? :-(
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
I have no WiFi calling at all, I stumped 2 Verizon locations and multiple techs. No one knows why I have no WiFi Calling.... What's wrong I need some help here
Griingo said:
I have no WiFi calling at all, I stumped 2 Verizon locations and multiple techs. No one knows why I have no WiFi Calling.... What's wrong I need some help here
Click to expand...
Click to collapse
Are you using anything like Package Disabler Pro?
I ask because I did have WiFi calling, but it's also missing for me now too and I've disabled a load of packages/apps
Although I'm fairly sure the setting was in the actual Phone app settings rather than OS connection settings
Nope
Griingo said:
Nope
Click to expand...
Click to collapse
Maybe a bug in the latest update then, the app itself is there but the setting is not
It's super weird my friend has the same phone and he has it
Yea I also had it, I have switched CSCs too though from carrier CSC to unlocked, maybe why for me although I've done that on all my Samsung phones and always still had WiFi calling
Read some people saying factory resetting brought the option back, but I never really needed it, very rare I lose signal in the house which was why I didn't enable it
---------- Post added at 23:57 ---------- Previous post was at 23:51 ----------
Griingo said:
It's super weird my friend has the same phone and he has it
Click to expand...
Click to collapse
I just rebooted the phone, and its back, WiFi calling is in the phone app settings
And another new setting appeared called "Rich Communications" in OS connection settings screen
https://i.imgur.com/XUmwLyr.png
https://i.imgur.com/c1snJuU.png