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

    Are we forgetting the little bugs?

    Scheduled Pinned Locked Moved General
    system
    51 Posts 13 Posters 15.3k Views 4 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.
      • U Offline
        UKPhil
        last edited by

        @Lakotaubp sure lets see as I still have not got the double boot on shut down after the latest upgrade. However, still getting the double start up issue.

        1 Reply Last reply Reply Quote 0
        • K Offline
          kristatos
          last edited by

          I've had this double boot issue for a long time on my E4.5 running stable. I also hoped that this would be fixed with the next OTA-update, but after every update nothing changed.
          I didn't want to wipe the phone because it's my daily driver so I searched for the problem. In my case it was a corrupt media database. I deleted

          "/userdata/user-data/phablet/.cache/mediascanner-2.0/mediastore.db"

          and then reboot the phone. After that everything was fine again.

          BQ Aquaris E4.5 (UT 16.04)
          Vollaphone (UT 20.04)

          1 Reply Last reply Reply Quote 1
          • U Offline
            UKPhil
            last edited by

            @Flohack @Lakotaubp guys we have a few people mentioning this double boot issue on at least two devices now and we seem to have a potential fix by "kristatos".

            Would this be a good time to have this looked into, so others do not have to just put up with it?

            @Flohack is you need this testing, you know you only have to give me a shout on Telegram.

            LakotaubpL 1 Reply Last reply Reply Quote 0
            • LakotaubpL Offline
              Lakotaubp @UKPhil
              last edited by

              @ukphil Can you check if you have that .db first. If you do you could try removing it and see what happens. I'll be back in about 8 hours. Good luck.

              1 Reply Last reply Reply Quote 0
              • U Offline
                UKPhil
                last edited by

                @Lakotaubp I have just tried to access /userdate in Filemanager (unlocked) and it will not let me in. I will have to try at home in a few hours.

                LakotaubpL 1 Reply Last reply Reply Quote 0
                • LakotaubpL Offline
                  Lakotaubp @UKPhil
                  last edited by

                  @ukphil Same with me.Lets see later. Thanks

                  arubislanderA 1 Reply Last reply Reply Quote 1
                  • arubislanderA Online
                    arubislander @Lakotaubp
                    last edited by arubislander

                    @lakotaubp the location mentioned by @kristatos can also be accessed as /home/phablet/.cache/mediascanner-2.0/mediastore.db

                    πŸ‡¦πŸ‡Ό πŸ‡³πŸ‡± πŸ‡ΊπŸ‡Έ πŸ‡ͺπŸ‡Έ
                    Happily running Ubuntu Touch
                    Google Pixel 3a (20.04 DEV)
                    JingPad (24.04 preview)
                    Meizu Pro 5 (16.04 DEV)

                    1 Reply Last reply Reply Quote 1
                    • U Offline
                      UKPhil
                      last edited by

                      @arubislander thanks for that, I was able to locate the item mentioned by @kristatos and remove it. I did not want to delete it straight away in case it all went wrong, so I moved it to another folder.

                      @Lakotaubp I can confirm that after moving the mentioned media database I have restarted my DPD a number of times (by shut down & restart) and each time it has booted up just once. Not I get past the two lots of scrolling dots, I get three lots and then the login screen. I will monitor this for some time and see how it goes, but initial tests are promising.

                      Is there any way we can get this fix/delete of corrupt media database in the next release to help all those that have this issue but may not of read this thread? Seems a nice quick and easy fox.

                      @kristatos you are a star for finding that out and adding it here. Like I say initial tests are very promising. Thank you so much for adding your fix here and helping me and all the others out who have this issue. Cracking work mate.

                      LakotaubpL 1 Reply Last reply Reply Quote 2
                      • LakotaubpL Offline
                        Lakotaubp @UKPhil
                        last edited by

                        @ukphil Keep an eye and report back here in a few days. If you could check the bug reports on github and see if one matches this and the fix works you can add it to that if not. Probably best to create a new bug report then add this as a fix. That way it won't get missed. Thanks for thework everyone.

                        1 Reply Last reply Reply Quote 1
                        • H Offline
                          hummlbach
                          last edited by

                          Awesom! Thats exactly how users can help the devs. I think now theres a reasonable chance to get that fixed. Well done community! πŸ™‚

                          LakotaubpL 1 Reply Last reply Reply Quote 1
                          • LakotaubpL Offline
                            Lakotaubp @hummlbach
                            last edited by

                            @hummlbach Quite right a great example of community pulling together to sort through an issue. Once again thanks to all those involved : )

                            1 Reply Last reply Reply Quote 0
                            • U Offline
                              UKPhil
                              last edited by

                              I can confirm that the fix given does actually work. Last night there was a system update (version 18) that I installed. After this install the double boot issue came back again. On checking the "/.cache/mediascanner-2.0/mediastore.db" was back again, so I removed it again and since then no double boot.

                              No worries about adding the bug report, but do you want to @kristatos as it is your hard work that has found the fix, I am just the tester πŸ™‚

                              1 Reply Last reply Reply Quote 0
                              • K Offline
                                kristatos
                                last edited by

                                Nice to hear that this fix works for other people with this issue also. @UKPhil I'm not sure if there's already a bugreport for this issue, if not you can add one and post my fix.

                                BQ Aquaris E4.5 (UT 16.04)
                                Vollaphone (UT 20.04)

                                1 Reply Last reply Reply Quote 1
                                • U Offline
                                  UKPhil
                                  last edited by

                                  Cool will do and will post the number here.

                                  1 Reply Last reply Reply Quote 0
                                  • U Offline
                                    UKPhil
                                    last edited by

                                    As an update I have noticed that most times I delete this db it will vome back. I think the fix has not worked when I get a double boot, only to find it back again.

                                    LakotaubpL 1 Reply Last reply Reply Quote 0
                                    • LakotaubpL Offline
                                      Lakotaubp @UKPhil
                                      last edited by

                                      @ukphil That sounds like proof! Do you have the bug number yet?

                                      1 Reply Last reply Reply Quote 0
                                      • dobeyD Online
                                        dobey
                                        last edited by

                                        To be clear, when people are saying "double boot" here, they do not actually mean that the phone reboots right? If so, I don't see how the mediascanner db could cause that.

                                        1 Reply Last reply Reply Quote 0
                                        • U Offline
                                          UKPhil
                                          last edited by

                                          @dobey this has been covered about 17 comments from the top

                                          1 Reply Last reply Reply Quote 0
                                          • U Offline
                                            UKPhil
                                            last edited by

                                            Issue raised in GitHub under https://github.com/ubports/ubuntu-touch/issues/929

                                            K 1 Reply Last reply Reply Quote 0
                                            • K Offline
                                              kristatos
                                              last edited by

                                              Strange that this issue is coming back to you. I deleted this DB around Ubports OTA-2 and after that there was no double boot again. Also not after installing OTA-3 and OTA-5.
                                              I've looked at my E4.5 and it seems that this DB is build at every boot again. So could it be that there are some broken files on your system which end up in a corrupt database?

                                              BQ Aquaris E4.5 (UT 16.04)
                                              Vollaphone (UT 20.04)

                                              1 Reply Last reply Reply Quote 1
                                              • First post
                                                Last post