UBports Robot Logo UBports Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. UniSuperBox
    3. Best
    U
    Offline
    • Profile
    • Following 0
    • Followers 9
    • Topics 88
    • Posts 599
    • Groups 1

    Posts

    Recent Best Controversial
    • I have ended my contract with the UBports Foundation

      Hi everyone,

      I'm letting you all know that I have ended my contract with the UBports Foundation, effective January 28, 2022. Therefore, my role as Development Manager within the UBports community has ended.

      What's changing?

      My departure is likely to change how the UBports Foundation's Board of Directors, Board of Trustees, contracted project teams, community, and the public interact. This change is most likely for the better: leadership may be formed within all of our (already tightly-knit) bodies to report on progress and next steps. Whereas I've been a nexus for project information, tasks, people, and interaction, these centralized functions will now be distributed between interested parties.

      Or, at least, that's the hope. This project has never functioned without you, dear reader. Your encouragement, leadership, and contributions make Ubuntu Touch possible. Now there will be a space left where I once contributed that pulls in new, unlikely faces.

      I'm not dying, or at least I'm not planning on it. I'll still be available for the occasional question or two. πŸ˜‰

      I'm also still available for my duties as the UBports Foundation Membership Committee chair. Watch out for more news about my assignments soon.

      I've left my leadership responsibilities to the Ubuntu Touch based on Ubuntu 20.04 project in the capable hands of our contracted project team.

      It is undecided whether the Ubuntu Touch Q&A will continue in its current format, use a new format, end its run, or do something else.

      Why leave?

      I'm all too familiar with the speculation when a project leader resigns. Allow me to alleviate some of that.

      I enjoy what I do, I appreciate and support our team. I love that we were able to build a kind, friendly community that's open to a great many people. We're building excellent software, even if we're still a little unsure of what it should do best. However, I've already stated that I experienced burnout last year. I took a week off in October to attempt to alleviate the problem. It was not enough.

      For the past four months, I've put myself under more stress and given myself less time to recover from it. Ultimately, it's led to me being unable to meet my expectations and yours. That feeling of missed expectations compounds my stress, and it's all snowballed. I now dread turning on my laptop, opening Telegram or my email, and even opening GitLab. Surely this can't be healthy. My resulting mood in communication isn't conducive to a healthy, productive environment.

      At this point, I think I've read every self-help book. I'm a newfound expert in getting rid of distractions, reducing stress, working intensely, being kind to myself, self-reflection, and generally being more productive or healthy. Unfortunately, these have not combined into a proper set of actions and environment for me to thrive.

      I also have dissonance compared to the UBports Foundation's values. The Foundation is set up to own copyrights, collaborate between disparate organizations, and drive projects where those organizations cannot do so themselves. This model does not have space for a rolling-contract, non-project-based, jack-of-all-trades community, development, and product manager any longer. Additionally, I've watched our community sentiment change from "what can we do together?" to "what can the Foundation do for me?" I have contributed to this misunderstanding of purpose, partially because I want to do things that the Foundation does not do. But what I would like in an ideal world and what we have are much different things.

      What's next?

      I'll be taking a bit of time to decompress and reorient. During this time, I'll be mostly unavailable for contact. Then, I'll come back around to finish things left incomplete, particularly in the Membership Committee.

      posted in General
      U
      UniSuperBox
    • It’s official: the UBports Foundation is Ready for Launch

      Two years ago to this day, Canonical announced the discontinuation of Ubuntu Touch. But, you know, as a valued community member, that we have all worked hard to keep Ubuntu Touch alive and the project is stronger than ever.

      We are proud to announce that UBports is now about to be granted the status of an official foundation that is recognized by the authorities in Berlin!

      Read our official announcement here:
      https://ubports.com/blog/ubports-blog-1/post/it-s-official-the-ubports-foundation-is-ready-for-launch-215

      Thank you for all of your support, and we look forward to even better years to come.

      posted in News
      U
      UniSuperBox
    • What's this Edge merge anyway?

      TL;DR

      • The revised Unity8 and Mir 1.x are coming in OTA-12
      • You may wish to switch from the devel to rc release channel on any devices you're using daily.
      • We might need to rewrite history on some git repositories. If this happens, we will keep a tag named xenial-before-2019-edge-merge to preserve the history.

      The rest

      We've been talking about "the Edge merge" for a while, and I understand that it is a rather opaque term to many people. I hope I'm able to answer your questions about what "the Edge merge" really is.

      In short, what we'll be doing over the next few days is merging code which currently deploys to our Edge channel into branches which deploy to our normal release cycle. That releases daily into devel, which gets promoted to rc, which in turn gets promoted to stable. The next update on our stable channel will be OTA-12.

      In order to understand why this is important, first I'll differentiate Edge from the normal release cycle. Ideally, most of our maintenance and feature work gets deployed into our xenial repository. This repository is used, along with the default Ubuntu repositories, to build the Ubuntu Touch images which land in devel. The Edge images are built with the xenial_-_edge repository overlayed on our xenial repository, allowing us to test large migrations before they impact a large number of users. So, at a base level, Edge is just devel with newer or more experimental packages laid over it.

      Currently, we are using the Edge repository to test a huge migration away from Mir 0.24 and Unity8 from 2015 - as deployed in Ubuntu Touch up until now - to Mir 1.x and Unity8 from 2017 - the latter had begun to neglect phone users in an attempt to bring it to the desktop faster. That neglect caused a large number of issues which needed to be fixed. Having these changes built into images for every device every day (in Edge) for months has allowed us to iron out most of these issues.

      We will also need to rewrite git history on the xenial branch in some cases, as the phone and desktop platforms diverged enough to prevent them from being merged cleanly. In these cases, we will save the old xenial branch in a tag called xenial-before-2019-edge-merge to ensure the history is preserved.

      During this time, we will pause updates to the devel channel for all devices. This will prevent you from receiving an update which could be very broken and, possibly, render your device unbootable. If you don't want to come right onto the bleeding edge when we re-enable those updates, now is a good time to switch to rc or stable using the UBports Installer (don't check the option to wipe your device) or by heading to "Settings -> Updates -> Update Settings -> Channels".

      Ubuntu Touch will have many fixes after this merge is finished, but it will also be broken in some new and interesting ways. Our goal as we reach OTA-12 is ensuring that the transition from OTA-11 is smooth. This will involve fixing those new and interesting issues.

      posted in OS
      U
      UniSuperBox
    • I wanna go home

      After https://github.com/ubports/unity8/issues/121 was filed and we've had not one, but many sour discussions about this or related topics, I figure we should try to slow it down a bit.

      People are getting antsy (read: livid) about the changes to Ubuntu Touch in upcoming releases. In this post I'll try to tackle the issue of "home." More specifically, Where is home in Ubuntu Touch now?

      The case for going home

      Home, in terms of an operating environment, is the first place where a user arrives and a place they can return to. It's taken many forms over the years of personal computing:

      • 7000 BYTES FREE, READY.
      • $ (or C:\>)
      • Windows' Start menu (Then its Start screen, then its Start menu again)
      • Screens which are actually called "Home" on Android and iOS

      The concept of Home is slightly different for every operating environment, but it serves a few important purposes:

      • It is used to start other interactions with the environment (applications, for example)
      • It is "returnable," a user should always know how to get to it. Now that operating environments are used for multitasking, this shouldn't be by destroying all running activities.
      • It is "safe," a user should always know what to do once they get there

      Home serves as an anchor point for the environment's experience. If the user gets lost or stuck, returning home should help.

      The Dash

      We can currently assert the following things about Unity8 on a mobile handset:

      • Long swiping from the left of the screen always returns you to the Dash.
      • The Dash is a window and is shown in the app stack.
      • Due to the last point, the Dash remains focused when the device is locked and unlocked.

      The dash is home.

      The Drawer

      The following things about those assertions have changed:

      • We no longer have the Dash. Long swiping from the left of the screen opens the App Drawer.
      • The Drawer is not a window and does not appear in the app switcher.
      • The Drawer does not remain focused when the device is locked and unlocked.

      It is consistent with our desktop experience.

      But it's got everyone up in arms.

      Where is home now?

      By far, the most important question I see us asking ourselves (indirectly) is, "where is home now?" The answer... isn't straightforward.

      Is the Background home?

      Users will land in the Ubuntu Touch experience at the Background (NOT the desktop, which implies you may put things on it):

      screenshot20190408_210722720.png

      When arriving at the Background, the Launcher (some call it the dock) appears to greet them. The user may arrive at the background by booting the device or closing all their apps. By offering the Launcher, the background can be used to start other interactions AND it is safe. However, it breaks one of our main rules: There is no way to return to the background without destroying all of your activities.

      Is the Drawer home?

      The Drawer may be opened by long-swiping from the left of the screen or tapping on the big ol' orange button:

      screenshot20190408_211357174.png

      This can be done at any time. This makes the Drawer returnable. It is very simple, so I assert it is safe. And, well, it starts new interactions.

      Something about it has people really uncomfortable, though. Maybe it's the fact that, unlike the Dash (or iOS' home, or Android's home), the Drawer is dismissed when you lock the device. This resonates with me a bit, a serial home-presser before locking my device. I like to start at square one whenever I pick up my phone.

      Can we find home?

      Does this add a new requirement to home? Does home also need to be durable (or comfortable?), lasting through transitions to lock states or other huge events?

      Or, is this okay? Is this a case of a different design being more efficient? The ideal use of Unity8 is pinning applications to the Launcher, where they can be managed and switched between (even on the lock screen).

      screenshot20190408_212713265.png

      (Maybe the Launcher is home, or the lock screen!)

      Home must be durable

      If home must be durable, the Background is close to being home. The only problem is we can't return to it easily. There are an infinite number of ways to solve this, here are a couple I've thought of:

      Go to background as an app

      1e24c9b3-a74c-49e2-a020-ab42d5d8c046-image.png

      Hide apps appears as another window in the app switcher. It is always located behind the most recently used app, as shown here.

      Go to background as an action

      We discussed having Go to background as a specific action you perform on the app switcher. It could also go somewhere else, but there's nowhere to put it. This issue proposes having it be the "Cancel" action of the app switcher, when you tap in the blank space. That caused a lot of upset since it changes the current behavior (tapping in the blank space goes to the app you were just using, today you learned) and is not explicit (as a Python developer, I agree). Here's a way to make it explicit:

      0898c284-15ab-4a87-9f08-5622bdbb3a2d-image.png

      (It took me twenty minutes to make that, don't judge me)

      Nah, this is more efficient

      If home doesn't need to be durable to be home, maybe there is a way to offer an olive branch to people who think it does?

      What do you think?

      Does home need to be durable? If so, is the Background a good place to have that interaction? Is there a good way to get there?

      How do we keep the home interaction consistent between phone, tablet, laptop, and desktop?

      Note that "just add another setting to..." is not an acceptable compromise. More customization means more development overhead, makes it more difficult to support users (you might have to do this, or you might have to do that), and takes away from a consistent experience. (If you want to discuss this metatopic, please make another thread.)

      Addendum: ground rules

      You're talking about a bunch of colorful rectangles, remember. Take your time when replying and keep it respectful and on-topic. This is a good place to brainstorm, but make your ideas concrete with mockups rather than talking about them abstractly.

      posted in Design
      U
      UniSuperBox
    • Can OTA-15 be the final release including Oxide?

      Hi everyone,

      It's been about two years since we added QtWebEngine to Ubuntu Touch, beginning the arduous process of replacing Canonical's Oxide rendering engine.

      At the time, all of the webapps and HTML5 apps on the store relied on Oxide's unique quirks. Some expected the behavior from Ubuntu.Web, others explicitly imported Oxide libraries.

      Since then, things have changed. We've become increasingly present on 64-bit ARM devices where Oxide simply isn't available. Many of our users coming to the platform now can't take advantage of these apps.

      Many app developers have released their apps to take advantage of Morph.Web or direct QtWebEngine imports. However, I believe there are still some holdouts on the store... Either by lack of maintainership or by choice. The Ogra webapp container in particular only uses the Oxide rendering engine. Any apps made with it simply don't work on the PinePhone, Volla Phone, Xperia X, Nexus 6P, or many other new ports...

      With this in mind, I propose that we make OTA-15 of Ubuntu Touch the final release which includes the Oxide rendering engine. In other words, OTA-16 should not include Oxide. That gives a roughly three-month period to transition any remaining apps to the new rendering engine (on top of the two years already provided).

      Removing the Oxide rendering engine takes a pretty large, not-updated piece of code out of the image. That means smaller updates for everyone, more space in the rootfs to provide newer features, and a more secure device overall.

      Is this timeline with OTA-16 the first non-Oxide update feasible? What else do we need to consider before its removal that we can prioritize for OTA-14 and OTA-15?

      posted in OS
      U
      UniSuperBox
    • Ubuntu Touch OTA-16 Changelog

      What follows is a log of most of the changes to Ubuntu Touch between OTA-15 and OTA-16 (as of the March 8, 2021 Release Candidate).

      OTA-16 is our second-largest release ever. About 1/3 of the binary packages installed in Ubuntu Touch changed in this release.

      This changelog does not include all changes. In particular, changes to the following components are not included:

      • Applications preinstalled using click packages
      • Device-specific changes made in their Halium build trees

      [Rodney]

      Upgrade 21 Qt source packages from v5.9.5 to v5.12.9
      Backport ~20 of Qt's dependent source packages to Xenial
      Remove the Oxide web rendering engine: ubports/morph-browser#419
      Fix build of U1DB, fixes ubports/u1db-qt#2: ubports/u1db-qt#3
      Add 16.04.5 app framework: ubports/ubuntu-touch-meta#59
      Fix QML warnings caused by Qt 5.12 update: ubports/ubuntu-ui-extras#66
      Fix QML module dependencies for Qt 5.12: ubports/unity-api#27
      Fix content-hub under Qt 5.12: ubports/content-hub#16
      Handle changes to Qt private window state API in qtubuntu, fixes ubports/qtubuntu#3: ubports/qtubuntu#17
      Fix maliit-framework's build against Qt 5.12: ubports/maliit-framework-packaging#4
      Replace transitional dependencies and run online-accounts-api tests on arm64: ubports/online-accounts-api#2
      Update QML module dependencies: ubports/accounts-qml-module#2
      Update libusermetrics dependencies: ubports/libusermetrics#11
      Update qtubuntu-print for private API changes in Qt 5.12: ubports/qtubuntu-print#1
      Clean up system-settings warnings and failed tests after Qt 5.12: ubports/system-settings#275
      Update ubuntu-push-qml dependencies: ubports/ubuntu-push-qml#3
      Update dialer-app dependencies: ubports/dialer-app#148
      Update dependencies and fix build of unity-webapps-qml: ubports/unity-webapps-qml#1
      Fix runtime errors of morph-browser against Qt 5.12: ubports/morph-browser#446
      Fix ubuntu-system-settings-online-accounts import errors and run tests on arm64: ubports/ubuntu-system-settings-online-accounts#4
      Add support for Qt 5.12 and 5.15 to ciborium (why is it like this): ubports/ciborium#47
      Fix messaging-app for Qt 5.12: ubports/messaging-app#261
      Fix qqc2-suru-style for Qt 5.12: ubports/qqc2-suru-style#52
      Update dependencies of mediaplayer-app: ubports/mediaplayer-app#17
      Build Oxide rendering engine against Qt 5.12 (but don't install it by default on Ubuntu Touch): ubports/oxide-packaging#2
      Port Ubuntu UI Toolkit to Qt 5.12: ubports/ubuntu-ui-toolkit#103
      Port Lomiri to Qt 5.12: ubports/unity8#355
      Log the whole filename when a file fails to save: ubports/qtubuntu-camera#16
      Fix Launcher becoming invisible when an app updated its messages bubble while the Drawer was open, fixes ubports/unity8#361: ubports/unity8#362
      Move internal implementations of QQC2-suru-style components into a subdirectory, fixes ubports/qqc2-suru-style#53: ubports/qqc2-suru-style#54
      Fix address-book-app for Qt 5.12: ubports/address-book-app#177
      Fix imports in Fingerprint settings plugin, fixes ubports/system-settings#24: ubports/system-settings#25
      Switch to ubuntu-touch-sounds instead of ubuntu-sounds: ubports/telephony-service#22
      Fix system-settings displaying "nan minutes" for screen timeouts: ubports/system-settings#279
      Import and use Morph.WebContext correctly: ubports/morph-browser#466
      Fix display of QtWidgets applications under Qt 5.12: ubports/qtubuntu#19

      [Marius Gripsgard]

      Fix automatic brightness on Android8+ and Treble devices: ubports/repowerd#14
      Add missing include for std::isnan in morph-browser's domain-settings-model: ubports/morph-browser#447
      Register the Morph.Web QML type: ubports/morph-browser#448
      Do not create runtime for biometryd's dbus stubs: ubports/biometryd#4

      [Ratchanan Srirattanamet]

      On Android 9 and Android 7 devices, make alarms and ringtones play through headphones and speakers even when a microphone is plugged in: ubports/pulseaudio-modules-droid#11 and ubports/pulseaudio-modules-droid#12
      Make unity-system-compositor compatible with newer Mir while maintaining Mir 1.2 support: ubports/unity-system-compositor#19
      Fix trust-store hanging when it failed to display a prompt, fixes ubports/ubuntu-touch#1668: ubports/trust-store#14
      Update GStreamer and bring in gst-droid, allowing an accelerated camera viewfinder on the PinePhone and video recording on 32-bit Android 7 devices.

      ["natur-produkt"]

      Fix switching mobile data SIMs in some cases on some Android 9 devices: ubports/indicator-network#57

      [Chris Clime]

      Update morph-browser user agent to "like Android 9" instead of "like Android 4.4", fixes ubports/morph-browser#374: ubports/morph-browser#386
      Fix page zoom settings sometimes not being applied, fixes ubports/morph-browser#350 and ubports/morph-browser#360: ubports/morph-browser#352
      Re-enable custom user agents and add "Always Deny" checkbox when a website requests location access, fixes ubports/morph-browser#320: ubports/morph-browser#368
      Fix QtQuickControls2 style being set incorrectly in morph-browser, fixes ubports/morph-browser#440: ubports/morph-browser#442

      ["Flohack"]

      Add option to rotate boot screen to upside-down orientations: ubports/unity-system-compositor#18

      [Kugi Eusebio]

      Make deleting a file from the morph-browser downloads list also delete the downloaded file, fixes ubports/morph-browser#330: ubports/morph-browser#412
      Make tabs taller when using the tablet/desktop browser UI, fixes ubports/morph-browser#221: ubports/morph-browser#418
      Fixed morph-browser click name, fixes ubports/morph-browser#335: ubports/morph-browser#423
      Add visual option to reopen most recently closed tab: ubports/morph-browser#416
      Overhaul Downloads UI with "recent downloads" panel, a toolbar icon which shows downloads in progress, and more, fixes ubports/morph-browser#193: ubports/morph-browser#415
      Avoid selecting a tab when trying to swipe on its title, fixes ubports/morph-browser#426: ubports/morph-browser#427
      Stop the browser from rotating itself whenever its window is taller than it is wide, fixes ubports/ubuntu-touch#1344: ubports/morph-browser#430
      Change "Unity8" to "Lomiri" in keyboard shortcut overlay: ubports/unity8#350
      Fix errors shown while using content-hub pickers: ubports/content-hub#17
      Changed type of edge-barrier-sensitivity: ubports/unity8#367
      Make the Keyboard theme page select the currently active theme when loaded, fixes ubports/system-settings#281: ubports/system-settings#282

      [Lionel Duboeuf]

      Allow apps to play audio files from a temporary directory, fixes ubports/media-hub#2: ubports/media-hub#25
      Display a message when the Contacts app fails to load the device's current phone number(s), fixes ubports/address-book-app#142: ubports/address-book-app#147
      Add support for animated images in default Messages app: ubports/messaging-app#258
      Fix incorrect audio recording timer, fixes ubports/mesaging-app#265: ubports/messaging-app#268
      Fix call timer not starting at 0, fixes ubports/dialer-app#149: ubports/dialer-app#150
      Fix message bubbles being invisible under Qt 5.12, fixes ubports/messaging-app#263 and ubports/messaging-app#269: ubports/messaging-app#267
      Fix DatePickers not showing when they are loaded asynchronously, fixes ubports/ubuntu-ui-toolkit#109: ubports/ubuntu-ui-toolkit#110

      [Jami Kettunen]

      Add support for the PM8998 PMIC LED flash controller as used in the Snapdragon 835 and 845 chipset: ubports/indicator-power#40

      ["NotKit"]

      Correctly display the device name when using generic Halium system.img: ubports/system-settings#273

      [Joan "Cibersheep"]

      Fixed inconsistent Catalan keyboard layout, fixes ubports/keyboard-component#125: ubports/keyboard-component#124

      [Mateo Salta]

      Hide the morph-browser scaling error on some devices: ubports/morph-browser#441
      Move "Update Settings" to a headerbar action: ubports/system-settings#276
      Change Ubuntu logo to Info icon for "About" page: ubports/system-settings#280

      [Dalton Durst]

      Rewrite WindowStateStorage to make it asynchronous and work on Qt 5.12: ubports/unity8#356
      Fix Shell being partially destroyed when a new Shell was created, causing test failures: ubports/unity8#365
      Speed up tests by creating fewer objects in the Indicators: ubports/unity8#366
      Fix notification LED for unread messages (wdehoog had an earlier attempt for this but it didn't entirely fix the issue, ubports/unity8#359, fixes ubports/ubuntu-touch#1651: ubports/unity8#363
      Fix vibration from apps with hfd-service: ubports/apparmor-easyprof-ubuntu#21
      Fix creation of MMS messages on Android 7 and 9 devices, fixes ubports/ubuntu-touch#1670, ubports/ubuntu-touch#1677, and HelloVolla/ubuntu-touch-beta-tests#94: ubports/telepathy-mission-control-5#4
      Allow apps with the Networking policy group to use QNetworkInterface, fixes ubports/ubuntu-touch#1680: ubports/apparmor-easyprof-ubuntu#22
      Fix double clicking or double tapping under Qt 5.12: ubports/qtubuntu#20

      [Alfred Neumayer]

      Fix use of QTemporaryFile (and therefore QFile::copy) with Qt 5.12: ubports/apparmor-easyprof-ubuntu#20

      [Caleb Connolly]

      Don't crash hfd-service when trying to add a transient trigger fails: ubports/hfd-service#13

      [Daniel Kutka]

      Fix browser tab previews under Qt 5.12, fixes ubports/morph-browser#457: ubports/morph-browser#467

      posted in OS
      U
      UniSuperBox
    • Ubuntu Touch OTA-18 Changelog

      What follows is a log of most of the changes to Ubuntu Touch between OTA-17 and OTA-18 (as of the July 7, 2021 Release Candidate).

      This changelog does not include all changes. In particular, changes to the following components are not included:

      • Applications preinstalled using click packages
      • Device-specific changes made in their Halium build trees
      • Anything I missed while browsing GitHub and GitLab. PM me if I missed yours!

      ["Flohack"]

      Add exposure modes to qtubuntu-camera: ubports/qtubuntu-camera#12
      Fix missing WiFi indicator on some Android9 devices: ubports/indicator-network#65
      Add a different vendor service for call audio on some Android devices: ubports/audiosystem-passthrough#2

      [Joan "CiberSheep"]

      Change top panel color during a call from "positive" (green) to "activity" (blue) ubports/unity8#324
      Add degree symbol to keyboard, fixes ubports/ubuntu-touch#1628: ubports/keyboard-component#178
      Fix theming in dialer SIM card selection: ubports/dialer-app#162

      [Lionel Duboeuf]

      Add "time sent" to information for SMS/MMS messages, fixes ubports/messaging-app#179: ubports/messaging-app#250 and ubports/history-service#32
      Enable stickers in the SMS/MMS messaging app: ubports/messaging-app#266
      Add method to PhoneUtils so it can return a country code from a locale string: ubports/telephony-service#29
      Don't perform long-running migration in history-service, fixes ubports/history-service#288: ubports/history-service#37
      Prevent migrations from running more than once in history-service: ubports/history-service#39
      Fix v17->v18 migration running more than once: ubports/history-service#38

      [Mateo Salta]

      Remove "New Tab" bar from History page: ubports/morph-browser#345
      Update look of tabs so they aren't floating in space: ubports/morph-browser#394
      Fix the header being weird in ExpandedHistoryView: ubports/morph-browser#488
      Fix building messaging-app with Clickable: ubports/messaging-app#297

      ["Danfro"]

      Add redeye flash mode to qtubuntu-camera: ubports/qtubuntu-camera#13

      [Luca Weiss]

      Only use Hybris in platform-api when required: ubports/platform-api#6
      A volley of fixes to dbus-cpp, network-cpp, and process-cpp

      ["userj"]

      Add a line break in the middle of the volume warning: ubports/indicator-sound#3

      ["Antikruk"]

      Add a Belarusian keyboard layout: ubports/keyboard-component#146

      [Kubi Eusebio]

      Open the on-screen keyboard on a new tab: ubports/morph-browser#417
      When opening a new tab from a link, place the new tab next to the tab that opened it, fixes ubports/morph-browser#326: ubports/morph-browser#439
      Add navigation history to the back/forward buttons: ubports/morph-browser#444
      Fix Control+Alt+T shortcut: ubports/unity8#375
      Replace the side stage handle with one that looks like Drawer and Indicator handle, fix the shadow stealing input from the app: ubports/unity8#374
      Fix building morph-browser with clickable, fixes ubports/morph-browser#484: ubports/morph-browser#485

      ["farkasdvd"]

      Snooze the alarm, rather than dismissing it, after it times out: ubports/indicator-datetime#29
      Start snooze timer from the time the snooze started, not the time the alarm started: ubports/indicator-datetime#30

      [Alberto Mardegan]

      Start and stop the SSH service without using Android properties: ubports/dbus-property-service#1
      Rewrite media-hub in Qt C++ instead of... whatever it was, fixes ubports/media-hub#29, ubports/media-hub#24. ubports/media-hub#28
      Fix location-service build under crossbuilder: ubports/location-service#10
      Fix remote media sometimes not playing, podcast tracks failing to resume in Podbird, fixes ubports/media-hub#31: ubports/media-hub#32
      Simplify moving to next track ubports/media-hub#33: ubports/media-hub#34
      Add tests for resetting a track: ubports/media-hub#36
      Fix strange play order in Podbird, fixes ubports/media-hub#35: ubports/media-hub#38
      Fix random test failures: ubports/media-hub#39

      [Dalton Durst]

      Remove log handler that disables warnings in trust-store: ubports/trust-store#16
      Save 30MB or more RAM whenever unity8 is running (always): ubports/unity8#388
      Fix being able to type too fast for the Drawer, being able to drag the drawer too far open, and 4-finger tap summoning the keyboard in addition to the Drawer, fixes ubports/unity8#389, ubports/unity8#251: ubports/unity8#391
      Fix opening the Drawer when Lomiri is in Shell-only mode: ubports/unity8#393

      [Ratchanan Srirattanamet]

      Update build infrastructure for trust-store: ubports/trust-store#17
      Remove qtubuntu dependency on platform-api: ubports/qtubuntu#21
      Explicitly depend on platform-api now that qtubuntu doesn't: ubports/core/seeds/ubuntu-touch#27
      Handle long power button press if it's the first input after Lomiri starts: ubports/unity8#390
      Fix autobrightness after ubports/core/repowerd!18: ubports/core/repowerd!31
      Add Wayland support to mir-android-platform: ubports/core/mir-android-platform!26
      Fix crashes in nemo-qtmultimedia-plugins when QMultimediaService is null: ubports/core/nemo-qemultimedia-plugins!1
      Build biometryd for both xenial and focal at the same time: ubports/core/biometryd!6
      Import gst-plugins-good security updates: ubports/core/packaging/gst-plugins-good1.0!1

      [Chris Clime]

      Define a storageName by default for morph-browser, so it will keep cookies between sessions in WebEngine 5.15: ubports/morph-browser#486

      ["doniks"]

      Translate the Libertine QML files, too: ubports/libertine#112

      [Adam Schrey]

      Update Libertine icons: ubports/libertine#116

      [Marius Gripsgard]

      Allow building repowerd without hybris support: ubports/core/repowerd!18

      posted in OS
      U
      UniSuperBox
    • Updates on Mir and OTA-8 (and watch out, Edge channel users)

      Hey everyone,

      I wanted to give you an update from the developer team in case you aren't following the development of Ubuntu Touch very closely. To get to it quickly, it seems like we won't be able to deliver an update to Mir 1.0 or higher in Ubuntu Touch OTA-8.

      Edit: Most of the problems listed here have been resolved. See https://github.com/orgs/ubports/projects/10 for more details on what's blocking the merge of unity8+Mir1.1 into the normal cadence.

      Apps failing to display

      There's a bit to unpack for this one. The best technical explanation can be gained from others on the team, but you're going to get me for this one. πŸ˜›

      The big problems

      Apps rarely display

      The most glaring issue is that apps are rarely able to display anything on the screen. They start correctly and can almost always be interacted with, but only a black box is displayed. Resizing windows in desktop mode leads to many fun effects.

      Apps doing weird things in desktop mode

      To paraphrase, it seems like there is a race condition in Mir getting a display surface (a box which the app uses to draw stuff) from Android before it has to pass it to the app.

      This problem is mainly exhibited on devices with Qualcomm chipsets.

      Poor performance

      Some actions are extremely slow. When apps display correctly, they have a very low framerate. Pulling out the dock and the app launcher is painful. There really is no excuse for this, newer versions of Mir are much more efficient than our current 0.24.

      Interestingly, the performance of the indicators is almost perfect. They feel way better to use than they do under Mir 0.24. In fact, the lowered input latency of Mir >0.26 is noticeable when scrolling around the indicators. This shows us that the failures are within Unity8 itself -- Mir is functioning perfectly.

      We should have known

      These challenges aren't entirely unexpected. The Android->Hybris->Mir->QtMir->Unity8->QtUbuntu pipeline can't be expected to be perfectly stable when several parts of that stack change all at once. We were over-optimistic when estimating how long it'd take to solve the problems upgrading Mir and Unity8 at the same time would bring.

      What's next?

      I'll change gears and focus on delivering some more fixes to OTA-8 before wrapping up. Marius will continue working on Mir and other intense low-level issues.

      This cycle has included a lot of behind-the-scenes fixes as we've been fixing up automated tests on many components (especially the Ubuntu UI Toolkit -- Thank you Rodney!), allowing us to bring on new code. I've been merging in some rather old PRs (sorry for the wait, everyone who opened those) and I hope to continue to clear the queue for this release.

      Tomorrow we'll merge the changes from our xenial_-_edge_-_mir branch into xenial_-_edge. This will cause any Qualcomm devices on the edge channel to experience the problems I listed above (and could cause general instability on other devices). It will be difficult to update Qualcomm devices without having developer mode enabled (which I hope you have anyway, you're on the edge channel). If you are using the edge channel and are not tolerant to these issues (I question how you got on edge in the first place πŸ˜› ), please move to rc or stable using the options in System Settings.

      If you're not sure whether you're using the edge channel or not, you probably are not. The current release channel is listed in "System Settings -> Updates -> Update settings, 'Channels'"

      posted in OS
      U
      UniSuperBox
    • RE: I wanna go home

      So, what have we learned this week?

      • Everyone wants a home
      • No one can agree on what home is
      • Some people like the desktop "stuff on your desktop" paradigm, others hate it
      • New Unity8 already provides features we're used to seeing on a home screen, but not somewhere that is a home screen

      Quite a few shades of gray here. I don't think we'll be able to reach consensus for everyone without just getting in and doing something, then taking the feedback from that. It's really hard to describe dynamic functionality in words and sometimes it doesn't make sense until it's put in front of you.

      Personally, I think Kugi said it best early on:

      I guess I could live without "home" until we get a great idea that's really a game changer

      Let's try some things out and see what sticks, starting at the simplest first. The best ideas will naturally float up and get traction behind them. As they develop past their initial stages, we'll see more development toward interfaces which are consistent at every point.

      I must reiterate that (since my job title is "development manager" and I feel the need to protect the time of our paid and volunteer developers) I do not support adding lots more settings or compromising between ideas. I truly believe we can make one really good way to use a mouse, keyboard, and/or touchscreen on any size personal device and the only way we'll do that is by working together. If that is totally not to someone's liking, we are not the only mobile operating system.

      So, to put what is next more concretely:

      • We may experiment with Jan's idea to tap the background (it's only a few lines of code to change what tapping there does) and ask for feedback from small groups.
      • Otherwise, we don't want to make any huge changes to new Unity8 before it is released to Stable the first time. We'll release then iterate.

      Go out and make.

      posted in Design
      U
      UniSuperBox
    • It's Qt 5.12 time.

      It's been a long time coming, but we're finally merging Qt 5.12 into Ubuntu Touch.

      This is a process that will take a few days. During that time, updates to the devel channel of Ubuntu Touch will be pinned to an older rootfs release. Changes to Android compatibility images will be shipped, but changes to packages in the system will not.

      So, you will still see updates available on some devices (like the Nexus 5, Volla Phone...) but not on others (Bq E5, E4.5...). Don't be alarmed!

      This is only a notification, no action is needed on your part. πŸ™‚

      posted in OS
      U
      UniSuperBox
    • RC updates begin shipping again February 12

      Hello everyone,

      I'm pleased to report that the first Release Candidate image in the OTA-12 cycle will ship tomorrow (Wednesday, February 12).

      RC 2020-W07 image will be the same as what users in devel have today. Please see our open issues board to find what to expect when you update: https://github.com/orgs/ubports/projects/15

      For users of the rc channel, this will begin the weekly release cadence anew. You will find a new update waiting for you in System Settings every Wednesday.

      For users of the devel channel, you will see no changes to the daily release cadence.

      This brings us closer to releasing Stable OTA-12.

      As always, we rely on our users of the devel and rc channels to discuss with each other about interesting findings they have, then move those findings into good bug reports. You can learn more about reporting a bug on Ubuntu Touch at Bug reporting on the UBports Documentation.

      Thank you to everyone who has tested, filed, and fixed issues with Ubuntu Touch and the new Unity8 to help us get to this point! We're almost there!

      posted in OS
      U
      UniSuperBox
    • On this (US) Thanksgiving...

      Thank you, everyone. Thank you for being here, for reading this, for helping us create Ubuntu Touch, and especially for helping others when it breaks. I know that sometimes it seems like the requests for help never end or that people go off into the ether after their threads are solved... but I've watched many stick around, turn around, and help others. It's all thanks to you.

      I'd like to open the floor... if you've had anyone that helped you while you were getting started, and you're still here, give them a ping to show them your thanks!

      I'd personally like to thank @Flohack and NotKit (who isn't on the forum, bummer!) for greeting me back in September of 2016 and helping me create the ultimately failed Nexus 5X port. Even if my original goals weren't reached, I've had three years of fun and met so many amazing people thanks to your level-headed approach to newcomers. Also, of course I need to thank @mariogrip for the opportunity to dedicate my time to the project.

      How about you?

      posted in General
      U
      UniSuperBox
    • RE: OTA-13 call for testing

      A critical issue was found in https://github.com/ubports/ubuntu-touch/issues/1556, "Text messages do not wake the phone."

      Fixing this issue, releasing the fix into devel, and testing it for inclusion to rc is our highest priority. But given the high profile nature of the issue, we will likely not feel safe in releasing an RC before Wednesday, and we will definitely not feel safe releasing to Stable until after the RC is released and tested.

      For that reason, Ubuntu Touch OTA-13 is again delayed, this time at least to September 16. We may need to further delay if the issue is not fixed in time.

      posted in OS
      U
      UniSuperBox
    • Ubuntu Touch OTA-17 changelog

      What follows is a log of most of the changes to Ubuntu Touch between OTA-16 and OTA-17 (as of the May 5, 2021 Release Candidate).

      This changelog does not include all changes. In particular, changes to the following components are not included:

      • Applications preinstalled using click packages
      • Device-specific changes made in their Halium build trees

      Lionel Duboeuf

      Fix word prediction not being loaded for swiss-french or english-dvorak layout, fixes ubports/keyboard-component#132 and ubports/keyboard-component#100: ubports/keyboard-component#134
      Clean up the dialer-app's logging and warnings: ubports/dialer-app#146
      Allow overriding the background color of popups: ubports/ubuntu-ui-toolkit#68
      Make uitk gallery documentation point to online documentation: ubports/ubuntu-ui-toolkit#111
      Allow uitk gallery build with Clickable: ubports/ubuntu-ui-toolkit#112

      "NotKit"

      Fix camera zoom, flash, rotation, and focus on many outstanding ports, including the OnePlus One, accidentally on purpose: [ubports/qtubuntu-camera#15]
      Import headers for android API level 29: ubports/android-headers#8
      Change Mirclient ABI to allow a larger MirBufferPackage: ubports/mir#32

      "boriseto"

      Add Macedonian keyboard layout: ubports/keyboard-component#138

      Rodney

      Use kernel configuration, not a hardcoded device list, to select an Anbox image: ubports/anbox#43
      Bring back apparmor confinement checks in morph-browser: ubports/morph-browser#473

      Marius Gripsgard

      Fix build of repowerd with newer versions of gcc: ubports/repowerd#16
      Make repowerd manage Wayland sessions: ubports/repowerd#17
      Implement CLOCK_REALTIME_ALARM support in repowerd: ubports/repowerd#20
      Fix retrieving MMS proxy settings on Android 9 devices: ubports/nuntium#11
      Update Mir to v1.8.1: ubports/mir#33
      Export MIR_SERVER_ENABLE_MIRCLIENT for mir sessions: ubports/ubuntu-touch-session#17
      Enable -Werror and -Wextra in unity-notifications: ubports/unity-notifications#3

      Alfred Neumayer

      Implement directory sync in Jumpercable: ubports/jumpercable#1
      Fix vibration not working correctly on startup on Pixel 3a: ubports/hfd-service#15
      Fix thumbnail generation on Pixel 3a: ubports/mediascanner2#5
      Add NFC apparmor policy: ubports/apparmor-easyprof-ubuntu#23
      Add 16.04.6 framework for OTA-17 app development changes: ubports/ubuntu-touch-meta#60
      Add NFC settings panel: ubports/system-settings#283

      Caleb Connolly

      Add Force Feedback vibration actuators to hfd-service: ubports/hfd-service#14

      Vince

      Fix setting up Libertine containers on OnePlus 3, fixes ubports/ubuntu-touch#1305: ubports/libertine#104

      Bart Ribbers

      Fix hardcoded config file location in deviceinfo: ubports/deviceinfo#11
      Fix hardcoded config file location in hfd-service, fixes ubports/hfd-service#7: ubports/hfd-service#16
      Fix spelling mistakes in DBus error messages: ubports/hfd-service#17

      Dalton Durst

      Add preinstalled clicks to amd64 images: ubports/livecd-rootfs#13
      Fix init occasionally stopping in an inconvenient spot on non-Android devices: ubports/ubuntu-touch-session#16
      Work around trust-store and online-accounts breaking on Nexus 4 and Nexus 7

      Kugi Eusebio

      Fix exiting the keyboard's selection mode with double-taps, fixes ubports/keyboard-component#159: ubports/keyboard-component#164

      Ratchanan Srirattanamet

      Import security updates up to 2.4-0ubuntu6.8: ubports/wpa#2
      Fix thumbnailer build with Qt 5.11 and up: ubports/thumbnailer#5
      Remove libunity-api-dev from system-settings build-depends: ubports/system-settings#293

      Joan "Cibersheep"

      Add NFC icon: ubports/ubuntu-themes#12
      Fiddle with the padding on Dividers: ubports/ubuntu-ui-toolkit#80

      "Flohack"

      Fix loud beeping from loudspeaker when hanging up a phone call: ubports/telephony-service#28
      Fix transitioning between ubp-5.1 and halium-7.1 ports on the Nexus 5 and OnePlus One: ubports/android_bootable_recovery#23, ubports/android_bootable_recovery#21, ubports/android_bootable_recovery#22, ubports/android_bootable_recovery#19 and ubports/android_bootable_recovery#20

      Rahammetoela Toekiman

      Clean up trailing spaces and use the icon theme instead of manual svg loading: ubports/keyboard-component#169

      Matthias Dahlmanns

      Avoid binding loop error in OptionSelectorDelegate: ubports/ubuntu-ui-toolkit#113

      posted in OS
      U
      UniSuperBox
    • RE: Liberty or conformism, make your choice !

      Pardon my brevity, but I've been reading nothing but arguments about this for a week.

      I have not seen one conversation about this topic which has remained in useful, measured debate. It has always devolved into name calling and subterfuge. I've watched friends leave and people get unreasonably upset over a conversation.

      I don't think that we're able to debate this topic here. Please find another forum to do so.

      posted in Off topic
      U
      UniSuperBox
    • RE: Edge to Dev Channel

      I really had no plan for where best to express this information, so here's as good a place as any.

      TL;DR: It's not ready yet.

      First, some definitions to make sure we're on the same page:

      • Roughly speaking, anything that is merged into a xenial branch on a Debian-style package in the https://github.com/ubports organization gets built and released to devel. This is what we mean when we say "edge merge" or anything similar.
      • We expect ourselves to ship a release of Ubuntu Touch every 6-8 weeks, including 2 weeks for testing. This gives us 4-6 weeks of "open merge" time in a cycle where low to critical priority changes may be merged. During the 2-week testing period that changes to merging critical priority changes only.
      • Releases of Ubuntu Touch move sequentially from devel to rc to stable. That is, Stable OTA-10 is the exact same set of bits as rc 2019-W33/2, which is the exact same set of bits as devel 2019-08-16.

      This is the only way we can release software. Changes we merge into a package go into devel which must go to rc which must go to stable. We cannot easily or cleanly substitute in a certain old version of a package, for example. If we merge broken changes, our options are to revert those changes or fix them so they are not broken. That was the cause of OTA-10's delay: we merged some improperly tested changes and believed we could fix them faster than we could revert them. This proved to be false.

      To make it crystal clear, if something is broken in devel, it will be broken in the upcoming stable.

      I'm fairly sure that it will take more than a week to merge all of the changes from xenial_-_edge into xenial, get the packages built correctly, and get the release pipelines happy again. This takes anywhere from 1/4 to 1/3 of our expected cycle time, reducing the number of bugs we can expect to fix before we can release again.

      I firmly believe "if you add a little to a little, you have a big pile" (attributed to Hesiod). Check out https://github.com/orgs/ubports/projects/10. It looks like a small pile of things. However, we know that, as very early adopters of the edge software, we are imperfect testers. We aren't going to catch every regression from devel to edge. That's why we release software to devel. Lots of people testing means more bugs filed and higher quality software. In this case, that would add a little more to our little pile. Suddenly it doesn't look like such a little pile of bugs any more.

      We don't want to end up with that rush or crunch. It means lower-quality software for you. Our goal is to have the number of known bugs in edge to a minimal point at the start of a cycle so we can take our 1-2 weeks to merge from xenial_-_edge to xenial. Then we can fix the myriad bugs that people will find, because they're better testers than us.

      If you want to help us, try out the edge channel and report anything strange you find. This might further delay the merge, but it will ensure a smooth transition and a faster release when the merge does happen.

      posted in General
      U
      UniSuperBox
    • RE: [Morph Browser] Explanation about Canonical in URL

      Hi @prog-amateur, thanks for bringing this to our attention. This was added to the browser back in 2015 by "Add t=canonical to DuckDuckGo search" and was never removed after we took over Ubuntu Touch. We do not currently have a partnership with DuckDuckGo to my knowledge, so I accepted @Aury88's PR to remove it.

      As you found, this allows DDG to assign advertisement revenue and give metrics to partners affiliated with them, to spread DDG. I don't know what metrics are shared, you would need to ask them as we don't have such a partnership.

      Your phone connects to the UBports Push Service to receive push notifications when a compatible app is installed. That should be the extent of any connections made from your device to our servers at idle, but if you find anything else please let us know.

      posted in OS
      U
      UniSuperBox
    • RE: Pinephone tutorial
      1. Download the rootfs image from https://ci.ubports.com/job/rootfs/job/rootfs-pinephone/
      2. Extract and write the image to an SD card
      3. Plug SD card into phone
      4. Boot phone

      That should do it. πŸ™‚

      posted in Support
      U
      UniSuperBox
    • RE: OTA-13 call for testing

      Apologies for the lack of detail in my previous message, but the reason for the delay was an embargoed fix for https://ubuntu.com/security/notices/USN-4519-1.

      I have now pushed RC image 2020-W38.

      Due to the contents of the PulseAudio change, we believe we can release safely on Monday (September 21).

      However, a change has been merged to ubuntu-push during our freeze period, causing a rebuild. Since the last time ubuntu-push was rebuilt was a year ago, we are cautious around this component. It is possible that a change in one of its dependencies has caused a regression in its behavior on-device. During this period, please be extra-conscious of push notification receipt from apps like TELEports and FluffyChat.

      I've run a variety of tests on devices using the pushclient example app in the store, so I'm fairly certain everything is fine. But please, watch this piece in particular.

      posted in OS
      U
      UniSuperBox
    • [Resolved] Ubuntu Touch updates are currently interrupted

      Edit: The situation is now resolved.

      Hello everyone,

      I regret to inform you that we made an oversight and allowed the Image Signing key for https://system-image.ubports.com expire. We are working to remedy the issue, but in the mean time downloading updates to Ubuntu Touch is not possible. You will receive a "FileNotFoundError" referencing a keyring file upon trying to update.

      Only the on-device image updater is affected. Installing Ubuntu Touch using the UBports Installer is still possible. You may still update apps and use your Ubuntu Touch device normally. Since there has not been a recent stable update, most users are not highly impacted by this issue.

      To ensure that this never happens again, we are implementing automatic checking of the image signing keys: https://github.com/ubports/build-scripts/pull/10

      This post will be updated as new information becomes available. You may also track this issue at https://github.com/ubports/ubuntu-touch/issues/1120

      posted in News
      U
      UniSuperBox