Fixed
Status Update
Comments
er...@gmail.com <er...@gmail.com> #2
Sorry for typo, iPhone 7 Pro is supposed to be iPhone 14 Pro instead.
Link to proxmark sniffed logs when iPhone 14 Pro was used to read Pixel 7 when NfcAdapter.setDiscoveryTechnology(this, NfcAdapter.FLAG_READER_DISABLE, NfcAdapter.FLAG_LISTEN_NFC_PASSIVE_F)
is used:
There's plenty of NFC-A communication going back and forth.
at...@google.com <at...@google.com>
at...@google.com <at...@google.com> #3
Thank you for reporting this issue. We have shared this with our product and engineering team and will update this issue with more information as it becomes available.
ad...@google.com <ad...@google.com> #4
The issue has been fixed and watch out for future releases.
Description
Are you an Android developer?"
Which Android Developer Preview build are you using? See Settings > About phone > Build number (for example AP31.240119.016).
Is this a regression from Android 14 to 15?
What device are you using? (for example, Android Emulator, GSI, Pixel 7)
What are the steps to reproduce the problem? (Please provide the minimal reproducible test case.)
NfcAdapter.setDiscoveryTechnology(this, NfcAdapter.FLAG_READER_DISABLE, NfcAdapter.FLAG_LISTEN_DISABLE)
to disable all polling and listening.NfcAdapter.setDiscoveryTechnology(this, NfcAdapter.FLAG_READER_DISABLE, NfcAdapter.FLAG_LISTEN_NFC_PASSIVE_F)
to disable all polling with only NFC-F listening.Issue Category e.g. Framework (platform), NDK (platform), Hardware (CPU, GPU, Sensor, Camera), ART (platform), Runtime Permissions etc
What was the expected result?
NfcAdapter.setDiscoveryTechnology(this, NfcAdapter.FLAG_READER_DISABLE, NfcAdapter.FLAG_LISTEN_DISABLE)
is used, the phone should not be polling and not listeningNfcAdapter.setDiscoveryTechnology(this, NfcAdapter.FLAG_READER_DISABLE, NfcAdapter.FLAG_LISTEN_NFC_PASSIVE_F)
is used, the phone should just be listening with NFC-F and not NFC-A.Can you provide the API document where this expected behavior is explained?
What was the actual result?
NfcAdapter.setDiscoveryTechnology
is not behaving as described withinRelevant logcat output.
Link to captured Android bug report (shared privately in Drive.)
Demo project