I get this question a lot, why focus on making Lomiri compatible with upstream components and why are you helping getting Lomiri into different distros? Why not focus on Ubuntu Touch? Why focus on making UbuntuTouch better? Why not make device X better right now!

And for many this choice of development direction might sound weird, and I get that, it's hard to know this if you’re not a developer working on these components. So i’ll try to explain why this is the best way for us to keep going.

The fact is that, focus on making Lomiri compatible with upstream components and making it possible for Lomiri to enter more distros will make Ubuntu Touch better, and much much better in the long run. This is a long term plan to make the Lomiri stack much better.

Doing upstream work greatly improves the support to all the components we heavenly depend on, so for us to upgrade our stack (like Bluez, NetworkManager, ofono and MANY others) we really need to make our source both buildable, usable and comparable with upstream non ubuntu patched components, as we cant maintain components like canonical did, so we really need to depend on upstream fixes. and to be honest this is better then what canonical did, as you can see what state we are in due to that. A great example is bluez, we are way behind upstream here, this is mostly due to the xenial base that again is due to our stack depending on xenial specific patches that makes it impossible to just upgrade base or even bluez without doing heavy porting.

Yes there will be a period where fixes for devices won't be prioritized, but for us to fix those now and later need to fix them all over again because we just made our own little fork is a sure death for us. We need to make a sustainable road head of us and not keep working on our little buble. This has been an issue with ubuntu touch from the beginning, it was only canonical doing the work with no outside contributors, this is something we really want to avoid. We need to make Lomiri a Linux desktop environment not only a Ubuntu Touch one.

Yes devices will be prioritized, but we need to follow upstream and get up to speed with all the great fixes we simply can't use.

Once this work is done, we don't need to worry about it anymore, as keeping up with upstream will be so much easier. Most of the work is to replace the ubuntu only patches that really do not solve anything other than making it much harder for us to upgrade our base to for example 20.04 or even pull in never fixes that will fix many of our issues.

But most important of all, when we are fully compatible, we will get more distro supported, this in turn will have many more developers looking and trying out Lomiri. This will greatly improve the system as we will get more contributions! An example for this is Luca from pmOS, he has done amazing work that we all enjoy today. And we need more developers like Luca to make Lomiri more awesome! We need to get out of our little Ubuntu Touch bubble and work with the huge Linux community, this will make Ubuntu Touch SHINE

Hi all,

I'd like to start posting weekly development updates here on the forums - this is a bit of an experiment, so please let me know if you find these updates useful and what could be improved. The goal is to provide a high-level overview of our development progress.

This past week focused heavily on Noble development, with rapid changes to the image. I'm pleased to report that the latest daily build should have all hardware features working, including GPS, calling, sound, fingerprint reader, NFC, and more. We've also fixed several indicator bugs, making the 24.04 base system quite usable.

Currently, we're missing 24.04 built clicks, which is why some core apps aren't starting yet. While most of them build and run fine, we're waiting for some clickable changes to enable compilation. There are also some pending tasks related to accounts and push services, plus likely a few bugs to address.

Please test out 24.04 and report any bugs you find! Your feedback helps us improve the system.

Hi everyone,

After a brief delay caused by some medical issues on my part, I'm excited to announce that I’ve successfully developed a fully functional VoLTE implementation for Qualcomm devices. I've been using the Fairphone 5 (FP5) as my testing platform, and everything is now up and running.

I do however request some help with testing, anyone wanting to help out with that?

Hello everyone! Here is my personal points for a "perfect personal phone operative system". And I want to hear what your points is, Please let me know

The main points for "a perfect personal phone operative system" in my eyes, is Convergence, Open source, freedom, developer friendly and secure.

And the biggest one for me is freedom, where I don't get tracked everywhere I go, google knows where I am every second, and I have to ask me is this acceptable?... I really want to get out of Android, but the only thing that i'm missing is some apps. When we get anbox working right, I will fully switch. but I really hate the google tracking ting... I don't know why I have allowed it to go as far as it has now, but it kinda have been like that due to convenient.

Convergence, a phone I can connect to a monitor, mouse and keyboard and have a full desktop in front of me

Developer friendly, A phone where I can hack on how I want, a phone I can install the apps I want and a phone where I can explore what I want.

