

Nope. Not what the question is about. This requires an admin user to create an invitation in the admin backend. I want a way to let users do that.
Nope. Not what the question is about. This requires an admin user to create an invitation in the admin backend. I want a way to let users do that.
I doubt that. Signal has slow development, there aren’t new features all that often.
I just realised I did not link to my most recent post, but the one before it. This one is two months newer: https://lemmy.sdf.org/post/22388672
This was the state three months ago. Quite a few things changed, I will definitely post an update once I find the time.
Curious how well existing Android devices with Linux support fare currently.
Better than the Pinephone. See my other post on this thread where I talk about my Mobian port to the Pixel 3a and click the link for some more detailed info on how well it works.
Oh and the Pinephone is just way too slow and the thermal design is not really good and it also does have issues in other parts of the hardware. It’s not a good phone, it’s a passable development device that easily allows to turn off things such as Bluetooth.
And… an old Android phone such as the Pixel 3a is just a lot cheaper and runs way faster with a far better battery life.
I’ve been recently porting Mobian to the Pixel 3a and posting about it here*. Now, Mobian is close to being ready, but is not yet. I’ve been using it as a daily driver for a few months now, but it is not what most people looking for a well-working phone would want, currently. If you want to try a well supported device now, I suggest trying postmarketOS on the Pixel 3a perhaps, they’re a bit quicker than I am, mostly because more people are working on it.
The Pixel 3a has recently been called one of the best supported Linux phones with a mainline kernel. Only issue right now is the camera not producing sharp photos, but they’re people working on the drivers in the kernel to improve on that.
Other than that, I don’t really know what’s well supported, as I focus on what I have available here.
* https://lemmy.sdf.org/post/19600671 Please note that this post is somewhat outdated and some of the issue are solved already.
And they’ve been working on it for years now. :)
I believe they’re working on it. :)
It uses a library which currently gets calls added, for example. Once that library supports calls, they can add it for Flare.
Yeah, because it’s a Pinephone. It’s an underpowered set top box SoC from around a decade ago. Definitely try something else. :)
Depends on the bank, I’ve been a customer at four different banks over the last few years, all their apps worked flawlessly without Play Services or microg installed. One just gave a warning.
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. :)
Yup. It definitely is now ready for everyday use, though there are still a few smaller issues I’ve got to fix. But nothing that stops me from using it now.
The only thing special about the Pixel 3a is that I had it already. Maybe it is special in that it is now the smallest Linux phone that is supported by a mainline kernel AND which is actually usable as a phone (for some other phones audio does not work, for example). Some might call a headphone jack something special… or an eSIM, as there are not many Linux phones with an eSIM.
To get involved, I recommend joining the Moban Development Matrix room: #mobian-dev:matrix.debian.social
Pretty sure we can find something where skills in C would be helpful.
Thank you. :)
Have a nice day!
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 already have an invite flow that users will arrive at and go through when signing up, now I want to let users create invites for other users. That page does not mention anything about that. It seems to be about adding a flow that asks user for details such as an email address and then they get their account.
In my case users have already gone through that and want to invite someone else.
I already have enrollment invitation URLs. Just not automatically. I wrote a script that uses the API for that purpose.
The docs even mention this about the flow: