T-Mobile Contributions

Greetings MM, I'm excited to announce that T-Mobile US is now using ModemManager/libMBIM/libQMI for our 5G Fixed Wireless products [https://www.t-mobile.com/home-internet]. We are currently the largest FWA ISP in the world with well over 3 Million subscribers, i.e., lots of ModemManager users! We

Re: T-Mobile registration trouble (USA)

>Code that was working back in July isn't working, and our IT > folks gave us new SIMs from T-Mobile. Here in the USA, T-Mobile has > instituted a requirement that a SIM be bound to a specific IMEI. I am > using the ModemSimple.connect call to connect, and I keep getting a timeout. If you are on

Re: Promoting MM for another embedded consumer distro (how to?)

ST / 5pm CET, So if any bi-weekly dates on that timeframe works for you then let me know and I'll get it arranged from there. On Thu, Sep 29, 2022 at 2:35 PM matthew stanger wrote: > Dylan, > >> What is the problem here? Could you elaborate? > > > The desire is to have the fa

Re: Promoting MM for another embedded consumer distro (how to?)

Dylan, > What is the problem here? Could you elaborate? The desire is to have the fastest power on to cell connection. Folks point out the probing times for modem detection as an example of unneeded/wasted performance vs. a custom solution that already knows the modem/API/dev's that it's

Promoting MM for another embedded consumer distro (how to?)

Hey MM, One time contributor, long time lurker here. TLDR: I'm seeking input to help champion MM as a core cell management component to a large firmware collaborations body. If successful, IMHO, it'd have huge benefits to WWAN/Linux wireless & MM as it'd bring in a lot of official support, more

Re: Built-in plugins?

> > But if you wanted to, you > could pass --enable-plugins=X,Y,Z or something and end up with a > smaller binary. I like that. It put's the optimization in the hands of the builder which seems more than fair to have integrator's figure out what goes in or out & dependency chains. It also will

Re: Where are you using ModemManager?

Hi, > If you or your company are using ModemManager in a professional > product, would you mind sharing your experience in the mailing list? > Not mine but worth mentioning on this thread, ModemManager/NetworkManager stack is being used in the Librem 5 Phone to provide voice & data:

Re: Where are you using ModemManager?

At Trimble Inc. we're using MM for the SNM941 ( https://construction.trimble.com/products-and-solutions/snm941-connected-site-gateway ) which is an Internet gateway for construction equipment. The SNM941 helps sync design files between the engineering office and equipment operators, collects

Re: ModemManager support on ARM?

I have it running on an ancient ARMv5 220Mhz processor :) On Mon, Mar 25, 2019 at 10:22 AM Stelling2 Carsten < carsten.stelli...@goerlitz.com> wrote: > Hi Ajay, > > Yes, MM works on other platforms like ARM too. We use it successfully on > i.MX6 (ARMv7). > If you use the Yocto Project for the

Re: Planning to add a PCIe(not in USB protocol) device

Mork wrote: > matthew stanger writes: > > > > I thought > > the (Librem 5 Linux Phone) ( https://puri.sm/products/librem-5/ ) was > > already using MM with PCIe? I know that's their plan. > > Forgot to comment on this. They use a SIMCom SIM7100E o

Re: Planning to add a PCIe(not in USB protocol) device

Is this thread implying the MM doesn't support PCIe in general? I thought the (Librem 5 Linux Phone) ( https://puri.sm/products/librem-5/ ) was already using MM with PCIe? I know that's their plan. On Fri, Mar 15, 2019 at 4:01 AM Bjørn Mork wrote: > 王道之 writes: > > > Intel have the plan to

Re: Connect Cinterion modem with SWWAN fails with unknown error

> > I have the same issues with the ELS61 modem. Did you make any progress > regarding > this issue? I've had a long back-and-forth with the vendor but basically we still can't get the demo board reliably working with basic AT commands. Could the GPRS/AutoAttach setting (see AT^SCFG) have

Re: connect using a specific PDP CID

> > I’m trying to use ModemManager 1.8.2 with a Verizon LTE Cat-M1 modem. Aleksander wrote this for my team for this very case. I've re-based it to 1.8.2 so it should go on clean. We should work on the new API at some point... I really think the patch here is great to be honest. Again we are

Re: Connect Cinterion modem with SWWAN fails with unknown error

ed debug output of ModemManager). This > happens endlessly in a loop. > > Do you have any clue what is happening? > > Thanks, > > Ana > > > > On 14/02/19 16:33, matthew stanger wrote: > > You need to call "common_create_bearer (task);" before the

