Welcome to XDA

Search to go directly to your device's forum

Register an account

Unlock full posting privileges

Ask a question

No registration required
Post Reply

Why the 4.4.2 TouchWiz update doesn't have Tap to Pay.

OP gakio12

6th March 2014, 01:57 AM   |  #1  
gakio12's Avatar
OP Senior Member
Thanks Meter: 103
 
178 posts
Join Date:Joined: Dec 2011
Donate to Me
A 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.
The Following 2 Users Say Thank You to gakio12 For This Useful Post: [ View ]
6th March 2014, 03:13 AM   |  #2  
0ri0n's Avatar
Senior Member
Attleboro, MA
Thanks Meter: 28
 
112 posts
Join Date:Joined: Feb 2007
More
Quote:
Originally Posted by gakio12

A 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.

Doesnt the sprint note 3 have the same nfc chip?
6th March 2014, 03:29 AM   |  #3  
gakio12's Avatar
OP Senior Member
Thanks Meter: 103
 
178 posts
Join Date:Joined: Dec 2011
Donate to Me
Quote:
Originally Posted by 0ri0n

Doesnt the sprint note 3 have the same nfc chip?

I assume yes; does the sprint note 3 tap to pay function on KitKat?
6th March 2014, 03:44 AM   |  #4  
0ri0n's Avatar
Senior Member
Attleboro, MA
Thanks Meter: 28
 
112 posts
Join Date:Joined: Feb 2007
More
Yup... so there goes that theory.
6th March 2014, 03:44 AM   |  #5  
Matrixk101's Avatar
Senior Member
Flag Tolleson
Thanks Meter: 50
 
155 posts
Join Date:Joined: May 2011
More
I was told in store that u need to update to a differnt kinda sim card for tap and pay I think its called a isis sim card l.

Sent from my SM-N900T using xda app-developers app
6th March 2014, 03:51 AM   |  #6  
parusia's Avatar
Senior Member
Flag Houston
Thanks Meter: 306
 
783 posts
Join Date:Joined: Nov 2010
More
Quote:
Originally Posted by Matrixk101

I was told in store that u need to update to a differnt kinda sim card for tap and pay I think its called a isis sim card l.

Sent from my SM-N900T using xda app-developers app

That is to use Isis method, what the majority of people want is Google wallet method. What happen with Isis is that works only with certain Credit Cards and not with all of them, I think is only with Wells Fargo, certain chase cards, and Amex.

Sent from my SM-T210R using XDA Premium 4 mobile app
6th March 2014, 03:51 AM   |  #7  
0ri0n's Avatar
Senior Member
Attleboro, MA
Thanks Meter: 28
 
112 posts
Join Date:Joined: Feb 2007
More
Quote:
Originally Posted by Matrixk101

I was told in store that u need to update to a differnt kinda sim card for tap and pay I think its called a isis sim card l.

Sent from my SM-N900T using xda app-developers app

Thats only if you are going to use ISIS as opposed to GWallet. KitKat is supposed to utilize Host Card Emulation so no secure element or secure sim needed. Its built into android, but it seems right now that TMobile and ATT removed that function to force you to use ISIS since that is what they are backing. I could be wrong, but it doesnt make sense that the Sprint Note 3 uses the same NFC controller and can use tap n pay, but the TMobile and ATT variants cant.
6th March 2014, 04:08 AM   |  #8  
Senior Member
Thanks Meter: 439
 
1,044 posts
Join Date:Joined: Jan 2010
Quote:
Originally Posted by 0ri0n

Doesnt the sprint note 3 have the same nfc chip?

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://forum.xda-developers.com/show....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.
Last edited by siraltus; 6th March 2014 at 02:54 PM.
The Following 4 Users Say Thank You to siraltus For This Useful Post: [ View ]
6th March 2014, 05:26 AM   |  #9  
cmjkxa's Avatar
Senior Member
Flag San diego
Thanks Meter: 86
 
436 posts
Join Date:Joined: May 2011
More
Quote:
Originally Posted by siraltus

No it does not. The Sprint variant uses a different NFC controller that has both a built-in secure element and implements the FeliCa card emulation standard.

This is why Google Wallet worked on Android 4.3 on the Sprint variant but not on any of the other variants.

I helped discover this difference. More info here: http://forum.xda-developers.com/show....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.

I have a question. Will the new S5 have the same NFC chip as the Note 3? This article says it willhttp://nfctimes.com/news/nxp-wins-ba...-embedded-chip. Also the S5 press release said they'd support both Isis and GW here http://www.droid-life.com/2014/02/24...g-this-spring/ I'm just trying to piece this together.
6th March 2014, 01:51 PM   |  #10  
Senior Member
Thanks Meter: 439
 
1,044 posts
Join Date:Joined: Jan 2010
Quote:
Originally Posted by cmjkxa

I have a question. Will the new S5 have the same NFC chip as the Note 3? This article says it willhttp://nfctimes.com/news/nxp-wins-ba...-embedded-chip. Also the S5 press release said they'd support both Isis and GW here http://www.droid-life.com/2014/02/24...g-this-spring/ I'm just trying to piece this together.

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).
Last edited by siraltus; 6th March 2014 at 02:54 PM.

The Following User Says Thank You to siraltus For This Useful Post: [ View ]
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes