Nice idea, that’s actually pretty clever! I’ve never thought about using the phone as a remote audio sink like that. Did you notice much delay in real use, especially for videos?

@richdb Dat kan ik alleen maar aanbevelen. Ik had echt meer mensen willen spreken. Een volgende keer dan maar!

@wqyeo There is a telegram group dedicated to quality assurance: https://t.me/ubports_qa_team Hope it may be useful for you

@projectmoon said: Mir 2.0 in the last UT Q&A was demonstrated an UT phone running Mir 2, the main blocker is the rootfs device size problem.

@gpatel-fr I can't see the difficulty. Instructions for clickable installation are the same for 8.7 version: https://clickable-ut.dev/en/latest/install.html (just use pipx command instead of pip3, as proposed also in the book)

@kugiigi Hello So I dont have another phone with display out so I cant test that unfortunately. I do agree that the hub seems to be what determines what issues I have. I dont have major issues using any hubs with my asus laptop to charge and display out and the laptop draws more power than the phone. What hub do you use?

@lduboeuf First there was the alert-message (I don't know which message-id was used right now) and after 30 minutes there was there clear-message for this alert which says, that the alert is over. I only received the second message (clear) but not the first one (alert). Is there an option to get the subscribed message-ids? The above mentioned test-cbs-script doesn't work for me.

@ma Thank you, I will try that!

@bunchy7s Note that the Oneplus 3 port isn't even listed on the main devices page. The page @moem dug up says that the last work on it was in 2021 and is for UT 16.04, which is quite out of date. And the video you followed is four years old. I can't say that your issues are definitely caused by how out of date it is, but I can say that you're unlikely to have a good experience of Ubuntu Touch on that device. Unless you want to take up the reins and bring the Oneplus 3 port up to date, I'd say your best bet to try UT is to read around on the forum and device pages and try to find a supported device that suits your needs and is affordable and available in your area. Also of note: some people have difficulty with putting a phone back to android, so do your homework on that before attempting.. people have bricked their devices.

hello we have an exchange about the indicator area. we propose 3 questionning way : Is it a good idea to add a usb menu : to connect the device (charging/file exchange/connection sharing) ? we found there is too much icons. so,what about 'group' some indicators by familly ? link : for usb link, bluetooth... interface : keyboard, rotation, (external display in the futur) the usage of the file icon seems not clear : no many apps use it. is it pertinent to group it with somthing else ? thanks. https://forums.ubports.com/topic/12034/usb-parameters-on-headband

@k.nacke Thank for the hint

@domubpkm thanks

@slowcyclist err, no, my test reconnects to the server. However there is something of a strange behaviour that I don't understand currently. When asking for a sync even in test mode from the command line: syncevolution --print-databases backend=caldav username=<user> password=<pwd> syncURL=http://192.168.20.12:5232 [INFO] start database search at http://192.168.20.12:5232, from sync config '@default', syncURL='http://192.168.20.12:5232' I often see a block, the connection is not established (nor refused). After some time (a few minutes ?) the reply is sent. I see the log of the server at the same time, it does not receive anything, it's syncevolution that is refusing to send. When looking at the same behaviour from the phone UI point of view, when clicking on the sync button, it turns in display busy and after some time the server is receiving data and the sync button turns in mode inactive (but with an red error indicator). Even trying syncevolution --help blocks. It's as if syncevolution was refusing to work at some moments. Looking a bit more, it's as if it's the phone UI connection that is blocking itself (and all other operations such as syncevolution --help or the manual sync that I posted above; when the UI phone attempt at connection finishes, I can then do sync tests from the command line without limitation. It's as if the sync initiated from the phone UI was blocking syncevolution for about 5 minutes, then it deblocks itself (and other syncevolution clients on the phone such as my test sync) , synchronize the events successfully but returns an error. A bit of testing seems to show that the delay is about 5-6 minutes. Maybe it's actually that syncevolution is setup to sync every 10 minutes and the button has no effect other than to block until the automatic sync does its thing. If what you see looks like what I see, that would be a pattern and maybe an issue could be created on Gitlab.

@nbdynl There is a way to force the update. https://ubports.com/blog/ubports-news-1/ubuntu-touch-24-04-1-2-and-20-04-ota-12-release-3987

@PringleMingle If you loved your Op3, try finding a used Op5 or 5t! Very good device, and very close to what you are used to... except this one runs the latest version of Ubuntu Touch. And nowadays they can be had for a song.

@MarcelloTogg Hello, There is a roadmap about Lomiri (one for Ubuntu Touch and one for Debian) here: https://ubports.com/lomiri-roadmap You can also get news in the blog section : https://d'UBports.com/blog For more technical insight : https://gitlab.com/groups/ubports/-/activity

@AndroFree said: Habe versucht auf einen Xiaomi Note 9 Pro Ubuntu Touch zu installieren. Habt in einer dauert Schleife Rebooting Fastbootd und es funktioniert nur noch Fastboot Modus. Sonst geht nichts mehr. Kennt jemand eine Lösung? @AndroFree ....you need to downgrade to android 10

That page probably is not for what you expect. It is not really a membership registration page. You become a member of the community simply by interacting and participating. I think the page's purpose was to generate a list for a pool of volunteers and their skills in order to match them with project needs. But may I ask what you registered for? Maybe you can be pointed in the right direction to contribute by someone here.

@kugiigi i like the convergence this is good

@PringleMingle Have you put it onto the required version of Android before installing UT? Was the device fully charged before starting the process? Noble (24.04.1.x)does not work on this device so use Focal (20.04) instead. Someone is working on this to get the upgrade to Noble. From experience a crashdump is usually a weak/dying battery or battery requiring a charge.