@wally said in Tip: call a contact with one hand (secret UT key !): doesn't sound like encouraging news about the database For the limited goal of making search the most efficient possible, it seems not so big a problem. Anyway, I'd say that you can't expect the search for numbers to be 100% efficient if your contact database has many incoherent formats. @wally said in Tip: call a contact with one hand (secret UT key !): A long press of the zero gives a plus sign. TIL I tried again to dial a number with a '+' and this time it worked, I must have done it wrong the first time. Basically it seems that for international numbers, + and 2 digits seems the most used format. Using the database could have some utility because international code numbers don't change often and the ones having 3 digits will have a vanishingly small number having changed to 2 digits or the reverse. The database is not well maintained for numbering out of the country but there are very few countries where it's not just '00'. @wally said in Tip: call a contact with one hand (secret UT key !): why, when set to either Canadian language, the tel_dom_fmt. Do you have any sense of what might be affected by this field? I'd say that the only thing depending on the 'language' selection (quoted because the change is both of the language and the country code) is the country code. It seems to me to be the only thing used in the code that is not hard coded. If I understand correctly the dialer app code, the choice between number matching and 'T9' matching depends on the first digit (0 or 1 --> number matching, other == T9 match, this algorithm could be inappropriate for some countries. France's code (33) has 2 digits, and if your database include entries that include country codes having 2 digits following a '+', they will be in the blessed path. To understand better it would help to have a dump of a few numbers of your contacts working or not depending on the country code. Feel free to replace the 5 (or so) last digits by '99999' or '00000' for privacy since they don't matter much in the matching anyway.

@RoobunOne Well, you'd have to make a port. To see if you are up for that, start reading here: Porting Guide

@Bolly Very nice! Now help me out, what's the 15th of April?

@jukebox3711 That took a long time! I guess it's a busy time for the mail. But it finally reached you, I'm glad to hear that. Thanks for the good news!

@wally Yes, I was adjusting the edges in UI tweaks. However as I stated in other thread I never liked swype OS navigation. Expanding the subject, I also don't like touch OS navigation. Touch screens register the touch "without my consent", i.e. when I just grab the phone. That's wrong, but it's been like that since the beginning of all mobile OSes. I'd love to see an option to enable touch-and-confirm input where you touch and have to swype a bit immediately to make the original touch point registered as touch, otherwise it's meaningless

@Gelukkig said in Apps I really would love: @projectmoon Thanks, I have installed all the apps you mention. For Waydroid I still need a Google account and the purpose is to get rid of Google and Apple accounts The default image of Waydroid does not have Play Services or anything else. As others have said, you can download F-Droid then use that to install Aurora Store, and from there, install apps that are on the Play Store. But as for bluetooth, this will not work in Waydroid. It is a limitation of Waydroid itself.

@enki said in top 3 app wish list for Ubuntu 24.04: Conversation for xmpp chat audio/video client There is an experimental port of Kaidan being developed: https://gitlab.com/alaskalinuxuser/kaidan_0_6_0

@gpatel-fr I see, thank you for clarifying.

@gpatel-fr said in French ID app interoperability.: The recent decision about digital control is concerning troubling for a UT user What are you talking about precisely?

@neinei0612 I'm sorry, that is outside of the scope of this forum.

@bekun Yeah that's the ideal functionality. On Android, that works fine, at least on Samsung phones. In UT, all touchscreens are mapped to the built-in display. I was talking about on the desktops. Gnome have the same issue while KDE Plasma handles it fine.

@jeffreyk Hi, it doesn't work like that. If your device is not on the supported list and a search doesn't show any one porting the device then if you have the skills and knowledge you will have to port UT to that device yourself. The alternative is to get a device that is on the supported list.

@edisss No one knows! There is no list, it depends on whether someone owns the device and the skills, and steps forward to do the work.

@libremax thanks , sorry for rely you late , i forgot my password

from what im reading its asking me to build package sources like indicator-network and i think that is needed because i ran lomiri once i got the setup no apps worked and when i restarted it failed to run so what do i need to b