yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] drinfernoo:
Nothing. I use TWRP and had no issues.
[Android Software/Hacking General [Developers Only]] degiovab:
What about countries outside US?

Did anyone manage to have Tap & Pay active outside the US? (e.g. with a Samsung i9300)

I followed all steps and still Tap & Pay says "Not available".

It was working though with previous R96 modded.

Maybe there's an extra check based on location or mobile operator? :confused:
[Android Software/Hacking General [Developers Only]] vt0r:
Though I can't speak for Wallet outside the US, I had this same "Not available" issue because I was skipping the ROM flash step.

If you've followed the steps exactly as listed above (including removing all traces of Wallet from /system/app and /data/app, rebooting, flashing the ROM, flashing the app zip, etc), I suppose there could be some region-based checking as well, but I'm really not sure.

If the steps are surely being followed 100% as written, I would suggest creating a full nandroid backup with either CWM or TWRP - whichever you prefer - then try doing a factory/data wipe, wiping the cache/dalvik, flashing the ROM again, flashing the zip and trying it barebones stock to see if it works that way.

If you still have trouble, the region restriction is far more likely, however if it works this way, you'll need to restore your backup and continue trying the steps exactly as written in the OP.

Hope this helps.
[Android Software/Hacking General [Developers Only]] degiovab:
Indeed I tried flashing a fresh new ROM (both dirty flashing and again I tried after a full wipe). I use TouchWiz roms though.

In both cases Tap & Pay is Not available.

I am curious to see if other outside US have tried too.
[Android Software/Hacking General [Developers Only]] 78Staff:
I have 2.0 working on s3 with no issues, but have an S4 on they way. Is the S4 lib fix linked specifically for Verizon S4's only, or will it work on other carriers, ie AT&T?
[Android Software/Hacking General [Developers Only]] vt0r:
The NFC library fix for TouchWiz ROMs should work on all carrier variants of the S4, as the non-network hardware (secure element included) should be identical.

Feel free to test it out after making a nandroid backup in case of issues, but just remember it's not necessary for AOSP-based ROMs like CM, etc.
[Android Software/Hacking General [Developers Only]] Jonnycat411:
groan

well first time didn't work with just force stop and deleting of data/cache. got message implying wallet couldn't connect to interweb or something of the sort.. so did a clean install of rom with no google wallet and followed instructions.. got the warning saying wallet wasn't available for my phone yet. so gonna flash rom again.. start with original wallet version 1.6 again and try one more time. I noted that there was no information though when I went into root explorer looking to delete stuff the first time.. neither in system nor data. so am I correct that I need to have wallet on the phone before I flash the above zips? (yes I have touchwiz)
[Android Software/Hacking General [Developers Only]] vt0r:
No need to have wallet there already.

The steps mention removing it only because most people already have/had 1.6 installed, and it's important to start from scratch.
[Android Software/Hacking General [Developers Only]] Jonnycat411:
yep.. just not workin for me. even tried the manual push this time and still got "unfortunately google wallet is not yet available for your device..."

*edit*

ok so changed build prop and it loaded up fine but still shows version 1.6-r96 in about? what am I missing here? *edit again* just updated via the play store (thought what the hell lets see what it does) and now its saying it works.. tap and all. this is some messed up sh!t.
[Android Software/Hacking General [Developers Only]] norbarb:
I tryed this metod on S3, S4 so many times and all i get is : "Not Supported. Unfortunatly, Google Wallet is not yet avalable for your device or mobil network" I'm running TW stock rooded on bouth devices.
[Android Software/Hacking General [Developers Only]] Jonnycat411:
good then im not the only one.. again. maybe it will work for you.. after doin everything on this page.. edit your build prop to galaxy nexus and then just update from the play store.. Im on my way to 7-11 to test it. annnnnnd it worked.
[Android Software/Hacking General [Developers Only]] norbarb:
I try update from play store but no tap to pay... something bogge is gonig on.. :)
[Android Software/Hacking General [Developers Only]] reluttr:
Odd, I dont have tap to pay enabled after flashing on CM 10.1.3. :S

Do you have to do the "deleting wallet.apk" thing even if you had wallet installed from the play store "and using the xposed plugin" on the previous ROM? I also formatted Data before installing 10.1.3.

