Just curious if anyone else knows when AT&T plans on whitelisting the Pixel 4 and Pixel 4 XL for RCS. It's honestly pretty sad that they haven't already.
Carrier whitelist shouldn't be required any more as the recent updates to Messages and Carrier Services should connect you to Google's RCS servers instead of your carrier's servers. If you're still not seeing it make sure you have the latest versions of those apps.
This is the "RCS available to all US Android users" that has been all over the Android news sites lately.
Sent from my Pixel 4 using Tapatalk
Related
Does anyone know if a Nexus 6P bought on contract from a carrier (I'm in Canada and looking at Bell) if the OS updates are received in the usual (quick-ish) fashion directly from Google or if the Carriers get in the way and delay them?
I'm on Rogers and I receive them right away.
It was bought on contract.
Sent from my Nexus 6P using Tapatalk
You shouldn't see any delay. This phone works out of the box on virtually every carrier.
Since Sprint is also a CDMA network, would a Sprint S7 Edge work on Verizon? Thanks!
Possibly, but not likely. Verizon has to white list the phones used on its network, and won't generally approve a non-verizon phone (except sometimes, iPhones, Nexus phones, some Motorola phones).
Sent from my SM-G935V using Tapatalk
IF the Sprint Version has Band 13 by default and is approved to use it then Verizon has to accept it and validate the device required by FCC regulations (Block C). If they say due to security reasons or what not they have to prove it not you.
Tidbits said:
IF the Sprint Version has Band 13 by default and is approved to use it then Verizon has to accept it and validate the device required by FCC regulations (Block C). If they say due to security reasons or what not they have to prove it not you.
Click to expand...
Click to collapse
Verizon can not lock their phones that use band 13, there is no requirement for them to accept other phones. This has been their policy for a very long time, unless you have evidence for the contrary I'll not believe they've changed their policy.
Sent from my SM-G935V using Tapatalk
_Dennis_ said:
Verizon can not lock their phones that use band 13, there is no requirement for them to accept other phones. This has been their policy for a very long time, unless you have evidence for the contrary I'll not believe they've changed their policy.
Sent from my SM-G935V using Tapatalk
Click to expand...
Click to collapse
We are talking the sprint version working on Verizon. There is a requirement for them to accept phones that support band 13. They have to meet certain requirements to allow them. The reason why the iphone 6 and higher, Nexus 6 and higher and the Motorola X 2015 can connect. The policy has always been the same since block c. Only now manufacturers have been taking advantage of it. Verizon even has to give how to connect to VoLTE and such to manufacturers to connect to their network.
Sent from my SM-G935T using Tapatalk
Tidbits said:
We are talking the sprint version working on Verizon. There is a requirement for them to accept phones that support band 13. They have to meet certain requirements to allow them. The reason why the iphone 6 and higher, Nexus 6 and higher and the Motorola X 2015 can connect. The policy has always been the same since block c. Only now manufacturers have been taking advantage of it. Verizon even has to give how to connect to VoLTE and such to manufacturers to connect to their network.
Sent from my SM-G935T using Tapatalk
Click to expand...
Click to collapse
Try a Sprint S7 IMEI here, see how well it works.
http://www.verizonwireless.com/bring-your-own-device/
Sent from my SM-G935V using Tapatalk
You are not listening. Does the Sprint version support band 13? No then it won't work automatically. If it did then it has to fit a few other criteria and then it can work on Verizon. Those unlocked and unbranded I listed are just examples. They don't even have Verizon bloat. Any manufacturer can take advantage of it, but right now very few do
Sent from my SM-G935T using Tapatalk
Tidbits said:
You are not listening. Does the Sprint version support band 13? No then it won't work automatically. If it did then it has to fit a few other criteria and then it can work on Verizon. Those unlocked and unbranded I listed are just examples. They don't even have Verizon bloat. Any manufacturer can take advantage of it, but right now very few do
Sent from my SM-G935T using Tapatalk
Click to expand...
Click to collapse
Cool. The hardware supports it, just not the firmware.
What is the limiting factor? Where is the documents that back up your claims?
You know what though, I don't care. I'm done with this. Have a wonderful day.
Sent from my E6683 using Tapatalk
_Dennis_ said:
Cool. The hardware supports it, just not the firmware.
What is the limiting factor? Where is the documents that back up your claims?
You know what though, I don't care. I'm done with this. Have a wonderful day.
Sent from my E6683 using Tapatalk
Click to expand...
Click to collapse
Sprint disabling it, and it isn't licensed for that specific device by the FCC. It's similar to the Nexus 4 with LTE in which Google removed support. Due to that Sprint version is deems band 13 doesn't exist, and therefore Verizon doesn't have to comply with block C rules.
Samsung could have made their one device model like Apple and it would have been it, and Verizon had to let them all go but making submodels is what killed it.
Sent from my SM-G935T using Tapatalk
Yes it works SM-G930V via Odin works fine on the Sprint variant but no guarantee Verizon doesn't kick you off their network since the imei is a "non approved" phone. Typing from a Sprint burned to Verizon right now but only been active 4 hrs or so...
I'm curious on how to do this.... I have a Galaxy S7 sprint, that I'd like to work for Verizon. Any how to out there?>
Was given the s7 tonite for a temp replacement for my broken note 8 The s7 is a verizon phone my coverage is sprint. I've read all the bs concerning how the services are incompatible and frankly I don't care or buy it. So far I've gotten access to mobile 3G data (can load webpages & access play store) but still no cell service. Not sure which it was that caused access to be available for data, but I set up APN for sprint and switched the network to GSM and manually selected sprint. (Wouldn't connect) but i think something in that process bypassed something to give me data access...which in my mind says cell service can be achieved as well. Any insight or ideas shoot em please.
How did you get the sprint variant to work on the verizon network?
I have a 64 GB Nexus 6P, currently running Android Nougat 7.0. Verizon is my provider. On 12.5.16, I received a notification that the update to 7.1.1 was available, but when I attempted an OTA, I did not get the update, nor the security patch. I read on the internet that Verizon blocked the update for Nexus 6P customers due to a SIM issue with this update. I am still running 7.0 and Settings shows my phone as up to date. Verizon has not been able to provide any information about why this update was blocked. I was told by a T-Mobile store supervisor that their Nexus 6P customers did get the update to 7.1.1. If I were to leave Verizon and switch to T-Mobile, allowed the update to 7.1.1, but then found T-Mobile reception was not good, I don't think I could return to Verizon with a phone updated to a version they had blocked. I was looking forward to Visual Voicemail, which I believe was introduced in 7.1.1. Could someone tell me if this block from Verizon is expected to affect all future Android upgrades for my Nexus 6P or is Google known to be working on a fix. ?Am I blocked from any future upgrades now that Verizon has blocked this one? Verizon told me there was a similar issue for the Pixel, but it was fixed because Verizon sells the Pixel, but never sold the Nexus 6P.
promosinc said:
I have a 64 GB Nexus 6P, currently running Android Nougat 7.0. Verizon is my provider. On 12.5.16, I received a notification that the update to 7.1.1 was available, but when I attempted an OTA, I did not get the update, nor the security patch. I read on the internet that Verizon blocked the update for Nexus 6P customers due to a SIM issue with this update. I am still running 7.0 and Settings shows my phone as up to date. Verizon has not been able to provide any information about why this update was blocked. I was told by a T-Mobile store supervisor that their Nexus 6P customers did get the update to 7.1.1. If I were to leave Verizon and switch to T-Mobile, allowed the update to 7.1.1, but then found T-Mobile reception was not good, I don't think I could return to Verizon with a phone updated to a version they had blocked. I was looking forward to Visual Voicemail, which I believe was introduced in 7.1.1. Could someone tell me if this block from Verizon is expected to affect all future Android upgrades for my Nexus 6P or is Google known to be working on a fix. ?Am I blocked from any future upgrades now that Verizon has blocked this one? Verizon told me there was a similar issue for the Pixel, but it was fixed because Verizon sells the Pixel, but never sold the Nexus 6P.
Click to expand...
Click to collapse
There are many "stuck" posts on XDA, but sometimes the Verizon ones get buried. Your phone is not blocked from getting an update, nor have Verizon phones been blocked- it's just stuck and sometimes that just happens. There is a 7.1.1 January update expressly for Verizon phones (N4F26J) that includes a new modem to address the Visual Voicemail and other Verizon specific issues. You can try various methods to force the OTA again such as a SIM swap, but you can also download and flash the full OTA directly to the phone. You don't have to be unlocked or rooted to do this. To address the other part of your question, you can definitely swap out SIMS from different carriers and go back and forth- not just in the US but many countries overseas as well. That is the beauty (and purpose) of owning a carrier unlocked phone.
Has anyone used the OnePlus 5 on US Cellular? From everything I can find it looks like it should be supported, but there's also reports with USC intentionally blocking or severely limiting phones they don't sell. I haven't found anyone saying they've used this phone on the USC network.
I noticed yesterday when I went to download the March OTA image that there was one specific for AT&T. Anyone know why the Pixel 4 has a specific image for AT&T?
spielnicht said:
I noticed yesterday when I went to download the March OTA image that there was one specific for AT&T. Anyone know why the Pixel 4 has a specific image for AT&T?
Click to expand...
Click to collapse
No. But it was pulled because it failed certification and was not passing Safety Net. So, right now, there's only the other build available.
Thanks for that. I just rant into an article on Android Police that it's coming back soon. I'm still curious as to how this differs from the standard ROM. My curiosity is driven by the fact that I'm on AT&T and haven't been able to enable Wifi Calling or Number Sync. I was told by the AT&T reps that it's because the phone doesn't support VoLTE, which is BS. While AT&T generally blocks non-AT&T purchased phones (unlocked or not), the Pixel line is exempt and supports all of their services. I had no issues with the Pixel 3.
EVR_PR said:
No. But it was pulled because it failed certification and was not passing Safety Net. So, right now, there's only the other build available.
Click to expand...
Click to collapse
spielnicht said:
Thanks for that. I just rant into an article on Android Police that it's coming back soon. I'm still curious as to how this differs from the standard ROM. My curiosity is driven by the fact that I'm on AT&T and haven't been able to enable Wifi Calling or Number Sync. I was told by the AT&T reps that it's because the phone doesn't support VoLTE, which is BS. While AT&T generally blocks non-AT&T purchased phones (unlocked or not), the Pixel line is exempt and supports all of their services. I had no issues with the Pixel 3.
Click to expand...
Click to collapse
That exemption was for the Pixel 2 and 3, which AT&T didn't sell. Now that they sell the 4/XL, they are uncertifying unlocked Pixel 4s. Only AT&T bought models are authorized by their servers to have VoLTE and WiFi Calling. Without VoLTE, you won't have access to WiFi Calling.
I didn't even know AT&T sold the Pixel 4. One of the primary reasons I bought another Pixel was because of AT&T support of unlocked Pixels. I guess not anymore.
EVR_PR said:
That exemption was for the Pixel 2 and 3, which AT&T didn't sell. Now that they sell the 4/XL, they are uncertifying unlocked Pixel 4s. Only AT&T bought models are authorized by their servers to have VoLTE and WiFi Calling. Without VoLTE, you won't have access to WiFi Calling.
Click to expand...
Click to collapse
Delete post. Wrong forum.... ;(
EVR_PR said:
That exemption was for the Pixel 2 and 3, which AT&T didn't sell. Now that they sell the 4/XL, they are uncertifying unlocked Pixel 4s. Only AT&T bought models are authorized by their servers to have VoLTE and WiFi Calling. Without VoLTE, you won't have access to WiFi Calling.
Click to expand...
Click to collapse
I had an at&t pixel 4 from November. Had to do warranty and received a Google pixel 4 in return. I have wifi calling.
Btw, yes I unlocked the bootloader immediately lol
bmwh0r3 said:
I had an at&t pixel 4 from November. Had to do warranty and received a Google pixel 4 in return. I have wifi calling.
Btw, yes I unlocked the bootloader immediately lol
Click to expand...
Click to collapse
It's a different case because you already had a registered AT&T Pixel 4 IMEI before you switched to an unlocked model. AT&Ts servers will still read your phone as an authorized model. Try getting an unlocked Pixel 4a or 5 (or whatever model comes next, for example) instead of a branded AT&T model and you will have the same issue as I.
EVR_PR said:
It's a different case because you already had a registered AT&T Pixel 4 IMEI before you switched to an unlocked model. AT&Ts servers will still read your phone as an authorized model. Try getting an unlocked Pixel 4a or 5 (or whatever model comes next, for example) instead of a branded AT&T model and you will have the same issue as I.
Click to expand...
Click to collapse
I had the 3a, 2, 1 and nexus devices before. The 4 was my first "at&t" phone.
EVR_PR said:
That exemption was for the Pixel 2 and 3, which AT&T didn't sell. Now that they sell the 4/XL, they are uncertifying unlocked Pixel 4s. Only AT&T bought models are authorized by their servers to have VoLTE and WiFi Calling. Without VoLTE, you won't have access to WiFi Calling.
Click to expand...
Click to collapse
So, i know it is a pain and it's because they want you to buy their "branded" crap. However, for a workaround, find an at & t branded iphone that has volte vowifi capability and put your sim in there. Then call AT & T or use their live chat support. Tell them you are trying to activate your sim with volte and vowifi for your sim. They will activate it for the that sim card. Once you verified the iphone shows volte and vowifi take your sim out and put it in android phone of choice. I found this out since my sister (sadly) is an apple user and i use all android phones. Once the sim is unlocked for volte and vowifi i haven't had any issues on my pixel or my op 6 or op 7 pro.
Good luck. Might be a pain if you don't have access to an i phone, but swappa is fairly reasonable for a 7 that you can use and then sell to a friend or something . Good luck.