Description: NFC tag scanning stops after the first successful read on Android 16? Check the documented DeadObjectException bug, affected reports, safe workarounds and the limits of Google's QPR3 Beta 1 fix.
If your phone reads an NFC tag once but ignores the next attempt, there is a documented Android bug matching that sequence. Google lists issue #456078994 as fixed in Android 17 QPR3 Beta 1, released on October 2, 2026. That is a Pixel beta release, not confirmation that every Android 16 handset has received a manufacturer fix.
What was reproduced, and on which phones?
A developer report opened in October 2025 describes tag detection working initially, then failing after the phone is moved away and brought back. Turning NFC off and on temporarily restored scanning for the reporter. A separate reproduction using Flutter 3.35.4 and flutter_nfc_kit 3.6.0 logged android.os.DeadObjectException and a disconnected NFC service. Reports on Google's tracker named Samsung Galaxy A54 and Galaxy S22; another developer reported additional brands. These are reported devices, not a comprehensive affected-model list.
| Evidence | What it establishes |
|---|---|
| First read succeeds, subsequent scan fails | The specific reported failure pattern |
DeadObjectException in the NFC service |
A communication failure observed in developer logs, not a complete root-cause diagnosis |
Google issue #456078994 marked fixed |
Google has recorded a fix for this tracked issue |
| Android 17 QPR3 Beta 1 release notes | The fix is listed in a Pixel beta build; Samsung firmware status requires separate confirmation |
The reports point to a failure in the NFC service path. They do not establish that every payment failure, every Pixel or every Samsung phone shares the same cause.
A safe five-minute check
- Use a spare, non-sensitive NFC test tag you control. Do not experiment with payment cards, transit passes or access badges, and do not write to the tag.
- On Pixel, check Settings → Connected devices → Connection preferences → NFC. Other brands use different menu labels.
- Read the tag, move the phone away, then try the same tag again. Note whether the second attempt is completely silent or the tag is detected but its app does not launch.
- For the second case, check the Android 16+ per-app NFC launch permission where available: Settings → Apps → Special app access → Launch via NFC. An app blocked here can look like a broken reader.
- On Android 17, web-link tags may show an Open link notification instead of launching a page immediately. A notification means the tag was detected; this is different from the service-crash pattern.
Workarounds without deleting data
Toggle NFC off and back on, then repeat the read-only test. This is a temporary recovery reported by the original issue author, not a guaranteed permanent solution. A normal reboot is another low-risk check. If only one app fails, update that app and check its NFC permissions; if only one tag fails, investigate the tag or its content. Record your phone model, Android version, build number, first successful scan and the exact next failure for support.
Google's October beta uses DP11.260918.005 on the Pixel 11 family and DP11.260918.006 on other supported Pixels. On Pixel, find the build under Settings → About phone → Android version. Check Settings → System → Software updates for updates offered to your own device. For Samsung and other brands, follow their firmware channels; Google's Pixel build is not installable as their fix.
Why a factory reset is the wrong first experiment
Google warns that leaving the Android beta program for a stable build can wipe locally stored data. A beta installation also carries pre-release risks. In Japan, FeliCa and Osaifu-Keitai services can involve stored transit and payment value, so erasing their service data requires the provider's transfer procedure first. Even outside Japan, removing wallet credentials or resetting the phone creates avoidable recovery work. Do not clear payment-service data to test an NFC reader bug.
Bottom line
Test a harmless tag twice, distinguish a silent second scan from a blocked app launch, then try the NFC switch and normal reboot. Issue #456078994 is listed as fixed in Android 17 QPR3 Beta 1; manufacturer-specific stable fixes need their own confirmation. Keep payment data intact while you diagnose the problem.
References (1)
Checked October 18, 2026: Google's QPR3 Beta 1 notes, issue #456078994, Flutter reproduction #222, Android NFC documentation, Pixel NFC support, Pixel update instructions, Android Beta data-wipe rules. The developer reproduction and Google's published fix are separate kinds of evidence.
