@pparent said in French ID app interoperability.: @domubpkm Well I'm not sure but given what I have published above, It could mean that it can only work by design on an un-compromised google certified devices ( I've read that there exists so-called technologies as "Android hardware-backed keystore" and "Trusted Execution Environment" , could the app possibly rely on that? ). So maybe it's not working with microG because they don't want it to, because they want the app to run only on a so-called "safe envieronement" provided by google. This kind of stuff is happening more and more. Even apps like the ChatGPT app for Android require "Play Integrity." It's an API that needs to be made illegal, and a lot of national apps are relying on it too. For example, the Icelandic app Auðkenni used to work without it, but now your device has to be "secure" in order to use the app. Thankfully, in that case, there is an alternative method of authentication using SIM Toolkit. MicroG is able to execute SafetyNet/Play Integrity, but the device has to have the bootloader locked and a bunch of other stuff. And depending on level of attestation required by the app, it may or may not actually run.

@pparent did you notice that there are menus that are displaying fine in the ChromiumUT app ? the menus in the top bar are not working, but the Google application menu is working correctly (although there is a wobble the first time, maybe it's the automatic resizing you are referring to, but it's failing to stop it to work)

Viability: hmmm, at the moment: No voice calls (no VoLTE) on Pixel 3A (which WAS a primary supported phone for UT), on UT in USA (which is the third largest phone market by country, or 4th largest by region, after Europe). [alternative: VOIP - NOT available in openstore for most recent version UT] That is pretty NON-Viable, if you want a phone you can make calls on. Is that the fault of the UT teams ? I would say NO, it is the fault of the much larger system cancelling 2G, 3G, (USA & Australia , etc, now, and changing worldwide, with plans in place over 10 years ago) and the fact that the drivers for the radio chips and most others are closed source or Android or whatever. Who would be the ones to fix it ? UT dev teams, if at all. Or, what about WiFi calling ? Not functional. Is that the fault of UT devs, or other main stream code (from the larger base) being unavailable ? OR some phone brands / models NOT supporting required radio bands in some countries. NOT Viable. I think PC's are a better analogy than cars, since we are mostly talking software here, not hardware. if using cars analogy, could mention how air bag manufacturers caused a huge recall problem for a variety of car manufacturers. Q: So, where did UT come from ? A: 1) a gigantic base of hardware and software: major players who recently CANCELLED (in some countries, and in process in others) the fundamental ability of UT to make phone calls, through changes to the larger hardware and software system. A: 2) a few dedicated, volunteer developers who are doing their best to modify code for specific devices to overcome above obstacles.

