@fischer.poco said: @turtle_racer Thanks for the help and comment. Now, if I understand correctly, I should reinstall OS Oxygene... and then reinstall the entire UT? You're welcome @fischer.poco ! No worries man. We all had to learn this initially (myself included), so you are doing great. You are past the hardest part in my opinion which is having a phone with unlocked bootloader! So, congrats on that! OnePlus has really clamped down and seems to not give out unlock tokens. Yes, you are understanding correctly. Re-install correct OxygenOS version and reinstall entire Ubuntu Touch. I think you should be good from there, but if not, just post in the forum and there are many kind people here to try to help out, such as @rocket2nfinity and @rondarius and others. Good luck!

Thanks, I am going to installiert telegram!

@PhAndersson said: Could it somehow be related to the fact that the clock is now reasonably synched? I don't think so, for the following reasons: I did give you the hint about recreating the connection, and I don't have a mediatek device date problems for ssl come from the securing through a certificate infrastructure, that don't make much sense for Bluetooth, whose hacking radius is 10 meters vs 40000 km for standard internet networking updating certificates and certificates lists would be unfeasible for many Bluetooth devices that don't even have an Internet link This said, if you want to try it out, it's easy: just re-enable the qualcomm time service and check again.

@DerekZoZo said: but in a sense of being told that "we don't want you here" 🤯 I am autistic and have a tendency to read to deep into what someone writes online All what I said is that volla is the device manufacturer and porter, and that best support (port related) for those devices is volla. Since you need support, i redirect you to the place I think you'll get the best for your device : volla. I'm not a dev, just here because I love Ubuntu Touch since more than 10 years, and try to help UBPorts and community with my limited knowledge and assets.

