lyft / lyft/Kronos-Android

Wrong Time

Open
#62 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Kotlin
Stars
287
Forks
17
PR merge metrics
No merged PRs in 30d

Description

Some times the clock gives wrong time in andorid
While the time in device is correct

as on 17 Dec the device and NTP server time are correct
but koronos clock gives the time of 12 dec 21.

On restarting the device the clock starts giving correct timing.
Is there something need to be hit on error or something is forgetted by me

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No file, test, or entry point is named. Start by reproducing the Android clock discrepancy while comparing device time, NTP time, and Kronos output, then inspect the time-synchronization and error-handling paths. Done means identifying the cause and adding a regression test that prevents the stale-time result.

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.