MX Linux Forum

Posted: **Mon Jun 21, 2021 2:55 am**

I installed snapd with this command:

sudo apt install snapd

and then also run this:

Code: Select all

sudo snap install core

After that i installed Anbox with this command:

Code: Select all

snap install --devmode --edge anbox

But when i try to launch the Anbox Application Manager from the start menu nothing happens. What am i doing wrong?

System info:

Code: Select all

System:    Host: <filter> Kernel: 4.19.0-17-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 
           parameters: BOOT_IMAGE=/vmlinuz-4.19.0-17-amd64 
           root=UUID=<filter> ro quiet splash 
           init=/lib/systemd/systemd 
           Desktop: Xfce 4.14.2 tk: Gtk 3.24.5 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0 
           Distro: MX-19.4_x64 patito feo November 11  2020 base: Debian GNU/Linux 10 (buster) 
Machine:   Type: Laptop System: Hewlett-Packard product: HP EliteBook 8560w v: A0001D02 
           serial: <filter> Chassis: type: 10 serial: <filter> 
           Mobo: Hewlett-Packard model: 1631 v: KBC Version 01.39 serial: <filter> 
           BIOS: Hewlett-Packard v: 68SVD Ver. F.22 date: 01/05/2012 
Battery:   ID-1: BAT0 charge: 6.9 Wh condition: 9.9/9.9 Wh (100%) volts: 16.9/14.8 
           model: Hewlett-Packard Primary type: Li-ion serial: <filter> status: Unknown 
CPU:       Topology: Quad Core model: Intel Core i7-2820QM bits: 64 type: MT MCP 
           arch: Sandy Bridge family: 6 model-id: 2A (42) stepping: 7 microcode: 2F 
           L2 cache: 8192 KiB 
           flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 36718 
           Speed: 1628 MHz min/max: 800/3400 MHz Core speeds (MHz): 1: 1628 2: 2364 3: 1820 
           4: 1692 5: 2063 6: 1841 7: 1786 8: 2159 
           Vulnerabilities: Type: itlb_multihit status: KVM: Split huge pages 
           Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable 
           Type: mds mitigation: Clear CPU buffers; SMT vulnerable 
           Type: meltdown mitigation: PTI 
           Type: spec_store_bypass 
           mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, 
           STIBP: conditional, RSB filling 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: NVIDIA GF108GLM [Quadro 1000M] vendor: Hewlett-Packard driver: nvidia 
           v: 390.143 bus ID: 01:00.0 chip ID: 10de:0dfa 
           Display: x11 server: X.Org 1.20.4 driver: nvidia 
           unloaded: fbdev,modesetting,nouveau,vesa alternate: nv resolution: 1920x1080~60Hz 
           OpenGL: renderer: Quadro 1000M/PCIe/SSE2 v: 4.6.0 NVIDIA 390.143 direct render: Yes 
Audio:     Device-1: Intel 6 Series/C200 Series Family High Definition Audio 
           vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus ID: 00:1b.0 
           chip ID: 8086:1c20 
           Device-2: NVIDIA GF108 High Definition Audio vendor: Hewlett-Packard 
           driver: snd_hda_intel v: kernel bus ID: 01:00.1 chip ID: 10de:0bea 
           Sound Server: ALSA v: k4.19.0-17-amd64 
Network:   Device-1: Intel 82579LM Gigabit Network vendor: Hewlett-Packard driver: e1000e 
           v: 3.2.6-k port: 5020 bus ID: 00:19.0 chip ID: 8086:1502 
           IF: eth0 state: down mac: <filter> 
           Device-2: Intel Centrino Advanced-N 6205 [Taylor Peak] driver: iwlwifi v: kernel 
           port: 4000 bus ID: 25:00.0 chip ID: 8086:0085 
           IF: wlan0 state: up mac: <filter> 
           IF-ID-1: anbox0 state: unknown speed: N/A duplex: N/A mac: <filter> 
           IF-ID-2: vboxnet0 state: down mac: <filter> 
Drives:    Local Storage: total: 1.02 TiB used: 892.05 GiB (85.5%) 
           ID-1: /dev/sda vendor: Kingston model: SA400S37120G size: 111.79 GiB block size: 
           physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: B1D1 scheme: MBR 
           ID-2: /dev/sdb vendor: HGST (Hitachi) model: HTS541010B7E610 size: 931.51 GiB 
           block size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s rotation: 5400 rpm 
           serial: <filter> rev: 1A01 scheme: MBR 
Partition: ID-1: / raw size: 62.46 GiB size: 61.23 GiB (98.03%) used: 52.09 GiB (85.1%) fs: ext4 
           dev: /dev/dm-0 
           ID-2: /boot raw size: 500.0 MiB size: 476.2 MiB (95.24%) used: 292.8 MiB (61.5%) 
           fs: ext4 dev: /dev/sda5 
Sensors:   System Temperatures: cpu: 52.0 C mobo: N/A gpu: nvidia temp: 51 C 
           Fan Speeds (RPM): N/A 
Repos:     No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list 
           1: deb [arch=amd64] https://brave-browser-apt-release.s3.brave.com/ buster main
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian buster-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian buster main contrib non-free
           2: deb http://deb.debian.org/debian-security buster/updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/google-earth-pro.list 
           1: deb [arch=amd64] http://dl.google.com/linux/earth/deb/ stable main
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb https://mirrors.netix.net/mx/MX-Packages/mx/repo/ buster main non-free
           No active apt repos in: /etc/apt/sources.list.d/various.list 
           Active apt repos in: /etc/apt/sources.list.d/vivaldi.list 
           1: deb http://repo.vivaldi.com/stable/deb/ stable main
Info:      Processes: 320 Uptime: 7h 56m Memory: 7.74 GiB used: 2.55 GiB (32.9%) Init: systemd 
           v: 241 runlevel: 5 default: 5 Compilers: gcc: 8.3.0 alt: 8 Shell: quick-system-in 
           running in: quick-system-in inxi: 3.0.36

Posted: **Mon Jun 21, 2021 3:31 am**

Snap packages require systemd. Consult the FAQ for more information.

Posted: **Mon Jun 21, 2021 4:27 am**

