Crash on launching main activity after non-focused disconnect

1. Connect QuasselDroid to core with remote disconnect feature
2. Connect to core with Quassel desktop client that has remote disconnect feature
3. Put QuasselDroid in background
4. Remotely disconnect QuasselDroid using Quassel desktop
5. Launch/resume the QuasselDroid activity

Alternatively, disconnect using QuasselDroid's connected notification's Disconnect action.

Expected

Account choosing screen shows, no crash.

Actual

Account choosing screen shows, immediately followed by crash and hang.

Additional

This only happens sometimes, I'm not yet sure why. I've attached crash reports from a remote disconnect and from a notification disconnect.

After every recent crash, QuasselDroid appears to hang instead of restarting. Not sure if this is intentional.

v0.4.0-68-g66d7e558_-_crash_after_remote_disconnect.txt

v0.4.0-72-ga60f920a_-_crash_after_disconnect_from_notification.txt