yashsingh1/xdaforums huggingface dataset:
[T-Mobile Samsung Galaxy Note 3] bdorr1105:
Don't be clear as mud in a post...There is a difference between Tap and Pay not showing and it just not being able to work because of hardware issues. Tap and Pay is still blocked, you can get the option to come up, however because the HCE framework does not support The NXP NFC Chipset it will never completely set up. Thanks for posting the thread but you should be more clear in what you say..Tap and Pay feature is blocked obvioulsy, the phones hardware setup will not prevent it from displaying. Regardless it won't configure based on your partially true statement. Thanks brother

There are closed source NXP implementations of HCE NXP, just nothing open source
[T-Mobile Samsung Galaxy Note 3] gakio12:
Actually, it isn't blocked. Are you saying that AOSP builds for the Note 3 are blocking Tap to Pay as well? The option does not appear in Cyanogenmod or any other AOSP based ROM. It isn't a hardware issue, it is a software issue. NXP just this week got the PN-547 chip integrated into Android 4.4, which means support will be there in 4.4.3.

Also why would Tap to Pay settings show up if it isn't going to work? Just wait for 4.4.3. Tap to Pay works on the S4 on T-Mobile, so T-Mobile obviously ISN'T blocking it.
[T-Mobile Samsung Galaxy Note 3] bdorr1105:
You can switch the build.prop to the Galaxy Nexus and it shows up...Same ROM, blocked before I remove T-Mobile build.prop info. What prop are you using. Input Galaxy build.prop and viola, tap and pay shows UP, like I said there is a difference from it being able to work and it to show up. We will see when that update comes around. Could be a while
[T-Mobile Samsung Galaxy Note 3] siraltus:
Don't be dense as mud. According to your "logic", T-Mobile is blocking Tap-and-Pay on AOSP ROMs including Cyanogen, which is quite simply impossible.
[T-Mobile Samsung Galaxy Note 3] bdorr1105:
Not being dense as mud, there can be software revisions, Im not saying the network is rejecting, but TouchWiz released by the carrier is different than AOSP..Did T-Mobile push out AOSP? No but all the TW Roms are based off oficial builds and need reverse engineering to see what was hacked, ie like any version of Wallet that has come out, lib fixes ect...not saying your wrong or trying to argue, I am just saying there is a difference.

