The following worked fine for me: open the Contacts App, select the Contacts wanted, click Share and the Folder wanted with the File Manager App.
This generate a vcf file that you can read, amend, import back in the Contacts App or almost anywhere else

Quick update after 3 days with updated Pro5 Baseband:

1. Overall mobile data and calls feel more smooth so far
2. Battery consumption seems to have improved as well
3. Wifi connection appears much more stable than previously

@mihael I do not use Bluetooth but would you know which firmware is that (maybe from @Stefano list)?

@Stefano Thanks, i might give it a go when i have some spare time in the next weeks...

Hi UBPorts Community,

Having experienced lots of signal issues recently with my Pro5, I decided to give it a go and the following looks promising:

Procedure:

1. Download from XDA (latest to date: https://forum.xda-developers.com/meizu-pro-5/development/meizu-pro5-baseband-21-12-2017-t3727070)
   Extract the file /system/vendor/firmware/modem.bin and transfer it to your Pro5 (for instance to /home/phablet/Downloads)

2. Open terminal or SSH to your Pro5 and run the following commands:
   sudo -i
   mount -o remount,rw /
   cp /var/lib/lxc/android/system.img /home/phablet
   cd /home/phablet
   mkdir system
   mount -o loop system.img system
   cd system/vendor/firmware/
   rm modem.bin
   cp /home/phablet/Downloads/modem.bin ./
   chmod 644 modem.bin
   cd /home/phablet
   umount system
   mv /var/lib/lxc/android/system.img /var/lib/lxc/android/system.img.old
   cp system.img /var/lib/lxc/android/

3. Reboot

Here are the results on my spare original Pro5 Ubuntu Edition still running the latest Canonical OTA-15 behind a badly broken screen:

BEFORE:
phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/list-modems | grep Revision
Revision = S333_M86_20151002_CHNOPEN_MZ024
Revision = S333_M86_20151002_CHNOPEN_MZ024

AFTER:
phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/list-modems | grep Revision
Revision = S333_M86_20171221_CHNOPEN_MZt04
Revision = S333_M86_20171221_CHNOPEN_MZt04

I will try later on my day to day Pro5 on UBPorts r3 over the week end but let me know if anyone improves signal, especially if traveling in Europe

Peace,
Tera

@WillemHexspoor Try to switch Prevent App Suspension for Terminal in UT Tweak Tool App

@tera said in Meizu Pro5/turbo - kernel missing aes-xts-plain64 crypto ciphers:

Opened a matching issue for those interested: https://github.com/ubports/ubuntu-touch/issues/1107

Added Bq E4.5/krillin & Meizu MX4/arale (thanks @zubozrout ) to the list

FYI, i checked further devices and ciphers are present on Fairphone 2/FP2 (confirmed working), Nexus 5/hammerhead (just confirmed working) & BQ m10 FHD/frieza (not yet confirmed due to space missing for apt-get update)

Please report if you can check on other available and supported devices

Interesting interview here, on that topic: https://www.phoronix.com/scan.php?page=news_item&px=Zlatan-Todoric-Interview

Hello,
Thanks for all the hard work and getting Xenial out
Following on the Halium question above:
What is the current status of the Librem/i.mx 6/8m image?
Are there plan to support the Pine Phone?
Additionally, what about Raspberry Pi and a VM image?
Thanks!

@PINE64 Sorry, i meant a GPS kill switch?

@advocatux Updated: Pro5/turbo: (64Gb version UbPorts OTA-3): 496M (32Gb version Canonical OTA-15): 679M

Just updated my Pro5 UBPorts r3 and looking good so far!!
Let's see in the next days...

@keneda yop indeed

I used this tool successfully fyi which seems required once device is unlocked from what i understood: http://www.flashtool.net/downloads.php

@keneda aha thanks, at least i could try to build it, great stuff!

I can't be bothered ab replacing the USB board tbh, it charges at least so usable and even more private/secure huh

Ab the tuto, the last steps involve pushing manually the files from the installer to the recovery, could do that from a Terminal and reboot to recovery and upgrade i believe...

@keneda agreed, planned to use/adapt from this tuto: https://forums.ubports.com/post/47969

I already kept the recovery install files for OTA18 required from another install on top of Android, same device obviously, fyi

Ps: i also tried many USB cable/laptop/sbc... without luck over the years
but maybe that solution i think of would allow to upgrade it and make an up to date hw based non Data over USB device

@applee the link do not work, and why i opened this thread, it complains about the channel not being valid...

The phone USB do not work either so was thinking of tempting an over the air kinda upgrade but need the terminal for that actually

Openstore click app would do as well i guess but link is not working either for Vivid, last i tried and just confirmed as we speak

@oli-sax it appears to be linked to the browser requesting dark mode (?): https://pradyunsg.me/furo/customisation/colors/

Hi there

I got a Meizu MX4 still running Vivid completely Out Of The Box and wanted to install the Terminal app, however i get an error when trying to download it from: https://open-store.io/app/com.ubuntu.terminal/versions

Would anybody have it handy by any chance?

Cheers,
Tera

There are some posts ab it, you need the UT Tweak Tool app, go to System and ADB/USB Settings and enable RNDIS
I believe i had working on my FP2 previously fyi

@reedzsu it looks like you've hit the issue with the cache partition being too small for the update files to be stored on the phone, can you check the size of the partition number 15 (/dev/mmcblk0p15)?
You can use lsblk in a terminal for instance, it should be at least 700MB to work from some threads i read recently

A few days ago, i actually repartitioned a resurected original MX4 with Android, i did killed/bricked it years ago, and following the help of this thread which is another solution to your problem as well: https://forums.ubports.com/post/47969 (see steps 9.0.STAGE 2)
I have kept the info how to repartition using the Philz recovery image, on another laptop though, so can post it later as well here

@planejoe great stuff
I cannot comment much about the partition layout, some looks legacy in link with the android container i'd guess... though not required on PinePhone. If you check the multi image, Ubuntu Touch run from a single btrfs partition if i'm not wrong: https://xnux.eu/p-boot-demo/