New version is out Introducing protocol v2 - now client apps do not need to use the microphone, audio recording is performed on a server. There are some flaws for this decision, though. CPU load has been reduced in this release This release is also backwards compatible with protocol v1, where client sends recorded data to server, just in case someone wants to send audio data from other sources. Also, my apologies, I forgot to link Client library for v2 protocol Client library for v1 protocol (requires Microphone permission)

@pparent Amazing improvements, thank you very much!

I've made a new pull request: https://github.com/alefnode/ubports-apps/pull/59 Anyone who would like to join the testing is welcome!

@pparent Waydroid and libertine aren't app distribution channels and snaps are just terrible (and centralized with a proprietary backend). Maybe if there was proper Flatpak support in UT, but that still wouldn't give us click-packages.

Thank you guys! I got it figured out. I am new to this and did not dive deep enough into the documentation. I am now done with most, if not all, of the features for my app. I am now just filling it with content. This was helpful for anyone that may read this down the line and is having similar confusion: https://ubports.gitlab.io/docs/api-docs/index.html?p=lomiriuserinterfacetoolkit%2Flomiri-theming-styles.html Sorry for not getting back sooner. Been so caught up with life and working on the app I almost forgot about actually posting to the forums. Look forward to becoming more active around these parts! Have a wonderful rest of your day!

New version updated. Small improvements. Working on Noble: [image: 1761729427818-ac6e1abe-3e20-43ef-8184-7fc862311597-imatge.png] But if you encounter a bug (links not showing, etc), check the logs and send them to me here or: https://gitlab.com/cibersheep/where/-/issues Total downloads: 198. Received donations: 0. Published ~1 year ago.

@bunt7 I see they have a desktop app that seems more or less responsive, maybe it could be possible to run it directly in Ubuntu Touch with Xmir. That's a shame they don't have a snap you could install it directly and try it. Upcoming Mir2.0 with wayland should also improve the feasibility of using desktop apps, in Ubuntu Touch.

@wilson101 OK sure do as you prefer! The last thing I can say is that normally you must have the compiled module in your application in qml-plugins/Pparent/Notifications/libNotificationsPlugin.so and qml-plugins/Pparent/Notifications/qmldir Then you can include the qml module dir in c++ with QQmlApplicationEngine engine; engine.addImportPath("qml-plugins"); That's all I can say! I wish you good luck!

@haagch said in uWolf (LibreWolf): My hope for real wayland support is that it improves not rendering stuff when idle. Currently when I run uWolf and power off the screen (even when I focus another app), lomiri permanently uses 30-40% cpu and pulseaudio 15%. 00b16def-826f-477d-8885-69a1d82969f3-image.png This makes the phone a nice pocket warmer, but also sucks the battery pretty fast. Or currently, might there be a way to tell firefox to drop its rendering while the screen is off or another app is focused, like maybe "minimizing" it in xwayland? This is an Xmir problem , same result with signal desktop https://forums.ubports.com/topic/11538/xmir-lomiri-high-cpu-usage-battery-drain.

I've had so many fun hours due to PodCat already! Thank you so much for doing this!

@aarontheissueguy You should definitely see this post, I really think signal-desktop is the way to go: https://forums.ubports.com/topic/11532/signal-ut-signal-desktop-for-ubuntu-touch

@klh Yeah, it still has some ways to go, but having it included in UT as a standard webview option for app developers would be awesome.

https://open-store.io/app/launchermodular.lut11 [image: 1760839116141-launchermodular.png]

@pparent Your app is very good and the improvement was made by volla 22 itself: I am now on dev 486 and scrolling on volla has improved considerably.

@Caedem Thank you very much. I added most of this results to the app. Unfortunately there were inconsistencies in the previous version with “--num-threads = 2”. With the new version (1.2.1), the tests were slightly changed and should be more consistent now.

[image: 1760703631860-screenshot20251017_140325935.png]