Jump to content

Emby is freezing on Insignia Roku TV


StrangledSyntax

Recommended Posts

StrangledSyntax

Hi -

 

I'm having difficulties getting the Emby app working on my kids Insignia Roku TV. I have installed the channel and can view my library, but when I select some media to play, the app freezes. The only way to recover is to disconnect the power plug and restart the TV. Could someone please assist?

 

Emby Server Version 3.0.5934.0

 

Insignia Roku TV

SV 7.1.0

Build 4055

 

Thanks

Link to comment
Share on other sites

That is odd.

 

As a test...

 

Can you try this app: https://my.roku.com/account/add?channel=EmbyBlueNeon

 

This is a fork of the official client. More about it below:

http://emby.media/community/index.php?/topic/24151-theme-blue-neon-night/

 

Does this app behave the same way?

 

 

Sent from my Nexus 7 using Tapatalk

Edited by speechles
Link to comment
Share on other sites

StrangledSyntax

Okay, I removed the official app and installed your forked version. Still the same thing. I can login to my server and browse the library, but the app just freezes. The only way to exit is to disconnect it from the power source. It seems to get hung up after going into the "Kids Movies" section in my library, as the quick movie summary stays the same, no matter which movie I am actively over. 

Link to comment
Share on other sites

Can you provide a photo of the screen when it locks up? This way we know where to start looking. Also when you say "quick movie summary" do you mean you click into the movie from the row of movies listed? Does the web client, and other apps work correctly? We are using some legacy methods to detect capabilities, and if newer firmware is found it uses a different method. This is in regards to audio. I am suspecting the problem is coming from a combination of appMain.brs and capabilities.brs but need these few answers from you until I can confirm.

 

Sent from my Nexus 7 using Tapatalk

Link to comment
Share on other sites

StrangledSyntax

Here is two images. All other apps are working correctly. As far as the "movie summary", I'm referring to the short summary that is shown below the poster view when scrolling through the movies. The bottom image shows the movie "A Bugs Life" with the summary still stuck on "Aristocats".  

 

*Update: Seems to be something with just this folder, as I tested with my "TV Shows" and "Movies" folder and there is no issue.

 

5740bca30b71e_IMG_2873.jpg5740bcc47efb2_IMG_2874.jpg

Edited by StrangledSyntax
Link to comment
Share on other sites

  • 2 weeks later...
StrangledSyntax

Could someone please take a look at this and guide me as to what is wrong?

Edited by StrangledSyntax
  • Like 1
Link to comment
Share on other sites

Okay.. the server log you posted shows everything should be okay there. It is the roku app which is freezing. This freezing is caused by the app soft crashing. The brightscript interpreter crashed.

 

http://inessential.com/2014/05/13/hard_and_soft_crashes

 

Soft crashes are harder to diagnose and need help from the person experiencing them. In order to help you your roku TV must be in developer mode. I am assuming your roku TV is still at 192.168.1.4 as per your server logs.

 

Go to the roku homescreen which shows all the roku apps, while on this screen use the following sequence on your remote.

Press Home 3x, Up 2x, Right, Left, Right, Left, Right

 

If done correctly you shall wind up at a developer prompt asking for a password and wanting to restart your TV. Fill this in, and let it restart. Once it has fully restarted do what is show below.

 

Once restarted, go to a computer, tablet, or phone and browse to this address: http://192.168.1.4

 

It will ask for a login, use rokudev, and a password you chose on the earlier screen when you enabled developer mode. Enter these and you wind up at the roku developer dashboard.

 

Now in a new tab, or new browser window visit this url:

http://192.168.1.4:8085

 

Nothing will show in that new tab/window..yet..

 

Now go back to the TV choose the blue neon emby app. Now look at the browser window that was empty on your computer/tablet/phone. It will be outputting text. Now use the roku app on your TV until you see in the browser window the app has crashed. You will be able to tell when that happens.

 

Now what we need to see is copies of that. You can choose "save" to capture the browser window and it should save all the text too that has been displayed. This is the text file log we need to see to help you. Some command isnt working on rokuTV the same way it does on every other roku. I can immediately solve the issue once I see the text file log which has dumped from your rokuTV during the crash.

 

Sent from my Nexus 7 using Tapatalk

Edited by speechles
  • Like 2
Link to comment
Share on other sites

There are also some slow responses in the server log. Not super slow, but maybe they're playing a role here. You could try the beta server and see if that helps.

Link to comment
Share on other sites

There are also some slow responses in the server log. Not super slow, but maybe they're playing a role here. You could try the beta server and see if that helps.

That might help speed up the (slow) but the app may still crash. If those slow responses were causing an issue I have it spawn a dialog there was a response error and that the response has no metadata. I added error dialogs to several spots to make users aware when the link between server and app starts to break. Then after this dialog is closed the app may work unpredictably with the lack of server responses but the user would know this. Ive also doubled most of the timeouts to twice their wait times. This increased timeout has helped make the app more resilent to slow responses.

 

