geeksville
|
8bf60c7603
|
make BLE exceptions strongly typed, so I can trigger closing down connections if needed
|
2020-04-20 11:10:53 -07:00 |
|
geeksville
|
0919bc75ef
|
only ignore connect failures if autoconnect is on
|
2020-04-20 11:01:27 -07:00 |
|
geeksville
|
2a52b707ee
|
fix autobug: some phones call gatt connected but with an error status code
|
2020-04-20 10:37:46 -07:00 |
|
geeksville
|
9b57d60432
|
add note about an unsolved autobug
|
2020-04-20 10:15:22 -07:00 |
|
geeksville
|
34aa4cde05
|
if bluetooth was disabled when we started, reattempt device connect later
|
2020-04-20 09:56:38 -07:00 |
|
geeksville
|
54d632eb84
|
some android stacks are buggy and need 500ms before returning BLE descriptors
|
2020-04-13 16:28:32 -07:00 |
|
geeksville
|
6ff84a1808
|
fix rare mystery bluetooth status 133 error
Thanks to comment by @pederovarela86
https://github.com/android/connectivity-samples/issues/18#issuecomment-374600798
|
2020-04-10 18:04:39 -07:00 |
|
Kevin Hester
|
90cee2f202
|
add support for reconnecting if bluetooth gets disabled
|
2020-03-02 08:05:43 -08:00 |
|
Kevin Hester
|
6a90881dd6
|
fix crashlytics auto report. oops error() is now a kotlin stdlib call
and therefore I was accidentally calling it instead of my Logging.error()
method. And that made some error logs incorrectly fatal.
|
2020-02-29 13:21:05 -08:00 |
|
geeksville
|
2c8c7ac8d6
|
if phone ble stack is hosed restart it
|
2020-02-25 09:28:47 -08:00 |
|
geeksville
|
601aeb83d7
|
BLE sw update kinda works again
|
2020-02-24 15:47:53 -08:00 |
|
geeksville
|
7ed5a3efac
|
make SafeBluetooth Closable
|
2020-02-24 15:34:17 -08:00 |
|
geeksville
|
bdd6e5de6c
|
gracefully handle when an esp32 bluetooth link slowly browns out
|
2020-02-17 18:46:20 -08:00 |
|
geeksville
|
10ad07e136
|
we now fetch any new rxmessages when they arrive at the radio
|
2020-02-10 15:31:56 -08:00 |
|