Any interest in exploring running F-Droid on Windows 11?

Personally, I wouldn’t say I’m interested given I don’t even use Windows. But I would like to see how usable Catima would be under Windows, just out of curiosity :slight_smile:

3 Likes

not really

1 Like

Isn’t Anbox dead?

Anbox’s last commit

was Jun 25th, so I don’t think so.

I couldn’t get it to run with Snap, deb, so…

Yes, but Microsoft confirmed you will be able to sideload apps.

1 Like

Indeed (source wikipedia):

" Windows 11 will also allow users to install and run Android apps onto their device using the new Windows Subsystem for Android (WSA) and the Android Open Source Project (AOSP). These apps can be obtained from within the Microsoft Store via the Amazon Appstore. This feature will require a Microsoft account, an Amazon account, and a one-time install for Windows Amazon Appstore client.[56][57][58][59] Users can also install Android apps through any source using the Android application package (APK) file format. "


APK is still supported by Windows but Google Play is now forcing .aab files. This should work until apks can be built with Android Studio…

1 Like

in fact Anbox is not a container, but snap is the container :wink:

Yes, it was one of the first things I thought of when I heard about WSA. I sideloaded it, and it runs okay. Here’s a photo of it: https://imgur.com/l7OjvVM

3 Likes

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.

Tried downloading Windows Subsystem for Android a while ago, but couldn’t figure out how to run it. Just tried again recently. Found out you need to side-load apps like F-Droid using adb. Once you side load an app, you can run it straight from Windows 11 almost like a regular program. Just wanted to mention, running F-Droid using Windows Subsystem for Android works really well and it was very easy to download and install Android apps through F-Droid. Most of the apps I looked at, downloaded and ran without any issues even though some had warnings regarding versions. At least one app that isn’t working properly on my Android devices ran great on the Windows system. It was a really nice experience using F-Droid on Windows and it’s a nice way to install FLOSS on that system.

8 Likes

Did you try to drag/drop the apk in the emulator (without adb command)?

1 Like

EDIT: they force .aab (appbundle) but it still works with APK on Google Play Store.

It’s what I said with Flatpak by email, but…

F-Droid appears to work quite well on WSA on Windows 11.

WSA itself currently is pretty clunky. The Amazon App Store that it requires doesn’t appear to have much in it (but it will load up apps that are in my account left over from an abandoned Kindle Fire.

The OTHER issue is that apps install under F-Droid interfiled in the Windows 11 start menu without any indicators that they are Android. Using Simple App Launcher to drive around that limitation so I can keep track of them.

I run Transistor from F-Droid so I have the same streaming radio on everything I use. Primitive ftpd was used to upload the stations from my phone.

1 Like

In Linux there’s software to install and boot Android x86 based on LineageOS.
It requires Wayland and it integrates in the system.

Update: I am experimenting with Discreet Laucher vs Simple Launcher. It has the advantage of staying open after the selected app is started – whether that’s beneficial is likely a matter of personal preference. I already use DL on my phone so now I am looking at the same launcher in both places.

What BOTH of these do is expose underlying functions that are otherwise a nusiance to get at. Like the Android settings and the native android Contacts app. The Contacts app is connected via DAVx5, which also appears to work fine. Now I can see my phone contacts on the PC and have the the same group functionality as my Nokia phone and Samsung tablet.

What WSA does is open up possibilities for interoperability between Windows and Android for ordinary Windows PC users. All it requires is side-loading an app store like F-Droid and skipping anything that requires Google Services and you are off and running. What I’ve tried that works well on my tablet appears work fine in WSA.

Final update for the benefit of anyone else who is interested in trying F-Droid on WSA - what I have settled down to using in parallel with tablet and phone:

Discrete Launcher
Material Files
primitive ftpd
DAVx5
FairEmail
Transistor
Several SECUSO games
ImapNotes3

ImapNotes3 solves a long-standing problem in Windows where there was no offline access to the notes feature in my Fastmail account.

The native android contacts app continues to work fine.

Have tried Simple Contacts but that doesn’t appear stable under WSA. I have also abandoned Simple Launcher. WSA just updated to Android 13 and the launcher quit scaling icons properly. Other Simple Apps also appear to currently have issues.

There doesn’t appear to be any native calendar function in WSA. I am currently using Business Calendar 2 Pro (via the Amazon Appstore). This is probably my one concession to closed source for interoperability with Windows.

1 Like

All good things must come to an end. Much mention of genteel mutual fingerpointing: