Meizu Pro5 fastboot mode locked
@advocatux Updated: Pro5/turbo: (64Gb version UbPorts OTA-3): 496M (32Gb version Canonical OTA-15): 679M
advocatux last edited by
@tera thank you!
df -h /android/cache/
mine is at 913m for cache after using the one Stefano put up
The NVRAM error does not show on BQ version 1.0.0, or 1.3.0, only from 2.1.0 and newer, FYI
on this post,how to increase cache size.
problems flashing UBports on meizu pro5.
I printed it, to follow it very carefully.
@marathon2422 interesting. I was checking right now since I reinstalled Flyme 126.96.36.199 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.
@advocatux 701M (resized already for Xenial)
@Stefano I'm still trying to investigate what's wrong with my pro5 as I feel there is something weird that prevents my phone to properly work. The problem seems related to APPARMOR in some ways. I attach here some of the logs I find mostly representative of my phone "illness":
I don't have the deep knowledge to understand what's going on...I hope somebody can identify the reason why this is happening helping me eventually to resolve the problem.
@matteo I wish I could help, but I'm not a developer, nor can code. Maybe someone will have a look? Have you filled a bug report on Github Ubports website?
@stefano thanks anyways. I didn't open a bug report on GH yet because I'm not sure if this is related to the Ubuntu Touch OS itself or if this is peculiar of my phone only. I have the evidence that other people with fresh UT installation on pro5 don't suffer for the bugs I'm experiencing.
@matteo A lot of people with Pro 5 experience the data connection problem, signal drops, but not wifi. Strange, cos on Flyme is rather stable, so don't really know what's wrong and where.