Related
Greetings,
I've recently switched over from the Samsung galaxy s3 to the m8. I have my phone rooted, but currently on the stock rom. I have Google wallet installed on my phone, and tried to us the tap and pay function at McDonalds. I was unable to get the NFC function to work. I know the store terminal works because I used my stock nexus 7 (not rooted) a few months ago to get some coffee there.
I had the same issue on my s3, but I was running cyanogenmod on the phone, and I thought that was the problem. Now I'm wondering if it's having root access. Anyone else having problems with tap to pay on their rooted phone?
Maybe the store terminal broke since... A few months cab do that try a different store
Sent from my 831C using XDA Free mobile app
I'm having the same issue. For me, the problem started when I switched from a Sprint-specific ROM to Viper ROM (intl base). After 2 minutes of bashing my phone against the terminal at McDonald's, it did finally work. But it is not working instantly like it used to, and it acts like nothing is happening. I know it's not McDonald's terminal because it happens at another McDonald's and Walgreens where previously it was working fine. Tapping my phone to another NFC phone works so NFC itself is working.
I don't really feel like going back to a different ROM over this, but it is annoying.
Only place I have has issues is one checkout lane at meijer. Felt like pretty stupid last night since I left my wallet at home. Cancelled my order, went to a different Lane and it worked fine. So for me at least it's not an issue with the phone
Just wondering if anyone else has experienced this. I still cannot get tap and pay to work. The light on the NFC reader at walgreens will blink once when I tap it, but there is zero activity on the phone even though google wallet says "tap and pay ready". Doesn't work at McDonalds either. Friend can use his Note 3 just fine with google wallet in those locations so I know it's not the NFC reader.
I have tried RUU back to the latest stock ROM, no dice. I re-locked my bootloader and RUU'd back to the oldest available HK ROM and did all the OTAs, still same exact issue. I have not been restoring from backup either so my phone is basically 100% stock now non-rooted. The only difference is it's S-OFF, but I've been S-OFF since June and my tap and pay was working until early September so I don't think that's it. I can use NFC to share things with other phones so I know my NFC is fine.
I'm completely stumped.
I think the nfc antennas on this phone might be too weak, I have to get my phone JUST right to read nfc tags...
Sent from my HTC One_M8 using XDA Free mobile app
I don't think that's the issue I'm having. I bought the phoen right when it came out, and I used NFC just fine at McDonalds and Walgreens without having to fiddle with it. It just worked. Now it doesn't work at all. I don't know what happened, the last time I was able to get it working was early September. Not sure if there was a wallet update or something that broke it. NFC communication to other phones still works fine though.
A few stores in my area have been working fine until recently. I was starting to think they were disabling the NFC on purpose. As it turns out, quite a few retailers really are purposely disabling the NFC portion of their credit cards terminals. Found an article about it yesterday.
om4 said:
A few stores in my area have been working fine until recently. I was starting to think they were disabling the NFC on purpose. As it turns out, quite a few retailers really are purposely disabling the NFC portion of their credit cards terminals. Found an article about it yesterday.
Click to expand...
Click to collapse
Yep, Best Buy and CVS are the big ones who have disabled it. However, Walgreens and McDonalds have not. They still accept NFC payments via Google Wallet, and it still works on my friend's Note 3 as of yesterday.
Just wanted to say I've had the same problem. It seems to work when it wants to. NFC itself works fine. I feel like it stopped working after the WiFi calling update... If someone's able to go to the previous update and test it would be awesome.
Figures if it affects Apple its all over the news.
http://www.theverge.com/2014/10/25/7069863/retailers-are-disabling-nfc-readers-to-shut-out-apple-pay
My wallet hasn't worked for me the past few times I've tried (at Walgreens and my work vending machine). I'm guessing it has something to do with my ROM (Viper) or a xposed mod I have running (though I don't have much and nothing related to Wallet directly).
After the 4.4.4 update and also removing all my cards from Wallet and re-adding them, tap-to-pay is working for me now.
kwolf said:
After the 4.4.4 update and also removing all my cards from Wallet and re-adding them, tap-to-pay is working for me now.
Click to expand...
Click to collapse
I am on the 4.4.4 HK firmware but not on the 4.4.4 rom (still on Viper which hasn't updated yet). I removed my cards, wiped app data, uninstalled/reinstalled wallet, and then put my cards back in and still when I put my phone up to the reader wallet doesn't open. The error I get on one machine is "Unable to read card" and the reader just beeps on a different machine. I do have SuperCID on my phone in order to flash HK ROMs/Firmware. Don't think that should matter since I've had that on for months well before Wallet quit working.
I'll wait until Viper updates to 4.4.4 or if they take more than a few days I might try a different stock-ish rom.
henderjr said:
I am on the 4.4.4 HK firmware but not on the 4.4.4 rom (still on Viper which hasn't updated yet). I removed my cards, wiped app data, uninstalled/reinstalled wallet, and then put my cards back in and still when I put my phone up to the reader wallet doesn't open. The error I get on one machine is "Unable to read card" and the reader just beeps on a different machine. I do have SuperCID on my phone in order to flash HK ROMs/Firmware. Don't think that should matter since I've had that on for months well before Wallet quit working.
I'll wait until Viper updates to 4.4.4 or if they take more than a few days I might try a different stock-ish rom.
Click to expand...
Click to collapse
Hmm, when I had the problem the card reader barely responded at all (a light blinked and that was it).
If you open the wallet app manually, does it do anything when you tap? Or is the phone acting like nothing is happening at all?
kwolf said:
Hmm, when I had the problem the card reader barely responded at all (a light blinked and that was it).
If you open the wallet app manually, does it do anything when you tap? Or is the phone acting like nothing is happening at all?
Click to expand...
Click to collapse
Wallet doesn't react at all if I have it open or not when "tapping" my phone. I think the phone beeps too but can't remember now. I know my nfc works fine as I use a nfc tag every morning when I get to work to put it on silent.
My m8 does the same thing... I figured it was running Viper as well, but I just flashed the newest firmware and the stock rom... Same story. I hold my phone up to the NFC terminal, and the lights stop blinking on the terminal, but nothing happens on my phone. When I use my S4, the terminal beeps, my phone vibrates and it just works. I just tried deleting all my cards and trying again... No dice. I just went through a chat with HTC, and they're escalating the issue, who knows, maybe it's bad hardware. (I've never had NFC working)
Update: htc called to confirm my information and to say the turnaround time is 7-10 days. They mentioned that it's rarely a software problem if you're not getting an error. I'm not. I'm assuming that once they research some more, they'll just end up replacing my phone. We'll see.
Sent from my 831C using Tapatalk
After upgrading Viper to 4.4.4, removing all cards, removing all old devices from here (https://wallet.google.com/manage/#devices:), uninstalling/installing wallet, and adding cards back in and it now works. I don't know which one of those fixed it as I did them all before trying.
Thanks henderjr! I tried everything you had posted there, but still didn't have any luck. (holy crap, I had a ton of devices listed... One for each ROM installed in the past few years.) Hope your information helps someone else get their device working!
i have noticed that after setting up the remote when i reboot my device the remote stops working. does anyone else have same issue ??
japanpatel said:
i have noticed that after setting up the remote when i reboot my device the remote stops working. does anyone else have same issue ??
Click to expand...
Click to collapse
I've not had that issue. It's working great for me. I had an M7 back in the day and this blows the HTC remote away.
Sent from my VZW Galaxy S6
RyanTX said:
I've not had that issue. It's working great for me. I had an M7 back in the day and this blows the HTC remote away.
Sent from my VZW Galaxy S6
Click to expand...
Click to collapse
I wish I could agree but since IR blasters on HTC phones can learn I would take that over the S6's anyday.
I'm having the same issue.. while setting the remote control.. the tv doesn't turn on.. stil don't have any solution for this
I didn't have any issues with FC's but I did notice that I would close the app and the icon would still be in the status bar indicating that it is running. I wouldn't even be home and it would still be running.
Sent from my SAMSUNG-SM-G920A using XDA Free mobile app
the remote is working great now after the recent update.
can someone please share the last version of smart remote apk file?
i can't download it with my phone
mine works flawlessly. Toshiba TV
What i like about it that it has a widget unlike the htc one.
There is no my country on the list, I dont know what to do... Croatia Can I put random country?
which country do i use for south africa dstv
It never worked. My wife has lg g4 and worked at the first attempt. All i can get from this is to turn on and off my devices and that is it.
Not working for me also on latest version 8.6.2. When open it I choose the country & satellite after that it keeps spinning please wait. But I try to clear cache & data & uninstall updates it was working perfect. Can someone please clarify what's happening here????
Hi guys.
I have installed Magisk on my Xiaomi Mi6 and everything is OK, but...
The Magisk hide working fine with every app like a Google pay or my bank app, but is only one app which recognise root on the phone still. Its My EE, the app for managing the mobile provider EE account.
Any idea what happened?
Mine works absolutely fine with it being hidden by Magisk Hide. I have the option to unlock using fingerprints
Have you tried wiping it's data in case its remembered you had root?
Same for me, it was working fine until this morning. I tried clearing the My EE app data but still the same.
Same here. Working fine until the 1st feb, then all of a sudden the myee app is unhappy with my OS status.
If you hide magisk manger in magisk settings you should be able to log in.
Many thanks. That seems to have done the trick. I did.not realise that MM had that functionality. Thanks for your time!
I only discovered it this morning too
Anyone else experienced problem with Google Pay after update?
It worked extremely well for me up until the update, then all of the sudden it doesn't work any more.
I checked the settings inside Google Pay, but all seems well. Card is registered and everything.
When holding my phone up to the terminal there is no reaction from the phone at all.
What can I do to fix this?
I have exactly the same, but with my normal banking app. It can also do payments via NFC, but when I hold it up to a terminal nothing happens like you said.
I'm now factory resetting my phone to see if that helps, I'll let you know!
Gfhoihoi72 said:
I have exactly the same, but with my normal banking app. It can also do payments via NFC, but when I hold it up to a terminal nothing happens like you said.
I'm now factory resetting my phone to see if that helps, I'll let you know!
Click to expand...
Click to collapse
Thanks! Looking forward to your feedback if this works or not.
TordFuglstad said:
Thanks! Looking forward to your feedback if this works or not.
Click to expand...
Click to collapse
Nope... Unfortunately not. Maybe I'll just downgrade to Android 9 and wait until a new patch for Android 10 comes out where they fix this.
No problems here, working as before
EnormoDerClown said:
No problems here, working as before
Click to expand...
Click to collapse
What firmware version are you on?
I've downgraded to Android 9.1 and the mobile payment is working perfectly again, so it's definitely an issue with Android 10. So if you really want to use it, you can downgrade for now. Otherwise just wait for the next Android update and hope that it gets fixed.
Same here in France, Google Pay says Phone moved too fast.
Can pay with one other bank's app, but not the other one's. (both Georgian banks)
They did warn in changelog that some banking apps are not working due to their compatibility issues with Android 10, though
giosal said:
Same here in France, Google Pay says Phone moved too fast.
Can pay with one other bank's app, but not the other one's. (both Georgian banks)
They did warn in changelog that some banking apps are not working due to their compatibility issues with Android 10, though
Click to expand...
Click to collapse
True, that changed the way apps can use your IMEI and this was the way most banking apps verified your phone. But my banking app should be compatible with Android 10 and it is working for some people but not for others.
Gfhoihoi72 said:
What firmware version are you on?
I've downgraded to Android 9.1 and the mobile payment is working perfectly again, so it's definitely an issue with Android 10. So if you really want to use it, you can downgrade for now. Otherwise just wait for the next Android update and hope that it gets fixed.
Click to expand...
Click to collapse
10.0.0.168. "normal" update. Not a member of the beta or anything, just normal OTA. Working exactly as on Android 9. Also tested/used with different cards/institutes in google pay. Working like a charm
Same problem here, Google Pay worked perfectly in 9.1. Now, with 10.0.0.173 there's no response when near terminal. No error messages anywhere. NFC works fine, e.g. ReadID to read the NFC chip in my passport.
The same here, but I have a mate 20 pro. After the update to Android 10 I can no longer pay with Google pay.
From Germany
Updated yesterday and works fine for me in UK
So i better stop an update i am asked to update to 173 and stay on my 168 It is working for sure on 168 for me. Used it quite often
I solved the problem on my P30 Pro. I was using a "twin SIM" card from Ice (service provider). When I switched sim cards to my main SIM, Google pay works as before. The twin SIM worked fine with Android 9. I think the problem is that the twin SIM does not have the real phone number, but some long code that the phone system somehow recognizes, but causes issues in some scenarios e.g. iMessage on iPhone which cannot verify it. That's why I had the twin SIM in my P30 Pro.
EDIT: The iMessage problem is caused by the fact that only the main SIM receives "class 0" or flash SMSs, used for iMessage's verification.
I'm having the issue with my UK region VOG-L29 that's running .173. I rarely use Google pay, so I'm not sure if it was working before the upgrade. Google Pay works fine on my Fossil Wear OS watch that's tethered to the phone. NFC also seems to work fine when connecting my camera to the phone.
Have also the problem of nfc payments (with gpay and postfinance app) not working after updating to Android 10. Full reset didn't help currently on version 10.0. 0.173 and still not working.
Huawei support doesn't know anything about this and said I should wait for app updates and/or emui update.not very helpful...
Uninstalling gpay and deleting the cards linked to it and setup everything from scratch didn't help either. Nfc hardware seems to work as I can trigger my bt connection with my nfc enabled headset.
Hopefully Huawei sorts this out quickly as it is very annoying since I used nfc payment almost every day on emui 9.1
Any solution for this problem? I also used the ohone to pay and the point is that it is a big inconvenience that there is no solution
Waiting for Huawei to fix the damn bug in their next update (hopefully). Downgrading or resetting and so on is a pain when the affected phone is your daily driver.
Been using GPay already multiple times with 10.0.173.
No problems here in germany.
Regards
Same here!
Updated yesterday to EMUI 10 and realized today that I could'nt pay at the terminal. Bad situation without credit cards
Seems like NFC does not work at all. When I try to read my credit cards with NFC Tools, there is no reaction from phone as before.
Hi Guys.
I just recently got the AA update to the 7.3 version, and suddenly the Google Podcast App is not working anymore in AA, I'm getting the message that the App is not ready or something similar, I will try to get a picture of the message and share it later...
Someone else is having the same problem? - Any workaround to fix it?
Thank you!!
So do I! Since this week.
Same, it worked the first day I had my new car but now it won't open. Other apps seem to work fine such as YouTube Music
rcklesslydriven said:
Same, it worked the first day I had my new car but now it won't open. Other apps seem to work fine such as YouTube Music
Click to expand...
Click to collapse
Yes, others apps seems to work, however today I noticed that Waze was running with a message of being offline, but my phone was getting data and working properly...
I Need to check if it's a persistent issue.
So, today it magically started to work!
Now Google podcast App is working normally in AA 7.3
Waze is working ok as well, but sometimes it marked itself as offline "no internet connection".
Andres.Navas said:
So, today it magically started to work!
Now Google podcast App is working normally in AA 7.3
Waze is working ok as well, but sometimes it marked itself as offline "no internet connection".
Click to expand...
Click to collapse
This is good news. I am having the same issue with the app not working so hopefully it will be fine for my drive to work. I've been using Spotify which I don't like because I can't reorder my podcast lists.
Andres.Navas said:
So, today it magically started to work!
Now Google podcast App is working normally in AA 7.3
Waze is working ok as well, but sometimes it marked itself as offline "no internet connection".
Click to expand...
Click to collapse
It seems to be ok now. I didn't find a good alternative, so I am relieved.