@Perrete You're welcome! There's another app that may offer what you are looking for, and will probably become available soon: https://forums.ubports.com/topic/12162/alpha-greenline-a-qml-whatsapp-client-for-ubuntu-touch

@rocket2nfinity said: Best thing to do is reflash the global ROM using MSMdownloadTool and EDL mode. Then Re-install UT. Hi, Unfortunately, I don't have Windows; is there something similar for Linux?

@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.

@uxes which fastboot archive, the latest or the one it came with?

I'm having a problem with sending/receiving files and my Volla22. I opened the Gallery, selected a picture and tapped on sharing via Bluetooth-Plugin. In the next window I selected my Laptop and then the transmission dialog comes up. On my Laptop there comes up a notification that my Volla22 is now connected and 1-2 seconds later a notification that it's disconnected. At the same time the Bluetooth-Plugin on my phone says that the transmission has failed. In the output of systemctl --user status obex I found for this time Unable to find service record Sending/receiving between my Laptop and other devices is working like expected, only the Volla with BT-Plugin and 24.04.-1.x stable does not. Any idea?

@acompleteidiot Trying to do the same, I am on windows and the Miflash tool doesn't work very well. I tried it yesterday with a a12 rom But I bricked it and reinstalled UT. I have to try again today. A few tips would help

@sambk Have you had any luck?

Those still requiring a token after converting to the global ROM, can you check if the boot loader image flashed? Maybe try flashing it manually. Ruben says it should be called LK.IMG Ruben thinks it might not have flashed, and reflashing it might unlock it without token.

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

as noted elsewhere for 24.04-2, unstable now can provide the OSK to XWayland apps such as Chromium-UT, Min, UWolf.

@Ida_ That's great news!!

I just went through 'journal' events (phone is now on 24.04-2.0 beta/RC) and found the following errors/warnings related to bluetooth: Jun 23 23:29:47 ubuntu-phablet bluebinder_post.sh[2815]: Failed to get bluetooth address! Jun 23 23:29:47 ubuntu-phablet bluetoothd[2861]: src/adapter.c:reset_adv_monitors_complete() Failed to reset Adv Monitors: Unknown Command (0x01) [...] Jun 23 23:29:50 ubuntu-phablet systemd[2767]: bluez-mpris-proxy.service - BlueZ MPRIS proxy was skipped because of an unmet condition check (ConditionPathExists=!/usr/lib/systemd/user/mpris-proxy.service). It's unclear to me whether any of those can explain the BT connection issue with the laptop, but here they are.

@DJac said: I update my sony Xperia X with ubuntu touch 24.04-2. But I have a problem with the "bookmarks app". They no longer works. What I see : a blue loading bar ,then a black screen (or white if i m not in dark mod). I found it with blablacar, but after some tests, it seems that include all " bookmarks app" I have also a display problem with morph web browser : nothing is displayed online, but parameters are usable. Others browsers works normaly (merezhyvo & ufirefox) Do anyone else have the problem with the "Boorkmark" apps problem? ( With apps based on webapp-container ). If confirmed it seems to me an important problem. What about apps created manually with Webber?

I have a small nitpick feedback Using the send button to send a message doesn't really feel good. The message just kinda goes and i find myself pressing the send button often because I have the idea that it either doesnt send immediately or sends with a delay. Also no feedback when something is being sent. other than that, it works great!

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.