In my case this is about a Philips 42PFL7676H TV, but this likely applies to many Philips TVs from the 2009-2012 era.
According to nmap, these ports are open:
PORT STATE SERVICE REASON VERSION
1925/tcp open unknown syn-ack
2323/tcp open 3d-nfsd? syn-ack
49153/tcp open upnp syn-ack Philips Intel UPnP SDK 1.4 (Philips Smart TV; UPnP 1.0; DLNADOC 1.50)
TCP port 1925 is actually implementing the jointSPACE REST API over HTTP which has some nice documentation (also locally on your TV).
PCremote implements this and is easy to install: just download (or git clone) the html locally or to a web-server and try it, or even easier: browse to the www.netdata.be/tv site. You can even use it on your Raspberry Pi. There is also support for jointSPACE it in agocontrol.
Two nice threads about it from the Philips support forum:
TCP port 2323 seems to be the voodooport which should enable you to do DirectFB Voodoo.
Jean-Marc Harvengt (software engineer at Philips) showed a nice demo (see video below) on using VooDoo. I wish he had published the source code.
TCP port 49153 also hosts an HTTP server. The base URL I could find information about is 192.168.71.115:49153/nmrDescription.xml It seems that nmrDescription.xml has to do with DLNA and upnp.
Later on I found that my brothers 32PFL7675H TV should also support JointSPACE, but that it had to be activated:
AFTER upgrading to the new firmware, jointSPACE NEEDS TO BE ACTIVATED by entering the following digits sequence while watching TV (WatchTV activity): “5646877223”
Source: jointSPACE TVs Developers
Before activation, only port was open 49153. After that, port 2323 was open as well. But the www.netdata.be/tv app doesn’t work on this TV. This does work however: Philips MyRemote – Android Apps on Google Play
–jeroen
Read the rest of this entry »
Like this:
Like Loading...