Posts made by kristatos

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 ?

@Bolly Vollaphone (yggdrasil) on 20.04 OTA-4. But this was also with OTA-3, maybe also earlier versions.

@MrT10001 Yes, there is a delay. It has nothing to do with switching between mobile data and wifi. My startpoint was always no data connection and then switched on wifi or mobile data. With mobile data only I can start surfing immediately, with wifi only I have to wait these 10-15 seconds.

@Bolly My phone is powered off every night and i've already tested it with other some other wifis, it's always the same.

I've observed an issue regarding uAdBlockNG. Before opening a bug report, I wan't to know, if others are also affected:

uAdBlockNG not activated:

• Connected via WIFI, internet is usable immediatly (e.g. loading websites, checking E-Mail)
• Connected via mobile data, internet is usable immediatly

uAdBlockNG activated:

• Connected via WIFI, internet is usable after 10-15 seconds. In this time for example you can enter an URL in morph, but the blue "loading bar" underneath isn't moving from left to right. Or as another example Dekko shows the spinning circle after updating the mails. After these 10-15 seconds, everything is working like expected.
• Connected via mobile data, internet is usable immediatly

So the only problem is activated adblock together with a WIFI-connection. Does somebody else also have this problem?