warning in logcat: DeadObjectException
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 221
- PR merge metrics
- No merged PRs in 30d
Description
device: gts28vewifi
operating system: lineageos 15.1
newest microg version,
lineageos from download.lineage.microg.org
logcat:
android.os.DeadObjectException
at android.os.BinderProxy.transactNative(Native Method)
at android.os.BinderProxy.transact(Binder.java:764)
at org.microg.nlp.api.LocationBackend$Stub$Proxy.update(LocationBackend.java:157)
at org.microg.nlp.location.BackendHelper.update(BackendHelper.java:71)
at org.microg.nlp.location.BackendFuser.update(BackendFuser.java:83)
at org.microg.nlp.location.ThreadHelper.run(ThreadHelper.java:73)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:457)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:307)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:302)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
at java.lang.Thread.run(Thread.java:764)
This warning is flooding my logcat.
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 with the supplied logcat trace, focusing on org.microg.nlp.api.LocationBackend and the BackendHelper, BackendFuser, and ThreadHelper call path. Reproduce the warning on the listed gts28vewifi device and LineageOS 15.1 setup, then determine the cause of the repeated DeadObjectException and verify that the logcat flooding is resolved.
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
- 25/100