geeksville
ba91920154
fix autobug: if user has location disabled, warn that we can't provide it to mesh
2020-04-25 07:33:51 -07:00
geeksville
51efde08c0
0.5.6 if we lose connection during initial radio download, fail gracefully
2020-04-24 15:59:01 -07:00
geeksville
e302848607
0.5.5 only try to set max MTU once, if it fails consider phone buggy
2020-04-24 15:49:34 -07:00
geeksville
3e89510f52
Some phones have buggy race conditions wrt finding services or characteristics
...
This workaround is: If we fail in that way during initial device connection
we disconnect() and try again 500 ms later.
2020-04-24 15:22:54 -07:00
geeksville
a3db3eca06
We now detect and use the newapi if the device doesn't offer the old one
2020-04-23 12:08:34 -07:00
geeksville
17edf75b95
setting now works using the new ble api
2020-04-23 11:24:57 -07:00
geeksville
a5eaa057a1
new ble api approximately works for reading
2020-04-23 11:24:57 -07:00
geeksville
2ced6f5f6a
WIP, begin adding support for the simpler BLE api
...
https://github.com/meshtastic/Meshtastic-esp32/issues/69
2020-04-23 11:24:57 -07:00
geeksville
6f5c7b2452
move logging to the IO thread
2020-04-22 08:20:57 -07:00
geeksville
8ec8b038b6
Increase MTU _before_ discovering services, because it will speed up the link
2020-04-22 08:10:23 -07:00
geeksville
b63ebadf72
track # of text messages received/sent
2020-04-22 07:59:07 -07:00
geeksville
b194659e8a
Fix autobug: some BLE implementations might not be completed
...
with service enumeration by the time they call the discover services
callback. Therefore be careful to not touch "service" until after
the 500ms delay everyone on stackoverflow says these buggy drivers need.
2020-04-22 07:25:07 -07:00
geeksville
35c745d93f
track total time connected to mesh
2020-04-21 14:46:52 -07:00
geeksville
671bafa05f
don't leak macaddrs into logs - could be possibly personally identifying
2020-04-21 08:21:42 -07:00
geeksville
c00ca9b3db
move notify later, to see if the autobug is _all_ BLE transactions or just notfiies
2020-04-21 07:57:07 -07:00
geeksville
bfff5f6215
fix autobug that occurs if the service gets destroyed immediately after creation
2020-04-20 20:44:21 -07:00
geeksville
47ba4f0243
oops I broke from scratch installs - seen on a Z2 Pro
2020-04-20 15:38:53 -07:00
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
428ea596b0
fix autobug: exceptions become RemoteException when crossing service boundary
2020-04-20 10:15:43 -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
25740c4fe4
don't leak user name in logs
2020-04-20 08:48:42 -07:00
geeksville
8c2d046255
properly show 'disconnected' while changing between radios
2020-04-20 08:27:08 -07:00
geeksville
62a64dd782
new cleaner approach of not whacking services seems to aprox work
2020-04-20 07:46:06 -07:00
geeksville
cde3f2dec2
WIP - doesn't yet build, but changing to set the device addresses the correct way
2020-04-19 20:06:11 -07:00
geeksville
1e47895904
fix a couple of old/rare autobugs
2020-04-19 18:12:11 -07:00
geeksville
39eb6664da
we now save node & msg db across service invocations
2020-04-19 17:25:20 -07:00
geeksville
ca1ada085e
use parcelize to eliminate boilerplate code
2020-04-19 12:00:41 -07:00
geeksville
613e4f7ec4
make aidl interface strongly typed
2020-04-19 11:56:06 -07:00
geeksville
5784138c96
Fix #11 : we now keep a record of past messages in the persistent service state
2020-04-19 11:47:34 -07:00
geeksville
6c0e56920d
fix part of #11 - show sender name in notification
2020-04-19 09:33:41 -07:00
geeksville
f13c05862d
update protos
2020-04-19 09:23:57 -07:00
geeksville
5036cb906b
#14 : not ready - but I need to do other stuff - so disabling for now
2020-04-18 18:45:50 -07:00
geeksville
b4bf682df0
#14 : WIP we now show the new GUI properly
2020-04-18 16:30:30 -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
eff21e6e80
don't leak location data into logs
2020-04-13 15:23:46 -07:00
geeksville
d1afb6fac6
don't leak personal data into logs
2020-04-12 10:56:45 -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
geeksville
2ba398cc51
fix this autobug:
...
https://console.firebase.google.com/u/0/project/meshutil/crashlytics/app/android:com.geeksville.mesh/issues/9ca00f8a87bb62f10c78009f450b13b8
2020-04-10 17:49:43 -07:00
geeksville
69e6b285c6
we now allow changing BLE connection to different meshtastic devices on the fly
2020-04-09 13:28:44 -07:00
geeksville
606dc0fd07
turn off gestures - they are confusing with the map view
2020-04-07 12:32:42 -07:00
geeksville
f2d43332f7
Making app aware of device sleep states, Fix #4
2020-04-04 17:00:38 -07:00
geeksville
83c1bfda69
use coroutines in the mesh service to move processing out of the GUI thread
2020-04-04 14:37:44 -07:00
geeksville
1e34e77fe9
only force refresh of the BLE service table the first time we talk
2020-04-04 14:37:13 -07:00
geeksville
ab31542fd8
bootstrap the mesh service if someone sets our radio macaddr late
2020-03-30 17:36:09 -07:00
geeksville
088ba687d4
if we receive packets early in app start, wait to process them till we have a nodedb
2020-03-30 17:35:33 -07:00
geeksville
81a1283148
Android can cache BLE service descriptors. But our device descriptors
...
can change still (because 'progress'). So force android to reread those
descriptors while we are in alpha.
2020-03-30 16:44:48 -07:00
geeksville
28f488a394
log device errors via analytics
...
related to https://github.com/meshtastic/Meshtastic-esp32/issues/53
2020-03-24 13:48:00 -07:00