Check out dolphin_oracle's instructional videos on systemd and snaps:

https://www.youtube.com/watch?v=qep28UOaWrc

https://www.youtube.com/watch?v=e-DrDXNnzlg

Posted: **Mon Jun 21, 2021 7:43 am**

JayM wrote: Mon Jun 21, 2021 3:31 am Snap packages require systemd. Consult the FAQ for more information.

I know, i am booting with systemd enabled.

Posted: **Mon Jun 21, 2021 7:52 am**

Then open a terminal and launch it there, so any error messages will be visible.

Posted: **Mon Jun 21, 2021 8:55 am**

How to launch it from terminal? I added /snap/bin to my $PATH, but if i type anbox in terminal it shows the usage instructions. The same happens if i type 'snap run anbox'.

Posted: **Mon Jun 21, 2021 9:32 am**

Did you try to just install it from the repos? That would be the first method we recommend. Here's a simulated install on MX-19.4

Code: Select all

sudo apt install anbox -s
[sudo] password for jb: 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following additional packages will be installed:
  libboost-log1.67.0 libboost-program-options1.67.0 libboost-regex1.67.0 libboost-serialization1.67.0 liblxc1
  libsdl2-image-2.0-0 lxc
Suggested packages:
  lvm2 python3-lxc
Recommended packages:
  dbus-user-session bridge-utils debootstrap libpam-cgfs lxcfs lxc-templates uidmap
The following NEW packages will be installed:
  anbox libboost-log1.67.0 libboost-program-options1.67.0 libboost-regex1.67.0 libboost-serialization1.67.0 liblxc1
  libsdl2-image-2.0-0 lxc
0 upgraded, 8 newly installed, 0 to remove and 0 not upgraded.
Inst libboost-regex1.67.0 (1.67.0-13+deb10u1 Debian:10.10/stable [amd64])
Inst libboost-log1.67.0 (1.67.0-13+deb10u1 Debian:10.10/stable [amd64])
Inst libboost-program-options1.67.0 (1.67.0-13+deb10u1 Debian:10.10/stable [amd64])
Inst libboost-serialization1.67.0 (1.67.0-13+deb10u1 Debian:10.10/stable [amd64])
Inst liblxc1 (1:3.1.0+really3.0.3-8 Debian:10.10/stable [amd64])
Inst libsdl2-image-2.0-0 (2.0.4+dfsg1-1+deb10u1 Debian:10.10/stable [amd64])
Inst lxc (1:3.1.0+really3.0.3-8 Debian:10.10/stable [amd64])
Inst anbox (0.0~git20190124-1 Debian:10.10/stable [amd64])
Conf libboost-regex1.67.0 (1.67.0-13+deb10u1 Debian:10.10/stable [amd64])
Conf libboost-log1.67.0 (1.67.0-13+deb10u1 Debian:10.10/stable [amd64])
Conf libboost-program-options1.67.0 (1.67.0-13+deb10u1 Debian:10.10/stable [amd64])
Conf libboost-serialization1.67.0 (1.67.0-13+deb10u1 Debian:10.10/stable [amd64])
Conf liblxc1 (1:3.1.0+really3.0.3-8 Debian:10.10/stable [amd64])
Conf libsdl2-image-2.0-0 (2.0.4+dfsg1-1+deb10u1 Debian:10.10/stable [amd64])
Conf lxc (1:3.1.0+really3.0.3-8 Debian:10.10/stable [amd64])
Conf anbox (0.0~git20190124-1 Debian:10.10/stable [amd64])

Posted: **Mon Jun 21, 2021 10:39 am**

Yes, before i tried the snap version i tried the version in mx repo, but if i try to launch anbox from the start menu it just shows the anbox windows and freezes.

Posted: **Mon Jun 21, 2021 8:54 pm**

OK. I installed it from the repos, rebooted into systemd and saw exactly what you describe above when I tried to launch it from the Menu. Then I opened a terminal and entered just

Code: Select all

anbox

That produced a list of commands to use.

Code: Select all

anbox
Unknown command 'run'
NAME:
    anbox - anbox

USAGE:
    anbox [command options] [arguments...]

COMMANDS:
    wait-ready                     Wait until the Android system has successfully booted                                               
    check-features                 Check that the host system supports all necessary features                                          
    version                        print the version of the daemon                                                                     
    help                           prints a short help message                                                                         
    launch                         Launch an Activity by sending an intent                                                             
    session-manager                Run the the anbox session manager                                                                   
    system-info                    Print various information about the system we're running on

I tried system-info and check-features, and those worked correctly. Then I tried session-manager:

Code: Select all

 anbox session-manager
[ 2021-06-22 00:43:58] [session_manager.cpp:130@operator()] Failed to start as either binder or ashmem kernel drivers are not loaded

That manager also seems to show up in the launch command (as appmgr) in Whisker menu:

Code: Select all

anbox launch --package=org.anbox.appmgr --component=org.anbox.appmgr.AppViewActivity

I tried to load those modules but they are not installed; then looked for the modules binder and ashmem, but neither is in the MX 19.4 repos. I finally googled those names and ended up in the anbox documentation: https://docs.anbox.io/userguide/install ... dules.html

I'm done. We now know that anbox needs kernel modules (not sure if both are needed) that are found in an Ubuntu PPA or can be compiled from a GitHub repo. The directions are there so it's up to you whether you want to proceed or not.

Hope this helps--good luck.

Posted: **Tue Jun 22, 2021 2:11 am**

Thanks for the effort. Will see what i can do making anbox work.

Posted: **Tue Jun 22, 2021 3:41 pm**

Seems like you need to do it the Debian way and forget about snaps: https://dev.to/sbellone/how-to-install- ... ebian-1hjd

I'll see if I can backport the upstream Debian version.

Posted: **Tue Jun 22, 2021 3:48 pm**

We still would need the two modules (binder and ashmem) @Stevo. See above.

Posted: **Tue Jun 22, 2021 4:51 pm**

The Readme file says they are already included in Debian kernels since 4.17.

Code: Select all

