Regarding the status on WSA

[sundave1998]

I'm sure many are aware that WSA has stopped development months ago. I have been informed by one of the group members that

1. they are aware that the newly released snapdragon X as well as any new chips likely will not support WSA out of the box
2. they have no plans to support them in the foreseeable future

I suggest to either remove the support for WSA for win on arm, or add a sidenote on which devices are supported, to avoid confusion.

[talynone]

A fix is coming soon for the new Elite Snapdragon CPUs:

https://x.com/sinclairinat0r/status/1812676637953019964

MustardChef/WSABuilds#325

[lexcyn]

A fix is coming soon for the new Elite Snapdragon CPUs:

https://x.com/sinclairinat0r/status/1812676637953019964

MustardChef/WSABuilds#325

The issue is the X Elite doesn't support ARMv7 instructions which WSA requires, so there needs to be a workaround. I would hesitate to say a 'fix' is coming though since all work on WSA was dropped by Microsoft (officially), so any fix will be a hack and/or community driven effort. I would leave this up to @arminask to determine if that constitutes the app being removed or not.

[talynone]

A fix is coming soon for the new Elite Snapdragon CPUs:
https://x.com/sinclairinat0r/status/1812676637953019964
MustardChef/WSABuilds#325

The issue is the X Elite doesn't support ARMv7 instructions which WSA requires, so there needs to be a workaround. I would hesitate to sayAny fixes in general are hacks jobs, there are many unofficial builds listed on the website a 'fix' is coming though since all work on WSA was dropped by Microsoft (officially), so any fix will be a hack and/or community driven effort. I would leave this up to @arminask to determine if that constitutes the app being removed or not.

Any fixes in general are hacks jobs, there are many unofficial builds listed in the repository, and ARM32 only builds which are incompatible with Elite laptops, I don't see why this is any different.

[lexcyn]

A fix is coming soon for the new Elite Snapdragon CPUs:
https://x.com/sinclairinat0r/status/1812676637953019964
MustardChef/WSABuilds#325

The issue is the X Elite doesn't support ARMv7 instructions which WSA requires, so there needs to be a workaround. I would hesitate to sayAny fixes in general are hacks jobs, there are many unofficial builds listed on the website a 'fix' is coming though since all work on WSA was dropped by Microsoft (officially), so any fix will be a hack and/or community driven effort. I would leave this up to @arminask to determine if that constitutes the app being removed or not.

Any fixes in general are hacks jobs, there are many unofficial builds listed in the repository, and ARM32 only builds which are incompatible with Elite laptops, I don't see why this is any different.

And that's fair too - we could always just update the note on the app to say "unofficial fix" or something like that!

[talynone]

The fix has been posted:

https://www.xda-developers.com/windows-subsystem-for-android-snapdragon-how-to/

[arminask]

The fix has been posted:

https://www.xda-developers.com/windows-subsystem-for-android-snapdragon-how-to/

Nice. Even if there was no fix for Snapdragon X Elite/Plus, I don't think only users on these platforms use WSA so I'm not sure if it's a good idea to remove them from the list.

[lexcyn]

The fix has been posted:
https://www.xda-developers.com/windows-subsystem-for-android-snapdragon-how-to/

Nice. Even if there was no fix for Snapdragon X Elite/Plus, I don't think only users on these platforms use WSA so I'm not sure if it's a good idea to remove them from the list.

I will update the description with a link to the fix, that should be good enough I think!

[talynone]

There was no news about this, but there was a new version of the fix released:

https://github.com/snickler/WSA-Patched/releases

This fixed the storage issues, and adds Google Services support. I was able to install the Google Play apk installer and was able to install Google Play apps such as YouTube.

[talynone]

Added fix to list:

#121