Database Users

Possible phone use on Verizon 7.7

Let me note: I am not a dev nor programmer.
With the similiarities of the P6800 and the Verizon 7.7, I threw together a rom w/ stock SCH-I815 samsung/verizon kernel using the P6800 frameworks and apps into the Verizon 7.7 and removed most bloat. The LTE/Verizon antennas aren't recognized by the device at all but everything else was working.
Now, you can't swap the phone.apk's around without the framework's else you'll experience FCs. So obviously I'll need to use the base stock apps and frameworks and go through the 2 framework files hunting about.
Has anyone else with the Verizon 7.7 taken a look into this?

I'm curious if you've made any progress on this?

Not yet, probably be a week before I even look through the files again. But I believe it's fully possible to get phone use
Sent from my DROID BIONIC using Tapatalk 2

i think you will need to find samsung modem for verzon networks, does verizon have a galaxy note or sgs2?
although your modem firmware probably has voice disabled, may have to find modem manufacturer and try to flash custom firmware.
good luck, wish you the best.

I'm happy enough using GrooveIP for google voice calling. What I'd really like is if we could activate the phone profile in bluetooth (or will that just come with enabling the proper phone part in the 7.7?).
As of now i can use GrooveIP and bluetooth to listen and speak, but it won't let the bluetooth device answer/hang up/transfer address book/show caller ID (on the Verizon LTE 7.7)

Doesn't verizon require some sort of signed telephony to work properly on their network

ph00ny said:
Doesn't verizon require some sort of signed telephony to work properly on their network
Click to expand...
Click to collapse
I got no idea but with the other packs it didn't detect the radio at all. This is keeping the vzw radio partition stock. I like the ideas and really wish the note was verizon as that'd help figure things out.
Sent from my DROID BIONIC using Tapatalk 2

just to confirm does this a sim slot? i thought someone said it did.

chrisrotolo said:
just to confirm does this a sim slot? i thought someone said it did.
Click to expand...
Click to collapse
It does for LTE but cdma service doesn't use sim
Sent from my GT-N7000 using XDA

Seeing as your data account won't have any provisioning for voice usage, even if you DID get a working modem and a modified framework to allow for phone functionality on the device, I doubt that you'd actually be able to made or receive a phone call due to Verizon's limitations at the account and provisioning level anyway.
Point is, it's a CDMA device, and thus your service is attached to the device itself, not the SIM card (except for LTE data). Basically, you can't just provision service to the SIM card alone, and then simply swap it into a different device. So if you got the modem and the framework working, and you called in to Verizon customer service and asked to provision your line for voice, they'll just be like "Umm, no... We never INTENDED for you to use that device as a phone, so no... You want a phone? Buy a phone. You want a tablet? Buy a tablet. You want to do both in one device? We won't allow that because that loses us money that we would be getting by having you either subscribe to two lines, or charge you extra to tether..."
There is a much simpler solution however.
Ditch ANY CDMA carrier in favour of a GSM carrier instead, preferably one that uses the same compatible frequencies adopted by the rest of the world, like AT&T (and MVNO's based off of AT&T's network), and buy the P6800.
The moral of this story is this: if you want the latest devices, with the best features, you're NOT going to find them in the north American market, EVER, at all, period; you're just going to find watered-down, gimped, bloated, and locked-down versions of the international models. You HAVE to import. If you're going to import, you HAVE to use a GSM service provider... That's just the way it is. It sucks, I know, but it is what it is.

I would have to agree, the GSM version would be best. It would be near impossible to make this happen. Of course if I was stick with one, I would try everything I could as well. I'd probably fail miserably and go for something like GrooveIP.

