SamyGO - User contributions [en]

MessageBoxService request format

2010-05-11T15:13:30Z

Doodlecz:

=MessageBoxService SOAP request=

In general, TV supports processing SOAP requests. Basic interface description can be downloaded from TV:

http://yourTV:52235/pmr/PersonalMessageReceiver.xml

<?xml version="1.0" ?>
<root xmlns="urn:schemas-upnp-org:device-1-0">
<specVersion>
<major>1</major>
<minor>0</minor>
</specVersion>
<device>
<deviceType>urn:samsung.com:device:PersonalMessageReceiver:1</deviceType>
<friendlyName>TV</friendlyName>
<manufacturer>Samsung Electronics</manufacturer>
<manufacturerURL>http://www.samsung.com</manufacturerURL>
<modelDescription>Samsung DTV PMR</modelDescription>
<modelName>Samsung DTV PMR</modelName>
<modelNumber>1.0</modelNumber>
<modelURL>http://www.samsung.com</modelURL>
<serialNumber>...</serialNumber>
<UDN>uuid:...</UDN>
<serviceList>
<service>
<serviceType>urn:samsung.com:service:MessageBoxService:1</serviceType>
<serviceId>urn:samsung.com:serviceId:MessageBoxService</serviceId>
<controlURL>/PMR/control/MessageBoxService</controlURL>
<eventSubURL>/PMR/event/MessageBoxService</eventSubURL>
<SCPDURL>MessageBoxService.xml</SCPDURL>
</service>
</serviceList>
</device>
</root>

You can see, interface implements only one service MessageBoxService which description can be downloaded from:

http://yourTV:52235/pmr/MessageBoxService.xml

<?xml version="1.0" encoding="utf-8" ?>
<scpd xmlns="urn:schemas-upnp-org:service-1-0">
<specVersion>
<major>1</major>
<minor>0</minor>
</specVersion>
<actionList>
<action>
<name>AddMessage</name>
<argumentList>
<argument>
<name>MessageID</name>
<direction>in</direction>
<relatedStateVariable>A_ARG_TYPE_MessageID</relatedStateVariable>
</argument>
<argument>
<name>MessageType</name>
<direction>in</direction>
<relatedStateVariable>A_ARG_TYPE_MessageType</relatedStateVariable>
</argument>
<argument>
<name>Message</name>
<direction>in</direction>
<relatedStateVariable>A_ARG_TYPE_Message</relatedStateVariable>
</argument>
</argumentList>
</action>
<action>
<name>RemoveMessage</name>
<argumentList>
<argument>
<name>MessageID</name>
<direction>in</direction>
<relatedStateVariable>A_ARG_TYPE_MessageID</relatedStateVariable>
</argument>
</argumentList>
</action>
</actionList>
<serviceStateTable>
<stateVariable sendEvents="no">
<name>A_ARG_TYPE_MessageID</name>
<dataType>string</dataType>
</stateVariable>
<stateVariable sendEvents="no">
<name>A_ARG_TYPE_MessageType</name>
<dataType>string</dataType>
<defaultValue>text/xml; charset="utf-8"</defaultValue>
</stateVariable>
<stateVariable sendEvents="no">
<name>A_ARG_TYPE_Message</name>
<dataType>string</dataType>
</stateVariable>
</serviceStateTable>
</scpd>

According to the "downloaded" content, the MessageBoxService should implement two actions - AddMessage and RemoveMessage. However, RemoveMessage does not seem to be implemented in TV, so let's forget about it for now.

== Structure of AddMessage ==

Structure of the AddMessage is partially clear from the description, and it should have following format:

<nowiki><u:AddMessage xmlns:u=\"urn:samsung.com:service:MessageBoxService:1\">
<MessageType>Body of MessageType</MessageType>
<MessageID>Body of MessageID</MessageID>
<Message>Body of Message</Message>
</u:AddMessage></nowiki>

This XML structure is valid if:
* Body of MessageType contains text "text/xml".
* Body of MessageID does not seem to be checked, so it can contain anything.
* Body of Message contains XML structure with message information.

== Structure of Message ==

The most interesting thing is content of the Message body which specifies message sent to the TV.

Content of the Message is in fact XML structure, but with replaced "<" -> "&lt;" and ">" -> "&gt;".

For easier reading, in following XML structured I use "<" and ">" characters but before sending the request to the TV, don't forget to replace them by "&lt;" and "&gt;"!

