MX Linux Forum

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

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) 2. Enable the service 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. 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)

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.

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

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.