Back to this.

The problem has been fixed and it everything should be ready for when OTA-22 gets released to the public.

In the mean time please avoid updating/changing to the RC and Devel channel.

Thanks. And sorry for the inconvenience!

There has been some questions on the forum related to these devices and they need their own subforum.

All the devices share the same port so it only needs one subforum for all of them.

https://devices.ubuntu-touch.io/device/joyeuse/
https://devices.ubuntu-touch.io/device/curtana/
https://devices.ubuntu-touch.io/device/excalibur/
https://devices.ubuntu-touch.io/device/gram/
Thanks!

@phiibuntu GPS under waydroid doesn't work. You have to use it with any of UTs apps that uses the GPS services following the instructions here: https://docs.ubports.com/en/latest/userguide/dailyuse/location.html

Idk. This tool looks like a jerk to me

After a few days I decided to try another vendor.img and out of nowhere reboots worked just fine. I still have no idea why the vendor messed up apparmor but anyway, if someone happens to have the same problem he could try using different vendor images.

@mbjunior sorry for the late reply. I'm more active in the https://t.me/ut_miatoll group on telegram.

Make sure you had the stock Android 10 ROM for your phone flashed with fastboot and also that you selected the wipe data option in the installer.

There are some cases I noticed that the OS refuses to boot if a custom ROM has been flashed before reflashing the stock ROM. The reason is unknown but it can be fixed by flashing the recovery ROM over the fastboot one. But I noticed this happening just one time on my phone.

Check again the first steps then in the last resort the last ones.

Thanks.

@mbjunior if miui starts and it says you have to confirm your phone number or something similar then you're good to go. Reboot in fastboot and run the installer.

Also you can find fastboot flashable ROMs here https://xiaomifirmwareupdater.com/archive/miui/curtana/

Just run flash_all.sh or flash_all.bash depending on your OS (Windows or Unix)

The sdcard will be properly fixed in the next OTA relase. If you want to test it now you can install the development channel from the settings app

@jakub Nah, the issue was with udisk udev. And actually I don't recommend it but you can fix the issue in stable and rc too.

sudo mount -o rw,remount /
sudo nano /lib/udev/rules.d/99-android.rules

Replace ENV{UDISKS_SYSTEM}="1" with ENV{UDISKS_SYSTEM}="0"

Save and reboot.

@nitanmarcel Thanks to everyone who tested this and contacted me.

Unfortunately there aren't any significant improvements so I've moved on and come back to this after the OTA-24.

In the mean time I managed to bring the port at the stage where is feature complete

@mecej2007 None of these apps you mentioned have support for Ubuntu Touch's push notification system, so you won't get any notifications from them

@lepotototor Make sure you used the latest fastboot image and not recovery image of android 10

The recording affects some other halium 10 devices too.

See this issue for a temporary fix https://github.com/ubports/ubuntu-touch/issues/2022

About the low audio, never had it myself, make sure you don't have the camera app in the background when playing audio, or don't play from multiple sources at once.

A quick fix is also restarting pulseaudio with pulseaudio -k instead of rebooting

About this issue. I don't use any external hardware that uses OTG and when the issue was first brought to me it has just late.

My only clue right now it's an issue with a kernel upstream patch, notified the contribuitor that helps me with the kernel version patches and hopefully will get it fixed in the next RC and OTA.

@linuxomane I noticed that the audio quality isn't so good, no idea how to fix it yet.

@nitanmarcel Thanks to everyone who tested this and contacted me.

Unfortunately there aren't any significant improvements so I've moved on and come back to this after the OTA-24.

In the mean time I managed to bring the port at the stage where is feature complete

@jakub Nah, the issue was with udisk udev. And actually I don't recommend it but you can fix the issue in stable and rc too.

sudo mount -o rw,remount /
sudo nano /lib/udev/rules.d/99-android.rules

Replace ENV{UDISKS_SYSTEM}="1" with ENV{UDISKS_SYSTEM}="0"

Save and reboot.

@mrt10001 That's only related to our miatoll port.The issue the OP has is totally different.

The sdcard will be properly fixed in the next OTA relase. If you want to test it now you can install the development channel from the settings app

For a while there have been complains about the battery lasting for a small amount of time (~2 days). Hopefully this will improve in the next upcoming OTA-24 but I need someone who has the possibility to go to the development channel, and leave the phone with the screen turned off and see if anything is improved here.

You can post the results here, on in the miatoll telegram chat at t.me/ut_miatoll

Thanks.