Hi,
I've just switched to Android Pie. I've tried both POSP and TugaPower ROMs.
They both seem great except for one thing - I can't use my phone for NFC payments. All the settings seem correct. NFC itself seems to be working, but when I near my phone to the payment terminal -nothing happens.
Was anyone able to solve this problem?
Considering I use mobile payments far more than making phonecalls it's kind of a big deal to me.
Cheers
Related
Brand new OnePlus, unlocked and rooted. I am unable to get the Android share/bump to work with LG G3 or Samsung S4.
Have researched around quite a bit.
Have tried File Beam, so it will send a file (bluetooth), but will not receive.
Any known fix for this NFC bump bug? My searches have turned up nada.
Thanks.
Well, SuperBeam works, but still no direct luck with NC Beam, even OnePlus to Oneplus, seems to 'beam' the file, until at then end, says unsuccessful at the end. The NFC beam, though saying NFC, turns on the bluetooth on both OnePlus'es, and at the end of the beam, turns off the bluetooth. Just having the bluetooth on, despite the NFC Beam, does not change the success.
I like the SuperBeam success, but it is a menu selection/more user active process.
Any help to solve the simple NFC 'bump' would be appreciated.
We now have 3 OPO's. I can NFC from any of them to a G3, but not between the OPO's themselves!
Anyone with similar issues or it's working well for you?
Please, does anyone have an idea on how to fix this?
I've tried nfc beam from opo to nexus 5 and it works OK. Don't have other devices to test though. Are you on stock ROM ? Did you try a clean wipe and reflash?
Yes, have tried full reset. All 3 phone on 44s. All rooted and all other systems working well.
what is odd is that I can NFC to other non-OPO phones. Just not to another OPO. I can Bluetooth bump share between them, it's just more cumbersome, and WI-fi bump share as well.
I think the NFC bump outta work straight forward. All three phone work great with other, non-OPO phones.
Is there anyway to track down this issue?
So what seems to happen is that with the NFC bump, with no bluetooth, the OPOs, with each other, fail the transfer. If I turn on bluetooth, and then NFC transfer, I am able to transfer.
OPO to other makes of phone, no need for bluetooth.
Is this all making any common sense about how this should/does operate?
Whenever I install CM14.1 nightlies from the official CM website, I cannot get NFC mobile payment from the Dutch Bank ING working. It does work on the CM13 nightlies from the website but not in 14.1. NfC is turned on, the mobile payment app is all set. NFC does work with simple NFC tags. But nothing happens on the payment terminal when I try to pay. My screen is turned on so it should work. Does anybody experience this too? And if so, is there a solution for this?
michaeljansse said:
Whenever I install CM14.1 nightlies from the official CM website, I cannot get NFC mobile payment from the Dutch Bank ING working. It does work on the CM13 nightlies from the website but not in 14.1. NfC is turned on, the mobile payment app is all set. NFC does work with simple NFC tags. But nothing happens on the payment terminal when I try to pay. My screen is turned on so it should work. Does anybody experience this too? And if so, is there a solution for this?
Click to expand...
Click to collapse
Hi,
Android Pay isn't working on the OnePlus One CM 14.1 yet.Refer this link for more info.
__
v7
Forum Moderator
Hello,
is anyone else experiencing any issue with NFC on 5.1.9?
Looks like I'm not able to read my tags for some reason.
Pretty sure Android Pay worked after the upgrade, but didn't have a chance to test it today (I just found the issue with tags).
EDIT: Android Pay working fine but none of the Leap Card (Dublin's public transportation card) I tried seem to work.
Weird.
No I haven't. I've been using Google Pay since I've gotten the phone which I rooted day one. I'm on 5.1.9 rooted with TWRP and EX Kernel. Also works with stock kernel too. Maybe a clean wipe and install is in order if you continue to have issues?
I'm on 5.1.9 and I use an app to write to nfc stickers and it is working fine. Reads the stickers no troubles too...
This is very odd.
Android Pay works flawlessly, every single time.
But I've tried with three different NFC based Leap Cards and none of them is triggering the NFC.
Tried them on another phone and they're absolutely fine.
Will try to get a couple tags different tags and I'll try again.
Thanks for the feedback tho!
So, tried with a couple other tags and I can read and write no problem.
Some weird issue with the Leap Card chip...
works fine here.
I had the same issue until I went into settings- more - tap&pay - and changed 'Use default' to 'always', now it works for leap cards
Here, check this out.
Me:
When two BT devices capable of telephony functions are connected, the second one connects as "Connected (no phone)", and its telephony function cannot be used.
Example (picture attached). If Huawei Watch is already connected, when Jabra Talk attempts to connect, it will connect as described above, and one cannot make or receive phone calls on Jabra Talk (but still can on the watch.)
Oneplus support:
Thank you for taking the time to send us this email as well as the screenshot that you provided. I understand that you want to use both of the Bluetooth devices for easy access and getting in touch with loved ones for helping us keep on track with our daily activities.
I would like to inform you that the OnePlus 6 can actually connect to two Bluetooth devices. However, by default, you can only choose one for making and receiving calls. Just choose which you preferred to use by toggling the "Phone calls" under each setting of the Bluetooth devices.
This bug was not present in 5.1.5. They introduced it in 5.1.6/7.
This bug is present in all Pixel phones because it's a buggy Google code that Google simply does not care to fix.
Samsung fixed this in their phones.
So, I am guessing OP had this fixed in 5.1.5, but then they just lazily copied and pasted that Google garbage code.
And they don't know how to fix it now. So now it's a freaking feature.
UNBELIEVABLE!
I have the same problem with my Huawei Watch and my cars hands free system
I tried to disconnect the watch with Tasker as soon as my hands free system connects, but it never worked reliable (because the watch connects again immediately and takes over the call functionality)
I guess we need to wait until we get Android Pie because as far as I know this problem is solved with Android Pie
MJFox78 said:
I have the same problem with my Huawei Watch and my cars hands free system
I tried to disconnect the watch with Tasker as soon as my hands free system connects, but it never worked reliable (because the watch connects again immediately and takes over the call functionality)
I guess we need to wait until we get Android Pie because as far as I know this problem is solved with Android Pie
Click to expand...
Click to collapse
I hope so. But I'm not that hopeful - I think it's a Google bug, and they simply don't care to fix it.
Meanwhile, I have to disable the phone functionality on the Watch so I can use my hands free car kit.
It's so disappointing, especially since this stuff always worked with Samsung phones, OOS 5.1.5 (the bug was introduced in 5.1.6/7) and even the early Pixel, pre Android 7.0.2.
nabbed said:
Here, check this out.
Me:
When two BT devices capable of telephony functions are connected, the second one connects as "Connected (no phone)", and its telephony function cannot be used.
Example (picture attached). If Huawei Watch is already connected, when Jabra Talk attempts to connect, it will connect as described above, and one cannot make or receive phone calls on Jabra Talk (but still can on the watch.)
Oneplus support:
Thank you for taking the time to send us this email as well as the screenshot that you provided. I understand that you want to use both of the Bluetooth devices for easy access and getting in touch with loved ones for helping us keep on track with our daily activities.
I would like to inform you that the OnePlus 6 can actually connect to two Bluetooth devices. However, by default, you can only choose one for making and receiving calls. Just choose which you preferred to use by toggling the "Phone calls" under each setting of the Bluetooth devices.
This bug was not present in 5.1.5. They introduced it in 5.1.6/7.
This bug is present in all Pixel phones because it's a buggy Google code that Google simply does not care to fix.
Samsung fixed this in their phones.
So, I am guessing OP had this fixed in 5.1.5, but then they just lazily copied and pasted that Google garbage code.
And they don't know how to fix it now. So now it's a freaking feature.
UNBELIEVABLE!
Click to expand...
Click to collapse
if Google's code is garbage, I suggest you stop using android and start making your own good code!
nabbed said:
I hope so. But I'm not that hopeful - I think it's a Google bug, and they simply don't care to fix it.
Meanwhile, I have to disable the phone functionality on the Watch so I can use my hands free car kit.
It's so disappointing, especially since this stuff always worked with Samsung phones, OOS 5.1.5 (the bug was introduced in 5.1.6/7) and even the early Pixel, pre Android 7.0.2.
Click to expand...
Click to collapse
I disabled the phone functionality too
I had a Samsung phone before as well (Note 8) and with that I had no problems with my hands free kit but instead the smartwatch lost the phone functionality after a few hours so I always had to reconnect it (basically the same problem but the other way round)... it's very frustrating that such a pretty basic thing doesn't work properly
I also tried this app: https://play.google.com/store/apps/details?id=org.myklos.btautoconnect
but it didn't seem to make any difference, it didn't seem to make anything at all
I read that Android Pie is able to connect to more than one Bluetooth headset at a time so this should fix the issue after all
kewlest22 said:
if Google's code is garbage, I suggest you stop using android and start making your own good code!
Click to expand...
Click to collapse
I had a Pixel XL for over a year. Only kept it for Project FI. Bug ridden POS.
Sold it for half going price just so I could feel clean again.
Even if Samsung *used* to have sluggish Touchwiz in the past, at least it didn't have deal breaking bugs.
Don't even have to make my own code - some XDA roms had fixed this bug, as opposed to Google.
MJFox78 said:
I disabled the phone functionality too
I had a Samsung phone before as well (Note 8) and with that I had no problems with my hands free kit but instead the smartwatch lost the phone functionality after a few hours so I always had to reconnect it (basically the same problem but the other way round)... it's very frustrating that such a pretty basic thing doesn't work properly
I also tried this app: https://play.google.com/store/apps/details?id=org.myklos.btautoconnect
but it didn't seem to make any difference, it didn't seem to make anything at all
I read that Android Pie is able to connect to more than one Bluetooth headset at a time so this should fix the issue after all
Click to expand...
Click to collapse
I am almost positive that if you had a somewhat similar problem on a Note 8, it's probably Google's fault.
I don't really use the 2 BT phone functionality for more than 30 min on average, but I've never had any problems on Note 7, GS6 or GS9, or even on a Pixel pre 7.0.2 android, when this bug was first introduced.
After 7.0.2, bluetooth stuff just broke everywhere. This bug, constant disconnects and reconnects, for some people music skips, for some doesn't even work, BT UI in Settings just crashing etc.
It's like Google replaced their BT programmer with a monkey at that point, or even a monkey's nephew.
So just because you cannot use 2 Bluetooth devices simultaneously to make phone calls, it's a deal breaker??? Lmao please please please go back to Samsung so we don't have to hear the whining anymore. Good luck with those bootloaders
I cant get NFC to work properly. My phone is able to read cards and tags in NFC mode but it doesnt emit anything. E.g. google pay is not working.
I have ArrowOS 11 with latest MIUI firmware.
I tried with my wifes NFC phone and my Poco can register signal from her phone but not the other way around.
Im thinking firmware issues or something with ArrowOS?
Any ideas?
I've got a similar issue, I can't get NFC payments to work. Also using Arrow OS 11 (latest release) with the newest miui firmware. Tried to root my phone with Magisk 24 to see if this works but until now without any success. Any help would be great.
I was able to get mine to work yesterday using an apple 12 as reciever.
The signal is insanely weak, i literally had to use a precise angle at a certain spot on the iphone to get a registration.
There is no way to get a card terminal to register anything this NFC emits. Seems it has to be closer than a few millimeters apart to get any registration.
Which is strange because i can scan tags/cards that are a few cm away without issue..
Im thinking this is a hardware issue
ndb055 said:
I've got a similar issue, I can't get NFC payments to work. Also using Arrow OS 11 (latest release) with the newest miui firmware. Tried to root my phone with Magisk 24 to see if this works but until now without any success. Any help would be great.
Click to expand...
Click to collapse
Install Magisk 23, hide the Magisk app (it will get a different icon and a different package name), hide Magisk from Google Play, Google Pay and your banking apps, install GPay SQLite Fix v2.6 from here:
Releases ยท stylemessiah/GPay-SQLite-Fix
A magisk module that ONCE allowed Google Pay to work on rooted phones - stylemessiah/GPay-SQLite-Fix
github.com