Analysis and Solution after OS/FW Upgrade
Background
PN7160 / PN7220 are external NFC front-end controllers provided by NXP, designed for deep integration with the Android OS. They are widely used in Android-based non-mobile devices such as digital signage, self-service terminals, access control and attendance systems, in-vehicle systems, and industrial control equipment. Unlike smartphone-class SoCs with integrated NFC, this solution oers flexible antenna layout, high system customizability, and long-term stable operation, making it particularly suitable for fixed Android terminals in non-mobile scenarios. The PN7160 / PN7220 NFC solution consists not only of hardware but also NXP-provided Firmware (FW) and Android Middleware (MW), covering NFC protocol handling, RF management, and Android system integration. This complete hardware–software solution helps ensure consistency, stability, and maintainability of NFC functionality across dierent Android versions, especially for non-handheld Android devices such as advertising displays, access control systems, and kiosks. During Android OS upgrades, changes in system framework design and power management strategies may aect NFC behavior and performance. At the same time, PN7160 / PN7220 firmware and middleware versions must remain compatible with the target Android version. Recent customer reports of NFC performance degradation and abnormal behavior in NFC Cockpit debugging are compatibility issues caused by changes in the Android OS, FW, and MW combinations, which can be improved through version alignment, configuration adjustment, and parameter optimization. This document summarizes the observed issues, root cause analysis, and solution approaches based on issue reproduction and test results, providing reference material for future technical support, troubleshooting, and system version evaluation. Test Environment - Android OS:Android 15 - NFC Reader IC:PN7220 / PN7160 - MW Version: NFC_AR_INFRA_001E_15.03.00 - FW Version:3.2.5(PN7220)/12.50.11(PN7160) - NFC Cockpit Version:NxpNfcCockpit_v8.3.0.0 Issue Description – Reduced NFC Communication Distance After Android OS Upgrade from 15 to 16 Recently, some customers reported a significant change in NFC read performance on Android devices using the PN7160 NFC controller when upgrading the Android OS from version 15 to version 16. Under Android 15, when operating in Reader Mode, the stable NFC card reading distance was approximately 4 cm. After upgrading to Android 16, with the hardware platform remaining completely identical (including NFC controller, antenna design, RF matching, and mechanical structure), the eective reading distance was reduced to approximately 1.5 cm. The customer confirmed the following conditions: NFC controller model: PN7160 Hardware revision unchanged Antenna specifications and mounting position unchanged Power supply, system structure, and peripheral components unchanged The only difference is the Android OS version before and after the upgrade The issue manifests as a significant reduction in NFC read range, while basic NFC functionality remains operational. This is a performance-level regression, which impacts application scenarios requiring relatively long reading distances, such as digital signage and self-service kiosks. Issue Location and Root Cause Analysis The issue is related to the NFC front-end reader configuration on the Android platform and is not caused by hardware design. Based on the observed behavior, the issue points to an RF configuration change. By extracting and comparing the RF configuration files from Android 15 and Android 16 platforms, it was found that polling protocol parameters in the Android 16 RF configuration file were modified—specifically, certain receiver-related parameters were changed. These parameters changes resulted in reduced read sensitivity, leading to a shorter NFC communication distance. Solution
Using the following ADB command to pull the NFC configuration file C:\Users\nxf920XX>adb pull vendor/etc/libnfc-nxp.conf Restore the parameters related to the polling protocol to their default RF values. The default RF values can be referenced from AN13218 – Annex 3. For the issue of reduced communication distance reported by customers, the specific parameters that need modification are shown in the original configuration screenshots:
After modification, push the updated configuration file back to the original path by using command C:\Users\nxf920XX>adb push libnfc-nxp.conf vendor/etc/ libnfc-nxp.conf . And then Reboot the device for the new configuration to take effect by using command C:\Users\nxf920xx>adb reboot. Issue Description – Cockpit Failure After Upgrading FW to Latest Version The latest NFC Cockpit version currently available is NxpNfcCockpit_v8.3.0.0. However, the firmware versions supported by this Cockpit release are not the latest Reader FW versions. When the NFC Reader firmware is upgraded to the latest version and then connected to NFC Cockpit, a version mismatch error occurs, as shown in the original error screenshot.
Once this error appears, all NFC Cockpit functions become unavailable or severely limited, greatly reducing debugging efficiency. Solution Navigate to the NFC Cockpit installation directory, for example: C:\nxp\NxpNfcCockpit_v8.3.0.0\cfg Open the file NxpNfcCockpit_Configuration. Modify the default Reader firmware version in the configuration file to match the latest firmware version used on the Reader. Save the file.
Reboot the device to apply the new configuration. For PN7220, use: C:\Users\nxf920xx>adb reboot . Verification Result After modifying the configuration file and restarting NFC Cockpit, all NFC Cockpit functions were verified to be fully operational again, as shown in the verification screenshot.
Recommendations NFC performance degradation after Android OS upgrade primarily aects PN7160-based platforms. NFC Cockpit malfunction after firmware upgrade aects all Reader products that support NFC Cockpit. When customers encounter the issues described above, it is recommended to follow the configuration adjustments outlined in this document.
View full article