@advocatux yes this is it. Thank you advocatux :). @ubuntoutou anyway if you wish to use it, consider this is not an official tool advised by UBports but you have to use it carefully, because apt-get command is not supported on UT OS.

@Marathon2422 yes I already checked in Flyme several times and I didn't get such a NVRAM error. That's why I excluded this issue among the possibilities. Thank you for asking by the way.

@ubuntoutou it is possible. I just did it: I have both installed on my phone and they work great when launched with the terminal. I used a software called ATU to install the packages but basically it installs those by apt-get command. I also rebooted my phone after that without any issue. I don't see very useful data among the reported ones with both the commands by the way.

@Stefano just now I realized I have the TD-LTE one...interesting...so, from what you said, this model is the only one with 4 GB?

@arubislander I don't think so, I just followed the procedure. Yes, I had to struggle a bit since the beginning when I needed to gain root access but then all went smooth. As said, anytime I flash back FlymeOS, the wi-fi connection starts again to work as expected.

@arubislander now your post is more clear, thank you. Anyhow, you have the international version. I believe the problem resides in the combination chinese version + 64 GB sd card, since, if I'm not wrong, @Stefano has got the chinese version, but with the 32 GB sd card.

@arubislander I also exploited a TWRP file Stefano pointed to me to install a previous version of UT to boot with, in order to be able to update to the latest image of UT. I don't think the problem could be caused by this let's say "short-cut" to by-pass the UBports installer, because after that I performed several times a brand new UT OS installation, in this case employing the official UBports installer and the wi-fi issue was always there.
When you say Android which OS are you talking about? I'm asking since I believe the Pro5 only comes with stock FlymeOS installed, which is an Android OS.

@Stefano I don't think Marius is the only one to have the skills to help us in this. Also Dalton does and even all the other UBports developers. Whoever can point us to the right direction is very welcome. Since this seems not only affecting the Pro5 but also other very well known devices, as the Nexus 5, maybe the interest at this topic will raise.

@ubuntoutou @Stefano @zubozrout I'm the one who first complained about the "Wi-fi" issue in the thread located HERE. I'm glad that finally someone else is raising the problem...I don't feel myself alone anymore in this crusade :). Now, I read with deep interest what you all wrote above and I'd like to proactively contribute to the discussion with my findings related to the Meizu Pro5. Similarly to @ubuntoutou, my device is a 64 GB/4 GB RAM, which was dispatched to me with installed chinese stock FlymeOS and, in order to make this device eligible to be flashed with UT, I needed first to follow the particular procedure to convert it from chinese to international device. Here my findings:

• What described by @ubuntoutou is exactly the same issue I have every time I re-boot the phone;

• I'm not convinced it could be a problem due to neither a faulty EFS partition nor to NVRAM as suggested by an other Forum user, because, as mentioned by @Stefano, when I flash again FlymeOS, as I already did many times in order to find the culprit, the wi-fi credentials are correctly stored and pushed at every reboot. When I flash back UT, it just doesn't work anymore.

• I didn't notice before that the wi-fi address changes at every reboot. I can confirm this behavior, thanks to @UniSuperBox.

• The only workaround I found to overcome the problem is related to the Anbox installation: when I first installed Anbox, surprisingly the issue was resolved (please read the relevant Github issue). I dug into the Anbox files to find out if I could isolate the part of code responsible for that and to maybe write a script useful at the scope, but, since I'm not a developer, I didn't accomplish completely the task. What I understood is that Anbox setup files create a bridge to the network and this bridge somehow resolves the issue. Since then, I gave up with Anbox because it caused to me other undesirable side effects and never tried to install it again, not even after it was made a sensible progress for the installation procedure and images (I'm talking about this thread by Marius).

What I believe is that the solution is closer than we think but we definitely need someone who can point us where to look at and who can suggest the path forward. Needless to say, I'm keen to spend some additional time at it in order to resolve that issue.

Thank you all very much.

Matteo

@Stefano I also once changed the baseband following the guide on this forum but I didn't notice such an improvement. To be honest I didn't test it so heavily so thank you Stefano to have made us aware of that, I'll certanly flash it back and pay more attention to the behavior. As a final comment, I'd say that if confirmed to be worth the upgrade, it would be great if the latest firmware would be included in the UT image.