Mobile data issues with November update? - Google Pixel 4 XL Questions & Answers

Is anyone else experiencing data connection issues with the November update? I'm a Sprint subscriber and I noticed during my 12 mile commute to work and back, my Google Store unlocked 4 XL is having problems keeping the data connection. It goes from LTE to 3G to no data several times but I do have reception. It's as if it's having problems going from tower to tower. I definitely didn't have this issue out of the box or with my Pixel 2 XL.
Sent from my Pixel 4 XL using Tapatalk

I'm in Verizon and I have a similar issue with data speeds after the November update. I'm considering going back to the October update to see if that actually makes a difference

I'm on Google Fi and after the November update or the carrier services update (not sure which) my phone seems to prefer the weaker/slower Sprint signal. Call quality and data speeds are worse than before

redskykiter said:
I'm on Google Fi and after the November update or the carrier services update (not sure which) my phone seems to prefer the weaker/slower Sprint signal. Call quality and data speeds are worse than before
Click to expand...
Click to collapse
Im noticing the same thing.
Seems to prefer Sprint. I can use the Fi dialer codes [*1] to switch to Tmo. But upon traveling between cellular coverage areas, it sticks to Sprint again.
It's always been the other way round for me.
[*1] https://support.google.com/fi/forum/AAAARQbf-usIkOy8ZGNyPk/?hl=en&gpf=#!topic/project-fi/IkOy8ZGNyPk

pdfruth said:
Im noticing the same thing.
Seems to prefer Sprint. I can use the Fi dialer codes [*1] to switch to Tmo. But upon traveling between cellular coverage areas, it sticks to Sprint again.
It's always been the other way round for me.
[*1] https://support.google.com/fi/forum/AAAARQbf-usIkOy8ZGNyPk/?hl=en&gpf=#!topic/project-fi/IkOy8ZGNyPk
Click to expand...
Click to collapse
I'm hoping the dsds on fi will fix this.....

So looks like the December update has fixed my issues. Didn't have a problem streaming YouTube while going to and from work today.
Sent from my Pixel 4 XL using Tapatalk

I'm on Sprint and I've got this issue also. Last week I upgraded from the LG G7 to the Pixel 4 XL. When commuting to and from work, my data will drop from LTE, to 3G, to nothing. It mostly stays on 3G. With my G7, I always had LTE when driving this route. My Pixel has been on the November update, except for today's commute. Still had the unstable data issue with the December update. I've also updated PRL and config, with out any change in behavior.

sdowie76 said:
I'm on Sprint and I've got this issue also. Last week I upgraded from the LG G7 to the Pixel 4 XL. When commuting to and from work, my data will drop from LTE, to 3G, to nothing. It mostly stays on 3G. With my G7, I always had LTE when driving this route. My Pixel has been on the November update, except for today's commute. Still had the unstable data issue with the December update. I've also updated PRL and config, with out any change in behavior.
Click to expand...
Click to collapse
Yeah will have to do more driving around the area to confirm since it was littler only two drives for me.
Sent from my Pixel 4 XL using Tapatalk

pdfruth said:
Im noticing the same thing.
Seems to prefer Sprint. I can use the Fi dialer codes [*1] to switch to Tmo. But upon traveling between cellular coverage areas, it sticks to Sprint again.
It's always been the other way round for me.
[*1] https://support.google.com/fi/forum/AAAARQbf-usIkOy8ZGNyPk/?hl=en&gpf=#!topic/project-fi/IkOy8ZGNyPk
Click to expand...
Click to collapse
I was running the November .007.A3 image.
Now I'm running the December 012.A3 012.A1 image.
After wiping and flashing the December 012.A3 012.A1 factory image, my phone seems to stay on [stonger in my area] T-mobile network now, instead of switching/sticking to Sprint.

