Age | Commit message (Collapse) | Author | Files | Lines |
|
HFP modem will be registered when Proxy Added callback gets called
or when Pair is True. This patch removes the support for dynamic modem
registration when a new connection is notified and there isn't a modem
associated with the Bluetooth remote device.
BlueZ behaviour has been changed and a NewConnection is not notified
before the service discovery finishes.
|
|
Apart from g_io_channel_unix_new() not setting errno, it never
returns an NULL pointer on error, because in practice it only
calls g_new().
|
|
As BlueZ 5 introduced backwards incompatible API changes, and we want to
keep support for BlueZ 4 based HFP AG plugin for some time, we need to
separate HFP AG plugin which is based on BlueZ 4 from the one based on
BlueZ 5.
The hfp_ag.c plugin is renamed to hfp_ag_bluez4. This will make it easy
to add an HFP AG plugin for BlueZ 5.
|
|
When there are many devices around that support the HFP AG profile,
we may have a lot of modems that the user will never use.
|
|
This patch removes unnecessary GDBusProxy object access when property
changed is triggered. The property name and the argument iterator is
informed in the function callback.
|
|
This patch fix an unusual scenario, service_level_connection() fails if
GIOChannel or GAtChat memory allocation fails.
|
|
Rename this property to better indicate that it is the remote Address
being referred to.
|
|
This patch adds a copy of Bluetooth RFCOMM socket declaration.
|
|
Adds a copy of BlueZ bacmp() function.
|
|
Adds a copy of BlueZ ba2str() function.
|
|
This patch adds the initial SCO server socket handling. BtIO and BlueZ
functions should not be used, with the new Profile API the objetive is
to get rid of these dependencies.
|
|
Adds a copy of BlueZ bacpy() function.
|
|
Adds local copy of SCO Bluetooth sockets declarations, since the
objective to avoid including BlueZ library headers.
|
|
When receiving a NewConnection call from BlueZ, initiates the Service
Level Connection using the received file descriptor. The HFP modem
sub-components (devinfo, voicecall, netreg, handsfree and callvolume)
are created at this point.
|
|
Parse the essential arguments in the message, in this case only the
file descriptor, and register the modem if it is not already
registered. This is necessary because in some cases, we may receive a
NewConnection call, and the SDP process is still taking place.
|
|
If the device Alias property changes we should also change the name of
the modem.
|
|
Now that we are able to keep track of devices appearing and
disappearing from BlueZ, we are able to register the modem when a
device that supports the HFP AG UUID appears.
|
|
|
|
This patch tracks the GDBusProxy for Bluetooth devices in order to be
able to get their properties.
|
|
This patch adds the initial callbacks to track when BlueZ connects so
we can register our HFP external profile handler. And tracks the
interfaces added or removed.
|
|
|
|
|
|
If we send these commands before the EMRDY notification has been seen,
they will simply return an error.
|
|
This patch declares the external HFP Profile handler. It contains the
initial implementation of the D-Bus Profile1 interface and methods
responsible for handling Bluetooth connections.
|
|
|
|
|
|
Adds utility API to handle BlueZ 5 RegisterProfile and UnregisterProfile
methods.
|
|
This patch adds the initial file to support external HFP profile and
BlueZ 5. "hfp_hf_bluez5" plugin will implement an external Bluetooth
profile compatible with BlueZ 5, and "hfp_hf_bluez4" plugin will keep
the compatibility with BlueZ 4.
|
|
This patch adds the file for Bluetooth(BlueZ 5) oFono plugin.
|
|
As BlueZ 5 introduced backwards incompatible API changes, and we want to
keep support for BlueZ 4 based plugins for some time, we need to separate
the plugins that are based on BlueZ 4 from the ones based on BlueZ 5.
The bluetooth.c plugin has now been renamed to bluez4.c and the hfp_hf.c
plugin is renamed to hfp_hf_bluez4. This will make it easy to add a
HFP HF plugin for BlueZ 5.
|
|
|
|
|
|
This matches the huawei plugin.
|
|
Telit HE910 needs the baud rate to be set.
|
|
The newer IFX firmware was changed, it no longer accepts AT commands
until the UA frame has been sent back to the AP. The commands are
simply dropped on the floor. This requires a proper fix in GAtMux, but
until then simply bump up the timeout to get around this issue.
|
|
When performing a SIM REFRESH, particularly NAA Initialization, we need
to wait until the modem sends XSIMSTATE: 7, not XSIMSTATE:2. Even on
normal initialization it seems safer to wait until XSIMSTATE:2.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Use AT#QSS=2 instead of AT#QSS=1 to get an URC when the SIM is not only
inserted but also when PIN is unlocked and when SMS + phonebook are
ready to be used.
Disable sim state notification in telit_enable() so that we sure get a
notification when we enable it later again. This way we don't have to
query the state the first time. Without this the Telit modem does not
always send an URC when AT#QSS=2 is sent.
Remove sim_inserted_source and sim_inserted_timeout_cb which are not
needed anymore as a consequence.
By the way the 1 second timeout was an ugly hack.
Don't query current SIM status in cfun_enable_cb() as the SIM is
disabled due to prior AT+CFUN=4.
Register '#QSS:' before enabling sim state notifications.
Remove telit_qss_cb() which was used as a callback for querying the
current SIM status.
Move sms atom creation into switch_sim_state_status() and add creation
of phonebook atom. These are created when QSS: 3 is received.
|