Re: Analysing boot time

> > But how does systemd measure the "boot time" of each? Is it only the > time needed by the daemon to be exposed in DBus? Or what? For 'Type=dbus' services, which most of the distro's use in MM's service file. Systemd will consider the unit started immediately after the main service process has

Re: Connect Cinterion modem with SWWAN fails with unknown error

> > You need to call "common_create_bearer (task);" before the return here A true dark knight, thanks Aleksander! Ana, try this instead: >From 43c8870b7478f3e5ccdb70a3fc89edddcef96d67 Mon Sep 17 00:00:00 2001 From: Matthew Stanger Date: Thu, 14 Feb 2019 08:28:14 -0700 Subje

Re: Connect Cinterion modem with SWWAN fails with unknown error

Give this a try (note this is just a hack to tmp disable the SWWAN feature & hopefully I get the ELS61 soon): Branched from 1.8.2: >From 63f9ac8a0db1d8902dd7bef329f441ef4ea86c6b Mon Sep 17 00:00:00 2001 From: Matt Stanger Date: Wed, 13 Feb 2019 20:18:00 -0700 Subject: [PATCH] mm-bb-m-cinterion:

Re: automatic APN selection

Tim & Belisko, My team still has a feature like this on our product road map. Right now we've been waiting for the next FW release, which has as part of our analytics suite, the ability to gather basic APN & context info(& we have presence in ~55+ countries). We plan on cross referencing this

Re: Connect Cinterion modem with SWWAN fails with unknown error

There are a few things we can do from here: 1. I can give you a simple patch to turn off SWWAN so you can just use ppp. This doesn't really help the greater good but will get you going on the issue. 2. You'd be the first out of the EU but I have seen carriers(in Asia) requiring LTE

Re: Connect Cinterion modem with SWWAN fails with unknown error

Hi Ana, There are quite a few things that catch my eye here. First there are many AT cmds that need to be updated for this specific modem, many proprietary AT cmds have changed. Still the SWWAN connection interface is pretty basic and as-is I think it should be able to work. It'd be great if you

Re: Connect Cinterion modem with SWWAN fails with unknown error

Hi Ana, Can you trying running ModemManager with the 'log-level' set to DEBUG and shooting me the results. System | device: '/sys/devices/platform/ahb/50.ohci/usb1/1-2' On a most likely unrelated note, if your bring up a product heads up that you'll have trouble with USB 1.x(ohci)

Re: [review] LTE attach config and status

re those in CID=1" then that would need to be tied to a > specific device. > > Didn't Verizon require to use CID=4 for the same purpose in their > modems? (or something like that) @matthew stanger what was that about? > I recall a patch were we allowed specifying the CID to use explicitly

Re: [review] LTE attach config and status

This is great to have and I'm seeing more carriers this is occurring in as well (Vzw, Japan & S. Korea). To be honest, this would be a much better way to get started with modem auto configure than APN guessing games :) On Fri, Nov 23, 2018 at 10:02 AM Aleksander Morgado <

Automatic APN

My engineering team has been looking at implementing automatic APN detection and I wanted to reach out and see if anyone has thoughts on where(MM/NM) or if this would belong. We're looking at using the Android APN/carrier lookup table via MCC/MNC & IMEI.

Re: Telit LE910 V2, cdc_ncm and systemd

Hi Carsten, If it comes to implementing the NCM protocol, it's nice to hear that you > will guide me :-) Aleksander gave me some guidance for a similar situation and what you want to do here is going to be very similar to the 'mm-broadband-bearer-cinterion.c' & 'mm-broadband-bearer-huawei.c'

Re: The loading order of plugins

? On Tue, Oct 9, 2018 at 3:51 AM Ken CJ Chou wrote: > Hi, > > matthew stanger 於 2018年10月9日 週二 上午2:48寫道： > >> Hi Ken, >> >> Given the datasheet Dan linked it seems like that modem family does >> support the 'SWWAN' connection interface type. Given that

Re: The loading order of plugins

Hi Ken, Given the datasheet Dan linked it seems like that modem family does support the 'SWWAN' connection interface type. Given that I'd expect basic connection attempts to work. Can you enable MM debugging and post the logs of a connection attempt? I'm sure we can get the plugin to support this

Re: Preferred way to get signal information

