@TheKit said in On the subject of Ubuntu Touch versioning scheme: Could you please elaborate why this type of version scheme makes it harder to introduce larger changes? We could always have OTA-x.y if needed for smaller changes in-between (and in practice already done so when specific issues/devices needed hotfixes), but I wonder what is the issue for larger ones? A special consideration is needed in order to isolate changes in-pipeline from hotfixes. For example, suppose we've landed multi-component code which improves Wayland application support but require some more testing (the larger change). But then there's a severe vulnerability in QtWebEngine which we have to patch as soon as possible. The original 20.04 OTA-x scheme doesn't have a way to do that; we would have to wait until the change is tested before we can release the next OTA. One way to alleviate that is to take a procedure from Canonical days and take an Apt snapshot at the OTA release time (nowadays trivially doable using Aptly), then binary-copy the QWE package from the current devel archive to the snapshot archive and build an rootfs image from that. Or am I understanding your question wrong? @Fuseteam said in On the subject of Ubuntu Touch versioning scheme: I would like to propose option 2 but keeping the "." between year and month so if the next version is released in may 2025 it would be called 25.05.0 [...] i think we can work around the confusion with the Ubuntu version we're based on by utilizing code names in the release announcement similar to upstream ubuntu e.g. Ubuntu 24.04 Noble Numbat vs Ubuntu Touch 25.03.0 Marvelous Moon I'm not sure that could really workaround the confusion though. For example, suppose we have a release in April 2026 then the version number would be e.g. Ubuntu Touch 26.04.0 Callisto [1]. But then we're likely not quite ready to base our system on Ubuntu 26.04 I think that unless we carry our codename everywhere (impractical, IMHO), I think confusions will ensue. [1]: someone suggested using moons in solar system as a codename in the UBports development channel.

@Lga It might be available on FOSDEM own channels like last years iirc. Check their website for info.

Hello. After sorting out some billing issue with Cloudflare and re-adding our domain to Read the Docs, https://docs.ubports.com/ is now online again. We apologize for any inconvenience caused by this.

Good idea, I've noticed it too, not sure how easy it would be to fix but it would definitely make sense!

@bhdouglass Thanks for the post, and for all your work!

@danfro said in Add a launcher to the app drawer to run a command: I actually had to add the line with "Type=Application" before the script launcher would show up in the launcher.. I'll move it to the top part then, thanks for the feedback!

Welcome @Il-Dorato I'm happy to see fresh blood joining our community. Season's greetings.

@naizena It might still be worth considering a wireless display option if it's important to you. I'm sure wired is a better solution, but if not possible, it's nice to have another option. I was going to suggest the Microsoft Miracast Adapter V2, which has worked very well for me with several different UT devices.. but it seems the adapter is no longer produced and it's hard to find a used one. Does anybody know of any other wireless display adapters that work well? Mine wasn't cheap, $60 CAD (€40), but if using an external display is an important feature to you, it's a shame not to be able to. I get minor latency in display (well under 0.5 seconds), and two-finger scrolling doesn't always work when using the phone screen as a mouse. But with a Bluetooth keyboard and mouse, it's great. And while not every app is well set up for it, on the whole the OS functions very well in desktop mode. I hope you're able to find a solution.

@manoiese As @AppLee said you don't sound rude, just honest. But what you don't understand is that Ubuntu Touch is like that since the beginning, Canonical made it that way (read only in first) and users like me that adopted it since that time don't need a phone system with full access all the time. Like already said if you want you can make it full read/write in a persistent way. Or like you experimented, temporarily untill next reboot. That can be useful, but for normal users for whom the system is designed, again, since the beginning, it is not mandatory or a normal use case. If you want to continue with Ubuntu Touch on a normal way, you should consider trying to achieve what you want/need in respect with this particular behaviour of the system, like some Devs already did with crackle or things like that, I'm sure this would be a welcomed contribution. Or maybe, like said @AppLee also, Ubuntu Touch is not what you need.

@Moem Sorry, yes I have yoused a german Word for AI. My post should show an alternative solution approach.

@linhmieu not in the supported devices list: https://devices.ubuntu-touch.io/ So probably no but it's up to you to try to port it: https://docs.ubports.com/en/latest/porting/introduction/Intro.html

500 k$ reached in twenty days, the funding target has now been raised to $1 million and the campaign extended to the end of January. https://www.indiegogo.com/projects/brax3-the-most-privacy-friendly-smartphone#/updates/all

@Jacobmilton9386 said in Mi 10i Snapdragon 750G processor same as fairphone 4: can I install Ubuntu touch No, it's a different device. Each device needs to be ported separately.