Jade Eyed Wolf said:
Seeing as your data account won't have any provisioning for voice usage, even if you DID get a working modem and a modified framework to allow for phone functionality on the device, I doubt that you'd actually be able to made or receive a phone call due to Verizon's limitations at the account and provisioning level anyway.
Point is, it's a CDMA device, and thus your service is attached to the device itself, not the SIM card (except for LTE data). Basically, you can't just provision service to the SIM card alone, and then simply swap it into a different device. So if you got the modem and the framework working, and you called in to Verizon customer service and asked to provision your line for voice, they'll just be like "Umm, no... We never INTENDED for you to use that device as a phone, so no... You want a phone? Buy a phone. You want a tablet? Buy a tablet. You want to do both in one device? We won't allow that because that loses us money that we would be getting by having you either subscribe to two lines, or charge you extra to tether..."
There is a much simpler solution however.
Ditch ANY CDMA carrier in favour of a GSM carrier instead, preferably one that uses the same compatible frequencies adopted by the rest of the world, like AT&T (and MVNO's based off of AT&T's network), and buy the P6800.
The moral of this story is this: if you want the latest devices, with the best features, you're NOT going to find them in the north American market, EVER, at all, period; you're just going to find watered-down, gimped, bloated, and locked-down versions of the international models. You HAVE to import. If you're going to import, you HAVE to use a GSM service provider... That's just the way it is. It sucks, I know, but it is what it is.
Click to expand...
Click to collapse
I move my SIM between devices all the time and have never needed to call VZ to provision the new device. Voice and data just work.

miiike said:
I move my SIM between devices all the time and have never needed to call VZ to provision the new device. Voice and data just work.
Click to expand...
Click to collapse
I can CONFIRM the following:
I have a VZ tab 7.7 with 5GB data plan and I have a VZ Razr with voice/unlimited data plan.
Both are LTE devices and hence use (micro) SIM cards. In "My Verizon" even the tab has a phone number assigned to it's "line". A call to that number just rings but obviously nothing on the tab.
BUT...
Put the tab sim in the phone and YES it will ring if you call that number! Even TXT in/out works! I assume they will just charge me per txt and per min phone use BUT IT WORKS in a PHONE.
And the kicker is, the unlimited PHONE SIM also works in the TAB! I immediately get LTE data and can surf with the tab. Of course at that point calls and texts to that phone number are "ignored" by the tab's neutered modem.
Lesson learned:
IF there was a way to flash a modem, say for example from the Samsung Galaxy Nexus to the VZ 7.7 TAB, we would have a full supersized phone in our hand. Only downside, no earpiece. So only speakerphone or BT calls I guess.
Anyway, after a little more research I also found this very interesting article:
http://www.phonenews.com/verizon-affirms-unlimited-smartphone-sim-card-usage-in-hotspots-tablets-lte-ipad-20053/
Hope this helps bring a little light into the messy CDMA/LTE darkness

I have swapped my Galaxy Nexus SIM in my VZW LTE 7.7 numerous times. It works. I'd love to have voice on the VZW LTE 7.7, then I could possibly do it all on my tab. I'm no developer tho ;p

Anyone gotten tap and pay to work on CM 11?