pdfruth said:
I was running the November .007.A3 image.
Now I'm running the December 012.A3 image.
After wiping and flashing the December 012.A3 factory image, my phone seems to stay on [stonger in my area] T-mobile network now, instead of switching/sticking to Sprint.
Click to expand...
Click to collapse
I think you mean '10.0.0 (QQ1B.191205.012.A1, Dec 2019)', I don't recall seeing 'A3' for the Pixel 4 XL.

Homeboy76 said:
I think you mean '10.0.0 (QQ1B.191205.012.A1, Dec 2019)', I don't recall seeing 'A3' for the Pixel 4 XL.
Click to expand...
Click to collapse
Yes, of course, you are exactly right.
Thinking Nov, and meant Dec.... I fat-fingered.
Fixed it

So here's an update for me on the issue. I still have a problem with data connection as it kept dropping from Kissimmee back to Tampa. Interestingly, I didn't notice the issue to Kissimmee. [emoji848]
Sent from my Pixel 4 XL using Tapatalk

Related

[Q] [Help] Sprint Nexus 6 - Missing Calls?

Has anyone else been missing calls occasionally with the Nexus 6 on sprint? I seem to miss atleast one or more every day with it. It is very intermittent but it does happen, but it's not good because some of them are important calls.
Any information or help would be appreciated!
cboz83 said:
Has anyone else been missing calls occasionally with the Nexus 6 on sprint? I seem to miss atleast one or more every day with it. It is very intermittent but it does happen, but it's not good because some of them are important calls.
Any information or help would be appreciated!
Click to expand...
Click to collapse
Are you using Google voice? Just curious because I've had it happen, but very rarely. By the way, check out my thread in general. Lots of Sprint users to ask.
http://forum.xda-developers.com/showthread.php?t=2949996
Spouted from shamu via Tapatalk
It happens to me 2-4 times everyday on my Sprint Nexus 6 with Android 5.0.1 (latest OTA). I got Nexus 6 on Dec 22 and missed calls 3-4 times a day that I know of. It happened very intermittently especially when I'm connected to WiFi at home. I went to Sprint store and they said it could be network related problem and they opened a ticket. Sprint rap from store mentioned that it could be issue related to CSFB on Spark network. Sprint never called me back regarding the issue. I decided to returned with restocking fees (they refused to waive the restocking fee) and got the HTC One M8 and issue went away.
Yesterday (Jan 8) I had to buy new Nexus 6 and activated on my sprint account (for work related reason), BAM! the missing calls issue showed up right away. From my experiences, I've other Spark phones (S5, LG G3, HTC One M8) and this issue only happened on Sprint Nexus 6.
If it is CSFB issue, it should show up on my M8 and it did not. Looks like this issue is Sprint Nexus 6 and Sprint network since I don't see other people reported on other network like ATT, T-Mobile and Verizon.
I searched for "Nexus 6 missing calls" on google, you will see a bunch of people reported on Sprint Community forum and issue is still not resolved.
The only work around is to put the phone in 3G mode. The csfb issue is at fault,as said above. So you have to leave LTE off. Still waiting for a damn resolution.
Is this still an issue in today? Just curious
kolyan said:
Is this still an issue in today? Just curious
Click to expand...
Click to collapse
Before I switched to Verizon (thank God) I had no issues using my Nexus 6 on Sprint in mid 2016. You know, other than the typical Sprint issues like poor coverage, no VoLTE, frequent 3G or 1x signal rather than LTE, etc...

Should I update now or wait for 6.0 on Fi?

