Categories

  • The Meta category: Organizational or general discussion.

    1k Topics
    9k Posts
    libremaxL
    @stanwood I think it's better to keep two subjects one for UT and an other ("off topic") for FuriOS. Otherwise, it would be confusing. Given multiboot is possible with FLX1, discussion about FuriOS may very well interest some people in this forum in the future.

  • Discuss news updates from Ubuntu Touch and its related projects

    1k Topics
    5k Posts
    I
    What can newbies do to help, other than donating? Enthusiastic and somewhat technical, but low in programming skills.

  • Discuss and solve problems with other users

    4k Topics
    27k Posts
    MoemM
    @jojumaxx Not in my case, since I don't use Waydroid Freezer at all.

  • 2k Topics
    17k Posts
    MrT10001M
    @liam I have been doing some research. I don't have an OTG hub with power and USB ports (yet) but do know that some don't support charging and USB together on certain devices as the device doesn't support dual screen.

  • Discussions on development of Ubuntu Touch

    494 Topics
    6k Posts
    P
    Not too sure where to ask that, feel free to redirect me! I'm currently working on getting better support between SDL and Ubuntu Touch. I've written code for SDL to add support for more features, and I'm working on a Clickable template to that effect. I hope with this to give developers an easier time porting SDL apps (including games ) to Ubuntu Touch, and perhaps to give another way of writing Ubuntu Touch apps After some reflection and discussion with other developers, I believe that it would be beneficial to ship SDL with the base system, if that would be reasonable. It would avoid packing one copy of SDL with each app that uses it, and instead have one single copy of SDL on the system. SDL takes about 3-4Mb of space; the satellite libraries (there are 4) takes a few 100's of kbs each. It would make it easier for device maintainers to apply device-specific fixes to SDL and other kinds of tweaks when necessary. It would simplify the build process for SDL apps that expect SDL to be installed on the system. (CMake's "find_package(...)") It would allow the base system to ship SDL updates without app developers needing to update their apps, leading to better global support of SDL apps, especially when an app maintainer becomes inactive Essentially, it would "patch" apps without developers needing to do anything. And in case a device developer ships an outdated SDL, nothing prevents the app from shipping a newer copy of SDL. I'm not sure what are all the variables to consider when making such a decision, but I suppose that I won't know unless I start the conversation!

  • Discuss the user experience or design of Ubuntu Touch or its apps

    163 Topics
    2k Posts
    W
    Hi @Capsia , Thanks to you and any others for the excellent work on the websites! I hope this is an ok topic to post this in. I didn't find much else pertaining to website discussion. (TL;DR - I'm suggesting a Donate button next to porter/maintainer names on each Devices page of the website.) Recently I tried to donate to my device's porter, and found it hard to find how to do so. I tracked down his Paypal eventually, but it took some searching, and it might not be possible to find some porters. I thought if there were a Donate button on the website, similar to how there's an option on the OpenStore to donate to the app's developer, it might both remind people to donate, and make it easier to do so. I asked about this idea on Q&A #157 and Alfred and AppLee were both favourable toward it. But of course this requires work, and I have no skills with websites. I imagine it would require reworking the Contributors section on the Devices pages, and enabling an optional donate button next to the names of any contributors who'd like donations and who provide a link to their patreon/libera/whatever. It would get more complicated when there are many developers and maintainers. Who will the user donate to? Each of them? And is it weird if some of them request donations and others don't? But to me, it's still better to have the option, even if there are complications. Anyway, sorry to be making a suggestion with no way to help bring it about. But I wanted to float the idea out there, to keep our porters supported!

  • Creating Ubuntu Touch apps

    721 Topics
    7k Posts
    P
    @hlbkv Noted! I won't make any promises about the timeframe, but I'll do that when I get a chance

  • Porting Ubuntu Touch to new devices

    475 Topics
    3k Posts
    F
    The porting guide requires img2simg and simg2img which are provided up to Ubuntu 22.04 and not later. You can install these utilities using this snap: sudo snap install android-platform-tools sudo snap connect android-platform-tools:adb-support sudo snap connect android-platform-tools:block-devices sudo snap connect android-platform-tools:raw-usb sudo snap connect android-platform-tools:removable-media sudo snap connect android-platform-tools:network sudo snap connect android-platform-tools:network-bind sudo snap alias android-platform-tools.img2simg img2simg sudo snap alias android-platform-tools.simg2img simg2img

  • Lomiri, the operating environment for everywhere

    67 Topics
    568 Posts
    alan_gA
    As kugiigi says, Ubuntu Touch is using an obsolete version of Mir (1.8) with dated Wayland support. Also, most of the Wayland support in Lomiri comes from Mir (the rest comes from Mir's support for "custom" Wayland extensions). The consequence of that is that there's no much prospect of improving the Wayland support in Ubuntu Touch without first updating it to use the current version of Mir. The good news is that is work currently going on to get Lomiri working with the current version (2.20) of Mir. As of today this works on the machines of the developers involved and is close to landing in both the Debian and Fedora archives. However, it will still take significant time to get the rest of Ubuntu Touch migrated over to this newer stack. That is probably the task that can most benefit from help at present. After all that is completed, it should be possible for Ubuntu Touch to track the current version of Mir, and Wayland support will follow Mir. It is also possible to contribute to Mir's Wayland support, but that won't help Ubuntu Touch at present.

  • Discussion on translating Ubuntu Touch and its core apps

    57 Topics
    310 Posts
    B
    @arubislander Understood. Thank you!

  • A place to discuss ideas for promoting Ubuntu Touch

    54 Topics
    711 Posts
    J
    @Arnoldko About your question: UBports is a German foundation. And when I search for "public transport" at open-store.io (app store for Ubuntu Touch (UT)) I see four German, two Spanish, one Norwegian, one American, one Hungarian and one Swiss app(s). So you have maybe slightly more people who know some things about UT in this countries, but I do not think that this is significant. It probably depends more on what you want to do and how you want to structure your company (How closely do HW and SW teams need to work together? Where is the head of your company? Is this a commercial project?...). If your hardware team also takes care of firmware and drivers and you are only searching for some people who write some apps for you, you should find people who can do some C++, Qt and server stuff nearly everywhere. Specifically for Ubuntu Touch, you could maybe post a job description in this forum and let the people work from home. Some time ago some people related to Volla did a fundraiser to bring Android apps to UT. They commissioned some Russian developer and it was very successful. So maybe this could also be an option for you: https://forums.ubports.com/topic/5907/open-ubuntu-touch-to-all-android-applications/ https://forums.ubports.com/user/stanwood https://www.gofundme.com/f/anbox-on-ut?utm_medium=copy_link&utm_source=customer&utm_campaign=p_lico+share-sheet About no phone numbers: A lot of messengers and other services depend on verification via SMS. This is maybe something you want to consider. About using UT as a base: Please be aware that Ubuntu Touch has some limitations and depending on what you want to do (how much you want to modify the system), it could maybe be more convenient to start with something else (like Debian). There are currently also some people working on Lomiri (the desktop environment of Ubuntu Touch) for Debian. But this very much depends on what you want to do.

  • Other Projects

    Projects which are started by a group within the UBports community

    64 Topics
    373 Posts
    ikozI
    The last step installs the rootfs usually in system partition, see the install section of the porting documention. Basically flash the latest xenial image from the CI to system. Alternatively push the image with adb to /data/system.img when booted to recovery. Otherwise you could try ubports installer with only the systemimage:install command. You can also see the halium-install source code, particularly these lines. Be sure to check if this partition exists as partition schemes can vary.

  • For things that just don't fit in the other categories.

    814 Topics
    5k Posts
    stanwoodS
    @tuXut Interesting and definitely worth to watch. (Use a live translation subtitle because it's in German) Though, no mention to Ubuntu Touch nor UBports in the video. @libremax has gave further information on the french Ubuntu community forum. I translate his comment below in English: "Note that the port is being developed by the same FuriLabs team that developed the FLX1 and FuriOS. What's more, dual boot is also supported, making it a competitor to the Volla devices. For the moment, it works with an SD card. It remains to be seen whether the main storage memory can be used at a later date (as announced for the Volla Quintus and Volla Tablet)." Source: https://forum.ubuntu-fr.org/viewtopic.php?id=2090409#p22829131