Default tab lost and not resettable for all libraries.

[Gilgamesh_48 1240]

Roku - 4.1.22

I just noticed that on my Roku all my libraries are starting in "Suggestions" even though I have set the default to "Movies" or "Shows" Except for Photos where it defaults to "Folders"

I have reset each library to what I had before (Shows, Movies, Photos) but they reset as soon as i leave the library involved. 

I have restarted the Emby app, several times and I have restarted my Roku itself twice and I have restarted my server (Version 4.9.0.23 beta) twice.

To put it simply the default tab is always reset to whatever is the default as soon as 4.8.0.23 was installed this AM but the web app still handles the tabs correctly.

This is a matter of a couple of button presses each time I enter one of the libraries on my Roku. But it is a couple of button presses that I have not needed in the past.

Please fix!!!

Edit to add: I just tested and my Fire stick and my Shield TV both work correctly so this is a Roku bug.

Edited June 6, 2024 by Gilgamesh_48

[Luke 42077]

HI, we'll take a look at this. Thanks for reporting.

[Gilgamesh_48 1240]

12 hours ago, Luke said:

HI, we'll take a look at this. Thanks for reporting.

A little addition to the report. Before this bug reared up I would exit a library after setting things like choosing "favorites" or sort order or anything else selected from the menu on the far right of the screen and when I reentered that library the choices would be retained but now, with the bug, the choices are lost upon exit. 

I really think the failure is upon reentry not on the exit. It is like the settings are saved just fine but are never read upon entry.

I hope that was somewhat clear,  

[ebr 16169]

Nothing has changed in the app here.  This happened when you updated a server version?

[Gilgamesh_48 1240]

7 minutes ago, ebr said:

Nothing has changed in the app here.  This happened when you updated a server version?

Yes, but it does NOT happen on my Fire or Shield or in the web app. Something is VERY wrong on the Roku only. And it is on all three Rokus i have active right now.

I am on Version 4.9.0.23 beta for the server and the bug is 100% repeatable.

BTW: I have restarted everything on my network including my server and all clients and my router and all switches. Just in case i also restarted everything, like my Echos, and my cameras and every other device attached to my network. The symptom did not change at all. 

I do not see how the server could be the problem but in the world of electronics anything is possible.

BTW: MY Rokus just (within the last week) updated the Roku's OS software ver 13.0.o build 24062-29

I also just tested and the new "tile size" setting that allows the main Roku screen to show 4 tiles across instead of the normal 3 does not have any effect. I am running with that Roku setting set to "small" but it makes no difference.

This is a verifiable and repeatable bug. Please fix!!!

[speechles 2055]

@Gilgamesh_48See the same issue on Version 4.9.0.23 beta.

No matter what I set the default it doesn't stick. It will always land on suggestions when entering this library. We will get this fixed. Thanks for reporting. You rock!

 

Reference: Issue #1617: [TabView] Select Default tab is not remembering and winds up defaulting to the default

Edited June 6, 2024 by speechles

[Gilgamesh_48 1240]

7 minutes ago, speechles said:

@Gilgamesh_48See the same issue on Version 4.9.0.23 beta.

No matter what I set the default it doesn't stick. It will always land on suggestions when entering this library. We will get this fixed. Thanks for reporting. You rock!

 

Reference: Issue #1617: [TabView] Select Default tab is not remembering and winds up defaulting to the default

But, for me, the selection of a default library does work fine in the web app and on all my clients EXCEPT my Rokus. It is ONLY the Rokus that show any problem. 

How can this possibly be the server's fault???? I simply do not understand at all.

BTW: The link in your post ( Version 4.9.0.23 beta.) does not work to take me to anything except an error page.

Edited June 6, 2024 by Gilgamesh_48

[speechles 2055]

@Gilgamesh_48I can reproduce this inside the Roku app. Same issue. Should be able to trace back what the issue is and fix whatever is causing it. We will get this fixed.

