I just noticted a further issue. In call forwarding it says to forward some home calls. When selecting this, it says forward incomming calls when not available (to a german number I do not know). When removing the hook to disable this and going back to the pre vious menu, it still says forwarding some phone calls. When going back to this menu, it says that calls are still forwarded to that phone number.

I just noticed that Waydroid Stop icon is there finally after successfully downloading waydroid on Volla 22.

Volla 22:
Calls: ok

I went down next to the dsl router wlan and connected directly to it. The download was fast and worked correctly. After that Waydroid worked correctly. Thus the problem seems to be, that the Waydroid helper download sometimes failes and still says with a green button complete, instead of saying download failed.

to upload I renamed the file ending with .txt, please ignore the txt when decompressing.waydroid-logs.tar.tz.txt

I think that I know what happend. I downloaded the image with GAPPS. It was very slow. I downloaded it via WLAN using a repeated jin the wlan network. It was 1 thrid downloaded, an seconds later it said "complete". But, I guess it had not downloaded at all. That is likely why the waydroid.desktop file ist not there. I tared it without it and uploaded the tar file as txt, as the forum was not able to upload tz files. I will try to download it near the wlan router without repeater. Pehaps it goes better.

@peat_psuwit

adb shell journalctl --user-unit=lomiri-app-launch--application-click--waydroidhelper.aaronhafer_waydroidhelper_3.2.0--.service >waydroid-helper.log
adb pull /home/phablet/.local/share/applications/Waydroid.desktop
adb: error: failed to stat remote object '/home/phablet/.local/share/applications/Waydroid.desktop':[waydroid-logs.tar.tz](Invalid file type. Allowed types are: .png, .jpg, .bmp, .jpeg, .txt, .log) No such file or directory
michael@debian:~$ tar -cv --xz -f waydroid-logs.tar.tz waydroid-helper.log Waydroid.desktop
waydroid-helper.log
tar: Waydroid.desktop: Funktion stat fehlgeschlagen: Datei oder Verzeichnis nicht gefunden
tar: Beende mit Fehlerstatus aufgrund vorheriger Fehler
michael@debian:~$ tar -cv --xz -f waydroid-logs.tar.tz waydroid-helper.log
waydroid-helper.log
[waydroid-logs.tar.tz](Invalid file type. Allowed types are: .png, .jpg, .bmp, .jpeg, .txt, .log)

@peat_psuwit
I have a Volla Phone 22. It had been on RC-channel.
It is now on UbuntunTouch 20.04 (2025-W22).

Waydroid was working before (previous version on RC-channel from the weeks before.
I did not reinstall the waydroid helper, as it seems to be the latest version.
I ran the Waydriod helper, selected deinstalling waydroid without wiping app data.
Then I used waydroid help to download the latest version of waydroid with GAPPS (as I had in my previous waydroid installed),

After download, I see the waydroid helper Icon and the waydrod stop (without the icon) in the app list. I do not see anything to start waydroid. Also after repeating the installation of waydroid it is the same and also after phone restart it did not change.

@Josh-FOSS
I have a similar issue on my Xperia X. My router has a seldom used name. If I leave it and I come back, it will automatically connect again. However the router / wifi network of my wife's parents has still the default name lets say "FritzboxXYZ". If I connect to it and leave the house the phone finds while I am going through the streets routers with this name and pouts a pop-up message on the screen that it found the router "FritzboxXYZ", however was not able to connect or and asks for the password, if I remember correctly. When I come back home, it detects my router immediately and if I go to my wife's parents house, the wifi router will not be detected anymore. However, if I restart the phone, it will immediately connect to the router "FritzboxXYZ".
Could it be the case, that you are using the routers default name or a frequently used name? Could you change the router / wifi networks name to a seldom used name? Does it work then?

Due to the black screen on Dekko 2 I switched on Xperia X lately from Dev to RC channel. Now the RC channel with latest update has also a blank screen.
Thus I switched to stable. This works fine as far as first tests indicated.

@alexjoverton

I am new to ubports.

Could you please provide more details how / where to get Dekko2 ReleaseCandidate.

As above with ubports-installer_0.8.4-beta_linux_x86_64.AppImage failed (latest version available) and I was unable to get the downloaded file SW_binaries_for_Xperia_AOSP_N_MR1_5.7_r1_v08_loire.zip / *.img accepted, I used ubports-installer_0.7.4-beta_linux_x86_64.AppImage, a previous version I still had on my computer and this worked.

After that I was able to reinstall with ubports-installer_0.8.4-beta_linux_x86_64.AppImage (latest version). This time it was not requested to manually download the image file. Installation worked.

Still there is the issue in ubports installer version 0.8.4 (ubports-installer_0.8.4-beta_linux_x86_64.AppImage) that installation of the image file failed before and why it is now working.

@phoenixlandpirat

No I did not. But now it worked. It found the Xperia X device itself. I guess I had the ubports installer opened twice. I found another window in the background.

But now I have another problem.

I had to download the SW_binaries_for_Xperia_AOSP_N_MR1_5.7_r1_v08_loire.zip from Sony manually. I have checked the sha256sum from the downloaded file against the checksum provided by Sony. It was the same.

I extracted the image file from the zip file and went on with the process.
Now I get the following error message:

I have tried it both. With the zip file and the image file. Both provide the above result. this was with ubports-installer_0.8.4-beta_linux_x86_64.AppImage

I made here a separate issue:
https://forums.ubports.com/topic/5540/update-versiom-609-failed-and-ubports-installer-fails

I had installed on my Xperia X Sailfish X OS and managed to install with ubports installer after some time to install ubports successfully (directly without reinstalling android before). This was quite difficult and I guess I had to activate the developer mode in sailfish os before.

Today in ubports a software update failed and therefore I tried to reinstall ubports with the ubports installer and I got the message.

Even if I had installed it some time ago with uborts installer.

I have installed on my Sony Xperia X Ubuntu touch. Today under software updates a new update version 609 appeared.
I downloaded it and installed it.

The install restarted the phone and the sony bootloader reported a recovery error. Thus the bootloader went back to the previous version from 21.01.21.

When I now come back to the software update menu, it still provides update version 609 as available, downloaded and ready for install.

If however I try to install it, it asks for "Restart & Installing" (german "Neustart & Installieren"), but nothing happens.

Now I have tried to install ubuntu touch with the ubports installer from scratch.
This failed with the above image, even if it worked successfully with a previous version of the bootloader before.

I have installed on my Sony Xperia X Ubuntu touch. Today under software updates a new update version 609 appeared.
I downloaded it and installed it.

The install restarted the phone and the sony bootloader reported a recovery error. Thus the bootloader went back to the previous version from 21.01.21.

When I now come back to the software update menu, it still provides update version 609 as available, downloaded and ready for install.

If however I try to install it, it asks for "Restart & Installing" (german "Neustart & Installieren"), but nothing happens.

Now I have tried to install ubuntu touch with the ubports installer from scratch.
This failed with the above image, even if it worked successfully with a previous version of the bootloader before.

I had installed on my Xperia X Sailfish X OS and managed to install with ubports installer after some time to install ubports successfully (directly without reinstalling android before). This was quite difficult and I guess I had to activate the developer mode in sailfish os before.

Today in ubports a software update failed and therefore I tried to reinstall ubports with the ubports installer and I got the message![alt text]( even if I already had ubports installed on thart device and developer mode activated.