android.os.DeadObjectException: This exception has no message.


Samebug tips

This might be caused by an overload on your system or maybe your remote devices having failures. Do check your hardware as well for problems. Check the trace for devices resetting.


8 months ago
Expert tip

This is a test tip.


Solutions on the web

Solution icon of github
via GitHub by be-neth
, 8 months ago
This exception has no message.

Solution icon of coderanch
via Coderanch by simone giusti, 9 months ago
This exception has no message.

Solution icon of bugzilla
via Xamarin Bugzilla by miha, 1 year ago
This exception has no message.

Solution icon of github
via GitHub by gotama
, 1 year ago
This exception has no message.

Solution icon of github
via GitHub by vanitasvitae
, 10 months ago
This exception has no message.

Solution icon of github
via GitHub by vanitasvitae
, 1 year ago
This exception has no message.

Solution icon of github
via GitHub by Equisetum
, 6 months ago
This exception has no message.

Solution icon of github
via GitHub by ashimokawa
, 1 year ago
This exception has no message.

Solution icon of github
via GitHub by hamorphis
, 1 year ago
This exception has no message.

Solution icon of github
via GitHub by hypery2k
, 7 months ago
This exception has no message.

Stack trace

android.os.DeadObjectException
	at android.os.BinderProxy.transactNative(Native Method)
	at android.os.BinderProxy.transact(Binder.java:615)
	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:428)
	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:278)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Schedul$dThreadPoolExecutor.java:273)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1133)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:607)
	at java.lang.Thread.run(Thread.java:761)

Write tip

You have a different solution? A short tip here would help you and many other users who saw this issue last week.

Users with the same issue

57 times, 1 month ago
Once, 1 month ago
Once, 4 months ago
Once, 8 months ago
Once, 9 months ago
124 more bugmates