The link in my post is an internal link generated by the dashboard when it shows the version.

[Gilgamesh_48 1240]

2 minutes ago, speechles said:

@Gilgamesh_48I can reproduce this inside the Roku app. Same issue. Should be able to trace back what the issue is and fix whatever is causing it. We will get this fixed.

The link in my post is an internal link generated by the dashboard when it shows the version.

Thanks. Sometimes i get the feeling from others that  they think I am lying even when I give exact symptoms and the exact method to reproduce. Once the problem gets verified the fix is usually forthcoming or at least there is verification that the problem is being worked on but, initially, I often get the feeling that i am not believed.

If you are using Chrome there is a feature that allows pasting as plain text. That is what I use to avoid pasting dead links. I am pretty sure other browsers also have a similar feature. Just as a suggestion you might want to post as plain text when what you copied contains a link that you don't want to include. I know you probably know that but I know I sometimes forget or forget to use things that I know. I can blame age but i doubt you are old enough to be experiencing "cognitive decline" that we all experience as we age past a certain point."

Thanks for assuring me that I am not, quite yet, insane.  But insanity is just a state of mind.  

[speechles 2055]

---- AA ----
Client: rokusg
CustomPrefs: unknown
Id: b5627eae3bb6b401b37713eabf616114
SortOrder: Ascending
------------

The prefs are coming back empty. Going to get together with the team and get to the bottom of this.. lol.

 

[Gilgamesh_48 1240]

On 6/6/2024 at 10:05 PM, speechles said:

---- AA ----
Client: rokusg
CustomPrefs: unknown
Id: b5627eae3bb6b401b37713eabf616114
SortOrder: Ascending
------------

The prefs are coming back empty. Going to get together with the team and get to the bottom of this.. lol.

 

I am wondering how long we should wait for this "inconvenience" to be reconciled? While it is not hideously bad it does impact me more than I thought it would.

Although it did not seem to matter much it turns out that I do run into it over and over when looking for something to watch late at night, or early morning.

I have my libraries arranged and sorted and tagged in ways that makes it easier for me to find things and now, whenever I enter a library, I have to resort and reselect what I want and do not want to show and to get things to display the way I like. It is not too time consuming but it is something that has to be done over every time I leave and reenter a library. Losing a few minutes on each entry is clumsy at best and upsetting at worst. 

I REALLY want this fixed and not become like the poor implementation with no alpha selection that exists in the web all for photos and just hang on for ever and ever and ever without any resolution even being promised even though the bug was reported a LONG time ago.

It is getting to seem a lot like Plex where they would would rather work on new or enhanced features than fix glaring bugs. 

I just want my preferences to stick through library entry, exit and reentry like it used to until the latest set of updates screwed things up.

It has been an excessively long time for the little bug to be fixed. Can we not just reissue the old Roku app that worked correctly until this ridiculous problem gets finally fixed?

I just want the simple interface to work like it did before. PLEASE FIX or ROLL BACK to an app that works, ASAP. 

[Luke 42077]

Hi, yes we are looking into it. Thanks for reporting.

[Gilgamesh_48 1240]

Just now, Luke said:

Hi, yes we are looking into it. Thanks for reporting.

I did NOT ask "if" I asked when. It turns out to be important to me.

[ebr 16169]

Hi.  This isn't an issue in the app.  Hopefully, the next server beta will fix it.

BTW it is only an issue with the beta server.

[Gilgamesh_48 1240]

5 minutes ago, ebr said:

Hi.  This isn't an issue in the app.  Hopefully, the next server beta will fix it.

BTW it is only an issue with the beta server.

It was not fixed in Version 4.9.0.24 beta that hit my system yesterday. So again the question becomes when?

I also wonder how it is not the app if all my other apps work fine. (Shield, Fire and web) I understand that it is possible that something "special" might need to be done for the Roku but it also seems quite sloppy to screwup parts on the server that only effect one app and then not fix it as soon as it is reported. It also seem sloppy that this bug was not caught in alpha testing. Don't you have any alpha testers using Roku?

