Re: [PATCH] broadband-modem-mbim: parse nw_error in register_state_set_ready only if MBIM_STATUS_FAILURE

Hey! See comments below. On Thu, Mar 21, 2019 at 1:14 PM Lech Perczak wrote: > > Some modems (Namely: Telit LE910 V2) report nonzero NwError code, > outside of 3GPP TS 24.008 - in "register-state set command-done" response, > while status code equals MBIM_STATUS_ERROR_NONE. > In such cases netwo

Re: How other applications use the ports that occupied by MM

> We're looking at using the AT port to get a few status values that don't > appear to be readily available from QMI. One we need in particular is device > temperature (there's a hardware failure condition that manifests as a very > high temperature value). Of course any hints on how to pull th

Re: How other applications use the ports that occupied by MM

> > Yeah, mixed feelings from me too. I guess before we do that, can we ask > what commands people want to use? I'd rather it not be used a short > circuit for stuff that could be fixed in MM or implemented fairly > easily for a device. That's my only reservation, that having it may > reduce the in

Where are you using ModemManager?

Hey! If you or your company are using ModemManager in a professional product, would you mind sharing your experience in the mailing list? Even generic descriptions would be appreciated, but if you can share also platform details that would be great. Of course, only asking for information that can

Re: Random MM and/or qmi-proxy hang?

> > > > > > This is RHEL7 so I’m using the 1.6 branch of MM and 1.18.0 libqmi; for MM > > > I > > tried building our own 1.16.4 when we suspected MM being the core issue, > > with no change in behavior. > > > > > > > Hard to say what the issue is, but you're really using somewhat old > > versions

Re: AT&T QMI Cancel Location Handling

On Thu, Mar 28, 2019 at 3:05 PM John Marrett wrote: > > Aleksander, > > >>> What libqmi version are you using? If you're using 1.22.0, please >>> update to 1.22.2 and retest. >>> > > Sorry for the delay in getting back to you and the list. With 1.22.2 we see > debug messages but also see a change

Re: [review] DW5821e: always allow GPS unmanaged

Hey > Please see the following MR to allow controlling the "unmanaged GPS" > source even if "raw/nmea GPS" sources are already being used, > applicable to the DW5821e where QMI LOC is used for "raw/nmea" instead > of a TTY. > > https://gitlab.freedesktop.org/mobile-broadband/ModemManager/merge_req

Re: [review] Carrier config support and fwupd integration

Hey! > The following MR adds support for reporting the current carrier config > in use, and also implements automatic carrier config switching based > on QMI PDC, initially done for the DW5821e. > https://gitlab.freedesktop.org/mobile-broadband/ModemManager/merge_requests/66 > > A single modem may

[review] A-GPS MSA/MSB support

Hey, The following MR updates the Location interface in order to allow enabling MSA or MSB A-GPS. Until now the A-GPS source was bound to trying MSA only, there was no way to enable MSB A-GPS. https://gitlab.freedesktop.org/mobile-broadband/ModemManager/merge_requests/84 Comments welcome! -- A

Re:

On Wed, Apr 3, 2019 at 8:07 AM Pavlin Georgiev wrote: > > Supported modem Nokia 21M-02 > Hi > > When I open the web page with supported modems in ModemManager > https://www.freedesktop.org/wiki/Software/ModemManager/SupportedDevices/ > and I check for "Nokia 21M-02" > then I see that the device is

Re: Supported modem by ModemManager - Zoom 4595

On Wed, Apr 3, 2019 at 8:23 AM Pavlin Georgiev wrote: > > Hi > > I report that modem Zoom 4595 from Omega Technologies > is supported by ModemManager. > > Please, add this modem to the list of supported modems here: > https://www.freedesktop.org/wiki/Software/ModemManager/SupportedDevices/ > Adde

Re: Supported modem by ModemManager - Sierra Wireless EM7345

On Wed, Apr 3, 2019 at 8:27 AM Pavlin Georgiev wrote: > > Hi. > > I report that modem Sierra Wireless EM7345 > is supported by ModemManager. > > Please, add this modem to the list of supported modems here: > https://www.freedesktop.org/wiki/Software/ModemManager/SupportedDevices/ > > Thank you. >

Re: Supported modem by ModemManager - Sierra Wireless EM8805 (DW5570e)

On Wed, Apr 3, 2019 at 8:38 AM Pavlin Georgiev wrote: > > Hi. > > I report that modem Sierra Wireless EM8805 > is supported by ModemManager. > > Please, add this modem to the list of supported modems here: > https://www.freedesktop.org/wiki/Software/ModemManager/SupportedDevices/ > Added, thanks

Re: Supported modem by ModemManager - Sierra Wireless MC7455

On Wed, Apr 3, 2019 at 12:19 PM Pavlin Georgiev wrote: > > Hi. > > I report that modem Sierra Wireless MC7455 > is supported by ModemManager. > > USB ID 1199:9071 > > Please, add this modem to the list of supported modems here: > https://www.freedesktop.org/wiki/Software/ModemManager/SupportedDevi

Re: Supported modem by ModemManager - Sierra Wireless EM7355

On Wed, Apr 3, 2019 at 1:44 PM Pavlin Georgiev wrote: > > Hi. > > I report that modem Sierra Wireless EM7355 > is supported by ModemManager. > > USB ID 1199:9041 > Looks like the attached mmcli.log is from a MC7455? > Please, add this modem to the list of supported modems here: > https://www.fre

Re: Supported modem by ModemManager - Huawei K3765

On Wed, Apr 3, 2019 at 1:59 PM Pavlin Georgiev wrote: > > Hi. > > I report that modem Huawei K3765 > is supported by ModemManager. > > USB ID 12d1:1465 > > Please, add this modem to the list of supported modems here: > https://www.freedesktop.org/wiki/Software/ModemManager/SupportedDevices/ > Add

Re: Supported modem by ModemManager - Qualcomm, Inc. Siemens SG75

On Wed, Apr 3, 2019 at 2:18 PM Pavlin Georgiev wrote: > > Hi. > > I report that modem Qualcomm, Inc. Siemens SG75 > is supported by ModemManager. > > USB ID 05c6:6000 Qualcomm, Inc. Siemens SG75 > > Please, add this modem to the list of supported modems here: > https://www.freedesktop.org/wiki/Sof

Re: Supported modem by ModemManager - Sierra Wireless EM7355

Hey, On Wed, Apr 3, 2019 at 3:14 PM Pavlin Georgiev wrote: > > I have found inconsistency and remove it. > Now I send the logs for Sierra Wireless EM7355 again > Added now, thanks -- Aleksander https://aleksander.es ___ ModemManager-devel mailing li

Re: Supported modem by ModemManager - Ericsson N5321

On Wed, Apr 3, 2019 at 6:46 PM Pavlin Georgiev wrote: > > Hi. > > I report that modem Ericsson N5321 > is supported by ModemManager. > > USB ID 0bdb:193e Ericsson Business Mobile Networks BV > > Please, add this modem to the list of supported modems here: > https://www.freedesktop.org/wiki/Softwar

Re: Where are you using ModemManager?

Hey! > If you or your company are using ModemManager in a professional > product, would you mind sharing your experience in the mailing list? > The ModemManager/NetworkManager stack is used in the NIO ES8 elecric SUV to provide mobile broadband connectivity. https://www.nio.io/es8 -- Aleksander

Re: Supported modem by ModemManager - Dell F3607gw v2

On Thu, Apr 4, 2019 at 10:10 AM Pavlin Georgiev wrote: > > Hi. > > I report that modem Dell F3607gw v2 > is supported by ModemManager. > > USB ID 413c:8184 Dell Computer Corp. F3607gw v2 Mobile Broadband Module > > Please, add this modem to the list of supported modems here: > https://www.freedesk

Re: Problems compiling with clang (3.8.21)

Hey! > > https://gitlab.freedesktop.org/mobile-broadband/libmbim/merge_requests/8 > > https://gitlab.freedesktop.org/mobile-broadband/libqmi/merge_requests/35 > > > https://gitlab.freedesktop.org/mobile-broadband/ModemManager/merge_requests/88 > > I tested the patches against the following version

Do you need hardware to develop ModemManager?

Hey, If anyone is interested in contributing more to ModemManager and would like to have more test devices to play with, please drop me a private email and we'll try to fix that. Cheers! -- Aleksander https://aleksander.es ___ ModemManager-devel maili

Re: Supported modem by ModemManager - Telit LE910-EU1

Hey! > > I report that modem Telit LE910-EU1 (MBIM) > > is supported by ModemManager. > > > > USB ID: 1bc7:0032 > > > > Please, add this modem to the list of supported modems here: > > https://www.freedesktop.org/wiki/Software/ModemManager/SupportedDevices/ > Thanks, added to the list now. Do you

Re: Supported modem by ModemManager - Telit LE910-EU1

On Mon, Apr 8, 2019 at 10:06 AM Stelling2 Carsten wrote: > > > General |dbus path: /org/freedesktop/ModemManager1/Modem/0 >|device id: 57296b70bd5c42eaf98afb46f49dbc8f83716b88 > > Hardwar

ModemManager/libqmi/libmbim openwrt feed moved to fd.o gitlab

Hey, I maintained an unofficial openwrt feed for MM/libqmi/libmbim in bitbucket.org, I've just moved it to fd.o gitlab alongside the actual projects: https://gitlab.freedesktop.org/mobile-broadband/mobile-broadband-openwrt BTW, if anyone would like to work on integrating these in the upstream ope

Re: Receive text messages without polling?

Hey! > since long I use a simple Python script that fetches text > messages via org.freedesktop.ModemManager.Modem.Gsm.SMS.List(). > However, polling is boring. Is there a way to get SMS > asynchronously, e.g. by D-Bus callback? > In the new MM1 .0 DBus API you have the Modem.Messaging interface

Re: M(ModemManager:12866): GLib-CRITICAL **: 02:15:18.771: g_array_ref: assertion 'array' failed

Hey Enrico, > I am writing to report an issue we are having with Wistron NeWeb (WNC) Modem > device. > libmbim -> GIT version at commit 67ba57f89fd3a2f4b280361e650eaef0057baeaa > libqmi -> GIT version at commit 38d6729b0822a96e757162208fd8c88bb648085b > MM -> GIT version at commit 44eac9e97424d6b

Re: Simple connect with profile # instead of APN

Hey, > Is there support for simple-connect where instead of overwriting the APN I > can just select the APN with the profile #. > > In qmcli, I can just do this: > --wds-start-network="3gpp-profile=3" > > reason is some carriers like Verizon have the internet APN in slot 3 and I do > not want to

Re: [PATCH] broadband-modem-mbim: parse nw_error in register_state_set_ready only if MBIM_STATUS_FAILURE

Hey! > > Any update on the patch? :) > In the meantime I got response from Telit that they won't fix the original > problem which made me create this patch. > Oh wow, I forgot about it, sorry... I have pushed it to a new merge request in gitlab now: https://gitlab.freedesktop.org/mobile-broadban

Re: u-blox LARA0-R2 (R280) not worrking with MM 1.10

> On Ubuntu 18.10 Cosmic (MM 1.8.2) I get the following. > > # ls /dev/ttyACM* > /dev/ttyACM0  /dev/ttyACM2  /dev/ttyACM4 > /dev/ttyACM1  /dev/ttyACM3  /dev/ttyACM5 > > # lsmod | grep acm > cdc_acm    32768  4 > > # mmcli -L > > Found 1 modems: >    

Re: Merge into OpenWrt?

Hey! > > Is there any interest in making ModemManager an official OpenWrt > > package? > > Yes. Aleksander already requested help doing that: > https://lists.freedesktop.org/archives/modemmanager-devel/2019-April/007201.html > > > It seems like they would accept it. Is there a TODO? > > https://

Re: Watching for available SIMs on D-Bus

Hey, > I need to collect informations about modems (for IMEI) and SIM cards > (for IMSI) available to system over D-Bus. > > While listening to signal InterfacesAdded on interface > org.freedesktop.DBus.ObjectManager does work as mentioned in > documentation, ie. returning properties on newly disc

Re: ModemManager Delayed Signal Lost Disconnect on u-blox TOBY-R200

Hey, > > First what are the conditions where a cellular data connection will be > automatically disconnected due to bad signal/loss of network? Also what > program handles the disconnect (NetworkManager, ModemManager, pppd)? > It's the modem firmware itself handling that, MM will just report w

