There are a number of threads about the loss of WiFi password after reboot of the Nexus 5 and of the BQ M10 but not much about the same problem on the MEIZU Pro 5 apart from https://forums.ubports.com/topic/708/meizu-pro5-fastboot-mode-locked

I have a MEIZU Pro 5 with 4GB of RAM and Ubuntu Touch 16.04 UBports OTA-7. This is not the Ubuntu Touch edition. This phone came with Flyme OS and I installed Ubuntu on it. I need to re-enter the WiFi password after reboot.

The way this problem occurs is strange because the password is not completely lost. If I open the Settings, go to Wi-Fi and then to the list of Previous networks, my access point is still there and it does have the password. The problem is that when I select this access point in this list, the only option I have is to Forget this network. I can't enable the connection from the list of previous networks.

In order to connect to this access point, I have to select it from the current list of networks from which the password is lost. Once I enter again the password, the list of Previous networks creates a new entry with the same network name albeit with the suffix " 1" added to it. If I reboot again and do the same thing, a new entry appears once again, this time with the suffix " 2". And so on with the suffixes 3, 4, 5, etc...

Has anyone found out how to fix the problem since the thread mentioned above?

Two questions if I may ask:

1 - How would it be possible to lower the minimum screen brightness?

2 - Would it be possible to have a full-screen function like the F11 function there is on Ubuntu Desktop? This would allow to display more lines to read on the web browser by hiding the web page address at the top of the screen. This would be particularly handsome in landscape mode.

I lower the display brightness to its minimum when in the dark but I find this minimum a bit too high. In the dark, the brightness is a bit blinding. How would it be possible to alter this minimum?

All Ubuntu Touch apps store user data in ~/.local/share/app-name/. It is impossible to open a file stored for instance in ~/Documents/.

One way around this would be to create a symbolic link:

 $ ln -s ~/Document/data-file ~/.local/share/app-name/link-to-data-file

Unfortunately, opening such a link with an app yield an empty file. However, if the data file were in the same directory as the link, then opening the link would yield the full non empty file. That is, if the link is created as:

 $ ln -s ~/.local/share/app-name/data-file ~/.local/share/app-name/link-to-data-file

then everything works fine.

It seems that Ubuntu Touch apps are blind to the directory tree. Does anybody know a way around this problem? How could one choose where to store data files and not be restricted to ~/.local/share/app-name/ ?

Shall we ever be able to boot from a mainline kernel and from an SD card on Android devices?

@hankschwie

UT Tweak Tool themes have no effect on the brightness of apps.

@kugiigi You are right. Thanks.

Usually recent mobile phones don't run UT because it takes time to port the software onto them. So I am surprised that the port to the OnePlus 6T was so quick. What happened then?
Has anyone tested convergence on this beast of 8GB of RAM? This could be an ideal device for use as a desktop computer.

@BrisPete Thanks BrisPete. I should have found out by myself instead of starting a new thread... Sorry.

@3t_ed Yes I have experienced issues with the keyboard too.

Thank you @arubislander and @MrT10001

This is really my fault. I should never have attempted to re-install with UBports graphic installer. Originally I had installed UT without it a long time ago. I did it manually. It was very complicated and I had to manually partition the device. Therefore the partitioning I made must have been different from that of the Pro 5 with 3GB that is approved for the UBports installer. So I must have bricked my 4GB Pro 5 when the UBports installer tried to write things on a somewhat wrongly partitioned device.

The problem now is not that I have lost the hardware by bricking it but that I have lost my data... I had tried sometime ago to make a backup with the intention of moving to a more recent device. But I was only able to backup a very limited amount of data and not the important data I wanted to save...

Is there anyone who could help me recover the data? I don't even know if it is possible since my attempt of re-installing with the UBports graphic installer may have screwed the partition and the addressing of the files or maybe even the files themselves...

All internet pages were said to be insecure with a broken red padlock. So I tried to reinstall the system with the UBports graphic installer. The installation failed and my device won't boot any more.

My Pro 5 has 4GB of RAM. It is not therefore the Ubuntu Touch version. However I could run Ubuntu Touch without problem before I bricked the device.

Any advice to un-brick my phone would be welcome.

@lduboeuf Thanks.

How would it possible to do a keyword search through the data of the agenda app? Would the grep command in the terminal app do the trick? Is this data in text or binary form and in what directory?

It turns out that the backup functionality was never pushed to the official installer.

The backup function seems to have disappeared from the installer. What happened to it please?

Thanks @MrT10001. It is indeed on GitHub:

$ cat ubports-installer_0.10.0_linux_amd64.deb.sha256
a530f8fbb867b07aafdabf06459b2ffec5f64202a56f13bf87ca0c225b5b1189

Where could I find an md5sum or an sha256sum for the ubport-installer please?

I can't install Ubuntu Touch on my OP6T. The installer is stuck at

"Waiting for device... Fastboot is scanning for devices".

This happened after the phone became bricked as it booted and still boots with the following message:

QUALCOM CrashDump Mode
Attempted to kill init! exitcode=0x0000000b
complete_and_exit

I bricked the device after running into difficulty trying to install TWRP first:

fastboot flash recovery twrp.img
Writing 'recovery' FAILED (remote: '(recovery_b) No such partition')

Then I read https://android.stackexchange.com/questions/209673/why-cant-i-write-to-recovery-using-fastboot-on-a-b-device which advised to run instead

fastboot boot twrp.img

That is when the phone became bricked...

May I ask if Focal Fossa is working on the Meizu Pro 5? If so, should I upgrade to it or should I stay with Xenial?