I haven’t noticed this problem in the first week of my new FP4. Do you guys still encounter this issue?
1 Like
Yep, sometimes a payment doesn’t go through and the phone vibrates like crazy (with a message “Phone moved too fast”). In most cases it’s fine, but definitely not 100%.
1 Like
That sounds like a different issue than I was having. I sometimes had to kill the app Yubico Authenticator because it couldn’t detect my Yubikey via NFC. Google Pay also had this issue a few times. I haven’t used Google Pay a lot the last week.
However, I wasn’t able to reproduce the Yubikey issue in the last week. I sometimes also have issues that I’m too fast with the NFC connection. But I also had this with my old phone. NFC needs some time. I’m using the official protective case by the way.
@NiceColdRum do you still experience this issue? Or is it similar to what @Razem said, that the connection needs some more time?
Yesterday the NFC didn’t work (at all), I had to launch the app that’s the default for NFC communication by hand before it worked again. This only happens with an uptime of about 24 hours. So maybe some process crashes or goes into deep suspend after a while. I didn’t have these issues with my old phone (Android 9-12).
Can you clarify what’s actually happening? Does NFC turn off by itself and you basically have to turn it back on? Or was it turned on but didn’t work unless you opened some app that uses NFC? None of this has happened to me so far, except for weird cases like NFC deactivates itself automatically - #3 by Razem.
Can’t say what actually is going wrong. But I use a Yubikey for 2FA so I use NFC on a daily basis. Sometimes it just stops working with the Yubikey Authenticator app (NFC is still on). I then have to start the app myself. Normally when I hold the key at the back of the phone the app opens automatically. But then it stops doing that, and manual intervention is needed. I don’t think it’s app related, because it works fine on my Pixel 3. Another theory is that because the Pixel 3 has less RAM, it may kill processes faster. My FP4 has 8GB, so maybe keeping it in the background for a long time triggers a bug. Just guessing.
It also happened once with Google Pay.
Yes I still have regular issues with trying to pay contactlessly it’s just Incredibly fussy about where your holding the phone I think it’s some kind of signal issue between the devices because it’s especially bad with handheld wireless payment terminals I suspect because both the phone and payment terminal are moving ever so slightly at all times I have to practically shove my phone on the terminal and hold both together to get it to work 
1 Like
Interesting, the payment terminals in The Netherlands have strong NFC fields. The moment it fails for me is when the software refuses to open the default app for the task, i.e. Google Pay for payments (only happened once) or opening my Yubikey Authenticator (happens after 24+ hours of uptime once in a while). The connection is quite strong, also with my Yubikey.
It’s not that it doesn’t detect the NFC device from a short distance but that if I don’t hold it against the device it won’t take the payment the phone will just vibrate constantly and the terminal will just say it that it didn’t take payment because the phone/card is moving too much
3 Likes
Interesting, I had something similar when I needed to scan my ID for a government app. But not with Google Pay or other things.
1 Like
Yeah, it’s exactly the same for me. It seems like both the sensitivity to the input signal and the strength of the output signal should be considerably increased. Like, it usually goes through, but I definitely need to position the phone much more precisely than I did with my previous phone (Moto Z2 Play). And with some specific terminals it just straight up fails no matter how I try to position it, while my previous phone had absolutely no problem with those.
3 Likes
There’s this one white handheld terminal that actually makes me internally cringe when I see it 
1 Like
I’m getting much more reliable reception now I’ve started positioning the middle of the phone near the NFC sensor, rather than the top as with every previous NFC-capable phone I’ve ever used. I’d guess that’s where the relevant bit of hardware is… even so it’s rather hit-and-miss 
2 Likes
Ha! So you didn’t see the official specs and diagram 
Do you have the phone in a case…
All rhetorical maybe as you seem to have it ‘sorted’?
2 Likes
Nope, no case. I use a belt pouch instead, bought for my previous phone: it’s a snug fit but fits fine as long as you don’t try to plug in headphones, which is a dead loss since it would require the USB plug to pass through the fake-leather pouch wall: the previous phone had an off-centre headphone socket which aligned with a hole in the pouch, bah!
And ooh official specs and diagram? I love this company though I note the back cover and battery are both out of stock. Better not damage either…
hah, NFC right in the centre indeed. How’s that for sheer deductive skill! (“terrible” the crowd calls, “a six-month-old baby could have worked that out”).
3 Likes
I tried to reproduce it, but now it works fine. In other words, I haven’t had any issues with NFC for some time. Please keep the reports coming, but I think it’s fair to at least lower the impact of this issue in the wiki.
It wasn’t in the changelog, but the NFC sensitivity seems to be better. It wasn’t bad for me, but it seems to be better. Could be just a placebo effect of thinking things have improved due to a recent update 
What do you think?
3 Likes
Yes I can confirm also that I’ve seen huge improvements with NFC sensitivity over the last few weeks especially with wireless handheld terminal devices which is very welcome I hope that continued improvements are made as it’s still not the best phone I’ve had for NFC but it’s a significant improvement
3 Likes
I’ve been having NFC similar NFC issues, often having to disable and re-enable it before I could use it. a few days ago I updated to a testing version of Android 13-based CalyxOS and it looks like it’s working as it should. quite a relief that it seems to have been a software issue.
2 Likes