NFC Emulation incorrectly added to Android CATEGORY_PAYMENT

I have a new U-Bolt NFC. It seems that when the U-home app is installed and NFC enabled, the Android NFC emulation is added to the payment cards category. What this means is that in order for it to work when you tap it, it MUST be the set as the default NFC payment app. The impact of this is that you can no longer tap to pay with Google Pay because it is no longer the default payment app.

The “Utec NFC Emulator” should be added to NFC as part of the Android “CATEGORY_OTHER” group so that people can still use their phone to pay AND use their phone to unlock their door, without manually fiddling with their default settings when doing either activity. This would allow their payment app to be default in the NFC payment category and also allow the lock NFC to be active as a service in the background.

Is this already in the works, as this will basically prevent anyone that uses mobile payments frequently from being able to make practical use of NFC for their front door. Am I missing something?

That’s a good write-up. I can’t comment on the Android app, but the iPhone app looks like it was built by outsourcing to a budget shop. There are a lot of bugs and non-standard behaviors.

1 Like