Mobile payment options for Note 3

[Amy Furlong]

Anyone know of any upcoming changes to Google Wallet or perhaps another nfc/tappa app that will work with the Note 3? I used Softcard and it worked well. A little bummed I can't pay with the phone anywhere (other than with starbucks app etc specific stores like that). Briefly had the LG G3 and loved using the tap n pay but missed this note 3

 

[gozirra]

It's a hardware issue. SOME Note 3's have an incompatible chip. So rather than code around that, they just say, "sorry, you can't play."

They also list which models have incompatible chips:

Not all devices running KitKat will support tap and pay. Here is a list of devices running KitKat that cannot be used for tap and pay:

• Evo 4G LTE
• Nexus 7 (2012)
• Samsung Galaxy Note III
• Samsung Galaxy S3
• Samsung Galaxy Light

https://support.google.com/wallet/answer/1347934?hl=en

 

[Hghlndr]

I'm with ya about being bummed! I'm a bit dubious about the "dysfunctional hardware" as it works on some carriers' Note 3, just not the VZW, AT&T, T-MOBILE models. And aren't they the big 3 who started the Isis/SoftCard fail and sold to Google? And isn't it interesting when I spent at least 4 calls with Wallet tech support it was quietly said they had a contract with the carriers re their app and maybe things will change with 5.0
Time will tell I suppose... until then it's hurry up and wait. :-(

Posted via Android Central App

 

[gozirra]

Like I said, different chipsets for different models.
Here's the source.
NXP Controller HCE for Google Wallet - Post #163 - XDA Forums

 

[kawana72]

So is this something that can be fixed in an update to either wallet or with 5.0? It seems did that tap to pay works with softcard, but not with wallet which we were told to use in its stead.

 

[recDNA]

So is this something that can be fixed in an update to either wallet or with 5.0? It seems did that tap to pay works with softcard, but not with wallet which we were told to use in its stead.

Can't fix chips with software. It's a hardware problem.

 

[Serial Fordicator]

If it's hardware, why did it work with Softcard?

 

[gozirra]

If it's hardware, why did it work with Softcard?

Simple. The requirement for a specific chipset wasn't checked for in Softcard. The only way that GW will ever work again on devices without that chipset is to remove the code that looks for that chipset (which is why, in the old days, there were different versions of Wallet for different carriers - I was able to install the Sprint version on my old rooted S3 and it worked as tap and pay, the Verizon version didn't). And since Google implemented the code to maintain compliance, I seriously doubt they will revert it due to the serfs uprising.

 

[kawana72]

So, wouldn't Verizon be able to remove the offending code? After all, softcard is now part of Google, right? It just seems ham fisted to force users from one system that works to another that will not replicate the basic performance of the first.

 

[Richard Friel]

Where did you get the Sprint version of NFC code to install on your rooted Verizon s3?

 

[gozirra]

This is the thread I used back then. It probably won't work anymore, but it was real and working at the time.

[GUIDE]Google Wallet - Everything you need t… | Sprint Samsung Galaxy S III

 

[gozirra]

Note that it was a Sprint version of the Google Wallet app (and being rooted, and editing your build.prop to make it look like you were a Sprint device instead of a Verizon device) to make all this work. That version specifically didn't look for a secure element, like the "official" Verizon version of Google Wallet did.

 

[Richard Friel]

Is there a similar link for the Verizon note 3?