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.

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

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

@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

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.

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

Yesterday all of our SIP in Germany stated, that they will shutdown MMS at the end of June. So it's important to have an alternative as RCS for people who need this kind of service.

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

UT 24.04-1.2 stable:

Actors:
Manual brightness -> y
Torchlight -> y
Vibration -> y

Camera:
Flashlight -> y
Photo -> y
Video -> y
Switching between cameras -> y

Cellular:
Carrier info, signal strength -> y
Data connection -> y
Incoming, outgoing calls -> y
LTE calling (VoLTE) -> y (Congstar / T-Mobile Germany)
MMS in, out -> y
PIN unlock -> y
SMS in, out -> y
Change audio routings -> p
Voice in calls -> y
Volume control in calls -> p

Endurance:
24+ hours battery lifetime -> y
7+ days stability -> y

GPU:
Boot into UI -> y
Hardware video playback -> y

Misc:
AppArmor patches -> ?
Battery percentage -> y
Offline charging -> p (Display stays active)
Online charging -> y
Recovery image -> y
Reset to factory defaults -> y
SD card storage -> ?
RTC time -> y
Shutdown / Reboot -> y
Wireless External monitor -> ?
Waydroid -> y

Network:
Bluetooth -> y
Flight mode -> y
Hotspot -> y
NFC -> ?
WiFi -> p (a bit weird)

Sensors:
Automatic brightness -> y
Fingerprint reader -> y
GPS -> y
Proximity -> y
Rotation -> y
Touchscreen -> y
Double touch to wake -> n

Sound:
Earphones -> y
Loudspeaker -> y
Microphone -> y
Volume control -> y

USB:
MTP access -> y
ADB access -> y
Wired External monitor -> n

@Flohack I think you had the right idea. The last couple of days I closed all opened apps before shutting down the device and there was no crash/restart of lomiri. So it could be that the issue is depending on the lower amount of ram. I will observe this behaviour. Thanks.

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

@eclku0 Hi, you can prevent mediascanner from scanning separate folders by adding a file named ".nomedia" into them.
Maybe you need to clean up the database of mediascanner by deleting "/home/phablet/.cache/mediascanner-2.0/mediastore.db", but I don't think it's necessary.

I've also found a "solution" for the notch which is working for me. I modified the the patch for the vollaphone from unity8-notch-hax so that the panelbar has got a greater height and the indicators are placed under the notch. In that case the space left and right of the notch is unused, but for me it's better than not seeing the indicators (and the screen is still big enough ). Maybe we can find a better solution in the future for this.

I've had this double boot issue for a long time on my E4.5 running stable. I also hoped that this would be fixed with the next OTA-update, but after every update nothing changed.
I didn't want to wipe the phone because it's my daily driver so I searched for the problem. In my case it was a corrupt media database. I deleted

"/userdata/user-data/phablet/.cache/mediascanner-2.0/mediastore.db"

and then reboot the phone. After that everything was fine again.

I've updated mine from 0.9.7 to 0.9.10 via the .deb-package and switched my volla successfully to stable 20.04. Works fine

Hi,
I've the same bug on my E4.5. But in my opinion the bug was there from beginning on. It's like you described, you can't reproduce it. It can be that three calls will ring, the fourth not, and the fifth will ring again. I haven't found a solution and I have no idea why this is happening. But I think it is not a regression between 15.04 and 16.04, the bug was already in earlier releases.

Nice to hear that this fix works for other people with this issue also. @UKPhil I'm not sure if there's already a bugreport for this issue, if not you can add one and post my fix.

Isn't the normal behavior that clicking on the message itself opens a textbox where you directly reply, and clicking on the message-icon right of the message-text opens the full message inside the message-app?