Waydroid best practices?

Help
1

Hello folks

I’ve noticed the NixOS wiki for Waydroid is particularly odd;

Prompting the user to install and configure it completely imperatively and in a non-reproducible way:

After rebuilding and switching, finish the Waydroid install in your shell.

Fetch Waydroid images.
You can add the parameters "-s GAPPS -f" to have GApps support. 
$ sudo waydroid init

General usage

Install an Android app
$ waydroid app install </path/to/app.apk>

Update Android

Use following command to upgrade Android (LineageOS) to a newer version if available
$ sudo waydroid upgrade

Those seems to be way off best practice from an outdated documentation

Are there not better ways?

2

AFAIK waydroid is and as always been imperative and non-reproducible.

Anbox was somewhat better because the android images were handled as Nix packages, so they were pinned to a specific version and checked cryptographically. For the rest, they work pretty much the same: there’s no declarative configuration of images, applications, etc.

3

One reason this imperativeness is necessary is because the system images are updated weekly or even more often, and I don’t think it makes so much sense to have to depend on system updates for that. Arguably it’s more state than configuration, anyway, since it’s writing to the runtime dir…

1 Like
4

Honestly, I’d rather have slower updates with a better source provenance (ideally built from source in Nixpkgs) than weekly updates of dubious origin.

1 Like