Launchpad has imported 2 comments from the remote bug at https://bugs.kde.org/show_bug.cgi?id=311931.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2012-12-19T12:15:57+00:00 Aleksander Morgado wrote: ModemManager >= 0.7 will come with an improved DBus interface. Documentation about this interface can be seen at: http://www.lanedo.com/~aleksander/modem-manager/api-20121005/api/ref-dbus.html In order to ease the integration of the new ModemManager, headers with enums/error definitions are also available: http://cgit.freedesktop.org/ModemManager/ModemManager/tree/include There's also a new 'libmm-glib', which helps to integrate ModemManager in glib-based applications, although not sure if this is really desirable here: http://www.lanedo.com/~aleksander/modem-manager/api-20121005/libmm-glib/ Some basic hints: * NetworkManager will expose Modems handled by the new ModemManager with a UDI prefixed with "/org/freedesktop/ModemManager1/Modem/". * SIMs are exposed as independent DBus objects. You'll need to get the SIM object path, if any, from the 'Modem' interface. PIN unlocking is done directly in the SIM interface of the SIM object. * Both 3GPP (a.k.a. GSM) and 3GPP2 (a.k.a. CDMA) modems are now handled in the same way. The new ModemManager exposes in 'CurrentCapabilities' in the modem interface which capabilities are supported. It is expected to have modems which are both 3GPP and 3GPP2 (e.g. LTE+CDMA modems). * For connecting/disconnecting, using the Simple interface is still the simplest way for now. The new ModemManager can handle multiple data bearer configurations if directly playing with creating bearer objects and connecting them independently (the Simple interface can't do that yet). * DBus interfaces are dynamic. E.g. a modem exposing the Messaging interface will have messaging (SMS) capabilities, otherwise the interface won't be exposed. * When a modem is non yet PIN-unlocked, only the Modem interface and the SIM object will be available. Reproducible: Always Can be tested with latest git master for both NetworkManager and ModemManager. Reply at: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/977761/comments/20 ------------------------------------------------------------------------ On 2013-02-22T09:54:04+00:00 Marius B. Kotsbak wrote: Hints, see how it is implemented in Gnome shell and NM-applet: https://bugzilla.gnome.org/show_bug.cgi?id=687359 https://bugzilla.gnome.org/show_bug.cgi?id=690445 Reply at: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/977761/comments/22 ** Changed in: kdenetwork Status: Unknown => New ** Changed in: kdenetwork Importance: Unknown => High -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to networkmanagement in Ubuntu. https://bugs.launchpad.net/bugs/977761 Title: Add support for using QMI protocol To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/977761/+subscriptions -- kubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
