That is what I am explaining. The HCE framework doesn't yet support the NFC controller in the Note 3. It uses NXP PN547. Google needs to update the framework to include that controller.
Why the 4.4.2 TouchWiz update doesn't have Tap to Pay.
- Thread starter gakio12
- Start date
That is what I am explaining. The HCE framework doesn't yet support the NFC controller in the Note 3. It uses NXP PN547. Google needs to update the framework to include that controller.
Just checked the /dev folder and the device is definitely PN547... not sure where you got your info from, but its wrong.
Thanks for verifying this once and for all, my bad. I got it from Wikipedia: http://en.wikipedia.org/wiki/List_of_NFC-enabled_mobile_devices Seems the article needs updating.
Last edited:
Supposedly I read our NFC chip will be supported in 4.4.3
Sent from my Note 3 on 4.4.2
Attachments
I'm not updating to Kit Kat yet. Far too many bugs for my comfort.
Sent from my SM-N900T using Tapatalk
Sent from my SM-N900T using Tapatalk
What bugs? Lol I've been on one rom ever since I upgraded and been beast
Lol yes me too.. hate to say it but this is why ios makes us look like amateurs at times... I expect tap to pay to work without issue :/
toastido
Senior Member
- Oct 23, 2013
- 1,276
- 1,233
It's completely different from that of Google wallet. Not that I'm a apple fan boy but some things do upset me when I'm trying to use a native Google feature that seems to be non existent currently on my firmware. I tried when it was isis wallet but it wasn't my type of deal.
toastido
Senior Member
- Oct 23, 2013
- 1,276
- 1,233
Well, it's still the same thing, just different name... Probably due to ISIS in the middle east... *snicker*
Anyway, works fine for me, using my AMEX and linked other cards to the virtual AMEX they give you.
I doubt it'll work perfectly. Google wallet failed just like all the others. Ios, not sure what was done different to be considered "successful" but there are a few hurdles it'll have to jump in order to be successful.
I was so pleased even with isis but yet to see a way to use my visa. How is it apple is able to allow it's users to so?
I was so pleased even with isis but yet to see a way to use my visa. How is it apple is able to allow it's users to so?
With ISIS or whatever it's named now, you can use most card types by linking them to the AMEX Serve card. It ends up working like paypal, if you have money in the pre-pay Serve card, it uses that. If not, it will load some in from another source. I used a Visa credit card for that and it worked fine. The auto load is optional and defaults off I believe. So if you would rather have it decline charges when you don't have money there, you can do that.
It's not as nice as connecting to the card directly, but all the players are too busy trying to make their way into the standard to work together. I'm surprised Apple got the card companies on board. It will be interesting to see.
All that said, I'm still not convinced it's a problem that needs solving. It's kinda cool, but since I generally have to carry ID and other payment methods for places that don't support NFC it's more of a curiosity than anything else for me. A local coffee shop had problems with ISIS occasionally and stopped supporting it because people would come in with just their phones. They are using some QR code based setup now that I haven't bothered to set up yet.
It's not as nice as connecting to the card directly, but all the players are too busy trying to make their way into the standard to work together. I'm surprised Apple got the card companies on board. It will be interesting to see.
All that said, I'm still not convinced it's a problem that needs solving. It's kinda cool, but since I generally have to carry ID and other payment methods for places that don't support NFC it's more of a curiosity than anything else for me. A local coffee shop had problems with ISIS occasionally and stopped supporting it because people would come in with just their phones. They are using some QR code based setup now that I haven't bothered to set up yet.
Similar threads
- Locked
- Poll
Top Liked Posts
-
There are no posts matching your filters.
-
4
No it does not. The Sprint variant uses a different NFC controller (NXP P65) that has both a built-in secure element and implements the FeliCa card emulation standard.
This is why Google Wallet works on it on Android 4.3 and on Android 4.4 (using the old SE-based method, not HCE) but not on any of the other variants.
I helped discover this difference. More info here: http://xdaforums.com/showthread.php?t=2476093
OP is correct - we need to wait for the T-Mobile variant's NFC controller to be supported by KitKat's HCE framework.2A lot of people are thinking that T-mobile is blocking Tap to Pay on the Note 3 with KitKat. However, it is reported that Tap to Pay works on the T-mobile S4.
T-mobile isn't blocking Tap to Pay; Google simply hasn't integrated the PN-547 chip into Tap to Pay yet. This is why AOSP builds still don't have Tap to Pay. NXP, within the last week, just integrated the PN-547 chip into 4.4, which means it will probably show up in Android 4.4.3.1
No idea, that's up to Samsung. The US variants have the NXP P544 controller, while the international variants have the Broadcom BCM20793 controller (same as used in all the Nexus devices), which is the only chip that KitKat's HCE framework currently supports - this is why phones with the Broadcom chip have Tap-and-Pay while those with the NXP chips don't yet. We need to wait for an update from Google that enables support for the P544 chip in the HCE framework.
The Sprint variant is using the NXP P65, which is a P544 combined with a secure element, which is why Wallet works on it (using the old method, not HCE).1
That is what I am explaining. The HCE framework doesn't yet support the NFC controller in the Note 3. It uses NXP PN547. Google needs to update the framework to include that controller.