Secure, A phone I can trust can keep my personal data safe.

Open souce, A phone I can modify, contribute and hack on.

Thank you!

Hey everyone,

Starting a new bug fixing project for Ubuntu Touch called Smooth Edges (name pending). The idea is simple: fix the bugs that make people give up on UT or prevent them from trying it in the first place.

The Problem
Look, we all know Ubuntu Touch has rough edges. Some bugs are annoying. Some make daily use frustrating. And some make people pull out their old Android phone after a week. We need to fix those bugs first. I'm not talking about theoretical issues or edge cases that affect small amount of users. I mean the stuff that actually stops UT from being a usable daily driver.

How This Works
Instead of just going through the bug tracker randomly, we're prioritizing based on impact. Two questions:

What bugs stop people from switching to Ubuntu Touch?
What bugs make current users switch away?

Simple as that. Real-world impact over everything else.

Priority Levels
Breaking bugs down into 5 categories:

Priority 1: Core System Stuff - Boot loops, crashes, phone completely unusable. Fix immediately.

Priority 2: Basic Phone Features - Calls, SMS, WiFi, Bluetooth, notifications, camera. If these don't work, it's not really a phone.

Priority 3: Daily Use - Browser crashes, app store issues, keyboard problems, file management. The stuff you hit every day.

Priority 4: Polish - Like those tiny contact navigation arrows that are impossible to see. UI glitches. Things that make UT feel unpolished.

Priority 5: Nice to Have - Advanced features, edge cases, stuff that matters to specific users.

QtWebEngine Upgrade
This is a big one. The browser affects almost everything you do on a phone. We're planning to upgrade QtWebEngine, which should improve a ton of daily use cases.

Finding the Bugs, We're looking at:

Forum posts, support tickets, social media complaints
Comparing UT to Android/iOS to see what's missing
Actually using UT as a daily driver (dogfooding)
Testing

Timeline (really rough estimate)
Roughly 20 weeks broken into phases:
Weeks 1-2: Figure out what needs fixing and how bad it is
Weeks 3-10: Fix the critical stuff (Priority 1 & 2), start planning the QtWebEngine upgrade
Weeks 11-18: Fix daily use bugs (Priority 3), get QtWebEngine upgrade done
Weeks 19-20: Test everything, make sure we didn't break anything

What Success Looks Like

No critical bugs in stable releases
Phone features that just work
You can actually use UT daily without workarounds
People stop complaining about the same issues
UT becomes a real option vs Android/iOS

Not shooting for perfection, just want UT to be solid enough that you'd recommend it to someone.

Need Your Help
This only works if the community gets involved:

Tell us what's broken - What bug almost made you quit UT? What stops you from daily driving it?
Report bugs properly - Help us reproduce issues
Test fixes - Volunteer to test updates
Spread the word - Help gather more feedback

Tracking Progress
We'll measure:

Crash rate
Number of Priority 1-3 bugs
Boot time, battery life, app performance
Community feedback (less complains = winning)

So What Do You Think?
What bugs are driving you nuts? What would it take for you to daily drive UT? Drop your thoughts below.

Hey,

As you may or may not have seen, i have been a bit offline last week. This was due to one of my close family member got into hospital with an serious infection, it was so bad that he got picked up by the ambulance. And since I'm living in the same house and is really close to this person, this has not been an easy week for me. This is the reason why i have been gone, but with all this said, hes now back home and in much better shape, he is still recovering but overall doing fine. and I'm slowly getting back to everything.

Thanks everyone!

Hey,

