I just happened to be looking when this appeared....
http://www.androidpolice.com/2013/09/17/google-introduces-the-new-and-improved-wallet-app-supports-all-android-phones-across-any-carrier/
:victory:It says it might not work on all phones, but it's working on my DNA, just thought the community would want to know.:victory:
NFC on your dna?
spinkick said:
NFC on your dna?
Click to expand...
Click to collapse
Yeah, the DNA has NFC.
Edit: just read your post on another thread. Was just about to go to the store to test out. Have they tried that and NFC isn't working, or NFC isnt working in general?
I have just installed it on my DNA and I'm going to try the vending machine here on campus. Will update soon!
Sent from my Galaxy Nexus using Tapatalk 4
scariestgnome said:
Yeah, the DNA has NFC.
Edit: just read your post on another thread. Was just about to go to the store to test out. Have they tried that and NFC isn't working, or NFC isnt working in general?
Click to expand...
Click to collapse
I have not tried yet, but without the secure element I dont see how it could work. Verizon wins again
If you go to the about screen it still says that tap and pay is "not available" for us. So I'm guessing we still can't use it for that. I wonder with this new version if it might be easier to get it to work though?
Droid DNA 4.3
spinkick said:
I have not tried yet, but without the secure element I dont see how it could work. Verizon wins again
Click to expand...
Click to collapse
We are able to get the SE Sim Cards from Verizon. If that's the only thing stopping it from working, then that's a piece of cake. If and only if
Just confirmed that if you change your build.prop to a Tap and Pay supported phone like the Galaxy Nexus, it will then proceed to look for a Secure Element and wallet will not load. If you keep your stock build prob for your device it knows that it has no secure element and will just report back that Tap and Pay is not available. Pulled a log cat to confirm this. It returns that no SMX is available and will force close wallet after a certain amount of time.
I'm wondering if Google might of added the ability to look for Secure Elements on sim cards with this updated. Can anyone confirm that might have an NFC SE Sim card?
Bottom line is.... If we have no SE embedded on our phones, then NFC payments with Wallet are not a possibility.
bb12489 said:
Just confirmed that if you change your build.prop to a Tap and Pay supported phone like the Galaxy Nexus, it will then proceed to look for a Secure Element and wallet will not load. If you keep your stock build prob for your device it knows that it has no secure element and will just report back that Tap and Pay is not available. Pulled a log cat to confirm this. It returns that no SMX is available and will force close wallet after a certain amount of time.
I'm wondering if Google might of added the ability to look for Secure Elements on sim cards with this updated. Can anyone confirm that might have an NFC SE Sim card?
Bottom line is.... If we have no SE embedded on our phones, then NFC payments with Wallet are not a possibility.
Click to expand...
Click to collapse
I wonder if all it needs now to get SMX access is the nfc_access.xml file in /system/etc that contains the Google Wallet key, instead of just a Isis key. AFAIK, you can have both keys listed in the nfc_access.xml file. But if you don't have a NFC sim card, I guess you can't verify ...
If you feel like changing your build.prop again, maybe you could experiment with the nfc_access.xml file?
jasoraso said:
I wonder if all it needs now to get SMX access is the nfc_access.xml file in /system/etc that contains the Google Wallet key, instead of just a Isis key. AFAIK, you can have both keys listed in the nfc_access.xml file. But if you don't have a NFC sim card, I guess you can't verify ...
If you feel like changing your build.prop again, maybe you could experiment with the nfc_access.xml file?
Click to expand...
Click to collapse
I have the right SIM, and wouldn't mind testing this for you. You may have to walk me through it, though... I'm not extremely savvy with altering xml files.
Sent from my HTC6435LVW using Tapatalk 4
bb12489 said:
Just confirmed that if you change your build.prop to a Tap and Pay supported phone like the Galaxy Nexus, it will then proceed to look for a Secure Element and wallet will not load. If you keep your stock build prob for your device it knows that it has no secure element and will just report back that Tap and Pay is not available. Pulled a log cat to confirm this. It returns that no SMX is available and will force close wallet after a certain amount of time.
I'm wondering if Google might of added the ability to look for Secure Elements on sim cards with this updated. Can anyone confirm that might have an NFC SE Sim card?
Bottom line is.... If we have no SE embedded on our phones, then NFC payments with Wallet are not a possibility.
Click to expand...
Click to collapse
It checks the the phone is rooted. That's what is stopping it. If you go to Verizon galaxy s4 thread and go to Google wallet you can see what they did to make it work.
Sent from my SCH-I545 using Tapatalk 4
egore93 said:
It checks the the phone is rooted. That's what is stopping it. If you go to Verizon galaxy s4 thread and go to Google wallet you can see what they did to make it work.
Sent from my SCH-I545 using Tapatalk 4
Click to expand...
Click to collapse
Those methods do not work. They have been tried in the past. You still need a secure element to have Tap n Pay function. The DNA lacks this element, but the GS4 has it.
bb12489 said:
Those methods do not work. They have been tried in the past. You still need a secure element to have Tap n Pay function. The DNA lacks this element, but the GS4 has it.
Click to expand...
Click to collapse
Oh OK. I have a S4 and have the old wallet installed on it. My DNA I have not messed with it. That sucks!
Sent from my SCH-I545 using Tapatalk 4
egore93 said:
Oh OK. I have a S4 and have the old wallet installed on it. My DNA I have not messed with it. That sucks!
Sent from my SCH-I545 using Tapatalk 4
Click to expand...
Click to collapse
Yea it does...
The new wallet app works on the S4 right out of the box! Really makes me want to switch to it from my DNA, but the G2 is looking like my next choice Sadly Wallet doesn't function on that either :/
bb12489 said:
Yea it does...
The new wallet app works on the S4 right out of the box! Really makes me want to switch to it from my DNA, but the G2 is looking like my next choice Sadly Wallet doesn't function on that either :/
Click to expand...
Click to collapse
The tap to pay does not work unless you trick the build prop.
Sent from my SCH-I545 using Tapatalk 4
egore93 said:
The tap to pay does not work unless you trick the build prop.
Sent from my SCH-I545 using Tapatalk 4
Click to expand...
Click to collapse
I was just looking at their thread for the new version and it doesn't even seem like you need to have xposed framework at all. Looks like all the flashable zip does is intall the Wallet.apk so you don't have to change your build.prop to get it from the market. Although it looks like people are having a tough time using the new version compared to the old version.
bb12489 said:
I was just looking at their thread for the new version and it doesn't even seem like you need to have xposed framework at all. Looks like all the flashable zip does is intall the Wallet.apk so you don't have to change your build.prop to get it from the market. Although it looks like people are having a tough time using the new version compared to the old version.
Click to expand...
Click to collapse
It's funny I installed the old wallet then a couple days later the new one came out and I wasn't going to switch it all over again. I'm running the hyperdrive rom and some people are hit and miss with tap to pay to work. I figured I would wait till someone gets it all hashed out and working flawlessly. There aren't very many pay pass places in Eugene Or. The only place I know of is toys R us.
Sent from my SCH-I545 using Tapatalk 4
Related
Has anybody tried to activate Samsung Dive on their Note? I created the Samsung account but I don't see any options to activate the remote control settings on the note, even though it says in Samsung's site that the options will be enabled automatically when the Samsung account is created.
http://www.samsungdive.com/DiveMain.do
I got to the samsung site logged in, but then to add my phone, nothing happens.
It will not let me register my phone.
StarLog said:
I got to the samsung site logged in, but then to add my phone, nothing happens.
It will not let me register my phone.
Click to expand...
Click to collapse
Same thing happens to me. The site will not let me register my phone and I cant find the remote settings anywhere on the phone...
NOTE STUFF
Supported Note info
Samsung Dive User Guide
Use Cerberus - https://market.android.com/details?id=com.lsdroid.cerberus&hl=en
Has some insanely cool features.
StarLog said:
NOTE STUFF
Supported Note info
Samsung Dive User Guide
Click to expand...
Click to collapse
Already read all that before posting. My Phone just doesn't have the "Find my Phone" under "Location and Security"...
The feature has been removed from the AT&T version just like SGS2 did.
foxbat121 said:
The feature has been removed from the AT&T version just like SGS2 did.
Click to expand...
Click to collapse
Nice, thanks!
ZaidSenall said:
Nice, thanks!
Click to expand...
Click to collapse
Don't thank me. Thank AT&T for it
To be honest, the feature doesn't work very well even for non-AT&T versions. I have a Galaxy Tab 10.1 wi-fi and I was never able to let DIVE find my tab at all. Another crapy buggy feature from Samsung.
foxbat121 said:
Don't thank me. Thank AT&T for it
To be honest, the feature doesn't work very well even for non-AT&T versions. I have a Galaxy Tab 10.1 wi-fi and I was never able to let DIVE find my tab at all. Another crapy buggy feature from Samsung.
Click to expand...
Click to collapse
That's what i meant, Thanks At&t...
I came from a windows phone, and microsoft has that feature enabled for all their phones just by going to windowsphone.com and signing in with your live id. and before that, on windows mobile, i had my phone setup with creeper and it got stolen and i wiped it remotely but before i wiped it, i sent it a couple texts telling the thief where he was and that if he didn't return it i was going to call the police. the next morning the phone was sitting on my desk...
I used that Windows phone feature to locate/spy on my kids iDevices have the similar functionality. Not sure why Google left this one out?
DIVE was left out of the i-717 because AT&T offers their own called Mobile Locate and surprise...they charge for it! It is an add-on to the phone insurance.
My Samsung Galaxy Note™ is smarter than your Honor Student.
Well Lookout could be an alternative.
Sent from my SAMSUNG-SGH-I717 using xda premium
Really, no love Cerberus?
You can snap pictures from the website control panel with the phone's front camera and have them emailed to you, or record audio from the mic and send that.
You can make it so any SIM put in the phone that isn't the current SIM will only call a phone number you specify.
You can wipe whatever you want from remotely and track the exact location of your phone at all times.
It is AMAZING!
jpeg42 said:
Really, no love Cerberus?
You can snap pictures from the website control panel with the phone's front camera and have them emailed to you, or record audio from the mic and send that.
You can make it so any SIM put in the phone that isn't the current SIM will only call a phone number you specify.
You can wipe whatever you want from remotely and track the exact location of your phone at all times.
It is AMAZING!
Click to expand...
Click to collapse
i looked at it but for a reason i can't recall, i went with the "Where's My Droid" app instead.
wish i read this thread earlier, woulda saved me from registering at Samsung's lame Dive site...
I saw Cerberus on Twit.tv and think it is a great option. I'd love to know if any of you Note folks tried it. I don't have a Note... yet.
Cerberus is one of the first things I install on a new phone. If you are rooted you can install it into the rom and it will survive factory reset. It blows away anything else out there right now. You can record audio, video, have it call a number, take a picture, snap a screenshot. Remote lock / wipe. It is just amazing.
Sent from my SAMSUNG-SGH-I717 using XDA App
btothec said:
Cerberus is one of the first things I install on a new phone. If you are rooted you can install it into the rom and it will survive factory reset. It blows away anything else out there right now. You can record audio, video, have it call a number, take a picture, snap a screenshot. Remote lock / wipe. It is just amazing.
Sent from my SAMSUNG-SGH-I717 using XDA App
Click to expand...
Click to collapse
It's not free, though, and Samsung Dive is free for the lucky ones that can run it. I wonder if there is a way to force it on the phone (mine is rooted)
ZaidSenall said:
It's not free, though, and Samsung Dive is free for the lucky ones that can run it. I wonder if there is a way to force it on the phone (mine is rooted)
Click to expand...
Click to collapse
Lifetime license is less than 5 bucks
Sent from my SAMSUNG-SGH-I717 using XDA App
im testing out the free trial on Cerberus now, where are the photos and video stored?
Search is disabled for some reason so I apologize if this came this already came up:
I did all the steps to get Google Wallet working on my HTC One and it stays suck on the 5 minute set up. Did anybody else have this issue and were you able to fix it? I'm afraid to think AT&T screwed me again by removing the security files to allow Google Wallet to work.
HTC didn't include the libs needed to get wallet to work. I wonder if they're present in the development edition.
gunnyman said:
HTC didn't include the libs needed to get wallet to work. I wonder if they're present in the development edition.
Click to expand...
Click to collapse
We need the libs from the sprint version. That is how it was able to work on the S3.
Sent from my HTC One using Tapatalk 2
Has anyone seen a working wallet for our device?
Sent from my HTC One using Tapatalk 4 Beta
It's being worked on but afaik there hasn't been a proven method yet.
Sent from my HTC One using xda premium
Bladerunner1825us said:
It's being worked on but afaik there hasn't been a proven method yet.
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Not yet. If they do get it working, it'll be through an international ROM. AT&T has refused to support it so far.
Yeah, I've tried the modaco toolkit version(from the youtube vid I found) and that person got it working, but it is on an Sprint HTC One.
Guess I'll wait and see what happens.
I found a verion that works on sprint, but on my phone (running cognition 0.6 - based upon dev rom) it still says "Device/carrier not supported"
I'm sure its based upon some carrier flag perhaps... not sure why/how at&t can actually keep google from releasing it... especially on a "deveoper" version of the phone...
centex99 said:
I found a verion that works on sprint, but on my phone (running cognition 0.6 - based upon dev rom) it still says "Device/carrier not supported"
I'm sure its based upon some carrier flag perhaps... not sure why/how at&t can actually keep google from releasing it... especially on a "deveoper" version of the phone...
Click to expand...
Click to collapse
Sprint is the only us carrier that can use wallet. Speaking from previous phones on their network. If I'm not mistaken the s3 on sprint and nexus all use wallet straight from the market.
Sent from my HTC One using Tapatalk 2
godfirst said:
Sprint is the only us carrier that can use wallet. Speaking from previous phones on their network. If I'm not mistaken the s3 on sprint and nexus all use wallet straight from the market.
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
Yeah but they(devs here) found a way to use the Sprint version of the phones to bypass the carrier locks. I had GW on my AT&T S3 via wallet installer. Requires root, but it was a simple build.prop edit to get it working.
nest75068 said:
Yeah but they(devs here) found a way to use the Sprint version of the phones to bypass the carrier locks. I had GW on my AT&T S3 via wallet installer. Requires root, but it was a simple build.prop edit to get it working.
Click to expand...
Click to collapse
Yeah I had it on mine as well.
Sent from my HTC One using Tapatalk 4 Beta
Well, looking at the build.prop I have, am running Cognition 0.6 rom... it has a line of ro.product.brand=cingular_us...
I wonder if we could just change that line to the sprint version (maybe sprint_us, not sure exactly what it's value is but we should be able to find out), reboot the phone, setup wallet, set the line back, reboot and have working wallet.... anyone want to try it?
centex99 said:
Well, looking at the build.prop I have, am running Cognition 0.6 rom... it has a line of ro.product.brand=cingular_us...
I wonder if we could just change that line to the sprint version (maybe sprint_us, not sure exactly what it's value is but we should be able to find out), reboot the phone, setup wallet, set the line back, reboot and have working wallet.... anyone want to try it?
Click to expand...
Click to collapse
I remember that I could get Google Wallet to work on my Galaxy SIII by changing the phone name in the build.prop to HTC RAIDER and it would work.
I can't seem to find the thread that detailed how to do it, but I bet with a rooted ROM you could use the same hack and install via the APK
giving it a shot
There were two lines I think in the build.prop related to at&t... may want to compare build.props against a sprint phone.... let me know how it goes...
veritas2884 said:
I remember that I could get Google Wallet to work on my Galaxy SIII by changing the phone name in the build.prop to HTC RAIDER and it would work.
I can't seem to find the thread that detailed how to do it, but I bet with a rooted ROM you could use the same hack and install via the APK
Click to expand...
Click to collapse
Go to this thread
http://forum.xda-developers.com/showthread.php?t=2245776
I got in touch with the dev who got wallet working on the s3, he is working on it for the s4 and the One as well.
I've tried all the build prop edits, along with Modaco toolkit using Xposed framework and removing carrier/root checks. Still nothing. Leads me to believe we need some files from the Sprint HTC One like the S3 needed to get this working.
nest75068 said:
Go to this thread
http://forum.xda-developers.com/showthread.php?t=2245776
I got in touch with the dev who got wallet working on the s3, he is working on it for the s4 and the One as well.
I've tried all the build prop edits, along with Modaco toolkit using Xposed framework and removing carrier/root checks. Still nothing. Leads me to believe we need some files from the Sprint HTC One like the S3 needed to get this working.
Click to expand...
Click to collapse
I've pulled all the nfc libs/files from the sprint ROM as per the other workarounds that have gotten google wallet working and flashed them, changed build.prop, installed all the modded wallet apks i could find as well as the play store version, but it never gets past the first screen (logcat showed a No Secure Element Error). I've recently, however, been told that the Secure Element is located in the micro sim, which currently i don't have (i'm using a cut mini sim, so ISIS doesn't even work. Can anyone check to see if ISIS will install for them?). Here is the flashable package iwth the nfc libs/files from the Sprint ROM, if anyone would like to try to see if it will utilize the secure element in the sim (it will still require the other workarounds, I'm guessing).
Keep in mind this is from the original ROM, before their update yesterday (or two days ago) that enabled wallet. Once i find a dump from the update, i'll redo the flashable with the most current files.. ah i see there's one posted, downloading now... will have a new flashable shortly.. i'm also gonna check out the new build.prop to see what, if any, changes happened there that might be necessary.
Edit: removed this one. New one will be up in about 15 minutes
homeslice976 said:
I've pulled all the nfc libs/files from the sprint ROM as per the other workarounds that have gotten google wallet working and flashed them, changed build.prop, installed all the modded wallet apks i could find as well as the play store version, but it never gets past the first screen (logcat showed a No Secure Element Error). I've recently, however, been told that the Secure Element is located in the micro sim, which currently i don't have (i'm using a cut mini sim, so ISIS doesn't even work. Can anyone check to see if ISIS will install for them?). Here is the flashable package iwth the nfc libs/files from the Sprint ROM, if anyone would like to try to see if it will utilize the secure element in the sim (it will still require the other workarounds, I'm guessing).
Keep in mind this is from the original ROM, before their update yesterday (or two days ago) that enabled wallet. Once i find a dump from the update, i'll redo the flashable with the most current files.. ah i see there's one posted, downloading now... will have a new flashable shortly.. i'm also gonna check out the new build.prop to see what, if any, changes happened there that might be necessary.
Click to expand...
Click to collapse
Once you get the new package I'll try flashing and see what happens.
I can install Isis from the Play store, but it won't let me initialize cause I'm rooted. Also not sure if my micro sim has a secure element or not(since I am not located in one of the test markets).
nest75068 said:
Once you get the new package I'll try flashing and see what happens.
I can install Isis from the Play store, but it won't let me initialize cause I'm rooted. Also not sure if my micro sim has a secure element or not(since I am not located in one of the test markets).
Click to expand...
Click to collapse
I can't even install ISIS..tells me my device is unsupported. So since you can, my guess is you do have a secure element. I was told by a chat representative yesterday (I know, taken with a grain of salt), that all of ATT's micro SD's have a secure element.
10 minutes left on the download, then some comparison, then I'll have a flashable
homeslice976 said:
I can't even install ISIS..tells me my device is unsupported. So since you can, my guess is you do have a secure element. I was told by a chat representative yesterday (I know, taken with a grain of salt), that all of ATT's micro SD's have a secure element.
10 minutes left on the download, then some comparison, then I'll have a flashable
Click to expand...
Click to collapse
Ok, I'm making a Nandroid right now, I'm going to try the flashable zip you already included to see if that works.
I'm going to update my build prop to one of the following and see if that bypasses it
ro.product.model=Galaxy Nexus
ro.product.name=yakju
ro.product.device=maguro
ro.product.model=htc_jewel
ro.product.name=htc_jewel
ro.product.device=htc_jewel
Both of those worked for the S3
nest75068 said:
Ok, I'm making a Nandroid right now, I'm going to try the flashable zip you already included to see if that works.
I'm going to update my build prop to one of the following and see if that bypasses it
ro.product.model=Galaxy Nexus
ro.product.name=yakju
ro.product.device=maguro
ro.product.model=htc_jewel
ro.product.name=htc_jewel
ro.product.device=htc_jewel
Both of those worked for the S3
Click to expand...
Click to collapse
yea i tried both of those, as well as M7WLS, m7wls, m7wls (as in Sprint's build.prop), and none worked - but again, I think it's a different issue for me
ok. i forgot that flashable had an issue. after you flash, nfc probably will be greyed out and won't turn on - go to /system/lib/hw/ and change nfc.m7wls.so to nfc.m7.so and reboot
or just wait for the new one and I'll have that issue fixed...
a
homeslice976 said:
yea i tried both of those, as well as M7WLS, m7wls, m7wls (as in Sprint's build.prop), and none worked - but again, I think it's a different issue for me
ok. i forgot that flashable had an issue. after you flash, nfc probably will be greyed out and won't turn on - go to /system/lib/hw/ and change nfc.m7wls.so to nfc.m7.so and reboot
or just wait for the new one and I'll have that issue fixed...
a
Click to expand...
Click to collapse
Already flashed it, I'll update the settings. Going through Android is upgrading right now
Wallet installed, and it is sitting at the setting up wallet screen(where it always does)
So looks like those lib files are a no go.
nest75068 said:
Already flashed it, I'll update the settings. Going through Android is upgrading right now
Click to expand...
Click to collapse
here's a flashable package with the libs/app/files from yesterday's Sprint update. build.prop changes in the update appeared to be negligible (just changes in version numbers, etc).
Not sure if anyone else saw this but tap to pay is unlocked on stock 4.4.2 rom!
Sent from my SCH-I545 using Tapatalk
They changed the way that the NFC secure element works. Essentially, its even more secure now. And they gave a big middle finger to Verizon/ATT and Isis.
Sent from my SCH-I545 using Tapatalk
I'm confused now. Does it work with root now?
Hell yeah
Sent from my SCH-I545 using XDA Premium 4 mobile app
jcwilliams said:
I'm confused now. Does it work with root now?
Click to expand...
Click to collapse
I works even without root!
To anyone using this...do you trust it? Any problems or safety issues to watch out for? Haven't added my bank account yet just not sure I trust google yet...
Poofster said:
To anyone using this...do you trust it? Any problems or safety issues to watch out for? Haven't added my bank account yet just not sure I trust google yet...
Click to expand...
Click to collapse
I have my info in mine. But can't use it bc of root but no problems with my cards being on there
jcwilliams said:
I have my info in mine. But can't use it bc of root but no problems with my cards being on there
Click to expand...
Click to collapse
I see you can add credit debit cards...can they be used at nfc places or do they only work for online purchases? I'm new to this but am interested in using this...I'm not rooted running kitkat so I should be ok
Poofster said:
I see you can add credit debit cards...can they be used at nfc places or do they only work for online purchases? I'm new to this but am interested in using this...I'm not rooted running kitkat so I should be ok
Click to expand...
Click to collapse
Yes you can set a default card that gets used when you tap to pay.
Thanks ...last question cause their site isn't very helpful. ..lol...do I need to enter a bank account or is a credit card enough? Thanks again
Poofster said:
Thanks ...last question cause their site isn't very helpful. ..lol...do I need to enter a bank account or is a credit card enough? Thanks again
Click to expand...
Click to collapse
Sorry didn't see this post. I'm not sure on the bank account. I don't think you need to since you'll be using a card. But the back account is there in case you want to add funds from bank to Google wallet card.
Poofster said:
Thanks ...last question cause their site isn't very helpful. ..lol...do I need to enter a bank account or is a credit card enough? Thanks again
Click to expand...
Click to collapse
I would never authorize on-line transactions directly from an account. Credit cards at least have limits/protections.
Bank account is not required. All I use is one of my cards. Works like a champ.
Has anyone been able to get tap to pay working on 4.4.2? I'm on Surge's 4.4.2 rom and tap to pay sets up immediately, which means it didn't completely setup. Proper setup usually takes a few minutes. I've tried it at a store and as expected it didn't didn't even register with the payment terminal. I was able to use tap to pay on my old s3 prior to April 14th and was hopeful I could use it on the s4 now that is has official kit kat.
I've been using it on the 4.4.2 release for weeks. Every now and then the first tap won't work but it always does the second time. It set up pretty much immediately for me compared to the old way NFC worked.
storm81456 said:
I've been using it on the 4.4.2 release for weeks. Every now and then the first tap won't work but it always does the second time. It set up pretty much immediately for me compared to the old way NFC worked.
Click to expand...
Click to collapse
I guess that means I'm likely experiencing operator error. I went into the transaction assuming that it wasn't going to work because of the different experience with setup. Then when the first tap didn't register, I quickly used the actual credit card.
When the first tap doesn't work for you, does it even register a transaction attempt? My phone didn't even attempt to start a transaction.
It makes the customary wallet sound and then has that reader/transaction may not have been successful message.
I'm about to buy the VZW G3. This might be a dumb question, but can anyone confirm whether or not tap to pay in Google Wallet works on the device?
I have it installed and activated TTP but haven't tried it out yet. Hopefully today I'll have chance to test it.
sentry_mode_activated said:
I'm about to buy the VZW G3. This might be a dumb question, but can anyone confirm whether or not tap to pay in Google Wallet works on the device?
Click to expand...
Click to collapse
sentry_mode_activated said:
I'm about to buy the VZW G3. This might be a dumb question, but can anyone confirm whether or not tap to pay in Google Wallet works on the device?
Click to expand...
Click to collapse
Yes works fine.
Worked like a charm at Walgreen's.
Sent from my VS985 4G using XDA Free mobile app
Worked flawlessly at Whole Foods. The cashier looked at me like i was crazy and said "How did you do that?"
For future reference, any phone/device with stock kk + nfc, Google wallet t&p will work. It can no longer be blocked by a manufacturer or carrier.
tried it out once but didn't work (app and cash register gave an error), probably just a fluke
Thanks for the responses guys. Yeah I wasn't sure because I came from a Galaxy S3 with CM 11 and there was a point where it just stopped working no matter what I threw at it. Worked fine for several months before that too. Wasn't sure if it was due to a restriction on the model, carrier or who knows what. About to try it out myself with the G3 today
sentry_mode_activated said:
Thanks for the responses guys. Yeah I wasn't sure because I came from a Galaxy S3 with CM 11 and there was a point where it just stopped working no matter what I threw at it. Worked fine for several months before that too. Wasn't sure if it was due to a restriction on the model, carrier or who knows what. About to try it out myself with the G3 today
Click to expand...
Click to collapse
Working great on my rooted G3.
Worked fine on my Galaxy S4 until Google removed support for everything that was not on KitKat.
So if at any point you were not on KitKat, support would have gone away.
I forgot the cutoff date for Wallet support for pre-KitKat releases.
tech_head said:
Working great on my rooted G3.
Worked fine on my Galaxy S4 until Google removed support for everything that was not on KitKat.
So if at any point you were not on KitKat, support would have gone away.
I forgot the cutoff date for Wallet support for pre-KitKat releases.
Click to expand...
Click to collapse
What was weird was that I was running the latest version of KitKat for quite some time and TTP never seemed to work. Wallet would show it as available but it never actually worked at terminals. Not sure why it stopped working, but I do know that other people had the same problem with the GS3. Just glad to be done with whatever incompatibility or blocking that was and on to a much better phone :good:
Probably unnecessary for me to post but figured I'd also add in that I just used Tap to Pay at McDonald's and it worked beautifully!!!
Sent from my VS985 4G using Tapatalk 2
Works for me. The cashier did not even talk to me through an entire transaction but when I used tap and pay she said...the was really cool.