diff options
author | Aleksander Morgado <aleksander@aleksander.es> | 2014-09-27 19:18:08 +0200 |
---|---|---|
committer | Aleksander Morgado <aleksander@aleksander.es> | 2014-09-27 19:18:08 +0200 |
commit | 6b554dcf742c4b426365406b50c84b36e9caa559 (patch) | |
tree | f5b7c39ffa2453421c231d6e20681378e3b89b8b | |
parent | 3a7fbf3adf8433d2057348c12f95d837b1995c78 (diff) | |
download | ModemManager-aleksander/zte-prefer-ussd-unencoded.tar.gz |
zte: use always unencoded USSD messagesaleksander/zte-prefer-ussd-unencoded
Some ZTE modems, like the MF180 (VID 0x19D2 PID 0x2003), will reply "OK" always
to both encoded and unencoded tries of USSD message sending, even if the encoded
one may fail afterwards.
So, instead of the base MMBroadbandModem logic where we try to look for the type
to use (first encoded is tried and then unencoded), restrict USSD to the
unencoded version always.
-rw-r--r-- | plugins/zte/mm-broadband-modem-zte.c | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/plugins/zte/mm-broadband-modem-zte.c b/plugins/zte/mm-broadband-modem-zte.c index 17658e003..c62c9e81a 100644 --- a/plugins/zte/mm-broadband-modem-zte.c +++ b/plugins/zte/mm-broadband-modem-zte.c @@ -728,6 +728,7 @@ mm_broadband_modem_zte_new (const gchar *device, MM_BASE_MODEM_PLUGIN, plugin, MM_BASE_MODEM_VENDOR_ID, vendor_id, MM_BASE_MODEM_PRODUCT_ID, product_id, + MM_BROADBAND_MODEM_USSD_TYPE, MM_BROADBAND_MODEM_USSD_TYPE_UNENCODED, NULL); } |