So, I have done the "heavy lifting" so far, but there are still some work needed. Like getting wifi and bluetooth to work (I suspect just adding firmware will help, see example for pine: https://gitlab.com/ubports/core/rootfs-builder-debos/blob/master/pine64-common.yaml#L15). On the graphical side of things, there is still a host of bugs using the wayland session, but this will be worked on in parallel with pinephone and librem5, so this is not a raspberry specific issue. In short, when it gets fixed on pine it gets fixed on rpi too

The build "scripts" can be found here: https://gitlab.com/ubports/core/rootfs-builder-debos/blob/master/raspberrypi.yaml please send pr's here to improve the images.

Images will be built daily by the ci, they can be found here: https://ci.ubports.com/job/rootfs/job/rootfs-rpi/. flashing is really easy using etcher (https://www.balena.io/etcher/) to flash the sdcard.

This has been tested on rpi3, but should work on anything newer then 3 (as it needs arm64)

Some bugs that i saw:

• Won't start without keyboard or mouse connected
• Once unity8 has started, you need to reconnect the mouse/keyboard to make it work
• Performance using the opensource mesa drivers is still not "great"
• Needs swap
• A host of wayland session bugs

Little the same as i wrote on github https://github.com/ubports/ubuntu-touch/issues/860,

Also please understand, we are a small team with a huge task, we have many moving parts and moving to a newer version of mir and unity8 at the same time is not helping, we are doing our best to make an an awesome operative system. but we are in a really busy period after taking over from canonical, we updated to xenial, we are updating mir and updating unity8 all these are huge since canonical left it all the current version far behind the latest releases, this forces us to make major changes. We are also building Halium and following the evolving of android and newer devices to be able to follow the mobile marked. At halium we are also trying to move our sensor, gps, media and camera system over to an active maintained system instead of maintaining our own. And we are also looking at merging our patched in celluar and pulse with an active maintained one. Once we move things to active maintained systems where we can work together to get to the same goal, we will then get more time to focuses on core functions.

About replacing the browser, this is an huge part for us, we are not able to maintain our own fork of chromium (oxide) that why we are forced to move the browser, this move will in fact give more time to focused on the core functions on the phone.

We are moving to newer version of pretty much every part of the system, this is a major work. Once we have done the major upgrade we will get a lot more time. And in fact we are really close go get to this point, we now are super close to finish all the mir/unity8/libhybris upgrades. And we don't have a big enough team to focus on all the bugs right now as the code may have merge errors to be able to merge with never version and to risk spending lots of time on bugs that might be fixed in newer version. that's why we are upgrading, getting our source aligned with newer sources to then focus on fixing and improving.

In fact most of these bugs comes from the canonical days, they was a much bigger team then we are right now, so we don't work at the same speed.

We are doing our best with the small team we have.

OTA 8 will include new mir and unity8 (and many other updated parts), we hope these have many of these issues fixed, but we have to expect some bugs to be included also since the upgrade is so major.

Thanks for understanding

Smooth Edges: Current Bug Report

Ubuntu Touch Bug Fixing Initiative

Updated: November 27, 2024
Source: https://forums.ubports.com/topic/11644/smooth-edges-name-pending-let-s-fix-the-bugs-that-drive-you-mad

I'll keep this up to date

Note this is taken directly, this will need to be cleaned up once collecting is done

---

Table of Contents

1. Priority 0: Platform Viability
2. Priority 1: Core System Stuff
3. Priority 2: Basic Phone Features
4. Priority 3: Daily Use
5. Priority 4: Polish
6. Priority 5: Nice to Have
7. Installer Issues
8. General Themes

---

Priority 0: Platform Viability

Definition: Issues that affect the viability and sustainability of the platform itself.

Device Hardware & Support

• Most phones are 5+ years old - No one wants to invest in outdated phones with poor batteries. Future development not guaranteed, relies on individual contributors. Suggested solution: New "primary device" released every two years.

---

Priority 1: Core System Stuff

Definition: Boot loops, crashes, phone completely unusable. Fix immediately.

System Stability

• Random Lomiri crashes - System randomly crashing
• Lomiri freezing/crashing after extended use - Phone gets stuck/freezes after using it longer without rebooting or using more than 3-4 apps. Lomiri crashes and restarts.
• Lomiri crashes on shutdown/restart - Bug since 2015: When you've opened more than 3 apps and try to restart/poweroff, Lomiri crashes and restarts. Have to select restart/poweroff again.
• Passcode prompt stops working (Volla Quintus, 1.x daily channel) - Number keys don't enter characters or phone doesn't respond to full passcode entry
• Battery drainage on LTE - Missing proper app state management (background/foreground/suspended). Works on 2G with battery-saver app, but phone lasting less than a full day is not reliable.
• Daily reboots without command (Poco NFC X3) - Device reboots and disconnects SIM about every 12 hours (device-specific)

Networking & VPN

• OpenVPN non-functional/unfriendly - Can't access corporate networks, complicated terminal setup that doesn't work

Device-Specific

• Apps not properly accessing apparmor - Camera app on OP5T and other devices have apparmor errors in logs, unclear if they're important or can be ignored
• Mobile data on SIM2 doesn't work - PR exists for this issue

---

Priority 2: Basic Phone Features

Definition: Calls, SMS, WiFi, Bluetooth, notifications, camera. If these don't work, it's not really a phone.

Bluetooth Connectivity

• Car Bluetooth connectivity issues:
  • Bluetooth audio playback problems in car
  • Car refuses to turn up music volume
  • Contacts don't sync - only shows numbers when calling, not names
  • Music controls (play/pause/previous) unreliable from car/headphones
  • Music auto-continues after Bluetooth disconnect
  • Answering calls while driving unreliable due to connectivity/UI issues
• General Bluetooth improvements needed - Usable with certain prerequisites but could be better
• Bluetooth almost unusable - No file transfer possible, no HFP (hands-free profile) in cars

Email & Notifications

• IMAP email notifications don't work (outside Gmail)
• Green email icon persists even after viewing notifications - should revert to non-active state after checking
• Keeping Dekko updated or replacing it - Email is critical feature for most users

Camera

• Multiple cameras not supported - Devices with multiple cameras (e.g., Volla Quintus with 3 cameras) can't switch lenses in main camera app, though test apps can access them
• Camera too slow, images blurry with motion or bad lighting (may be device-specific)
• Camera app lags behind Android - Slow focus, missing macro function, wide angle, panorama modes
• Camera app crashes - Daily crashes or device-specific, requires reboot (Poco NFC X3 and other devices)
• Camera image quality poor - All pictures and videos have colors off and overall poor quality (may be device-specific)
• Camera not fully supported - Partial hardware support on some devices

Communication Features

• VoLTE - Needed for calls, will be required across Europe in coming years. Not reliable yet, becoming "basic phone functionality" in more countries
• VoLTE issues - Phone app freezes when receiving call while already online with VoLTE enabled, requires reboot. Switching to airplane mode often disconnects VoLTE, requires reboot.
• RCS (Rich Communication Services) - SMS/MMS replacement, will be next big point for UT

Security

• Encryption should be mandatory - Several users left UT because of lack of encryption. Entire device should be encrypted when powered off. Bonus: lock-screen encryption like Android.

Display & Interface

• Display cutouts and rounded corners not handled - Makes upper taskbar display incorrectly (especially FP5), restricts usage of indicators. Clock not fully visible. Nowadays a must, instant frustration for new users with no option to set it correctly.
• Notch handling + too many indicators:
  • Dual SIM with roaming = 4 network icons alone
  • Rotation lock is entire pull-down with one item
  • Many pull-downs have only 2 items
  • Suggested: Remove rotation lock, Bluetooth, GPS icons entirely from header
  • Merge dual SIM icons into one
  • Email icon should only show when there's a notification
• Notification area too fragmented - Better to have less indicators or option to reach most used on same "page". Hard to swipe down without accidentally selecting wrong indicator.
• Lomiri must avoid rounded corners and camera notch - Bring indicators under camera notch

Browser

• Morph browser old and falling behind - Mentioned by multiple users as Priority 2
• App menu too long (12 actions) and redundant - Use ToolBar for additional actions
• Downloads not integrated in indicator since Oxide

Messaging

• Improvements needed in Teleports, Matrix, Signal apps - Messengers are most used smartphone apps
• Call/video call options needed in browser and messengers

Backup

• Backup function should be in UT installer or at least have tutorial/instructions
• AGPS missing - Navigation hard to rely on without it
• Data backup and syncing missing

---

Priority 3: Daily Use

Definition: Browser crashes, app store issues, keyboard problems, file management. The stuff you hit every day.

Browser Issues (QtWebEngine)

• Outdated QtWebEngine - Most frequently mentioned issue
• Firefox alternative has no clipboard
• No autoplay disable option in native browser
• Poor web smoothness

Keyboard Problems

• Keyboard crashes during active SMS/chat conversations - "Gets my pulse going"
• Random OSK crashes
• Keyboard positioning too low - Need ability to raise/lower keyboard. Ambot installer keyboard works better.
• OSK issues:
  • Predictive text gets in the way
  • Weird behavior when typing/deleting
  • Paste doesn't work between apps

Multimedia & Files

• Nextcloud photo sync unreliable
• Gallery loads slowly
• Video playback issues - One of UT's weakest points since beginning:
  • Poor UX in Camera app preview - opens separate Video app that stays open after playback
  • Video flipping at end of playback
  • App crashes (e.g., in Teleports)
  • Totally stops working on some devices until restart of media hub or reboot
  • Experience generally bad
• Camera app crashes (device specific but affects several devices)
• Too slow to take picture/video - Too much delay, sometimes fails and needs reboot

Navigation & Location

• Navigation apps unreliable/non-functional - Forces use of Waydroid
• GPS position doesn't work reliably in webview (works in PureMaps) - Orientation/compass problem, important for Google Maps public transport itineraries
• Faster GPS needed - Initial fix can be slow, too slow for reliable navigation
• GPS too slow - General positioning speed issue

Calendar & Contacts

• Calendar sync failures with Google/Nextcloud - Leads to missed meetings. Event links and call info not clickable/openable
• Call history unclear - Hard to track communication sequence with contacts (missed calls, outgoing, answered)
• Date indicator - Tapping dates doesn't show all calendar entries

Networking

• Cellular network re-connection sometimes needs reboot
• Loses cellular data connection (especially dual SIM) - Have to switch from 3G to LTE/4G in settings to get internet back
• MMS doesn't work if WiFi is On
• Dual SIM boot issues - Sometimes boots with only one SIM working or none, requiring reboot. Can also change default parameters to SIM2 that persist even after reboot with SIM1.
• WiFi always trying to connect to last used network - Instead of the one with the best signal

VPN

• No usable VPN UI - Required for corporate users, Wireguard, Tailscale. Terminal commands won't work for most users. Need integration for several protocols for open WiFi security.

Email (Dekko)

• No HTML replies - Everything sent as plain text only
• Broken message forwarding - Forwarded messages become garbled/unreadable for recipient due to plain text limitation

System & Performance

• Interface sluggish/freezes - Not fluid or snappy, varies over time (may improve with next Halium upgrade). Sometimes freezes for fraction of second or even few seconds.
• Overall performance could be smoother - When switching between apps
• App start time much longer than Android - Even simple apps like calculator or clock need several seconds to start
• Mir 2 migration essential - Convergent Linux apps don't work due to scaling/keyboard issues. X server jankiness is a problem (keyboard, slowness, focus issues).
• Developer mode keeps turning on after every boot even when toggled off (security issue, may be daily channel specific)

Apps & Integration

• No default target selection with url-dispatcher or content hub
• Calendar sync issues - Painful to get working reliably again when it breaks
• Native Matrix client needed - Ideally disconnected from "Matrix" branding, just "UT Messenger" or similar
• System-side backup feature - Not everyone can setup Nextcloud/Syncthing easily

---

Priority 4: Polish

Definition: UI glitches, UX improvements. Things that make UT feel unpolished.

Keyboard & Input

• Keyboard .tld button (.cz, .com) - Frequently misclicked instead of spacebar, causes DNS errors when using address bar for searches (typing "query.czsearch.cz" instead of "query search")
• Keyboard sometimes hard to use - Writing sentences full of mistakes because of missing blanks. May be due to keys being too narrow or input being too slow. Tip: Disabling haptic feedback may help typing speed.

Contacts & Dialing

• Clicking contact in history doesn't call directly - Just pre-fills number in dialer instead
• Contact navigation arrows impossible to see - Small visual indicators for swiping navigation

Buttons & UI Elements

• Small back buttons - Hard to tap accurately, especially for one-handed use. Major issue for users coming from Android. Examples: dekko, uRSSes - sometimes can see button press but have to tap again because it was too short.
• Notification UI - "Clean" button should float at bottom, not positioned relatively below all notifications

Header & Indicators

• Header clutter - Too many icons make it hard to see time:
  • Remove rotation lock, Bluetooth, GPS icons entirely
  • Merge dual SIM icons into one
  • Email icon should only appear with actual notification

Apps & Consistency

• App counters/badges - Should use notifications indicator instead. One place for all notifications instead of going app by app.
• Core apps have inconsistent UI - Random icons, different designs
• Notes app abandoned - Needs work
• App drawer organization - Need ability to make folders, favorites and rarely used sections

Audio

• Audio feeds to both earpiece and speaker simultaneously

Security Perception

• Lack of security trust - Unlocked bootloader, corporate data/banking inside Waydroid creates feeling of insecurity

Device-Specific

• Under-screen fingerprint reader doesn't work (Volla Quintus)
• Fingerprint reader activation - Would be nice to unlock Lomiri without pressing button first

Connectivity

• Connect to public WiFi via QR code - Missing feature

APIs & Integration

• Auto-fill/auto-type APIs missing - Copying/pasting passwords is inefficient and insecure
• KDE Connect port needed - Phone/computer sync is very handy

Waydroid Integration

• Notifications not propagated to main notification bar - Should function like native notifications, opening corresponding Android app
• Multiple window mode needs icons in sidebar/app drawer properly
• Copy/paste doesn't work inside Waydroid or between Waydroid and system
• File access not transparent - Waydroid should see home directory without copying files via Waydroid Files app

---

Priority 5: Nice to Have

Definition: Advanced features, edge cases, stuff that matters to specific users.

Apps & Software

• Productivity apps missing - Native MS Teams, Slack, Google Meet support
• Spotify non-functional via Waydroid - Painful experience. Proposed solution: Integrate mainstream desktop Linux apps (Snap, Flatpak, AppImage) into OpenStore as alternative to Waydroid
• Cloud notes app missing (e.g., Nextcloud integration)
• Banking software and government apps missing - Hence Waydroid use
• Snap applications should be offered to fill gaps
• Update snapz0r for direct snap installation without terminal
• Docker container cannot start normally - Nice to have feature

Features

• Shared clipboard - Like iOS/Android + KDE Connect
• QR code reader extremely unreliable
• Audio playback speed control
• Swype feature in OSK - Currently only possible with proprietary code. Options to explore:
  • AnySoftKeyboard (open source swiping)
  • FUTO (source-available, open swipe dataset)
  • Magic Keyboard for Sailfish OS
  • Heliboard uses proprietary Google library
  • Florisboard has glide typing but functionality uncertain

System

• Core apps force specific viewport - Clock app mentioned specifically, shouldn't do this
• Dash filters for apps
• Backup/sync app with PC - rsync was removed (can be reinstalled via crackle)

Privacy & Security

• Browser privacy/security lacking - Need ability to change DNS server, secure browser with anti-tracking/fingerprinting extensions

Documentation

• Device port maintenance info - Not just "Last commit on X date" but also why and for what
• Better documentation on which apps can replace popular Android apps, how to get VPN or OwnCloud working
• Precise description of what you get by installing UT vs what you lose by changing ecosystems

---

Installer Issues

Definition: First impression problems that prevent adoption.

Installation Experience

• Installer can block/hang - Pressing continue button on phone during assumed hang causes issues, needs reflashing of Android. Need better warnings.
• Raining arrows icon confusing - Unclear what's happening during download, meaning not obvious to users
• Installation complexity puts people off - Fear of rendering phone unusable
• Offer stable versions before dev versions in installer
• Polish critical for installer - Last 5% of polish can get or stop thousands of users. Last 1% toward perfection very important.

---

General Themes

Most Frequently Mentioned Issues

1. Outdated browser/QtWebEngine - Mentioned by nearly every user
2. Bluetooth connectivity problems - Especially car integration
3. Display cutout/rounded corner handling - Makes UT look unfinished
4. VPN integration/UI - Multiple users need this
5. Encryption mandatory - Multiple users left because of this
6. Camera issues (slow, crashes, multi-camera support) - Multiple users
7. Dekko email client needs work - Multiple users
8. Waydroid integration improvements needed
9. Dual SIM issues - Multiple users
10. VoLTE - Increasingly critical
11. Video playback - Consistently problematic across system
12. Small back buttons - Especially for one-handed use

Key Insights from Community

On Polish vs Features:

• "Polish" has much more important ranking for new users than Priority 4 suggests
• A phone is a status object - obvious defects block adoption
• First impressions are critical - can block influencers from featuring UT
• For installers, getting to 95% isn't enough - last 5% of polish critical

On Browser:

• "Without an up-to-date browser, we don't do much!"
• Affects almost everything you do on a phone
• Absolute priority according to multiple users

On Device Support:

• Future development not guaranteed for older devices
• Heavily relies on individual contributors
• Need for sustainable hardware strategy

On Security:

• Privacy-focused users need adequate browser protection
• Encryption is deal-breaker for many users
• Corporate users need VPN support

---

Document Statistics

• Total unique bugs reported: 100+
• Priority 1 (Critical): 7 issues
• Priority 2 (Essential): 25+ issues
• Priority 3 (Daily Use): 30+ issues
• Priority 4 (Polish): 25+ issues
• Priority 5 (Nice to Have): 15+ issues
• Installer Issues: 5 issues

---

This document compiled from UBports Community Forum thread "Smooth Edges (name pending) - Let's Fix the Bugs That Drive You Mad" as of November 27, 2024. Includes community feedback from multiple users across various devices and use cases.

Please discuss here: https://forums.ubports.com/topic/11644/smooth-edges-name-pending-let-s-fix-the-bugs-that-drive-you-mad

This category is only for ongoing ports, any other post will be remove or moved.

How the ports should look like
Title: "Device name (codename)"

Posts here needs to include the current status of the device, sources and how to install the device. Try to structure the post to be easy to get the information. Also add some info on how to help or contribute to improve the device.

Example:
Title: "Oneplus one (bacon)"

Port for Oneplus one,

Sources:
Kernel: link to kernel
Device: link to device configs
Halium: Link to halium-devices manifest

Status:

• Wifi: works
• ....

Install:
How to install

Hello everyone!

The expected release date for Ubuntu Touch OTA-13 is Friday, Sep 4 Wednesday, September 9 Monday, September 21.

This forum post is a companion to the upcoming OTA-13 call for testing blog post.

Please post any general observations you have while testing the current image in the rc channel, as compared to OTA-12, in this thread. The current release candidate (rc) is 2020-W37

If you have any comments on any of the specific issues in the OTA-13 tracker, please post them in the issue thread so they are easier to track. OTA-13 tracker: https://github.com/orgs/ubports/projects/17

Please note that only critical and security fixes will be able to enter OTA-13 as this point, normal bug fixes and new features will need to wait for our next release. Please do not discuss normal bug fixes and new features here.

A big thank you to everyone that made this possible! I'm super happy to see these release being bigger and bigger with contribution from so many beautiful people! Thank you everyone!

• Much love!

Edit 2: On the 7th of September the release date for OTA-13 was moved from the 9th of September to the 16th of September

Edit 3: On the 15th of September the release date of OTA-13 was moved from the 16th of September to the 21st of September.

Hi,

This will just be a quick "how-to" upgrade your apps to 16.04

So, first off you need to update your manifest, here you need to set framework to ubuntu-sdk-16.04

Next and important step (without this your app will fail to install), you need to update your .apparmor file, here you need to set policy_version to 16.04

Here is an git diff how i did this on the ubports app:

diff --git a/com.ubuntu.ubports.apparmor b/com.ubuntu.ubports.apparmor
index 06ff04c..5f9e005 100644
--- a/com.ubuntu.ubports.apparmor
+++ b/com.ubuntu.ubports.apparmor
@@ -7,5 +7,5 @@
         "location",
         "content_exchange"
     ],

