Revert "CHROMIUM: modemmanager: Workaround for error code mapping."

This reverts commit 43a6af4a961874548354266395bf4d3b6479906b.

The error code mapping workaround is no longer needed, as the MTK
plugin already accounts for this change required in FM350 firmware
versions before 29.22.13.

TEST=Manual testing

Change-Id: I9571a1ce40b7a013791ed5a5e4b0ab8229a5211e
Reviewed-by: Andrew Lassalle <>
Commit-Queue: Aleksander Morgado <>
Tested-by: Aleksander Morgado <>
3 files changed
tree: 6d0f4ba77add6a9dac80832cae1bfdfc5c9cb8eb
  1. build-aux/
  2. cli/
  3. data/
  4. docs/
  5. examples/
  6. include/
  7. introspection/
  8. libmm-glib/
  9. libqcdm/
  10. po/
  11. src/
  12. test/
  13. tools/
  14. vapi/
  15. .editorconfig
  16. .gitignore
  17. .gitlab-ci.yml
  23. meson_options.txt
  24. NEWS
  25. OWNERS
  26. PRESUBMIT.cfg
  27. README.chromium
  30. unblocked_terms.txt


ModemManager provides a unified high level API for communicating with mobile broadband modems, regardless of the protocol used to communicate with the actual device (Generic AT, vendor-specific AT, QCDM, QMI, MBIM...).


ModemManager is a system daemon and is not meant to be used directly from the command line. However, since it provides a DBus API, it is possible to use ‘dbus-send’ commands or the new ‘mmcli’ command line interface to control it from the terminal. The devices are queried from udev and automatically updated based on hardware events, although a manual re-scan can also be requested to look for RS232 modems.


ModemManager is a DBus system bus activated service (meaning it's started automatically when a request arrives). It is written in C, using glib and gio. Several GInterfaces specify different features that the modems support, including the generic MMIfaceModem3gpp and MMIfaceModemCdma which provide basic operations for 3GPP (GSM, UMTS, LTE) or CDMA (CDMA1x, EV-DO) modems. If a given feature is not available in the modem, the specific interface will not be exported in DBus.


Plugins are loaded on startup, and must implement the MMPlugin interface. It consists of a couple of methods which tell the daemon whether the plugin supports a port and to create custom MMBroadbandModem implementations. It most likely makes sense to derive custom modem implementations from one of the generic classes and just add (or override) operations which are not standard. There are multiple fully working plugins in the plugins/ directory that can be used as an example for writing new plugins. Writing new plugins is highly encouraged! The plugin API is open for changes, so if you're writing a plugin and need to add or change some public method, feel free to suggest it!


The ModemManager and mmcli binaries are both GPLv2+. The libmm-glib library is LGPLv2+.

Code of Conduct

Please note that this project is released with a Contributor Code of Conduct. By participating in this project you agree to abide by its terms, which you can find in the following link:

CoC issues may be raised to the project maintainers at the following address: