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.

@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.

Hi everyone! It's time for sharing my experience on how UTouch in jasmine has sprouted
As stated here https://devices.ubuntu-touch.io/device/jasmine-sprout/ most of the phone features are available OOB, except regarding the wireless display monitor which is reported as "untested". So I tried... (OTA-19, devel channel)
You can jump part 3 if you want to get directly to the point

1. Firstly, I connected these Bluetooth thingies : (BT works like a charm! thank you Developers! Lovely!)

BT : adapter to HiFi (testing with music = more fun), keyboard, mouse (more convenient)

2. (a small parenthesis) On the Pro5 the external display works well. As you can see below, the Brightness & Display setting page is displayed like this :

• The Wireless Display page lets you see WL display adapters available in the area.
  Select the adapter and the pairing process starts : the phone screen becomes a "mouse/trackpad" and the external monitor switches to UT desktop - decidedly cool, really !

3. Now it's time to mess around with ext monitor on the Mi A2. To beginning with the Settings page, the "Brightness" icon is a bit different as it doesn't specify "& Display" and as expected, there isn't any "External display" section :
   [EDIT] : setprop ubuntu.widi.supported 1 , will make appear "& Display"

At this stage, well, I'm still determined to test the thing! Let's get to the terminal and see what one can do with the aethercastctl command (I paired a BT keyboard + mouse) : It enables, scans... Hopefull!

Now let's try to connect and see what happen... aethercastctl reports "connected" !

On the TV set, I can see the MS-display adapter screen showing "connection to ubuntu-phablet..."
Then as expected, the phone screen becomes a mouse/trackpad..., the TV set screen switches... but to... a black screen.
Ok, I pressed VOL+/- to get a screenshot... And here's what I got : a screenshot of the external monitor, which screen resolution seems to be the TV set.

Finally, I typed "blindly" : disconnect c6:9d... ( that one I pasted it ) and got my phone screen back !
Note that the resolution has changed back to "normal" and the stretched size of some indicator icons (the same occurs on the Pro5). The phone remains in "desktop mode" because of the BT mouse still connected.

4. Conclusion
   It seems some bits and bytes are missing or something else.
   Is the Mi A2 capable to screen cast ? On the Android side it seems to be : I remember the "screen cast" menu on androidone but I didn't try it out.
   There a XDA forum post saying that it works.
   It let me think and hope that something need to be done on UT (or Halium) to fully succeed.
   Can anyone help ? @shouko I'd be ok to provide logs, do testing and so on...
   Let me know and thanks for reading !

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

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

@applee Hi, thanks for your reply.
Yep, I can edit the source but, I don't know what to do. I tried to change the file clickable.json using my IDE ( atom) to tell the compiler some arm64 args but it does not have any impact.
Hopefully I could compile arm64 directly from the source code folder with clickable...

Hi,
I'm working on having arm64 build for Openradio. I succeeded to simply build it within the terminal and this command :

• clickable build --arch arm64

Then I installed the package with UT tweak tool and that's ok.
I noticed that the Openstore App shows that it conflicts with the stable version, which is btw the armhf version. Not a big deal, but not so clean either.

Now I'd like the make the relevant changes in the source code so I can compile it within my IDE setup (Atom+click plugin) and finally push a PR to the maintainer who will make it available for download in the Openstore.
I tried to add this in the file "clickable.json" :

• "build_args": ["arch=arm64"],

but atom still compile for the armhf version... So what should I do ?

Sorry for being so noob with such a question and as always, thanks for your help!

@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.

@nreal Can u try this in the terminal

Bluetoothctl [enter]
scan on [enter]

Then u should get this message:
No default controller available

I'm trying to get BT stops then starts again with command line but no success yet.

sudo service bluetooth restart

Does not gives any positive result neither

• on MiA2 = nothing happens + unable to restart the phone, need hard power off.
  It seems that a process is really stuck.
• or PRO5 = "job has already been stopped" but BT is still on

Would be interesting to ask someone owning another halium 9 device.

@danilo748 I experienced exactly the same, except that BT on my A2 seems to be more stable

@nreal Sorry I'm not sure to understand well. You mean BT is not working at all on your MiA2 ?

@nreal Theses steps to reproduce :
WIFI is on and BT is on = OK, can see devices. BT off then on again = OK, can see devices.
Set WIFI off = BT goes OFF itself few seconds after WIFI.

Set WIFI back on = BT stays off.
Restart is needed to get BT back on too.
If you can repoduce, I will file a bug.