Thanks to my checkmk monitoring I've nearly managed to catch the smartremote Android app in the act of quitting on the remote. Relevant snippets of myServer and Android debug logs attached. I can see a fatal exception in the Android debug log at roughly the right time it happened but don't know enough about Android or the smartremote app to interpret what's going on. Hopefully
@David Li or
@davep might have a better idea. And no, it doesn't look like the myServer server rebooted or process restarted to cause this.
The timeline goes like this (all on 8th Dec, times GMT):
10:57:14.808 Fatal exception in Android debug log on remote
10:58:08.58 smartremote Android device logged as offline by myServer
11:00:25.00 smartremote Android device logged as disconnected by myServer
11:xx:xx:xx I picked the remote up off the cradle, the screen lit up showing the Android desktop with the smartremote app icon
11:xx:xx:xx I put the remote back down on the cradle
without restarting the smartremote app
11:05:51.05 smartremote Android device logged as reconnected by myServer
11:xx:xx:xx I picked the remote up again and it's back running the smartremote app
So maybe there's something in the logs that will give a clue as to what's going on.
Note there are lots of other crash reports in the Android debug log - I've included a large chunk in case it's helpful.
Andrew