Hi Nick, If your using c/c++ consider looking into the library ModemManager exposes, this is how mmcli works (https://cgit.freedesktop.org/ModemManager/ModemManager/tree/libmm-glib). It handles the dbus calls for you and just exposes some nice c code wrappers. In your case you should look at how

Re: HP lt4120 failing to make single-stack connections on LTE using MM

> > it only seems to happen with the single-stack IP types (both IPv4- and > IPv6-only), never with dual-stack. >From what I've seen many carriers (and subsets of towers) don't support every IP type, especially IPv6. On Tue, Sep 4, 2018 at 6:17 AM Aleksander Morgado wrote: > Hey, > > > > > I

Re: [PATCH] mm-modem-helpers-cinterion: update band table for PLS8-J

+1 On Mon, Jul 30, 2018 at 9:26 AM, Reinhard Speyerer wrote: > The default AT^SCFG="Radio/Band" value for Cinterion PLS8-J devices is > "16819472". Add UMTS band 19 and LTE band 19 entries based on the > information given in the PLS8 datasheet. > --- >

Re: [RFC] Deprecate SubscriptionState?

We've really been wanting to get it working better for our customers, but honestly your summary is true. Carriers aren't supporting hooks to reliably to get the information. I personally haven't seen a 3GPP command in the data sheets I have to get the info either. If that changes I'd be the first

mmcli man page update for bands

Hi, I noticed the man page for mmcli had the string incorrect for setting bands. https://www.freedesktop.org/software/ModemManager/man/1.8.0/mmcli.8.html All versioned pages show: --set-bands=[BAND1|BAND2|...] it should be: --set-current-bands=[BAND1|BAND2|...] The string was

Re: URC mistaken for solicited responce

> > On Fri, May 18, 2018 at 11:03 PM, matthew stanger <stange...@gmail.com> wrote: > > You're good at what you do mate, thanks! You want a patch? I think just > > might be our slow antique hardware though to be honest. > > > > I'll gladly accept a p

Re: URC mistaken for solicited responce

dbus-org.freedesktop.ModemManager1.service: Main process exited, code=dumped, status=6/ABRT 2018-04-25T07:36:11.278862 systemd[1]: dbus-org.freedesktop.ModemManager1.service: Unit entered failed state. 2018-04-25T07:36:11.300202 systemd[1]: dbus-org.freedesktop.ModemManager1.s

Re: URC mistaken for solicited responce

> > +CIND shouldn't be any URC +CIND isn't (polled by mm-broadband-modem.c), but the +CIEV that follows it is. Cinterion's ^SIND turn's on the +CIEV URC's. Which means the setting AT cmd doesn't match the AT URC response. Lovely huh, not sure if that makes a difference. On Fri, May 18, 2018 at

URC mistaken for solicited responce

Hey Aleksander, I found this in our logs. As you can see we get a URC right after a solicited request that's polled. This causes a connection reset. 2018-04-25T07:35:19.155738 ModemManager[1797]: (ttyACM1): --> 'AT^SWWAN?' 2018-04-25T07:35:20.317705 ModemManager[1797]: (ttyACM0): <-- '+CIEV:

Modem hotplug behavior inconsistent

Hey Aleksander, I'm see something odd that I think may be related to the new device filter policy stuff and before digging into it too far I wanted to run it by you and see if this sounds like an issue. When running 'mmcli -m 0 -e' the modem is not flagged as hotplugged (enabling_started(),

Re: PDP specific carriers

> > Sadly I have less and less free time every day, so it's hard to keep up > with everything... :/ Help would be much appreciated I hear you man :), will do if we produce anything in this area. On Fri, Nov 3, 2017 at 2:19 PM, Aleksander Morgado wrote: > > > > You

Re: Roadmap for next stable 1.8?

> > I've been a bit nervous about the weight of the GTask migration changes > but, to be fair, I don't think I've encountered any issues with them. We've been running off '689dad9f6e4a08c5f68a02363703d58f6d9fbadf' which had all the GTask items, for the Cinterion plugin, and it's been very

PDP specific carriers

Aleksander, You did the out-of-band patch for specifying PDP context in the bearer to satisfy Verizon requirements and we didn't end up getting that stuff back upstream since it seemed really too specific for general MM use. We just got info back that major Japaneses carriers, NTT DOCOMO &

Re: RFC: New device filter policies

Aleksander, Following the discussion regarding Debian wanting to patch > ModemManager to avoid unnecessary probing of non-modem TTYs This patch was great for us. I went ahead and re-based it on top of 1.6.10 and it has been running on the PLS8-X/E without issue. I used the white-list option &

Re: [PATCH 1/4] iface-modem: consolidate signal quality and access tech polling

LGTM, for syntax & control flow. Like the idea but I'm biased on this one ;) On Sun, May 21, 2017 at 1:49 PM, Aleksander Morgado < aleksan...@aleksander.es> wrote: > Plugins have two ways to update signal quality and access technology > values: via unsolicited messages or via polling

Re: [PATCH 1/2] log: new --log-func-loc option to enable function location in logs

> > ...do quite often find the function location useful. But I don't mind > patching it back in for myself if the consensus is to remove it for > mainstream. When I was starting out I also found it very helpful, but I think if there was a patch or something for others off to the side then it's

Re: [PATCH] api: allow specifying the PDP CID to use

Logic is sound. the user ends up changing the CID that the device uses for default LTE > attachment (e.g. CID=1 for Qualcomm or CID=16 for Huawei ME909u) Wouldn't this still end up being okay for users too. Once they realize they're using the wrong CDC & switch pdp-cid (& the lte back off timer

Re: Cinterion plugin (in)compatibilities

Hi Colin, I'm not a core maintainer but I've recently done some work on the Cinterion plugin. I've been actually hoping to do some more but have been overwhelmed the last 2 months with person life oblations. Anyways the next patch I'll be submitting in fact is for Cinterions updated GPS commands.

Re: Leveraging GPS in MC7700

Hi Adam, First check to make sure you can get GPS location and not just 3gpp location, i.e. location from just the cell tower. Run 'mmcli -m 0 --location-status' and check capabilities. You'll want to see something like: /org/freedesktop/ModemManager1/Modem/0

Re: [RFC] stanger/cinterion branch

Yes sorry that is what I was referring to. That really helps to know. We are good on my end then. On Thu, Jan 5, 2017 at 11:30 AM, Aleksander Morgado < aleksan...@aleksander.es> wrote: > On Thu, Jan 5, 2017 at 6:29 PM, matthew stanger <stange...@gmail.com> > wrote: > > O

Re: [RFC] stanger/cinterion branch

It looks good & we have the bug in on the only thing I found. Only thing I haven't been able to test is SIM's with User/Pass. Does anyone out there have one they are able to test with? We have reached out to our major carrier rep's here (in North America) and none of them can provide this tech, it

Re: [RFC] stanger/cinterion branch

hu, Dec 22, 2016 at 2:10 AM, Aleksander Morgado < aleksan...@aleksander.es> wrote: > On Wed, Dec 21, 2016 at 5:14 PM, matthew stanger <stange...@gmail.com> > wrote: > >> What's the output of the SWWAN status check when the SIM is gone? is > >

Re: [RFC] stanger/cinterion branch

over-temp or voltage info > It was just putting it in logs so we would know for field failures. Nothing special. Other than that this looks solid. Exciting times! On Tue, Dec 20, 2016 at 4:08 AM, Aleksander Morgado < aleksan...@aleksander.es> wrote: > Hey! > > On Sat, Dec 17, 20

Re: [RFC] stanger/cinterion branch

Sorry for the slowness, I'm going to be grid-locked for the next 5 weeks due to personal commitments so I'll be slow :( , very sorry. Code wise everything looks good, maybe I'd take out the goto's for if/else and remove the unused mm_bb_b_cinterion_init() function, but that's trivial opinion. A

GPS blocked by enable

Hi all, I was just wondering if I could get the background on why the GPS flow requires enable. It's causing us pain with unit's that don't have a SIM inserted but which would still want to collect GPS data. Since we can't enable without a SIM, then we can't get GPS. I'm sure I can hack something

Re: Fwd: Cinterion plugin patch

Mon, Nov 28, 2016 at 7:03 PM, matthew stanger <stange...@gmail.com> > wrote: > > >> Ah, yeah. If the plugin does its own logic to select which CID to use, > > >> it should not rely on the parent's connection status check. In our > > >> case, though, I think

Re: Fwd: Cinterion plugin patch

em to provide you one so hopefully that will work out and you'll have one soon. On Mon, Nov 28, 2016 at 9:29 AM, Aleksander Morgado < aleksan...@aleksander.es> wrote: > On Sun, Nov 27, 2016 at 4:27 AM, matthew stanger <stange...@gmail.com> > wrote: > > Sorry I sent that last

Re: Fwd: Cinterion plugin patch

ount is 2 (open) The code works on my PLS8-X after testing. Cheers, On Sat, Nov 26, 2016 at 7:47 PM, matthew stanger <stange...@gmail.com> wrote: > Code looks awesome (*¬*), so much to learn for me. A few comments which > are all trivial and really don't need to be in

Re: Fwd: Cinterion plugin patch

Code looks awesome (*¬*), so much to learn for me. A few comments which are all trivial and really don't need to be included but in attempt to be as detailed as you > > > * The PDP context mapping is as suggested by Cinterion, although it looks > like > * this isn't strictly enforced by the

Re: Fwd: Cinterion plugin patch

t; Gutschein einl|sen\0A4 Pack Manager\0A7 Tarifinfo\0A8 Hilfe",15 > > > > Any idea if this has any impact on how ModemManager handles USSD in > > this device? Or is this only an issue to the consumer of the USSD > > responses? > > What I think curious is that 0x

Re: Fwd: Cinterion plugin patch

AM, matthew stanger <stange...@gmail.com> wrote: > Alexsander, > > I'm traveling right now will test as soon as I get back tomorrow. > > On Nov 24, 2016 2:58 AM, "Aleksander Morgado" <aleksan...@aleksander.es> > wrote: > >> Hey Matthew, >>

Re: Fwd: Cinterion plugin patch

Alexsander, I'm traveling right now will test as soon as I get back tomorrow. On Nov 24, 2016 2:58 AM, "Aleksander Morgado" wrote: > Hey Matthew, > > On Wed, Nov 23, 2016 at 10:28 PM, Aleksander Morgado > wrote: > > Great work! it looks

Re: Fwd: Cinterion plugin patch

onse so we don't have to > assume that > > + * zero length response means 'OK' or am I doing it wrong?... */ > > +else if (!g_utf8_strlen (response, 100)) > > +*result = g_list_append (*result, GINT_TO_POINTER(0)); > > No need for that g_utf8_strlen(); if you get

Re: PolicyKit authorization error

016-10-24 at 13:43 -0600, matthew stanger wrote: > > Hi all, > > > > I just upgraded our little box with MM 1.6 to systemd 230 and I'm now > > getting a PolicyKit error from mmcli. The issue only happens about 1 > > out of > > 10 times after a reboot. The other 9 ti

PolicyKit authorization error

Hi all, I just upgraded our little box with MM 1.6 to systemd 230 and I'm now getting a PolicyKit error from mmcli. The issue only happens about 1 out of 10 times after a reboot. The other 9 times everything is fine, weird. When I do a simple connect I get the error "PolicyKit authorization

Re: Modem Status State vs. Bearer Status Connected

016-09-08 at 11:27 -0600, matthew stanger wrote: > > I'm trying to understand the difference of what these properties tell > > the > > user? I want to make sure I don't update the status of one in the > > wrong way > > because of my interpretation. > > If

Modem Status State vs. Bearer Status Connected

I'm trying to understand the difference of what these properties tell the user? I want to make sure I don't update the status of one in the wrong way because of my interpretation. Thanks ___ ModemManager-devel mailing list

Re: Cinterion plugin patch

:44 -0600, matthew stanger wrote: > > Attached is the patch, gmail is the culprit. > > Thanks! > > A couple general comments. > > If it's possible, could the GPS stuff be split out into a separate > patch? Makes for easier review of both that and the SWWAN stuff. >

Help with *-port-type.rules

I'm trying to fix the GPS for the Cinterion plugin for the PLS8-X and I'm just a little confused about the 77-mm-cinterion-port-types.rules file. I see it sets a uDev tag based on idVendor and idProduct, of which idProduct is wrong for this new modem. I'm just not quite sure where this file is

mm_iface_modem_is_cdma_only

Hi, I was just finishing up a patch for swwan support in the Cinterion plugin. During my testing I noticed that with the PLS8-X & no SIM card inserted mmcli gives a timeout error instead of a no-sim error. I traced it back to 'mm-inface-modem.c' where there is a bitwise operation: return

Prevent MM from probing serial port

Hi, Is there an easy way from keep MM from probing the serial port? ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel

Setting up a data connection mmcli with PLS8-X

I'm trying to get MM to work with the the Cinterion PLS8-X on Linux 3.14. I've tried using two different methods (ttyACM vs. qmi_wwan) but can't get to the end state of making a data connection and was hoping someone could tell me which way would be best and maybe hint at what I might be doing