Sent from my Nexus 7 using Tapatalk

Edited by speechles
  • Like 1
Link to comment
Share on other sites

StrangledSyntax

Okay, @@speechles I followed your directions, but when I try and bring up the address you gave me I get:

  This site can’t be reached

192.168.1.4 took too long to respond.

 

 

 

 

 

Should I be going to the address shown in the below picture?

57534a8a444ba_IMG_29051.jpg

Link to comment
Share on other sites

Okay, @@speechles I followed your directions, but when I try and bring up the address you gave me I get: This site can’t be reached

192.168.1.4 took too long to respond.

 

 

 

Should I be going to the address shown in the below picture?

57534a8a444ba_IMG_29051.jpg

Did you enable developer mode on your roku TV first. You must enabke that on the roku via the installer, yes. After this you set a password and the TV rebooted?

 

Edit: it seems yes, your router assigned it a new IP. The address shown there is required. If you repeat the steps to open the developer dashboard after this the 8085 port will spew text.

Edited by speechles
Link to comment
Share on other sites

Yes

Yeah my bad, you need to use the IP that rokuTV is using. Your picture hadnt loaded yet for me. Now that I see it yes. You are thinking the right idea.

 

I am await the debug from you. :)

Link to comment
Share on other sites

To get debug, you must upload your own developer zip. The will make another blue neon app on your homescreen. You can tell them apart, one ends with (dev).Thats the one you want to use for this.

 

http://ereader.kiczek.com/emby-roku-blueneonnight.zip

 

This is the zip install identical to that on roku store. Use the 192.168.1.12 address and use the installer to install the above zip. Now the debug window @ 192.168.1.12:8085 will work in a browser window. If it doesnt close the browser and try again.

 

Let me know if you have any issues doing any of these steps. Your help here will help every other user of that TV model. Not every member has bravery to attempt all that is required to get debug to work. I am hopeful you are. There is no harm doing this and it is simple to remove developer mode after if you wish.

Edited by speechles
Link to comment
Share on other sites

StrangledSyntax

Attached is the log. I put it in notepad, as the screen cap wouldn't capture it all. Hopefully this is ok. I tried playing the movie "Frozen"  ;) ....

I could navigate to it, but once I hit the "ok" button it doesn't do anything. I can continue to navigate through the movies, but can't go back to the main emby screen or get back to the roku home screen. Thanks for your help again. Let me know if I need to upload into a different file format.

 

blue_neon_dev_log_strangledsyntax.txt

Link to comment
Share on other sites

Attached is the log. I put it in notepad, as the screen cap wouldn't capture it all. Hopefully this is ok. I tried playing the movie "Frozen"  ;) ....

I could navigate to it, but once I hit the "ok" button it doesn't do anything. I can continue to navigate through the movies, but can't go back to the main emby screen or get back to the roku home screen. Thanks for your help again. Let me know if I need to upload into a different file format.

 

 

MediaPlayer::playVideo::VideoScreenEvent::isPlaybackPosition: set progress -> 333

Skipping progress report

MediaPlayer::playVideo::VideoScreenEvent::isPaused: position -> 333

Skipping progress report

MediaPlayer::playVideo::VideoScreenEvent::isPartialResult: position -> 333

MediaPlayer::playVideo::VideoScreenEvent::isScreenClosed: position -> 333

 

Your log starts in the middle of playback. It shows playback was paused and then stopped by the screen closing. Then after this it looks like you browsed to the detail screen and it lost focus of which screen it was supposed to be on. Almost like the home button was pressed. Then the app starts again like you re-entered it. I can't see a real issue in that log. Is it not playing the video when it thinks it is? Does the videoplayer window spawn at all?

 

Also you dont have to screenshot it that is the hard way. Use the "save page as" in the browser you are using. The log you provided doesn't actually show any errors. If you can provide a full one from app start to the crash I can see what exactly is going on.

Edited by speechles
Link to comment
Share on other sites

StrangledSyntax

Tried this again this morning....

 

Launched the app, went into the "kids movies", navigated to the movie "UP" and hit OK on the remote. I would guess it took 7-10 minutes until the play option showed. Then I hit play, it started to play, but after a few seconds it kicked me back out. Logs are attached. 

192.198.1.12.txt

Log.txt

Link to comment
Share on other sites

 

MediaPlayer::playVideo::VideoScreenEvent::isRequestFailed - message = An unexpected problem (but not server timeout or HTTP error) has been detected.
MediaPlayer::playVideo::VideoScreenEvent::isRequestFailed - data = 0
MediaPlayer::playVideo::VideoScreenEvent::isRequestFailed - index = -3
MediaPlayer::playVideo::VideoScreenEvent::isScreenClosed: position -> 3

 

