Nick's MCE 59 Posted July 29, 2016 Share Posted July 29, 2016 Hi Just noticed a problem on my roku's. I am unable to launch and keep getting the error "FAILED TO POST CAPABILITIES". I have 2 roku's and they both have the same problem. Any help appreciated. Nick Link to comment Share on other sites More sharing options...
CBers 6766 Posted July 29, 2016 Share Posted July 29, 2016 Remove and re-add the channel? Link to comment Share on other sites More sharing options...
Nick's MCE 59 Posted July 29, 2016 Author Share Posted July 29, 2016 How do I remove blue neon, it doesn't come up in the channel search. Link to comment Share on other sites More sharing options...
CBers 6766 Posted July 29, 2016 Share Posted July 29, 2016 From your Roku home screen, highlight the channel, press * and Remove Channel. Link to comment Share on other sites More sharing options...
speechles 1917 Posted August 2, 2016 Share Posted August 2, 2016 Hi Just noticed a problem on my roku's. I am unable to launch and keep getting the error "FAILED TO POST CAPABILITIES". I have 2 roku's and they both have the same problem. Any help appreciated. Nick Is this still an issue? Sent from my Nexus 7 using Tapatalk Link to comment Share on other sites More sharing options...
vaise 304 Posted August 7, 2016 Share Posted August 7, 2016 I get this, just click OK and it is running as normal then. Seems to be random, over all 6 Roku's. Link to comment Share on other sites More sharing options...
speechles 1917 Posted August 9, 2016 Share Posted August 9, 2016 (edited) When it happens, are you changing the play method? From auto to force, and back occasionally? That error means the roku wasnt able to tell the server its new capabilities. As you modify from auto detection to another play method the roku has to tell the server what it can then play, and how. Usually an app only has to report capabilities once when it starts. Because of how this app works when changing the play method it reports to the server the changed capabilities. When you see this error, it should be fine, but it might cause transcoding when it shouldnt and try to direct play when it shouldnt. Everytime you change the play method it has to inform the server of its new capabilities. You can also press the back button on your remote when seeing dialog errors, rather than use the ok button on the dialog. Pressing the ok makes the app move forward, with some errors this may make the app try again. Pressing back moves the app backward to the last place it was before the error, it does not try again. Sent from my Nexus 7 using Tapatalk Edited August 9, 2016 by speechles Link to comment Share on other sites More sharing options...
mattyg8 18 Posted March 6, 2018 Share Posted March 6, 2018 I get this issue on one of mine and tried for ages to fix Link to comment Share on other sites More sharing options...
Luke 37008 Posted March 7, 2018 Share Posted March 7, 2018 So this only happens with the blue neon app, the emby app, or both? Link to comment Share on other sites More sharing options...
speechles 1917 Posted March 7, 2018 Share Posted March 7, 2018 (edited) So this only happens with the blue neon app, the emby app, or both? It's just with blue neon. Because of how it allows users to change play method. Every time that is done forces a change of capabilities so the server can understand what the app is trying to do. When that error happens the person needs to clear their devices list on the server of any devices which use blue neon and then use the "clear registry" button when selecting a user in the blue neon app. This will reset both the server and app into using the correct device name. The server will recreate these devices. There is no need to worry anything will be lost. I made a small change during a short period to how the device name was stored. Any devices which stored the authentication for devices during that short period will be the ones reporting the problem. It should be a very small subset of users. So low it might be only 1 or 2. There should not be a need to worry this carried over into the official app. Edited March 7, 2018 by speechles Link to comment Share on other sites More sharing options...
mattyg8 18 Posted March 7, 2018 Share Posted March 7, 2018 It's just with blue neon. Because of how it allows users to change play method. Every time that is done forces a change of capabilities so the server can understand what the app is trying to do. When that error happens the person needs to clear their devices list on the server of any devices which use blue neon and then use the "clear registry" button when selecting a user in the blue neon app. This will reset both the server and app into using the correct device name. The server will recreate these devices. There is no need to worry anything will be lost. I made a small change during a short period to how the device name was stored. Any devices which stored the authentication for devices during that short period will be the ones reporting the problem. It should be a very small subset of users. So low it might be only 1 or 2. There should not be a need to worry this carried over into the official app. I am using the blue neon theme as I have a 2 Telstra Tv devices and can only side load, How do I go about clearing the device list on the server. Link to comment Share on other sites More sharing options...
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