Difference between revisions of "OmaDm"
| Line 21: | Line 21: | ||
system_settings.info (contains localeCountry and localeLanguage settings) | system_settings.info (contains localeCountry and localeLanguage settings) | ||
tmp (empty directory) | tmp (empty directory) | ||
| + | |||
| + | If you run "OmaDm -syncdata", a couple of files appear: | ||
| + | |||
| + | DmTree.backup.xml | ||
| + | DmTree.xml | ||
| + | |||
| + | On a Veer, you also get the following error message: | ||
| + | |||
| + | [RdmInitCarrier: 423]: Unrecognized carrier ATT | ||
| + | |||
| + | The OmaDm binary seems to have support for Sprint, bell, ROW, and Verizon only. We're not sure whether this is a problem for AT&T or other carrier devices, but we'll assume that it is intentional for the moment. | ||
Revision as of 04:38, 8 July 2011
This page will document knowledge about OmaDm. Note that some previous research of the over-the-wire behaviour of OmaDm has been done at Update_Service_Trace.
OmaDm seems to be involved in carrier provisioning and webOS OTA updates. Its working directory seems to be /var/lib/software.
It is called from UpdateDaemon, with the following arguments (found by using strings on the UpdateDaemon binary):
OmaDm -syncdata OmaDm -revert_tree OmaDm -set_domain OmaDm -client OmaDm -task OmaDm -server OmaDm -prepare OmaDm -prepare %X OmaDm -report_results
If you doctor and boot a device with the UpdateDaemon and OmaDm binaries disables, you get the following directory contents:
ModemFiles (empty directory) SessionFiles (empty directory) system_settings.info (contains localeCountry and localeLanguage settings) tmp (empty directory)
If you run "OmaDm -syncdata", a couple of files appear:
DmTree.backup.xml DmTree.xml
On a Veer, you also get the following error message:
[RdmInitCarrier: 423]: Unrecognized carrier ATT
The OmaDm binary seems to have support for Sprint, bell, ROW, and Verizon only. We're not sure whether this is a problem for AT&T or other carrier devices, but we'll assume that it is intentional for the moment.