Re: ModemManager Delayed Signal Lost Disconnect on u-blox TOBY-R200

> > > It's the modem firmware itself handling that, MM will just report > > whatever the modem is reporting. > > > > E.g. if the modem is registered and connected in LTE, and the LTE > > network disappears (e.g. low signal quality, out of coverage) then the > > modem will try to handover to 3G or 2

Re: Get the last SMS from mm_modem_messaging_list

Hey, > > I have some trouble with pulling a received SMS from the ModemManager > messaging-list. Roughly described I'm doing things like so: > > gdbus_sms = MM_GDBUS_MODEM_MESSAGING(mm_sms->modem_messaging); > g_signal_connect (gdbus_sms, "added", > G_CALLBACK (cb_dbus_sign

ModemManager 1.10 integration in openwrt

Hey Nick, Rick and everyone, I've pushed a MR to integrate MM 1.10 (including the new key-value output support) in the openwrt repo: https://gitlab.freedesktop.org/mobile-broadband/mobile-broadband-openwrt/merge_requests/3 Nick; it's not really based on the previous work you did. The main change

Re: u-blox LARA0-R2 (R280) not worrking with MM 1.10

Hey Brendan, Looking at the tags we set, we're just ignoring the ports we don't want to use or we don't support, but we're not explicitly specifying the purpose of each of the ports: # LARA-R2 port types # ttyACM0 (if #0): primary # ttyACM1 (if #2): secondary # ttyACM2 (if #4): tertiary # tty

