• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
UBports Robot Logo UBports Forum
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login

Meizu Pro5 fastboot mode locked

Scheduled Pinned Locked Moved Support
133 Posts 9 Posters 80.1k Views 1 Watching
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • M Offline
      matteo @Marathon2422
      last edited by 20 Jun 2018, 09:26

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

      M 1 Reply Last reply 20 Jun 2018, 15:59 Reply Quote 0
      • A Offline
        advocatux
        last edited by 20 Jun 2018, 10:19

        Sorry for hijacking this thread but as there are some Pro5 users here, can someone with a running device type this on the Terminal df -h /android/cache/ and paste the "size" output here https://papad.org/p/ubp-devices-cache-space?

        Thank you!

        T M S 4 Replies Last reply 20 Jun 2018, 11:59 Reply Quote 0
        • T Offline
          tera @advocatux
          last edited by 20 Jun 2018, 11:59

          @advocatux Updated: Pro5/turbo: (64Gb version UbPorts OTA-3): 496M (32Gb version Canonical OTA-15): 679M

          A 1 Reply Last reply 20 Jun 2018, 14:02 Reply Quote 1
          • A Offline
            advocatux @tera
            last edited by 20 Jun 2018, 14:02

            @tera thank you!

            1 Reply Last reply Reply Quote 0
            • M Offline
              Marathon2422 @advocatux
              last edited by 20 Jun 2018, 15:55

              @advocatux said in Meizu Pro5 fastboot mode locked:

              df -h /android/cache/

              mine is at 913m for cache after using the one Stefano put up

              1 Reply Last reply Reply Quote 0
              • M Offline
                Marathon2422 @matteo
                last edited by 20 Jun 2018, 15:59

                @matteo
                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 m10fhd

                M 1 Reply Last reply 20 Jun 2018, 16:49 Reply Quote 0
                • M Offline
                  Marathon2422 @advocatux
                  last edited by Marathon2422 20 Jun 2018, 16:30

                  @advocatux
                  on this post,how to increase cache size.

                  Support
                  problems flashing UBports on meizu pro5.
                  I printed it, to follow it very carefully.

                  1 Reply Last reply Reply Quote 0
                  • M Offline
                    matteo @Marathon2422
                    last edited by 20 Jun 2018, 16:49

                    @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.

                    1 Reply Last reply Reply Quote 0
                    • S Offline
                      Stefano @advocatux
                      last edited by Stefano 20 Jun 2018, 17:20

                      @advocatux 701M (resized already for Xenial)

                      1 Reply Last reply Reply Quote 1
                      • M Offline
                        matteo
                        last edited by 27 Jun 2018, 17:18

                        @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":

                        Dbus.log
                        Ubuntu-location-service-trust-stored
                        application.click.sensorstatus
                        ubuntu-location-service-trust-stored

                        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.

                        Thank you.

                        Matteo

                        S 1 Reply Last reply 27 Jun 2018, 18:42 Reply Quote 0
                        • S Offline
                          Stefano @matteo
                          last edited by 27 Jun 2018, 18:42

                          @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?

                          M 1 Reply Last reply 28 Jun 2018, 08:26 Reply Quote 0
                          • M Offline
                            matteo @Stefano
                            last edited by 28 Jun 2018, 08:26

                            @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.

                            S 1 Reply Last reply 28 Jun 2018, 08:43 Reply Quote 1
                            • S Offline
                              Stefano @matteo
                              last edited by 28 Jun 2018, 08:43

                              @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.

                              1 Reply Last reply Reply Quote 0
                              130 out of 133
                              • First post
                                130/133
                                Last post