@CiberSheep @TheBird @zubozrout Can you please mention on which device these freezes happen to you? I've opened a bugreport but it seems to work on a Fairphone 4 (qualcom device...).
For me these freezes are happening on Vollaphone and Vollaphone22 running Focal and Noble.

@CiberSheep I think that's also the wrong place, because it must be a problem in the location-daemon/gps-daemon.
I've tested it again with todays build of noble and it's the same behavior like under focal: unav, puremaps and even morph are freezing once you have searched your position and want to do something with it (e.g. calculate a route from the actual position). Maybe @peat_psuwit does have an idea or can even take a look at it?

@ezst036 You have to unlock the phone first and then you can directly access the files on your phone via the filemanager on your computer.

The last days I've used the navigation a lot for a motorcycle tour and it was very annoying when the navigation freezes.
I've played around with noble on my spare phone and it seems, that this bug is present there as well
So hopefully we'll get this fixed in near future, to have a reliable working navigation again (as we had in 16.04).
Is there anything we can provide to the devs @costales @rinigus or help in any other way?

AFAIK it will move to noble, but it won't get VoLTE (like the Vollaphone). First it's nice to know that these devices are kept alive with the move to noble, but on the other hand it's a pity that they won't get VoLTE (even if they are capable of that under VollaOS). So they will be up to date from the software-side, but can't do a simple phone call or sending a message/SMS because of the 2G shutdown

@Vlad-Nirky I'm using the calendar of my E-Mail-Provider (posteo) and it's working like expected with caldav.

@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