In order to run Android system inside container, you need two kernel
modules: ashmem_linux and binder_linux. Since Debian kernel 4.17, these
two modules are enabled. You can find theme at,
/lib/modules/`uname -r`/kernel/drivers/android/binder_linux.ko and
/lib/modules/`uname -r`/kernel/drivers/staging/android/ashmem_linux.ko.
.
If your kernel doesn't have these two modules, you can follow upstream
instructions to install them with DKMS. Please see
<https://github.com/anbox/anbox-modules/>.
.
Run following commands to check if you have the kernel modules:
.
  modinfo binder_linux
  modinfo ashmem_linux

I've found that you have to precede modinfo with sudo or run it as root. Doesn't seem that the Liquorix kernels enable those, though. Since it has something mysterious to do with containers and namespaces, it may not be as simple as just copying the Debian config for those. The Readme still recommends starting with systemd for the anbox service, also.

I've almost finished the backport of Bullseye's anbox for MX 19 test..armhf version is building.

Posted: **Tue Jun 22, 2021 4:57 pm**

I saw that, but the app isn't seeing the modules.

Posted: **Tue Jun 22, 2021 5:00 pm**

Jerry3904 wrote: Tue Jun 22, 2021 4:57 pm I saw that, but the app isn't seeing the modules.

The snap version or the native Debian version? It also won't do anything without the android img file manually downloaded and installed, at least that's what the guide and Readme say.

Posted: **Tue Jun 22, 2021 6:35 pm**

Look at my long post above, which starts with the repo version.

Posted: **Wed Jun 23, 2021 1:49 pm**

I just installed and tested the test repo version on our 5.10 kernel booted with systemd, also installing the android.img file manually per the guide.

Code: Select all

⌁0% steve@msigp63:~ $  ls -1 /dev/{ashmem,binder}
ls: cannot access '/dev/ashmem': No such file or directory
ls: cannot access '/dev/binder': No such file or directory
⌁0% steve@msigp63:~ 2 $ sudo modprobe ashmem_linux
[sudo] password for steve: 
⌁0% steve@msigp63:~ $ sudo modprobe binder_linux
⌁0% steve@msigp63:~ $ ls -1 /dev/{ashmem,binder}
/dev/ashmem
/dev/binder
⌁0% steve@msigp63:~ $

As seen above, I also had to manually load the two modules per the guide to get them to work. After that, I restarted the service and then:

Code: Select all

anbox launch --package=org.anbox.appmgr --component=org.anbox.appmgr.AppViewActivity

and got an Android desktop--the web browser even works.

IDK if our adb needs updating in order to install apks per the guide. I would appreciate if anyone else that gets it working follow the guide to try and install Fdroid.

Posted: **Wed Jun 23, 2021 6:17 pm**

I installed the stock Buster android tools, and then followed the commands to wget the Fdroid apk file, and then abd to install it, after which it appeared in Android and I was able to use it to get and install more free android apps.

I'd like to get some feedback if others can't do the same, otherwise it can be marked solved.

Posted: **Wed Jun 23, 2021 6:50 pm**

I'm hoping this might go into MXPI to get all that into a script for MX-21

Posted: **Wed Jun 23, 2021 6:54 pm**

I rebooted to the same kernel with systemd, and this time did not have to modprobe the two modules to get Anbox to start from the menu. We may have to create our own init script to get the service to start from sysvinit, though.

I'll take a look at the PPA for those that aren't using kernels that already include the modules, too.

Posted: **Thu Jun 24, 2021 1:22 pm**

I'm going to attempt to see how difficult it would be to have the Liquorix kernel build those modules by default. If it's simple, odds are that Mr Damentz would make that the default Liquorix configuration upon request.

Posted: **Thu Jun 24, 2021 2:01 pm**

The Liquorix kernel does build the two drivers, but into the kernel itself instead of as modules. I'll switch that from "y" to "m" in the config to see if that makes any difference. There may also be a different procedure for anbox if it's built into the kernel.

BTW, the ubuntu PPA seems dead, since Ubuntu's kernels also have had the drivers as modules for several years now.

Posted: **Thu Jun 24, 2021 3:09 pm**

Thanks for the effort! It would be cool if we could get it to work without hassle in MX-21

Posted: **Sun Oct 31, 2021 4:35 am**

Well MX-21 is out and it still don't work. It would be nice to have a hassle free anbox installation that would just work, I mean Windows and Mac has android apps working on their OS and yet Android is based on Linux and we still don't have a reliable way to use the Android apps yet. oh well, no wonder so many people don't want to switch to linux. smh

Posted: **Sun Oct 31, 2021 5:04 am**

mike lovin wrote: Sun Oct 31, 2021 4:35 am Well MX-21 is out and it still don't work. It would be nice to have a hassle free anbox installation that would just work, I mean Windows and Mac has android apps working on their OS and yet Android is based on Linux and we still don't have a reliable way to use the Android apps yet. oh well, no wonder so many people don't want to switch to linux. smh

Wait, I thought you volunteered to make this happen already, what’s the hold up?

No wonder people don’t want to do more in their free time to do things for people for free with comments like this. Asking nicely gets better responses.

And Android uses a highly modified Linux kernel, that doesn’t mean everything else is based on the GNU/Linux ecosystem.

Posted: **Sun Oct 31, 2021 5:30 am**

SwampRabbit wrote: Sun Oct 31, 2021 5:04 am
Wait, I thought you volunteered to make this happen already, what’s the hold up?

No wonder people don’t want to do more in their free time to do things for people for free with comments like this. Asking nicely gets better responses.

And Android uses a highly modified Linux kernel, that doesn’t mean everything else is based on the GNU/Linux ecosystem.

some people (a minority in fairness) come across so bally entitled ......

at the risk of sounding overly sycophantic and in the absence of a 'like'' button...... i very like this post

as an aside, i maintain a small 50 gig partition on windows on one of my machines for 2 apps that i can't get to work on linux ... one of those is bluestacks ..... as much as i would prefer to be windows free, dual booting (very occasionally) resolves that particular issue for me

Posted: **Wed Mar 23, 2022 7:08 pm**

junoluna wrote: Sun Oct 31, 2021 5:30 am as an aside, i maintain a small 50 gig partition on windows on one of my machines for 2 apps that i can't get to work on linux ... one of those is bluestacks ..... as much as i would prefer to be windows free, dual booting (very occasionally) resolves that particular issue for me