[review] Fix sending/storing SMS messages when other AT commands get in the way

Hey Dan & all, The original fix I had for this issue was to always add raw commands to the head of the queue inside the serial port: https://gitlab.freedesktop.org/mobile-broadband/ModemManager/merge_requests/103 The new fix I have for this issue is to setup a new queue of operations at modem obj

[review] Fix reporting modem state when registration denied

Hey all, This MR fixes an issue with the modem state reported as "registered" even if the registration was really denied, comments welcome: https://gitlab.freedesktop.org/mobile-broadband/ModemManager/merge_requests/107 -- Aleksander https://aleksander.es ___

Re: New u-blox TOBY-R200 Firmware and CID Issues

> It looks like ModemManager takes the highest numbered CID it sees and assumes > it needs to use the next one available or if at the max CID then reuse it. > In the case of the TOBY-R200, only CID 1 and 31 are used so ModemManager > tries to reuse CID 31 but the modem reports an error since it

Re: --list-bearers option errors in 1.10

> To answer my own question to get current band ID you can use the new (1.10) > option: > > qmicli -p -d /dev/cdc-wdm0 --nas-get-rf-band-info > [/dev/cdc-wdm0] Successfully got RF band info > Radio Interface: 'lte' > Active Band Class: 'eutran-20' > Active Channel:'6400' > Please note that

ANN: ModemManager 1.10.2

Hey hey, This is the first bugfix release in the ModemManager 1.10.x series. Unlike previous bugfix releases of stable branches, this release comes with a new feature that may require packaging updates, see notes to distribution packagers below. Overview of changes in ModemManager 1.10.2 --

Re: EM7455 modem --location-enable-gps-unmanaged fails

Hey, > I'm trying to setup GPS support for EM7455 modem by using 1.10.0 release of > MM. > I tried to use following script from [0] to setup unmanaged raw gps > mode so then /dev/ttyUSB1 can be used by gpsd to get coordinates. > > While running step: mmcli -m 0 --location-enable-gps-unmanaged I g

Re: EM7455 modem --location-enable-gps-unmanaged fails

> > > I'm trying to setup GPS support for EM7455 modem by using 1.10.0 release > > > of MM. > > > I tried to use following script from [0] to setup unmanaged raw gps > > > mode so then /dev/ttyUSB1 can be used by gpsd to get coordinates. > > > > > > While running step: mmcli -m 0 --location-enable

[RFC] TTY port locked problems when using PPP

Hey! In the past months we've seen several reports of issues with the TTY port "forced closed" and not being able to be reopened after that and things like that. The root cause from this problem is that MM tries to reuse the TTY port after MM itself has detected a disconnection (via +CGEV URCs or

Re: [RFC] TTY port locked problems when using PPP

> > Have you seen the following commit from NetworkManager for pppd? It has > helped solve many of the issues of being in sync with pppd and MM that I have > seen: > > https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=a251712a729f676c9c2d38e469e4f88e250229ba > > Even with tha

Re: 1.10 ModemManager availability on Debian Stretch

Hey, > > I am interested in the location and reset feature of ModemManager that is > available in version >=1.8 Debian package. > > > > Debian Buster has 1.10 version. Please let me know if 1.10 will be > backported to Debian Stretch. > @Mathieu Trudel-Lapierre may know this? -- Aleksander h

Re: Some doubts regarding ModemManager Network Registration API

