All Activity

Thank you @Dickydodah!, I though I tried to get it there 1st time I saw this post but was unable to download it. Got it and love it!

Where can I find release notes for beta stuff, is there a location? TY I have the latest AndroidTV beta and will test tomorrow to check the new search function Thank you

Na dann! Ich bin gespannt und freue mich schon. Danke

Hi there, let's look at an example. Please attach the information requested in how to report a media playback issue. Thanks!

HI, not yet, but stay tuned for the upcoming smart views/playlists feature. Also the upcoming 4.10 release will allow you to design your own home screen sections, so I think that will help you with this.

Hallo an alle, Besteht irgendwie die Möglichkeit zum anlegen einer Bibliothek die Täglich Vorschläge zu ungesehenen Filmen generiert? Ich stell mir das ganze in etwa so vor: mit Leiste der Zufälligen Filme In dieser Bibliothek sollen nur Ungesehene Filme ... Zufällig ausgewählt ... aus den von mir hinterlegten Ordnern (Filme-1, Filme-2, Filme-3, etc.) erscheinen. Am liebsten zeitlich einstellbarer Intervall, etwa alle 6 / 12 / 24 / 48 / 60 Stunden. Die Anzahl der Gezeigten Objekte kann auch ruhig auf 30 Stk. beschränkt sein, oder gar selbst definierbar nach Unterordner. z.B. Filme-1: 5 Objekte, Filme-2: 10 Objekte ... Auch wäre es schön auf der Startseite im allgemeinen die "Bewertungen (IMDb)" unter den Filmen und Serien anzuzeigen, in einem anderen Beitrag wurde schon vor Jahren dieses feature als Update versprochen, wurde aber bis heute nicht umgesetzt ... oder ich habe den Schalter dafür noch nicht gefunden Viele liebe Grüße H

I encountered the same problem. I am a docker emby deployed under wsl2 of windows server 2025. Version 1.0.5.0 of the Bluray Folder Support plug-in in Emby Server 4.9.5.0 does not play the BDMV folder normally. Returning Emby4.8.10.0 with Bluray Folder Support1.0.2.0 version can achieve normal playback of the original Blu-ray folder. Looking forward to the official repair.

After testing, this scheme is a thing of the past and is completely unsuitable for the plug-in Bluray Folder Support 1.0.5.0 of the new version of 4.9.5.0. Emby4.8.10.0 with Bluray Folder Support1.0.2.0 version can achieve normal playback of the original Blu-ray folder.

That does, of course, depend on the screen size and resolution of the poster artwork used. In any event, this may be why the BBFC has an alternative set of certificate icons that use colour and shape to differentiate. The "classic" set was already pretty good in this respect, with only the 12 and 15 ratings being differentiated solely by text. It should be noted that this set is missing "12A", which is the same colour as "12". However, being 50% MORE text (as opposed to just different text), it remains easily differentiated even at small sizes. Ultimately, if this was an OPTION, then users could decide.

What example are we focusing on in these log files?

What do you mean by same old locations?

Ok yes now I found it, it’s available only when I use “TV mode”, but still the horizontal problem persists, it’s not in everything but mainly still the same old locations .

I apologize for the delay. The emby server is up2date and I was having no issue with the truehd7.1 until I updated the shield emby app. Issue remains with only truehd7.1 audio codec. When I change to another codec, no problem. Emby is still awesome. Thank you. NOTE: when I updated the app it gave the option to try another emby app android interface. I did not wish to push my luck like if I did not like it could I go back, but now I wonder. I will also endeavor to return to the previous app on the shield. I appreciate your effort. Thank you. To tidy things up a bit, please close the thread.

i added log in first post but here are some others not sure what one it would be in now. these are from the 5/6th embyserver-63921571200.txt embyserver-63921657600.txt embyserver-63921589611.txt

I’m sorry but still I can’t find it, here’s what I see ..

I appreciate the clarification from everyone. To be clear, yes, EmbyCredits was the starting point in the sense that it was the existing project I wanted to remain compatible with. That was the reason for using it as a reference point — so the new services could work alongside it and be useful to existing users, including users who may want to migrate slowly to another solution if they have AV1 content or other specific needs like I do. It was never intended to imply that the entire concept of credit detection belongs to one project. Detecting credits in media is a general problem, and different implementations can approach it in different ways. The reason I created this was to build a different architecture with the features I wanted: dedicated OCR services, CPU/GPU editions, Docker-based backend services, new detection engines, expanded configuration, and a more flexible workflow. I also want to emphasize that compatibility was part of the goal from the beginning. The OCR services can be used with EmbyCredits, and users can run both projects side-by-side if they choose. I appreciate the questions because it gives me a chance to clarify the relationship properly. That said, I think I have explained the history and intentions clearly, so I will be stepping back from further discussion on this thread. I’ll continue focusing on development and supporting users through the appropriate channels.

The ones thing this needs is to be able to use discogs or music brainz for identifying the media. Instead of the movie database, tvdb, IMDb, or be able to switch between the metadata sites.

Piracy was also one of the reasons they stated as being part of this. The amount of dmca requests they probably had to deal with on a daily basis must be staggering. Some legitimate, some bogus, all requiring paid attorneys to review and respond. I know it because we deal with it and we don't even provide content. To not have to deal with that anymore was one of their stated goals.

They already had this before, it's just that the whole system was hard for them to work with and maintain because it wasn't theirs. Yes, they used the Android OS to get a head start and build market share, but eventually the relationship ran it's course and they decided it was no longer sustainable. They need to be able to control internal policies, api's, etc, and they can't do that with somebody else's OS. I don't think they intended to punish the small segment of enthusiasts with custom launchers. I think that just became casualty in order for them to solve their bigger problems.

I just disagree, which is fine "It wasn't about money" ignores Amazon's entire revenue strategy. Amazon doesn't make profit selling $30 streaming sticks. They profit off the home screen real estate, sponsored ad banners, and transaction fees from inside the ecosystem. On Fire OS, custom launchers and ad-blockers allowed users to bypass that entire monetized pipeline. Replacing Android with Vega OS permanently seals those financial leaks. They waited because they needed Android's app library to build market share and defeat early competitors like Roku. Once they achieved dominant market position, they pulled the ladder up behind them. Using open Android to build a user base and then locking it down once established is a classic tech platform play.

It works. Thank you.

If our app gets pulled from the store, I don't think google would accept the explanation that our users were running in developer mode.

WOuld it be possible, that if the android device is in "developer mode" then it would show all?

Yes of course. The loss of sideloading is a negative. But what I listed as the reasons for change are still true and that this wasn't about money. They started depending on android in 2014, so to go 12 years and then pull the rug out is really hard and going to upset a lot of people. If they had done this say, 8 years ago, the impact would have been smaller, by now they'd have a large catalog of apps, and who knows, with enough user pressure over time they may have brought back some form of sideloading.

Like many, I’d never buy a Vega device: Because Vega OS isn't built on Android, it can’t run standard .apk files. Amazon intentionally locked the system down, completely eliminating the "Install from Unknown Sources" toggle. For the enthusiast community, losing the ability to sideload apps or customize the software environment is an absolute dealbreaker. Vega OS exists primarily to give Amazon total control over the hardware. Third-party home screen launchers, deep system tweaks, and custom background services are completely blocked. For anyone who wants an ad-free interface or full control over their home theater hardware, Vega OS is just too restrictive and tied to Amazon’s ad ecosystem.