@applee hi, I finally updated atom clickable plugin and clicklable v7 and everything is fine! I can choose suitable target architecture.

Feel free to suggest any other peripherals working on UT. Please, give as much information and specify your device. I will adapt the post afterwards
Note : BT audio during phone call may not work with BT devices above 5.0 (incoming/outgoing).

Many thanks for advices below!

Hi Everone!
RCS is aiming at replacing SMS in a near futur.
Any plan to support it ?
Cheers

Hi everyone,
Thanks and honours to the UBports team for the great achievement so far! Thanks to make the whole thing moving forward.
I made my journey testing the 16.04/devel on my MX4 and wrote down my experience in a Calc spreadsheet. I'd to ask whether it's useful to share the file or not... It might be some kind of interest to gather experience to help developers ? No question to challenge Github of course...
Cheers,
W.

Hi Matthias,
You should get a system phone call code from your operator. It looks like ( remplace + with stars **)
++systcode+other.numbers.followed.by.your.phone.number++seconds.to.ring.before.voicebox#
Use the phone app to send the whole thing, press the green call button and voila...
The code might be different for you obviously, but anyway, it's triggered by the operator. Give a call to helpline...

BR

W.

@applee ok I'll give it a try. Thank you very much!

@oli.sax , Flohack & WLBI

At the EoD , Anbox wouldn't be a sustainable solution to run WA. Some month ago, I managed to make WA successfully work on Anbox/Xenial...but after a couple of weeks, it stopped suddenly... I upgraded the WA apk, reinstalled...nothing... After lots of retries I got an error message saying approx. "You have a custom Andoid rom installed, WA doesn't support...blabla..." .... End of the story.

I totally agreed with all opinions and all that has been said on WA...
Nowadays I some times use LoquiIM, which finally (voodoo magic?) stop displaying the sadly famous "decrypt error“ message after about 2.5 month...

W.

@linuxomane hi, this is a known bug that affects miatoll devices and maybe other Halium 10 ports. As I read a while ago, it is not that easy to fix

@ezze Hi, same step for me but coming from PRO5. I can confirm that the X6 is the chinese version and is not supposed compatible with UBports, neither MiA2 Lite.
I got my MiA2 on Amazon (Xiaomi boutique) after 2 weeks search and I must admit, a lot of chance because it was brand new, never used !
I also searched before on "second hand" web sites but the risk is you never know what you will receive as a phone.
I really hope you will finally have the opportunity to get one ! From my perspective, the MiA2 is currently one of the best phone to use with UTouch.

@nreal This will work for me :

1. Download firmware_jasmine_sprout_V11.0.28.0.zip
2. flash file "bluetooth.img" to slot a or slot b (depends of the setup)

This fixed completely BT issue on my MiA2.

@keneda Yeah ! Thanks ! update done

@muskist

@muskist Thanks! table updated

@luksus Hi! It does the job ! thanks!

Feel free to suggest any other peripherals working on UT. Please, give as much information and specify your device. I will adapt the post afterwards
Note : BT audio during phone call may not work with BT devices above 5.0 (incoming/outgoing).

Many thanks for advices below!

@bogotrax,hi, try download https://github.com/ubports-xiaomi-sdm660/artifacts/releases/download/20211023/firmware_jasmine_sprout_V11.0.28.0.zip

Then extract and flash bluetooth.img

@linuxomane hi, this is a known bug that affects miatoll devices and maybe other Halium 10 ports. As I read a while ago, it is not that easy to fix

Fixed : Wireless External Monitor is working on MiA2 with OTA-23 (thanks Alfred!)

@applee hi, I finally updated atom clickable plugin and clicklable v7 and everything is fine! I can choose suitable target architecture.

@flohack hi, is this feature specific to each device / port or will you change benefits to other ones?