be more struct in when we update what.. deal with enable or disable
actually failing.. and leaking the atchat
create netreg only after we have moved to the online state.. this
avoids crashes in case the sim is partially initialized.
Use +WIND only for the SIM ready/inserted state.. We can probably
try to use AT+CFUN=1,0 on the initial startup.. only tested with the
SL8xxx modem bank and serial.. let's see how AT+CFUN=1,1 behaves on
a true USB device..
for some strange reason, SIM_STATE_READY wants to be entered only
some 30 seconds after our wavecom modems come up. At this point,
cycling throug modem state OFFLINE would cause all existing and functional
interfaces to disappear.
When issuing a Scan() in poor reception while attached to an operator it's
fully possible to get no results, which causes the attached operator to be
cleaned up. In certain scenarios this would cause a use-after-free as there
are still references to this operator.
Transfer the attached operator to the new list regardless of removal caused
by the Scan() results.
This matches the behavior described by the documentation the signal
value returned by the code. This was causing a headache when using
stricter D-Bus wrappers like dbus-c++.
In situations where location changes rapidly, a use-after-free condition
can occur. What happens is that the timeout leaks and then the cbs
struct with the callback is cleaned up, resulting in a SIGSEGV when the
callback occurs from the glib loop.
The return value from a RIL_REQUEST_GET_FACILITY_LOCK
is the TS 27.007 service class bit vector of services
for the specified barring facility. The value canf be
zero, which indicates "disabled for all".
During the re-factoring of rilmodem's sim atom
messaging code, the sim_status_cb function's
RIL tracing code was converted to DBG calls.
This change adds the same prefix to DBG/trace
calls when a single message's parameters span
more than one DBG call. This makes it easier
to filter out trace messages when looking at a
log file.