@stefano yes it is definitely annoying. I'll keep an eye on it and this thread in case I see something similar to your bug and I will report to you. Honestly, I'm not using the Pro5 that hard to be a 100% sure my device isn't affected.

@arubislander thank you for the pointer, you are right. I selected SuruDark and this makes not seeing anymore the cross on each tab header...Am I supposed to file this bug somewhere? The theme options selector is only available with UTTT, so maybe the issue should be properly raised there.

@advocatux I know, however I made several flashes of UT on the Pro5 so Next I'm sure coudn't exist anymore. Sorry to hijack this thread then, maybe I misunderstood its purpose.

@libremax ok but in the thread it was stated that the closing cross has disappear, so I just took advantage of that statement to expose this related issue. By the way, no big deal, don't pay attention to this issue, this could be something peculiar to my phone, maybe correlated to the weird behavior my phone has with certain UT features. Thank you for the reply!

@advocatux thank you for the hint but I just tried to clear the Morph's cache, data and config file but nothing changed, I'm afraid.

@libremax I reply here just to take advantage of the current thread opened by @guru to flag to you I found a similar issue as described by him. I noticed it since a while, I'm not quite sure since when, but for sure after Morph browser stepped in and got the first bunch of fixes. My device is a Pro5 and currently I'm up to date to the devel channel. I'd like to share with you what I see by attaching a picture. As you can see, the closing cross is not shown anymore in the tabs header but I'm still actually able to close each tab if I tap on the place where it was supposed to be.

@stefano I don't see such a behavior on my Pro5, I'm not on the stable channel but on devel one. I didn't understood if it does happen always to you or just in some reproducible circumstances?

@alainw94 I think you misunderstood...when I installed Anbox then my phone lost the IMEI number for some reason. I was just wondering if you made the same but from your answer it is clear you didn't so the reason why you lost the IMEI should be something else. However, try to follow Stefano's suggestion above and flash again Flyme in order to recover your IMEI.

By the chance, did you install Anbox on your Pro5? When I installed it on my Pro5, I lost the IMEI numbers but after an image wipe, i.e. changed channel, IMEI numbers came back.

@marc_aurel just my 2 cents here. Did you try, before to navigate into the anbox folder, to type sudo su and gaining the root access?
Second hint: you could try to move first your contacts file to an accessible folder, as for example Documents or Downloads, with adb push from your PC and then, from the terminal on your PC, you could type phablet-shell instead of adb shell, since I found out the latter has some limitations in writing on the phone partition. In the end, you could just copy your file, maybe better with root privilege, to /home/phablet/anbox-data/data/media/0/ using the cp or mv command.

@unisuperbox Test on Meizu Pro5 16.04 devel, last update 04-01-2019.

Environmental setup:

• Meizu Pro 5 phone: installed Bloototh File Transfer from the OpenStore;

• Dell Inspiron PC with Ubuntu 16.04 OS: installed blueman package.

I paired and connected both sides together prior to start with any transfer file.

Attempt #1: Sea.zip file to be transferred from PC to Pro5 caught into the following error, without even starting the transfer. Reading from /var/log/syslog:

Jan 5 11:59:39 ubuntu-phablet bluetoothd[2444]: Unable to get io data for Object Push: getpeername: Transport endpoint is not connected (107)

It doesn't seem to have been logged any other relevant messages in the syslog file.

Attempt #2: a random file, in this case it was a very small one, 2.5 kB, from Pro5 to PC was successfully transmitted.