[Q] Google wallet? - AT&T HTC One (M7)

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).

Related

WM8850-Mid Contacts.apk not present

I decided to get my daughter a cheap WM8850-Mid based tablet for christmas this year. It works well, have even gotten it rooted. But for the life of me I can't get the Contacts.apk files I have found to install. I have even pulled them from the Eclipse emulator and gotten no luck. I know I need to replace the contactsprovider.apk as well but can't get it removed to replace with a matching version of contacts. It is running ICS 4.0.3 rooted as I said earlier. I've checked permissions when moving the new contacts.apk to /system/app and verified the are rw-r--r--. The error Application Not Installed is all I get. I am stumped at this point. Any help out there would be appreciated.
Puff3r said:
I decided to get my daughter a cheap WM8850-Mid based tablet for christmas this year. It works well, have even gotten it rooted. But for the life of me I can't get the Contacts.apk files I have found to install. I have even pulled them from the Eclipse emulator and gotten no luck. I know I need to replace the contactsprovider.apk as well but can't get it removed to replace with a matching version of contacts. It is running ICS 4.0.3 rooted as I said earlier. I've checked permissions when moving the new contacts.apk to /system/app and verified the are rw-r--r--. The error Application Not Installed is all I get. I am stumped at this point. Any help out there would be appreciated.
Click to expand...
Click to collapse
You cannot get it because it is a tablet, not a phone
Ilyes123 said:
You cannot get it because it is a tablet, not a phone
Click to expand...
Click to collapse
In that case, why do Samsung's Galaxy Tab series have phone functionality too? Anyway, contacts don't involve only phone numbers, why shouldn't you have contacts on a tablet for email addresses and other info?
Sent from my Desire HD using xda premium
sashank said:
In that case, why do Samsung's Galaxy Tab series have phone functionality too? Anyway, contacts don't involve only phone numbers, why shouldn't you have contacts on a tablet for email addresses and other info?
Sent from my Desire HD using xda premium
Click to expand...
Click to collapse
Only in some countries dose it have the phone option. It is not available in every version of the tab.
Batcom2
zelendel said:
Only in some countries dose it have the phone option. It is not available in every version of the tab.
Batcom2
Click to expand...
Click to collapse
Oh, ok. I wasn't aware of that.
Sent from my Desire HD using xda premium
Me either until my boss came back from Korea with a version that had it while my US version didn't. That's when I started to pay real close attention and almost completely stopped buying all US based devices
Batcom2
I completely agree with you. I don't have a clue why the US ends up with weird variants of devices so often, rather than have the regular international variants. It's so convoluted that there are so many carrier variants, and then there are missing features, and the hardware is different too (like One X and Galaxy S3). It's just too confusing to keep track of all that. The hardware difference is understandable, but the boatload of carrier variants with their own crappy update policies, and especially missing features are pretty ridiculous. Something really needs to be done about that as it's turning into a real mess. At least that's what I feel, because here in my country there's only one variant of a phone which works with any carrier, really plain and simple. No need to develop different ROMs for 5-6 variants of the same device lol.

One can't link to HTC Media Link without turning on hotspot