Sorry for seeming picky but Roku can take a long time for updates to go through but a beta server update can happen quickly and so the fix should have been in .24.  

[ebr 16169]

3 minutes ago, Gilgamesh_48 said:

So again the question becomes when?

Whenever the next server beta is.

4 minutes ago, Gilgamesh_48 said:

I also wonder how it is not the app if all my other apps work fine.

The Android TV and Fire TV apps are also affected.

When running beta, these types of disruptions can occur.  Thanks for being a part of the test.

[Gilgamesh_48 1240]

3 minutes ago, ebr said:

Whenever the next server beta is.

The Android TV and Fire TV apps are also affected.

When running beta, these types of disruptions can occur.  Thanks for being a part of the test.

Actually that is very hard to believe when my Fire and Shield apps work fine. I do not understand the "why" at all. 
However the "why" no longer matters much to me. I just want/need this fixed so my sleep rituals are not so disrupted. I know I am making this too much about "me" but I am the one that is using my Roku at night and I find having to make all the extra presses very distracting.  

If I wanted the defaults i would not have changed my settings. Also why is it that the default tab is "suggestions"? That seems very stupid. I know my circle of acquaintances is small but I know absolutely no one that even uses "suggestions" for anything.  The default tab that makes the most sense is "movies" for a movie library and "shows" for TV libraries. Suggestions are just stupid!!!!!

[Detail4687 3]

To add,: the "show only unwatched" filter also doesn't stay select either. I

[Gilgamesh_48 1240]

I just wanted to follow up to say that I have successfully solved this issue, at least for now.

What I did was repurpose an older computer to run the release ver of Emby. I had a few problems until I realized that the video board in that computer had malfunctioned years ago and apparently failed in such a way as to kill the entire computer on an intermittent basis. I replaced that board (actually just removed it and I just use the on board video) and realized that I did not need hardware transcoding because all my videos direct play (or in a few cases direct stream)and I believe the access is fine. It is not perfect as it is a bit on the slow side but that only seems to matter much during the building process. That will end soon. I also, on my beta server, save everything with the media and the media for both servers is the same. That means that things like generating bif files are handled by the beta server and stored with the videos so the release server has them to use.

It was just a little involved but my release server really does very little and it then reads most info directly from the drive(s). 

It seems quite stable but i will not be sure everything is correct for a month or two but at least the "bug" is handled.

I do not think I will switch back to the beta even if this bug does get fixed as the release seems to work fine fine and does not have the intermittent bugs that crop up in the beta. I will only switch back if something unexpected happens or some feature shows up in the beta I can't live without.

Thanks. I am now running again the way i intended with one server beta and another release.

BTW: I used the legacy backup to transfer user setup to the release and it worked great. 

I will, of course, no longer be of much value to the beta but I can still test some things as my beta server will continue to be operational, at least until it fails or I cannot continue to keep it functional but i will primarily be using my release server.

When the release and beta are again in sync I will install the release on the machine that is now my beta and switch my current release server to the beta. That is the way I believe I want my servers to eventually run.

[Gilgamesh_48 1240]

One more thing: I used this "opportunity" to make my overall setup more reliable. I found a "refurbished" Fire 4k stick at Amazon for the price of #19.95 and I had a $12,.00 credit so the net cost to me was about $9.00 or so. 

I now have a backup device for my bedroom and that means a good deal less aggravation for me if something else screws up.

Sometimes a small cash outlay can result in a great improvement to my life.  

[Gilgamesh_48 1240]

I just tested this on my beta server (Version 4.9.0.25 beta) and I can confidently say THIS IS NOT  fixed contrary to what I was told. I guess I was told it would be fixed just to shut me up.. That worked for a short time but I detest being lied to and saying this would be fixed is a LIE..