Curiosity,

Is there a reason a Windows virtual machine (VM) couldn't/wouldn't work instead?

(I have a Win VM solely to use a printer, so I feel your pain on the "apps that i can't get to work on linux")

Best,
Michael

Posted: **Wed Mar 23, 2022 7:15 pm**

Stevo wrote: Wed Jun 23, 2021 6:17 pm I installed the stock Buster android tools, and then followed the commands to wget the Fdroid apk file, and then abd to install it, after which it appeared in Android and I was able to use it to get and install more free android apps.

I'd like to get some feedback if others can't do the same, otherwise it can be marked solved.

Hey Stevo,

Would you consider doing a mini-writeup on what you did to get Anbox to work on MX21? Just copying the code you executed and linking to sites/pages you used as sources should be plenty. (Not that a complete MXPI entry wouldn't be welcomed

)

Best Regards,
Michael

Posted: **Thu Mar 24, 2022 1:22 pm**

Michael-IDA wrote: Wed Mar 23, 2022 7:15 pm
Stevo wrote: Wed Jun 23, 2021 6:17 pm I'd like to get some feedback if others can't do the same, otherwise it can be marked solved.
Hey Stevo,

Would you consider doing a mini-writeup...

Ah, never mind, Anbox seems like it was abandoned in 2018. Other than Fdroid, no .apk I downloaded (even ones that I could successfully transfer and install on my phone) would install into Anbox.

The link provide earlier, https://dev.to/sbellone/how-to-install- ... ebian-1hjd , works well enough to get Anbox setup and running. My details below (if you want to cut/paste stuff).

Best,
Michael

Oracle VM: 4 CPU, 8 GB RAM, 400 GB HD
MX-21 (have to boot into systemd)

Code: Select all

user@mx:~
$ sudo apt install anbox
[sudo] password for user: 
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
  bridge-utils libboost-log1.74.0 libboost-program-options1.74.0 libboost-regex1.74.0 liblxc1
  libsdbus-c++0 libsdl2-image-2.0-0 lxc
Suggested packages:
  python3-lxc
Recommended packages:
  apparmor debootstrap libpam-cgfs lxcfs lxc-templates uidmap
The following NEW packages will be installed:
  anbox bridge-utils libboost-log1.74.0 libboost-program-options1.74.0 libboost-regex1.74.0
  liblxc1 libsdbus-c++0 libsdl2-image-2.0-0 lxc
0 upgraded, 9 newly installed, 0 to remove and 0 not upgraded.
Need to get 4,721 kB of archives.
After this operation, 33.1 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://deb.debian.org/debian bullseye/main amd64 liblxc1 amd64 1:4.0.6-2 [324 kB]
Get:2 http://deb.debian.org/debian bullseye/main amd64 bridge-utils amd64 1.7-1 [37.9 kB]
Get:3 http://deb.debian.org/debian bullseye/main amd64 lxc amd64 1:4.0.6-2 [2,010 kB]
Get:4 http://deb.debian.org/debian bullseye/main amd64 libboost-regex1.74.0 amd64 1.74.0-9 [516 kB]
Get:5 http://deb.debian.org/debian bullseye/main amd64 libboost-log1.74.0 amd64 1.74.0-9 [619 kB]
Get:6 http://deb.debian.org/debian bullseye/main amd64 libboost-program-options1.74.0 amd64 1.74.0-9 [356 kB]
Get:7 http://deb.debian.org/debian bullseye/main amd64 libsdbus-c++0 amd64 0.8.3-4 [53.9 kB]
Get:8 http://deb.debian.org/debian bullseye/main amd64 libsdl2-image-2.0-0 amd64 2.0.5+dfsg1-2 [67.0 kB]
Get:9 http://deb.debian.org/debian bullseye/contrib amd64 anbox amd64 0.0~git20210106-1 [737 kB]
Fetched 4,721 kB in 1s (3,753 kB/s)
Preconfiguring packages ...
Selecting previously unselected package liblxc1:amd64.
(Reading database ... 318689 files and directories currently installed.)
Preparing to unpack .../0-liblxc1_1%3a4.0.6-2_amd64.deb ...
Unpacking liblxc1:amd64 (1:4.0.6-2) ...
Selecting previously unselected package bridge-utils.
Preparing to unpack .../1-bridge-utils_1.7-1_amd64.deb ...
Unpacking bridge-utils (1.7-1) ...
Selecting previously unselected package lxc.
Preparing to unpack .../2-lxc_1%3a4.0.6-2_amd64.deb ...
Unpacking lxc (1:4.0.6-2) ...
Selecting previously unselected package libboost-regex1.74.0:amd64.
Preparing to unpack .../3-libboost-regex1.74.0_1.74.0-9_amd64.deb ...
Unpacking libboost-regex1.74.0:amd64 (1.74.0-9) ...
Selecting previously unselected package libboost-log1.74.0.
Preparing to unpack .../4-libboost-log1.74.0_1.74.0-9_amd64.deb ...
Unpacking libboost-log1.74.0 (1.74.0-9) ...
Selecting previously unselected package libboost-program-options1.74.0:amd64.
Preparing to unpack .../5-libboost-program-options1.74.0_1.74.0-9_amd64.deb ...
Unpacking libboost-program-options1.74.0:amd64 (1.74.0-9) ...
Selecting previously unselected package libsdbus-c++0.
Preparing to unpack .../6-libsdbus-c++0_0.8.3-4_amd64.deb ...
Unpacking libsdbus-c++0 (0.8.3-4) ...
Selecting previously unselected package libsdl2-image-2.0-0:amd64.
Preparing to unpack .../7-libsdl2-image-2.0-0_2.0.5+dfsg1-2_amd64.deb ...
Unpacking libsdl2-image-2.0-0:amd64 (2.0.5+dfsg1-2) ...
Selecting previously unselected package anbox.
Preparing to unpack .../8-anbox_0.0~git20210106-1_amd64.deb ...
Unpacking anbox (0.0~git20210106-1) ...
Setting up libsdl2-image-2.0-0:amd64 (2.0.5+dfsg1-2) ...
Setting up libboost-program-options1.74.0:amd64 (1.74.0-9) ...
Setting up liblxc1:amd64 (1:4.0.6-2) ...
Setting up libsdbus-c++0 (0.8.3-4) ...
Setting up libboost-regex1.74.0:amd64 (1.74.0-9) ...
Setting up bridge-utils (1.7-1) ...
Setting up libboost-log1.74.0 (1.74.0-9) ...
Setting up lxc (1:4.0.6-2) ...
Created symlink /etc/systemd/system/multi-user.target.wants/lxc-net.service → /lib/systemd/system/lx
c-net.service.
Created symlink /etc/systemd/system/multi-user.target.wants/lxc.service → /lib/systemd/system/lxc.se
rvice.
Setting up anbox (0.0~git20210106-1) ...
Created symlink /etc/systemd/user/default.target.wants/anbox-session-manager.service → /usr/lib/syst
emd/user/anbox-session-manager.service.
Created symlink /etc/systemd/system/multi-user.target.wants/anbox-container-manager.service → /lib/s
ystemd/system/anbox-container-manager.service.
Processing triggers for desktop-file-utils (0.26-1) ...
Processing triggers for libc-bin (2.31-13+deb11u2) ...
Processing triggers for man-db (2.9.4-2) ...
Processing triggers for mailcap (3.69) ...
user@mx:~
$ ls -1 /dev/{ashmem,binder}
ls: cannot access '/dev/ashmem': No such file or directory
ls: cannot access '/dev/binder': No such file or directory
user@mx:~
$ which modprobe
/sbin/modprobe
user@mx:~
$ sudo modprobe ashmem_linux
user@mx:~
$ sudo modprobe binder_linux
user@mx:~
$ ls -1 /dev/{ashmem,binder}
/dev/ashmem
/dev/binder
user@mx:~
$ anbox session-manager
[ 2022-03-24 03:26:46] [daemon.cpp:61@Run] Failed to connect to socket /run/anbox-container.socket: No such file or directory
user@mx:~
$ ll Do
Documents/ Downloads/ 
user@mx:~
$ ll Downloads/
total 274M
-rw-r--r-- 1 user user    0 Mar 23 23:29 android_amd64.img
-rw------- 1 user user 274M Mar 23 23:30 android_amd64.img.part
user@mx:~
$ ll Downloads/
total 311M
-rw-r--r-- 1 user user 311M Mar 23 23:30 android_amd64.img
user@mx:~
$ sudo mv ~/Downloads/android_amd64.img /var/lib/anbox/android.img
user@mx:~
$ sudo service anbox-container-manager restart
anbox-container-manager: unrecognized service
user@mx:~
$ anbox session-manager
[ 2022-03-24 03:31:33] [daemon.cpp:61@Run] Failed to connect to socket /run/anbox-container.socket: No such file or directory
user@mx:~
$ anbox launch --package=org.anbox.appmgr --component=org.anbox.appmgr.AppViewActivity