I can link my EVO 4G LTE to HTC media link HD (got it for free from pre-ordering htc one). However, HTC ONE wouldn't connect to it without turning on the hotspot which I don't have. I was wondering if there's a way to fix this? Has anyone successfully link htc one to the media link hd?
libai8268 said:
I can link my EVO 4G LTE to HTC media link HD (got it for free from pre-ordering htc one). However, HTC ONE wouldn't connect to it without turning on the hotspot which I don't have. I was wondering if there's a way to fix this? Has anyone successfully link htc one to the media link hd?
Click to expand...
Click to collapse
What is your Rom version?
Bump.
I have exact same issue.
Can't figure it out.
I really hope AT&T didn't rig it so we have to get Hotspot through them.
libai8268 said:
I can link my EVO 4G LTE to HTC media link HD (got it for free from pre-ordering htc one). However, HTC ONE wouldn't connect to it without turning on the hotspot which I don't have. I was wondering if there's a way to fix this? Has anyone successfully link htc one to the media link hd?
Click to expand...
Click to collapse
Ditto
Same issue - can't get it to work... and I'm a computer guy! haha.
Called ATT - they were obviously clueless and at first I needed to add hotspot, after refusing they transferred me to HTC. Setup a ticket with them. I'll get back with info once they contact me.
I suspect it's something to do with ATT's customization, surprise surprise.
Same issue - HTC One "2013 M7" at&t
I got it to work by tuning on airplane mode then tuning wifi back on. But once I turn airplane mode off it no longer works.
cobbcobbdavid said:
What is your Rom version?
Click to expand...
Click to collapse
Not sure how to answer your question. Mine is stock. Android 4.1.2 HTC Sense 5.0. Is that what you are asking?
libai8268 said:
Not sure how to answer your question. Mine is stock. Android 4.1.2 HTC Sense 5.0. Is that what you are asking?
Click to expand...
Click to collapse
It should start with 1.xx.x.x
Yup I had this problem too. I'd try to connect and that damn message would cancel out anything I did with it. I tried freezing everything AT&T related through Titanium, but that didn't fix it, so it's part of the ROM.
I flashed a ROM from the international forums (Renovate 1.0) and now I'm able to connect just fine though!
ErikWithNoC said:
Yup I had this problem too. I'd try to connect and that damn message would cancel out anything I did with it. I tried freezing everything AT&T related through Titanium, but that didn't fix it, so it's part of the ROM.
I flashed a ROM from the international forums (Renovate 1.0) and now I'm able to connect just fine though!
Click to expand...
Click to collapse
How's that rom running on ATT version? Is it flawless at this moment or something doesn't work?
libai8268 said:
How's that rom running on ATT version? Is it flawless at this moment or something doesn't work?
Click to expand...
Click to collapse
As far as I can tell everything is working perfectly. All the AT&T bloatware is gone, as smooth/smoother than stock, transparent notification shade, back button as menu enabler, etc. Only thing missing is the 4G and LTE icons in the statusbar. I still have LTE I think (haven't tested), but the icons are just different, which isn't a big deal to me. I also dirty flashed this so I didn't lose any data and I haven't encountered any negative side effects.
ErikWithNoC said:
As far as I can tell everything is working perfectly. All the AT&T bloatware is gone, as smooth/smoother than stock, transparent notification shade, back button as menu enabler, etc. Only thing missing is the 4G and LTE icons in the statusbar. I still have LTE I think (haven't tested), but the icons are just different, which isn't a big deal to me. I also dirty flashed this so I didn't lose any data and I haven't encountered any negative side effects.
Click to expand...
Click to collapse
Can you link us to where you got the files and/or if there are instructions on flashing this? Also I'd like to confirm this is the HTC One, not the One X, V, S or any other phones. I'm still trying to figure out why the hell HTC would call this the "One", other than to make it impossible to search for items for this phone vs the other phones. :-\
Also have you confirmed LTE is working?
Thanks!
P.S. Still haven't heard back from HTC/ATT, but I'd just assume blast away all the bloatware from the get-go.
Same problem here. First says check the input on my TV then says I need to enable hotspot. At one point I was able to connect long enough to change the name of the media link and it even displayed what was on my phone, but then the aforementioned dialogues popup and I am forced to click ok which puts the tv back at the media links initial screen. I've tried both wireless n and g as well as my Panasonic and Vizio tvs. Version number on the media link is 5.19.103.1
njellis said:
Can you link us to where you got the files and/or if there are instructions on flashing this? Also I'd like to confirm this is the HTC One, not the One X, V, S or any other phones. I'm still trying to figure out why the hell HTC would call this the "One", other than to make it impossible to search for items for this phone vs the other phones. :-\
Also have you confirmed LTE is working?
Thanks!
P.S. Still haven't heard back from HTC/ATT, but I'd just assume blast away all the bloatware from the get-go.
Click to expand...
Click to collapse
Yeah this is the HTC One. No way in hell would I be flashing a One X ROM on my One. The ROM is here: http://forum.xda-developers.com/showthread.php?t=2202696
Standard instructions for installing a ROM. Download the file (I used v1.0, not the nightlies), place it on SD card, boot into recovery, install .zip file.
- I said no when it asked to wipe my data before installation (it's an aroma installer).
Something else I just noticed, the media link is connecting to my wireless network and it displays the SSID and full signal strength. However, as soon as I try to push content to the TV, via the 3 finger swipe up, the wifi signal strength drops to nothing and it attempts to do the whole tethering nonsense. Also, "filter multicast" is in option on my router, but it is disabled. I figure I'll just keep this going since not everyone will want to flash a new ROM just to fix this.
Ramborouser said:
Something else I just noticed, the media link is connecting to my wireless network and it displays the SSID and full signal strength. However, as soon as I try to push content to the TV, via the 3 finger swipe up, the wifi signal strength drops to nothing and it attempts to do the whole tethering nonsense. Also, "filter multicast" is in option on my router, but it is disabled. I figure I'll just keep this going since not everyone will want to flash a new ROM just to fix this.
Click to expand...
Click to collapse
I'm not sure when, but I'm sure HTC/AT&T will release an update to get this working properly. My Media Link is still 'pending shipment'.
http://forums.androidcentral.com/htc-one/269723-cant-pair-media-link.html
been talked about over at AC
Phil says his works but he has an older firmware on the media link
I've talked to both att and htc for a couple hours and both of them are casting the blame on the other.
att tried to tell me once that i needed a hot spot plan... until i explained the technology to them and said how my One X connects just fine without a sim card in it.... and they quickly take it back
eventually they both tell me there should be an update to fix it yada yada yada
Well hopefully someone will come up with a fix before then...I don't have much confidence in them patching it unless it's pretty widespread. Not many people complaining of it yet
Sent from my HTC One using xda app-developers app
i can already see AT&T behind this. Turn on hotspot, accuse users of using the hotspot, remove unlimited data plans. makes total sense to me.
Prime said:
i can already see AT&T behind this. Turn on hotspot, accuse users of using the hotspot, remove unlimited data plans. makes total sense to me.
Click to expand...
Click to collapse
Haha No doubt. *Like*
Seggzy said:
http://forums.androidcentral.com/htc-one/269723-cant-pair-media-link.html
been talked about over at AC
Phil says his works but he has an older firmware on the media link
I've talked to both att and htc for a couple hours and both of them are casting the blame on the other.
att tried to tell me once that i needed a hot spot plan... until i explained the technology to them and said how my One X connects just fine without a sim card in it.... and they quickly take it back
eventually they both tell me there should be an update to fix it yada yada yada
Click to expand...
Click to collapse
Does he have the mobile hotspot plan? As a tech writer I'd imagine he would.

Google Wallet and our AT&T versions

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

Wallet for everyone? Google, oh you.

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

[Q] Google Wallet TTP?

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.

Categories

Resources