Categories

  • The Meta category: Organizational or general discussion.

    1k Topics
    10k Posts
    K
    @domubpkm The app itself would be doable but the packages aren't doable since they ust replace system files so translations can't be processed. I mean it's doable but it'll take for someone to modify each file manually and create separate packages per language
  • Discuss news updates from Ubuntu Touch and its related projects

    1k Topics
    5k Posts
    UBportsNewsU
    Today is Ubuntu Touch Q&A Day Ubuntu Touch Q&A191 is today at 19:00 UTC please join us on our YouTube channel: https://www.youtube.com/watch?v=hS6sOkNhX1s Questions can be posted during the show or for priority using this link: https://forums.ubports.com/topic/12300/ubuntu-touch-q-a-191-call-for-questions UBports@telegram #ubports:matrix.org #UBports #UbuntuTouch #UBportsQandA #Lomiri #OTA12 #Ubuntu #UTnoble #MobileLinux
  • Discuss and solve problems with other users

    4k Topics
    29k Posts
    L
    @lduboeuf Many thanks for the suggestions & help Actually, when I got the problem, at first I tried removing the whole conversation. Then, I tried sending another SMS to the same contact, which re-created a new conversation, but that SMS got stuck too (spinning wheel), which made me think there was some service lomiri-messaging relied on that was somehow stuck, maybe ofono (pure conjecture on my behalf). Following your sugestion (a few hours later), I tried to delete the blocked message, then again the whole conversation, and then sent another SMS to the same contact and this time, it worked. So AFAIK, problem solved, but I do not know why. I tried to look at the traces by doing a journalctl | grep lomiri-messaging > somefile.txt but I got 2MB worth of traces. I tried to grep -i 'error' or 'invalid' but I do not know exactly what to look for. Lines which appear suspicious to me (but may be completely unrelated) are: juin 02 14:38:27 ubuntu-phablet lomiri-messaging-app[95339]: QSocketNotifier: Invalid socket 19 and type 'Read', disabling... ... juin 04 17:58:56 ubuntu-phablet lomiri-messaging-app[16850]: file:///usr/share/lomiri-messaging-app//MessagesListView.qml:87: TypeError: Cannot read property 'left' of null ... juin 04 12:05:42 ubuntu-phablet lomiri-messaging-app[11099]: error calling result "An AppArmor policy prevents this sender from sending this message to this recipient; type="method_call", sender=":1.103" (uid=32011 pid=11099 comm="lomiri-messaging-app message:+XXXXXXX" label="lomiri-messaging-app (enforce)") interface="com.lomiri.libertine.Service.OperationsMonitor" member="result" error name="(unset)" requested_reply="0" destination="com.lomiri.libertine.Service" (uid=32011 pid=4480 comm="/usr/bin/python3 /usr/bin/libertined" label="unconfined")" juin 04 12:05:42 ubuntu-phablet lomiri-messaging-app[11099]: lastError - no arguments? ... No sure this is much help. I will experiment again with MMS and post back on this thread if find something useful
  • Community section for all languages other than English

    24 Topics
    121 Posts
    G
    Bonjour j'avais le problème suivant sur mon Fairphone 5 sous 24.04-1.3 stable: les personnes m'appelant ne tombaient jamais sur le répondeur, ça sonnait sans limitation de durée. Tout d'abord, sur le principe le répondeur n'est pas configuré dans le téléphone: le passage sur répondeur en cas de non réponse après une durée donnée n'est pas paramétré dans le téléphone mais chez le fournisseur de services téléphoniques, dans mon cas FreeMobile. Cependant, en dépit d'une documentation officielle disant le contraire, il n'existe aucune option 'paramétrage du répondeur' dans l'interface Web de FreeMobile. La réponse du support FreeMobile est d'utiliser les codes USSD (Unstructured Supplementary Service Data == codes cabalistiques pour configurer diverses fonctions du téléphone du genre #002# ou autre). Malheureusement, aucun code n'a fonctionné sur mon beau téléphone UT. J'ai trouvé une vidéo Youtube conseillant pour un téléphone Android de configurer le téléphone en 3G plutôt que en 4/5G, mais dès que je configure en 3G je n'ai plus de réseau. L'astuce tordue: Finalement, j'ai appris de source non officielle que passer par l'interface de gestion de Free et positionner l'option 'Relais téléphonique' réinitialise les paramètres du répondeur à leurs valeurs par défaut, c'est à dire passage sur répondeur au bout de 20 secondes, ce qui convient parfaitement à mes besoins. (je n'ai pas la moindre idée pourquoi ma ligne était configurée différemment) L'option Relais peut être annulée ensuite immédiatement. L'hypothèse de la personne m'ayant renseigné est que le téléphone que j'avais utilisé pour montrer le problème (un Android bas de gamme, je ne voulais pas demander à un non spécialiste de regarder un téléphone Ubuntu Touch) n'était pas assez moderne pour que ça fonctionne correctement (j'ai eu la démonstration qu'il était possible de configurer le répondeur avec les codes USSD avec un Android moderne sur un téléphone non bas de gamme) Conclusion: la compatibilité des codes USSD est un problème délicat. Même s'il y a du code dans Ubuntu Touch pour les gérer, la compatibilité n'est pas garantie. Concrétement, lorsque je passe dans l'écran de configuration des fonctions téléphoniques du fournisseur (répondeur) j'ai plusieurs ronds bleus qui tournent sans jamais déboucher sur quoi que ce soit. Je me souviens que ce même écran fonctionnait lorsque j'ai installé mon téléphone sous UT début octobre 2025, donc c'est une évolution venant de mon fournisseur FreeMobile.
  • 2k Topics
    20k Posts
    B
    @gpatel-fr anyway thanks for your lines and good to know, that the problems with tones is frequently.
  • Discussions on development of Ubuntu Touch

    546 Topics
    7k Posts
    mihaelM
    @gpatel-fr Oh, wow, I would have never thought of checking after a restart... Let me just link that here: https://forums.ubports.com/topic/12289/changing-message-sound-requires-restart
  • Discuss the user experience or design of Ubuntu Touch or its apps

    171 Topics
    2k Posts
    Linus67L
    @Zer0 I hope you stay in touch with Ubuntu Touch. Just like Ubuntu Touch itself, there are several layers to the Ubuntu Touch community. You'll find the right people.
  • Creating Ubuntu Touch apps

    815 Topics
    8k Posts
    alaskalinuxuserA
    And some pics: [image: 1780593457929-photo_2026-06-04_08-50-30.jpg] [image: 1780593457952-photo_2026-06-04_08-50-38.jpg] [image: 1780593457970-photo_2026-06-04_08-50-42.jpg] [image: 1780593457991-photo_2026-06-04_08-50-46.jpg]
  • Porting Ubuntu Touch to new devices

    507 Topics
    4k Posts
    systemmaniac2010S
    Device Boot Loop Issue While Porting to Ubuntu Touch (Halium 13) I am trying to port my device to Ubuntu Touch, using Halium 13. I have flashed the images to the right partitions, but I encountered a boot loop with the following behavior: Boot Loop Sequence The device shows the Motorola start-up logo for one second. The device shows the unlocked bootloader warning screen for 6 seconds. It shows the Motorola logo again for 6 to 10 seconds, but now with a horizontal pixelated line on the screen. It then shows a blank screen for 5 to 10 seconds. The cycle repeats, but the line gradually moves down on each reboot. Troubleshooting Performed At this stage, I entered the fastboot bootloader and tried: fastboot boot twrp.img However, the device immediately started boot looping. I then replaced dtbo.img with the one from the latest LineageOS 20 build available for my device. After this change, the horizontal line disappeared. I was able to successfully boot TWRP using: fastboot boot twrp.img Logging Investigation I attempted to read the pstore logs but couldn't find any useful output. I suspected the kernel might not have been built with the required logging options enabled. To address this, I: Created a separate logging.config file with the right kernel flags. Added it to deviceinfo. Verified that the options were correctly applied to the generated .config file located at: workdir/downloads/KERNELOBJ Added the appropriate kernel command-line parameters to the vendor cmdline in the deviceinfo file. Current Status Despite these changes: The device still does not boot properly. USB does not become available. The pstore directory remains empty even after enabling all relevant logging flags and kernel parameters. Source Tree For debugging and error analysis, the device source tree is available at: https://gitlab.com/systemmaniac2010/motorola-rhode Please help me out with this.
  • Lomiri, the operating environment for everywhere

    77 Topics
    640 Posts
    U
    @ChromiumOS-Guy yes its just perfect as second clipboard for selected text, daily used on desktop
  • Discussion on translating Ubuntu Touch and its core apps

    61 Topics
    335 Posts
    lduboeufL
    said: Hello, With the next calendar-app release coming, a bunch of new strings are waiting to be translated, thanks for looking into it: https://hosted.weblate.org/projects/lomiri/lomiri-calendar-app/ Lionel oops forgot to mention the forum post about it: ( arf can't paste the link here), look into category OS->Call for testing: calendar-app)
  • A place to discuss ideas for promoting Ubuntu Touch

    57 Topics
    733 Posts
    developerbaymanD
    i just posted a testing version in app development ....expect bugs ....i expect feedback ....i add the missing features mentioned as well
  • Other Projects

    Projects which are started by a group within the UBports community

    72 Topics
    431 Posts
    CiberSheepC
    @libremax Spain when there's football on the tv (I'm not joking)
  • For things that just don't fit in the other categories.

    903 Topics
    5k Posts
    R
    Hello, had anyone tried to fiddle with cubot king kong mini 4 or onemyth m17pro by chance? Both phones are available on aliexpress. Here are the specs: https://www.gsmarena.com/cubot_kingkong_mini_4-14099.php https://share.google/aimode/vblB9hnaaflKi6zcl