I'm currently on T-mobile but will be switching to Fi in a week or two when my SIM gets delivered. Is it safe to update to 6.0 now while still on T-mobile or should I wait till I'm on Fi before doing the 6.0 update?
Thanks
My Guess
bmwjnky said:
I'm currently on T-mobile but will be switching to Fi in a week or two when my SIM gets delivered. Is it safe to update to 6.0 now while still on T-mobile or should I wait till I'm on Fi before doing the 6.0 update?
Thanks
Click to expand...
Click to collapse
My Guess would be you are ok to update now because they both use the same build "MRA58K"
Google Fi uses MRA58K
T-Mobile uses MRA58K
Other than some new battery saving and on tap if you are on 5.1 or higher you could probably wait two weeks. Up to you. I just finished doing it for my Nexus 6 on Verizon with the same build and had no issues.
bmwjnky said:
I'm currently on T-mobile but will be switching to Fi in a week or two when my SIM gets delivered. Is it safe to update to 6.0 now while still on T-mobile or should I wait till I'm on Fi before doing the 6.0 update?
Click to expand...
Click to collapse
jdice is correct. It will all be the same build. But be aware that there are issues reported by Fi users who have flashed to the MRA58K build, notably the loss of Band 12 data connectivity. Prognosis unknown.
From what I've seen/heard, flashing to MRA58K is fine on Fi, just keep the radio at the previous version. I'm running MRA58K on Fi with band 12. You can flash the MRA58K radio, but it does drop the band 12.
This is apparently not a bug. It's intended due to some regulatory hoopla on band 12.
What is the advantage to keeping a radio that uses band 12?
bmwjnky said:
What is the advantage to keeping a radio that uses band 12?
Click to expand...
Click to collapse
Might be better to do some googling on band 12. Seems like t-mobile needs it. Seems like the new Nexus 5x and 6p dont support it either.
www.androidpolice.com/2015/08/26/wh...2-lte-support-from-some-unlocked-smartphones/
Band 12 pushes farther into buildings and allows data while on voice when using T-mobile, or at least that's what I keep getting told.
Lagarde said:
Band 12 pushes farther into buildings and allows data while on voice when using T-mobile, or at least that's what I keep getting told.
Click to expand...
Click to collapse
This is what I found as well. I also found that it could possibly cause problems when making a band 12 LTE call to a land line and the call may not complete. The articles I found mentioning this issue say it's most likely to happen when trying to reach 911 when calling from your cell phone.
I haven't noticed a coverage issue in my area when using my Nexus 5 which doesn't support band 12 so I may go ahead with the update whenever it's pushed to my N6. Worst case if I notice a coverage issue I can put the different radio file back on it.

T-Mobile MRA58X build possibly did something to turn radio down a notch..

