NFC logcat spam in Android Studio

adam · February 20, 2017, 9:23am

Hi, I’m running the Android 5.1 image provided by https://www.96boards.org/products/ce/dragonboard410c/ on my 410c, and seeing a ton of spam in logcat / adb. Apparently something to do with NFC?

In logcat:


...
10-29 22:41:22.455 2939-2939/com.android.nfc E/AndroidRuntime: FATAL EXCEPTION: main
10-29 22:41:22.455 2939-2939/com.android.nfc E/AndroidRuntime: Process: com.android.nfc, PID: 2939
10-29 22:41:22.455 2939-2939/com.android.nfc E/AndroidRuntime: java.lang.NoClassDefFoundError: com.android.nfc.QNfcService
10-29 22:41:22.455 2939-2939/com.android.nfc E/AndroidRuntime:     at com.android.nfc.NfcApplication.onCreate(NfcApplication.java:70)
10-29 22:41:22.455 2939-2939/com.android.nfc E/AndroidRuntime:     at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1012)
10-29 22:41:22.455 2939-2939/com.android.nfc E/AndroidRuntime:     at android.app.ActivityThread.handleBindApplication(ActivityThread.java:4553)
10-29 22:41:22.455 2939-2939/com.android.nfc E/AndroidRuntime:     at android.app.ActivityThread.access$1500(ActivityThread.java:151)
10-29 22:41:22.455 2939-2939/com.android.nfc E/AndroidRuntime:     at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1364)
10-29 22:41:22.455 2939-2939/com.android.nfc E/AndroidRuntime:     at android.os.Handler.dispatchMessage(Handler.java:102)
10-29 22:41:22.455 2939-2939/com.android.nfc E/AndroidRuntime:     at android.os.Looper.loop(Looper.java:135)
10-29 22:41:22.455 2939-2939/com.android.nfc E/AndroidRuntime:     at android.app.ActivityThread.main(ActivityThread.java:5254)
10-29 22:41:22.455 2939-2939/com.android.nfc E/AndroidRuntime:     at java.lang.reflect.Method.invoke(Native Method)
10-29 22:41:22.455 2939-2939/com.android.nfc E/AndroidRuntime:     at java.lang.reflect.Method.invoke(Method.java:372)
10-29 22:41:22.455 2939-2939/com.android.nfc E/AndroidRuntime:     at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:902)
10-29 22:41:22.455 2939-2939/com.android.nfc E/AndroidRuntime:     at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:697)
10-29 22:41:22.621 2958-2968/? E/art: Failed sending reply to debugger: Broken pipe
10-29 22:41:22.638 2958-2958/? E/AndroidRuntime: FATAL EXCEPTION: main
...

In bash session running Android Studio:


[3703222]   WARN -            #com.android.ddmlib - Adb rejected connection to client &#039;16339&#039;: closed 
[3703232]   WARN -            #com.android.ddmlib - Adb rejected connection to client &#039;16358&#039;: closed 
[3703243]   WARN -            #com.android.ddmlib - Adb rejected connection to client &#039;16377&#039;: closed 
[3703254]   WARN -            #com.android.ddmlib - Adb rejected connection to client &#039;16396&#039;: closed 
[3703265]   WARN -            #com.android.ddmlib - Adb rejected connection to client &#039;16416&#039;: closed 
[3704465]   WARN -            #com.android.ddmlib - Adb rejected connection to client &#039;16454&#039;: closed

These messages show up several times a second while plugged into the 410c. What can I do about this?

giantpune · February 20, 2017, 9:23am

I got this, too. You can delete the NFC apk from /system and reboot and it quiets the spam. Not sure if it breaks anything.

ldts-atsuka · February 20, 2017, 9:23am

Thank you for reporting the error messages.

The procedure bellow from adb shell should remove the NFS apk.

adb root
adb remount
adb shell rm –rf /system/app/QNfc
adb shell rm -rf /system/app/GsmaNfcService
adb shell sync
adb reboot

We are considering to remove NFS files in the future release at the moment.

adam · February 20, 2017, 9:23am

Seems to have fixed it, thanks!

gwideman · February 20, 2017, 9:25am

As new users of DragonBoard just trying to understand Android Studio talking to DragonBoard, this problem just wasted hours of our time.

“We are considering to remove NFS files in the future release at the moment.”

Presumably you’re talking about NFC, not NFS. And it’s 4+ months later and this problem wasn’t solved?

And why isn’t the target NO crap in the log. Even with the problem described here fixed, something is still pumping reams of incomprehensible jibberish into the logcat window. I’ll post that separately.

But for heaven’s sake, do you want people to actually use this product?