I have fixed the problem for me by installing a release server on a second computer but I would MUCH rather this get fixed or eventually it will creep into the release and I, for one, will have a much more unpleasant experience using Emby.

While I like Emby a LOT I also do not understand why I was told it would be fixed when it was not fixed at all. 

I want to be told the truth and please do not insult me, and others, by lying again.   

[Happy2Play 9780]

Well fixes went in that build but what they entail only devs can say or requirements users need to do.

4.9.0.25-beta

• Fix regression causing some Roku and android tv settings to not be saved

Edited June 15, 2024 by Happy2Play

[Gilgamesh_48 1240]

11 minutes ago, Happy2Play said:

Well fixes went in that build but what they entail only devs can say or requirements users need to do.

4.9.0.25-beta

• Fix regression causing some Roku and android tv settings to not be saved

It "might" be supposed to be fixed but it is NOT. It really really seems that the developers are too lazy to fix a problem they are well aware of. 

I hate being lied to but that seems to be the chosen way to make people reporting BUGS go away. 

I cannot use any other media handling program but I am really getting to the point where the only thing  I can trust Emby to do is lie to me.

I have, obviously, restarted my server and i have exited and reentered Emby on my Roku but the bug persists. I can live with this as I am not using a release server for my main Emby usage but, eventually, if no one bothers to fix this bug. it will creep into the release as Emby seems to have no aversion to releasing buggy software and the lying to say it is working. 

II am becoming convinced that Emby does not care and will say anything to get users reporting BUGS to go away.

@ebr, @speechles, @LukeDo any of you actually test for fixes using Roku? It sure does not look like it!

[speechles 2055]

@Gilgamesh_48

Emby Server Updated to 4.9.0.25 on BECKY

6/15/2024, 3:17:08 PM

 

That would be roughly 2 and a half hours ago it auto-updated.

 

1 hour ago, Gilgamesh_48 said:

 

@ebr, @speechles, @LukeDo any of you actually test for fixes using Roku? It sure does not look like it!

 

It isn't a Roku issue, per se until it is. The Emby server abruptly changed some things without realize that some legacy apps on the Roku and Android TV were still using those. These things happen. Then later you find out the thing we need to do most of the custom settings disappeared overnight and no changes were done to the apps. The change was made on the server. It is expected that this move at a break-neck speed. You have to keep up with trends, and all the other stuff that attracts new users. Having the user base increase with new users requires it moves at damn near the speed of light. This is a "Move Fast, Break Things" momentum where you have to keep up with relevance. Lose speed and you start to become irrelevant. Apologies that this is happening to you and most of all that it is happening on the Roku.

But these server changes are something we can only test after the Beta comes out. Just like it appears you tested and discovered it broken. Yep, I just did the same thing. Realized that it still has the same issues. I am sure Luke is very aware he is just a very busy person. A human with many many hats. One who occasionally makes mistakes. Just like all humans do. We just have to let him know that this did not fix the issue in the Beta. I tried to store both a tab preference, a custom grid with image size, image type, and sort. All of these restart at the default as if I never set anything. That is the real. No joke. No lies. We aren't here to play with your head. This is just something we need resolved. It is an issue.

 

1 hour ago, Gilgamesh_48 said:

It "might" be supposed to be fixed but it is NOT. It really really seems that the developers are too lazy to fix a problem they are well aware of. 

I hate being lied to but that seems to be the chosen way to make people reporting BUGS go away. 

I cannot use any other media handling program but I am really getting to the point where the only thing  I can trust Emby to do is lie to me.

I have, obviously, restarted my server and i have exited and reentered Emby on my Roku but the bug persists. I can live with this as I am not using a release server for my main Emby usage but, eventually, if no one bothers to fix this bug. it will creep into the release as Emby seems to have no aversion to releasing buggy software and the lying to say it is working. 
I am becoming convinced that Emby does not care and will say anything to get users reporting BUGS to go away.

