alesimula / wsa_pacman

A GUI package manager and package installer for Windows Subsystem for Android (WSA)
GNU General Public License v3.0
3.9k stars 837 forks source link

Quick power button does not work #20

Closed ShlomoCode closed 2 years ago

ShlomoCode commented 2 years ago

Thanks for this great software! But the WSA quick power button does not work for me, I press and it does not turn on the WSA Only after I open any app is the WSA enabled and then apps can be installed. with gratitude Written using Google Translate, I do not speak English.

ShlomoCode commented 2 years ago

fiald

ShlomoCode commented 2 years ago

I press like that 👆👆👆 and nothing happens.

ShlomoCode commented 2 years ago

@alesimula

alesimula commented 2 years ago

@shlomo-shlomo do you see (even for a moment) the process WsaClient.exe appear in Windows' task manager when you click on the button?

ShlomoCode commented 2 years ago

@alesimula NO.

alesimula commented 2 years ago

@shlomo-shlomo Alrighty then... please download this application version and tell me what you see in this text box (the text is selectible)

Does the file exist? does the directory exist?

image

ShlomoCode commented 2 years ago

@alesimula Errors installing the file ... image image

alesimula commented 2 years ago

@shlomo-shlomo just skip the file

alesimula commented 2 years ago

@shlomo-shlomo I need your feedback, I cannot replicate this issue and no other user reported it

ShlomoCode commented 2 years ago

@alesimula OK, I installed and opened the software:

image

What now?

alesimula commented 2 years ago

Can you confirm that file exists? If so, it's strange that it doesn't boot

BTW when you install WSA with the terminal (eg. When installing the Magisk + GApps version) the installation directory will be the directory where you extracted the files into; it's unrelated to this problem, but I recommend not using the Download folder

ShlomoCode commented 2 years ago

Can you confirm that file exists?

YES,

image

Is it possible to transfer the WSA location after installation?

alesimula commented 2 years ago

@shlomo-shlomo Maybe it's possible if you find all registry entries that point to the application, but I haven't tried.

Anyway, at least now I know how to replicate the issue, I'll try to install WSA with Gapps and Magisk and see if a can solve the problem

ShlomoCode commented 2 years ago

@alesimula Thanks. I installed from here https://github.com/LSPosed/MagiskOnWSA

alesimula commented 2 years ago

@shlomo-shlomo Wait, I see the last two folders have a different name; Does copying the exact path you see on the app (except the exe) and pasting it on top of the file explorer bring you to the folder? Also what language is that?

ShlomoCode commented 2 years ago

@alesimula Copying the path brings me to the folder, as you can see in the picture https://github.com/alesimula/wsa_pacman/issues/20#issuecomment-1008299301 The words are My Computer> Downloads. The language is Hebrew. But the path is not in Hebrew because the real directory name is downloads, and it is only displayed in Hebrew.

alesimula commented 2 years ago

@shlomo-shlomo Oh, I see, in any case I'll also try changing the system language just in case that's causing the issue

ShlomoCode commented 2 years ago

@alesimula Is there anything new about it? ...

alesimula commented 2 years ago

@shlomo-shlomo trying it out right now

alesimula commented 2 years ago

@shlomo-shlomo I don't know why, but starting WSA from the app directory won't work (With the Magisk/Gapps version), only starting it from %LOCALAPPDATA%\Microsoft\WindowsApps\MicrosoftCorporationII.WindowsSubsystemForAndroid_8wekyb3d8bbwe

ShlomoCode commented 2 years ago

@alesimula I did not really understand what I needed to do so I could use the quick power button for my WSA.

alesimula commented 2 years ago

@shlomo-shlomo What I'm trying to point out is starting the WSA's .exe file directly works with the official WSA, but not with the Magisk+Gapps one, I might need to use a workaround and start the executable located in appdata instead (which seems to work)

alesimula commented 2 years ago

I'll just write this here to keep track of this issue's possible solutions

start shell:appsFolder\MicrosoftCorporationII.WindowsSubsystemForAndroid_8wekyb3d8bbwe!App

explorer.exe wsa://

alesimula commented 2 years ago

@shlomo-shlomo I might have found a workaround, could you confirm the bug is fixed in this test version? (portable)

ShlomoCode commented 2 years ago

@alesimula Yes, it works :) Well done!!

alesimula commented 2 years ago

@shlomo-shlomo latest version released with the fix