Hey, >I have a few questions regarding getting Network Registration status > in ModemManager. > > May I know how can I achieve the following: > 1. How to get if current network registration state is automatic? There is no way to know this from the outside right now. By default it is automatic

Re: Missing error message when connecting with invalid APN

Hey, > > I’m currently using ModemManager 1.6.10 on Ubuntu 16.04 server, on a system > without user interaction. The modem is unlocked and enabled based on a > configuration in a database. > > I tried to set an invalid APN on a modem to see if this error situation > easily could be reported bac

Re: [RFC] TTY port locked problems when using PPP

> wt., 18 cze 2019 o 14:43 Aleksander Morgado > napisał(a): > > > My opinion is a bit open on this, I liked the first way because we > > would try to be as robust as possible and totally avoid using the port > > with wrong CLOCAL settings, but I don't think we can

Re: ModemManager warning messages

Hey, > > I am using a ModemManager - 1.6.4 ( Ubuntu 16.06.4) running on a Sierra > Wireless EM74xx modem > That Ubuntu version seems wrong, I assume you mean 16.04? > I happen to run the following command multiple times ( modem resets as part > of test functionality). > > mmcli -m 1 --reset

ANN: ModemManager 1.10.4

Hey hey, This is the second bugfix release in the ModemManager 1.10.x series. Overview of changes in ModemManager 1.10.4 --- The list of changes in this version includes: * QMI: ** Fix assertion when cleaning up event report indications. * MBIM:

ANN: ModemManager 1.8.4

Hey hey, This is the second bugfix release in the ModemManager 1.8.x series. I wasn't really going to push any new stable update in the 1.8.x branch, but there were some obvious fixes that anyone shipping 1.8.2 would have wanted... Overview of changes in ModemManager 1.8.4 -

Re: Multipart SMS

Hey! > I have an issue with SMS > 160 characters not showing up in my SMS > application. > > When SMS < 160 characters are received, the following steps take place: > > - MM emits an 'added' signal > - in the callback, the SMS client pulls the SMS list with > 'mm_modem_messaging_list' > - in the '

[review] 3GPP registration logic updates and QMI NAS specific fixes

Hey, The following MR is ready for review: https://gitlab.freedesktop.org/mobile-broadband/ModemManager/merge_requests/124 This MR introduces some cleanups on how the registration updates are managed, and explicitly fixes the "QMI NAS Initiate Network Register" based implementation, which was not

[review] #BND based band management in the ME910

Hey Carlo, Daniele and all, Here's a branch that tries to implement #BND based band management for the ME910, because the 2G bands are managed in a different way than on the previous original logic. https://gitlab.freedesktop.org/mobile-broadband/ModemManager/merge_requests/125 Let me know what

[review] call waiting network service query/enable/disable

Hey, Until now, the only setup we did for the call waiting service was to unconditionally enable URCs while the modem was enabled, but we were not doing any specific setup with the network. This MR allows client applications to query the status of the call waiting service, and also request to enab

[review] Initialize common SMS fields early for multipart messages

Hey, Until now, most of the SMS properties of a multipart SMS object were being initialized once the SMS was fully assembled (i.e. when absolutely all parts were received). This MR updates that logic so that the common SMS object fields (e.g. pdu-type, number, smsc...) are initialized as soon as t

Re: Watching for available SIMs on D-Bus

Hey, > > > I need to collect informations about modems (for IMEI) and SIM cards > > > (for IMSI) available to system over D-Bus. > > > > > > While listening to signal InterfacesAdded on interface > > > org.freedesktop.DBus.ObjectManager does work as mentioned in > > > documentation, ie. returning

Re: GPRS not allowed in PLMN

Hey! On Sat, Jul 20, 2019 at 3:35 PM Vincent Bernat wrote: > > ❦ 20 juillet 2019 12:00 +02, Vincent Bernat : > > > ModemManager[989]: Simple connect state (4/8): Wait to get fully > > enabled > > ModemManager[989]: Simple connect state (5/8): Register > > ModemManager[989]: Simple connect

Re: Watching for available SIMs on D-Bus

Hey! > > > > > I need to collect informations about modems (for IMEI) and SIM cards > > > > > (for IMSI) available to system over D-Bus. > > > > > > > > > > While listening to signal InterfacesAdded on interface > > > > > org.freedesktop.DBus.ObjectManager does work as mentioned in > > > > > docum

[review] Retry reloads for the Band/Mode set operation

