• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
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 835 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.
    • C Offline
      carbonated
      last edited by 26 Jul 2023, 01:10

      NOTE: This is reposted from the OnePlus subform, but as other devices have had the issue too, I will post it here.

      I'm currently using a OnePlus 6 on Ubuntu Touch OTA-2 RC and during testing, I have found that the clock will reset to manual after a reboot and display the incorrect time.

      I am unsure if this is the case for many others. If you have any spare time, could anyone report if you have this problem as it has been present for me ever since 20.04 was released for the OP6 (Though it is not present on 16.04 OTA-25).

      D 1 Reply Last reply 26 Jul 2023, 01:19 Reply Quote 1
      • D Online
        Dunbrokin @carbonated
        last edited by 26 Jul 2023, 01:19

        @carbonated I had it on my OP6 but the latest update fixed it.

        C 1 Reply Last reply 26 Jul 2023, 02:48 Reply Quote 0
        • C Offline
          carbonated @Dunbrokin
          last edited by 26 Jul 2023, 02:48

          @Dunbrokin I am still having the same issue. What channel is this?

          C 1 Reply Last reply 26 Jul 2023, 03:06 Reply Quote 0
          • C Offline
            carbonated @carbonated
            last edited by 26 Jul 2023, 03:06

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

            D 1 Reply Last reply 26 Jul 2023, 05:49 Reply Quote 0
            • D Online
              Dunbrokin @carbonated
              last edited by 26 Jul 2023, 05:49

              @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! 😠

              C 1 Reply Last reply 26 Jul 2023, 07:05 Reply Quote 1
              • C Offline
                carbonated @Dunbrokin
                last edited by 26 Jul 2023, 07:05

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

                D 1 Reply Last reply 29 Jul 2023, 02:23 Reply Quote 0
                • D Online
                  Dunbrokin @carbonated
                  last edited by 29 Jul 2023, 02:23

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

                  C 1 Reply Last reply 29 Jul 2023, 22:36 Reply Quote 1
                  • C Offline
                    carbonated @Dunbrokin
                    last edited by 29 Jul 2023, 22:36

                    @Dunbrokin Still present in OTA-2

                    A 1 Reply Last reply 31 Jul 2023, 07:46 Reply Quote 0
                    • A Offline
                      arubislander @carbonated
                      last edited by 31 Jul 2023, 07:46

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

                      C 1 Reply Last reply 31 Jul 2023, 13:40 Reply Quote 0
                      • C Offline
                        carbonated @arubislander
                        last edited by 31 Jul 2023, 13:40

                        @arubislander No

                        A 1 Reply Last reply 31 Jul 2023, 13:50 Reply Quote 0
                        • A Offline
                          arubislander @carbonated
                          last edited by arubislander 31 Jul 2023, 13:50

                          @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 31 Jul 2023, 20:29 Reply Quote 0
                          • D Online
                            Dunbrokin @arubislander
                            last edited by 31 Jul 2023, 20:29

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

                            A 1 Reply Last reply 1 Aug 2023, 06:23 Reply Quote 0
                            • A Offline
                              arubislander @Dunbrokin
                              last edited by 1 Aug 2023, 06:23

                              @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
                              10 out of 13
                              • First post
                                10/13
                                Last post