mirror of
https://github.com/google/pebble.git
synced 2025-04-30 07:21:39 -04:00
spelling: workaround
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
This commit is contained in:
parent
af088d08a6
commit
a33fc19e8e
7 changed files with 7 additions and 7 deletions
|
@ -321,7 +321,7 @@ static void prv_timer_stop(void) {
|
|||
//! connectability mode has changed.
|
||||
static void prv_perform_next_job(bool force_refresh) {
|
||||
|
||||
// Part of work-around for CC2564 bug (see comment with prv_work_around_should_not_cycle).
|
||||
// Part of workaround for CC2564 bug (see comment with prv_work_around_should_not_cycle).
|
||||
// When forced, we've just connected or disconnected, in that case cycle as well, because
|
||||
// otherwise we'll continue to advertise non-connectable if we've just disconnected and there
|
||||
// was already a job being advertised.
|
||||
|
|
|
@ -73,7 +73,7 @@
|
|||
// to zero). It can be calculated using the formula:
|
||||
// Effective Connection Interval = (Connection Interval) * (1+(Slave Latency))
|
||||
|
||||
//! This module contains a work-around for parameter update requests not being applied by
|
||||
//! This module contains a workaround for parameter update requests not being applied by
|
||||
//! iOS / Apple's BT controller, even though they get "accepted" by the host.
|
||||
//! @see gap_le_connect_params_handle_connection_parameter_update_response below for more
|
||||
//! commentary about the erroneous behavior.
|
||||
|
|
|
@ -107,7 +107,7 @@ static void prv_evaluate(ReconnectType prev_type) {
|
|||
// include the SIMULTANEOUS_LE_BR_EDR_TO_SAME_DEVICE_CONTROLLER and
|
||||
// SIMULTANEOUS_LE_BR_EDR_TO_SAME_DEVICE_HOST flags. However, we have never
|
||||
// done this (ignorance) and gotten by, by using a "random" address (the
|
||||
// public address, but then inverted) as a work-around for the problems
|
||||
// public address, but then inverted) as a workaround for the problems
|
||||
// leaving out these flags caused with Android.
|
||||
// I intend to use the "Peripheral privacy feature" some time in the
|
||||
// near future. With this, these flags and the issues on Android become
|
||||
|
|
|
@ -27,6 +27,6 @@ void pp_decline_call(uint32_t cookie);
|
|||
void pp_get_phone_state(void);
|
||||
|
||||
//! Enables or disables handling the Get Phone State responses.
|
||||
//! This is part of a work-around to ignore for stray requests that can be in flight after the phone
|
||||
//! This is part of a workaround to ignore for stray requests that can be in flight after the phone
|
||||
//! call has been declined by the user from the Pebble.
|
||||
void pp_get_phone_state_set_enabled(bool enabled);
|
||||
|
|
|
@ -83,7 +83,7 @@ typedef struct PACKED {
|
|||
//! @note Not available in Bluetopia/cc2564x implementation
|
||||
//! Flag to indicate that when re-pairing this device, the re-pairing should be accepted
|
||||
//! automatically for this remote device (matching IRK or matching identity address).
|
||||
//! @note This is a work-around for an Android 4.4.x bug. This opens up a security hole :( where
|
||||
//! @note This is a workaround for an Android 4.4.x bug. This opens up a security hole :( where
|
||||
//! a phone could pretend to be the "trusted" phone and pair w/o the user even knowing about it.
|
||||
//! @see https://pebbletechnology.atlassian.net/browse/PBL-39369
|
||||
bool should_auto_accept_re_pairing:1;
|
||||
|
|
|
@ -95,7 +95,7 @@ void test_gap_le_advert__initialize(void) {
|
|||
s_unscheduled_job = NULL;
|
||||
s_unscheduled_completed = false;
|
||||
|
||||
// This bypasses the work-around for the CC2564 advertising bug, that pauses the round-robining
|
||||
// This bypasses the workaround for the CC2564 advertising bug, that pauses the round-robining
|
||||
// through scheduled advertisement jobs:
|
||||
s_is_connected_as_slave = true;
|
||||
|
||||
|
|
Loading…
Add table
Reference in a new issue