Hey! The following MR adds some retry mechanism to the "reloading" of bands/modes during a set operation. https://gitlab.freedesktop.org/mobile-broadband/ModemManager/merge_requests/130 E.g. if we were configured with band "EUTRAN 19" and we try to set "EUTRAN 20" instead, the modem may return a

Re: forcing a specific handler plugin on a fixed tty

Hey, > > Currently when forcing the quectel modem i have to be proved via udev, i get > "not supported by any plugin". > > As far as i understand MM_PLUGIN will create a match thing against > MM_PLUGIN_ALLOWED_VENDOR_IDS, but adding anything there wont work for me > because the modem is not on

Re: forcing a specific handler plugin on a fixed tty

Hey Arvid, > > > > Currently when forcing the quectel modem i have to be proved via udev, i > > get "not supported by any plugin". > > > > As far as i understand MM_PLUGIN will create a match thing against > > MM_PLUGIN_ALLOWED_VENDOR_IDS, but adding anything there wont work for me > > because

Re: [RFC] TTY port locked problems when using PPP

Hey Dan and all, > > > > The main issue with this approach is that ModemManager would do a > > > > lot > > > > of tasks that were exclusively done by NetworkManager before, > > > > like > > > > IP > > > > addressing setup or IP routing setup. I'm sure we can instruct NM > > > > to > > > > play nic

Re: mmcli simple connect timeout

Hey, > > I'm hoping that those with inside knowledge might explain where my > problem lies. > > I have a sim (ee, uk) that works well in an EE 4g hotspot gadget, and > I'm putting it into a laptop to use it there as I will get more value > from it. The laptop is a Dell 7280 running ubuntu 19.04,

[RFC] AT-capable ttyACM port heuristics are not perfect

Hey, When using the "strict" filter in ModemManager, we try to use different heuristics to guess whether a device is a modem or not. One of the checks we do is looking at the exposed interfaces: if the device exposes one or more ttyACM ports that report themselves as "AT capable" (class=2/subclas

Re: Announcing AGH 0.01

Hey! > I am announcing AGH: a 3G/4G connection manager (via ModemManager) / XMPP > control agent, specifically designed for OpenWrt. > Great work :) > Some of it's features: > Documentation: AGH is documented enough to get you to a good start; The documentation is extremely verbose, which is v

[RFC] Reworked MM udev tags

Hey all, Please review this MR that repurposes the ID_MM_DEVICE_IGNORE tag (e.g. so that it applies to all port types and to all filter modes) and also renames/removes some other tags: https://gitlab.freedesktop.org/mobile-broadband/ModemManager/merge_requests/138 The commit doing the ID_MM_DEVI

Re: ModemManager not displaying e-utran band 28

Hey > I am running libqmi 1.22.4 and ModemManager 1.8.4. I want mmcli to display > e-utran band 28 in its output because I also want the ability to specify band > 28 as an allowed band. > > Qmicli definitely shows band 28 among the supported bands. I have checked in > the ModemManager enums,

Re: Modemmanager significant startup delay

Hey all, From Paul's email, the port type hints for the TTYs exposed by the MC74xx could help make the probing much faster. I haven't tested them myself, but we could definitely add them in the release. # MC74XX: Add port hints # if 03: primary port # if 02: raw NMEA port # if 00: diag/qcdm po

Re: Modemmanager significant startup delay

On Thu, Aug 22, 2019 at 11:06 AM Bjørn Mork wrote: > > Dan Williams writes: > > On Wed, 2019-08-21 at 12:23 +, Amol Lad wrote: > >> Please help with this. What could be the cause of significant MM > >> startup delay? > > > > When started, or when a new modem is plugged attached, ModemManager

Re: Modemmanager significant startup delay

Hey! On Mon, Aug 26, 2019 at 5:14 AM Amol Lad wrote: > > Same here. Paul's rules brought the ModemManager start-up delay to almost nil! > I've pushed a MR to get these port type hints included in the release, review/tests welcome: https://gitlab.freedesktop.org/mobile-broadband/ModemManager/merg

Re: [RFC] AT-capable ttyACM port heuristics are not perfect

Hey all, > > When using the "strict" filter in ModemManager, we try to use > different heuristics to guess whether a device is a modem or not. > > One of the checks we do is looking at the exposed interfaces: if the > device exposes one or more ttyACM ports that report themselves as "AT > capable"

Re: hp-lt4132 'unavailable' in NetworkManager on Debian 10

