Compatibility with Samsung Frame TVs #110
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks! I'll merge it preemptively and see if it causes issues for anyone else. |
|
finally it brings dlna-support to many torrserver users with samsung tv! thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I got a Samsung Frame TV model 2021 (User-Agent:
DLNADOC/1.50 SEC_HHP_Samsung The Frame 50/1.0 UPnP/1.0).When browsing to any DMS based DLNA server, it displays an empty content directory.
I went through the painful debugging process and started comparing every piece of the protocol with MiniDLNA responses (that is working smoothly), mismatching case sensitivity in header names, removing non-standard looking fields from the XML responses, forcing the SPCD descriptor to be the same, etc.
The resolution of this issue was to patch the entity encoding of the DIDL-Lite envelope.