Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incorrect activity time (time missing) #440

Closed
fdawans opened this issue Jun 12, 2020 · 3 comments
Closed

Incorrect activity time (time missing) #440

fdawans opened this issue Jun 12, 2020 · 3 comments

Comments

@fdawans
Copy link

fdawans commented Jun 12, 2020

I am using AW 0.9.0 on Android 10 and the activity time reported in the app is much much lower than the actual time. The app is reporting 30 minutes but it should be a few hours.
Any help?
Thank you.

@ErikBjare
Copy link
Member

ErikBjare commented Jun 12, 2020

This might be a known bug.

ActivityWatch should regularly wake your phone (once every 24h/1h, not sure) to sync the time spent, but if it was a while since that job ran then you may not see the data for the entire day yet.

If you open the Activity view, wait for 30s, and then click the refresh button, does the total time increase? If so, that would indicate that your missing activity is still being loaded into ActivityWatch in the background.

This happens most of the time that I open the app. Although the data is never older than last night, so it appears the job runs at least daily (on my phone, likely affected by power settings of your Android ROM).

Fixes could be to:

  • Speed up the job that creates heartbeats from the Android API (pre-merge heartbeats, for example).
  • Make sure the job has completed before showing the Activity view.
  • Indicate the data is stale/being updated on the Activity view.

@fdawans
Copy link
Author

fdawans commented Jun 16, 2020

Yes, time is increasing but I guess it stops recording a few times a day. Recorded time is roughly equal to only half of my total screen on time.

@ErikBjare
Copy link
Member

This should be (mostly) fixed by ActivityWatch/aw-android#40 which will be included in the next release.

Closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants