+- Kodi Community Forum (https://forum.kodi.tv)
+-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33)
+--- Forum: Add-on Support (https://forum.kodi.tv/forumdisplay.php?fid=27)
+---- Forum: Program Add-ons (https://forum.kodi.tv/forumdisplay.php?fid=151)
+---- Thread: Release 3D Enabler Samsung TV (/showthread.php?tid=185212)
RE: 3D Enabler Samsung TV - the8thsign - 2014-06-01
I'm getting a Connection Failed error. I haven't seen anyone else with the error. Any idea what may be causing it?
Here are the logs:
23:27:22 T:4710219776 DEBUG: CPlayerCoreConfig::<ctor>: created player [TV]Samsung LED55 for core 5
23:27:23 T:4711829504 DEBUG: tvXMLloc: http://192.168.1.37:7676/smp_6_
23:27:23 T:4711829504 DEBUG: tvip: 192.168.1.37
23:27:23 T:4711829504 DEBUG: tvXML: <?xml version="1.0"?>
<root xmlns='urn
chemas-upnp-org:device-1-0' xmlnsec='http://www.sec.co.kr/dlna' xmlns:dlna='urnchemas-dlna-org:device-1-0'><specVersion>
<major>1</major>
<minor>0</minor>
</specVersion>
<device>
<deviceType>urn
amsung.com:device:RemoteControlReceiver:1</deviceType><friendlyName>[TV]Samsung LED55</friendlyName>
<manufacturer>Samsung Electronics</manufacturer>
<manufacturerURL>http://www.samsung.com/sec</manufacturerURL>
<modelDescription>Samsung TV RCR</modelDescription>
<modelName>UN55H7100</modelName>
<modelNumber>1.0</modelNumber>
<modelURL>http://www.samsung.com/sec</modelURL>
<UDN>uuid:05f5e101-0064-1000-bc6f-5056bfe76852</UDN>
<sec:deviceID>SHCHVWLLGRLHK</sec:deviceID>
<sec
roductCap>Resolution:1920X1080,ImageZoom,ImageRotate,Y2014,ENC</secroductCap><serviceList>
<service>
<serviceType>urn
amsung.comervice:MultiScreenService:1</serviceType><serviceId>urn
amsung.comerviceId:MultiScreenService</serviceId><controlURL>/smp_8_</controlURL>
<eventSubURL>/smp_9_</eventSubURL>
<SCPDURL>/smp_7_</SCPDURL>
</service>
</serviceList>
<sec:Capabilities>
<sec:Capability name='samsung:multiscreen:1' port='8001' location='/ms/1.0/'></sec:Capability>
</sec:Capabilities>
</device>
</root>
23:27:23 T:4711829504 INFO: Discovered devices count: 1
23:27:23 T:4711829504 DEBUG: Connecting to:192.168.1.37:55000
23:27:23 T:4711829504 INFO: TV is Off or IP is outdated
23:27:23 T:4711829504 INFO: NOTIFY: Discovered TV: [TV]Samsung LED55. Connection Failed
23:27:23 T:4412887824 DEBU
RE: 3D Enabler Samsung TV - pavel.kuzub - 2014-06-01
Hello the8thsign,
First of all congratulations with your new TV. As the log indicates - you have a new H-series model that no one has reported yet, so please be the first to help us checking if the model is backward compatible with previous.
Previous models are using port 55000 on TV for authentication and remote control. It may happen that new models may use another port and/or protocol for remote control to support new features.
Can you please do the following:
1) Ensure your TV is on and check from your PC if the port is open by running the following in CMD/Terminal:
telnet 192.168.1.37 55000
2) Verify that your TV is not set to deny access to the remote devices
3) Check if other applications that can control your TV via LAN works. If so - what are they? I use iOS apps: "myTifi", "Smart View"
Hello PH-SYM,
Thank you for your valuable inputs about the key sequence for D-series models
Hello jasius, bugleboy,
I cannot adopt this to other vendor devices and to another protocol as I simply don't own such devices.
RE: 3D Enabler Samsung TV - brazen1 - 2014-06-01
Hi pavel.kuzub.
Great to see your return in this time of turmoil and hope all is as well as can be.
Do you still have interest in external player trigger for checkerboard?
RE: 3D Enabler Samsung TV - the8thsign - 2014-06-02
Thanks for the help pavel.kuzub,
The port has definitely change. I cannot telnet in to 55000 and both myTifi and Smart View find the TV but cannot connect. I'd be happy to do whatever you may need to update for the H series.
I can however send Video to the TV using http://192.168.1.37:7676/smp_22_ but I'm not sure if that even helps with control.
RE: 3D Enabler Samsung TV - law007 - 2014-07-22
Hi!
the H series tv's opened ports:
Completed SYN Stealth Scan at 02:14, 6311.61s elapsed (65535 total ports)
Nmap scan report for 192.168.77.18
Host is up (0.0027s latency).
Not shown: 65526 closed ports
PORT STATE SERVICE
4443/tcp open pharos
6001/tcp open X11:1
7676/tcp open imqbrokerd
8000/tcp open http-alt
8001/tcp open vcom-tunnel
8080/tcp open http-proxy
8443/tcp open https-alt
15500/tcp open unknown
52345/tcp open unknown
RE: 3D Enabler Samsung TV - Jon-G - 2014-07-28
Hi, Just got my UN55F900 and couldnt connect.
A port scan revealed the following:
PORT STATE SERVICE
80/tcp open http
443/tcp open https
6000/tcp filtered X11
7676/tcp open imqbrokerd
9090/tcp open zeus-admin
50000/tcp open ibm-db2
50001/tcp open unknown
50500/tcp open unknown
Opened up the service.py file and tried with the port set to both 50001 and 50500 in the script but using either I just get the status box popping up saying authentication failed, and the TV is not prompting me to allow the device like it did when I "paired" my iPhone using Samsungs Smart View app.
In the config page of the addon I can see its now correctly pulling back the TV name.
Anything I can do to test Ill be glad to. Would love to have this working
RE: 3D Enabler Samsung TV - robclarke41 - 2014-08-07
Wow this add-on is absolutely amazing I just wanted to say how grateful I am and how impressed I am with it. I mainly use over/under or top and bottom movies in XBMC for which the add-on works like a dream. For some reason though it does not switch the TV to sbs mode when an sbs movie is played. I'm assuming that as long as XBMC knows that the movie is sbs then the add-on bases the TVs 3D mode on this? I have a Samsung ue65f6400, is the problem I'm having to do with the key press combinations as other users have mentioned? The problem with this TV is that it remembers the last 3D mode used. When XBMC detects and sbs movie I guess ideally it should move from ou to sbs in the menu. If anyone has any ideas or a solution I would be eternally grateful, otherwise this is great work sir.
RE: 3D Enabler Samsung TV - SiliconKid - 2014-08-08
First of all, excellent work on this add-on.
SUGGESTIONS
1. It would be awesome if the add-on had a button called "TEST" next to each command sequence in the config that you could click when you are setting up the add-on to test your command sequences right there and then.
I have a PS51D550 3D Plasma TV and I've managed to get this to work after a bit of experimentation.
Some notes that might help others:
1. I had to enable networked remote control from the TVs menu to get this to work. That may seem obvious, but I'm stating it anyway because if you don't turn that on, it won't work.
2. I had to change the key sequence for SBS completely.
I found that I need this: P3000,3D,P3000,EXIT
For some reason, I HAVE TO have a delay before the 3D command is sent, otherwise it does strange things. It's as if XBMC first needs to get its Stereoscopic mode active and start playing the video stream BEFORE you switch the TV in to 3D mode.
I know that doesn't seem right and the TVs mode should be independent of what XBMC is doing, but I can't get it to work any other way. If I start the sequence with 3D,P1200 I don't end up in the right mode and I don't even see the 3D menu appear on the TV, I have to have that 3 second delay in there BEFORE the 3D command is sent.
3. It seems like I don't need any commands on exiting a movie. My TV seems to just go back to 2D mode on its own when the movie stops playing. If I try to send it a 3D command to turn off 3D, more weird things start happening again.
I'm still playing with that to understand exactly what it's doing.
4. My TV also remembers the last 3D mode, also wraps around when you navigate left or right, and does not respond to UP or DOWN when you are in the 3D menu.
Which means that I also have a problem with:
a. Ending up in the wrong mode if the TV somehow resets that "Last remembered mode" to a different mode that my command sequences expect it to be in.
b. Switching between TAB and SBS movies, because obviously all command sequences have to now be setup assuming ONE initial starting position, and there is now way to tell what that is or reset it with a command as far as I can tell.
The add-on is not responsible for these problems of course, it is merely a victim of them.
What would solve this would be a way to force the TV to reset the 3D mode to the default 2D->3D mode via a remote command BEFORE sending the relevant mode switch command sequence.
RE: 3D Enabler Samsung TV - fallback - 2014-08-10
I got the H6470 and there is no Port 55000 listening.
It seems the new H series is a bit different.
RE: 3D Enabler Samsung TV - NicCo - 2014-10-08
Hi,
I'm using Gotham 13.2 and I have a Samsung UE40ES6300 with a wifi connection to the LAN. I have installed your plugin, it's OK but I can't detect my TV.
Telnet to IP:55000 is OK, ping is OK, I can control my TV with a Samsung Smartphone so all seems to be OK.
Could you help me ?
Thanks !
Edit : On my Laptop it's OK, but there is no difference between both, running Windows 8.1 and Gotham 13.2. Differences are telnet enable and no skin on my Laptop. I'm going to try an solution.
Edit 2 : I have installed Telnet client on Windows 8.1 and now it's OK, XBMC detects my TV ! Thanks !
RE: 3D Enabler Samsung TV - Masakari - 2014-10-23
Hi,
I also have a new 2014 H series and I'm really keen to get this plugin working and willing to help. I can use "Samsung Smart View 2.0" to control the TV over Wi-Fi from my phone. I believe "2.0" was introduced with the H series and it doesn't work with older TVs nor does the original "Samsung Smart View 1.0" work with this H series.
I used tcpdump to watch the comms between the phone and the TV. It seems to initially connect to TCP/7676 upnp which directs it to TCP/8001. It then jumps to TCP/8080 to authenticate and issue some commands, most of which do not make sense to me.
tcpdump available here : http://filebin.net/t4aytjwn19
XBMC log here:
09:57:04 T:3356 DEBUG: tvXMLloc: http://192.168.0.89:7676/smp_7_
09:57:04 T:3356 DEBUG: tvip: 192.168.0.89
09:57:04 T:3356 DEBUG: tvXML: <?xml version="1.0"?>
<root xmlns='urn
chemas-upnp-org:device-1-0' xmlnsec='http://www.sec.co.kr/dlna' xmlns:dlna='urnchemas-dlna-org:device-1-0'><specVersion>
<major>1</major>
<minor>0</minor>
</specVersion>
<device>
<deviceType>urn
amsung.com:device:RemoteControlReceiver:1</deviceType><friendlyName>[TV]MasakariTV</friendlyName>
<manufacturer>Samsung Electronics</manufacturer>
<manufacturerURL>http://www.samsung.com/sec</manufacturerURL>
<modelDescription>Samsung TV RCR</modelDescription>
<modelName>UA55H7000</modelName>
<modelNumber>1.0</modelNumber>
<modelURL>http://www.samsung.com/sec</modelURL>
<serialNumber>20090804RCR</serialNumber>
<UDN>uuid:068e7780-006e-1000-bc6f-5056bf39a20a</UDN>
<sec:deviceID>43CHVWLLOXIMK</sec:deviceID>
<sec
roductCap>Resolution:1920X1080,ImageZoom,ImageRotate,Y2014,ENC</secroductCap><serviceList>
<service>
<serviceType>urn
amsung.comervice:MultiScreenService:1</serviceType><serviceId>urn
amsung.comerviceId:MultiScreenService</serviceId><controlURL>/smp_9_</controlURL>
<eventSubURL>/smp_10_</eventSubURL>
<SCPDURL>/smp_8_</SCPDURL>
</service>
</serviceList>
<sec:Capabilities>
<sec:Capability name='samsung:multiscreen:1' port='8001' location='/ms/1.0/'></sec:Capability>
</sec:Capabilities>
</device>
</root>
09:57:04 T:3356 INFO: Discovered devices count: 1
09:57:04 T:3356 DEBUG: Connecting to:192.168.0.89:8080
09:57:04 T:3356 DEBUG: setSetting:ipaddress=192.168.0.89
09:57:04 T:3356 DEBUG: setSetting:tvname=[TV]MasakariTV
09:57:04 T:3356 INFO: [JS3D] Attempting to send: 001d006970686f6e652e3344456e61626c65722e696170702e73616d73756e674400640014004d546b794c6a45324f4334774c6a45344f413d3d18004d4441744d5559745244417451555174517a41745245513d10004d30516752573568596d786c63673d3d
09:57:14 T:3356 DEBUG: Parsing response (0):
09:57:14 T:3356 DEBUG: authenticate() returned: False
09:57:14 T:3356 INFO: NOTIFY: Discovered TV: [TV]MasakariTV. Authentication Failed
RE: 3D Enabler Samsung TV - Moonbase - 2014-10-24
I have a Samsung UE40H6750 and very much hoped this would work – switching to 3D on this TV is horrible, you have to press Menu → Right → 9x Down → 2x Enter → 3x Right → Enter! No 3D button altogether, shame on them.
Unfortunately, v0.1.1 I installed seems to find the TV (and shows its name) then states "Connection Failed".
Telnet to port 50000 gives "Connection refused".
How can I help to diagnose and make this work?
If it helps, I did a port scan on the TV:
Code:
PORT STATE SERVICE
4443/tcp open pharos
6001/tcp open X11:1
7011/tcp open unknown
7676/tcp open imqbrokerd
8000/tcp open http-alt
8001/tcp open vcom-tunnel
8080/tcp open http-proxy
8443/tcp open https-alt
8889/tcp open ddi-tcp-2
15500/tcp open unknown
52345/tcp open unknownChanging "port" to 15500 in service.py changes the output from "Connection Failed" to "Authentication …" (can't read rest of message, it goes away too fast). Same for port 52345.
Starting/Ending a 3D video shows the 3DEnabler message: "Authentication Failed. Authentication Failed."
RE: 3D Enabler Samsung TV - Masakari - 2014-10-24
If it helps you moonbase I can enable 3d on my tv by pressing keypad and selecting the 3d icon. Seems to remember the last mode. Why Samsung didn't put 3d in the tools menu or allow us to hold down a button to activate I will never know.
I am going to try posting those same json messages I captured my phone sending to the TV but I don't think I am going to get past authentication as the code the phone sends is bizarre. Might have some time today.
RE: 3D Enabler Samsung TV - Masakari - 2014-12-30
So I had another look at this over the Christmas holidays and at this point I'm assuming the H series uses the following ports:
tcp/7676 UPNP
tcp/8000 Main webservice port
tcp/8080 Secure Pairing port
I believe we just need to "trick" the TV into pairing with a non-android client but all my attempts have failed. The only thing I can do is crash the webservice on the TV and cause it to restart (doesn't damage anything)! After pairing on 8080, we should be able to establish a websocket on 8000 and send through commands.
In my original packet trace it first sent this message to the TV but it no longer accepts this:
POST URI = http://masakaritv.localdomain:8080/ws/pairing?step=1&app_id=12345&device_id=4e5068a7-b99a-4eb2-897c-8a413d0bbfd1&type=1
JSON_CONTENT = ""auth_Data":{"auth_type":"SPC","GeneratorServerHello":"010200000000000000008A00000006363534333231ED866E9A58301B12B491577920A977687D81B3DFC3B945D10F80C8973CA8671B72B07759C1D6670CB607DDB4698E085EC3396B86DE66FDE904A137C135B02B81A3F7B36D11A5BA605C24231F906DF3F480591F8A4B447163DF3FA5A85B78B3A0177A00E90E50B0873E4EFA3E8EFB730688F40315A2F1176A429C42313625D9840000000000"}"
I've started to pull apart the apk file for the Samsung Smartview 2.0 application but it's way above my abilities. I've pasted the source here:
http://filebin.net/qime9h3nym
Hopefully someone with some java knowledge can workout how this GeneratorServerHello and GeneratorClientHello pairing works.
Kind regards,
Masakari
RE: 3D Enabler Samsung TV - Lunatixz - 2014-12-30
I would be grateful to anyone who can get this working on a H series....