[Kde-hardware-devel] MMQt - SMS

[Daniel]

The modem manager version is 1.4.2

I will try to check with MM developers.

Sorry for send the message just for you.

Thanks

On Fri, Jan 22, 2016 at 10:20 AM, Jan Grulich <jgrulich at redhat.com> wrote:

> Then it looks like a ModemManager issue, at least my understanding is that
> ModemManager should emit signal when a new message is received. It's also
> possible that it doesn't work that way, but that's something you would
> need to
> check with ModemManager developers.
>
> Btw. what is your ModemManager version? And please keep sending your emails
> also to the kde-hardware-devel mailing list.
>
> Jan
>
> On Friday 22 of January 2016 10:15:31 Daniel wrote:
> > Hi Jan,
> >
> > I ran the dbus-monitor in order to watch the dbus traffic but there is
> > nothing there while I am sending the messages.
> >
> > If i ran:
> >
> > # disable the modem
> > mmcli -m 0 -d
> >
> > and after that
> >
> > mmcli -m 0 -e
> >
> > all messages that were sent will be received at same time and the signals
> > are emitted in the dbus, as follows:
> >
> > signal sender=:1.3 -> dest=(null destination) serial=197
> > path=/org/freedesktop/ModemManager1/
> > Modem/0; interface=org.freedesktop.ModemManager1.Modem.Messaging;
> > member=Added
> >   object path "/org/freedesktop/ModemManager1/SMS/5"
> >   boolean true
> >
> > When the signal is emitted my application works perfectly, so the MMQt is
> > doing the right job.
> >
> > So, I am thinking that there is a problem or in modem driver or in modem
> > manager.
> >
> > Thanks in advance.
> >
> > On Fri, Jan 22, 2016 at 9:43 AM, Jan Grulich <jgrulich at redhat.com>
> wrote:
> > > Hi Daniel,
> > >
> > > I would try to check whether there is a problem in ModemManager or in
> the
> > > communication between ModemManager and MMQT.
> > >
> > > 1) Check whether ModemManager really sends signals about received
> > > messages.
> > > You can use dbus-monitor to watch ModemManager activity over dbus.
> > >
> > > Use:
> > > dbus-monitor --system
> > > "type='signal',sender='org.freedesktop.ModemManager1'"
> > >
> > > 2) If you see ModemManager sending signal Added()  from
> > > org.freedesktop.ModemManager1.Modem.Messaging interface then there is
> > > probably
> > > problem in MMQT. You can try to put some debug output to
> onMessageAdded()
> > > slot
> > > in modemmessaging.cpp from MMQT library to see what's going on and
> whether
> > > the
> > > slot is called.
> > >
> > > I hope this will help to identify where is your problem.
> > >
> > > Regards,
> > > Jan
> > > --
> > > Jan Grulich <jgrulich at redhat.com>
> > > Software Engineer, Desktop team
> > > Red Hat Czech
> > >
> > > On Friday 22 of January 2016 07:54:41 Daniel wrote:
> > > > Hi all,
> > > >
> > > > I am using the MMQt in order to handle SMSs in an embedded device.
> > >
> > > Sending
> > >
> > > > SMS it's ok. But receiving a message it is a bit weird. In the truth
> if
> > > > I
> > > > send a SMS to the device, the SMS will be available after a reboot.
> > > >
> > > > How can I debug the process of receiving a SMS?
> > > >
> > > > Follow some information:
> > > >
> > > > root at ts-imx6-s:~# mmcli -m 0
> > > >
> > > > /org/freedesktop/ModemManager1/Modem/0 (device id
> > > > '3fba001a3e3ce5ffefda417609400ad882ef3c7f')
> > > >
> > > >  -------------------------
> > > >  Hardware |   manufacturer: 'Telit'
> > > >
> > > >           |          model: 'HE910-EUD'
> > > >           |
> > > >           |       revision: '12.00.224'
> > > >           |
> > > >           |      supported: 'gsm-umts'
> > > >           |
> > > >           |        current: 'gsm-umts'
> > > >           |
> > > >           |   equipment id: '354043052132539'
> > > >
> > > >  -------------------------
> > > >
> > > >  System   |         device:
> > > >
> '/sys/devices/soc0/soc.1/2100000.aips-bus/2184000.usb/ci_hdrc.0/usb2/2-1
> > > > '
> > > >
> > > >           |        drivers: 'cdc_acm'
> > > >           |
> > > >           |         plugin: 'Generic'
> > > >           |
> > > >           |   primary port: 'ttyACM3'
> > > >           |
> > > >           |          ports: 'ttyACM3 (at), ttyACM0 (at)'
> > > >
> > > >  -------------------------
> > > >  Numbers  |           own : 'unknown'
> > > >  -------------------------
> > > >  Status   |           lock: 'none'
> > > >
> > > >           | unlock retries: 'unknown'
> > > >           |
> > > >           |          state: 'connected'
> > > >           |
> > > >           |    power state: 'on'
> > > >           |    access tech: 'umts'
> > > >           |
> > > >           | signal quality: '42' (recent)
> > > >
> > > >  -------------------------
> > > >  Modes    |      supported: 'allowed: 2g, 3g; preferred: none'
> > > >
> > > >           |        current: 'allowed: 2g, 3g; preferred: none'
> > > >
> > > >  -------------------------
> > > >  Bands    |      supported: 'unknown'
> > > >
> > > >           |        current: 'unknown'
> > > >
> > > >  -------------------------
> > > >  IP       |      supported: 'ipv4, ipv6, ipv4v6'
> > > >  -------------------------
> > > >  3GPP     |           imei: '354043052132539'
> > > >
> > > >           |  enabled locks: 'none'
> > > >           |
> > > >           |    operator id: '72410'
> > > >           |
> > > >           |  operator name: 'VIVO'
> > > >           |
> > > >           |   subscription: 'unknown'
> > > >           |   registration: 'home'
> > > >
> > > >  -------------------------
> > > >  SIM      |           path: '/org/freedesktop/ModemManager1/SIM/0'
> > > >
> > > >  -------------------------
> > > >  Bearers  |          paths: '/org/freedesktop/ModemManager1/Bearer/0'
> > > >
> > > > Thanks in advance.
>



-- 
Daniel Vaz
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-hardware-devel/attachments/20160122/cb813fe0/attachment-0001.html>