im on CM11 bootloader unlocked, gsm unlocked razr M on T-mobile with the latest 3/13/14 update of the wallet app.
CM 11 kitkat 4.4.2 has HCE and tap and pay NFC should be working without a problem, yet I have never gotten it to work and have tried it at multiple locations.
Is there something im missing?
EDIT: PROBLEM AND SOLUTION
okay after EXTENSIVE research, i have finally found our problem. so basically our phones have the capability for TnP to work. The only issue is drivers and support.
As of now TnP only works with Broadcom NFC chipsets and nothing else, so even if your phone has NFC, TnP will not work unless it is a Broadcom controller chipset. Our razr phones have NXP NFC chipsets which as of right now are not supported by the google wallet app (google's fault) so Host Card Emulation (HCE) support in kitkat is missing from AOSP roms
this has absolutely nothing to do with the secure element anymore at all in 4.4.2. Google went the HCE specifically so the likes of verizon couldn't block the TnP function.
TL;DR
We will get it, it is only a matter of time. either direct from wallet app support for our NXP chipset or from our wonderful dev community. Currently the code for NXP's NFC chips is empty for the host card emulation to work.
some active work being done if you can help the movement (sorry I can't post links yet)
http://forum.xda-developers.com/showthread.php?t=2573842

dman9691 said:
im on CM11 bootloader unlocked, gsm unlocked razr M on T-mobile with the latest 3/13/14 update of the wallet app.
CM 11 kitkat 4.4.2 has HCE and tap and pay NFC should be working without a problem, yet I have never gotten it to work and have tried it at multiple locations.
Is there something im missing?
Click to expand...
Click to collapse
Yeah, there's something missing on the M and HD that won't allow TnP to work. I can't remember what exactly it is, but there was a pretty good discussion about it in the HD forum.

What you're thinking of is a "secure element". This was a thing built into older phones to enable stuff like NFC payments. Our phone does not have one built in to it.
Tmobile phones (and probably the others) that support ISIS don't use one built into the phone, but have a secure element built into the sim card (you need a new sim, along with methods of accessing it which CM probably doesn't have).
Kit Kat has a software-only version of the "secure element" and should not require anything built into the phone or the sim card. In theory you just have to convince google wallet to use the software one. That said, there's still probably some work to do to convince google wallet to do its thing. I think it still only enables tap to pay for some phones. What OP is asking for should be possible.

ezdi said:
What you're thinking of is a "secure element". This was a thing built into older phones to enable stuff like NFC payments. Our phone does not have one built in to it.
Tmobile phones (and probably the others) that support ISIS don't use one built into the phone, but have a secure element built into the sim card (you need a new sim, along with methods of accessing it which CM probably doesn't have).
Kit Kat has a software-only version of the "secure element" and should not require anything built into the phone or the sim card. In theory you just have to convince google wallet to use the software one. That said, there's still probably some work to do to convince google wallet to do its thing. I think it still only enables tap to pay for some phones. What OP is asking for should be possible.
Click to expand...
Click to collapse
That's what I was looking for, thanks.

