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

android.os.DeadObjectException:
at android.os.BinderProxy.transactNative(Native Method)
at android.os.BinderProxy.transact(Binder.java:527)
at com.android.server.wm.WindowAnimator.updateWindowsLocked(WindowAnimator.java:288)
at com.android.server.wm.WindowAnimator.animateLocked(WindowAnimator.java:688)
at com.android.server.wm.WindowAnimator.access$000(WindowAnimator.java:54)
at android.view.Choreographer$CallbackRecord.run(Choreographer.java:856)
at android.view.Choreographer.doCallbacks(Choreographer.java:670)
at android.view.Choreographer.doFrame(Choreographer.java:603)
at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:844)
at android.os.Handler.handleCallback(Handler.java:739)
at android.os.Handler.dispatchMessage(Handler.java:95)
at android.os.Looper.loop(Looper.java:152)
at android.os.HandlerThread.run(HandlerThread.java:61)
at com.android.server.ServiceThread.run(ServiceThread.java:46)

Users with the same issue

7 times, 1 year ago
28 times, 10 months ago
106 times, 9 months ago
19 times, 1 year ago
Once, 1 year ago
119 more bugmates

Know the solutions? Share your knowledge to help other developers to debug faster.