This is what the roku app shows. Unfortunately, this isn't the app having an issue. This is the roku itself saying "An unexpected problem (but not server timeout or HTTP error) has been detected.".

 

 

2016-06-05 07:27:33.5933 Error App: Error in Nfo
    *** Error Report ***
    Version: 3.0.5972.0
    Command line: C:\Users\HTPC\AppData\Roaming\Emby-Server\System\MediaBrowser.ServerApplication.exe
    Operating system: Microsoft Windows NT 6.1.7601 Service Pack 1
    Processor count: 4
    64-Bit OS: True
    64-Bit Process: True
    Program data path: C:\Users\HTPC\AppData\Roaming\Emby-Server
    Application Path: C:\Users\HTPC\AppData\Roaming\Emby-Server\System\MediaBrowser.ServerApplication.exe
    Data at the root level is invalid. Line 1, position 1.
    System.Xml.XmlException
       at System.Xml.XmlTextReaderImpl.Throw(Exception e)
       at System.Xml.XmlTextReaderImpl.ParseRootLevelWhitespace()
       at System.Xml.XmlTextReaderImpl.ParseDocumentContent()
       at System.Xml.XmlReader.MoveToContent()
       at MediaBrowser.XbmcMetadata.Parsers.BaseNfoParser`1.Fetch(MetadataResult`1 item, String metadataFile, XmlReaderSettings settings, CancellationToken cancellationToken)
       at MediaBrowser.XbmcMetadata.Parsers.BaseNfoParser`1.Fetch(MetadataResult`1 item, String metadataFile, CancellationToken cancellationToken)
       at MediaBrowser.XbmcMetadata.Providers.EpisodeNfoProvider.Fetch(MetadataResult`1 result, String path, CancellationToken cancellationToken)
       at MediaBrowser.XbmcMetadata.Providers.BaseNfoProvider`1.<GetMetadata>d__0.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
       at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
       at MediaBrowser.Providers.Manager.MetadataService`2.<RefreshWithProviders>d__50.MoveNext()
  

 

The server shows possible an nfo/xml is incorrect.

 

 

But more importantly, is your insignia roku TV setup to allow 1080p? If so, it likely is the bad nfo/xml info for the file causing the issue. Somewhere emby is having problems. @@Luke can you look over his logs and see an issue?

 

Why are you using the folders row to access "Kids Movies" and not just directly choosing "Kids Movies" from the view. You need to enable the use enhanced views for movie, tv, and music in the server when logged in as your users.

Link to comment
Share on other sites

i did already give a suggestion

<3

 

Haw... it isnt the roku app indeed.

 

@@StrangledSyntax you need to update your server to the beta and see if this solves the issue.

 

Sent from my Nexus 7 using Tapatalk

Link to comment
Share on other sites

If the beta server does not solve this for you Ive seen others having similar issue with playback solved it. They factory reset their rokuTV and let it redownload firmwares in the software update that occurs when the TV reboots after restoring. This doesnt lose all your installed applications. These will be redownloaded automatically during its initial software update. It does reset all the preferences in your apps.This will also remove developer access, and your development application. To debug again you have to enter the developer screen code, run the installer...etc all over again.

 

Keep us informed how this goes.

 

Sent from my Nexus 7 using Tapatalk

Edited by speechles
Link to comment
Share on other sites

StrangledSyntax

Well I updated to the beta server  as per @@Luke and I am still suffering from the same issues...

 

@@speechles, the tv can output 1080p. I fixed the issue with the views, but don't see why that would cause a problem.

 

I will try the factory reset and test it again...

Link to comment
Share on other sites

@@speechles, the tv can output 1080p. I fixed the issue with the views, but don't see why that would cause a problem.

 

I will try the factory reset and test it again...

Using "views" is just a prettier way to access the library. This will give you multiple rows of items and you can see more things to do from the one screen. Using "folders" will simply give you an item row, and a favorite item row. This is why I suggested it. Just so you could experience the app in the best way possible.

 

The factory reset hopefully solves it. After the reset, and software update make sure to manually choose software update again. This way you can verify for yourself it says no further updates are available.

 

 

Sent from my Nexus 7 using Tapatalk

Edited by speechles
Link to comment
Share on other sites

StrangledSyntax

The factory reset hopefully solves it. After the reset, and software update make sure to manually choose software update again. This way you can verify for yourself it says no further updates are available.

 

 

Well, I'm about to give up fellas...

 

Factory reset the TV. First just audio and video settings, with no change, and then a full factory reset. Same thing happens as I've been reporting. Everything is unreasonably slow to respond. Takes minutes to respond to just one click on the remote. This is the only device in my network that has issues pulling media from the server. I really appreciate all the help and time spent trying to get this going. But, I don't really know what else to do.

Link to comment
Share on other sites

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...