-    "policy_version": 1.3
+    "policy_version": 16.04
 }
diff --git a/manifest.json.in b/manifest.json.in
index 10c8bc7..8af6c2d 100644
--- a/manifest.json.in
+++ b/manifest.json.in
@@ -10,5 +10,5 @@
     },
     "version": "1.6",
     "maintainer": "UBports <jan@ubports.com>",
-    "framework" : "ubuntu-sdk-15.04.6"
+    "framework" : "ubuntu-sdk-16.04"
 }

Finally build for 16.04 using clickable

clickable -k 16.04

That's it, your app should work in 16.04

Hello guys!

This is will just be a quick development update.

So the last ~2 weeks the development has been really slow, this is due to me having some personal issues i had to take care of that had be unable to do anything. So that is why it has been kinda quiet from both me and development on my side.

But don't worry, i'm somewhat back now and will hopefully be fully back in ~1 week

Xenial (phone) is still in the scope, I was expecting to be done with all the backlog bugs and most of the ota-4, but i was also expecting to have the first xenial rc landed, but due to my issues I have not been able to complete this.

Unity8 is still in the scope, but has a lower priority then xenial (phone). Unity8 is somewhat broken on bionic due to Ubuntu (upstream) have removed the mir patch from mesa, this means none of the apps will work. We have to change this to using the wayland protocol for all the apps. But on top of this mir has bumped the abi/api version for miral so we have do some some work to get things building again. We will hopefully get this working quickly! (at least before bionic release :))

