Linux mint 20, installation of Anbox looking for a procedure

[Virus-]

Hello I want to install Anbox so I can try a specific application called "Moises - Ai music ap, instrument remover. "

It looks fairly impressive, perhaps even revolutionary? I hope there will be a free open source plug-in for Linux one day, perhaps in Audacity.

https://play.google.com/store/apps/deta ... n_US&gl=US
https://www.youtube.com/watch?v=0PGnNIbH0zk

***
I tried a couple of procedures to install Anbox but without success so far, it's either not working or I don't understand parts of the procedure. I am looking for a clear step by step link to a working procedure for Linux Mint 20.

(I don't know is Moises is going to work on Anbox in the first place.)

These are the infos of my computer:

Code: Select all

System:
  Kernel: 5.4.0-52-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 
  Desktop: Cinnamon 4.6.7 wm: muffin 4.6.3 dm: LightDM 1.30.0 
  Distro: Linux Mint 20 Ulyana base: Ubuntu 20.04 focal 
Machine:
  Type: Desktop Mobo: ASUSTeK model: PRIME B360M-A v: Rev X.0x 
  serial: <filter> UEFI: American Megatrends v: 2603 date: 10/11/2019 
CPU:
  Topology: 6-Core model: Intel Core i5-8400 bits: 64 type: MCP 
  arch: Kaby Lake rev: A L2 cache: 9216 KiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
  bogomips: 33599 
  Speed: 800 MHz min/max: 800/4000 MHz Core speeds (MHz): 1: 800 2: 800 
  3: 800 4: 800 5: 800 6: 800 
Graphics:
  Device-1: Intel UHD Graphics 630 vendor: ASUSTeK driver: i915 v: kernel 
  bus ID: 00:02.0 chip ID: 8086:3e92 
  Display: x11 server: X.Org 1.20.8 driver: modesetting unloaded: fbdev,vesa 
  resolution: 1920x1080~60Hz 
  OpenGL: renderer: Mesa Intel UHD Graphics 630 (CFL GT2) 
  v: 4.6 Mesa 20.3.4 - kisak-mesa PPA direct render: Yes 
Audio:
  Device-1: Intel Cannon Lake PCH cAVS vendor: ASUSTeK driver: snd_hda_intel 
  v: kernel bus ID: 00:1f.3 chip ID: 8086:a348 
  Sound Server: ALSA v: k5.4.0-52-generic 
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
  vendor: ASUSTeK driver: r8169 v: kernel port: 3000 bus ID: 03:00.0 
  chip ID: 10ec:8168 
  IF: enp3s0 state: up speed: 100 Mbps duplex: full mac: <filter> 
  IF-ID-1: lxcbr0 state: down mac: <filter> 
  IF-ID-2: tun0 state: unknown speed: 10 Mbps duplex: full mac: N/A 
Drives:
  Local Storage: total: 2.05 TiB used: 1.15 TiB (56.2%) 
  ID-1: /dev/nvme0n1 vendor: Western Digital model: WDS250G2B0C-00PXH0 
  size: 232.89 GiB speed: 31.6 Gb/s lanes: 4 serial: <filter> rev: 211070WD 
  scheme: GPT 
  ID-2: /dev/sda vendor: Seagate model: ST2000DM008-2FR102 size: 1.82 TiB 
  speed: 6.0 Gb/s rotation: 7200 rpm serial: <filter> rev: 0001 
Partition:
  ID-1: / size: 227.74 GiB used: 20.84 GiB (9.2%) fs: ext4 
  dev: /dev/nvme0n1p2 
Sensors:
  System Temperatures: cpu: 27.8 C mobo: N/A 
  Fan Speeds (RPM): N/A 
Repos:
  No active apt repos in: /etc/apt/sources.list 
  Active apt repos in: /etc/apt/sources.list.d/brandonsnider-cdrtools-focal.list 
  1: deb http://ppa.launchpad.net/brandonsnider/cdrtools/ubuntu focal main
  Active apt repos in: /etc/apt/sources.list.d/heyarje-makemkv-beta-focal.list 
  1: deb http://ppa.launchpad.net/heyarje/makemkv-beta/ubuntu focal main
  Active apt repos in: /etc/apt/sources.list.d/kdenlive-kdenlive-stable-focal.list 
  1: deb http://ppa.launchpad.net/kdenlive/kdenlive-stable/ubuntu focal main
  Active apt repos in: /etc/apt/sources.list.d/kisak-kisak-mesa-focal.list 
  1: deb http://ppa.launchpad.net/kisak/kisak-mesa/ubuntu focal main
  Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list 
  1: deb http://packages.linuxmint.com ulyana main upstream import backport #id:linuxmint_main
  2: deb http://archive.ubuntu.com/ubuntu focal main restricted universe multiverse
  3: deb http://archive.ubuntu.com/ubuntu focal-updates main restricted universe multiverse
  4: deb http://archive.ubuntu.com/ubuntu focal-backports main restricted universe multiverse
  5: deb http://security.ubuntu.com/ubuntu/ focal-security main restricted universe multiverse
  6: deb http://archive.canonical.com/ubuntu/ focal partner
  Active apt repos in: /etc/apt/sources.list.d/stebbins-handbrake-releases-focal.list 
  1: deb http://ppa.launchpad.net/stebbins/handbrake-releases/ubuntu focal main
  Active apt repos in: /etc/apt/sources.list.d/tehnick-direct-connect-focal.list 
  1: deb http://ppa.launchpad.net/tehnick/direct-connect/ubuntu focal main
Info:
  Processes: 261 Uptime: 39m Memory: 15.48 GiB used: 2.06 GiB (13.3%) 
  Init: systemd v: 245 runlevel: 5 Compilers: gcc: 9.3.0 alt: 9 Shell: bash 
  v: 5.0.17 running in: gnome-terminal inxi: 3.0.38 

[rickNS]

When I did some Android experiments I used the "Android-x86".
Arguably, it is rated number one, at least by some.
https://fossbytes.com/best-android-emulators-linux/

Download here,
https://www.android-x86.org/download

Installation instructions here, it is not the same installer Mint has, but not difficult either.
You can install it in a virtual machine, but performance suffers, best to give it a partition, and dual boot it.
https://www.android-x86.org/installhowto.html

I've installed it a couple of times, but I have since removed it. If you have trouble, I "just might" go through it again.

[rickNS]

(I don't know is Moises is going to work on Anbox in the first place.)

Anbox does not support the google play store, so, unless you can find your app (Moises) somewhere else, it would be a waste of your time anyway.

[Virus-]

Ok thanks RickNS I had success installing Android-x86 on virtualbox, I think this will be enough to try the app.

[miraculina]

How did you configure your virtualbox exactly to get android-x86 running with it? which versions do you use of both?
as anbox is too unstable under my lmde4 (you never know if its still going to start after the last system update... had that several times already, got tired of this neverending bugfixing...)

[rickNS]

(you never know if its still going to start after the last system update... had that several times already, got tired of this neverending bugfixing...)

I hear you, I hate updates, it's one of the big reasons I left windows over a decade ago.

I won't say this is good advice, but to avoid headaches like having mis-matched kernel modules, or having to rebuild them etc. (for over a dozen guest machines) this is what I always did, and will contine to do. Once Virtualbox is installed, I blacklist so it never gets an update. Used virtualbox for long time, never any issue.

As far as which version of both, (for me anyway) was Virtualbox 5.2.18, and Android-x86 version 9 (the newest as far as I know.)

I've not tried it on mint 20, Virtualbox version 6.1.16, because I still mostly use mint 19, but I could install it for the heck of it.

[rickNS]

OK there is a bit missing from the install instructions link I gave earlier in this thread.

This one has more info, you need to make the partition in the virtual HD..
https://www.howtogeek.com/164570/how-to ... irtualbox/

Also it seems in Virtualbox 6 you need to also attach the HD, as well as the iso..

Will edit this same post as needed, I'm installing now android-x86 (9) in virtualbox 6.1.

EDIT, done,

[miraculina]

Wow thank you dear rickNS! Followed exactly all the steps in the howtogeek manual you linked here above and android-x86 finally works!!! YEAH YEAH YEAH!

[miraculina]

i just one single more time need your help.
i want to access the android-x86 in my virtualbox via adb.
here https://www.android-x86.org/documentati ... albox.html they write:

Suppose the network of your vbox is OK, you can upload a file from your host by

ADBHOST=<ip of vbox> out/host/linux-x86/bin/adb push <your desired file> /sdcard

You need to know the ip of your vbox. You can get it by Alt-F1 and netcfg. You may also need to reboot Android to see the uploaded files

but neither the android terminal nor my host system (lmde4) know the command netcfg. if i use "sudo ifconfig" in the Alt-F1-Terminal of the Android instead, i get shown the IP of its virtual Wifi adapter: 10.0.2.15. But when I try to ping this IP from my host system, it just says " Destination Host Unreachable".
What do I do wrong?

Or what else is the easiest way to transfer files from the host system to the android-x86 virtualbox?

[miraculina]

found the solution to my last question myself. just tried to apply the wrong part of the debug manual. it's described here, and only 2 steps for making access via adb working:
1. VBoxManage modifyvm <VMName&rt; --natpf1 adb,tcp,*,<localport&rt;,*,5555
• Example from one machine: VBoxManage modifyvm android-x86 --natpf1 adb,tcp,*,5555,*,5555
• Once this is done, you should see the local port (i.e. 5555 in this case) bound on the host via netstat -a (this step is optional)
2. You can now connect to the VM by adb connect localhost:5555

now adb devices shall show localhost:5555 in its result list.

Now I just wonder if / how i can transfer my personal userdata from whatsapp i used in anbox from my anbox backup (i mean the backuped files from /var/snap/anbox/*) to android-x86 in the virtualbox. already installed whatsapp in the latter. making a google backup from the old installation doesnt work because anbox doesnt start anymore on my pc and i never use google anymore at all btw.
dont know which files from the backup belong where now within the virtualbox

[rickNS]

found the solution to my last question myself. just tried to apply the wrong part of the debug manual.

Glad you found a solution, and thanks for the "thanks".

Sorry, I'm not at all familiar with the software adb.

Now I just wonder if / how i can transfer my personal userdata from whatsapp i used in anbox from my anbox backup (i mean the backuped files from /var/snap/anbox/*) to android-x86 in the virtualbox.

I'm also not very familiar with the android OS, so can it use/understand the rsync command ? (quick look says apparently it can)

rsync is how I get files "easily" in, and out of virtual machines, (without having to get USB working). On your host, put the files you want on to send to android guest in a top level folder in home, (helps keep the command short) call it send, or shipping (whatever) then on the android guest run;
rsync -ahv rick@192.168.0.174:~/shipping/ ~/shipping

Again I'm not sure about android syntax IE does it know ~ ? and obviously change rick@ip.address to your correct info.
At least it's a starting point, and maybe another way to "skin a cat".