There is a reason HCE was developed because the carriers cant touch it, however they can revise the OS to not use it, simple stupid stuff. HCE is the answer and the slap in the face to the big 3 trying to force ISIS down our throats...Just needs more development and integration
[T-Mobile Samsung Galaxy Note 3] open1your1eyes0:
I believe the only thing lacking here is the support for NXP chipsets. HCE is not disabled by T-Mobile or Samsung (as it's not allowed as per Android use terms by Google since it is part of the OS framework now). HTC actually added a closed-source support module to get their HTC One's NXP NFC controller with work with HCE but Samsung has not done the same for the Note 3 (yet at least). Perhaps they are waiting for Google to do it first.

According to the press release the Galaxy S5 will come with Google Wallet support (officially). Since we know the Galaxy S5 will have the NXP chipset, it is likely Samsung actually added their custom support module into that device framework (TouchWiz). We hope one day Samsung will do the same for the Note 3 if Google takes too long to release 4.4.3.
[T-Mobile Samsung Galaxy Note 3] bdorr1105:
Right I didn't say it was blocked which is the reason I said HCE was a slap in the face and I said the same thing about lacking support....i said there's a difference between tap and play showing up and it not working....same phone tmobile build. Prop no option, sprint prop it's like magic, even if HCE worked with our note 3 we still would need a hacked wallet that ignores the prop or makes it think the device is a nexus. I am not holding my breath for the note 3, the release of the s5 can certainly help though
[T-Mobile Samsung Galaxy Note 3] siraltus:
I think you're not understanding the simple idea that be it Samsung or Cyanogen or whoever makes the ROM chose to hide a feature that's non-functional and rightly so - after all, what's the point of exposing it only to have people attempt to use it and then get frustrated and pissed off? That's why it's hidden, and it will be exposed once the underlying hardware issues are worked out. Would you want your car to have a "Bluetooth" button only to press it and find out the Bluetooth system doesn't pair with any phones, even though it's there?
[T-Mobile Samsung Galaxy Note 3] bdorr1105:
The reason it was blocked was because ATT, Verizon, and Tmobile are behind IS IS and they wanted to prevent Google Wallet from taking off so the first attempt was just blocking it from the market, then blocking access to the secure element and all in all Google answered by Introducing HCE, however everyone has been frustrated they can't use it period, whether it's limited locations or not....it has worked awesome since the S3 just had to go through hell and high water just to be able to use it
[T-Mobile Samsung Galaxy Note 3] siraltus:
Did you not read what I wrote? Did you miss the part where AOSP ROMs are also not showing Tap-and-Pay for phones whose NFC hardware is not yet supported by KitKat's HCE framework? Cyanogen and any other AOSP ROM makers hiding Tap-and-Pay until the phone's NFC hardware is supported has nothing to do with T-Mobile or ISIS.
[T-Mobile Samsung Galaxy Note 3] bdorr1105:
Because they have their own version of A mobile wallet but you can easily fix that....you are just arguing too argue....look it up on the Internet did a research paper on it...AOSP are where all the wallet fixes came from so if it's blocked totally up to the dev on AOSP
[T-Mobile Samsung Galaxy Note 3] gakio12:
This has nothing to do with blocking. Yes, in the past, the carriers blocked Google Wallet from the Play store, then removed secure elements from the phones, etc. Now that is not the case.

The only reason why you don't see Tap-and-Pay in settings is because the framework doesn't support the PN-547 NFC chip yet (on Google's end).

By changing the build.prop to Galaxy Nexus, you are telling the OS that it is a different phone, so it thinks it will work. That's why when you set it up it doesn't work.

There is a big blank spot in the source code of the framework for the pn547, it does nothing when called. That's all there is to it.
[T-Mobile Samsung Galaxy Note 3] Persianhawkes:
Is there a way to manually update the NFC chip to support hce. Maybe this article may shed some info

http://www.nfcworld.com/2014/02/26/328088/nxp-updates-nfc-controller-hce/
[T-Mobile Samsung Galaxy Note 3] siraltus:
I think you are really clueless on the subject, so I'm not going to prolong this. Moving on.
[T-Mobile Samsung Galaxy Note 3] bdorr1105:
Not really at all, you were naive about everything, but thanks for wasting my time though
[T-Mobile Samsung Galaxy Note 3] bdorr1105:
Not really at all, you were naive about the whole subject, anyway thanks for wasting my time though
[T-Mobile Samsung Galaxy Note 3] bdorr1105:
Thanks for the productive info though.

Google dropped support for NXP in favor of broadcom for the time being. Looking forward to the future
[T-Mobile Samsung Galaxy Note 3] gakio12:
deleted;
[T-Mobile Samsung Galaxy Note 3] Persianhawkes:
Well hopefully soon. Google wallet has came in hand numerous times at the store where I have forgotten my wallet.
[T-Mobile Samsung Galaxy Note 3] open1your1eyes0:
This!

Until 4.4.3 is released and confirmed to add the HCE support for NXP NFC Controllers, one of two things is and will stay true:

Any KitKat ROM based on pure AOSP will fail to work with Tap and Pay on ANY device that has the NXP NFC controller (ie. Galaxy Note 3, HTC One, Moto X).

Any KitKat ROM based on GPe/TouchWiz/Sense/Other-3rd-party-framework will work with Tap and Pay

ONLY

if the official framework added at least a closed-source support for their NXP chipset (like already on the HTC One and Moto X) and the same has been carried over to that custom ROM as well.

As far as we know (aside from possibly the upcoming Galaxy S5 based on the press release), Samsung did not add their own NXP chipset HCE support into TouchWiz yet.

You can hack the build.prop to make it appear as a different device to Google Wallet and it may show up but the actual transaction point will fail because the framework itself lacks the code needed to process all that to the NFC controller itself. So just small FYI, it's not even worth messing with build.prop for that reason.
[T-Mobile Samsung Galaxy Note 3] Walter.White:
For people who care about Tap and Pay..Support for PN547 might be coming soon

http://www.nfcworld.com/2014/02/26/328088/nxp-updates-nfc-controller-hce/
[T-Mobile Samsung Galaxy Note 3] Entropy512:
It's not build.prop. Build.prop hacks will work for "legacy" SE-based support (GW without HCE) although this has been announced to be going away as of April 14. Past then - HCE is the only solution.

HCE can be "enabled" (at least from the perspective of an app) by adding a special permissions XML to /system/etc/permissions - this will cause Wallet to claim it's ready for tap-and-pay, but when you actually try to pay at a payment terminal, nothing will happen.

The majority of Android devices with NXP chipsets are PN544, not PN547.

Not sure how much difference there is.
[T-Mobile Samsung Galaxy Note 3] open1your1eyes0:
Thank you for the correction/clarification. Was not aware as it seems HCE is no longer build.prop sensitive as in the past with SE-based authentication.
[T-Mobile Samsung Galaxy Note 3] Samstealth7:
sorry if this doesn't really belong here but I didn't come up with much information upon doing a search,

I noticed some of the other carriers have a mod for Isis wallet that enables Them to use Tap & pay at any PayPass station,

do we have anything like that for us since we cant use tap and pay with Google Wallet, I mean if we can get tap & pay through Isis to work at all of the PayPass stations, we can just run Google Wallet for everything else, I could live with that

Thanks in advance guys. And sorry if this doesn't belong hear.
[T-Mobile Samsung Galaxy Note 3] bdorr1105:
You need to get Xposed Framework

also go here and download Isis Root Bypass for xposed, activate the module and download ISIS from the marketplace, enable NFC and setup
[T-Mobile Samsung Galaxy Note 3] gilbertodelbosque:
it work for me

thank you for your information....it did work for me. (i'm on t-mobile)
[T-Mobile Samsung Galaxy Note 3] Samstealth7:
Thanks buddy. Downloading now.
[T-Mobile Samsung Galaxy Note 3] bdorr1105:
No problem glad it worked
[T-Mobile Samsung Galaxy Note 3] Samstealth7:
Says my device is not supported?

followed all the steps to the T.

the phone is rooted and I do have the latest exposed activate, correct module installe, the app starts perfectly fine and I get through the setup enter my PIN number, get to setup my email address and password after I complete that step, it says device is not supported

so I went back reinstall the module, deleted Isis cleared cache and data before deleting it,

clear dalvik cache through TWRP not sure where to go from here. here's some screenshots.

thanks in advance
[T-Mobile Samsung Galaxy Note 3] farfromovin:
The model should be SM-N900T.
[T-Mobile Samsung Galaxy Note 3] bdorr1105:
Yea if you looked at the comment below you, your build.prop was wrong, hit the thanks button
[T-Mobile Samsung Galaxy Note 3] zaydaboss:
Links no longer work is there a mirror ?
[T-Mobile Samsung Galaxy Note 3] bdorr1105:
These links were never active because wallet does not work on the note 3
[T-Mobile Samsung Galaxy Note 3] KennyG123:
Thread closed at OP's request
[T-Mobile Samsung Galaxy Note 3] ttabbal:
If that's all you need in there, I can probably xposed that check out tonight. ...
[T-Mobile Samsung Galaxy Note 3] Fenny:
Anyone feel like posting up the deodexed nfcnci.apk? :D
[T-Mobile Samsung Galaxy Note 3] rmsmerd:
I'm confused. I installed this on my note 2 with this method and it worked well. I now have to note 3 and I installed Google wallet from the play store. Why the need to go through all this?
[T-Mobile Samsung Galaxy Note 3] ttabbal:
Because the carriers are trying to push isis on everyone.
[T-Mobile Samsung Galaxy Note 3] rmsmerd:
Ahh. Yeah I rather keep my Google wallet
[T-Mobile Samsung Galaxy Note 3] Fenny:
Try replacing Nfc.apk with this one: http://www.cheatersedge.org/android/n900/Nfc.apk

I did this mod blind (I don't have a note 3 to test on), so we will have to see if it works. Make sure you make a backup of the original file.

You will also need to add the following to the resources section of the nfcee_access.xml file.

<!-- Google wallet release signature -->
<signer android:signature="3082044c30820334a003020102020900a8cd17c93da5d990300d06092a864886f70d01010505003077310b3009060355040613025553311330110603550408130a43616c69666f726e6961311630140603550407130d4d6f756e7461696e205669657731143012060355040a130b476f6f676c6520496e632e3110300e060355040b1307416e64726f6964311330110603550403130a476f6f676c65204e4643301e170d3131303332343031303635335a170d3338303830393031303635335a3077310b3009060355040613025553311330110603550408130a43616c69666f726e6961311630140603550407130d4d6f756e7461696e205669657731143012060355040a130b476f6f676c6520496e632e3110300e060355040b1307416e64726f6964311330110603550403130a476f6f676c65204e464330820120300d06092a864886f70d01010105000382010d00308201080282010100c30f88add9b492096a2c586a5a9a80356bfa026958f8ff0c5dfaf59f49268ad870dee821a53e1f5b170fc96245a3c982a7cb4527053be35e34f396d24b2291ec0c528d6e26927465e06875ea621f7ff98c40e3345b204907cc9354743acdaace65565f48ba74cd4121cdc876df3522badb095c20d934c56a3e5c393ee5f0e02f8fe0621f918d1f35a82489252c6fa6b63392a7686b3e48612d06a9cf6f49bff11d5d96289c9dfe14ac5762439697dd29eafdb9810de3263513a905ac8e8eaf20907e46750a5ab7bf9a77262f47b03f5a3c6e6d7b51343f69c7f725f70bcc1b4ad592250b705a86e6e83ee2ae37fe5701bcbdb26feefdfff60f6a5bdfb5b64793020103a381dc3081d9301d0603551d0e041604141ccece0eea4dc1121fc7515f0d0a0c72e08cc96d3081a90603551d230481a130819e80141ccece0eea4dc1121fc7515f0d0a0c72e08cc96da17ba4793077310b3009060355040613025553311330110603550408130a43616c69666f726e6961311630140603550407130d4d6f756e7461696e205669657731143012060355040a130b476f6f676c6520496e632e3110300e060355040b1307416e64726f6964311330110603550403130a476f6f676c65204e4643820900a8cd17c93da5d990300c0603551d13040530030101ff300d06092a864886f70d01010505000382010100a470c728e1d31b06d9af6ae768b565046c57806b9843724931d75d4ca10c321520d33ccfed2aa65462234c9ef9b6f910cc676b99cb7f9895d6c06763574fbb78331275dc5cf38fbaa918d7938c051ffba2ade8f303cde8d9e68a048d1fdb9e7c9f2a49b222c68fff422bf15569b85eeeedb04aa30873dbe64b9c9e74f8f2c2f6c40124aaa8d1780d18512b540add28b3e9581971a4170dd868cf5f31e44712b2c23bb51037d7ef9f87a6e5bdb35e2ceb6bb022636c17a56a96bc7a50258c0bd2ed7b31555a18452e17321a0d52838c82f63f742d74ff79586a5cbb7faf7198a84bcf744310e9e927597f00a23dd00660800c2238d90b2fb372dfdbba75bd852e" />

Attached is a zip with this already done. (No, it's not flashable... sheeesh.)
[T-Mobile Samsung Galaxy Note 3] ttabbal:
Made these changes and the build.prop mods and installed wallet. It complaints about secure element access. I double checked the XML to make sure the key is installed.
[T-Mobile Samsung Galaxy Note 3] Fenny:
Can you grab a logcat?

Are you using the stock google wallet application (from the play store)?

Also, you did reboot after replacing/editing the xml file, right?
[T-Mobile Samsung Galaxy Note 3] Fenny:
try adding the following line just before the google wallet cert in the xml.

<debug />

I.E.

<!-- Google wallet release signature -->
<debug />
<signer android:signature="blabla" />

it should spit out signatures in logcat.

*Edit*

AH-HA!

You may need to install wallet as a system app, and then install an "update" into /data/app, otherwise I can disable the nfcee_admin check, but that is a scary solution.
[T-Mobile Samsung Galaxy Note 3] Fenny:
Did it dump signatures into logcat?

If so, we can correct whatever is wrong with our signatures.

Okay, I made another mod to nfc.apk, this will allow any application to access the secure element, so you should NOT use it as a final solution, but we can test with it.

http://www.cheatersedge.org/android/n900/Nfc.NoAdminCheck.apk

Rename to Nfc.apk, and replace in /system/app. You may also want to ensure you if you are not deodexed that you rename Nfc.odex... Just a thought. ;D

Also don't know if you saw this in my previous post:

AH-HA!

You may need to install wallet as a system app, and then install an "update" into /data/app.
[T-Mobile Samsung Galaxy Note 3] ttabbal:
Nope, no signatures in the log. I tried the new APK, no change.

I just saw your mention of making it a system app. I'll try that.
[T-Mobile Samsung Galaxy Note 3] Fenny:
Sounds like a plan, and just to confirm, even with that new modified Nfc.apk you are still seeing "java.lang.SecurityException: /etc/nfcee_access.xml denies NFCEE access to com.google.android.apps.walletnfcrel" in the logcat?
[T-Mobile Samsung Galaxy Note 3] ttabbal:
Still no signatures in the log... There's got to be something missing....

For a system app, I just copied it over to /system/app and changed permissions. I also wiped the data and ran the selinux fix script.

Still getting the same error in the log with the modified Nfc.apk.

ROM is the deodexed stock posted here in the dev forum.
[T-Mobile Samsung Galaxy Note 3] Fenny:
Well then we know that there is an additional check outside of Nfc.apk... because the only place that error string can come from is in the NfcService class.

fenny@ohBitchPlz:~/Android-Kitchen/WORKING_N900TUVUBMI7/system/app/Nfc$ grep -r "/etc/nfcee_access.xml" .
./com/android/nfc/NfcService.smali: const-string v2, "/etc/nfcee_access.xml denies NFCEE access to "
./com/android/nfc/NfceeAccessControl.smali:.field public static final NFCEE_ACCESS_PATH:Ljava/lang/String; = "/etc/nfcee_access.xml"
./com/android/nfc/NfceeAccessControl.smali: const-string v15, "/etc/nfcee_access.xml"
./com/android/nfc/NfceeAccessControl.smali: const-string v15, "could not find /etc/nfcee_access.xml, no NFCEE access allowed"

There must be some code duplication in /system/framework or something... or crazy thought: Maybe it doesn't like the tabs in the xml file. perhaps replace them with spaces...
[T-Mobile Samsung Galaxy Note 3] ttabbal:
I'll pull it over and try replacing it...

Out of curiosity, I did an on-device grep for the xml filename... Found this

root@maguro:/ # cd /system
root@maguro:/system # grep -r "/etc/nfcee_access.xml" .
./etc/security_nfc_profile.dat:config@system/etc/nfcee_access.xml
root@maguro:/system #

I'll attach that .dat file in a zip. It's referencing the Nfc.odex in there, could it be something like that?

EDIT: Tried fixing up the xml file. All spaces, no joy.
[T-Mobile Samsung Galaxy Note 3] Fenny:
I believe that that that file contains the signatures that NFC.aPK uses to test to ensure that system files have not been modified. I have patched that check out of NFC.aPK. I'm headed home from work in 2 minutes here, and I'm thinking what I need to do is decompile all of the files from framework. Then I can search through to find any files that reference that string.
[T-Mobile Samsung Galaxy Note 3] ttabbal:
Thanks for your help. I'll check back if I find anything and am happy to test new changes.
[T-Mobile Samsung Galaxy Note 3] bdorr1105:
You guys are all over it I tried decompiler today against the stock deodexed framework just didn't have time to actually sit down and look yet. Also I passed the insufficient keys...The wallet app force closes because no access to the secure element which is in the NFC apk. Also there are libs as well that I have seen with every workaround on Samsung. I pulled them from sprint. Has anyone tried with Sprint libs?
[T-Mobile Samsung Galaxy Note 3] Fenny:
I decompiled all of both /system/app/ and /system/framework/ and the ONLY reference to that file is in Nfc.apk are you certain that you don't have an .odex file in /system/app? Tried clearing dalvik cache?

I would to a lot more testing if I had one of these devices... :P
[T-Mobile Samsung Galaxy Note 3] siraltus:
I noticed that the files that have "nci" (no carrier integration?) in the name on the Sprint version are equivalents to files that don't have "nci" in the name - for example, Nfc_nci.apk on Sprint would equal Nfc.apk on T-Mobile. However, replacing all those files with Sprint versions and changing the names results in the NFC service repeatedly crashing.

I'll keep digging. Also, if I'm wrong about the above, please correct me, I'm just speculating here based on file sizes and names.
[T-Mobile Samsung Galaxy Note 3] ttabbal:
Cleared Dalvik, same thing. I'm not getting the keys printed out in the log either, even though I do have the <debug /> in there.

C:\Users\ttabbal>adb shell ls /system/app/*.odex
/system/app/*.odex: No such file or directory

No .odex files....

Probably not related, but searching the log, I found this...

W/PackageManager( 2829): Unknown permission com.android.nfc.permission.NFCEE_ADMIN in package com.google.android.apps.walletnfcrel

Funny thing is, when I had Wallet I rarely used it. This whole carrier nonsense is just irritating me. :)
[T-Mobile Samsung Galaxy Note 3] Fenny:
Hmm, very possibly related. That's what is causing the wallet app to freak out it looks like... perhaps we should patch that part out.

Alright fine... I downloaded the Sprint system dump, and I am going to deodex, decompile, and compare the services. I'll watch for functions that need to be ported from the sprint NfcNci.

http://www.youtube.com/watch?feature=player_detailpage&v=ueZ6tvqhk8U#t=19
[T-Mobile Samsung Galaxy Note 3] bdorr1105:
The exact propblem I keep running into myself. They also did the same exact thing with the lib files, non of them are named the same, probably Sammy's way or the Carriers way of trying to make it harder, it breaks NFC when you swap the files
[T-Mobile Samsung Galaxy Note 3] Fenny:
It's possible that there needs to be support built into the kernel for a specific block device. see below:

WORKING_N900TUVUBMI7/system/app/Nfc/com/android/nfc/NfcService.smali:"/etc/nfcee_access.xml denies NFCEE access to
WORKING_N900TUVUBMI7/system/app/Nfc/com/android/nfc/NfcIntegrityChecker.smali:"/system/etc/security_nfc_profile.dat
WORKING_N900TUVUBMI7/system/app/Nfc/com/android/nfc/NfcIntegrityChecker.smali:"/system/etc/security_nfc_profile.dat
WORKING_N900TUVUBMI7/system/app/Nfc/com/android/nfc/dhimpl/NativeNfcManager.smali:"/system/vendor/firmware/libpn544_fw.so"
WORKING_N900TUVUBMI7/system/app/Nfc/com/android/nfc/dhimpl/NativeNfcManager.smali:"/system/vendor/firmware/libpn547_fw.so"
WORKING_N900TUVUBMI7/system/app/Nfc/com/android/nfc/NfceeAccessControl.smali:"/etc/nfcee_access.xml"
WORKING_N900TUVUBMI7/system/app/Nfc/com/android/nfc/NfceeAccessControl.smali:"/etc/nfcee_access.xml"

WORKING_N900PVPUBMI3/system/app/NfcNci/com/android/nfc/NfcService.smali:"/dev/felica_cen"
WORKING_N900PVPUBMI3/system/app/NfcNci/com/android/nfc/NfcService.smali:"/dev/felica_cen"
WORKING_N900PVPUBMI3/system/app/NfcNci/com/android/nfc/NfcService.smali:"/etc/nfcee_access.xml denies NFCEE access to
WORKING_N900PVPUBMI3/system/app/NfcNci/com/android/nfc/NfcIntegrityChecker.smali:"/system/etc/security_nfc_profile.dat
WORKING_N900PVPUBMI3/system/app/NfcNci/com/android/nfc/NfcIntegrityChecker.smali:"/system/etc/security_nfc_profile.dat
WORKING_N900PVPUBMI3/system/app/NfcNci/com/android/nfc/NfceeAccessControl.smali:"/etc/nfcee_access.xml"
WORKING_N900PVPUBMI3/system/app/NfcNci/com/android/nfc/NfceeAccessControl.smali:"/etc/nfcee_access.xml"

Looks like the T-mo version uses user-mode so files, while the Sprint version uses a device block in raw. Anyone care to give me the result of the following command?

su root ls -l /dev/
[T-Mobile Samsung Galaxy Note 3] bdorr1105:
You want me to do that using terminal emulator
[T-Mobile Samsung Galaxy Note 3] Fenny:
Or adb shell. Either works.
[T-Mobile Samsung Galaxy Note 3] Fenny:
Try without the '-l' or pipe the results to a text file.

yourcommand > /sdcard/out.txt

Then post the file.
[T-Mobile Samsung Galaxy Note 3] bdorr1105:
what would the full command look like to pump out as a txt file