Ubuntu Touch Q&A 86 Saturday 10th Of October AT 19:00 UTC
-
Given that Oxide based webapps apparently do not work on devices such as PinePhone and PineTab, and given that all the major native apps that used to use Oxide have been updated to use QTWebEngine instead at that this point - does it make sense to start the purge of Oxide support from all the UT images, as well as remove the webapps based on Oxide from the Open Store, either for OTA-14 or OTA-15? Isn't this move ultimately needed to free up space in the images to allow for new features anyway, and wouldn't it be advisable to not have Pine device users not get frustrated by having so many webapps not be usable on their devices still in the Open Store?
Best regards,
Steve Berson -
Who (as organization, group, company, volunteers etc.) is responsible for bringing Pinephone to the mainline linux kernel and if the UBports is involved, how does it contribute to this challenging task?
-
This post is deleted! -
Is there any consideration in having a separate build that is not a read-only filesystem, e.g. more of a standard Ubuntu install? If there were something like that, I would think it could stand as the main development branch that would allow faster upgrade to 20.04 / wayland / systemd / etc. Then it could be a testing ground that new releases of the "stable" or "consumer" read-only system would come from.
It would also not frustrate any potential developers who want "standard Linux on a phone" (mobian, manjaro, fedora, etc.).
In summary, I understand a lot of the reasons behind the read-only system for stability, for security, for end users, etc. but I fear it keeps away possible developer interest that would benefit Ubuntu Touch in the long run if it were more "traditional Ubuntu" on a phone?
People could be trying all sorts of things like flatpak / snap / different apps, etc. I know there is Libertine but there is some performance issues and it isn't available everywhere, etc. So take the chains off and see what happens? I suspect a large growth of the community (???)
-
@rik please could you delete the first of your posts as you have posted another. you can use the three vertical dots for the options.
-
-
Seems like there is some work going on to get webpush notifications work in Morph. Will that also work in webapps? What about qt-apps with embedded qtwebengine? Any chance that this will lead to PWA support in the future?
-
Accounts has been semi broken for a really long time now. As of OTA-13 it doesn't even trigger the OSK when trying to input for example the Nextcloud credentials (and even with cut&paste I could not get it to work). Yet (non-google) calendar and contacts (the all elusive CardDAV
) syncing are such a vital part of using a smartphone. Is anyone currently even looking into this? Maybe you could join forces with Plasma Mobile on that and support a common system like this: https://github.com/KDE/kaccounts-integration ?
-
-
Are there any plans to bring category based search to the search bar in the App Drawer? Seems this, along with the ability to initiate an internet search directly from the App Drawer search bar, would be a welcome feature improvement that might make sense to prioritize for OTA-15.
Best regards,
Steve Berson -
I'll second that...
A "Search your computer" function like Unity7 had would be a valuable feature... especially as things often seem to get put in nether regions.
Not a top priority though.
-
@rik said in Ubuntu Touch Q&A 86 Saturday 10th Of October AT 19:00 UTC:
Is there any consideration in having a separate build that is not a read-only filesystem, e.g. more of a standard Ubuntu install? If there were something like that, I would think it could stand as the main development branch that would allow faster upgrade to 20.04 / wayland / systemd / etc. Then it could be a testing ground that new releases of the "stable" or "consumer" read-only system would come from.
It would also not frustrate any potential developers who want "standard Linux on a phone" (mobian, manjaro, fedora, etc.).
In summary, I understand a lot of the reasons behind the read-only system for stability, for security, for end users, etc. but I fear it keeps away possible developer interest that would benefit Ubuntu Touch in the long run if it were more "traditional Ubuntu" on a phone?
Based on the reactions to comments that I recently posted in the "The road(map) explained" thread, what you (and I) suggested doesn't seem likely, or at least not likely in the near future. However, Manjaro Lomiri may fit your needs.
-
i wanted to know if someone is developing WiFi Calling for UbuntuTouch?
-
Q: hacktoberfest? (now opt in only)
-
@rik you can remount r/w
-
@mateo_salta yes but everything wiped out at update. Good discussion from the link @GizmoChicken posted. The way I see it the challenge is a bit of a "chicken and egg" problem. Some devs want "pure linux" so they don't come. Since they aren't here, development team is small and can't expand to a broader scope.
At the same time, very good points have been made about needing to be compatible with android devices. Pinephone is a tinkerers delight, but is less powerful than a N5 from 2013. So I see Ubuntu Touch as a viable "daily driver" in its current form for halium devices / former android phones. But a lot of people want "pure linux phone" which is hard to have as a daily driver yet. It is a different group.
Ok enough for now
