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

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

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

I would apreciate something to get rid of the cookie questions. Something like addon "I still don't care about cookies". Maybe someone knows how to achieve it.

A small text size and a lack for a Setting to adjust all the different text sizes individually, as well as a general scaling factor for all text types is really a headache. Text adjustment is needed to improve usability. If this means rewriting code, it still needs to be addressed. There is no way around it. Text size(s) needs to be easily adjustable in Settings without falling outside of screen limits. Scaling makes everything bigger, even icons. Icons should be able to scale separately. Like in a modern desktop linux, which is a newbie's reference. It is also difficult to understand for newbie the scaling in desktop mode, since it is set to 8 instead of for instance 24 on the device. Changing desktop mode scaling affects the scaling on the device after disconnect from external monitor. Two different scalings are needed; a separate one for desktop mode to not mess with the device scaling.

@rocket2nfinity Its a pixel 3a. It also just straight up says "denied". I've even tried those, ejecting the SIM card, to no avail. Like, no data, nothing.

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.

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

Nice to hear Ubuntu Touch worked well for her, that is a fun way to learn the basics. You might also set up a simple contacts shortcut or favorites list so she can call family faster.

Maybe the public can be divided into subgroups with different needs. Ubuntu Touch has to fulfill those needs. Newbies that are not so into terminal coding generally say Ubuntu Touch is buggy. That the text is so small overall. That the text cannot be easily adjusted. They cannot see the text! Major road block for some. The cookie nagging in Morph browser can drive somebody nuts, especially if they can't figure out how to block those cookie questions. Adblock exists in Openstore, but there may be difficulty to find a cookie question block solution. Or youtube ad blocking. Some newbies want a laptop Ubuntu Touch like a Xubuntu desktop. Few understand that literally means to work inside a Libertine container with a terminal, inside Ubuntu Touch, but still isolated from Ubuntu Touch. That they need a device with USB3, external monitor and desktop mode to get things done. Or with snaps. It is not easy to grasp how Ubuntu Touch really works inside as a newbie. Major road block. Offline GPS navigation with route planning is definitely on many newbies wishlist. If this part is too buggy it cools down emotions. Music player is there thankfully. Signal is probably one such app that has to exist on Ubuntu Touch natively and work well. There is no way around it. Communication is high priority for some and a show stopper for many if not available. Comparison: zoom does not exist for linux aarch64. Games do not focus on snapdragon chips. Result: people regret buying an arm computer because their wanted apps are not there. Same with linux distros lacking those apps people want. Others want EPUB3 in night mode with proper fonts and good rendering. Try to find any android app that can render epub3 with inline svg graphics as well as those two most used apps in Openstore. Here is the uniqueness in Ubuntu Touch. Still, the epub3 viewers have some noticeable bugs which cools emotions. Night mode flickering between pagination is one. What is downloaded most usually is most wanted by many. Many times it is games. The core apps are expected to be there but maybe do not get as much attention. Gameboy emulator is really good! No bugs there. Lets look at the app ISODrive. It really solves a big support issue. But it does not work in 24.04/daily. Creating a bootable USB-stick when your laptop needs reinstalling is a nightmare when you are travelling, right? Here you have a unique thing, but it is not working. Why not fix it? Such things make effect because they are needed and solve a real problem that arises quite frequently.

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

Notif are back but seems not of PM received Yet.

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

@pparent Good for you. I have tested more heavily this solution and it's promising, but I suspect that there are still a bug or two in systemd itself and I need to clear the air about it before suggesting it in a QA.

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