Ubuntu Touch Q&A 79 Saturday 4th Of July At 19:00UTC
PhoenixLandPirat last edited by
are there plans to bring flutter support to Ubuntu Touch, Fluffychats new features and functions come in the flutter version of Fluffychat, and it'd be lovely to get all these fancy flashy features and get full support back on Ubuntu Touch.
Keneda last edited by
Did you managed to add export in VCF too?
This post is deleted!
Lakotaubp last edited by
Please note this thread is for questions for the Q&A and is not the place for support questions and answers. Also that this still applies...Please remember that questions on porting to device **** or it's status, and questions on bugs will not be answered
lduboeuf last edited by
@Keneda yes also done
Some pinephones have stability issues at the high dram frequency the images have. How will you address this for future non tech savvy users?
dobey last edited by
@farkasdvd There are plans to upgrade Qt, but "binary compatibility" is not as simple as that. There are plenty of things using private APIs (because they have to).
Please talk about camera update. I don't really need it but could be awesome to see it working, plus if you see now It can work as stated here: https://gitlab.com/ubports/community-ports/pinephone/-/issues/37
What do You think about ICE contacts and medical information quick access on lockscreen?
plotters last edited by
@UBportsNews Issue resolution process
Looking at all the issues, is there a process in place to decide which issues will be solved in which release, let's say prioritize them?
Gitlab has a nice board for this. It would help to focus efforts. There are for example many issue related to 2G/3G/4G, like 172, 152, 140, 120, 57. They could be all related.
Proposal for review
- tag all issues using predefined tags
- organize the board to see which issues are solved per OTA release
- voting system? (bug bounty). Which developer fixes which issues.
Maybe all of this is already in place, but I could not find it.
Please give us an update on the improvements that have recently been merged into the armhf and arm64 root file systems, as well as those you expect to land in the immediate future.
@dobey Thanks, I did not know that. It makes sense that there are binary compatibility issues if the D-pointer pattern is ignored
Could you give me an example where the private API is used?