Investigation of failure to report received SMS

2010-02-26 Thread Neil Jerram
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.) 1. SMS timestamp: dbus.String(u'Fri Feb  5 08:31:39 2010 +' Detected as h

Re: Investigation of failure to report received SMS

2010-02-01 Thread Neil Jerram
On 1 February 2010 04:43, Alishams Hassam wrote: > On Sun, 2010-01-31 at 19:44 +, Neil Jerram wrote: >> So far no recurrences with frameworkd log level set to DEBUG.  (And I >> have received several messages.)  So maybe this is a heisenbug, of the >> kind that disappears when frameworkd runs m

Re: Investigation of failure to report received SMS

2010-01-31 Thread Alishams Hassam
On Sun, 2010-01-31 at 19:44 +, Neil Jerram wrote: > So far no recurrences with frameworkd log level set to DEBUG. (And I > have received several messages.) So maybe this is a heisenbug, of the > kind that disappears when frameworkd runs more slowly. > > Regards, > Neil Using qtmoko

Re: Investigation of failure to report received SMS

2010-01-31 Thread Neil Jerram
On 30 January 2010 11:48, Neil Jerram wrote: > > I guess what you have in mind is that the next step would be to try to > reproduce with the AT traffic included in the logs.  I agree, and will > try to do that. So far no recurrences with frameworkd log level set to DEBUG. (And I have received se

Re: Investigation of failure to report received SMS

2010-01-30 Thread Neil Jerram
On 30 January 2010 10:35, Timo Juhani Lindfors wrote: > Neil Jerram writes: >> (Note that I've raised some logs about incoming messages from DEBUG to >> WARNING, for this investigation.) > > At least with old frameworkd setting ogsmd loglevel to DEBUG would > show the actual AT traffic which I di

Re: Investigation of failure to report received SMS

2010-01-30 Thread Neil Jerram
On 30 January 2010 11:25, Fox Mulder wrote: > Neil Jerram writes: >> (Note that I've raised some logs about incoming messages from DEBUG to >> WARNING, for this investigation.) > > You lowered the log output with this option. DEBUG is the highest > logging option and warning does log much less.

Re: Investigation of failure to report received SMS

2010-01-30 Thread Fox Mulder
Neil Jerram writes: > (Note that I've raised some logs about incoming messages from DEBUG to > WARNING, for this investigation.) You lowered the log output with this option. DEBUG is the highest logging option and warning does log much less. ___ Openmo

Re: Investigation of failure to report received SMS

2010-01-30 Thread Timo Juhani Lindfors
Neil Jerram writes: > (Note that I've raised some logs about incoming messages from DEBUG to > WARNING, for this investigation.) At least with old frameworkd setting ogsmd loglevel to DEBUG would show the actual AT traffic which I did not see in your logs.. __

Investigation of failure to report received SMS

2010-01-29 Thread Neil Jerram
I'm not sure if this is really news. Apologies if not. I've been experiencing a lot of unreported SMSs - by which I mean that the phone receives an SMS, but it is not announced at the time of receipt - and have just managed to catch some useful logs for an occurrence of this. There's at least on