Here's a code sample binding to SMS Inbox services: bindings:Ĭ_smsInbox1 -> smsInboxService.le_smsInbox1 But, the application can also explicitly delete messages if it doesn't need them anymore.Īll the functions of this API are provided by the smsInboxService application service. This way, the message box contents will be kept up to date automatically by the SMS Inbox Service, even when the user app is slow to start, is stopped while it is being updated, or is being restarted to recover from a fault.Ī message box works as a circular buffer, when the message box is filled, the older messages are deleted to free space for new messages. The creation of SMS inboxes is done based on the message box configuration settings (cf. All files are saved into the file system in the directory /mnt/flash/smsInbox. The message box is a persistent storage area.
This process is the same when the SMS message storage is the device's storage area (ME - Mobile Equipment). This mechanism keeps the SIM always empty in order to guarantee the reception of SMS messages. Message Storage" folder and deleted from the SIM. Moreover, every new received SMS message is automatically copied into the "Inbox Then, the process frees automatically the SIM content. Message Storage" folder allocated in the root file system of the device. In fact, at device's startup or when a SIM is inserted, the SIM content is copied into the "Inbox The SMS Inbox Service handles the resource arbitration for the user app: the message reception is always guaranteed, for example the user app doesn't have to worried about freeing space in the SIM (or device's storage area) when it is full. missing messages while being updated or restarted.conflicting with other applications that also receive SMS messages.Legato provides an SMS Inbox service to allow apps to receive SMS messages through their own, private message box, without: 3rd-party customer applications need to access to SMS messages at anytime without worrying how the resources are managed.