efraimbart/openinwsa

Open in WSA

Routes clicked links through WSA (Windows Subsystem for Android™) and opens them in an applicable Android application if found, otherwise opens them in the default Windows browser.

Getting Started

Instructions to set up Open in WSA either using the latest release executable or via cloning the repo.

Prerequisites

Required:

• WSA with Developer mode enabled under settings.
• ADB

Suggested:

• Subsystem resources set to Continuous under WSA settings.

Installation

1. Download Executable:

   • Download the latest release executable.

or

2. Clone Repo

   • Download and set up .Net 6.0
   • Run $ git clone https://github.com/efraimbart/OpenInWSA
   • Run $ dotnet build

Setup

1. Open OpenInWSA.exe.
2. If ADB is not automatically found, set the path to ADB.
3. If the default browser is not automatically detected, set a default browser.
4. The application will attempt to elevate itself and register as a browser. If it fails, attempt to run the application manually as an administrator.
5. Set Open In WSA as the default for URL:HyperText Transfer Protocol in Windows settings under Apps > Default apps

Usage

Click a link from within a Windows application and it will route through WSA and open in the applicable Android application. If none are found the link will open in the default Windows browser.

To route links from within Chrome through WSA install the Open in WSA Chrome Extension | Repo and right click on a given link and click Open link in WSA.

openinwsa's Issues

doesnt use right port

So I think this is a cool project, sadly it doesn't seemm to connect to the right port and therefore give an error instead, f.e it tries to connect to 127.0.0.1:5037, while my adb tells me that it is 127.0.0.1:58526 instead. I dont have a lot of knowledge on this so it might be totally easy to fix

Links aren't passed to Firefox

Links seem to not pass through to Firefox or any variation of Firefox. When I click a link that is not associated with an android app, nothing happens. Chromium-based browsers seem to not have this issue.