Hey, > > Since migrating from Debian 9 to Debian 10, my hp-lt4132 is 'unavailable' in > NetworkManager. > > Attached > > ModemManager_2019-08-27_00-43-36.odt -- commands used to enable modem and > connect to bearer > ModemManager_2019-08-27_00-39-18.log -- debug log > > > Thanks, Christian > Th

Re: hp-lt4132 'unavailable' in NetworkManager on Debian 10

Hey, > We may need NetworkManager logs to see why that connection attempt > > wasn't completed correctly in the NM side. > > > Attached > > NetworkManager_2019-08-28_15-24-08.log -- debug log > That's weird, because NM does say it's connected: Aug 28 15:08:51 hp-eb-x360-1030-g3 NetworkManager[74

Re: Sierra EM7511 modem not found

Hey, > > Struggling to understand the steps necessary for ModemManager to detect a > Sierra Wireless EM7511 modem. I'm using an embedded Linux distro (created > via Buildroot). > > mmcli can't seem to find any modems: > # mmcli -L > > No modems were found > > > Here is my output from ModemManag

Re: hp-lt4132 'unavailable' in NetworkManager on Debian 10

> cfocke@hp-eb-x360-1030-g3:~$ ip addr > > 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group > default qlen 1000 > > link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 > > inet 127.0.0.1/8 scope host lo > >valid_lft forever preferred_lft

Re: Resetting Bearer on OpenWRT

> > > I'm running modemmanager on OpenWRT and am getting this error fairly > > > regularly such as when I use AT commands to manually change LTE > > > bands(is there a better way to change/lock bands than using AT > > > commands?): "Bearer not allowed to connect, not registered in 3GPP > > > networ

Re: modemmanager/qmicli openwrt feed update

Hey! > If you consider this ok, then can you please update the modemmanager and > qmicli to the latest release in openwrt feed? They are currently at 1.10.0 > and 1.22.4 respectively. > I will first sync the packages with the updates already done in https://github.com/openwrt/packages/pull/9137

Re: Timing of next major release

Hey! > > We're considering a major version update of ModemManager used in our platform, > so it would be nice to know if you plan a major release until around the end > of year. > > If so, we could pick it up right away, or it'll take longer, so should we go > with 1.10 branch instead? > I thin

Re: modemmanager/qmicli openwrt feed update

> Does this variable need to be used by another file? > In modemmanager.common line 14: > MODEMMANAGER_PID_FILE="${MODEMMANAGER_RUNDIR}/modemmanager.pid" > ^-- SC2034: MODEMMANAGER_PID_FILE appears unused. Verify it or export it. > Don't think it's used anywhere else. > Is the expected behaviour

Re: hp-lt4132 'unavailable' in NetworkManager on Debian 10

Hey! > thanks; the modem is plugged to the mainboard, so no simple plugging-in; > instead, I did this > > $ mmcli -m 0 --simple-connect="apn=a1.net,user=p...@a1plus.at,password=ppp" > $ # sleep some time > $ mmcli -m 0 --simple-disconnect > You should not use mmcli for anything, maybe that's the

Re: hp-lt4132 'unavailable' in NetworkManager on Debian 10

Hey! On Wed, Sep 11, 2019 at 11:22 AM Focke Christian wrote: > > Yes I know, but with NM-GNOME and nmcli it doesn't work at all; that's where > I started from. > > Actually it was you who instructed me to use mmcli to analyse the issue on MM > side. > Oh, ok, sorry for the confusion then :) T

ANN: ModemManager 1.10.6

Hey hey, This is the third bugfix release in the ModemManager 1.10.x series. Overview of changes in ModemManager 1.10.6 --- The list of changes in this version includes: * Bearer: if connecting a bearer with PPP method, require upper layers to disconnec

Re: mmcli not listing firmware images from modem

Hey, > > I’m using Solidrun’s clearfog-base plarform with Sierra Wireless EM7430 LTE > chipset. I’m running OpenWRT 18.06 with ModemManager feed from > https://gitlab.freedesktop.org/mobile-broadband/mobile-broadband-openwrt > > > > mmcli is not reporting stored firmware images but same can be r

Re: [PATCH] Support allow-roaming property in openwrt protocol handler

