Comments (7)
注:这台win10本体是台通用计算服务器,虚拟化默认就是开启的
并且后台还挂着两个HyperV虚拟机在跑,所以虚拟化相关的配置肯定是没有问题的
from wsapatch.
WSA 的 log 位置如图所示。
这里应该会有 WsaClient 和子系统的 dmesg.
但是我并没有遇到过这样的情况,你可以自行看看 log 尝试一下...
另外 winver
看看版本号,10.0.19044.2311 以上应该是可以的,或者说是小版本号 2311 以上。
from wsapatch.
WSA 的 log 位置如图所示。
这里应该会有 WsaClient 和子系统的 dmesg. 但是我并没有遇到过这样的情况,你可以自行看看 log 尝试一下...
另外
winver
看看版本号,10.0.19044.2311 以上应该是可以的,或者说是小版本号 2311 以上。
感谢回复
首先是winver,操作系统内部版本号为19045.3086,主版本号为22H2,这点是我疏忽了,之前在提交issue的时候没有注意到win10的主要系统信息中没有包含这个,不过在安装部署之前有确认过的
然后,这里是按照您说的步骤得到的日志
WSA diagnostics.zip
由于这份日志出乎意料的长
(好吧,安卓就没有不长的logcat,但是目前还不明确是wsa自身的问题还是内部安卓的问题)
所以我觉得先把他上传上来比较好,便于大家一起分析,顺便我也会去microsoft/WSA那边发个discuss(因为我的win11上也出现了类似的问题)
最后吐槽一句,微软社区居然还是踢皮球把我的问题从learn Q&A丢到Github来了= =
不知道该说什么好
微软社区的帖子 https://answers.microsoft.com/zh-hans/windows/forum/windows_11-wintop_apps-win_subtopamazon/wsa%e5%9c%a8%e6%b2%a1%e6%9c%89%e6%8a%a5%e9%94%99/a5429b78-432e-47e0-9848-1c4dd48499fb?messageId=87368b5f-e36f-49ae-bb01-b866847e1228
from wsapatch.
在日志中有大量的 SurfaceFlinger 的 crash 相关信息,推测这是直接原因。
08-21 15:32:47.320 84 84 I tombstoned: received crash request for pid 204
08-21 15:32:47.355 263 263 I crash_dump64: performing dump of process 169 (target tid = 204)
08-21 15:32:47.562 263 263 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
08-21 15:32:47.562 263 263 F DEBUG : Build fingerprint: 'google/redfin/redfin:13/TQ2A.230505.002.A1/2305.40000.6.0:user/release-keys'
08-21 15:32:47.562 263 263 F DEBUG : Revision: '0'
08-21 15:32:47.562 263 263 F DEBUG : ABI: 'x86_64'
08-21 15:32:47.562 263 263 F DEBUG : Timestamp: 2023-08-21 15:32:47.357155800+0800
08-21 15:32:47.562 263 263 F DEBUG : Process uptime: 7s
08-21 15:32:47.562 263 263 F DEBUG : Cmdline: /system/bin/surfaceflinger
08-21 15:32:47.562 263 263 F DEBUG : pid: 169, tid: 204, name: surfaceflinger >>> /system/bin/surfaceflinger <<<
08-21 15:32:47.563 263 263 F DEBUG : uid: 1000
08-21 15:32:47.563 263 263 F DEBUG : signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr --------
08-21 15:32:47.563 263 263 F DEBUG : Abort message: 'no suitable EGLConfig found, giving up'
08-21 15:32:47.563 263 263 F DEBUG : rax 0000000000000000 rbx 00000000000000a9 rcx 00007c8ee1e173bf rdx 0000000000000006
08-21 15:32:47.563 263 263 F DEBUG : r8 25bc74d8371b10a7 r9 25bc74d8371b10a7 r10 00007c8c517c13d0 r11 0000000000000207
08-21 15:32:47.563 263 263 F DEBUG : r12 00007c8c517c1b20 r13 00007c8c515a4648 r14 00007c8c517c13c8 r15 00000000000000cc
08-21 15:32:47.563 263 263 F DEBUG : rdi 00000000000000a9 rsi 00000000000000cc
08-21 15:32:47.563 263 263 F DEBUG : rbp 0000000000000001 rsp 00007c8c517c13c0 rip 00007c8ee1e173bf
08-21 15:32:47.563 263 263 F DEBUG : backtrace:
08-21 15:32:47.563 263 263 F DEBUG : #00 pc 000000000005f3bf /apex/com.android.runtime/lib64/bionic/libc.so (abort+191) (BuildId: 76cb658c499bceaab85932d1254e26df)
08-21 15:32:47.563 263 263 F DEBUG : #01 pc 0000000000006a0a /system/lib64/liblog.so (__android_log_default_aborter+10) (BuildId: de12a5576cf4c4b289feca9973c804f4)
08-21 15:32:47.563 263 263 F DEBUG : #02 pc 00000000000075c2 /system/lib64/liblog.so (__android_log_assert+370) (BuildId: de12a5576cf4c4b289feca9973c804f4)
08-21 15:32:47.563 263 263 F DEBUG : #03 pc 00000000006406b0 /system/bin/surfaceflinger (android::renderengine::skia::SkiaGLRenderEngine::chooseEglConfig(void*, int, bool)+544) (BuildId: 3319b64c6af9010451849fdcd0b09352)
08-21 15:32:47.563 263 263 F DEBUG : #04 pc 00000000006578c2 /system/bin/surfaceflinger (android::renderengine::skia::SkiaGLRenderEngine::create(android::renderengine::RenderEngineCreationArgs const&)+162) (BuildId: 3319b64c6af9010451849fdcd0b09352)
08-21 15:32:47.563 263 263 F DEBUG : #05 pc 000000000063eabc /system/bin/surfaceflinger (std::__1::__function::__func<android::renderengine::RenderEngine::create(android::renderengine::RenderEngineCreationArgs const&)::$_1, std::__1::allocator<android::renderengine::RenderEngine::create(android::renderengine::RenderEngineCreationArgs const&)::$_1>, std::__1::unique_ptr<android::renderengine::RenderEngine, std::__1::default_delete<android::renderengine::RenderEngine> > ()>::operator()() (.f853b653ec5f0649c15b11b979e782e0)+12) (BuildId: 3319b64c6af9010451849fdcd0b09352)
08-21 15:32:47.563 263 263 F DEBUG : #06 pc 0000000000653671 /system/bin/surfaceflinger (android::renderengine::threaded::RenderEngineThreaded::threadMain(std::__1::function<std::__1::unique_ptr<android::renderengine::RenderEngine, std::__1::default_delete<android::renderengine::RenderEngine> > ()>)+353) (BuildId: 3319b64c6af9010451849fdcd0b09352)
08-21 15:32:47.563 263 263 F DEBUG : #07 pc 0000000000655ef1 /system/bin/surfaceflinger (void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (android::renderengine::threaded::RenderEngineThreaded::*)(std::__1::function<std::__1::unique_ptr<android::renderengine::RenderEngine, std::__1::default_delete<android::renderengine::RenderEngine> > ()>), android::renderengine::threaded::RenderEngineThreaded*, std::__1::function<std::__1::unique_ptr<android::renderengine::RenderEngine, std::__1::default_delete<android::renderengine::RenderEngine> > ()> > >(void*)+145) (BuildId: 3319b64c6af9010451849fdcd0b09352)
08-21 15:32:47.563 263 263 F DEBUG : #08 pc 00000000000cca4a /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+58) (BuildId: 76cb658c499bceaab85932d1254e26df)
08-21 15:32:47.563 263 263 F DEBUG : #09 pc 00000000000609f7 /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+55) (BuildId: 76cb658c499bceaab85932d1254e26df)
08-21 15:32:47.568 263 263 E crash_dump64: unable to connect to activity manager: Connection refused
08-21 15:32:47.569 84 84 E tombstoned: Tombstone written to: tombstone_00
from wsapatch.
首先,感谢您的回复
另外我遇到了个非常离谱的情况
正如上面我所说的,应用之前看到是0个,没有在开始菜单出现,并且打不开
然后这台设备似乎是由于内存条的问题,然后蓝屏宕机了一次,后续重启之后发现开始菜单出现了WSA的应用(面具和谷歌套件)
打开WSA的设置以后发现也能够正常识别到这些软件了
看起来一切正常了不是吗?于是我尝试启动WSA的安卓子系统
结果还真的能启动了.....并且看起来功能一切正常(ADB还尚未测试,但是我想应该问题不大)
from wsapatch.
目前在我的两台设备上,win10的这台设备目前算是正常工作了
win11的主力pc还依然打不开WSA
(这个问题就留给微软的WSA官方仓库的issue去解决吧
毕竟不属于现在我们讨论的这个项目的范围了,虽然目前还没有得到微软那边的回复)
而且我注意到一个比较奇怪的地方,虽然win10和win11的闪退表现症状相同,但是win10的日志中有安卓系统那部分的logcat产生,而win11这边的日志只有wsa本体的日志,换句话说,可能安卓这块根本没有被启动,或许这两者产生的原因有本质上的区别
对于win10这边,虽然目前工作正常了,不过我认为还需要在观察一段时间,这莫名其妙的坏掉又莫名其妙的好了多少还是有点不正常的
from wsapatch.
好的,目前我对ADB也进行了测试,目前一切正常,并且也能够从magisk获取到root权限
from wsapatch.
Related Issues (20)
- Is it possible use this patch or try to make this patch work on Windows 10 ARM (Snapdragon 8c Compute Platforms) HOT 8
- Windows 10 22H2自从安装安卓子系统后,经常弹出系统错误窗口
- 可以让windows server 2022运行wsa吗? HOT 5
- Add-AppxPackage : 部署失败,原因是 HRESULT: 0x80073CF6, 无法注册包。 HOT 1
- 开发人员模式打开后安卓应用闪退,且无法连接 ADB HOT 4
- 安卓子系统的语言、地区设置,每次启动都会被重置
- 2604安装WSA_2301.40000.7.0无法启动 HOT 1
- AppxManifest.xml(79,27): 错误 0x80073B06: 无法安装或更新程序包,因为无法识别当前 应用程序上下文的初始屏幕图像。
- WSA受Windows10睡眠影响
- Windows 10 ARM DLL ? HOT 4
- WSAPatch has broken in v2304 of WSA HOT 23
- There was a problem communicating with Google servers. Try again later. HOT 3
- incompatible with Windows server HOT 6
- 功能
- 是否有在win10上将旧版WSA升级到新版WSA的解决办法
- Como puedo cambiar el nombre de "pixel5" a otro?
- server 21h2(2022) not working
- wsap
- 确实可以用,但时没声音。
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from wsapatch.