Update 30 June 2026: we've decided to postpone the release of Ubuntu Touch 24.04-2.0 by 1 more week due to a number of important fixes missing their deadline. The new release date is set to be 20 July 2026. So, instead of a Release Candidate image, today we've published 24.04-2.0 Beta 2 which contains a number of improvements and fixes since the last Beta. We hope to be able to have a Release Candidate image next week. Notable changes Following devices can now receive Ubuntu Touch 24.04-2.0 Beta 2: Asus Zenfone Max Pro M1 JingPad A1 OnePlus Nord N10 5G OnePlus Nord N100 Xiaomi Redmi 9 and 9 Prime Xiaomi Redmi Note 9 Additional devices receive notch position configurations, including all Volla devices and a few Xiaomi devices. Fixed the problem where the top panel gets confused about whether it has to avoid notches or not when the screen is rotated using the floating rotate button. Improved support for legacy (X11-based) applications significantly by backporting changes from Mir 2. Widevine installer is now fully functional. If you're dependent on DRM-protected contents, Morph Browser could be used to watch such contents. Morph Browser can now get access to location. Screenshot editor no longer obscures notifications. Notable known issues While Widevine could be installed, some sites (e.g. Netflix) might impose further restrictions on what browser it supports. Video recording and media playback in most applications (except browsers) might be broken due to some cache not clearing up. As a workaround, the following command could be run to remove such cache: rm -v ~/.cache/gstreamer-1.0/registry.* Followed by a reboot. A fix is being developed. (lomiri-camera-app#221). Morph Browser may show black screen after it's switched to background and back. Scrolling will allow webpage to display again. (qt6-webengine#2) Some keyboard layouts are displayed incorrectly by overflowing to the left and right edges of the screen. (lomiri-keyboard#214) Morph Browser may show black screen after it's switched to background and back. Scrolling will allow webpage to display again. (qt6-webengine#2) Hardware video decoding in the updated Morph Browser is not working. Video playback still work, but will be done in software, increasing power usage (qt6-webengine#1). Morph Browser's new tab page is not fully functional. In particular, it doesn't show bookmarked sites correctly (morph-browser#624) Notch avoidance does not work yet on landscape mode. We're still working on issue with mouse position on built-in screen affecting the trackpad on Volla Tablet's keyboard cover. As such, Volla Tablet will not receive 24.04-2.0 Beta at this time.

It did NOT break my GPS in fact I'll give you a rundown of what I did to get to my original conclusion. Installed Navius having used my GPS with other apps (like PureMaps) before. Saw Navius not getting a GPS signal even though I was outside for a while (15 to 20 minutes). Saw PureMaps not getting a GPS signal even though I was outside for almost 40 minutes. Then I panicked (since I really need GPS on my daily) and searched for information on how to fix the issue, then I found out about the test_gps command and saw it showed the above message. I tried changing locations, rebooting, taking the battery out, changing update channels and I was seriously considering having to re-flash my phone but I saw a post about someone saying that the test_gps command is unreliable and can miss-report GPS functionality. In the end I moved to a more populated area with better satellite signal (apparently) and I got my GPS working again after a bit of waiting, even though the above command said otherwise (and it still gives me the same output). I feel like I ow the developer an apology . I wish I could edit my original reply. I'll be giving the app a good shot now and share my feedback! But really what is wrong with the test_gps command? Any idea why it works for some people and not in this particular case?

@777X yea i am using localsend now and then, its a nice clean application if it works xD

@KoJans said: That worked in a few minutes outside. Glad to hear it!

Thanks for the hint. Yes, both work correctly. The physical volume buttons change the playback volume. The system volume slider (volume indicator) also changes the playback volume. Only QMediaPlayer::setVolume() has no audible effect, although the property itself changes correctly. So it looks like the backend ignores the player's volume while still using the system media volume.

@gpatel-fr Merci beaucoup pour ces informations je vais orienter ma recherche du côté de Volla

@nbdynl Thank you again for your replies. You are right, the app actually works great.

New Release: Download here: https://git.brennoflavio.com.br/brennoflavio/greenline/releases Github mirror: https://github.com/brennoflavio/greenline/releases You now can translate Greenline for your language, go to UBports translation project and feel free to contribute https://hosted.weblate.org/projects/ubports/greenline/ Many thanks for UBports admins to make this happen. Changelog: Animated stickers now renders correctly Fixed a bug where the name and photo in the notification was not shown correctly Now you can start new chats. Either by inputting a phone number or importing a contact into the app Translation support Progress towards beta: https://git.brennoflavio.com.br/brennoflavio/greenline/milestone/1

@Moem Looks promising, It could be just what I need. Thank you!

@UBportsNews Is 24.04-2 supposed to be ready for click packages based on Qt 6 out of the box, i.e. without any Qt 6 related install_lib entries in clickable.yaml? If so, the clickable docker images should probably be adapted to contain a Qt 6 dev environment (but this might have to be discussed with the clickable maintainers). And a question regarding the lomiri-ui-toolkit snap: Any plans/timeline for lomiri-ui-toolkit-core26? DeltaTouch would really profit from Qt >= 6.6, but snap based on core24 only offers 6.4.

Yes! I confirm that disabling the Timekeeper service resolves the issue. The clock on the phone was still correct this morning after turning it on in "offline" mode. Which also confirms that RTC is indeed supported natively on the Quintus.

@mariogrip FP5 build 137 Now it's the camera app that don't work anymore. Like with the store, it's a missing library problem: libexiv2.so.27 called from libcamera-qml.so 26.04 provides libexiv2-28, but contrary to libicu74 there is a compatibility layer in 26.04: libexiv2-27-compat, but it's not installed. I don't see why this breakage appears only now. Was this libexiv2-27-compat library included previously in the rootfs and not anymore ? I am not keen on the idea of a regression test by installing a previous version of Ubuntu Touch 26.04 to check on that. Anyway, getting the library from the compat package and doing an overlay to add it to the system solves this particular problem.

@Persinto since you want to use it as android phone, then any

@sambk Have you had any luck?

@pparent en effet, même problèmes avec les autres signets. Je vais tâcher de signaler ça. Visiblement il y a un pb d affichage avec morph aussi. Cela est sans doute lié. (Merezhyvo fonctionne)

In frenchie: https://www.clubic.com/actualite-619081-iptv-les-fai-europeens-en-ont-marre-du-blocage-et-le-font-savoir.html