I just flashed this build to my N6 a couple a days ago and right off I noticed that while in my house I wasn't getting a good lte signal anymore. Now before I updated to this build I had good lte in my house almost full bars even in my basement I had at least 2 or 3 bars. Well needless to say I wasn't happy with that so I flashed back to what I was running before which was MRA58N and sometimes R . Well when I flashed back to these builds I noticed again that something wasn't right my signal seemed to have been broke! So I started flashing just radios to see if that would help but to no avail.. I even called T-Mobile and they said nothing was going on in my area and I should have good signal ,but in that same sentence he brought up the cellspot tower that they want everyone in low signal areas to use. Well to make a long story short I live in the city and before I flashed this latest T-Mobile build I had great service even in my house. The messed up thing is I can't fix my N6 now know matter what build I use my signal is no good in my house anymore. It's almost like they have put a patch of some sort to my phone and it modded my phone to not had goog lte service behind walls. My phone now jumps from 3g to h to the ! Mark even when it's in some spot! My battery sucks now because of the constant change. I'm getting a new n6 Monday and I hope it doesn't have this X build on it because I'm going to not flash and see if my signal stays the way it used to which was a good signal. If it has good signal I'm (and this is just my opinion) think there /T-Mobile is just trying to push this cellspot tower on as many as they can and help it along is turning down Rf in our phones so they don't work well indoors.. Just my opinion!
I want the MRA58X radio to see if I have the same problem. I have the MRA58M with the 27R radio and it runs good. I wanna see if the 30R radio gives me more band 12 because I live in a band 12 area but it switches back to band 4 with the quickness. Anybody have the 30R radio in zip forms? It'll be greatly appreciated.
scoonie said:
I want the MRA58X radio to see if I have the same problem. I have the MRA58M with the 27R radio and it runs good. I wanna see if the 30R radio gives me more band 12 because I live in a band 12 area but it switches back to band 4 with the quickness. Anybody have the 30R radio in zip forms? It'll be greatly appreciated.
Click to expand...
Click to collapse
Oh the MRA58X does have band 12. Im not flashing this X build when my new N 6 gets here! I'll stay far away from it! I'll stick with Google's official builds! MRA58N worked great for me on T-Mobile and WiFi calling and I had band 12 as well. When I flashed this X build everything went haywire... IMO!
Im on MRA58X just wanted to know why all these different numbers ? And why is the x bad?
samomamo said:
Im on MRA58X just wanted to know why all these different numbers ? And why is the x bad?
Click to expand...
Click to collapse
MRA58X screwed up my data/ signal it was jumping all over the place for me. It would literally go from band 12 to 2 then 4 the radio never had a chance to settle and was causing major battery drain. The messed up thing is for some reason I couldn't even revert back to other builds cause the radio stayed messed up no matter what build I was on or rom.. I truly think MRA58X messed my n6 up and T-Mobile thinks it may have as well that's why there sending me a new n6 by Monday..?
Oh I forgot this radio jumping all over the place happens anywhere I go even when Im not even moving..?
Flashing different radios don't help either... I'm truly think this build/X does something weird with the way the phone tracks signals and for me its a major problem
beachbum40 said:
MRA58X screwed up my data/ signal it was jumping all over the place for me. It would literally go from band 12 to 2 then 4 the radio never had a chance to settle and was causing mager battery drain. The messed up thing is for some reason I couldn't even revert back to other builds cause the radio stayed messed up no matter what build I was on or rom.. I truly think MRA58X messed my n6 up and T-Mobile thinks it may have as well that's why there sending me a new n6 by Monday..?
Click to expand...
Click to collapse
Interesting, i have moto x pure , nexus 5x amd yesterday got the nexus 6 from the Amazon deal, so before using the nexuses i was with the moto x and had no problems with it watching youtube videos or anything. Then 3 days ago i got the nexus 5x and put my tmobile sim in it and started using that and was noticing that the videos were stopping like i was feeling something is not right , then yesterday got the Nexus 6 and put the sim in this now im having the same issues i was on lollipop and was not offering me the marshmallow update, so i unlocked the bootloader and when the phone started it gave the 6.0 update . so now im on the MRA58X. And im thinking maybe the marshmallow has to do something with that? Because the moto x is on lolipop and its a beast. Sorry for the long write.
you guys do realize that you can use any nexus 6 radio on any version of android? well you can. if this radio is giving you issues, you are more than welcome to try any other radio that you like, until you find the one that works best for you. im on tmobile, am using the 27R radio, wifi calling works fine, and so does everything else.
simms22 said:
you guys do realize that you can use any nexus 6 radio on any version of android? well you can. if this radio is giving you issues, you are more than welcome to try any other radio that you like, until you find the one that works best for you. im on tmobile, am using the 27R radio, wifi calling works fine, and so does everything else.
Click to expand...
Click to collapse
I know but im thinking maybe its the T-Mobile giving problems with the signal not the phone itself? Or maybe the marshmallow is handling the radio differently then the lolipop?
samomamo said:
I know but im thinking maybe its the T-Mobile giving problems with the signal not the phone itself? Or maybe the marshmallow is handling the radio differently then the lolipop?
Click to expand...
Click to collapse
im using marshmallow on tmobile, in nyc, and no problems here. try a different radio, or a few, if the problems still persist then its probably a local tmobile issue. as i said before, im using the 27R radio.
simms22 said:
im using marshmallow on tmobile, in nyc, and no problems here. try a different radio, or a few, if the problems still persist then its probably a local tmobile issue. as i said before, im using the 27R radio.
Click to expand...
Click to collapse
I've tried every radio out there. Before MRA58X this would solve the problem but since I flashed the X build it seems every radio now that I try has same issue. It's like the new X build did some kind of software change and now I'm stuck with every single radio I use jumping all over the place. Before X I didn't have this issue..
I did call T-Mobile and they said there is no problems with the network in my area. They are sending me a new phone and I'm not flashing X period..?
beachbum40 said:
I've tried every radio out there. Before MRA58X this would solve the problem but since I flashed the X build it seems every radio now that I try has same issue. It's like the new X build did some kind of software change and now I'm stuck with every single radio I use jumping all over the place. Before X I didn't have this issue..
Click to expand...
Click to collapse
well, it could be not the radio thats the issue as well. tmo delayed marshmallows release because they found a bug, then waited for a rom update. the rom update might be the issue. no, im not on that last tmo build, but all the builds work on tmo, and all of tmos features too. maybe you should try a different marshmallow build?
simms22 said:
well, it could be not the radio thats the issue as well. tmo delayed marshmallows release because they found a bug, then waited for a rom update. the rom update might be the issue. no, im not on that last tmo build, but all the builds work on tmo, and all of tmos features too. maybe you should try a different marshmallow build?
Click to expand...
Click to collapse
I did go back to NRA58K then N then even R. But after I flashed the X build it screwed up something where now even on those older builds its screwed up my data. before I flash X I was using MRA58k N and r with no issues. But since I flashed X now on any build its screwed up . Hope that makes sense..?
I'd put up a logcat but I run purely stock anymore because of PAY which I have to have?when I get my new n6 I'm not going to flash MRA58X and I'll see how things work. If all is well then it was the X build or maybe just something in my phone broke. I guess I'll find out Monday..
I've been on stock x for about 4 days. I'm seeing none of these issues and I still have great battery life. Phone has been perfect. I took the ota though. I did not flash x
Sent from my Nexus 6 using XDA Free mobile app
I am having the exact same issue on my Nexus 6 after taking the MRA58X update. My phone never used to associate with anything besides LTE or HSPA. After updating my phone would switch between all different network modes, even those that I have never seen in my area before the update. The problem is especially bad when roaming around, but having the phone stationary can also exhibit this behavior. The sequence of events is similar to the following: LTE, HSPA, GPRS, EDGE, UMTS (3G), GPRS, EDGE, LTE for a couple seconds, GPRS, HSPA, GPRS... The network is so unstable on the 2G based networks which made using the Internet very difficult. Reverting the radio to the previous version does not fix the issue as reported by a previous user, and it seems like that the update has made some changes in a way to at affects how the radio associates with neighboring towers permanently. I would advise against taking this update if you are using T-Mobile and your device is out of warranty, as T-Mobile will most likely not cover the "damage" even though it may be OTA related. It does however seem that using the *#*#4636#*#* code and forcing the phone into LTE mode makes the mad network switching go away, although now the phone can't grab onto HSPA in LTE coverage holes and call issues in non VoLTE areas. My standby battery life also seems to be significantly reduced by all of this network searching in the background.
You have been warned...
I took the X Ota and the phone is working flawless for me. Sorry you guys are having issues
Sent from my Nexus 6 using Tapatalk
Clean flash back to lollipop and see if that changes anything.
If it doesn't, it isn't the phone/rom.
BTW I recently got the X update and so far so good but to be fair I'm on wifi alot.
(but LTE does work as before)
...and it there are indeed weird tower issues, a rep won't tell you specifics.
I'm on MRA58N with TMO in the Metro Chicago area, WiFi calling, VoLTE, and HD calling all work fine, but it seems as though my N6 is just stuck on band 4. I've never ever seen this device surf on band 12 (and I run the LTE Discovery app).

