| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
We will instead not export an SMS until completed and assembled
|
|
|
|
When running AT+CIND=? we get the real range for the signal quality indications,
like: "signal",(1-7).
The max value doesn't need to be 5; so if we do get min and max, we will
normalize the returned quality using the proper range and scale it to the
[0,100] range.
|
|
Some modems will report strings instead of indicator indexes, like:
+CIEV: roam,1
So allow non-integer indicators.
|
|
|
|
Cinterion modems seem to include
"signal",(0-7,99)
We just get rid of the ',99' part.
|
|
Currently the support for text mode lacks a lot of functionality.
|
|
|
|
Whenever we get unlocked, the modem initialization sequence will be run again.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
When notifying added or completed SMS objects, don't return their properties as
they can be retrieved by looking at the specific objects in DBus.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
We'll just:
* Report unsupported on CDMA-only modems.
* Check if AT+CNMI=? replies correctly, and if so, assume SMS-based messaging
is supported.
|
|
The interface won't be exported if the given check fails.
|
|
|
|
|
|
connect_cdma()
These implementations must not update neither port nor connection_type, as
these items are specific of the MMBroadbandBearer object, and hence not
available by subclasses.
|
|
didn't change
|
|
Managing existence of the SMS objects better done only via the Messaging
interface.
|
|
|
|
|
|
|
