Investigation of failure to report received SMS
neiljerram at googlemail.com
Fri Feb 26 23:54:29 CET 2010
I got two occurrences of this problem recently, with DEBUG frameworkd logging.
(I've replaced data strings in the following and linked logs by ***,
but am happy to
share the real contents privately if that would help.)
SMS timestamp: dbus.String(u'Fri Feb 5 08:31:39 2010 +0000'
Detected as having been missed (by added zhone code ) at 08:32:12:
2010-02-05 08:32:08,525 INFO check for missing received messages...
2010-02-05 08:32:08,532 INFO new message! Retrieving messagebook...
2010-02-05 08:32:10,027 INFO IDLE STATE = idle_dim
2010-02-05 08:32:12,101 INFO retrieved messagebook: ***
2010-02-05 08:32:12,147 INFO play sound to announce unread messages
2010-02-05 08:32:12,184 INFO show missed message
2010-02-05 08:32:12,214 DEBUG transition to text_show
frameworkd log is at http://ossau.homelinux.net/~neil/fr1.txt
SMS timestamp: dbus.String(u'Fri Feb 5 11:40:45 2010 +0000'
Detected by zhone code at 11:43:
2010-02-05 11:43:35,521 INFO check for missing received messages...
2010-02-05 11:43:35,527 INFO new message! Retrieving messagebook...
2010-02-05 11:43:38,212 INFO retrieved messagebook: ***
2010-02-05 11:43:38,260 INFO play sound to announce unread messages
2010-02-05 11:43:38,295 INFO show missed message
2010-02-05 11:43:38,309 DEBUG transition to text_show
frameworkd.log is at http://ossau.homelinux.net/~neil/fr2.txt
In both cases, it seems:
- the only frameworkd trace near the time of the SMS timestamp is
about a CypherStatus indication
- the retrieval of the messagebook (initiated by zhone) triggers
frameworkd to send a wakeup signal to the modem, and then to get
lots of data from it.
There are lots of other occurrences of the "last communication with
modem" trace in my log, so it looks like that might be perfectly
Does that give anyone any clues about why those received SMSs are
More information about the community