We also want to make a architecture overview of Ubuntu touch including sources and build instructions for the different parts that powers Ubuntu touch. This will both be nice for Developer and Users alike. Please contact if you want to help out with making this

And lastly,
I want to do a call our for help with development, If there is any of the areas you want to work on/help with please don't hesitate to contact me if you need help getting started.

Thanks you!
You guys rock!

Call now do work on the latest release
also camera is somewhat working on arm64.

And you can now install it with the installer

One point i want to add, is that we might want to remove the "Ubuntu logo" since for this exact reason we are limited. Things that we want to include yumi on might be approved each time, like if we want to have it on the pinephone for example. We also want to move into debian and other distros, so a removal of the logo would be a good move in my opinion.

Yumi itself can be used by anyone, that was one of the main point when it was made, but i see now adding the ubuntu logo was a mistake.

The reason why you got banned is because you was rude to other people on the forum, THIS IS NOT IN ANY WAY ACCEPTED BEHAVIOR, you got an warning for this. Even though you got an warning you got into a discussion with one of the admins in which you there proceeded to be straight up rude to the admin, this resulted in a BAN. END OF DISCUSSION!

@Jackl said in PinePhone:

2 Being a privacy oriented phone, it would be cool a physical switch to turn off the module, and maybe the cameras, microphone. I dont trust very much the module stand-by state.

