mjktg99 35 Posted December 22, 2015 Posted December 22, 2015 (edited) Hello, Has this issue been resolved with a emby server update or is it all related to the roku firmware? I have a lot of friends with roku's who have reported crashing as well, I hope this is an easy fix. Thanks Both, the server was updated with a fix and Roku released a fix in their latest build. Luke did mention a concern of the fix from Roku breaking his fix in the server but at this point, it doesn't seem to have done that. Edited December 22, 2015 by mjktg99 1
christhetower 1 Posted December 25, 2015 Posted December 25, 2015 my server is up to date Version 3.0.5781.8 but my roku is still rebooting after tryimg to play any movies over 2 hours long. Do i have to do anything to make the fix work for me?
ITMonkey 1 Posted December 25, 2015 Posted December 25, 2015 (edited) @@christhetower have you updated to the latest Roku firmware? That seems to have fixed it. Edited December 25, 2015 by ITMonkey 1
Luke 42077 Posted December 28, 2015 Posted December 28, 2015 Well done guys. Thanks for helping investigate this.
footose 2 Posted December 29, 2015 Posted December 29, 2015 Anyone else sometimes get "kicked out" of emby (not a reboot) and then you can go back in and can play the movie after selecting it a second time?
Happy2Play 9780 Posted December 29, 2015 Posted December 29, 2015 Anyone else sometimes get "kicked out" of emby (not a reboot) and then you can go back in and can play the movie after selecting it a second time? Helps to know server and channel version numbers. But no haven't had that issue yet.
speechles 2055 Posted December 29, 2015 Posted December 29, 2015 (edited) @@footose 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 December 29, 2015 by speechles
ohara124 0 Posted December 29, 2015 Posted December 29, 2015 Roku has a new update V7 build 9044. All movies that used to cause a firmware reboot now play with roku EMBY app v2.1 build 7. Have not tried build 5. Running lateset server.
Luke 42077 Posted January 11, 2017 Posted January 11, 2017 If you'd like to try a preview of the new Roku app you can do so here: https://emby.media/community/index.php?/topic/43616-new-emby-for-roku-public-preview-beta Please make sure to read the disclaimers. Thanks and enjoy !
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now