@Bubu said in Ubuntu Update on FP3+ und FP4: Den Tip von arubislander ( https://forums.ubports.com/topic/10352/unable-to-update/7 ) Das ist ein PinePhone, der Tip gilt nicht für FP4.

@lduboeuf I think that I can as well note here the results of my sunday tests with Radicale and UT, it will allow me to retrieve them easily and maybe be of some usefulness to others: it works with 24.04-1.1 stable, but it can be quirky. I used a test server that has already other databases, notably an address book, and these database were proposed as options for sync with the calendar. It's already a problem since an address book is not a calendar. However it got worse since even after selecting the right database, the sync failed repeatedly until I deleted the 'wrong' databases. The server reported a 400 error on some query aimed to the address book (why oh why since I asked specifically to sync with the calendar...) and the whole sync was failed (I guess that Google Calendar has not this problem since it's just a calendar, it does not try to support all kind of Dav databases like Radicale do) This was reported by a red indicator in the UI, however the detailed journal was not particularly enlightening, it reported error codes (10400 ? I guess it was error code 400 with database number 10 - so very Unixy error reporting ) The whole testing was not made easier by the syncevolution user interface, a software that has a conception of 'user friendly' that is decidedly selecting its friends. I had to delete the offending files with 'rm' in the evolution (not syncevolution) directory via the command line to get rid of the excess databases in the UI, while they all got back when I deleted the last one (the calendar). Finally butchering my test server was the right option (and now I don't have any failing test case anymore ).

@projectmoon said in standard browser: is there something in the DB that allows it to select a browser without excluding apps from the list by doing a fake domain? no, that's why I did this ugly hack (that will most probably not survive an update btw). Adding a column named for example pref_order to the urls table and sorting by it instead of the row_id (that can't be changed since it's an implicit column) could allow to change dynamically the browser. It would be nice to have if alternative browsers could be used. I don't know if the packagers for alternative browsers would be motivated enough to search what is missing for that.

@gpatel-fr Yes, I meant TLS encryption. I'm still looking for the reason why dekko isn't working (I've already tried all the settings ...).

Well but Hello, everyone! Thank you very much for your information. I've been around long enough to know that a daily channel (i.e., dragon channel) exists in the versions, but I don't want it on my daily driver. I can wait for the RC or stable channel, even though my attempt on the Samsung Galaxy S9 with E-OS failed. I found the following post in the E-OS forum: These international Samsungs don’t get VoLTE with any U.S. network, due to: their internal hardware which is different from North America Samsungs and identifies as incompatible, i.e. non-certified for a particular U.S. network’s VoLTE; their exact model number + suffix is also different from the North American variant. Samsung’s proprietary IMS/VoLTE implementation which no custom ROM can integrate (or so I’ve read). Even U.S. variants of Samsung apparently can’t get VoLTE once a custom ROM is installed (unless something changes). Other OEMs don’t have this problem. Any carrier can tell if a phone has or has not been certified by the OEM specifically to carry Voice over LTE on their network, just by the IMEI, which is visible to their systems; if not, then they will disallow it in countries like the U.S., where VoLTE is now a hard requirement. It would probably introduce a legal liability (inability to call emergency services) to them if they allowed a non-compatible phone on the network once all the 3G is shut down, and eventually 2G. If a particular device has been tested and certified to use a particular network’s VoLTE, then a setting such as “Enable voice over LTE” or “Enable 4G calling” or “Use VoLTE,” etc., will appear in the menu when that network’s SIM is inserted. (Not to be confused with LTE data, which is not specifically referring to making phone calls.) Greetings Mario

@messayisto Ok I think I can make use of the device, thank you very much! (and in any case if I don't need it anymore one day, or you need it again, I can always send it back to you.) I send you a PM. @moem In an ideal world Signal would provide an API for external webpush server, as telegram does, and we don't need to keep an app open ususpended to receive notifications.

@faveoled it disconnecting by me (because the charging cable is about to broken)

I tried to enter command in the terminal: sudo snap install libreoffice. It installed. This version of LibreOffice seems to work better than the libertine version I described above. Some dialogs end up partially outside the monitor in desktop mode, but it is indeed usable.

@pparent Will let you know if an upgrade fix it and pinpoint what happend. Yes , devs must know . Thanks for min browser .

It's beginning now.

@oldbutndy Great as you say ,but , i do not code... i share your hope .

@bhdouglass Thank you very much!

@Vlad-Nirky That is an issue with the device from Xenial and Focal.

@libremax Wow, nice! Thanks to whoever did the work and thanks for letting me know!

@mango ISODrive is awesome but it's a bit finicky to use. You'll have yo mount the ISO when it gets powered by the machine so this means after you pressed the power button on your PC. You can also try the boot from USB function from Windows if you have it. I tried this on mine and it worked once I remembered how to make it work

@deadthousand Try one of the Verizon Data APNs - Some devices in the US can still connect as a Data only device, even though VoLTE isn't functioning. The rest won't work on Verizon without registering an IMS APN first. You did not specify your device, but in general, Verizon will not work with UT, except for models that are currently VoLTE capable and on Verizon's whitelist - In the US, that would be the Oneplus N10 and N100. OP 6/6T will be VoLTE capable shortly.

@mango I have tried it a bit and I think it's broken