It isn't that we do not care. That this isn't a bug enough issue to do something about and we can delay fixing it. This Issue specifically needs a server update.

But we are all human beings. It is nice to be told that the software isn't working as intended. It is also nice to have people contribute feedback. Both of which are highly desirable and come with a cost. That cost is you are allowed to say whatever you want to us and we cannot really have that kind of back and forth on a public forum. I get it that you are highly upset. I am too. I use the Roku on a daily basis and it is broken for me too since I only run Beta server. But I understand how these things happen. I also understand there is an enormous work load and sometimes some things get overlooked. I can understand since I can kind of see where that can happen. It happens to all of us.  We will get this fixed ASAP. Apologies again this happened.

 

Edited June 16, 2024 by speechles

[Gilgamesh_48 1240]

2 minutes ago, speechles said:

@Gilgamesh_48

Emby Server Updated to 4.9.0.25 on BECKY

6/15/2024, 3:17:08 PM

 

That would be roughly 2 and a half hours ago it auto-updated.

 

It isn't a Roku issue, per se until it is. The Emby server abruptly changed some things without realize that some legacy apps on the Roku and Android TV were still using those. These things happen. Then later you find out the thing we need to do most of the custom settings disappeared overnight and no changes were done to the apps. The change was made on the server. It is expected that this move at a break-neck speed. You have to keep up with trends, and all the other stuff that attracts new users. Having the user base increase with new users requires it moves at damn near the speed of light. This is a "Move Fast, Break Things" momentum where you have to keep up with relevance. Lose speed and you start to become irrelevant. Apologies that this is happening to you and most of all that it is happening on the Roku.

But these server changes are something we can only test after the Beta comes out. Just like it appears you tested and discovered it broken. Yep, I just did the same thing. Realized that it still has the same issues. I am sure Luke is very aware he is just a very busy person. A human with many many hats. One who occasionally makes mistakes. Just like all humans do. We just have to let him know that this did not fix the issue in the Beta. I tried to store both a tab preference, a custom grid with image size, image type, and sort. All of these restart at the default as if I never set anything. That is the real. No joke. No lies. We aren't here to play with your head. This is just something we need resolved. It is an issue.

 

It isn't that we do not care. That this isn't a bug enough issue to do something about and we can delay fixing it. This Issue specifically needs a server update.

But we are all human beings. It is nice to be told that the software isn't working as intended. It is also nice to have people contribute feedback. Both of which are highly desirable and come with a cost. That cost is you are allowed to say whatever you want to us and we cannot really have that kind of back and forth on a public forum. I get it that you are highly upset. I am too. I use the Roku on a daily basis and it is broken for me too since I only run Beta server. But I understand how these things happen. I also understand there is an enormous work load and sometimes some things get overlooked. I can understand since I can kind of see where that can happen. It happens to all of us.  We will get this fixed ASAP. Apologies again this happened.

 

I no longer care about "why" I just want the bug to go away. T facilitate that I am in the process of removing all aces of the beta from my machine that ran the beta and, once that finishes I will install the release on that machine as well and Emby will have completely lost a beta tester. I wanted to run the beta for testing purposes and the release for general running but I now cannot do that at all. 

I can easily live with bugs and other problems in the beta, those are expected, but the complete failure of this even being tested on Rokus is as close to unforgivable as things like this get. I no longer believe anything Emby spins into the universe. I just hope against hope that the release does not get screwed up too. 

I will soon, OK maybe two days, have two release servers and, unless something changes, that is how I intend to run for the near future at least. 

If Plex was even half way decent i would switch back as they don't lie to me. They just don't talk to anyone. 

My media life is in turmoil but everything will soon stabilize and that will. maybe, make my media viewing go back to where I believe it should be.

I like to think I had some value as a beta tester but this latest make me think that the higher ups at Emby just want me to shut up and go away. 
Well, in that, the have success.