[ 2022-03-24 03:35:40] [daemon.cpp:61@Run] [org.freedesktop.DBus.Error.ServiceUnknown] The name org.anbox was not provided by any .service files
user@mx:~
$ 

user@mx:~
$ sudo apt install android-tools-adb
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Note, selecting 'adb' instead of 'android-tools-adb'
The following additional packages will be installed:
  android-libadb android-libbase android-libboringssl android-libcrypto-utils android-libcutils
  android-liblog android-sdk-platform-tools-common
The following NEW packages will be installed:
  adb android-libadb android-libbase android-libboringssl android-libcrypto-utils
  android-libcutils android-liblog android-sdk-platform-tools-common
0 upgraded, 8 newly installed, 0 to remove and 0 not upgraded.
Need to get 1,021 kB of archives.
After this operation, 3,057 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://deb.debian.org/debian bullseye/main amd64 android-liblog amd64 1:10.0.0+r36-7 [44.4 kB]
Get:2 http://deb.debian.org/debian bullseye/main amd64 android-libbase amd64 1:10.0.0+r36-7 [41.5 kB]
Get:3 http://deb.debian.org/debian bullseye/main amd64 android-libboringssl amd64 10.0.0+r36-1 [612 kB]
Get:4 http://deb.debian.org/debian bullseye/main amd64 android-libcrypto-utils amd64 1:10.0.0+r36-7 [12.3 kB]
Get:5 http://deb.debian.org/debian bullseye/main amd64 android-libcutils amd64 1:10.0.0+r36-7 [33.3 kB]
Get:6 http://deb.debian.org/debian bullseye/main amd64 android-libadb amd64 1:10.0.0+r36-7 [165 kB]
Get:7 http://deb.debian.org/debian bullseye/main amd64 android-sdk-platform-tools-common all 28.0.2+3 [8,020 B]
Get:8 http://deb.debian.org/debian bullseye/main amd64 adb amd64 1:10.0.0+r36-7 [104 kB]
Fetched 1,021 kB in 0s (6,113 kB/s)
Selecting previously unselected package android-liblog.
(Reading database ... 318993 files and directories currently installed.)
Preparing to unpack .../0-android-liblog_1%3a10.0.0+r36-7_amd64.deb ...
Unpacking android-liblog (1:10.0.0+r36-7) ...
Selecting previously unselected package android-libbase.
Preparing to unpack .../1-android-libbase_1%3a10.0.0+r36-7_amd64.deb ...
Unpacking android-libbase (1:10.0.0+r36-7) ...
Selecting previously unselected package android-libboringssl.
Preparing to unpack .../2-android-libboringssl_10.0.0+r36-1_amd64.deb ...
Unpacking android-libboringssl (10.0.0+r36-1) ...
Selecting previously unselected package android-libcrypto-utils.
Preparing to unpack .../3-android-libcrypto-utils_1%3a10.0.0+r36-7_amd64.deb ...
Unpacking android-libcrypto-utils (1:10.0.0+r36-7) ...
Selecting previously unselected package android-libcutils.
Preparing to unpack .../4-android-libcutils_1%3a10.0.0+r36-7_amd64.deb ...
Unpacking android-libcutils (1:10.0.0+r36-7) ...
Selecting previously unselected package android-libadb.
Preparing to unpack .../5-android-libadb_1%3a10.0.0+r36-7_amd64.deb ...
Unpacking android-libadb (1:10.0.0+r36-7) ...
Selecting previously unselected package android-sdk-platform-tools-common.
Preparing to unpack .../6-android-sdk-platform-tools-common_28.0.2+3_all.deb ...
Unpacking android-sdk-platform-tools-common (28.0.2+3) ...
Selecting previously unselected package adb.
Preparing to unpack .../7-adb_1%3a10.0.0+r36-7_amd64.deb ...
Unpacking adb (1:10.0.0+r36-7) ...
Setting up android-sdk-platform-tools-common (28.0.2+3) ...
Setting up android-liblog (1:10.0.0+r36-7) ...
Setting up android-libboringssl (10.0.0+r36-1) ...
Setting up android-libcrypto-utils (1:10.0.0+r36-7) ...
Setting up android-libbase (1:10.0.0+r36-7) ...
Setting up android-libcutils (1:10.0.0+r36-7) ...
Setting up android-libadb (1:10.0.0+r36-7) ...
Setting up adb (1:10.0.0+r36-7) ...
Processing triggers for man-db (2.9.4-2) ...
Processing triggers for libc-bin (2.31-13+deb11u2) ...
user@mx:~
$ 