Message XML structure is parsed as following:

<Category>Body</Category>
is checked to contain "SMS", "Incoming Call", "Schedule Reminder" and "MMS". However, "MMS" category is not implemented in TV.

<DisplayType>Body</DisplayType>
is checked if contains "Maximum". If yes, detailed message is displayed on the TV, otherwise only short info is displayed.

According to the Category type, different tags are used to retrieve content:

=== "SMS" Category ===

<ReceiveTime>
<Date>YYYY-MM-DD</Date> (YYYY - year, MM - month, DD - day)
<Time>HH:MM:SS</Time> (HH - hour, MM - minute, SS - second)
</ReceiveTime>
<Receiver>
<Number>Receiver Phone Number</Number>
<Name>Receiver Name</Name>
</Receiver>
<Sender>
<Number>Sender Phone Number</Number>
<Name>Sender Name</Name>
</Sender>
<Body>SMS Body</Body>

Sender and Body is displayed only in case DisplayType is set to "Maximum".

=== "Incoming Call" Category ===

<CallTime>
<Date>YYYY-MM-DD</Date> (YYYY - year, MM - month, DD - day)
<Time>HH:MM:SS</Time> (HH - hour, MM - minute, SS - second)
</CallTime>
<Callee>
<Number>Callee Phone Number</Number>
<Name>Callee Name</Name>
</Callee>
<Caller>
<Number>Caller Phone Number</Number>
<Name>Caller Name</Name>
</Caller>

Caller is displayed only in case DisplayType is set to "Maximum".

=== "Schedule Reminder" Category ===

<StartTime>
<Date>YYYY-MM-DD</Date> (YYYY - year, MM - month, DD - day)
<Time>HH:MM:SS</Time> (HH - hour, MM - minute, SS - second)
</StartTime>
<Owner>
<Number>Owner Phone Number</Number>
<Name>Owner Name</Name>
</Owner>
<Subject>Schedule Reminder Subject</Subject>
<EndTime>
<Date>YYYY-MM-DD</Date> (YYYY - year, MM - month, DD - day)
<Time>HH:MM:SS</Time> (HH - hour, MM - minute, SS - second)
</EndTime>
<Location>Location Name</Location>
<Body>Schedule Reminder Body</Body>

EndTime, Location and Body is displayed only in case DisplayType is set to "Maximum".

== Sample Request ==

Sample SOAP request to display SMS message (without HTTP headers):

<nowiki><?xml version="1.0" encoding="utf-8"?>
<s:Envelope s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" >
<s:Body>
<u:AddMessage xmlns:u="urn:samsung.com:service:MessageBoxService:1\">
<MessageType>text/xml</MessageType>
<MessageID>can be anything</MessageID>
<Message>
&lt;Category&gt;SMS&lt;/Category&gt;
&lt;DisplayType&gt;Maximum&lt;/DisplayType&gt;
&lt;ReceiveTime&gt;
&lt;Date&gt;2010-05-04&lt;/Date&gt;
&lt;Time&gt;01:02:03&lt;/Time&gt;
&lt;/ReceiveTime&gt;
&lt;Receiver&gt;
&lt;Number&gt;12345678&lt;/Number&gt;
&lt;Name&gt;Receiver&lt;/Name&gt;
&lt;/Receiver&gt;
&lt;Sender&gt;
&lt;Number&gt;11111&lt;/Number&gt;
&lt;Name&gt;Sender&lt;/Name&gt;
&lt;/Sender&gt;
&lt;Body&gt;Hello World!!!&lt;/Body&gt;
</Message>
</u:AddMessage>
</s:Body>
</s:Envelope></nowiki>

Main Page

2010-05-11T14:37:07Z

Doodlecz: /* General Information */

== Welcome to SamyGo WiKi ==


'''WARNING: DO NOT UPDATE THE SAMSUNG LATEST FIRMWARE UPGRADES or YOU CAN NOT USE OUR HACKS AND CAN NOT REVERT FIRMWARE BACK EASILY!'''


SourceForge doesn't allow users to write on wiki. We needed to assign writing permission by hand.

