Getting "kicked out" of emby rather than a reboot means the brightscript crashed out to the debugger. It can be a soft-crash, like a type-mismatch or similar, which makes the client unusable, but stays inside the screen stack. Or a hard-crash using screen component calls which takes down the screen-stack and crashes you back to the homescreen. The error usually means a timeout (network issue) has occured, and metadata required for a screen to be created is missing. This is why re-enter the app, and play same video from the resume point works. This is the only way I can reproduce it. A firmware crash reboots the entire device.
It is a known issue if you "flip through" the toggle very quickly for movies, from latest, to jump-in, to resume, to genre, to suggested, to etc.. Unless you wait for the "suggested" row to populate before you change the row to a new view it will hard-crash the client. The suggested row has a 2nd toggle, the "reference movie" ("Because you watched"/"Because you liked") which when clicked cycles to the next suggestion. This difference causes the crash.
The post below mine is about fixing a firmware crash reboot. Anyone on firmware v7.0 build 9044 should no longer see these reboot issues.
Edited by speechles, 29 December 2015 - 07:59 PM.