Edit: did a restore to before I installed the zip, there was no wallet related stuff in the specified folders in system. So maybe it has to do with my ROM being slightly "worn in".

Will try just installing everything fresh tonight.
[Android Software/Hacking General [Developers Only]] vt0r:
Yes.

The wallet APK deletion and clearing of its data were necessary at least in my case.

There is no build.prop modification needed with the modified APK, and those who are seeing version 1.x in about didn't properly clear the data or remove the APK(s) (or possibly both).

The application can be installed in both /system/app and /data/app, and it can be called different things, so it's important to check thoroughly for it and to force close / remove data before deleting all Google wallet APKs.

I also disabled the xposed module (Modaco) I used to use with 1.x before proceeding with the listed steps, as it should also no longer be needed.
[Android Software/Hacking General [Developers Only]] norbarb:
Is there else some data for wallet exept system/app and data/app ? I'm asking cuze everytime i push moddifed file and open wallet is asking me for pin not to setup new pin.
[Android Software/Hacking General [Developers Only]] vt0r:
While wallet is installed, you can just go to the app manager, find Wallet, force close it and clear its data, then remove any APK you have of the old or current version (in either /{system,data}/app).

This should remove all data stored by wallet versions 1.6 or 2.0, as the old version stored data in the same location, as far as I'm aware.

Just to be clear though, on subsequent flashes after ROM updates, etc, I no longer have to follow the entire setup procedure every flash.

It seems like I only have to choose the account, enter the PIN I chose the first time, then I'm ready to go.
[Android Software/Hacking General [Developers Only]] reluttr:
I just got it to work.

Basically you HAVE to flash wallet before booting the phone for the first time and doing the set up tutorial.

So in your case with touchwiz, you might need to check for rogue files, then factory reset in recovery, flash the lib fixes, then flash this zip. Then boot up the phone, setup wallet "in my case enter the pin", then activate tap to pay on the first screen.

With the past version of wallet you had to disable it before you could flash a new ROM due to a risk of actually "frying" the security chip. Is this still the case? Because I do not see a way to disable wallet in the settings.
[Android Software/Hacking General [Developers Only]] vt0r:
I guess I haven't been using Wallet for very long... I don't ever remember reading anything about that.

I've had no trouble just reflashing it after each nightly update and never disabled even the earlier 1.x versions between flashes.

Would you happen to have a link to one of the threads where this was mentioned?

I'm curious to read the explanation on that.
[Android Software/Hacking General [Developers Only]] drinfernoo:
Prior to the 2.0 update, you had to "deactivate" (there's another word, but I can't remember it) your Wallet app before flashing a new ROM, or it would "mess up the secure element". I haven't seen anything about this in 2.0, and there isn't even an option to "deactivate" it like there used to be.
[Android Software/Hacking General [Developers Only]] vt0r:
Whoops.

I never did that once with 1.6 and older.

I guess I got lucky! :)
[Android Software/Hacking General [Developers Only]] drinfernoo:
Me neither! That's why I used quotes :D
[Android Software/Hacking General [Developers Only]] degiovab:
I believe the option to "deactivate" is Settings->Change account.

It produces an effect very similar to what used to happen with v1.6.
[Android Software/Hacking General [Developers Only]] Inigo Montoya:
I finally got this to work on my S4 with safestrap running Eclipse GE. Took alot of fiddling but here's what I did.

1) I started from scratch. Uninstalled Wallet and removed all traces of it in system/app and data/app.

2) Rebooted into recovery

3) Installed the TW version of 2.0 found here: Download Link

4) Installed loserskater's modded version of 2.0 found here: Download Link

Now this is where I think I hit a bump in the road. When I rebooted my apps "refreshed" or whatever it says I forget right now, and upon opening Wallet after the restart I noticed no tap to pay. So I forced closed the Wallet app cleared cache and data and rebooted to recovery. From there:

5) I reflashed loserskater's modded version.

6) Reboot system

7) When I went back into Wallet the option to tap and pay was available.

