Although I use Ubuntu Touch (UT) as my daily driver, I haven't been able to convince anyone to switch to UT so far. Besides the availability of Android apps, I see two main reasons for this.

1. Most phones are 5 years old or older. No one wants to invest money in an outdated phone that also has a poor battery by now. Furthermore, the future development for the selected devices is not guaranteed and heavily relies on individual contributors. A potential solution, in my opinion, would be to have a new "primary device" released every two years. This point might be classified as priority 0.

2. People interested in UT often have a strong focus on privacy and security. While the OS is privacy-friendly, I don't see adequate protection when using browsers. For me, in addition to data encryption, it’s important to easily change the DNS server and to use a secure browser that can mitigate tracking and fingerprinting, for example, through extensions. I think this is priority 5.

Thank you for starting the initiative!

On a OnePlus 5T, I have updated both UT and Waydroid. Since then, on one hand, it has become almost impossible to establish an internet connection in Waydroid. On the other hand, I also have the following problem: if the phone is lying overnight with airplane mode on and Waydroid open, the phone freezes by morning. While the current time is displayed, I can only restart the phone through a hard reset. If I turn off Waydroid beforehand, this does not happen. Does anyone know this problem?

In the calendar of the upper menu bar, each month starts on a Wednesday (like in the current month).

I found a solution: The private DNS must be disabled, and the network connection needs to be restarted.

I have also updated Waydroid and now face the issue that I no longer have an internet connection inside Waydroid. Is there a solution to this problem now?

Is it otherwise possible to revert to the old Waydroid image?

Thank you!

I reinstalled the update with the UBports installer again, then restarted the phone twice for testing, and the restart duration was normal. It looks to me like everything is working as expected now.

Yes, I installed the stable image via the Ubports installer. After that, I restarted the phone. Several attempts led to the following results:

1. The phone displays the Android boot screen for about 45 minutes, then the UBports lock screen appears, but without a SIM PIN prompt. When I unlock the screen, the phone jumps back to the UBports boot mode until the lock screen appears again. This happens in an infinite loop.

2. The phone gets stuck endlessly on the Android boot screen until I force it to shut down.

3. In one attempt, the phone started up correctly.

By the way, the booting consumes an extremely large amount of battery. After about 5 attempts, the full battery was drained. The minimum boot time was 20 minutes.

@Keneda I understand that the first start after the update takes longer. However, I wasn't aware that it takes so long each time I restart the phone.

P.S.: Sometimes it doesn't work even after a long wait. Then I have to hart reset the phone.

Does anyone have an idea on how to fix this?

@danfro With the ubports installer, I was able to apply the update. Unfortunately, the phone always gets stuck at the android boot logo every time I restart it. Something seems to be going wrong here. To be able to restart the phone, I need to reinstall the update using the UBports installer. My daily driver is a OnePlus 5T.

@danfro I was finally able to install the update using the Ubports Installer. However, I also received a message here that an error occurred. I chose the "Ignore" option, and the update was installed—hopefully without errors.

Thank you for your support!

@danfro After a long wait, the Ubuntu Touch boot screen appeared yesterday, followed by the unlock screen. However, the phone could not be unlocked. So, I restarted it by pressing the power button. Then the Android screen appeared, and I waited for about 8 hours.

When I press the power button again and restart the phone, it remains stuck on the Android screen without any changes.

Yesterday I received the update. After restarting, the phone gets stuck on the startup screen (Android logo). What can I do? Thanks.

No problems with OP5T and Debian.

@danfro

@danfro The installation worked. The error does not occur in this version.

After I installed the version from the Open Store again, the error no longer occurred.

I'm sorry, but I don't know how to install it.

OP5T = build-arm64?

No, I would have definitely noticed.

@danfro The problem persists even after a restart.

It gets even crazier. If I quickly scroll through a long note, the app also crashes.

When I lock and then unlock the device, the app only crashes when it is in the foreground.