- Jun 06, 2011
-
-
Dan Williams authored
-
Dan Williams authored
-
Aleksander Morgado authored
Implemented using a custom invoke method which doesn't call the callback, and instead calls parent disable passing the callback as argument. This fix ensures that if a modem gets removed, no invalid modem reference is passed to the parent disable, as info->modem would be set to NULL and we can detect it in the custom invoke method.
-
Aleksander Morgado authored
-
Aleksander Morgado authored
We try to avoid a memory leak when info->error is reset, as well as a second re-schedule of the info.
-
Dan Williams authored
Same USB IDs as the X060s which is driven by Longcheer, but uses the X22X command set so we have to do a little dance and make sure we don't claim the X060s here.
-
Dan Williams authored
The X200 shares the same USB VID and PID as the X060s but the X200 does not use the same AT command set; it uses the X22X plugin instead. Since both modems also report the same +GMM and +GMI responses, we have to fall back to using +GMR even though that's a pretty sketchy way to tell them apart if the firmware ever changes.
-
Dan Williams authored
Previously plugins could only stop probing, *or* stop probing and indicate support for a device. For the Alcatel X200/X060s debacle we need to stop probing and indicate that the plugin does not support the device at all.
-
- Jun 05, 2011
-
-
Dan Williams authored
-
- Jun 02, 2011
-
-
Change-Id: I1f7dabc8209d9757b573a59abb788a2346f72ad5
-
Using a SIM with a SPN, run the following command: dbus-send --system --dest=org.freedesktop.ModemManager --print-reply /org/freedesktop/ModemManager/Modems/0 org.freedesktop.ModemManager.Modem.Gsm.Card.GetSpn Change-Id: I8f36c8432f40fa4e3cb3f8c6ceef16b2bdadf2a1 Reviewed-on: http://gerrit.chromium.org/gerrit/1464 Reviewed-by: Nathan J. Williams <njw@chromium.org> Tested-by: Nathan J. Williams <njw@chromium.org>
-
BUG=chromium-os-partner:4278 TEST=Send SMS from phone (to get +... format) and from AIM-SMS gateway (to get raw-digit format). Change-Id: I36eb9f1432a432435578180dfdb315b0e7ee5744
-
Aleksander Morgado authored
-
- May 27, 2011
-
-
sms_parse_pdu(): Protocol ID doesn't actually affect decoding, so don't fret about its value. ChromeOS: Change-Id: Ia4cb20c415aed1026bb7b8dd4daa8ae53dd749e8
-
Dan Williams authored
-
- May 19, 2011
-
-
Dan Williams authored
-
- May 16, 2011
-
-
Dan Williams authored
-
- May 12, 2011
-
-
-
-
If the modem sends the same notification on more than one port, make sure we don't send a signal out to clients more than once.
-
- May 09, 2011
-
-
Dan Williams authored
-
- May 04, 2011
-
-
Dan Williams authored
Other devices from the same vendor (x220) need to be handled by the x22x plugin, so Longcheer can't just rely on the vendor ID match to know whether it should handle the modem.
-
Dan Williams authored
Sigh... it seems we do need to use major/minor/micro versioning to make various things happy and clearer. After 0.5 we'll start even/odd versioning in a more coherent manner.
-
Dan Williams authored
-
Dan Williams authored
-
- May 02, 2011
-
-
Dan Williams authored
Like the SGH-Z810/SCH-U209 which are a different chipset, don't have pseudo-ethernet ports, and just wouldn't work with this plugin.
-
- Apr 29, 2011
-
-
Aleksander Morgado authored
-
Aleksander Morgado authored
-
Aleksander Morgado authored
-
Aleksander Morgado authored
It was being used in several places with different static implementations
-
Aleksander Morgado authored
-
Aleksander Morgado authored
-
- Apr 28, 2011
-
-
Aleksander Morgado authored
-
Aleksander Morgado authored
Location API is always built
-
- Apr 27, 2011
-
-
Dan Williams authored
-
Dan Williams authored
This reverts commit 0299cf51.
-
Dan Williams authored
This reverts commit ba170602.
-
Dan Williams authored
Since translations are only used with polkit.
-
Dan Williams authored
-
Dan Williams authored
Long ago there were problems where certain Huawei devices would stop responding on various ports, and sometimes would crash randomly. The theory at the time was that touching the secondary ports made the device angry, thus the plugin simply opened the ports and listened for unsolicited messages. But if the device didn't send any during that 7 second period, MM would not detect and secondary ports at all. Plus, it was always a hack. Instead, the new theory is that the device crashes if unsolicited messages are enabled (^CURC=1), the secondary port gets touched, *and* then closed and left for a while. Fix that by turning unsolicited messages off at probe time, on when the device is enabled, and off again when the device is disabled like happens for other modems. Thus when MM first detects the modem, it turns off unsolicited messages and the serial buffer on the secondary port doesn't fill up and crash the modem. Second, this allows us to simplify the probing logic quite a bit so that we can probe all ports we find, but we still wait to probe the first port so we can turn off unsolicited messages and get hints about what port is the secondary.
-