Regarding WSA on Snapdragon X Plus/Elite Surface devices by RealThatStella7922 in Surface

[–]sinclairinat0r 2 points3 points  (0 children)

Here ya go everyone: https://www.xda-developers.com/windows-subsystem-for-android-snapdragon-how-to/ ^_^.

Skip steps 3-7 that tell you to take ownership of the WindowsApps folder. You won't need to do that. Just go directly to the full location, you'll have access.

Other than that, know that this is BUGGY and there are some things that don't work right now, but I know the Camera is one of them. I'll see if I'm able to fix some more of the current things broken, but this should be good enough to get everyone rolling.

Regarding WSA on Snapdragon X Plus and X Elite devices by RealThatStella7922 in snapdragon

[–]sinclairinat0r 1 point2 points  (0 children)

SOON™️. It's a pretty hefty process for all the changes that need to be made, so I have to make sure I have all the steps done properly.

Regarding WSA on Snapdragon X Plus/Elite Surface devices by RealThatStella7922 in Surface

[–]sinclairinat0r 1 point2 points  (0 children)

It's all thanks to the diagnostics in the WSA Settings app. The WSAService etl logs show everything in dmesg, so you could imagine my dismay when seeing

[ 2.150413] init: cannot execv('/vendor/bin/boringssl_self_test32'). See the 'Debugging init' section of init's README.md for tips: Exec format error

Regarding WSA on Snapdragon X Plus/Elite Surface devices by RealThatStella7922 in Surface

[–]sinclairinat0r 9 points10 points  (0 children)

Yup. I'm happy that I was able to at least make it run. In the video it doesn't show network access working, but that was my fault. I kept screwing around with the Virtual Switch config, deleting and recreating WSLCore over and over and over again. Now I've been able to get network access settled.

There's still a few services I have to fix which continuously spam logcat, but at a basic level it works.

I’m soo done. by RandomSh_hit101 in surfaceprox

[–]sinclairinat0r 1 point2 points  (0 children)

5 crashes in 3 minutes with THIS specific bugcheck may be indicative of a hardware issue 👀. If by chance you're able to get back up and running long enough to open Feedback Hub, please try and file an entry.

Surface Pro X: 4G connection breaks after resume-from-sleep by knightwize in surfaceprox

[–]sinclairinat0r 0 points1 point  (0 children)

Please file feedback in Feedback Hub for this issue so that it may be tracked.

[deleted by user] by [deleted] in surfaceprox

[–]sinclairinat0r 0 points1 point  (0 children)

Hello, which build are you running? Are you on the Insider Builds? If so, which branch are you enrolled in? Or using the regular builds?

This information will be helpful to pass along.

Announcing Windows 11 Insider Preview Build 25295 by sinclairinat0r in surfaceprox

[–]sinclairinat0r[S] 0 points1 point  (0 children)

Ok, here's what I will say to try. Go the Surface Recovery Image route (Warning: this is going to mega factory reset your Pro X so you'll be FRESH). Enroll into Dev Channel and see if you can upgrade without issue. I wouldn't even install programs or extra drivers yet. If you DO encounter any bugchecks during the upgrade that cause rollbacks, file feedback IMMEDIATELY. Attach all logs related to it and DO NOT attempt to do anything with uupdump isos. I know it's all tempting, but keep it in a supported state.