CM11 NXP chip NFC HCE support
RikRong said:
That's what I was looking for, thanks.
Click to expand...
Click to collapse
okay after EXTENSIVE research, i have finally found our problem. so basically our phones have the capability for TnP to work. The only issue is drivers and support.
As of now TnP only works with Broadcom NFC chipsets and nothing else, so even if your phone has NFC, TnP will not work unless it is a Broadcom controller chipset. Our razr phones have NXP NFC chipsets which as of right now are not supported by the google wallet app (google's fault) so Host Card Emulation (HCE) support in kitkat is missing from AOSP roms
this has absolutely nothing to do with the secure element anymore at all in 4.4.2. Google went the HCE specifically so the likes of verizon couldn't block the TnP function.
TL;DR
We will get it, it is only a matter of time. either direct from wallet app support for our NXP chipset or from our wonderful dev community. Currently the code for NXP's NFC chips is empty for the host card emulation to work.
some active work being done if you can help the movement (sorry I can't post links yet)
http://forum.xda-developers.com/showthread.php?t=2573842

Question about cross-carrier compatibility

Okay, I'll start with a little background. I'm a Verizon Wireless employee, and the store's resident Android nerd. That said, I'm stumped on something.
With the recent government ruling about sim-unlocking phones, we've seen an influx of devices from other carriers. Honestly, we've not been trained on how to handle these. Popping active sims into the phone typically activates them just fine, but we've been running into issues with SMS pretty frequently. Also, having AT&T firmware on a Verizon device is weird too, and can result in some odd behavior with baked in features.
With regard to the SMS issues, my immediate first thought was to edit the APN settings. Those are greyed out on a lot of devices I've seen though. So now I'm thinking something needs to change in the firmware. We do not have the ability to flash firmware* though.
We recently had a customer come in and activate 12 sim-unlocked US Cellular GS5s.They report that everything is working except SMS. What do I do?
*We do have an unapproved laptop laying around, and I do have Kies installed on it. I've never used it though, and nobody in the store wants to be liable for bricking a phone. With the right customer, I'd be willing to try it through Kies if that's something it is capable of. But as a large store, that's not a viable solution for most customers.

YamiYaiba said:
Okay, I'll start with a little background. I'm a Verizon Wireless employee, and the store's resident Android nerd. That said, I'm stumped on something.
With the recent government ruling about sim-unlocking phones, we've seen an influx of devices from other carriers. Honestly, we've not been trained on how to handle these. Popping active sims into the phone typically activates them just fine, but we've been running into issues with SMS pretty frequently. Also, having AT&T firmware on a Verizon device is weird too, and can result in some odd behavior with baked in features.
With regard to the SMS issues, my immediate first thought was to edit the APN settings. Those are greyed out on a lot of devices I've seen though. So now I'm thinking something needs to change in the firmware. We do not have the ability to flash firmware* though.
We recently had a customer come in and activate 12 sim-unlocked US Cellular GS5s.They report that everything is working except SMS. What do I do?
*We do have an unapproved laptop laying around, and I do have Kies installed on it. I've never used it though, and nobody in the store wants to be liable for bricking a phone. With the right customer, I'd be willing to try it through Kies if that's something it is capable of. But as a large store, that's not a viable solution for most customers.
Click to expand...
Click to collapse
I would defer to my boss or VZ corporate lest I get fired for doing the "wrong thing", which I learned on an internet forum!

UNBELIEVABLE
Sent from my SM-G900V using XDA Free mobile app

YamiYaiba said:
Okay, I'll start with a little background. I'm a Verizon Wireless employee, and the store's resident Android nerd. That said, I'm stumped on something.
With the recent government ruling about sim-unlocking phones, we've seen an influx of devices from other carriers. Honestly, we've not been trained on how to handle these. Popping active sims into the phone typically activates them just fine, but we've been running into issues with SMS pretty frequently. Also, having AT&T firmware on a Verizon device is weird too, and can result in some odd behavior with baked in features.
With regard to the SMS issues, my immediate first thought was to edit the APN settings. Those are greyed out on a lot of devices I've seen though. So now I'm thinking something needs to change in the firmware. We do not have the ability to flash firmware* though.
We recently had a customer come in and activate 12 sim-unlocked US Cellular GS5s.They report that everything is working except SMS. What do I do?
*We do have an unapproved laptop laying around, and I do have Kies installed on it. I've never used it though, and nobody in the store wants to be liable for bricking a phone. With the right customer, I'd be willing to try it through Kies if that's something it is capable of. But as a large store, that's not a viable solution for most customers.
Click to expand...
Click to collapse
No offense, I'm actually trying to do the opposite and move my Verizon S5 and S3 to T-Mobile. (Verizon phone reps, through six separate phone calls, gave me six different stories of how to unlock my phone. I'm experiencing hiccups as I go - T-Mobile gave me some misinformation as well.)
They were able to change a lot of settings for their network, there are still SMS issues and other random odd issues. Maybe that's the nature of it?

I haven't looked into this in over a year, but I was under the impression that Verizon operates on an IMEI white list, i.e. ONLY Verizon branded phones are allowed on the network. When a user attempts to activate a phone on the network, it's IMEI is checked against the list of IMEIs for every phone Verizon has sold. If it's IMEI is not on that list because it's a non-carrier branded phone or it's another carrier's version of the phone it will not be allowed on the network regardless of hardware compatibility.
From what I recall, this was also the reason that Nexus 7 LTE buyers were screwed by Verizon. Verizon was advertised as supporting the tablet because legally they had to due to the open access provision they agreed to when they purchased their LTE spectrum. Up to that point Verizon had operated with a white list as I described above. They were able to get away with this despite the open access provision because they run voice and text over the older 2G and 3G networks on which they have not agreed to open access. When the tablet came out, for months Verizon had no system in place to activate it because the IMEIs were not on the white list. Users were able to successfully connect to the network with a SIM activated in another tablet proving that it was not a hardware issue.
Has this changed in the last year? If so that great news!
---------- Post added at 12:25 PM ---------- Previous post was at 11:58 AM ----------
I just Googled it, and based on information from November when the Nexus 6 came out, Verizon still operates on a white list, but it's only for activating NEW LINES. Verizon will not allow you to activate a new line with a non-Verizon branded phone, however, once the SIM has been activated, if it is placed in a non-white listed phone, that phone will be allowed on the network.
Some people suggest that you can take the IMEI of a floor model at the Verizon store and enter that when you order a SIM CARD, and that will allow for activation. I cannot personally verify this as I'm not a Verizon customer, and I'm not sure if the SIM activation process requires an actual phone with a white listed IMEI.
---------- Post added at 12:51 PM ---------- Previous post was at 12:25 PM ----------
Also OP, have you verified that the handsets with SMS problems support all of Verizon's 2G and 3G network frequencies? From what I recall, Verizon still runs voice and SMS over its legacy 2G/3G networks. I'm not sure if they've implemented Volte yet, but it's likely that older handsets and even some newer ones don't support it, especially if they don't have a Verizon ROM. It's possible that a handset could support only Verizon's LTE frequencies or support everything except it's 3G frequencies for example. If it supports only the LTE frequencies, data could work while voice and SMS don't. If voice and SMS are run over different frequencies it's possible that only one of the two will work.
Information on supported frequencies can be tough to find for phones sold in the US. The information is readily available for the same phones sold anywhere else in the world. The most plausible explanation is that this is because the US carriers insist upon it. They've been forced to start unlocking phones that in the past they've been able to permanently lock to their own networks for domestic use. To combat the emergence of a free marketplace where customers are free to move to a carrier offering a better deal, the carriers have started specifying that their carrier branded versions of the phone be shipped with firmware (possibly also hardware variations) that does not support the frequencies of other US carriers. That way, the phone is "unlocked," but it still won't work on other US networks, so they've managed to sidestep the legislation and continue screwing over consumers.
If the supported frequencies aren't listed on the manufacturer website, you can find them in FCC testing documents.
If customers do have a problem where voice or SMS doesn't work because the frequency isn't supported, they could use a Google voice number for calls and SMS over the data network using the Hangouts app. It works great for me. Your employer definitely would not approve of this suggestion though, since it compromises the way they've artificially limited their technology to force consumers to pay more. All calls and texts to/from a Google voice number are totally free when you're on a Wifi network, and the number is device agnostic, so there's no barrier at all to switching phones or carriers. Verizon wants to use your phone number to make switching as inconvenient as possible, so they don't want you using a cloud based phone number.

Taking VZW S7 to VZW-based MVNO

Okay - I have a question on whether I should even bother to attempt a migrate. I have an ex-VZW Galaxy Nexus on Tracfone (dual-carrier MVNO - currently on the VZW side). I also have a VZW Galaxy S7 inbound that is being replaced by the current owner (who is having issues with the phone itself) - the owner wants to GIVE me the phone in question (the frustration level is THAT high). I have worked on the phone (and used it as basically a tablet - I did not use the phone AS a phone) and am thus familiar with everything including factory-resets; however, how would I migrate it?
1. Issue #1 - it takes a different SIM style (from what I suspect) from the GNex I'd be leaving; if it didn't, it would be a straight migration that I could do.
2. Preferably, I'd like to be able to stick with VZW firmware (it's what I'm familiar with on the phone in question).
3. As far as SAMSUNG/Android Pay on an S7 (or any other phone), if you rooted the phone, it normally will NOT pass SafetyNet (this was an issue I faced with the GNex; therefore, it's not unique to the S7). You need a method to hide root - if done properly, that will fix the issue. Still, not a new issue (and it's one I know how to deal with).

PGHammer said:
Okay - I have a question on whether I should even bother to attempt a migrate. I have an ex-VZW Galaxy Nexus on Tracfone (dual-carrier MVNO - currently on the VZW side). I also have a VZW Galaxy S7 inbound that is being replaced by the current owner (who is having issues with the phone itself) - the owner wants to GIVE me the phone in question (the frustration level is THAT high). I have worked on the phone (and used it as basically a tablet - I did not use the phone AS a phone) and am thus familiar with everything including factory-resets; however, how would I migrate it?
1. Issue #1 - it takes a different SIM style (from what I suspect) from the GNex I'd be leaving; if it didn't, it would be a straight migration that I could do.
2. Preferably, I'd like to be able to stick with VZW firmware (it's what I'm familiar with on the phone in question).
3. As far as SAMSUNG/Android Pay on an S7 (or any other phone), if you rooted the phone, it normally will NOT pass SafetyNet (this was an issue I faced with the GNex; therefore, it's not unique to the S7). You need a method to hide root - if done properly, that will fix the issue. Still, not a new issue (and it's one I know how to deal with).
Click to expand...
Click to collapse
Number 3 is a no go, only 1 root option and it will not pass safetynet. The first 2 are fixable with 1. being get ST to mail you a sim and 2. Vzw firmware works fine on vzw ST.

gunz.jones said:
Number 3 is a no go, only 1 root option and it will not pass safetynet. The first 2 are fixable with 1. being get ST to mail you a sim and 2. Vzw firmware works fine on vzw ST.
Click to expand...
Click to collapse
That is what I was afraid of; actually, I can get Tracfone to send me a nano-SIM (they are my MVNO of record) or purchase one locally via any of their retail POPs (Dollar General, Wal-Mart, or Target - with DG being the closest and thus the easiest), since I'd be porting my existing number on my existing provider). Right now, I am updating the newly-arrived S7 with the Nougat firmware of the VZW sort (the original owner stayed with MM). What IS the one method that works for rooting? I'm used to either SuperSU and Magisk (Magisk was my SafetyNet compatible rooting solution - however, with MagiskManager booted out of the PlayStore, I need an alternative). I can set up everything else in the meanwhile.

PGHammer said:
That is what I was afraid of; actually, I can get Tracfone to send me a nano-SIM (they are my MVNO of record) or purchase one locally via any of their retail POPs (Dollar General, Wal-Mart, or Target - with DG being the closest and thus the easiest), since I'd be porting my existing number on my existing provider). Right now, I am updating the newly-arrived S7 with the Nougat firmware of the VZW sort (the original owner stayed with MM). What IS the one method that works for rooting? I'm used to either SuperSU and Magisk (Magisk was my SafetyNet compatible rooting solution - however, with MagiskManager booted out of the PlayStore, I need an alternative). I can set up everything else in the meanwhile.
Click to expand...
Click to collapse
https://forum.xda-developers.com/tm...eres-how-rooted-nougat-s7-edge-g935t-t3567502

Thanx for this
gunz.jones said:
https://forum.xda-developers.com/tm...eres-how-rooted-nougat-s7-edge-g935t-t3567502
Click to expand...
Click to collapse
Thanx for this; I'll check that out when I'm ready.
I have some other news on my testing; while I would have preferred to stick with Verizon-branded firmware, it commits two major sins - it lacks the latest security updates, and it's "cornflakey" in SIMless/tablet mode - however, there is an alternative firmware for the G930V (despite it being originally for its unlocked cousin, the G930U, it will install on the V as well - even in VZW trim; my own V is the gold exclusive-to-VZW model, and, atop that, this particular U firmware is for Tracfone's version of the U - hence absolutely none of the VZW shovelware that folks complain about). It is the May 16th (this year) U firmware for the G930U for the Tracfone S7 (yes - there is such a creature); it will also install on the VZW S7 (which means it will also install on the V from Big Red) via ODIN (use the four-file method - BL, AP, CP, and HOME_CSC) the file name is SM-G930U_1_20170516105039_fspus9jwu3_fac.zip, and is present on both SamMobile and updato.com (I used updato for speedier downloads). There are two good things about Tracfone's alternative firmware - it is pretty much designed for SIMless/tablet operations; while it has gotten easier to pick up SIM kits (you can grab them at any Wal-Mart or Dollar General anywhere in the country - in addition to having them mailed/shipped via Tracfone.com or StraightTalk.com), why should your new(er) phone be a paperweight in the meantime? Second, it is *vanilla* as firmware gets - and I don't mean French Vanilla, either - it reminds me of iOS or AOSP (specifically Unlegacy-Android); it may be burdened with TouchWiz; however, that is, literally, the only real ding against it. (And, from personal experience, the Snapdragon 820 bakes TouchWiz to a turn - more so on N than MM - and isn't N supposed to be heavier compared to MM?)

PGHammer said:
Thanx for this; I'll check that out when I'm ready.
I have some other news on my testing; while I would have preferred to stick with Verizon-branded firmware, it commits two major sins - it lacks the latest security updates, and it's "cornflakey" in SIMless/tablet mode - however, there is an alternative firmware for the G930V (despite it being originally for its unlocked cousin, the G930U, it will install on the V as well - even in VZW trim; my own V is the gold exclusive-to-VZW model, and, atop that, this particular U firmware is for Tracfone's version of the U - hence absolutely none of the VZW shovelware that folks complain about). It is the May 16th (this year) U firmware for the G930U for the Tracfone S7 (yes - there is such a creature); it will also install on the VZW S7 (which means it will also install on the V from Big Red) via ODIN (use the four-file method - BL, AP, CP, and HOME_CSC) the file name is SM-G930U_1_20170516105039_fspus9jwu3_fac.zip, and is present on both SamMobile and updato.com (I used updato for speedier downloads). There are two good things about Tracfone's alternative firmware - it is pretty much designed for SIMless/tablet operations; while it has gotten easier to pick up SIM kits (you can grab them at any Wal-Mart or Dollar General anywhere in the country - in addition to having them mailed/shipped via Tracfone.com or StraightTalk.com), why should your new(er) phone be a paperweight in the meantime? Second, it is *vanilla* as firmware gets - and I don't mean French Vanilla, either - it reminds me of iOS or AOSP (specifically Unlegacy-Android); it may be burdened with TouchWiz; however, that is, literally, the only real ding against it. (And, from personal experience, the Snapdragon 820 bakes TouchWiz to a turn - more so on N than MM - and isn't N supposed to be heavier compared to MM?)
Click to expand...
Click to collapse
The firm from any u or v/vl would work on the vzw and st/tf phones. I have a vl running v firmware. The v has updates to June security as far as I'm aware, but they ruin gps spoofing. Carrier fw gets updated more often than u as well from reading the forums

gunz.jones said:
The firm from any u or v/vl would work on the vzw and st/tf phones. I have a vl running v firmware. The v has updates to June security as far as I'm aware, but they ruin gps spoofing. Carrier fw gets updated more often than u as well from reading the forums
Click to expand...
Click to collapse
And why would you need GPS spoofage? (Yes - I'm serious.) The big reason for the hate on VZW firmware has to do with all the shovelware - I hate it because it is not as friendly to SIMless operation as Tracfone's more vanilla U-ware; some of VZW's shovelware I can actually use.

PGHammer said:
And why would you need GPS spoofage? (Yes - I'm serious.) The big reason for the hate on VZW firmware has to do with all the shovelware - I hate it because it is not as friendly to SIMless operation as Tracfone's more vanilla U-ware; some of VZW's shovelware I can actually use.
Click to expand...
Click to collapse
I use it for pogo and that's about it.

Advanced Calling Features on MVNOs
gunz.jones said:
I use it for pogo and that's about it.
Click to expand...
Click to collapse
Are you referring to EA's mobile-gaming service? I don't even use it for that.
I have a question for anyone that has a VZW-based MVNO (Tracfone, Straight Talk, etc.) - have you ever tried to use Wi-Fi calling? (This is actually a switch in the S7 settings menu which lets you use it when mobile data is unavailable - it's below the Advanced Calling switch.)

PGHammer said:
Are you referring to EA's mobile-gaming service? I don't even use it for that.
I have a question for anyone that has a VZW-based MVNO (Tracfone, Straight Talk, etc.) - have you ever tried to use Wi-Fi calling? (This is actually a switch in the S7 settings menu which lets you use it when mobile data is unavailable - it's below the Advanced Calling switch.)
Click to expand...
Click to collapse
Pokemon go. WiFi calling doesn't work on vzw mvno.

gunz.jones said:
Pokemon go. WiFi calling doesn't work on vzw mvno.
Click to expand...
Click to collapse
I wouldn't think so - such an advanced feature is what separates carriers from MVNOs; therefore, I certainly understand why a carrier would want to keep such a feature to itself.

PGHammer said:
I wouldn't think so - such an advanced feature is what separates carriers from MVNOs; therefore, I certainly understand why a carrier would want to keep such a feature to itself.
Click to expand...
Click to collapse
There is a possibility of it working with an att or tmo sim. I had it working on an st att sim and tmo note 4 as well as volte. Oh, volte also doesn't work on a vzw mvno.

gunz.jones said:
There is a possibility of it working with an att or tmo sim. I had it working on an st att sim and tmo note 4 as well as volte. Oh, volte also doesn't work on a vzw mvno.
Click to expand...
Click to collapse
Advanced feature, remember? I get that. Somehow, I got SIMless operations straightened out (V firmware). I'm right now waiting on two things - the latest security update (have any of you on a VZW MVNO but VZW firmware gotten it yet?) and to grab a Tracfone SIM (I'm going local retail for that - likely Dollar General, as they are the closest retailer that carries them).

Play Protect certification

after getting the update from one plus for 6T to android 10.3.0. the play store pops up say "device is not certified" now I cannot use Google Pay. Is there any way to fix this
My phone is a T-Mobile to International Conversion no root or bootloader is lock

From my understanding I'm in the same boat, the only fix I see in other forum's is rooting, or waiting for TMobile to put out a10. Which will probably take along time

This has been answered many times.
To be certified by Google, the ROM digital fingerprint must be communicated to Google by the manufacturer.
As you have modified your device by installing an OOS designed for another phone (yes technically global OP6t is a different phone compared to TMob one), there is a mismatch in parameters transmitted to Google leading to a non certified device.
The only solution is to root and use a Magisk module to modify your phone digital fingerprint towards a recognized one. (Magiskhide props config)
Complaints are to be addressed to TMobile.

Is this still an issue? I'm rooted and use Magisk to certify but I can't play games like Mario Tour and I'm considering going back to stock.

Striatum_bdr said:
This has been answered many times.
To be certified by Google, the ROM digital fingerprint must be communicated to Google by the manufacturer.
As you have modified your device by installing an OOS designed for another phone (yes technically global OP6t is a different phone compared to TMob one), there is a mismatch in parameters transmitted to Google leading to a non certified device.
The only solution is to root and use a Magisk module to modify your phone digital fingerprint towards a recognized one. (Magiskhide props config)
Complaints are to be addressed to TMobile.
Click to expand...
Click to collapse
I just wanted to say thank you for sharing this.
I know these types of things are shared in many places, but unfortunately its hard to figure out where to look sometimes. So thanks for being redundant it was helpful!