ticksDelta is extremely unstable
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 287
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
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?
Contributor guide
No contributing guide indexed for this repository
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.
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.
Assessment
- Tech stack
- kotlin
- Domain
- mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100