On Thu, Sep 12, 2019 at 8:25 AM Amol Lad wrote: > > Hi, > > > > Below patch allows user to configure roaming in /etc/config/network along > with other parameters such as apn. This patch is generated from Mobile > Broadband OpenWRT git > (https://gitlab.freedesktop.org/mobile-broadband/mobile-br

Re: modemmanager.proto issue?

Hey Amol, > > Regarding modemmanager.proto file @ > https://gitlab.freedesktop.org/mobile-broadband/mobile-broadband-openwrt/blob/master/modemmanager/files/modemmanager.proto > > Did you mean "while [ $idx -le $bearercount ];" in below function instead of > " while [ $idx -ge $bearercount ];" ?

Re: [PATCH] Include minutes in SMS timezone field

Hey Amol On Wed, Sep 18, 2019 at 2:00 PM Amol Lad wrote: > > Hi, > > Below is a sample received SMS. I'm in timezone "+0530" but the timestamp > only shows "+05". I've attempted to fix this in master. Thus, if the timezone > field notes not include minutes then it will be shows as "+hh" and if

Re: [PATCH] Include minutes in SMS timezone field

Hey, > Comment in libmm-glib/mm-sms.c :mm_sms_get_timestamp() states that the time > returned is ISO8601 complaint. However, ISO8601 mandates that year must be in > format and not just YY. What we are showing in timestamp field is > YYMMDDHHMMSS+ZZ. This is more in-line with the 7 octet ti

Re: Dual SIM support in Sierra EM7455/7430

Hey, > Sierra EM7455/7430 provide support for dual SIM cards. Current sim can be > found out using AT!UIMS? at command. This will return “0” or “1” depending > on which sim is active. Similarly, SIM 0 can be made active using AT!UIMS=0 > and SIM 1 using AT!UIMS=1. > > > > Now how to achieve th

ModemManager, libqmi, libmbim in openwrt packages repository

Hey! Nick has successfully integrated all ModemManager, libqmi and libmbim into the upstream openwrt packages repository (https://github.com/openwrt/packages/pull/9137), and therefore the packaging I maintained in https://gitlab.freedesktop.org/mobile-broadband/mobile-broadband-openwrt is NO LONGE

Re: “bytes-rx” and “bytes-tx” statistics are not getting populated

Hey, > I’m using almost the latest modemmanager from master (commit hash: > 0a85254d1765db6e55770d36e24b1e6349e789f4). I started noticing that the > “bytes-rx” and “bytes-tx” statistics are never getting updated even though > there is regular traffic (say ping). I’m not sure if anything has cha

Re: mmcli 3gpp network scan

Hey, > > I’m using almost the latest modemmanager from master (commit hash: > 0a85254d1765db6e55770d36e24b1e6349e789f4). When starting network scan using > mmcli, the availability field is always “unknown” whereas for qmicli the > “Status” is reported with more details. Please advise if this is

Re: “bytes-rx” and “bytes-tx” statistics are not getting populated

Hey, > Oct 10 09:23:13 OpenWrt [6904]: [/dev/cdc-wdm0] Received message > (translated)... > >> Header: > >> length = 96 > >> type= command-done (0x8003) > >> transaction = 37 > >> Fragment header: > >> total = 1 > >> current = 0 > >> Co

Re: “bytes-rx” and “bytes-tx” statistics are not getting populated

Hey! > > Yes, my default route is through modem only and in fact below is qmicli output > > root@OpenWrt:/# qmicli -d /dev/cdc-wdm0 -p --wds-get-packet-statistics > [/dev/cdc-wdm0] Connection statistics: > TX packets OK: 97 > RX packets OK: 87 > TX packets dropped: 0 >

Re: Sim added / extracted not detected

Hey, > > I am developing an application which makes use of the libmm-glib high level > API and I have been making some tests and I have not been able to detect when > a SIM is added or removed (I know its not very common to add/extract it on > runtime but I want to be aware of this in my app).

Re: Sim added / extracted not detected

Hey, >> >> >> I am developing an application which makes use of the libmm-glib high >> >> level API and I have been making some tests and I have not been able to >> >> detect when a SIM is added or removed (I know its not very common to >> >> >>add/extract it on runtime but I want to be aware of

Re: Fwd: Sim added / extracted not detected

Hey! > > Ok, yes, that is exactly what I am expecting to see. I would be pleased > > if you could confirm me that the modem I am using does not support this > > feature. > > Possibly also worth pointing out that some modem implementations do not > connect the sim-change indicator switch from the S

  1   2   3   4   5   6   7   8   9   10   >