@captainzer0 Finally the phone is ringing again. What I did is an update to version 764 from the development channel. It seems to have fixed the problem.

@keneda Yes, exactly. I alteady found a bug report on the github. It looks like it is affecting more phones.

Hello all. I have just experienced strange behaviour after update to version 40 of UT. I do not know what exactly is causing this, but since the update, there is no ringtone at incoming calls. Only vibrations. Does anybody have the same experience? And is there any way to fix it?

Thank you.

Hello all. I found out that recently a new update was released for this phone. The files are here:

https://github.com/ubports-xiaomi-sdm660/artifacts/releases

Does anybody know, how to perform update of the phone's system with this latest release? Is any guide existing? I believe it could solve some problems I have (e.g. with bluetooth), but I have absolutely no idea how to do it.

Thank you.

@c4pp4 If I restart, then the hci0 goes on. But when I go to the settings to search for any device to connect, the hci0 goes out. So it seems going to the settings is breaking it.

@c4pp4 Still no hci0 unfortunately. Output is below:

phablet@ubuntu-phablet:~$ sudo stop bluebinder
[sudo] password for phablet:
bluebinder stop/waiting
phablet@ubuntu-phablet:~$ rfkill list bluetooth
0: bt_power: Bluetooth
Soft blocked: no
Hard blocked: no
phablet@ubuntu-phablet:~$ sudo start bluebinder
bluebinder start/running, process 10005
phablet@ubuntu-phablet:~$ rfkill list bluetooth
0: bt_power: Bluetooth
Soft blocked: no
Hard blocked: no
phablet@ubuntu-phablet:~$

It is strange, because it has worked until today in the morning.

@c4pp4 Yes. I downloaded the vednor.img from the link in the ubports installer and then uploaded it manually. The only thing is that I downloaded the vendor.img in the latest version of ubports installer, but the intsallation itself was done in the older version - 0.88 I guess.
It was necessary due to the fact that the latest uboports installer did allow selecting the downloadad vendor.img in the file picker, but nothing happened then (button next did not respond). The version 0.88 worked fine. I had to use DEB package, because in SNAP package, the installer always crashed when trying to select the vendor.img in file picker.
I do not know if this procedure might bring any problems, but I do not think so, because it installed the latest version of UT successfully without any complaints.

@sladek9 I made another finding by using dmesg | grep -i blue
It seems that there was some failure during bluetooth initiation. The output is below:

phablet@ubuntu-phablet:~$ dmesg | grep -i blue
[ 1.363871] Bluetooth: fffffffcf9533d68
[ 1.363919] Bluetooth: fffffffcf9533d68
[ 1.363933] Bluetooth: fffffffcf9533d48Bluetooth: fffffffcf9533d28
[ 1.363975] Bluetooth: fffffffcf9533d48<6>[ 1.364322] cfg80211: World regulatory domain updated:
[ 1.960541] Bluetooth: fffffffcf9533d78
[ 2.186937] Bluetooth: fffffffcf9533d48
[ 2.186943] Bluetooth: fffffffcf9533d48Bluetooth: fffffffcf9533d68
[ 2.186964] Bluetooth: fffffffcf9533d28Bluetooth: fffffffcf9533d28
[ 2.186975] Bluetooth: fffffffcf9533d08Bluetooth: fffffffcf9533d78
[ 2.186987] Bluetooth: fffffffcf9533d58<6>[ 2.187022] l2tp_core: L2TP core driver, V2.0
[ 4.670332] init: /vendor/etc/init/hw/init.qcom.rc: 576: ParseTriggers() failed: unexported property trigger found: ro.bluetooth.ftm_enabled
[ 4.695718] init: Parsing file /vendor/etc/init/android.hardware.bluetooth@1.0-service-qti.rc...
[ 7.909464] init: starting service 'vendor.bluetooth-1-0-qti'...
[ 7.934887] init: Command 'mkdir /persist/bluetooth 0770 bluetooth bluetooth' action=boot (/vendor/etc/init/hw/init.qcom.rc:176) took 0ms and failed: mkdir() failed: Read-only file system
[ 21.241687] bluetooth_power: bt_power gpio config failed
phablet@ubuntu-phablet:~$

@sladek9 So now it stopped working again. I cannot make it working and rfkill list bluetooth gives:

0: bt_power: Bluetooth
Soft blocked: no
Hard blocked: no

the section about hci0 is missing. Does anybody know what this means?
Thank you.

@c4pp4 Bluetooth works at the moment. The output is:
0: bt_power: Bluetooth
Soft blocked: no
Hard blocked: no
2: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
I will try the same as soon as the problem reoccurs. It might show something.
Thank for the advice.

Hello all,
yesterday I managed to successfully install the UT (OTA-19) on my Xiaomi Mi A2. Everything works well apart from bluetooth.
After boot, the bluetooth is activated in the system tray, but when go to the bluetooth settings to search for devices, the bluetooth is off and the phone is undiscoverable. And it cannot be switched on at all.
Sometimes it helps when I disable the bluetooth in the system tray right after reboot, go to settings and enable it there. But not always. I cannot find any particular pattern how to make it work reliably.
Another thing is that even if I am lucky sometimes, I manage to activate the bluetooth and connect to any audio device (headphones, car multimedia), the sound is played through the bluettoth device in all cases except from the phone call. If I make a call, then its sound does not go through the bluettoth, but through speaker of the phone (dialing via bluetooth works well).
Does anybody have similar experience or does anybody happen to know how to fix it and make bluetooth work reliably?
Thank you.