General wsaLink 6.0

[jocala]

Microsoft is pulling support for the Windows Subsystem for Android, a Windows 11 feature first released in October of 2021 that allowed Windows PCs to run Android apps alongside native Windows apps.

 

[jocala]

wsalink is now deprecated.

 

[Deleted member 1890170]

Refuses to install APKs: Directs to LOG what I can't find.


Hint: Add button "View LOG" to app's GUI.

 

[Deleted member 1890170]

Refuses to install APKs: Directs to LOG what I can't find.

 

[jocala]

Refuses to install APKs: Directs to LOG what I can't find.

Look at Menu->Log->View wsaLink log. You can also see log operation in the video demo at 6:57m.

 

[jocala]

Look at Menu->Log->View wsaLink log. You can also see log operation in the video demo at 6:57m.

wsaLink Video Help

I've reworked the help videos. In addition to the full overview, there are now sections:

1. Intro & Install/Uninstall APKs
2. Shell & Console buttons
3. IP Addresses
4. Menu System
5. File Manager

 

[Deleted member 1890170]

Installing .XAPK currently not supported. Will it get supported in the near future?

 

[jocala]

Scoped storage and Android 11 are making life difficult for PC-based applications. Installing the multiple apks within an xapk archive is no big deal, but pushing the archive's obb contents to Android/obb is throwing security errors. I am working on it.

 

[jocala]

When will WSA-Link get File Explorer the Feature to access the root File-System and the ability to transfer files from Windows Explorer to WSA (and there on the root file system)?

wsaLink's file manager isn't root-aware and does not directly interface with Windows file explorer. if wsa continues to allow a drop-in kernel after it moves into wide release I'll have another look at root. For now the shell and su are your best bet.

 

[jocala]

12/03/21

wsaLink 1.01

File manager sorting added.

Jocala Software

 

[CFKod]

wsaLink provides a link between your Microsoft Subsystem for Android virtual machine and your computer.

Features

Install Programs without Android SDK
ADB enabled console
Busybox
File Manager
ADB Shell
Install/Uninstall Apps
Connect to WSA via localhost or IP
Edit text files on your WSA virtual machine
Log file viewer for wsaLink logs
Hyperlinked HTML Help

Jocala Software

Hey - Thanks for the WSA update
I was just connecting to local host using an older version

even though I've not used Kodi for 5 or 6 years now, the functionality of your apps have helped me so much...

even used the adb controls instead of a mouse on twrp for my old fire tv box...

anyway - thanks again

 

[jocala]

Thanks and Merry Christmas!

 

[jocala]

My contact email has changed to adbjocala@gmail.com

in-program references will be changed in the next release.

 

[jocala]

04/20/22

Version 1.02

Display scaling mode changed.

Support email changed from jocala@jocala.com
to adbjocala@gmail.com

Jocala Software

 

[jocala]

NOTE: wsaLink 1.02 has been pulled due to build issues. If you downloaded v1.02 please visit http://www.jocala.com and download wsaLink v1.03. Thanks you and sorry for the bother!

 

[jocala]

08/08/22

wsaLink 1.04

Windows Terminal support added

Internal script directory added

Jocala Software

 

[jocala]

Unfortunately, I've pulled wsaLink 1.04 due to bugs. Please revert to 1.03. I hope to have v1.05 out soon.

 

[knigge111]

Unfortunately, I've pulled wsaLink 1.04 due to bugs. Please revert to 1.03. I hope to have v1.05 out soon.

Any new version?

 

[jocala]

Not yet. I hope to have a refresh for all Jocala *link software this quarter.

 

[Almighty1]

I am using wsaLink v1.03 and it seems like it cannot connect, when I put in 127.0.0.1, the logs shows it trying to connect to 127.0.0.1, when I put in 127.0.0.1:58526, the logs shows it trying to connect to 127.0.0.1:58526:5555 as it is appending :5555 to everything.

This is what the logs show:
starting server

Unable to connect to: 127.0.0.1:5555

Unable to connect to: 127.0.0.1:5555

Unable to connect to: 127.0.0.1:5555

Unable to connect to: 127.0.0.1:5555

Unable to connect to: 127.0.0.1:5555

Unable to connect to: 127.0.0.1:5555

Unable to connect to: 127.0.0.1:58526:5555

Unable to connect to: 127.0.0.1:58526:5555

Unable to connect to: 127.0.0.1:58526:5555

Unable to connect to: 127.0.0.1:5555

Unable to connect to: 127.0.0.1:58526:5555

Unable to connect to: 127.0.0.1:58526:5555

Unable to connect to: 127.0.0.1:58526:5555

Was looking at your videos,
The current WSA which is 2302.40000.9.0 no longers shows a separate IP address other than the 127.0.0.1:58526