@arubislander For @Salah EVERY bug get's fixed with the release of 24.04

@arubislander I'm pretty sure there is a bugreport anywhere. As I said, the bug is in Focal, was in Xenial and I think also in Vivid/Trusty.

Edit: Here is one bugreport for this.

And that's an old bug: Shutdown the OS with more than three opened apps crashes Lomiri.

@Vlad-Nirky That's the same for me. When you wan't to change the keyboard-layout in system-settings you are not able to do so. But when you try it through the keyboard-indicator you can select your layout. After that system-settings etc. is not available anymore (crashes directly after starting the app).

According to the question @domubpkm : Will the milestones be updated to the actual release schedule? These dates and milestones are outdated but in earlier days it was a nice place to look at which OTA will land at aprox. what time.

@Salah Then it seems for me that it's not related to the cache.

@Salah Nice to hear that your camera is working again. But I don't think, that rebooting the device 4 times helped to reactivate the vibrations. Have the vibrations worked before deleting the cache? Have the settings (there are several) in the settings-app related to vibrations been enabled?

@Salah I don't understand what you mean with hardcoded? Open the terminal app and enter the mentioned command.

@Salah You can try to delete the cache (~/.cache) and check if the camera is working again. For testing it's ok to just rename/move the cache-folder (mv ~/.cache ~/.cache_old). After that do a reboot and check.

@arubislander The merge was done some hours before the actual build, so I thought, it's already included. Let's see what the next days will bring

@uxes OSK still seems not to work (e.g. morph and messages).
@mariogrip Is it intended to install updates only when connected to the power supply? Before Noble it was always possible to install OTA's without beeing connected to AC. Maybe there can be a hint that says it's safer being connected to AC, but let's you install the update even without being connected.

@Lakotaubp Here's the bugreport. The missing OSK and the lack of adb is keeping me away from playing around with the current state.

@domubpkm What do you mean with system parameters? I've done a fresh install via UBports installer but there's only one "channel" for 24.04 AKA "utnext", as @peat_psuwit told in another thread (but system-settings says "16.04 daily", funny ).
When your Volla22 is your only phone, then stay on 20.04 until noble is ready, because for now it's not nearly ready for daily use.

@mariogrip I think in this stage of develpment of 24.04 it's very interesting to know, what's going on from week to week, especially when it's evolving so fast, like you said.
I've installed it on a Rephone/Volla22 since a few weeks and I've observed, that the OSK is not coming up in some apps (e.g. Morph, messaging-app).
But for now it's running very well

@domubpkm That's the site I was looking at. Under "android9plus" there are all the devices listed. And for almost all of them the last build is from 28.11.2024. But before there was a new build almost everyday.
I'm on devel with my volla and make updates normally around every two weeks or when there are some interesting merges. But for now, the last build is almost a week behind.

Hi,

is there something wrong with the build of the system-images? The last build (20.04 and utnext) is from 28.11.2024. As there are changes going on every day shouldn't newer builds be available?

On the nationwide test in September in Germany my Volla did the job well. I've received the notification and the whole message was shown in the message-app. AFAIR there was a vibration and also a tone triggered.
So, well done @lduboeuf

That's no device specific issue for the Volla22, it's a general issue of WaydroidHelper. Here's the bugreport. Long story short: You have to manually edit the .desktop-files and set the NoDisplay-Value to the correct section [Desktop Entry].

@_Joao_ To create the file you have to open the terminal app and enter:

nano /home/phablet/.local/share/applications/waydroid-stop.desktop

Then you have created the file and it's opened for editing. Then you have to enter the content ([Desktop Entry]...) and save it.

@arubislander For me it's the same authentication failure like @danfro The GUI which comes up in your example isn't there for me. You have to enter the password in the same terminal-window where you have entered the command. (Vollaphone, UT 20.04 devel)