android.os.DeadObjectException: This exception has no message.
Searched on Google with the first line of a JAVA stack trace?
We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.
Recommended solutions based on your search
Samebug tips
- Expert tip
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.
This is a test tip.
Solutions on the web
via GitHub by dknaan
, 2 years agovia GitHub by bigbighill
, 1 year agovia GitHub by bigbighill
, 1 year agovia JIRA by Joni, 1 year ago
via Stack Overflow by Manuel
, 1 year agoandroid.os.DeadObjectException:
at android.os.BinderProxy.transactNative(Native Method)
at android.os.BinderProxy.transact(Binder.java:496)
at android.app.ActivityManagerProxy.handleApplicationCrash(ActivityManagerNative.java:5005)
at com.android.internal.os.RuntimeInit$UncaughtHandler.uncaughtException(RuntimeInit.java:95)
at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:693)
at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:690)