Place note for editing permissions by hand on request from forum ([http://forum.samygo.tv/ucp.php?i=pm&mode=compose&u=68 Erdem_ua] or [http://forum.samygo.tv/ucp.php?i=pm&mode=compose&u=78 dynamic1969]).

[[File:Logo.png]]

== Compatibility Overview ==

See the [[Compatibility]] page to see which TV models should work.

== Safety Measures ( which you shouldn't start without ) ==
#Have a working [[Enable Serial Console on non CI+ Devices|Ex-Link cable]] at hand.
#Ensure the backup exe.img ( stored on /dev/tbml10 ) is in good condition ( and ideally not altered. )
#Ensure your RS232 Setting in the Service-Menu is set to "debug".
#Know that your TV will reset RS232 jack back to UART mode after new firmware installation or reverting back to old version.
 

== Useful WIKI articles ==
*[[Is my TV supported?]]
*[[Is this tools avoids my warranty?]]
===Firmware Modification===
*[[Flashing Hacked Firmware to CI+ devices]]
*[[How to capture channel (PVR functionality)]]
*[[How to enable Telnet on samsung TV's]]
*[[How to enable Advanced mode startup script]]
*[[Enable Serial Console on non CI+ Devices]]
*[[Getting access to uBoot / bootloader]]
*[[Dumping and Flashing images by hand]]
*[[Open backdoor for fixing bootloop situations]]
*[[Using NoN-Samsung USB WiFi dongles with TV]]
*[[Mounting an NFS share on a USB device to bypass DLNA]]
*[[Mounting an CIFS/SAMBA share on a USB device to bypass DLNA]]
*[[Samsung A Series (2008 Model) Hacks]]
*[[Samsung A Series (sh4 CPU) Hacks]]
*[[Video AR Fix]]
*[[Playing with Firmware Images]]
*[[Enable Wiselink Movie on B550 and B6000 Series Devices]]
*[[Boot from USB using u-boot]]
*[[Forced revert back to older firmware]]
*[[Autoloader for extra exeDSP plugins (B65x)]]

===Software Tools===
*[[Setting up a native-compilation toolchain]]
*[[Setting up a cross-compilation toolchain]]
*[[SamyGO OpenEmbedded]]
*[[SamyGO Telnet Enabler]]
*[[SamyGO Extensions Pack]]
*[[SamyGO ChanEdit - Chanel Editor]]
*[[SamyGO Firmware Patcher]]
*[[NetSurf Web Browser]]
*[[Other Small Applications at Forum Pages]]

===General Information===
*[[Frequently Asked Questions]]
*[[Recovery of Bricked Device]]
*[[Service Manuals]]
*[[Service Menu]]
*[[Engineering Codes]]
*[[Media Play and DLNA]]
*[[Samsung channel list format]]
*[[MessageBoxService request format]]
 

== Interesting Reference Material ==
*[http://www.samsung.com/global/business/semiconductor/products/flash/downloads/applicationnote/rfs_v12_application_note.pdf Introduction to SAMSUNG's Linux Flash File System - RFS]
*[http://www.samsung.com/global/business/semiconductor/products/fusionmemory/downloads/RFS_130_Porting_Guide.pdf Linux RFS ( Robust FAT File System ) Porting Guide]
The file-system used in the the recent Samsung TVs is "RFS". Its proprietary nature and consequently so the absence of an according Linux RFS-Module in the standard Linux distributions makes it currently impossible to modify files by simply mounting the respective image as "RW", modifying it and saving the respective image again. This is the reason why currently all changes are done via patching of the image-binaries.

*[http://www.samsung.com/global/business/semiconductor/products/flash/downloads/LinuStoreII_GPL%20Compliance_10.pdf Source code of XRS and TinyXSR in Linux kernel and u-boot]

*[http://www.samsung.com/global/opensource/ Samsung's Source Code]
All the source code Samsung is legally obliged to post can be found here.

*[http://forums.cnet.com/samsung-forum/ Official Samsung Forums]
Should be able to find useful info somewhere.

== Disclaimer ==
Neither this WIKI/Forum nor the author(s) of articles and information provided accept any responsibility for damage that may be caused by use of the information provided. You do everything at your own risk. Be aware that "hacking" activities do void your warranty!
 Tested on UExxB70xx, LExxB65x and compatible devices only.

[[Crew List]]

MessageBoxService request format

2010-05-11T14:36:45Z

Doodlecz: Created page with ''''Description of MessageBoxService service''' To be filled in.'

'''Description of MessageBoxService service'''

To be filled in.