this guide didn’t work for me Android Emulator on 4.1
Also, can I android work as disposable on Qubes os
this guide didn’t work for me Android Emulator on 4.1
Also, can I android work as disposable on Qubes os
In what way did it not work?
Try this as well: Android runs fine in qubes, no mouse issue, But - #19 by qubesnewb
Those hacks were required in 4.0 but should not be needed in 4.1
Some open Android issues that might be of interest:
This what happened many times in different days
user@anbox-debain-11:~$ wget https://build.anbox.io/android-images/2018/07/19/android_amd64.img.sha256sum && wget https://build.anbox.io/android-images/2018/07/19/android_amd64.img --2023-02-01 11:04:34-- https://build.anbox.io/android-images/2018/07/19/android_amd64.img.sha256sum Resolving build.anbox.io (build.anbox.io)... 163.172.154.175 Connecting to build.anbox.io (build.anbox.io)|163.172.154.175|:443... connected. GnuTLS: Error in the pull function. Unable to establish SSL connection.
It seems like maybe you are doing this from a TemplateVM
, yes? If so …
tinyproxy
when internetting from a template
. Try this:# export https_proxy=127.0.0.1:8082 && wget https://build.anbox.io/android-images/2018/07/19/android_amd64.img.sha256sum && wget https://build.anbox.io/android-images/2018/07/19/android_amd64.img
Ok I am not tech savy …
Do you mean First:
open console
second
I have to write this in my console
# export https_proxy=127.0.0.1:8082 && wget https://build.anbox.io/android-images/2018/07/19/android_amd64.img.sha256sum && wget https://build.anbox.io/android-images/2018/07/19/android_amd64.img
Yes but, now I’ve got to ask; why are you even downloading this to a TemplateVM
?
The last time I installed anbox, I just followed this documentation:
A) Manually download (via browser/cli) from a (disposable?) internet connected guest qube
B) Verify file with signature
C) Copy to dom0
In dom0:
$ qvm-run --pass-io dispXXXX 'cat "/media/user/android_amd64.img"' > android_amd64.img
D) Create Standalone/HVM
In dom0:
$ qvm-create --property=virt_mode=hvm --property=memory=4096 --property=kernel='' --label red --standalone --root-move-from android_amd64.img anbox
Why sudo?
Because I’m tired …
You’re correct, not needed nor specified in documentation. Thanks for pointing that out
let’s give it a try …
First I have to follow this guide to download Anbox on my disposable vm (fedora )
https://docs.anbox.io/userguide/install.html#
Is it correct ?
I’ve never bothered to install in that way, nested.
I (and, I think others) have opted to install the raw img
file to a Standalone/HVM drive.
The steps for creating like this are here.
i followed your steps exactly but when i start the VM it says ‘no bootable device’.