@marathon2422 interesting. I was checking right now since I reinstalled Flyme 5.6.1.19 and I didn't see such an error among all the wi-fi access points. So you say that it could be there this NVRAM error but maybe I'm not able to see it on this Flyme version. However, I don't understand why rebooting the phone with Flyme the wi-fi credentials are retained but with UT they are not.

@marathon2422 Thanks. I need to investigate the matter searching on youtube and better acknoledge the issue.

Hi guys, it's still me :-)
I was reading this bug post on GH for Cooler:
https://github.com/ubports/ubuntu-touch/issues/76

It's quite the same issue I'm experiencing with my Pro5 and it seems that the @Marathon2422 comment on the NVRAM was right, even if on Flyme I didn't see any strange NVRAM-ERROR WIFI.
Nonetheless, I will re-install Flyme to better check the matter but in the meantime I'd like to raise some questions: why on Flyme the wi-fi password is retained, while once installed UT it is not retained anymore? Doesn't the NVRAM, in case of failure, act in the same way for every OS installed on the same phone?

@stefano I installed the Canonical version you gave to me Stefano, but as usual I have the same wi-fi and GPS problem also there unfortunately. I tried also with the ubuntu-device-flash from CLI but it throws similar error I attached before. No way to make this phone to work as expected with UT, considering that on Flyme it does work, thus it is very awkward.
This was the last attempt from my side for now, I'm afraid. I will try again maybe later but without bothering you people again, enough is enough.
Thank you everybody for the great support and in particular thank you Stefano, you were very helpful, I really appreciated ;-)

Ciao!

Matteo

@stefano sorry for the inconvenience Stefano. I don't want to bother you so much....However, in the meantime I re-installed UBPorts OTA 1 but always same problems...when the wi-fi is working, if I toggle off the wi-fi and suddenly on, it does recall the wi-fi AP credentials, no problem; but if I reboot the phone then no way to make the wi-fi to read from the stored file....it's a nightmare!

@stefano it doesn't work flashing to the Canonical version following your procedure. The error thrown after pushing the files is always the same:

@stefano Stefano, in the end it doesn't work with the CLI method, it pushes all the files but then just after starting the recovery boot it crashes...now, what I would like to do is the following:

1. Flashing back the Flyme version with the unlocked bootloader;
2. Flashing the UT Canonical version with TWRP but I don't know if this is possible, since I don't see any .img file in the folder you @Stefano pointed to me and when I tried from TWRP to restore from that folder it didn't work (confirmation needed, pleeeeaaassseeeeee);
3. Checking if with the Canonical version the wi-fi and GPS are working as expected;
4. If confirmed, I'll proceed by flashing the 15.04 UBPorts version with the UBPorts installer, checking if the working wi-fi and GPS are retained;
5. If confirmed, I'll proceed by flashing the 16.04 UBPorts version with the UBPorts installer, checking if the working wi-fi and GPS are retained.
6. If GPS and wi-fi will not work, I'm going to give up this time.

Thank you guys for the patience.

Cheers.

Matteo

@tera nope, also with sudo it throws me errors....maybe, I was thinking I could try to flash the Canonical Ubuntu Touch version and then switch to UBPorts and see what happens...do you guys by the chance have the Canonical image to be flashed? Any OTA up to 15 would be good, I guess. Thank you.

@tera I got this error:

I also tried other commands and for instance the wi-fi AP seems to be set in auto-connection mode, even if doesn't work:

@tera I confirm all the connectivity data regarding the "FASTWEB-1-AB8961" are correctly stored there, but it doesn't seem the phone actually read it after a re-boot. Thanks anyways.