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

Like @messayisto already said: Thank you all for your hard work to implement VoLTE into UT. And so I have a few questions concerning VoLTE:

• Can you please clarify which devices got already working VoLTE?
• Which devices will get VoLTE? What needs to be done?

In another thread there was already the information that for example Vollaphone (1st Gen) will not get it but Vollaphone22 (Halium12) and Vollaphone X23 will get it. So it seems to me, that a minimum Halium-Version is needed.

@Salah There is the "Active Screen" App which does that. But I agree, it would be nice, if there would be an option in the indicators.

@domubpkm Thanks, even if this was not the answer I wanted to hear
But for me it's not such a big deal like for other users, cause I'm located in Germany where 2G will be for a long time.

@mariogrip Thanks for the good news! I have a few questions about that:

• Is there something else to setup (APN?)
• Is VoLTE working on SIM2 (cellular data only works on SIM1)
• How about mediatek devices? If I understand correctly on the last Q&A only Volla X23 is supported?

Thanks for your reply.

Here's the bugreport

@dosolly On my Volla it isn't activated after cold boot and I can't activate it through system-settings. So I've created a systemd-timer and a corresponding systemd-service that enables CB via ofona-scripts.

Timer:

[Unit]
Description=Aktivieren von Cell-Broadcast

[Timer]
OnBootSec=2min
Unit=enable-cbs.service

[Install]
WantedBy=multi-user.target

Service:

[Unit]
Description=Aktivieren von Cell-Broadcast

[Service]
Type=simple
ExecStart=/usr/share/ofono/scripts/enable-cbs

[Install]
WantedBy=multi-user.target

After that you have to enable timer and service and CBS is enabled 2 minutes after a cold boot.
The CB-test yesterday showed me, that it's working (before, there was no way to check it )

@dosolly Have you checked if CB is activated in the system-settings? For my Volla/GS290 it has worked yesterday, but I had to do some tricks to get it activated.

According to the question of @sap : What will happen to focal after the switch to noble? AFAIR there is LTS from Canonical-side (it wasn't there for xenial for our architecture), so will there be security-updates parallel to noble? I remember some Q&As earlier you said, every device that's capable of focal is also ready for noble, so that there's no need for focal-updates.

You can install UT Tweak Tool from the Openstore and activate SSH within the app. After connecting your phone and the Ubuntu-PC to the same network you enter the phone via SSH from your PC.

@domubpkm That's right. The old uadblock (unde xenial) had this selection of blocklists. After reading a bit of source code of uAdblockNG I think it wouldn't be very difficult to modify this app to also have this selection like in earlier days, because all of these single hardcoded blocklists where merged into this one big hosts-file. So if there will be an option to choose which of them should be included, it would help to decrease the size of the hosts-file.

Now I've made some tests:

• Copying the hosts-file from uAdblockNG (ca. 42 MB) manually to /etc/hosts ends up in the same 10-15s of waiting
• Copying an older hosts-file I had saved earlier from Xenial (ca. 10 MB) works like expected, maybe 1-2 seconds of waiting

While waiting these 10-15 seconds I've checked the cpu-usage via top. The process "systemd-resolve" takes up 100%. So in my opinion the hosts file generated from uAdBlockNG is way too big for the performance of the volla.

I hope some other users can give a feedback to this, maybe @domubpkm ?