ticksDelta is extremely unstable
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- kotlin
- Domain
- mobile-dev
Research direction
No file, test, or entry point is named in the report. Start by tracing the Android sync path that emits the shown ticksDelta and determine whether the differing values are expected Android clock behavior or a Kronos defect; done means a reproducible diagnosis and a clearly documented fix or explanation.
Written by the indexing model from the issue text.
Description
Hey, I started using Kronos a few days ago. May I have few questions regarding time sync/drifting on android?
The time seems to be complately unstable, almost each sync process ends with different diff
2020-05-01 01:49:16.804 6818-6928/Application$onCr: [kronos][sync] success sync ticksDelta[-118] responseTimeMs[222]
2020-05-01 01:50:16.934 6818-6928/Application$onCr: [kronos][sync] success sync ticksDelta[-151] responseTimeMs[129]
2020-05-01 01:50:16.994 6818-6928/Application$onCr: [kronos][sync] success sync ticksDelta[-128] responseTimeMs[56]
The calls are a minute apart from each other but the responses say that the device clock drifted 20milliseconds
Is it standard behavior of Android or am I doing something wrong?
- Dominant language
- Kotlin
- Stars
- 287
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from lyft/Kronos-Android
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
lyft/Kronos-Android#67 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
lyft/Kronos-Android#66 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
lyft/Kronos-Android#65 ·
-
Wrong TimeOpen
Difficulty 4/5 3-5 days Newbie friendliness 25/100
lyft/Kronos-Android#62 ·
-
getCurrentTimeMs() return the wrong date time everytime I manually change the device clockPossibly taken @Rajin9601 claimed this 1696 days ago. Open
Difficulty 4/5 3-5 days Newbie friendliness 25/100
lyft/Kronos-Android#61 · 10 comments · 2 reactions ·
All issues in lyft/Kronos-Android
Similar issues
-
Raijin Scans (FR)OpenBug Domain changed
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
keiyoushi/extensions-source#19644 · 1 reaction ·
Maintainers usually reply within 1 day
-
node: disconnection push notification is logged as "Unknown notification" instead of the disconnect warningPossibly taken @datatrigger claimed this today. Openbug 🐞 Untriaged user issue
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
valkey-io/valkey-glide#7278 ·
Maintainers usually reply within 2 days
-
design
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement triaged
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 3 days
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
mobile-dev-inc/Maestro#3659 · 1 comment ·
Maintainers usually reply within 1 day