=== Reboot, select systemd in Advanced boot optoins ===


user@mx:~/Downloads
$ wget https://f-droid.org/F-Droid.apk
--2022-03-23 23:48:04--  https://f-droid.org/F-Droid.apk
Resolving f-droid.org (f-droid.org)... 149.202.95.241, 148.251.140.42
Connecting to f-droid.org (f-droid.org)|149.202.95.241|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 8010257 (7.6M) [application/vnd.android.package-archive]
Saving to: ‘F-Droid.apk’

F-Droid.apk              100%[==================================>]   7.64M  6.79MB/s    in 1.1s    

2022-03-23 23:48:08 (6.79 MB/s) - ‘F-Droid.apk’ saved [8010257/8010257]

user@mx:~/Downloads
$ adb install F-Droid.apk
* daemon not running; starting now at tcp:5037
* daemon started successfully
Performing Streamed Install
Success

user@mx:~/Downloads
$ adb install bermuda-adventures-island-farm-games-v0-4-0-mod.apk 
* daemon not running; starting now at tcp:5037
* daemon started successfully
Performing Streamed Install
adb: failed to install bermuda-adventures-island-farm-games-v0-4-0-mod.apk: Failure [INSTALL_FAILED_NO_MATCHING_ABIS: Failed to extract native libraries, res=-113]
user@mx:~/Downloads
$ sudo adb install bermuda-adventures-island-farm-games-v0-4-0-mod.apk 
[sudo] password for user: 
Performing Streamed Install
adb: failed to install bermuda-adventures-island-farm-games-v0-4-0-mod.apk: Failure [INSTALL_FAILED_NO_MATCHING_ABIS: Failed to extract native libraries, res=-113]

Posted: **Tue Oct 04, 2022 10:48 am**

I wonder how you got it to run like this.
If you look closely at your console output you'll see that the container service is not actually available:

Code: Select all

$ sudo service anbox-container-manager restart
anbox-container-manager: unrecognized service
user@mx:~
$ anbox session-manager
[ 2022-03-24 03:31:33] [daemon.cpp:61@Run] Failed to connect to socket /run/anbox-container.socket: No such file or directory

I'm facing those same messages and running anbox afterwards does not succeed - it's stuck at `Starting...` just the same.

I was able to locacte the service file at

Code: Select all

/etc/systemd/system/multi-user.target.wants/anbox-container-manager.service

Does it perhaps require switching to systemd/systemctl as the init system? If that's the case either way then the snap installation seems like the simpler option.
But I'm unsure what switching the init system entails long-term and would rather not risk it.

Or maybe this can be converted to init.d properly? For this I could use some help.
Here's the contents of the `anbox-container-manager.service` file:

Code: Select all

[Unit]
Description=Anbox Container Manager
Documentation=man:anbox(1)
After=network.target
Wants=network.target
ConditionPathExists=/var/lib/anbox/android.img

[Service]
ExecStartPre=/sbin/modprobe ashmem_linux
ExecStartPre=/sbin/modprobe binder_linux
ExecStartPre=/usr/share/anbox/anbox-bridge.sh start
ExecStart=/usr/bin/anbox container-manager --daemon --privileged --data-path=/var/lib/anbox
ExecStopPost=/usr/share/anbox/anbox-bridge.sh stop

[Install]
WantedBy=multi-user.target

The accompanying user service `/etc/systemd/user/default.target.wants/anbox-session-manager.service`, which merely runs `anbox session-manager`, seems to be optional:

Code: Select all

$ env ANBOX_LOG_LEVEL=debug anbox launch --package=org.anbox.appmgr --component=org.anbox.appmgr.AppViewActivity
[ 2022-10-04 14:23:32] [launch.cpp:168@operator()] Session manager is not yet running, trying to start it
[ 2022-10-04 14:23:32] [launch.cpp:117@launch_session_manager] Started session manager, will now try to connect ..   <--------
[ 2022-10-04 14:23:32] [splash_screen.cpp:55@SplashScreen] Window has no associated renderer yet, creating one ...
[ 2022-10-04 14:24:22] [daemon.cpp:61@Run] [org.freedesktop.DBus.Error.ServiceUnknown] The name org.anbox was not provided by any .service files

Here's my QSI for completeness:

Code: Select all

System:    Kernel: 5.16.0-3mx-amd64 x86_64 bits: 64 compiler: gcc v: 10.2.1 
           parameters: BOOT_IMAGE=/vmlinuz-5.16.0-3mx-amd64 root=UUID=<filter> ro quiet splash i915.force_probe=46a6 
           Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm 4.16.1 vt: 7 dm: LightDM 1.26.0 
           Distro: MX-21.2.1_ahs_x64 Wildflower November 22  2021 base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Laptop System: Micro-Star product: Raider GE76 12UGS v: REV:1.0 serial: <filter> Chassis: type: 10 
           serial: <filter> 
           Mobo: Micro-Star model: MS-17K4 v: REV:1.0 serial: <filter> UEFI: American Megatrends LLC. v: E17K4IMS.201 
           date: 12/08/2021 
