VirtualXposed icon indicating copy to clipboard operation
VirtualXposed copied to clipboard

Published 20 hours ago • verified publisher icon android-hacker

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

Open kenny68 opened this issue 6 years ago • 6 comments

问题描述

在群聊容易发现问题，其他群成员收到消息后，使用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.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.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-->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.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.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.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.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.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.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.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.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.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.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.861 25179 25179 I MicroMsg: MicroMsg.CoreServiceConnection-->onServiceConnected 11-15 17:45:13.865 25179 25179 I MicroMsg: MicroMsg.CoreServiceConnection-->remove zombie killer.

kenny68 avatar Nov 18 '19 03:11 kenny68

出现问题的时候是不是不可以收发消息？我这边也有遇到类似情况。 机型：RMX1971 ColorOS 版本：v6.0 Android 版本：9 VirtualXposed版本：0.17.3

xinGCN avatar Nov 19 '19 02:11 xinGCN

出现问题的时候是不是不可以收发消息？我这边也有遇到类似情况。 机型：RMX1971 ColorOS 版本：v6.0 Android 版本：9 VirtualXposed版本：0.17.3

可以收发消息，但放置几个小时后，会出现收消息延迟

kenny68 avatar Nov 19 '19 06:11 kenny68

确实会出现，而且不规律出现！！！

igit-cn avatar Nov 25 '19 05:11 igit-cn

我这边也有遇到类似情况。好像没有网络一样,但是朋友圈可以正常加载。 只是发送消息一直转圈，就是不发送。然后就收不到消息 机型：华为畅享9 Android 版本：8.1.0 EMUI版本：8.2.0 VirtualXposed版本：0.18.1

Ayu8806 avatar Mar 17 '20 09:03 Ayu8806

出现：问题的时候是不是不可以收发消息？我这边也有遇到类似情况。 方法：RMX1971 ColorOS版本：v6.0 Android版本：9 VirtualXposed版本：0​​.17.3

可以收发消息，但放置几个小时后，会出现收消息延迟

有解决的方法吗？兄弟

Ayu8806 avatar Apr 07 '20 03:04 Ayu8806

请问有解决的吗

jiachengliu avatar Jun 10 '20 01:06 jiachengliu