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

    [OTA-1/OTA-2 RC] Clock resets after reboot

    Scheduled Pinned Locked Moved 20.04 Focal Fossa
    13 Posts 3 Posters 846 Views 3 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.
      • carbonatedC Offline
        carbonated @carbonated
        last edited by

        Latest RC
        This is on the latest RC after a reboot.

        D 1 Reply Last reply Reply Quote 0
        • D Offline
          Dunbrokin @carbonated
          last edited by

          @carbonated Actually, you are correct, I apologise for giving incorrect information....I upgraded the phone about a week a go to version 430 and it seemed to work.....and than I stuck the phone in a drawer (it is not my main phone) and on firing it up again to check the update number, I find it is still on some date back in the 1970s. Sorry again! 😠

          carbonatedC 1 Reply Last reply Reply Quote 1
          • carbonatedC Offline
            carbonated @Dunbrokin
            last edited by

            @Dunbrokin that's alright, thanks for helping confirm this issue.

            D 1 Reply Last reply Reply Quote 0
            • D Offline
              Dunbrokin @carbonated
              last edited by

              @carbonated Problem still persists after the recent update to 440.

              carbonatedC 1 Reply Last reply Reply Quote 1
              • carbonatedC Offline
                carbonated @Dunbrokin
                last edited by

                @Dunbrokin Still present in OTA-2

                arubislanderA 1 Reply Last reply Reply Quote 0
                • arubislanderA Offline
                  arubislander @carbonated
                  last edited by

                  @carbonated Is there an issue about this in the issue tracker on Gitlab / Github?

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

                  carbonatedC 1 Reply Last reply Reply Quote 0
                  • carbonatedC Offline
                    carbonated @arubislander
                    last edited by

                    @arubislander No

                    arubislanderA 1 Reply Last reply Reply Quote 0
                    • arubislanderA Offline
                      arubislander @carbonated
                      last edited by arubislander

                      @carbonated Then one needs to be opened. That is the only place were issues are tracked by the developers.
                      Also, you can then track when the issue has been resolved and in which OTA the solution will land.

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

                      D 1 Reply Last reply Reply Quote 0
                      • D Offline
                        Dunbrokin @arubislander
                        last edited by

                        @arubislander Thanks for that tip.....could you give us the link please and we can post it there.

                        arubislanderA 1 Reply Last reply Reply Quote 0
                        • arubislanderA Offline
                          arubislander @Dunbrokin
                          last edited by

                          @Dunbrokin You want to be in looking in https://www.gitlab.com/ubports. You will need a GitLab account to open an issue. If you think the issue might be specific to the clock app then searching for or else opening an issue here would be the right place. If you think it might be something more general then here is a good place to open the issue.

                          Also take some time to click around and familiarize yourself with the layout of the project, so you know where to file issues for other ... issues ... that you might encounter. This is a valuable way of contributing to the project.
                          Just don't be a drive-by issues opener: Include as much information about the issue as possible, especially information on how it can be reliably reproduced. Stay engaged, be ready to answer follow-up questions and to try out suggested work-arounds or fixes.

                          πŸ‡¦πŸ‡Ό πŸ‡³πŸ‡± πŸ‡ΊπŸ‡Έ πŸ‡ͺπŸ‡Έ
                          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 0
                          • First post
                            Last post