Not sure why it worked for me this way but after about 25 attempts to get this thing to work in different ways I finally have it. I have yet to test it out but it is installed and tap to pay is available...Step 1!!!!
[Android Software/Hacking General [Developers Only]] degiovab:
Thanks. Just a quick question: are you based in the US or outside US?
[Android Software/Hacking General [Developers Only]] Inigo Montoya:
US
[Android Software/Hacking General [Developers Only]] cjranucci:
This worked for me. Thanks for the post!
[Android Software/Hacking General [Developers Only]] gk1016:
Worked awesome on my AT&T SG4 running CM 10.2 nightly builds. Great work!!
[Android Software/Hacking General [Developers Only]] ArtificialMusik:
Is this going to be updated to the newest GWallet? Not rushing or asking ETA. Was just seeing if that was the plan! Thanks though!
[Android Software/Hacking General [Developers Only]] vt0r:
Update will be ready some time today.
[Android Software/Hacking General [Developers Only]] drinfernoo:
Looks like Tap & Pay might be included in 4.4 :)
[Android Software/Hacking General [Developers Only]] vt0r:
Updated the OP with the new zip.

Be sure to remove the old v9 one from /system/app and any updates from /data/app (if applicable).

If you already had 2.0 working before with the v9 zip, there's no need to clear data for wallet - just remove the existing APKs, reboot into recovery, flash the new zip and you're fully updated.
[Android Software/Hacking General [Developers Only]] vt0r:
Just so that you're aware, my zip contains the same APK you used, so instead of copying the APK and setting permissions manually, just flash the zip to turn those two steps into one.

Glad you got it working, and thank you for posting back with the details.
[Android Software/Hacking General [Developers Only]] ConeyKiller:
Just flashed this and it says nothing about tap and pay? I came from v9 and it had a field saying tap and pay was ready to use.
[Android Software/Hacking General [Developers Only]] vt0r:
Did you remove the v9 APK from /system/app, as well as any wallet APK that may have been placed in /data/app from an automatic upgrade?

If settings --> about shows your real device and/or some message about tap to pay not being available, you should follow the original upgrade procedure to start from scratch.

What's weird is that mine still appeared to work after the play store upgrade.

It showed both tap to pay being available as well as my actual device (Verizon Galaxy S4).

I didn't test it out at any stores before flashing the updated zip in the OP, though.
[Android Software/Hacking General [Developers Only]] ConeyKiller:
Yeah. I followed to a tea. No instance in data/app says galaxy nexus under about....but tap and pay not available. Guess I'll just go back to v9.

Edit: went back to v9 and it asked me to set up tap and pay. V14 never did. Weird.
[Android Software/Hacking General [Developers Only]] reluttr:
So wait, if I update from the play store it might still have tap to pay enabled?
[Android Software/Hacking General [Developers Only]] vt0r:
I honestly wish I could say what was going on there, but the behavior of this app is so unpredictable, even when unmodified.

Since v9 is working now, I would make a nandroid backup, then try flashing the v14 zip to see if the upgrade works without clearing data.

Have you tried that already?
[Android Software/Hacking General [Developers Only]] ConeyKiller:
I just updated from play store last night. Went from v9 to v14. I did it this way because I could not get tap and pay to work via the v14 modded apk. It still says tap and pay is ready to use. Haven't had a chance to use it yet, though.

Edit: just checked after reading below me. It shows my device as d2uc not d2att but still says Samsung I747. So we shall see.
[Android Software/Hacking General [Developers Only]] vt0r:
Yes, it's definitely possible.

As I mentioned before, mine was working after the upgrade, and even showed the right device info.

I didn't want to risk trying it out like that since the VZW S4 is still not an official device, so I just flashed the V14 modified zip anyway.
[Android Software/Hacking General [Developers Only]] reluttr:
This only supports my theory as to how wallet handles the secure element now. Basically when you trick it to install the 1st time it puts a encryption key or something in the secure element, and any future installations of the app check here first to enable TTP instead of checking the build.prop. Obviously, wallet assumes if the approval key is in the secure element then the build.prop passed. Where if you clear data and then install it checks the build.prop. So in theory you should be able to safely update and retain TTP as long as you dont "log out" of wallet.

This modded apk spoofs the app to think your running a galaxy nexus, but it does not work on the 1st run of the app. To get around this you have to install the apk BEFORE doing the initial device setup, as this makes wallet skip the initial check for some reason "presumably because wallet assumes the device is compatible if it is preinstalled at the factory". However as I said, if you install this AFTER the initial set up then it goes ahead and checks the build.prop.

