Why is android pay and samsung pay not available for the note 3

[tnerb123]

Anyone got a clue on why either of these are not compatible with the note 3? Is the version android we are on? If so I am starting to think Samsung hates the note 3 buyers.

 

[KTownGT]

Because Samsung doesn't want repeat customers? :silly:

 

[cherokee140]

This might explain it a bit:

http://forum.xda-developers.com/showpost.php?p=59951925&postcount=163

http://forums.androidcentral.com/ve...3/512346-mobile-payment-options-note-3-a.html

My understanding is that currently there are 2 different NXP chips which use two different stacks.
pn544 used libnfc-nxp stack binary patched by NXP to add HCE support (no support in AOSP for HCE)
pn547 uses libnfc-nci, which is from broadcom but uses standard NCI command sets, with HCE support already in-place in AOSP code.

There has been investigations to establish if pn544 could be made NCI-compliant through firmware upgrade, but it seems like it is not working, thus no HCE support for pn544, binary patched images excluded.
pn547 have HCE support, but it seems like Ttp capabilities are still missing for some Google choice

Sorry to resurrect the thread with a new question: how does all of this relates to the HCI based infrastructure in Linux kernel (drivers/nfc) ?
Android support, afaik, is completely userspace, using a trivial i2c-dev kernel driver as interface. Is this correct? Where is the i2c-dev driver for pn544/547? It shouldn't be in drivers/nfc/ tree right?

 

[tnerb123]

This might explain it a bit:

http://forum.xda-developers.com/showpost.php?p=59951925&postcount=163

http://forums.androidcentral.com/ve...3/512346-mobile-payment-options-note-3-a.html

My understanding is that currently there are 2 different NXP chips which use two different stacks.
pn544 used libnfc-nxp stack binary patched by NXP to add HCE support (no support in AOSP for HCE)
pn547 uses libnfc-nci, which is from broadcom but uses standard NCI command sets, with HCE support already in-place in AOSP code.

There has been investigations to establish if pn544 could be made NCI-compliant through firmware upgrade, but it seems like it is not working, thus no HCE support for pn544, binary patched images excluded.
pn547 have HCE support, but it seems like Ttp capabilities are still missing for some Google choice

Sorry to resurrect the thread with a new question: how does all of this relates to the HCI based infrastructure in Linux kernel (drivers/nfc) ?
Android support, afaik, is completely userspace, using a trivial i2c-dev kernel driver as interface. Is this correct? Where is the i2c-dev driver for pn544/547? It shouldn't be in drivers/nfc/ tree right?

Thanks for this.

Samsung just lost me as a customer. First the GPS never works, then the whole storm about Knox, then android/samsung pay, now no updates post 5.0?

This phone was dropped by them for getting updates in May way before the 2 years commitment they said they would keep.

 

[KTownGT]

Thanks for this.

Samsung just lost me as a customer. First the GPS never works, then the whole storm about Knox, then android/samsung pay, now no updates post 5.0?

This phone was dropped by them for getting updates in May way before the 2 years commitment they said they would keep.

This.

It's not exactly flattering when a flagship phone is mostly forgotten the next year. Especially when your biggest 2 competitors still support older/cheaper/slower products

Sent from my SM-n900A using Tapatalk