contact@france-identite.gouv.fr

@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.

@mango Ok but I don't understand why you have icons that are that big on your phone in the top panel, in comparaison to my phone. @mango said in Signal UT: Signal-Desktop for Ubuntu Touch: By the way, I tried to attach a photo from the camera, but the app crashed after creating the photo. Voice message works well. Try it again, as mentioned in the description of the app it may happen some times. It's always better to take the photo the normal way, and then load it from the gallery. I think the process of taking a picture diirectly through the camera app in contentHub is slightly buggy. Looking forward to working menus as well. If you're talking about the top menu, this will probably not happen soon. But I'm not sure why you would need them.

Ich kann mich dem nur anschließen, apt sollte man bei den ARM-basierten Geräten lassen oder eben nur gezielt einsetzen. Dein benutztes apt update ist unkritisch, aber das anschließende upgrade -y kann auch schnell mal nach hinten losgehen. Aber gut, wenn du jetzt das Upgrade via Systemeinstellungen hinbekommen hast, sollte ja alles wieder passen.

@ma a gitlab account can be created for free, all that is needed is a mail address to get the account confirmed.

@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 ).

@deadthousand You clearly got it boot loader unlocked since you are running UT on it. If it is network locked, and you bought it, you can request to network unlock it. There is also a way to network unlock it by removing a file in the HAL, but that requires hacking skills. See xda-developers for that.

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

@UTUS I second the assessment of @rocket2nfinity . I've always found MMS a bit quirky, but largely it works except for group messages. Can vary a bit depending on provider and APN settings. Group messages have been a known issue for 5+ years, Ibelieve there's just no fix. I receive nothing, no notification, no error, when someone sends a group message. No way to know anything was sent. I just tell my contacts I can't do group texts. It's more awkward now that iOS picked up RCS.. everyone expects group messages should work. So far as I know, RCS is on the radar of the devs, but not really even a work in progress yet.. they do incredible work with few people, mostly unpaid. In Canada, this is the most unusable part of UT. Otherwise it's great! Somehow even my banking works, though this isn't the case for most. Definitely look into bootloader unlocking before buying. Surest way, as stated, is BE2026 (North American version, non-carrier specific). Most people succeed in getting an unlock token from Oneplus eventually, but they now seem to say they only send one when given proof of purchase from an official vendor or something. Downgrading to aporopriate Android is a bit tricky.. follow the instructions, using MSM tool and EDL mode. You'll figure it out!

Here are the videos recorded about mobile: https://video.fosdem.org/2026/ub4132/ UT is mentioned in the videos about state of Foss on mobile and the one about the apps store: the UT one is rather well placed, however Flatpak is coming for mobile and it has already a dominant position in general Linux apps. The video about openHarmony is intriguing given the resources of the organisations behind it. I have been interested by the one about push notifications, apparently more ready for prime time that I was thinking. It seems that the only real solution for Linux clients is the kde one, that would seem a good fit for UT since it uses QT.

@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.

@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.

I don't know the technical details of the app. You can probably log an issue and the dev could look into it. It would definitely be nice if it just works without timing it. It's a great app that probably doesn't exists in other systems

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

@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!