Battery:   ID-1: BAT1 charge: 89.1 Wh (94.9%) condition: 93.9/95.0 Wh (98.8%) volts: 16.9 min: 15.2 model: MSI BIF0_9 
           type: Li-ion serial: N/A status: Unknown 
CPU:       Info: 10-Core model: 12th Gen Intel Core i7-12700H bits: 64 type: MT MCP arch: Alder Lake family: 6 
           model-id: 9A (154) stepping: 3 microcode: 41C cache: L2: 24 MiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 107520 
           Speed: 486 MHz min/max: 400/4600 MHz Core speeds (MHz): 1: 486 2: 464 3: 427 4: 427 5: 400 6: 400 7: 400 8: 400 
           9: 400 10: 400 11: 400 12: 400 13: 457 14: 495 15: 482 16: 448 17: 491 18: 495 19: 518 20: 501 
           Vulnerabilities: Type: itlb_multihit status: Not affected 
           Type: l1tf status: Not affected 
           Type: mds status: Not affected 
           Type: meltdown status: Not affected 
           Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Enhanced IBRS, IBPB: conditional, RSB filling 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel Alder Lake-P Integrated Graphics vendor: Micro-Star MSI driver: i915 v: kernel bus-ID: 00:02.0 
           chip-ID: 8086:46a6 class-ID: 0300 
           Device-2: NVIDIA GA104 [Geforce RTX 3070 Ti Laptop GPU] vendor: Micro-Star MSI driver: nvidia v: 510.73.08 
           bus-ID: 01:00.0 chip-ID: 10de:24a0 class-ID: 0300 
           Device-3: Acer Integrated Camera type: USB driver: N/A bus-ID: 1-7:3 chip-ID: 5986:1160 class-ID: 0e02 
           serial: <filter> 
           Display: x11 server: X.Org 1.20.14 compositor: xfwm4 v: 4.16.1 driver: loaded: modesetting,nvidia 
           unloaded: fbdev,nouveau,vesa alternate: nv display-ID: :0.0 screens: 1 
           Screen-1: 0 s-res: 2560x1440 s-dpi: 96 s-size: 677x381mm (26.7x15.0") s-diag: 777mm (30.6") 
           Monitor-1: eDP-1 res: 2560x1440 dpi: 171 size: 381x214mm (15.0x8.4") diag: 437mm (17.2") 
           OpenGL: renderer: Mesa Intel Graphics (ADL GT2) v: 4.6 Mesa 22.0.5 direct render: Yes 
Audio:     Device-1: Intel Alder Lake PCH-P High Definition Audio vendor: Micro-Star MSI driver: sof-audio-pci-intel-tgl 
           alternate: snd_hda_intel,snd_sof_pci_intel_tgl bus-ID: 00:1f.3 chip-ID: 8086:51c8 class-ID: 0401 
           Device-2: NVIDIA GA104 High Definition Audio vendor: Micro-Star MSI driver: snd_hda_intel v: kernel bus-ID: 01:00.1 
           chip-ID: 10de:228b class-ID: 0403 
           Sound Server-1: ALSA v: k5.16.0-3mx-amd64 running: yes 
           Sound Server-2: PulseAudio v: 14.2 running: yes 
Network:   Device-1: Intel Alder Lake-P PCH CNVi WiFi vendor: Rivet Networks driver: N/A modules: iwlwifi, wl port: 6000 
           bus-ID: 00:14.3 chip-ID: 8086:51f0 class-ID: 0280 
           Device-2: Realtek Killer E3000 2.5GbE vendor: Micro-Star MSI driver: r8169 v: kernel port: 3000 bus-ID: 2f:00.0 
           chip-ID: 10ec:3000 class-ID: 0200 
           IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter> 
           IF-ID-1: lxcbr0 state: down mac: <filter> 
Bluetooth: Device-1: Intel type: USB driver: btusb v: 0.8 bus-ID: 1-10:6 chip-ID: 8087:0033 class-ID: e001 
           Report: hciconfig ID: hci0 rfk-id: 0 state: down bt-service: N/A rfk-block: hardware: no software: no 
           address: <filter> 
           Info: acl-mtu: 0:0 sco-mtu: 0:0 link-mode: slave accept 
Drives:    Local Storage: total: 953.87 GiB used: 344.83 GiB (36.2%) 
           SMART Message: Unable to run smartctl. Root privileges required. 
           ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Micron model: 3400 MTFDKBA1T0TFH size: 953.87 GiB block-size: 
           physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD serial: <filter> rev: P7MA000 temp: 38.9 C 
           scheme: GPT 
Partition: ID-1: / raw-size: 645.22 GiB size: 634.02 GiB (98.26%) used: 310.16 GiB (48.9%) fs: ext4 dev: /dev/dm-0 
           maj-min: 253:0 mapped: root.fsm 
           ID-2: /boot raw-size: 512 MiB size: 487.2 MiB (95.16%) used: 269.3 MiB (55.3%) fs: ext4 dev: /dev/nvme0n1p2 
           maj-min: 259:2 
           ID-3: /boot/efi raw-size: 128 MiB size: 126 MiB (98.45%) used: 274 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p1 
           maj-min: 259:1 
           ID-4: /home raw-size: 199.98 GiB size: 195.79 GiB (97.90%) used: 34.33 GiB (17.5%) fs: ext4 dev: /dev/dm-1 
           maj-min: 253:1 mapped: 1.home.fsm 
Swap:      Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default) 
           ID-1: swap-1 type: partition size: 7.98 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/dm-2 maj-min: 253:2 
           mapped: swap 
Sensors:   System Temperatures: cpu: 53.0 C mobo: N/A 
           Fan Speeds (RPM): N/A 