AT&T wifi calling on unlocked 4 XL

Long story short, I swapped my sim from my unlocked ATT 2 XL to the 4 XL and it fired right up with wifi calling and HD voice. I gave my wife the 2 XL and when I swapped her sim from her iphone I had to call ATT to get her hotspot working. The 2 XL is now in business but during that process they killed wifi calling on my 4 XL. I called again and they gave me the runaround about it being an unlocked device and that's a feature reserved only for ATT phones. I explained that it was working prior and they couldn't seem to figure it out. They said they were going to send me a software push that could take up to 24 hours and if that doesn't work, I'm out of luck. Anyone have any ideas on how to get wifi calling back? I appreciate it.
No resolution here, but same issue. though I had my sim in samsung phones most recently. At first, visual voicemail wasn't working either. I called, gave IMEI, and VVM started working a few minutes later. As far as wifi calling, they said my imei didn't show my phone as being LTE capable (or something to that effect). He knows pixels and couldn't understand why I was getting that error. He said he would submit a ticket to get it figured out. That was Thursday.
I had this problem also when I switched to AT&T when using a Verizon LG V30 flashed to AT&T software. Wifi-calling would not work, and their CS said only AT&T phones support it. Their system checked your IMEI and kills wifi-calling if it's not one of their phones.
Only solution is to get an official AT&T branded Pixel 4 XL.
Sent from my Pixel 4 XL using Tapatalk
Well this will suck. Anyone else confirm that unlocked pixel 4s don't have wifi calling on ATT?
Works fine on mine.
WiFI calling & HD Voice.
That blows, I have t mobile WiFi calling on my OnePlus 5t. Unlocked, not purchased from the carrier. Maybe it's time to switch provider
I can confirm that is DOES work on my unlocked Pixel 4XL and my wife's unlocked Pixel 3. Upper left corner says AT&T Wi-Fi Calling and when in a call, you see the WiFi signal meter by the call timer.
wattsja said:
I can confirm that is DOES work on my unlocked Pixel 4XL and my wife's unlocked Pixel 3. Upper left corner says AT&T Wi-Fi Calling and when in a call, you see the WiFi signal meter by the call timer.
Click to expand...
Click to collapse
Thanks I though it would be strange that it worked on the unlocked 3xl and not work on the 4.
It worked fine when they still had my Sim tied to my 2XL. Once they updated my imei it killed it. Still not working, I'll keep trying.
Sent from my Pixel 4 XL using Tapatalk
crazy3gz said:
It worked fine when they still had my Sim tied to my 2XL. Once they updated my imei it killed it. Still not working, I'll keep trying.
Sent from my Pixel 4 XL using Tapatalk
Click to expand...
Click to collapse
You might try talking to their tech support to see if they can add your imei to their system to allow wifi-calling.
Sent from my iPad using Tapatalk Pro
MicroMod777 said:
I had this problem also when I switched to AT&T when using a Verizon LG V30 flashed to AT&T software. Wifi-calling would not work, and their CS said only AT&T phones support it. Their system checked your IMEI and kills wifi-calling if it's not one of their phones.
Only solution is to get an official AT&T branded Pixel 4 XL.
Sent from my Pixel 4 XL using Tapatalk
Click to expand...
Click to collapse
I have an unlocked Pixlel 4XL, upgrading from a 3 XL. But I have had WiFi calling on my 2XL, and 3XL and now on my 4XL.
MicroMod777 said:
You might try talking to their tech support to see if they can add your imei to their system to allow wifi-calling.
Sent from my iPad using Tapatalk Pro
Click to expand...
Click to collapse
I've had a ticket open for a few days. This morning I get a text saying the ticket was resolved and to call. I tested wifi calling again first, but still same error. When I call I got directed to the retention dept. They said they were giving my $5 off my bill indefinitely, as long as I keep my unlimited plus plan. Then my ticket came up and I got transferred to tech support. They said they were not able to add the imei and my phone was not showing as VOLTE capable. The tech i talked to said she knew that was BS so she opened the ticket back up saying they would just have to add the imei on the backend. After a couple more return phone calls they said it's not supported because I didn't buy it from them. I've been with AT&T for many years, since they were Cingular. With the $5 off, my bill should only be about $80, plus I get HBO for free. That's not much more than what tmobile or google fi would be, but I really feel like leaving because of this ****.
I left att specially for this reason when I first got my pixel..... No other phone company has a rule that u can't utilize all the advanced carrier features unless you buy the phone from them.
I never tested but I suspect if you get an att branded phone that has WiFi calling on and operational and then just swap the SIM I to your P2XL without telling att it should work.
It's a provisional flag that needs to be activated.... It may happen automatically or you could ha e them manually do it for the att branded phone..... My assumption is that when you transfer the SIM to the P2XL the provisional flag won't turn off unless the carrier manually alters you account again... Like adding hotspot or something.
And what's even worse is you can buy an iPhone from the Apple store and wifi calling works.... I told them that is discrimination. They had no answer.....
I have an unlocked Pixel 4 XL and wifi calling has always worked just fine.
AT&T sucks for things like this. And now since AT&T offers the Pixel 4 they force AT&T customized firmware even if you buy the phone from Google. It looks like it's the Nexus 6 all over again. AT&T will likely be involved in updates now too even if the phone was bought from Google. It would have been better if AT&T didn't offer the Pixel 4. My Pixel 2 XL on AT&T gets updates from Google right away but no wi-fi calling.
bsg411 said:
I left att specially for this reason when I first got my pixel..... No other phone company has a rule that u can't utilize all the advanced carrier features unless you buy the phone from them.
Click to expand...
Click to collapse
Actually Sprint is/was like that because I didn't have WiFi calling, voLTE, or their visual voicemail on my Pixel 2 XL. Now, I surprisingly have all three with my Pixel 4 XL.
Sent from my Pixel 2 XL using Tapatalk
EeZeEpEe said:
Actually Sprint is/was like that because I didn't have WiFi calling, voLTE, or their visual voicemail on my Pixel 2 XL. Now, I surprisingly have all three with my Pixel 4 XL.
Click to expand...
Click to collapse
Yeah.... It's not fair. If we paying for the service and to use a carrier's network, why penalize a customer for not buying the phone thru the carrier.... Especially when they dont penalize people for buying the iPhone outside the carrier.
bsg411 said:
Yeah.... It's not fair. If we paying for the service and to use a carrier's network, why penalize a customer for not buying the phone thru the carrier.... Especially when they dont penalize people for buying the iPhone outside the carrier.
Click to expand...
Click to collapse
Curious but how did you setup your phone? Did you go through the eSIM method? I saw AT&T was an option along with Google Fi and Sprint. I was surprised to see Sprint there and during the setup I got the visual voicemail option. Not saying that setup is what gave me WiFi and voLTE as well but just wondering.
Sent from my Pixel 2 XL using Tapatalk
EeZeEpEe said:
Curious but how did you setup your phone? Did you go through the eSIM method? I saw AT&T was an option along with Google Fi and Sprint. I was surprised to see Sprint there and during the setup I got the visual voicemail option. Not saying that setup is what gave me WiFi and voLTE as well but just wondering.
Click to expand...
Click to collapse
I did the regular sim option. But I ended up leaving att because of this issue plus I wanted to see if I got better cellular reception on Verizon in general.... and my Verizon bill is cheaper than the att one was. But Ionly have a 5GB + rollover data plan versus a 6GB plan on att.
I want to follow this since I am done with AT&T branded phones. They only way I might get the Pixel 4 is through Google directly and I want Volte and Wifi calling, otherwise there is no point.
I hope that AT&T/Google will get many complaints and fix this nonsense.
Sent from my LG-H910 using Tapatalk

