I'm trying to port PN7160 to i.MX 8M Nano Evaluation Kit | NXP Semiconductors
When I porting complete follow《AN13189-PN7160 Android porting guide》.The device will automatically restart after booting.
I have tried 2 different Android versions(android-13.0.0_1.0.0 & android-12.1.0_1.0.0), the problem is the same.
The following description can be seen from the startup log.
[2023/7/4 10:03:50] [ 32.922292][ T1] init: starting service 'vendor.nfc_hal_service'...
[2023/7/4 10:03:50] [ 32.955690][ T1] init: starting service 'bootanim'...
[2023/7/4 10:03:50] [ 32.983711][ T1] init: Control message: Processed ctl.start for 'bootanim' from pid: 455 (/system/bin/surfaceflinger)
[2023/7/4 10:03:50] [ 33.114696][ T283] logd: logdr: UID=1027 GID=1027 PID=612 n tail=0 logMask=8 pid=606 start=0ns deadline=0ns
[2023/7/4 10:03:50] [ 33.126380][ T283] logd: logdr: UID=1027 GID=1027 PID=612 n tail=0 logMask=1 pid=606 start=0ns deadline=0ns
[2023/7/4 10:03:50] [ 33.169961][ T1] init: Untracked pid 612 exited with status 0
[2023/7/4 10:03:50] [ 33.176235][ T1] init: Untracked pid 612 did not have an associated service entry and will not be reaped
[2023/7/4 10:03:50] [ 33.186900][ T1] init: Service 'vendor.nfc_hal_service' (pid 606) received signal 6
[2023/7/4 10:03:50] [ 33.195279][ T1] init: Sending signal 9 to service 'vendor.nfc_hal_service' (pid 606) process group...
[2023/7/4 10:03:50] [ 33.205886][ T1] libprocessgroup: Successfully killed process cgroup uid 1027 pid 606 in 0ms
[2023/7/4 10:03:50] [ 33.218814][ T1] init: Untracked pid 614 exited with status 0
[2023/7/4 10:03:50] [ 33.225348][ T1] init: Untracked pid 614 did not have an associated service entry and will not be reaped
Hello all,
I've encountered the same issue with the pn7220, could you please share the patch?
regards
I will send you a patch to your email address. later today. You can integrate it and try it again.
Regards
Daniel
Hi @danielchen
Have you already sent the patch? I haven't received it yet.
I sent it , please check your email
The patch are well received, thank you.
OK, Thank you so much! Is this patch for android13, or android12?
tested with Android 13