Countly / Countly/countly-sdk-android
The duration statistics of Activity usage are incorrect.
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 696
- Forks
- 290
- Avg merge
- 9h 15m
- Merged PRs (30d)
- 8
Description
Translate the following sentence into English: "Activity usage duration statistics are performed in onStart and onStop. However, the statistics are incorrect when the Activity switches rapidly. For example, from activityA to activityB, then quickly back to activityA. This scenario can also lead to incorrect determination of foreground and background switches."
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
Start by tracing the Android Activity onStart and onStop handling and reproduce rapid switches from activityA to activityB and back. Done means duration statistics and foreground/background switch detection remain correct during rapid Activity changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- analytics, mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100