Hi @WillemHexspoor Security is a matter of trust. You either trust Signal and the "experts" that audited them with your data or you don't. Same goes for Matrix. If you self host matrix, than you only have to trust the software. But if you don't you'll have to trust the hosting entity as well. With a bridge it adds another party, but if you already trusted it, it doesn't change anything. But of course the more code you add, the more probable there is an exploit possible. So your reasoning is not bad. But if you consider using a bridge, that's probably because your contacts are not already using matrix and are probably not interested (at least for some of them).

@WillemHexspoor i also have the same issue on Xenial on my Poco x3 NFC

@WillemHexspoor Then I don't know the answer to your question, as I don't use waydroid.

I reinstalled Android, the SIM card still did not work properly. I was able to read the correct provider name in the phone settings. I tried different SIM cards from different operators, all had the same issue. I could read the operator correctly, but no cellular connection did not work. Than GPS also started to show issues, in the first weeks I was able to get and hold a fix. But now the first fix was ok, but after a couple of minutes the GPS stopped working. I opened the device, because previous owner said it got a new battery. half of the screw were missing. I needed my phone for work and had no time for further investigation. In the end I bought a new Pixel 3a and am installing UT at the moment.

@WillemHexspoor You can download and try the 16.04 version of UTTT from the OpenStore using Morph. Some of the operations work not sure about Edge sensitivity.

@Mic_ I suppose this will only apply to devices released after the specified date. And also only in Germany (or perhaps also EU if it gets pushed up to that level). But longer warranty or support periods don't mean that stuff will get released as open source at the end (or that even if it does, that the license will let you do anything with the source).

@willemhexspoor Hi, seeing this question now, I was recently faced with a similar problem, having to use a Azure Active Directory cloud login, where the admins had forced users to configure MFA. Turns out that there is a well hidden way to configure a TOTP code-generator (i.e. google-authenticator) for use as second factor with Azure AD. This was very frustrating, and I think that the MFA setup page uses dark patterns to prevent users from discovering that feature. There is not much information online. After some googling I just found this old article that seems to describe the method. When the Azure login page tells you "Your organization requires more information bla bla" and you go to the setup page where it displays the QR code for windows authenticator, there will be some very misleading seemingly unimportant link (like "configure app without notifications") which will switch the whole authentication scheme to TOTP. Of course it will never tell you that it is using TOTP and the name Google Authenticator will not appear anywhere. Still it is TOTP and will work correctly using any "standard" authenticator app.

why do we have it on UT and UBports? Resource limits? Very definitely to limit resource consumption. On a mobile phone you have very different expectations about battery life. I think UT sigstops the process when the app switches to background.

Not sure whether this is a feature or a bug but definitely add the information to the bug you've opened and not creating a new one.