Repos:     Packages: note: see --pkg apt: 2558 lib: 1416 flatpak: 0 
           No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian bullseye main contrib non-free
           2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/microsoft-prod.list 
           1: deb [arch=amd64,arm64,armhf] https://packages.microsoft.com/debian/11/prod bullseye main
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mirror.digitalnova.at/mxlinux/packages/mx/repo/ bullseye main non-free
           2: deb http://mirror.digitalnova.at/mxlinux/packages/mx/repo/ bullseye ahs
           Active apt repos in: /etc/apt/sources.list.d/nodesource.list 
           1: deb [signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_16.x bullseye main
           2: deb-src [signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_16.x bullseye main
           Active apt repos in: /etc/apt/sources.list.d/skype-stable.list 
           1: deb [arch=amd64] https://repo.skype.com/deb stable main
           Active apt repos in: /etc/apt/sources.list.d/vscode.list 
           1: deb [arch=amd64] https://packages.microsoft.com/repos/vscode stable main
Info:      Processes: 350 Uptime: 34m wakeups: 7584 Memory: 31.07 GiB used: 2.64 GiB (8.5%) Init: SysVinit v: 2.96 runlevel: 5 
           default: 5 tool: systemctl Compilers: gcc: 10.2.1 alt: 10 Shell: Bash v: 5.1.4 running-in: xfce4-terminal 
           inxi: 3.3.06

Please advise :-)

Posted: **Thu Oct 06, 2022 12:12 pm**

square wrote: Tue Oct 04, 2022 10:48 am I wonder how you got it to run like this.
If you look closely at your console output you'll see that the container service is not actually available:
I'm facing those same messages and running anbox afterwards does not succeed - it's stuck at `Starting...` just the same.
Does it perhaps require switching to systemd/systemctl as the init system? If that's the case either way then the snap installation seems like the simpler option.

Yes, it requires systemd. I was running it in a VM, re-read my full post to get the details.

square wrote: Tue Oct 04, 2022 10:48 am Or maybe this can be converted to init.d properly? For this I could use some help.
Please advise :-)

I gave up because even when I got Anbox to run, no .apk I was interested in would install. Also Anbox, unless it's changed, was abandoned 5 years ago.

If you want to play with it, my suggestion is to use either testing hardware or a VM. Then you can convert it to init or anything else without fubar-ing your primary system.

Best,
Michael

Posted: **Sun Oct 23, 2022 5:11 am**

Ok... getting it to run was quite trivial at this point.
1. Convert the unit to sysvinit using this handy tool: https://github.com/akhilvij/systemd-to- ... nverter.py (change the shebang to python2 and install python2 package)

Code: Select all

systemd-to-sysvinit-converter /etc/systemd/system/multi-user.target.wants/anbox-container-manager.service 1>/etc/init.d/anbox-container-manager.sh

2. Enable the service

Code: Select all

update-rc.d anbox-container-manager.sh defaults

3. (probably unneccessary) reboot and `service anbox-container-manager.sh restart`
4. Install F-Droid
5. Anbox didn't have an internet connection which I solved with `/usr/share/anbox/anbox-bridge.sh start`. This might have been due to step 3 above - didn't investigate.

And then I ran into the same problem you faced, trying to install some apk I got from elsewhere.

Code: Select all

Failure [INSTALL_FAILED_NO_MATCHING_ABIS: Failed to extract native libraries, res=-113]

Some quick research on this error however revealed to me that this is in fact not an anbox issue. It is an issue with the apk - it's built for a different CPU architecture.
Anbox is not a VM after all - it's as thin a layer as possible. Meaning that the android installation uses the same CPU you actually have (with x86_64 architecture).
From what I can tell the only solution to this is to get an apk built for that architecture (instead of ARM or such).
So the user's options are rather limit... Either find an x64 build (if one exists) or get the app author to also compile and ship for x64. (as seen here: https://stackoverflow.com/questions/364 ... es-res-113)

Posted: **Sat Feb 18, 2023 9:10 am**

SwampRabbit wrote: Sun Oct 31, 2021 5:04 am
mike lovin wrote: Sun Oct 31, 2021 4:35 am Well MX-21 is out and it still don't work. It would be nice to have a hassle free anbox installation that would just work, I mean Windows and Mac has android apps working on their OS and yet Android is based on Linux and we still don't have a reliable way to use the Android apps yet. oh well, no wonder so many people don't want to switch to linux. smh
Wait, I thought you volunteered to make this happen already, what’s the hold up?

No wonder people don’t want to do more in their free time to do things for people for free with comments like this. Asking nicely gets better responses.

And Android uses a highly modified Linux kernel, that doesn’t mean everything else is based on the GNU/Linux ecosystem.

What part of my statement isn't true? If you think that statement is "entitled" then you're the one with the problem, I merely stated my observations of many distros through the years. If that hurts your feelings then all I can say sorry not sorry.

Posted: **Sat Feb 18, 2023 10:27 am**

Take it to pm folks, we don't all need to enjoy this, thanks.

Posted: **Mon Feb 20, 2023 3:55 am**

Eadwine Rose wrote: Sat Feb 18, 2023 10:27 am Take it to pm folks, we don't all need to enjoy this, thanks.

You're welcome to remove any of my post if it is deemed offensive to anyone. Thanks.

MX Linux Forum

Problem installing Anbox

Problem installing Anbox

Re: Problem installing Anbox

Re: Problem installing Anbox

Re: Problem installing Anbox

Re: Problem installing Anbox

Re: Problem installing Anbox

Re: Problem installing Anbox

Re: Problem installing Anbox

Re: Problem installing Anbox

Re: Problem installing Anbox

Re: Problem installing Anbox

Re: Problem installing Anbox

Re: Problem installing Anbox

Re: Problem installing Anbox

Re: Problem installing Anbox

Re: Problem installing Anbox

Re: Problem installing Anbox

Re: Problem installing Anbox

Re: Problem installing Anbox

Re: Problem installing Anbox

Re: Problem installing Anbox

Re: Problem installing Anbox

Re: Problem installing Anbox

Re: Problem installing Anbox

Re: Problem installing Anbox

Re: Problem installing Anbox

Re: Problem installing Anbox

Re: Problem installing Anbox

Re: Problem installing Anbox

Re: Problem installing Anbox

Re: Problem installing Anbox

Re: Problem installing Anbox

Re: Problem installing Anbox

Re: Problem installing Anbox

Re: Problem installing Anbox