Transfer progress API

Intended for the Messages app, so that it can show MMS
send/receive progress.

D-Bus interface for the list of transfers goes like this:

<interface name="org.nemomobile.MmsEngine.TransferList">
    <method name="Get">
        <arg name="list" type="ao" direction="out"/>
    </method>
    <signal name="TransferStarted">
        <arg name="path" type="o"/>
    </signal>
    <signal name="TransferFinished">
        <arg name="path" type="o"/>
    </signal>
</interface>

D-Bus interface for individual transfers (identified by path):

<interface name="org.nemomobile.MmsEngine.Transfer">
    <method name="GetAll">
        <arg name="version" type="u" direction="out"/>
        <arg name="bytes_sent" type="u" direction="out"/>
        <arg name="bytes_to_send" type="u" direction="out"/>
        <arg name="bytes_received" type="u" direction="out"/>
        <arg name="bytes_to_receive" type="u" direction="out"/>
    </method>
    <method name="EnableUpdates">
        <!-- 1 - send, 2 - receive, 3 - both -->
        <arg name="flags" type="u" direction="in"/>
        <arg name="cookie" type="u" direction="out"/>
    </method>
    <method name="DisableUpdates">
        <arg name="cookie" type="u" direction="in"/>
    </method>
    <method name="GetInterfaceVersion">
        <arg name="version" type="u" direction="out"/>
    </method>
    <method name="GetSendProgress">
        <arg name="bytes_sent" type="u" direction="out"/>
        <arg name="bytes_to_send" type="u" direction="out"/>
    </method>
    <method name="GetReceiveProgress">
        <arg name="bytes_received" type="u" direction="out"/>
        <arg name="bytes_to_receive" type="u" direction="out"/>
    </method>
    <signal name="SendProgressChanged">
        <arg name="bytes_sent" type="u"/>
        <arg name="bytes_to_send" type="u"/>
    </signal>
    <signal name="ReceiveProgressChanged">
        <arg name="bytes_received" type="u"/>
        <arg name="bytes_to_receive" type="u"/>
    </signal>
    <signal name="Finished"/>
</interface>

Progress signals are not emitted unless there's at least one
D-Bus client expressed an interest by calling EnableUpdates
with appropriate flags. Request for updates can be revoked
with DisableUpdates. This complicates things a bit but I think
it's worth the trouble.

See merge request !9

Some tests did't delete temporary directories.

Processing of downloaded messages is now finished before the next
download is started.

MMS_CONNMAN_NEMO defined from the command line conflicted with the macro
defined in mms_connman_nemo.c

ligofono 1.0.11 does it for us.

This way it will end up in the tarball generated by MMS Logger app,
and it's generally useful for debugging.

Drop inactive connections

Otherwise mms_connman_nemo_open_connection() may keep on returning
the same dead connection.

See merge request !7

See merge request !6

This error means that operation should be retried.

Pass "user request" flag to the connection manager

It's not being used at the moment but we may need it soon.

See merge request !5

It's not being used at the moment but we may need it soon.

Fix "auto" voice SIM behavior

mms-engine was interpreting "auto" default voice sim literally,
as an IMSI. Instead, the default should be IMSI of the SIM
associated with the default voice modem (if it's not empty).

See merge request !4

The default should be IMSI of the SIM associated with the
default voice modem (if it's not empty)

It can still be overwritten by MMS_ENGINE_VERSION macro, it's just that
now we have a reasonable default for it.

Proper support for multiple SIMs

We need to use `org.nemomobile.ofono.ModemManager` API to notify
ofono that we need to download MMS so that it enables mobile data
for the appropriate SIM. If it's different from the currently
selected data SIM, then connman will be prevented from using
mobile data while MMS download is taking place.

See merge request !3

We need to use org.nemomobile.ofono.ModemManager API to notify ofono
that we need to download MMS so that it enables mobile data for the
appropriate SIM. If it's different from the currently selected data SIM,
then connman will be prevented from using mobile data while MMS download
is taking place.

Fix MMS break with latest devel

Recently updated MMS ofono integration module wasn't waiting for ofono client interfaces to finish initialization and was deciding that SIM card is missing. That's why it worked when mms-engine is started by MMS Logger and didn't work under normal circumstances (when mms-engine is started by dbus-daemon)

See merge request !2