Just type in a few commands and you'll have an image you can flash.

I've got a detailed description of what to do: https://git.erebion.eu/forgejo/erebion/sargo-temp

It is to Android apps what WINE is to Windows programs, while Waydroid is to Android apps what something between Docker and a VM would be to server software.

Actually, Waydroid is not too dissimilar from running, for example, an Ubuntu Desktop system in a Docker container on a Debian desktop system, just so you can use snap packages... Instead of installing snapd on Debian. (Not that I want snapd.)

Waydroid is more like an Android container appliance that runs a full Android system, while ATL, as the name Android Translation Layer suggests, translates functions and API calls, used by Android apps, into the appropriate methods of doing things on a regular GNU/Linux system (in contrast to an Android Runtime/Linux system), thereby being much more efficient, more comfortable to use and having the potential of integrating into the system really well.

Let me know how it goes! You might notice an issue I have missed and can then fix. :)

Definitely do! It's a lot of fun and it feels great to have Mobian on the phone instead of having old Android on it or even a phone in the trash and no phone.

No idea, but you could of course install Waydroid on Mobian. I hope Android Translation Layer (https://gitlab.com/android_translation_layer) will at some point get to a state where it is usable as the superior Waydroid alternative for many people.

No idea, but you could of course install Waydroid on Mobian. I hope Android Translation Layer (https://gitlab.com/android_translation_layer) will at some point get to a state where it is usable as the superior Waydroid alternative for many people.

Also, I keep some notes up to date over on my Forgejo instance: https://git.erebion.eu/forgejo/erebion/sargo-temp

I'm on Debian, that's the reason I asked whether anyone knows the right Debian packge. :)

For now I use the Flatpak version, but that one has other issues, it does not keep the phone awake and once it suspends Bluetooth gets disconnected as well, which is fiddly.

exciting episode, many interesting topics

Try git pull and see whether the updated fork works now. If not, I will have a closer look.

Also, I've just built it successfully. Make sure there are no left-overs from a previous run which failed.

Help would certainly be appreciated. I also have tags, but no idea how to test NFC. :)

Okay, just wrote an Ansible Playbook to roll out the workarounds, including call audio, which I just got to work, I've also tried to get Bluetooth working, but the udev rule is still broken.

https://git.erebion.eu/forgejo/erebion/sargo-temp

There are also some hastily written steps for building an image. :)

Let me know what things are unclear, I will improve this.

EDIT: Only tried using call audio via headphone jack and did not notice that internal speaker and mic currently do nothing, so I have to amend my to do list by just another bug. :D

EDIT 2: The mic patch has not yet been pushed by the kernel dev and the ALSA config needs changes, but then audio calls with built-in speaker and mic will work. :)

Started writing, but then got sidetracked... by making audio calls work. :)

Will post the link here soon, just want to verify there are not too many dumb mistakes in it, do not want to fruatrate anyone with terrible docs. :D

You won't have to wait for very long.

Let me know if you'd like a writeup of the way I currently build the image out of the linked sources and what files (temporarily) need manual fixes, in case you want to try it out. Could still take a while to get the kernel and the call audio daemon ready for Mobian and to get it included, but other than that... Pretty close ^_

If you exclude the time your PC does compiling and works for you, then it is probably 20 minutes work to get an image currently. :)

I also have an Ansible role which does the few fixes I need for now, like that one systemd unit. I could publish that as well in case others want to be alpha testers and tell me about any issues they notice.

I should probably also create a repo with a temporary issue tracker until there are official images. 🤔

I've posted a follow-up, it looks much better now: https://lemmy.sdf.org/post/19600671

Yes, but even the app could be avoided altogether with the other authentication method implemented. :)

Exactly that.

I don't know what would fit your needs, but Signal does not require Play Services. And even if those are present, it does not leak data to Google. Other than "Signal is installed" and "You get a push message", Signal does not put your messages into the notifications. Instead Signal connects to the Signal servers and then gets the encrypted messages from there and only then decrypts.

Even if you have Play Services installed, you can force it to use a background connection inatead, if you disable Play Services before installing Signal, it wall automatically fall back to it.

If you want a version without Play Services libraries, you could use Molly, a hardened version of Signal, which is available in a version without those libraries.

Molly even allows linking phones as secondary devices, not just desktops.

Matrix is not the right protocol for staying anonymous. There's way too much unprotected metadata.

You might be able to mitigate that somewhat by using an instance that is accessible via TOR and being careful who you communicate with, depending on threat models and so on.

But if you want to communicate anonymously and not leak meta data... Probably not what you are looking for.

• user names cannot be changed
• never delete your database, have backups, all the state is in there, if you lose your DB, you essentially have to set up a new server: Your server will say you are not in a room while others say you are, so you cannot join. Always keep your DB backed up.