-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Cannot run on Copilot+ PCs and other ARM64 Windows 11 devices #325
Comments
galaxybook2 扩容的8G表示可以正常的使用,比我三年前装的好多了。不过同样是只显示英文。 |
I tried and found that only the KernelSU version fails to boot. Additionally, the loss of i18n is due to makepri.exe becoming a file without an extension. Switching to a version other than KernelSU and then changing makepri.exe back to its original state resolves the issue. |
Thank you for the info. |
For me every build doesnt work, the only one that works is the official one from the microsoft store on my arm64 device. |
Including LTS Builds? |
Yep, tried latest build. It just loads and then closes itself. |
What ARM CPU do you have? |
Snapdragon 8cx Gen 3 |
Hey @MustardChef i've found something related about that issue: Protocol name: Application WinDBG: |
I found the only 2 versions that work for me: WSA_2311.40000.5.0_arm64_Release-Nightly-NoGApps-NoAmazon.7z WSA_2311.40000.5.0_arm64_Release-Nightly-NoGApps.7z Might be a gapps issue? |
Probably. |
I have check on a Windows 11 arm64 device (Surface Pro X) and all WSABuilds LTS 1 builds seem to be working for me. |
All builds can't run on ASUS Vivobook S 15 (X1E-78-100), even the official one. |
Can't run on Surface Pro 11th, X Plus version |
@HappyMax0 Even the official version? |
I've tried , the offical version also can't be launched.
…________________________________
发件人: MustardChef ***@***.***>
发送时间: 2024年6月19日 17:17
收件人: MustardChef/WSABuilds ***@***.***>
抄送: HappyMax0 ***@***.***>; Mention ***@***.***>
主题: Re: [MustardChef/WSABuilds] [BUG] Cannot run in ARM64 devices (Issue #325)
Can't run on Surface Pro 11th, X Plus version
@HappyMax0<https://github.com/HappyMax0> Even the official version?
―
Reply to this email directly, view it on GitHub<#325 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AHEPQDJ3SDR6XKFXDHAA6A3ZIFEEPAVCNFSM6AAAAABEEDIL7GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNZYGE4DEOBZGU>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Seems like something was removed in 24H2. |
Happens on Surface Pro 11 w Snapdragon X Elite as well. The VmmemWSA seems to hang a certain number of CPU threads to 100% for a few minutes and then closes. The GApps Amazon Magisk one hangs between 4-7 threads seemingly randomly. The KernelSU one always only hangs one thread (constant 8% CPU usage). Changing display driver makes no difference. Haven't tried the GApps-less versions yet |
Ok tried both the Amazon only WSABuilds as well as the official WSA. These also don't work but with a different behavior. Both crash during launch quickly, getting to about 400MB memory usage before shutting down. I'm starting to think maybe Microsoft just didn't bother with WSA support on these new CPUs |
GApps-less versions also cannot be launched.
获取Outlook for Android<https://aka.ms/AAb9ysg>
…________________________________
From: Jason Zhao ***@***.***>
Sent: Thursday, June 20, 2024 1:51:04 AM
To: MustardChef/WSABuilds ***@***.***>
Cc: HappyMax0 ***@***.***>; Mention ***@***.***>
Subject: Re: [MustardChef/WSABuilds] [BUG] Cannot run in ARM64 devices (Issue #325)
Happens on Surface Pro 11 w Snapdragon X Elite as well.
The VmmemWSA seems to hang a certain number of CPU threads to 100% for a few minutes and then closes. The GApps Amazon Magisk one hangs between 4-7 threads seemingly randomly. The KernelSU one always only hangs one thread (constant 8% CPU usage). Changing display driver makes no difference. Haven't tried the GApps-less versions yet
―
Reply to this email directly, view it on GitHub<#325 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AHEPQDOENLXIKOKQO43VYYLZIHAIRAVCNFSM6AAAAABEEDIL7GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNZZGI2DEMZRHA>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Each version don't work on Surface Pro 11 with XElite inside, also the official version installed by install Amazon Store. |
Yes this is exactly what's happening on my Surface Laptop 7. |
Same here for my X Plus Surface Pro 11 |
Same for lenovo 7x snapdragon x elite |
@MustardChef - If you modify the vendor and system partitions, set the properties to make it an arm64-v8 only distro, replace the armv7 binaries/services with armv8 versions, this will be resolved. I'm going to try and write up some instructions to repro how I made it work through all my trial/error. Buuuuuuut... Here ya go. And I owe it to your build.sh script to show how to PROPERLY mount these partitions as rw then convert back to vhdx. That saved my arse, because manually editing via hex editor / Notepad++ was not fun. |
https://www.xda-developers.com/windows-subsystem-for-android-snapdragon-how-to/ https://github.com/snickler/WSA-Patched/releases/tag/0.0.1 <-- I zipped up my system and vendor vhdx. The same exact steps on here to do the custom WSA install folder apply for replacing the vhdxs. There's some things not implemented properly. The Camera doesn't work due to one of the media components still being armv7, but I'm sure someone with actual experience with Android internals can fix this. BTW, I pulled the armv8 versions and some of the changes from one of the Android 13 Armv8 Google emulators. @MustardChef - If you want to play around with these and modify, feel free :). |
First thank you for your big achievement |
Likely related to the same issue of the media service I haven't gotten to work properly yet, which is likely causing the issue I have with /storage/emulated/0 not being mounted properly. I'm trying to see if I can pull something else from the android emulator that would work. |
I tried the patched WSA and it does work, which is amazing! Btw if you already have WSA from WSABuilds installed, I haven't tried but you should be able to just copy the two files from wsa-patched.7z into your WSA installation folder (replacing the files that are already there) and this should result in a working WSA installation. Of course it won't include things like google play services though. Edit: Authenticator app login on Amazon account does work. Weird. Might be my internet since i am on mobile hotspot. |
@snickler Thank you for the great work. |
@MustardChef I totally agree with that. I'm going to finish up the process details tonight and link to them. It makes the most sense. Also, I would LOVE to have help around figuring out why vold isn't mounting /data/media properly. That one of the biggest bugs I have right now. The process details should be helpful with that. |
Niceeee |
Does the Amazon app verification work with you, or multimedia such as YouTube in the browser, or any app that contains a video player?" |
No, not yet. BUUTTTT https://x.com/sinclairinat0r/status/1817326463634338105 ^^ I've made a milestone that involves the emulated storage working! Camera works too for taking pictures, but fails when recording (likely the same issue related to anything involving video). I should have enough of my trial/erroring done to write steps on how to modify an unmodified image to put it in this "mostly" working state. |
@snickler Do you have any instructions or modified files? I tried extracting (7-zip) system.vhdx and vendor.vhdx from the amazon+Gapps latest, removing all 32-bit components and references, and repackaging the files. |
Here has the solution
Someone fixed the Windows Subsystem for Android because Microsoft refuses to ― here's how you can do it (xda-developers.com)<https://www.xda-developers.com/windows-subsystem-for-android-snapdragon-how-to/>
…________________________________
发件人: josh900 ***@***.***>
发送时间: 2024年8月11日 14:33
收件人: MustardChef/WSABuilds ***@***.***>
抄送: HappyMax0 ***@***.***>; Mention ***@***.***>
主题: Re: [MustardChef/WSABuilds] [BUG] Cannot run on Copilot+ PCs and other ARM64 Windows 11 devices (Issue #325)
@snickler<https://github.com/snickler> Do you have any instructions or modified files? I tried extracting (7-zip) system.vhdx and vendor.vhdx from the amazon+Gapps latest, removing all 32-bit components and references, and repackaging the files.
It installed but with the same issue of not having any apps, and continuous loading screen.
―
Reply to this email directly, view it on GitHub<#325 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AHEPQDP4E6M3FX33GW2UGWTZQ4ASNAVCNFSM6AAAAABEEDIL7GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOBSGY2DGMRSGA>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
I tried on Surface Pro 11 Copilot PC arm64 and getting similar issue. Version installed: WSA_2407.40000.0.0_arm64_Release-Nightly-GApps-13.0-NoAmazon This popup stays for a minute and then closes without any errors. @snickler : Here is a sequence of what I tried:
Please suggest if I am missing or having a wrong sequence of steps. Note: I haven't tried uninstallation, as there were no AppxBlockMap.xml and AppxSignature.p7x in my installation directory. |
Same issue. I got application crash on my copilot pc:
If need any further information, i can try to provide |
Would love to see if Video issue will be resolved |
same issue |
This version started successfully on snap 8cx gen3 WSA_2307.40000.6.0_arm64_Release-Nightly-MindTheGapps-13.0-RemovedAmazon |
Snapdragon X Elite: Tried a normal install with WSA_2407.40000.4.0_x64_Release-Nightly-with-KernelSU-v1.0.2-MindTheGapps-13.0-RemovedAmazon, which was never able to launch. Replacing vendor.vhdx and system.vhdx with the custom patch also failed. WSA_2307.40000.6.0_arm64_Release-Nightly-MindTheGapps-13.0-RemovedAmazon ran into the same issue, but applying the patch here actually worked. Google appstore is stubbornly stuck on "checking info", though... |
Describe the bug
After installation, I found that the WSA settings app lost i18n, so it will only display the English interface. At the same time, when starting, it will display the
Starting Windows Subsystem for Android™
window, and then disappear after a few minutes. During the window display, I noticed thatvmmemCmZygote
had no memory usage changes.Steps to reproduce the issue
WSA_2311.40000.5.0_arm64_Release-Nightly-with-KernelSU-v0.7.5-MindTheGapps-13.0-RemovedAmazon.7z
Run.bat
Expected behaviour
WSA started
Downloaded Build Of WSA
WSA_2311.40000.5.0_arm64_Release-Nightly-with-KernelSU-v0.7.5-MindTheGapps-13.0-RemovedAmazon.7z
In GitHub release page.
Windows build number
10.0.22635.3212
PC Specification
System Model Surface Pro X
System Type ARM64-based PC
Processor Microsoft SQ1 @ 3.0 GHz,2995 Mhz,8 Cores
RAM 16.0 GB
Additional context
No response
The text was updated successfully, but these errors were encountered: