Comment for /branches/2.0/imsdroid/src/org/doubango/imsdroid/NativeService.java
- Dominant language
- Java
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
```
Dear developers, this is not a patch, but simply a comment. I was wondering why
the wakelocks in this NativeService is hold for very short time (10 ms)? Is it
enough to keep device awake for the needed computation here? Thanks.
```
Original issue reported on code.google.com by `yepang...@gmail.com` on 18 Jul 2014 at 8:48
Attachments:
- [NativeService.java.patch](https://storage.googleapis.com/google-code-attachments/imsdroid/issue-527/comment-0/NativeService.java.patch)
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading /branches/2.0/imsdroid/src/org/doubango/imsdroid/NativeService.java and locating the wakelock handling. Consult the Android power-management behavior relevant to the 10 ms duration; the issue is not actionable until the required computation window and expected change are clarified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100