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
Related
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
I know there are several other threads that deal with the titular separate topics...I even started one myself before the phone was released. However, I wanted to make this thread to pool all the relevant questions about the general topic of NFC on this phone under one roof, as it were, since almost none of the following questions have been answered very thoroughly.
1) What is the status of ISIS compatibility on this phone? Version 1.09, I can personally confirm, works fine with the Verizon variant, but the app has recently been marked as incompatible on Google Play. The ISIS webpage only lists the AT&T variant of the Note 3 as compatible with the service, which seems inconsistent. Verizon also doesn't seem to have updated their branded version of ISIS to 1.9 alongside T-Mobile and AT&T, so it's extremely confusing, and I want to know whether the app will continue to be supported on the Verizon Note 3 or not?
2) What is the status of Google Wallet tap-to-pay? It's fairly obvious that the normal, non-NFC version of Google Wallet works properly, but I haven't heard anything definitive on the status of bringing the tap-to-pay version to the Verizon variant. One thread suggested that it may be more difficult to do than simply changing the build.prop to the Sprint version and adding the required SE authorization keys, so what's the status?
3) Related to question 2: Does the Verizon variant of the Note 3 even include an embedded secure element? It's fairly easy to acquire an SE-enabled SIM card from Verizon, but one thread awhile back suggested that the phone may not even include an embedded SE, and also suggested that that was what was holding up (or, rather, making impossible) this phone's Google Wallet port. Can anyone with authority on this phone's hardware answer this question?
Again, sorry if this seems redundant--these are just loose ends, and I thought it would be useful to bring them into one thread for coherence.
Reading up on some of the other threads the non Sprint variants do not (by default) have the required libraries flashed (Google wallet fix for SGS3 US variants AT&T, T-MOBILE, US Cellular, VERIZON, etc), although since the hardware is the same, flashing the required libraries (properly) should not bork the phone. From this question 3 could be answered as "There should be a hardware based secure element in the phone".
For question 1) it is quite possible that ISIS may be on the downslope. From September 20, 2013, PC Mag was reporting that Capital One was dropping supporting for ISIS Capital One Drops Support for Isis Mobile Wallet with a zdnet report on a CTIA panel discussion Mobile payments: Are we there yet? CTIA panel talks up Isis.
For question 2) it's hard to tell at the current moment. The reason being is obviously about the physical secure element required. With the latest version of android (4.4 'KitKat'), Google collaborated with Doug Yeager and Ted Fifelski (of SimplyTapp) to bring Host Card Emulation to the official builds of Android (Google gets around the carriers with Host Card Emulation for NFC payments).
Back in 2012 SimplyTapp proposes secure elements in the cloud/ both of these gentlemen approached the problem of the inaccessible secure element by 'using the cloud' (or more technically accurate, an active data connection) to emulate the secure element. The only caveat was because the official builds of android didn't include the libraries required for HCE (ie ISOPcdA, ISOPcdB, etc) that was built from starch via Doug Yeager (GitHub Repo for the NFC libaries) could only be included in forked, unofficial builds of Android, most notably the CyanogenMod Roms (Emulating a PKI smart card with CyanogenMod 9.1).
With Google taking the cloud approach it is possible that Wallet may eventually work on all NFC phones running 4.4 (and hopefully on unofficial builds including the CyanogenMod Roms.
Hope this helps
Joe
Does the Note 2 google wallet hack to enable Tap to Pay work on the N3?
deputydog95 said:
Does the Note 2 google wallet hack to enable Tap to Pay work on the N3?
Click to expand...
Click to collapse
No, unfortunately. If you have a Sprint Note 3 then it already works, and if you have an AT&T/Verizon/T-Mobile model then Host Card Emulation isn't supported at all by the NFC chip. Kind of seriously aggravating that they went with a different NFC chip in those models, if you ask me. I really love the Note 3, but I absolutely will not be getting a Note 4 unless HCE is supported by the hardware AND the software; if it's available on some carriers, but not on the AT&T models, then I'll almost certainly change carriers.
Does the tmobile version of the G2 have NFC? I cannot seem to get it to read any tag or connect to any NFC devices. The NFC is turned on in the settings. Has anyone used NFC successfully on the tmobile version?
Yes I have.
I have used it to send/receive pictures (G2/S4). I have also used it a few times at a vending machine getting a coke for 30 coke reward points through ISIS.
Works fine here bud.
Sent from my LG-D801
I'm not using a TMobile G2, but iirc there are different NFC standards and therefore different NFC tags - make sure you are using the correct tags!
With my D802 I have no problem at all to use NFC - created the tags with Trigger > works great!
Hi,
I've read that KitKat brings Host Card Emulation. Do I understand it rignt that I can record any wireless card into my phone and later use my phone exactly as I would use that card? (credit card, tesco benefit card, door card etc.?)
I know I can connect google wallet with US credit card and pay with it, but this is for US only (I'm from Europe) and payments go through wallet account etc.
I would like to use it just as card emulator. Can someone please tell me, how to achieve this?
Is google wallet app necessary (because I struggle a little with country check).
I've tried to search but I couldn't find any usable informations, only discussions that HCE is enabled only for Broadcom NFC chips (which N4 has, so I presume it sould work on N4)
Thanks for any usable info
http://www.xda-developers.com/android/google-wallet-updated-with-kitkat-nfc-host-card-emulation/
I think it doesnt work without Google Wallet but I could be wrong.
We have a NFC hack section on xda..
Sent from my Nexus 4, while driving in my Evo9.
Current state: VZW LG V20 VS995, 7.0, unrooted
So, I've used Samsung smartphones for years and one of my must-haves is an IR blaster. I moved from a Note 4 to the LG V20, and all is good, except for one thing.
I've used Beep n Go for digital storage of loyalty and membership cards. As you may know, that app uses a beaming service where information from the bar code is beamed to the handheld or bed scanner to transmit the information.
For POS scanners where they're using imaging technology, Stocard works fine. But my gym apparently is using the older laser scanner (red line moving across the bar code), so none of the apps will work.
I was able to get Beep n Go onto the V20, but the Mobeam beaming service app that beams the card info can't be installed. Since the V20 has the hardware (IR blaster and proximity sensor), I thought that this would work, but apparently not. I tried sideloading the apk for Mobeam, but the install fails because there's already a beaming service installed.
I'd rather not root (I use the V20 to access work email, and non-rooted devices are authenticated), but I guess I could root, do my business, then unroot if that's possible.
Has anyone else ever run into this?
Thanks!!
AdmiralMVP said:
Current state: VZW LG V20 VS995, 7.0, unrooted
So, I've used Samsung smartphones for years and one of my must-haves is an IR blaster. I moved from a Note 4 to the LG V20, and all is good, except for one thing.
I've used Beep n Go for digital storage of loyalty and membership cards. As you may know, that app uses a beaming service where information from the bar code is beamed to the handheld or bed scanner to transmit the information.
For POS scanners where they're using imaging technology, Stocard works fine. But my gym apparently is using the older laser scanner (red line moving across the bar code), so none of the apps will work.
I was able to get Beep n Go onto the V20, but the Mobeam beaming service app that beams the card info can't be installed. Since the V20 has the hardware (IR blaster and proximity sensor), I thought that this would work, but apparently not. I tried sideloading the apk for Mobeam, but the install fails because there's already a beaming service installed.
I'd rather not root (I use the V20 to access work email, and non-rooted devices are authenticated), but I guess I could root, do my business, then unroot if that's possible.
Has anyone else ever run into this?
Thanks!!
Click to expand...
Click to collapse
Doesnt magisk hide the root making the authentication pass as true? I mean, i rooted my lg v20 h918 and im currently using a custom rom with magisk and im able to use android pay (which requires authentication) thanks to magisk.