[OTA-1/OTA-2 RC] Clock resets after reboot
-
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).
-
@carbonated I had it on my OP6 but the latest update fixed it.
-
@Dunbrokin I am still having the same issue. What channel is this?
-
This is on the latest RC after a reboot. -
@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!
-
@Dunbrokin that's alright, thanks for helping confirm this issue.
-
@carbonated Problem still persists after the recent update to 440.
-
@Dunbrokin Still present in OTA-2
-
@carbonated Is there an issue about this in the issue tracker on Gitlab / Github?
-
-
@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. -
@arubislander Thanks for that tip.....could you give us the link please and we can post it there.
-
@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.
