@messayisto The bugreport for the Volla22 is linked in my above post.

@charly @messayisto Can you please add a bugreport for your devices for the problem with missing dial tone? I've already done a bugreport for the Volla22, but for your devices there are none. Hopefully this will prioritize this bug, as it's present in every(?) Volla device.

@pparent Sure, I can complement your bug report. But do you have the same experience?

• Press power button
• Backlight powers up
• No image is coming up

I've upgraded my Volla (yggdrasil) yesterday from 20.04 OTA-11 to 24.04-1.1 stable. Since then I already had two times where the phone freezes/crashes. When I press the power button to wake up the phone it seems that only the backlight is on but there is no picture. If pressing power button again, the backlight is off again. I can repeat this procedure several times without luck. Several minutes later the phone again wakes up like expected while pressing the power button.
After having a working phone again I checked the RAM&SWAP. Both of them were not totally used and had some reserve. Then today I tried to flood RAM&SWAP by starting many different apps and after a while my SWAP was filled 100% while the RAM does still have some free space. The phone is still usable and is not freezing/crashing...

Have you tried to lower the swappiness of the system? Maybe this could help to slow down the use of the swap-partition. On my phones (and Laptops) i set the swappiness to 10:

sudo sysctl vm.swappiness=10

If that works for you, you can make this permanent via a config-file

@domubpkm I can not confirm this. On mine the player is working like expected. It shows my music and it also plays the selected songs.

Today I got the the update from 1.0 to 1.1 and did it via Updates in the Settings-App. The update installed fine and after a reboot everything works like expected.

@gpatel-fr Yes, that's one option plus "Sound"->"other vibrations" (I'm using german localization , don't know exactly what it's called under with english localization)

@gpatel-fr Thanks for the hint, but I'm always using my phones without haptic feedback or any tones.

Thanks for your initiative for making UT better and more reliable.
Here are my ideas, although they are similar to what others had already mentioned:

Priority 1:

• Sometimes the phone is stucking, almost freezing after using it a longer time without rebooting or using more apps than just 3-4. Then Lomiri seems to crash and just restarts.
• An annoying bug that we have since the beginning of UT back in 2015 is still present: When you've opened more than 3 apps and then want to restart or poweroff your device Lomiri crashes and restarts. Then you have to select restart/poweroff again.

Priority 2:
Like others already said:

• VoLTE is not reliable yet (but it's seems to be the "basic phone functionality" in more and more countries)
• WiFi is always trying o connect to last used network instead of the one which has the best signal
• Bluetooth is almost unusable (no file transfer possible, no hfp in any of my last 4 cars)
• Notification-area is too fragmented. I think it's better to have less indicators or an option to reach the most used on the same "page". Also it's often hard when swiping down from the notification-area to keep in line with the selected indicator and not to swipe to much to left/right and select the wrong one.
• I think RCS will be a next big point for UT to keep in line with Android/iOS

Priority 3:

• The browser is of course outdated and it's more for basic browsing. It's even a bit laggy and slow compared to Android, but that's not as important than the outdated engine.
• The keyboard is sometimes hard to use and I'm writing sentences full of mistakes because of missing blanks and so on. But I don't know why it's happening, if the keys are to narrow or if the input is to slow?

Priority 4:

• The "back" buttons in for example "dekko", uRSSes",... are hard to tap on or sometimes you have tapped on it and you can see the button-press but you have to tap on it again because it was to short or something else.
• Overall performance, it could be "smoother" when switching between apps and so on.
• The start-time of apps is much longer than under android, I don't know why they need so long to start. Even a simple app like calculator or clock needs several seconds to start...
• Support for rounded corners and notches is nowadays a must. When a new user installs UT on his phone and even the clock is not fully visible and there's also no option in the system to set it correctly he will instantly frustrated.

Priority 5:
Nice to Have - I think with the above points there's no time for "nice to have"

@gandalf There will be a 20.04 OTA-11 Release, see here.

@Charly Here it's the same with a Volla22 and congstar (T-Mobile) VoLTE in Germany. When you call someone there is no ringtone until the called person accepts the call. When you deactivate VoLTE everything is as it should be.

@ma There is already a fix for that, coming with the next release.

I have the problem, that I cannot change the volume when I'm in a call. The Onscreen-Display is shown when pressing volume up/down but the volume stays the same. This happens on a normal call and also with loudspeaker on.
Volume control in other applications, for example with music-app, works like expected.
Is there someone with the same issue?

PS: This happens to me on Volla22 with 24.04-1.0 stable

@Charly I'm running Waydroid via Waydroid Helper from Openstore on a Volla22 with UT24.04-1.0 without any problems.

@vverve It's fixed in 24.04-2.x and also backported to 24.04-1.x. So when the there first update of 24.04-1.0 to 24.04-1.1 you will get this fix. Or you switch to 24.04-1.x daily to get it directly.

@domubpkm I think there is already a bugreport for this, because the counter within the icon is also not resetted e.g. emails from Dekko.

@Charly I've not tested it on my 20.04 device, there I'm still on version 0.4.1, because with 0.5.0 Dekko becomes unreliable and that's not welcome on my daily device.

Version 0.5.2 is working fine under 24.04-1.0 for me.