| Age | Commit message (Collapse) | Author |
|---|
|
|
|
mmcli is GPLv2+; that's what --version has always said and that's what the
README in ModemManager sources specifies:
License.
The ModemManager and mmcli binaries are both GPLv2+.
The libmm-glib library is LGPLv2+.
|
|
|
|
|
|
|
|
Both the ModemManager daemon and the mmcli will now include `libmm-glib.h' only.
We also handle two new special `_LIBMM_INSIDE_MM' and `LIBMM_INSIDE_MMCLI'
symbols, which if included before the `libmm-glib.h' library allow us to:
* Don't include the libmm-glib high level API in the ModemManager daemon, as
the object names would clash with those in the core.
* Define some of the methods of helper objects to be included only if compiling
ModemManager daemon or the mmcli.
|
|
This switch can be run along with the `--messaging-create-sms' action, in order
to include in the SMS the data as given in the file specified by the new switch.
E.g.:
$> sudo mmcli -m 0 \
--messaging-create-sms="number='1234567890'" \
--messaging-create-sms-with-data=file.txt
In this case, the SMS properties string cannot contain a 'text' field.
|
|
$> sudo mmcli -m 1 --messaging-status
/org/freedesktop/ModemManager1/Modem/1
----------------------------
Messaging | supported storages: 'sm, mt, me, sr'
| default storage: 'me'
|
|
Just for consistency with other interfaces, which also provide interface
specific prefixes in their mmcli actions.
|
|
Currently shows the list of supported SMS storages.
|
|
By default 30s will be used for every operation.
|
|
Don't rely on the lock status, as the modem may say it requires SIM PIN 2, but
we're allowed to run most operations even with that unlock required.
|
|
Do not try to perform feature/capability specific actions if we're still
unlocked, as the modem didn't yet export the feature/capability specific
interface.
The only interfaces expected while modem is unlocked are the Modem and Simple
interfaces, as well as the SIM interface in the SIM object, of course.
|
|
An SMS must be first created with the Messaging interface, and then sent using the
Send() method from the SMS-specific interface.
|
|
|
|
|
