下面为详细的日志，截图和txt都已上传，报错service not register 是哪里引用有问题吗？ 还是少导入了哪个so库或是其他的？ 之前2.0.0so库少的情况下会报闪退，然后把相应的so推送到system/lib路径下就可以解决，2.1.0出现这个问题要怎么解决？
2023-12-15 10:40:27.527 10773-10773 IPC.IPCBridgeManager com.vs.eldertv I onServiceConnected(20306741), id:63161501529699
2023-12-15 10:40:27.530 10773-11043 IPC.IPCBridgeManager com.vs.eldertv I [getIPCBridge] bw:20306741, id:63161501529699, process:com.tencent.wmpf pingBinder:true
2023-12-15 10:40:27.534 10773-11043 IPC.ObjectRecycler com.vs.eldertv I addIntoSet(com.tencent.wmpf)
2023-12-15 10:40:27.534 10773-11043 IPC.IPCInv...ackWrapper com.vs.eldertv I keep ref of callback(45139596)
2023-12-15 10:40:27.563 10773-11039 WMPFIPCInvoker com.vs.eldertv I invokeSync <<<< response [WMPFIsDeviceActivatedResponse{isActivated=false}] rId [0]
2023-12-15 10:40:27.563 10773-11039 HomeActivity com.vs.eldertv E 291:false
2023-12-15 10:40:27.564 10773-11039 WMPFIPCInvoker com.vs.eldertv I invokeSync >>>> request [IS_DEVICE_ACTIVATED] [AbstractWMPFSyncInvokeRequest{clientVersion=0, clientApplicationId='null', clientInvokeToken='null', invokeTimestamp=-1, clientProcessName='null'}] rId [1]
2023-12-15 10:40:27.565 10773-11039 IPC.Execut...reatorImpl com.vs.eldertv I newThread(thread : IPCThreadPool#Thread-1)
2023-12-15 10:40:27.565 10773-11043 IPC.IPCBridgeManager com.vs.eldertv I [getIPCBridge] tid=[513] com.vs.eldertv -> com.tencent.wmpf
2023-12-15 10:40:27.566 10773-11043 IPC.IPCBridgeManager com.vs.eldertv I [getIPCBridge] bw:20306741, id:63162816600575, process:com.tencent.wmpf pingBinder:true
2023-12-15 10:40:27.567 10773-11043 IPC.ObjectRecycler com.vs.eldertv I addIntoSet(com.tencent.wmpf)
2023-12-15 10:40:27.567 10773-11043 IPC.IPCInv...ackWrapper com.vs.eldertv I keep ref of callback(36395227)
2023-12-15 10:40:27.575 10773-11039 WMPFIPCInvoker com.vs.eldertv
看着还是库的版本不匹配导致crash，确认下
2.32位设备
然后想看下这个service有没有正常启动起来的时候，又报了一些跟SO库相关的问题，但是libilink2等等的那些SO库是有推送进去的
2023-12-15 11:14:45.961 2211-2278 libc com.tencent.wmpf A Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0 in tid 2278 (DefaultDispatch), pid 2211 (om.tencent.wmpf)
2023-12-15 11:14:46.062 2292-2292 DEBUG pid-2292 A pid: 2211, tid: 2278, name: DefaultDispatch >>> com.tencent.wmpf <<<
2023-12-15 11:14:46.336 2292-2292 DEBUG crash_dump32 A #13 pc 00063413 /data/app/~~mPVCLDAu9MlP-sJrEifXVg==/com.tencent.wmpf-sn694446xVbV-AbUb0h7Nw==/lib/arm/libilink2.so
(BuildId: f317808183b94825f11dc94519ca4cf76a4d9773)
2023-12-15 11:14:46.337 2292-2292 DEBUG crash_dump32 A #14 pc 0006337b /data/app/~~mPVCLDAu9MlP-sJrEifXVg==/com.tencent.wmpf-sn694446xVbV-AbUb0h7Nw==/lib/arm/libilink2.so
(BuildId: f317808183b94825f11dc94519ca4cf76a4d9773)
2023-12-15 11:14:46.337 2292-2292 DEBUG crash_dump32 A #15 pc 0008159d /data/app/~~mPVCLDAu9MlP-sJrEifXVg==/com.tencent.wmpf-sn694446xVbV-AbUb0h7Nw==/lib/arm/libilink2.so
(BuildId: f317808183b94825f11dc94519ca4cf76a4d9773)
2023-12-15 11:14:46.337 2292-2292 DEBUG crash_dump32 A #16 pc 00088323 /data/app/~~mPVCLDAu9MlP-sJrEifXVg==/com.tencent.wmpf-sn694446xVbV-AbUb0h7Nw==/oat/arm/base.odex
(art_jni_trampoline+74)
2023-12-15 11:14:46.338 2292-2292 DEBUG crash_dump32 A #24 pc 00278b18 /data/app/~~mPVCLDAu9MlP-sJrEifXVg==/com.tencent.wmpf-sn694446xVbV-AbUb0h7Nw==/oat/arm/base.vdex
(com.tencent.ilink.Context.newDeviceSession)
2023-12-15 11:14:46.339 2292-2292 DEBUG crash_dump32 A #27 pc 009128c8 /data/app/~~mPVCLDAu9MlP-sJrEifXVg==/com.tencent.wmpf-sn694446xVbV-AbUb0h7Nw==/oat/arm/base.vdex (bkz.<init>+20)
2023-12-15 11:14:46.339 2292-2292 DEBUG crash_dump32 A #30 pc 00905fe8 /data/app/~~mPVCLDAu9MlP-sJrEifXVg==/com.tencent.wmpf-sn694446xVbV-AbUb0h7Nw==/oat/arm/base.vdex
(biz$f.invokeSuspend+108)
2023-12-15 11:14:46.339 2292-2292 DEBUG crash_dump32 A #33 pc 013f6e68 /data/app/~~mPVCLDAu9MlP-sJrEifXVg==/com.tencent.wmpf-sn694446xVbV-AbUb0h7Nw==/oat/arm/base.vdex
(hpm.resumeWith+28)
2023-12-15 11:14:46.340 2292-2292 DEBUG crash_dump32 A #36 pc 00b3df82 /data/app/~~mPVCLDAu9MlP-sJrEifXVg==/com.tencent.wmpf-sn694446xVbV-AbUb0h7Nw==/oat/arm/base.vdex
(kotlinx.coroutines.DispatchedTask.run+338)
2023-12-15 11:14:46.340 2292-2292 DEBUG crash_dump32 A #39 pc 00b69c54 /data/app/~~mPVCLDAu9MlP-sJrEifXVg==/com.tencent.wmpf-sn694446xVbV-AbUb0h7Nw==/oat/arm/base.vdex
(kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely)
2023-12-15 11:14:46.340 2292-2292 DEBUG crash_dump32 A #42 pc 00b68db4 /data/app/~~mPVCLDAu9MlP-sJrEifXVg==/com.tencent.wmpf-sn694446xVbV-AbUb0h7Nw==/oat/arm/base.vdex
(kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask+28)
2023-12-15 11:14:46.340 2292-2292 DEBUG crash_dump32 A #45 pc 00b68ee4 /data/app/~~mPVCLDAu9MlP-sJrEifXVg==/com.tencent.wmpf-sn694446xVbV-AbUb0h7Nw==/oat/arm/base.vdex
(kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker+56)
2023-12-15 11:14:46.341 2292-2292 DEBUG crash_dump32 A #48 pc 00b68e94 /data/app/~~mPVCLDAu9MlP-sJrEifXVg==/com.tencent.wmpf-sn694446xVbV-AbUb0h7Nw==/oat/arm/base.vdex
(kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run)