Bought T-Mobile Pixel 4 XL. If I get Verizon will Wi-Fi calling work?

Pretty much like the title states.
I have a T-Mobile Pixel 4 XL that currently has both AT&T and T-Mobile service on it. Rather than paying for two carriers, I'd like to just get Verizon as it seems to work everywhere here. T-Mobile is spotty as hell but the data is WAY faster than my AT&T.
I tested a friends Verizon SIM and did some speed tests but I forgot to test Wi-Fi calling which I will need inside my work building. That works on T-Mobile just fine but I can't get it working on AT&T. I see you can bug AT&T but no since if I just go Verizon anyway.
Thanks!
kdoggy said:
Pretty much like the title states.
I have a T-Mobile Pixel 4 XL that currently has both AT&T and T-Mobile service on it. Rather than paying for two carriers, I'd like to just get Verizon as it seems to work everywhere here. T-Mobile is spotty as hell but the data is WAY faster than my AT&T.
I tested a friends Verizon SIM and did some speed tests but I forgot to test Wi-Fi calling which I will need inside my work building. That works on T-Mobile just fine but I can't get it working on AT&T. I see you can bug AT&T but no since if I just go Verizon anyway.
Thanks!
Click to expand...
Click to collapse
The TMO pixel 4 runs the same firmware as an unlocked phone bought straight from Google. If Verizon offers wifi calling on their plans you should have no issues.
the.emilio said:
The TMO pixel 4 runs the same firmware as an unlocked phone bought straight from Google. If Verizon offers wifi calling on their plans you should have no issues.
Click to expand...
Click to collapse
WELL you would think but have you seen the AT&T thread about Wi-Fi calling on the unlocked Pixel 4 XL? GOOD LORD!
SO it seems AT&T blocks Wi-Fi calling on devices not *sold* by them so people are spending hours on the phone arguing with them and spoofing IMEI's to get it working. Some people are getting it done, others are sitting a wall and AT&T won't help.
Just wondering if Verizon pulls the same crap.
The AT&T thread:
https://forum.xda-developers.com/pixel-4-xl/help/att-wifi-calling-unlocked-4-xl-t3991909
kdoggy said:
WELL you would think but have you seen the AT&T thread about Wi-Fi calling on the unlocked Pixel 4 XL? GOOD LORD!
SO it seems AT&T blocks Wi-Fi calling on devices not *sold* by them so people are spending hours on the phone arguing with them and spoofing IMEI's to get it working. Some people are getting it done, others are sitting a wall and AT&T won't help.
Just wondering if Verizon pulls the same crap.
The AT&T thread:
https://forum.xda-developers.com/pixel-4-xl/help/att-wifi-calling-unlocked-4-xl-t3991909
Click to expand...
Click to collapse
Oh wow. Sucks to be with ATT lol. Hopefully Verizon isn't a PITA for ya.
kdoggy said:
WELL you would think but have you seen the AT&T thread about Wi-Fi calling on the unlocked Pixel 4 XL? GOOD LORD!
SO it seems AT&T blocks Wi-Fi calling on devices not *sold* by them so people are spending hours on the phone arguing with them and spoofing IMEI's to get it working. Some people are getting it done, others are sitting a wall and AT&T won't help.
Just wondering if Verizon pulls the same crap.
The AT&T thread:
https://forum.xda-developers.com/pixel-4-xl/help/att-wifi-calling-unlocked-4-xl-t3991909
Click to expand...
Click to collapse
Have never had an issue with WiFi calling on any of my pixels - OG bought from Google and my 4XL from Amazon both have wifi calling (on unlimited plan).
T
I have Pixel 4 XL on T-Mobile and wifi calling works just fine. Can't tell you the spped since I never treated that but I use it inside the hospital where I work at since my cellular signal isn't the strongest
Belfire29 said:
I have Pixel 4 XL on T-Mobile and wifi calling works just fine. Can't tell you the spped since I never treated that but I use it inside the hospital where I work at since my cellular signal isn't the strongest
Click to expand...
Click to collapse
Is T-Mobile variant on android 10 root able?
jerryspring said:
Is T-Mobile variant on android 10 root able?
Click to expand...
Click to collapse
As far as I know as long as your phone isn't owed money... Meaning your not doing payments and you own the phone outright than yes. There is a setting under developer options called OEM Unlocking to unlock the phone from T-Mobile. Once unlocked from T-Mobile it will always unlock the bootloader.
At least that is what I read. I'm not sure how to do any of that anyway with rooting and such. I'm still trying to figure out how to screen recording on this phone.
Curious... Did an unlocked t mobile pixel 4 XL end up working fine on verizon? Like regular calls and data?

Categories

Resources