It will have physical switched for all those

@Jackl said in PinePhone:

• 3 The display manager should be i3 or lxde (kde or gnome would be f00l(no offence ubports)) and the OS arch or debian. All the always-running apps should be gtk2.

gtk on phones is a bad idea. It's not designed for low end hardware nor is it designed to work on a phone form factor. Why do you want gtk?
Qt has superior performance on embedded, ARM based devices. Also LXDE is moving to LXQT which is qt based.

UBports does not use kde or gnome, we use unity8 that's crafted specifically to work on phones and desktop alike, based on qt.

i3 would be hard to use? no keyboard?

But you can run whatever you want there is debian builds already for it, and i know other project are working on it as well, like arch, plasma mobile, etc.

@Jackl said in PinePhone:

4 I hope that the pinephone 2 will use a mediatek or qualcomm soc. Not a surprise a battery of 3000 mAh.

It will use the allwinner a64

@doniks Yes there will be a transition phase, we wont "just remove" oxide The phase time really depends if and how many apps it breaks, since we keep Ubuntu.Web we really hope the transition would be minimal.

What i meant with 100% QtWebEngine is that every part that is "pre-installed" like browser, web container etc would be moved over, not that we would remove oxide.

Ubuntu.Web will still exist and will not go anywhere, It will still be based on oxide until oxide is removed, once oxide is removed it will be moved over to QtWebEngine so it will continue to work (unless it uses oxide only apis)

The oxide api will be removed at some point, when is still unsure. We would need to go over and see how many apps use this raw, and how many apps will break as an result of this. We will also try our best to create a compat layer to be able to make the transition without breaking apps (like webapps+)

Hi all,

So since we are all stuck at home, me and Alfred had a thought, lets create a online hacking group where we can get together have a good time and just hack on Ubuntu touch. there is no topic but we want to float around with porting and focal hacking. We will start 17.04.2021 17 UTC and carry as long as we want.

We will be over at https://whereby.com/ubports-chat

So i have good news here! So after last thing got pushed for OTA4, i got more time to work on this, and I got some progress! after merging upstream and some more hacking I have got it working on qcom devices! It will still take time to be something usable for daily use, but i will push some test images this week. After OTA4 is out we will put more work into making anbox smooth and ready for daily driving.