I think everybody is interested in the actual state of

• 20.04 development-process:
  How far is this process ongoing? Are there any bigger problems? Is there an approximate timetable for the release?

• VoLTE:
  How far is this process ongoing? Are there any bigger problems? Is there an approximate timetable for the release?

I don't understand why people want to change from iOS/Android to UT but on the other hand still want to use all their services. In my opinion one effort of UT is, that you don't have to use accounts and services from these big companies and still have a functional and free phone in your hand.

I've upgraded my Volla from 16.04 to 20.04 with the installer. Here are my observations:

• Upgrade was easy and there were no problems with installing.
• With the first boot, the introduction/first start screen (Welcome to 20.04...) came up.
• My first SIM-card is PIN-protected and the system doesn't ask for the PIN automatically anymore. Now I have to unlock the card manually from the indicators. The second card (without PIN) works fine. The System is asking for the PIN-Code automatically.
• GPS is working with uNav.
• Calls (in/out) are working.
• WIFI is working.
• Cellular data is working (but only with SIM1).
• Flashlight is working. You can use the flashlight now with the app "uTorch", too.
• Automatic screen dimming is working.
• Camera is working (photo and video).
• Hotspot can be activated, but the device which wants to use the hotspot doesn't get an IP-address. Hotspot is working.
• Shutdown/Reboot from the indicator is working.
• Updates through WIFI are working.
• Battery-life seems to be like under Xenial.
• OSD (e.g. volume up/down) is working.
• Fingerprint is working.

I'll update this post if I realize any changes.

Update 26.12.2022: I've switched the phone to the 20.04 RC-channel and resetted the device using the "Erase & Reset All"-Option under system-settings.
Update 05.01.2023: I've switched to devel-channel.
Update 29.03.2023: I've made a fresh install of 20.04 stable OTA-1 via the installer with "wipe"-option
Update 01.08.2023: Update to OTA-2 via System-Settings

Is somebody able to tell about the status of "First steps in VoLTE"?
Is this project started, in which phase are we now, actual problems/showstopper, forecast?
I think this may help to clarify where UT stands in case of VoLTE.

Thanks

@domubpkm Work has started to open the door for you

@naizena When flashing my Volla with the installer it sometimes was so that the installer didn't restart my phone to fastboot-mode. It also said "flashing firmware partitions using fastboot" but I think it was still waiting for the phone to enter fastboot-mode.
When I restart my phone and select fastboot manually then the installer instantly started flashing. The whole process of flashing my device (with downloading files) takes around 5 minutes.
You can enter fastboot-mode by press and hold the power-button and volume-lower-button. Then there comes a little menu-selection where you can choose fastboot

Maybe you can test if it depends on your media files or something else. It seems that there is an option to prevent mediascanner from scanning separate folders by creating a file named ".nomedia" in the folder you want to prevent from scanning. I think you have not so many folders containing media on your phone so it would be easy to test.
After that please delete the DB and reboot the phone. I would expect that the DB-file will be rebuild but the mediaplayer will not know/detect any media on your device. If there's no double boot too you have found the problem. If not the search goes on

@bmarbol Here's what you're searching for.

Today Dekko2 is officially available for Focal in the Openstore and for me it's working like expected

How is the development of the "Bluez Upgrade" going on? On the Github project-page there's no status change. It would be nice if I can use the handsfree in my (new) car again.

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 )