This is my only guess as to why it still works if you update from the play store. I want to say this is google giving us "unsupported" folk a helping hand, but in reality the skipped checks are probably done to help speed up loading times, as instead of having to verify 3 things it just checks in one necessary place now.

EDIT:

I just checked in the sticky thread and it supports my idea even more. It is entirely possible to change your build.prop, install wallet and enable TTP, then revert the build.prop with no negative side effects. Tap To Pay should work until you uninstall wallet or "log out" of wallet in its settings and you should also be able to update without worry. :D
[Android Software/Hacking General [Developers Only]] xCAVEMANx:
I just installed the latest lib from the other thread then did this modded apk. Then I upgraded right from play store and still have TTP.
[Android Software/Hacking General [Developers Only]] picklerick:
are there any libs available for the HTC One AT&T version?
[Android Software/Hacking General [Developers Only]] dabuck:
I'm on AT&T note 2 running CM 11 from 11/24 and using the v14 modded wallet app. Followed directions, but when trying to setup tap and pay, getting "Tap and pay setup failed. Unable to set up Wallet for purchases"

Settings/About shows the following:

Tap and pay - Unavailable (NfcPaymentSetupFailure: 11)

Version - Version 2.0-R133-v14-RELEASE

OS - yakju JDQ39E Galaxy Nexus test-keys (build.prop shows GT-N7105)

Any ideas what would be going on?
[Android Software/Hacking General [Developers Only]] vt0r:
There is no need to use the modified APK with 4.4 on devices with an NFC element.

Just install the updated official version (mine came from the PA gapps package for 4.4), run through the setup, removing the account first if it gives you trouble, and you'll now have integrated tap to pay.

EDIT: Here's the link: http://paranoidandroid.co/roms/gapps/
[Android Software/Hacking General [Developers Only]] borguesian:
Tried this... Still not working on note 2
[Android Software/Hacking General [Developers Only]] vt0r:
Can you be a little more specific, please?

> Tried this...

Tried what, exactly?

> Still not working on note 2

Please define not working.

What (if any) error message(s) did you receive?

At what point does the failure occur?

How is it reproduced?
[Android Software/Hacking General [Developers Only]] dabuck:
I tried updating to the official wallet version (not the modded one), but tap to pay showed not available. I changed build.prop to Galaxy Nexus and now had the option to setup tap to pay. It get's to the point where it's setting it up and then fails. Checking about shows the same error nfcpaymentsetupfailure: 11

I've been trying to find information about that error, but the only thing I could find points me to the possibility that my SE has been blacklisted. Isn't the SE virtualized now?
[Android Software/Hacking General [Developers Only]] vt0r:
Why would you modify build.prop?

If you're actually running 4.4, all you have to do is install the official wallet app.

If you still receive some error during tap and pay setup, you may have to "remove account data" from the settings, then re-add your account to Wallet and try again.
[Android Software/Hacking General [Developers Only]] dabuck:
I'm running BeanStalk 4.4 which uses a build.prop of:

ro.product.model=GT-N7105

ro.product.brand=samsung

ro.product.name=t0lte

ro.product.device=t0lte
[Android Software/Hacking General [Developers Only]] borguesian:
Using the stock app does not work for me either... Tap and Pay shows as unavailable. This is on beanstalk 4.4.
[Android Software/Hacking General [Developers Only]] vt0r:
Looks right to me..

And have you tried removing the account already?

Settings --> Change Account

I had a problem setting this version up after updating from 4.3, but it immediately worked after removing the account and re-adding it.
[Android Software/Hacking General [Developers Only]] dabuck:
Removed the account, then force stopped and cleared data. Tap to pay showed not available. Changed build.prop to nexus and rebooted. This time, tap to pay showed not started. Tried to see it up, but failed with same nfcpaymentsetupfailure: 11. Tried removing account and clearing data, but no change.
[Android Software/Hacking General [Developers Only]] vt0r:
Why are you still changing build.prop?

Please stop that.

It's NOT necessary anymore on 4.4 with the latest version of wallet, as the device restrictions have been removed.

If you're not sure if you have the latest Wallet, install the latest PA gapps package for 4.4.

