markzhai / markzhai/AndroidPerformanceMonitor
add append mode to avoid conflicted getMainLooper().setMessageLogging()
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Java
- Stars
- 6.7k
- Forks
- 1k
- PR merge metrics
- No merged PRs in 30d
Description
Currently BlockCanary directly calls getMainLooper().setMessageLogging() to do monitor, which may conflicts with the original logging set by app, we can add a append mode for those situation.
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 current BlockCanary call to getMainLooper().setMessageLogging() and review the surrounding monitor setup. The change is complete when an append mode preserves an app's existing message logging while still allowing BlockCanary to monitor the main looper.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- mobile, performance
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100