This exception has no message.

Samebug tips1

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.

Don't give up yet. Our experts can help. Paste your full stack trace to get a solution.

Solutions on the web635

  • via GitHub by iaros
    , 3 months ago
    This exception has no message.
  • via GitHub by gotama
    , 1 year ago
    This exception has no message.
  • via GitHub by vanitasvitae
    , 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( at android.hardware.display.IDisplayManager$Stub$Proxy.getDisplayInfo( at android.hardware.display.DisplayManagerGlobal.getDisplayInfo( at android.view.Display.updateDisplayInfoLocked( at android.view.Display.getState( at android.view.ViewRootImpl.setView( at android.view.WindowManagerGlobal.addView( at android.view.WindowManagerImpl.addView( at at at at at at at

    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

    Unknown user
    Once, 1 year ago
    50 times, 2 days ago
    3 times, 2 days ago
    Once, 3 days ago
    2 times, 1 week ago
    114 more bugmates