Please change build.prop back to stock, knowing that you should never have to change it again, then reboot and repeat the same steps you did above, minus the Nexus change.
[Android Software/Hacking General [Developers Only]] borguesian:
Dude we have both tried both ways... If you don't change build.prop then tap and pay is unavailable... If you change it then you get the set up error. This is with the latest full PA gapps
[Android Software/Hacking General [Developers Only]] vt0r:
Well then I honestly don't know what to tell you. The only other common denominator here is Beanstalk.

I don't know enough about that ROM to really know what the issue is.

Is that a TouchWiz ROM by any chance?

Not sure if it matters anymore with 4.4, but with 4.3 and earlier, NFC libs were necessary.

It's supposed to be virtualized now, so I'm at a loss.
[Android Software/Hacking General [Developers Only]] borguesian:
Its based on CM11.... I had the same problem on that so I assume it is CM11 issue
[Android Software/Hacking General [Developers Only]] dabuck:
On latest beanstalk 4.4.2, the issue is resolved. Apparently the Rom was missing an nfc xml from /system/etc/permissions.
[Android Software/Hacking General [Developers Only]] dust.:
Followed these instructions for my S4 and now I'm getting a constant "Unfortunately, Nfc Service has stopped." message...

On a 4.3 TW based ROM so I flashed the NFC libs as instructed.
[Android Software/Hacking General [Developers Only]] _tru_:
this work for an Optimus G?
[Android Software/Hacking General [Developers Only]] vt0r:
Most likely, but this version is a bit outdated.

I upgraded to KitKat several months ago and have not been updating this zip or thread.

I would suggest getting it from loserskater's thread (as he is the one who created the APK in my zip):

http://xdaforums.com/showthread.php?t=2457569

I will update the OP to reflect the status.
[Android Software/Hacking General [Developers Only]] vt0r:
Sorry for the delay in response. I hope you've resolved this by now. If you have to stay on a 4.3 ROM that's TW based, I'd suggest visiting the original thread by loserskater to get his most updated APK.

In addition, you'll find links to the original NFC fix threads, which may have newer versions:

http://xdaforums.com/showthread.php?t=2457569
[Nexus 7 (2013) Q&A] lespaulman67:
Read all of this. Go to page 4 and read about Charger Interference.

http://www.silabs.com/Support Documents/TechnicalDocs/Minimizing-Touchscreen-EMI.pdf
[Nexus 7 (2013) Q&A] GoneTomorrow:
That''s nice and all, but that would only cause issues in the device-charging case. Since people seem to have issues in any situation, no, that isn't the problem.

Software is the most likely cause, since the latest update made my previously perfect touch Nexus 7 have the same issues as widely reported.
[Nexus 7 (2013) Q&A] lespaulman67:
So explain how mine and many other people that will find out soon or later that there tablet works great on hard surfaces and soon as you lay it down on a couch or pillow or any cloth type material they will have screen issues. If it was software my screen would work the same all the time.

So if my screen has dead spots when using it on my couch then I need some couch drivers right. Not lol

Its caused by some type of interference.

The software is causing less sensitivity so its blocking some of the excessive noise from your finger as it grounds itself to the screen. So when you hold the tablet or its plugged in it has a true ground at all times that why it works great.

Plus if it was software don't you think a company like Google would of fixed this issue already. There running around with there heads cut off looking for ideas to keep us from suing there but holes.
[Nexus 7 (2013) Q&A] GoneTomorrow:
ASUS develops and maintains of the low level software, not Google. Google only provides the Android OS and some creative input. This explains the delays, as Taiwanese companies are notorious for poor software support.

As you alluded to, the issues MAY be some kind of interference. With enough investigation, this can be mitigated through software. I work for a company that manufactures devices with 3rd party hardware very similar to the Nexus 7, and you'd be surprised how much errata we get for botched IC's that we then have to code around. Almost anything can be mitigated with software.

Either way, I highly doubt it has anything to do with charging. That link you provided talks about capacitive coupling from the switching transformer inside the power supply, how could this cause issues when the device isn't being charged?

In saying that, you have to remember that the number of users with actual issues is VERY small. Forget about threads on here for statistics, as this is where people come to moan about it.

Like I said, my touchscreen issues are clearly software related as it was flawless before the latest update JSS15R.
[Nexus 7 (2013) Q&A] sfhub:
Well, people with N7 first gen have touchscreen issues also despite not having the wireless charger.

http://www.youtube.com/watch?v=2ypEh4vOVkI