android 微信推送延迟,使用virtualXposed，微信消息会延迟10-60分钟-优快云博客

在使用VirtualXposed的环境下，微信出现CoreService启动失败，导致消息延迟的现象。问题主要发生在vivo x9i和小米9手机上，系统版本分别为7.1.2和9.0。对比root版Xposed，发现VirtualXposed中微信无法正常启动CoreService，服务可能因zombie状态而停止响应。日志显示多次尝试重新启动CoreService但未成功，最终导致消息接收延迟。问题可能与VirtualXposed的兼容性或服务管理有关。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

问题描述

在群聊容易发现问题，其他群成员收到消息后，使用virtualXposded的微信app，会延迟消息，时间不定，有可能10分钟，也可能60分钟

复现步骤

打开微信聊天界面，亮屏状态下，过几个小时会出现，出现概率性高

环境

机型：vivo x9i ，小米 9

系统版本：7.1.2， 9.0

ROM版本：非root，正式版

Xposed 插件以及插件版本：version89， v3.1.5

VirtualXposed版本：0.17.3

补充

使用root版的Xposed，微信不会延迟消息，对比两者的微信开发log

发现在virtualxposed运行的微信，启动CoreService失败(CoreService是微信的重要服务)

以下是微信启动CoreService失败的log：

11-15 17:44:50.160 25179 25179 I MicroMsg: MicroMsg.CoreServiceConnection-->enter bindCore, isBinding: true, binderAlive: false

11-15 17:44:50.160 25179 25179 I MicroMsg: MicroMsg.CoreServiceConnection-->bindCore reenter, isBinding: true, binderAlive: false, return directly.

11-15 17:44:50.270 25179 25179 I MicroMsg: MicroMsg.CoreServiceConnection-->enter bindCore, isBinding: true, binderAlive: false

11-15 17:44:50.270 25179 25179 I MicroMsg: MicroMsg.CoreServiceConnection-->bindCore reenter, isBinding: true, binderAlive: false, return directly.

11-15 17:44:50.339 25179 25209 I MicroMsg: MicroMsg.CoreServiceConnection-->enter bindCore, isBinding: true, binderAlive: false

11-15 17:44:50.340 25179 25209 I MicroMsg: MicroMsg.CoreServiceConnection-->bindCore reenter, isBinding: true, binderAlive: false, return directly.

11-15 17:44:50.963 25179 25179 I MicroMsg: MicroMsg.CoreServiceConnection-->enter bindCore, isBinding: true, binderAlive: false

11-15 17:44:50.963 25179 25179 I MicroMsg: MicroMsg.CoreServiceConnection-->bindCore reenter, isBinding: true, binderAlive: false, return directly.

11-15 17:44:51.483 25179 25179 I MicroMsg: MicroMsg.CoreServiceConnection-->enter bindCore, isBinding: true, binderAlive: false

11-15 17:44:51.484 25179 25179 I MicroMsg: MicroMsg.CoreServiceConnection-->bindCore reenter, isBinding: true, binderAlive: false, return directly.

11-15 17:44:53.137 25179 25179 I MicroMsg: MicroMsg.CoreServiceConnection-->enter bindCore, isBinding: true, binderAlive: false

11-15 17:44:53.137 25179 25179 I MicroMsg: MicroMsg.CoreServiceConnection-->bindCore reenter, isBinding: true, binderAlive: false, return directly.

11-15 17:44:56.065 25179 25209 I MicroMsg: MicroMsg.CoreServiceConnection-->enter bindCore, isBinding: true, binderAlive: false

11-15 17:44:56.066 25179 25209 I MicroMsg: MicroMsg.CoreServiceConnection-->bindCore reenter, isBinding: true, binderAlive: false, return directly.

11-15 17:44:56.614 25179 25179 I MicroMsg: MicroMsg.CoreServiceConnection-->mZombieWaker run serviceBinder: null, binderAlive: false

11-15 17:44:56.615 25179 25179 I MicroMsg: MicroMsg.CoreServiceConnection-->CoreService started but not responding, possibly zombie. Use step 0 to restart CoreService.

11-15 17:44:56.616 25179 25179 I MicroMsg: MicroMsg.CoreServiceConnection-->CoreService started but not responding, possibly zombie. Use step 0 to restart CoreService.

11-15 17:44:56.616 25179 25179 I MicroMsg: MicroMsg.CoreServiceConnection-->unbinding CoreService...

11-15 17:44:56.617 25179 25179 I MicroMsg: MicroMsg.CoreServiceConnection-->unbinding CoreService...

11-15 17:44:56.628 25179 25179 I MicroMsg: MicroMsg.CoreServiceConnection-->ZombieWaker posted again with step 1

11-15 17:44:56.829 25179 25179 I MicroMsg: MicroMsg.CoreServiceConnection-->enter bindCore, isBinding: true, binderAlive: false

11-15 17:44:56.830 25179 25179 I MicroMsg: MicroMsg.CoreServiceConnection-->bindCore reenter, isBinding: true, binderAlive: false, return directly.

11-15 17:45:06.434 25179 25179 I MicroMsg: MicroMsg.CoreServiceConnection-->enter bindCore, isBinding: true, binderAlive: false

11-15 17:45:06.435 25179 25179 I MicroMsg: MicroMsg.CoreServiceConnection-->bindCore reenter, isBinding: true, binderAlive: false, return directly.

11-15 17:45:06.628 25179 25179 I MicroMsg: MicroMsg.CoreServiceConnection-->mZombieWaker run serviceBinder: null, binderAlive: false

11-15 17:45:06.629 25179 25179 I MicroMsg: MicroMsg.CoreServiceConnection-->CoreService started but not responding, possibly zombie. Use step 1 to restart CoreService.

11-15 17:45:06.667 25179 25179 I MicroMsg: MicroMsg.CoreServiceConnection-->Push Process 25179 killed.

11-15 17:45:06.668 25179 25179 I MicroMsg: MicroMsg.CoreServiceConnection-->Push Process 25179 killed.

11-15 17:45:06.669 25179 25179 I MicroMsg: MicroMsg.CoreServiceConnection-->unbinding CoreService...

11-15 17:45:06.670 25179 25179 I MicroMsg: MicroMsg.CoreServiceConnection-->unbinding CoreService...

11-15 17:45:06.930 25179 25179 I MicroMsg: MicroMsg.CoreServiceConnection-->ZombieWaker posted again with step 0

11-15 17:45:06.931 25179 25179 I MicroMsg: MicroMsg.CoreServiceConnection-->ZombieWaker posted again with step 0

11-15 17:45:13.861 25179 25179 I MicroMsg: MicroMsg.CoreServiceConnection-->onServiceConnected

11-15 17:45:13.865 25179 25179 I MicroMsg: MicroMsg.CoreServiceConnection-->remove zombie killer.

android 微信 推送延迟,使用virtualXposed，微信消息会延迟10-60分钟

android 微信推送延迟,使用virtualXposed，微信消息会延迟10-60分钟