mirror/Meshtastic-Android
1
0
Fork 0
mirror of https://github.com/meshtastic/Meshtastic-Android.git synced 2026-04-07 23:50:53 -04:00
Code Issues Packages Projects Releases Wiki Activity
525 Commits 17 Branches 297 Tags
d526d11d20c81a0ff4de81f96efdd55578825bca
Commit Graph

357 Commits

Author SHA1 Message Date
geeksville
d526d11d20 Fix #32 
+            // Note: To workaround https://issuetracker.google.com/issues/36995652
+            // Always call BluetoothDevice#connectGatt() with autoConnect=false
+            // (the race condition does not affect that case). If that connection times out
+            // you will get a callback with status=133. Then call BluetoothGatt#connect()
+            // to initiate a background connection.
 2020-06-04 09:35:25 -07:00
geeksville
6a3a763f71 workaround a kotlin(?!) bug 
// FIXME - possible kotlin bug in 1.3.72 - it seems that if we start with the (globally shared) emptyList,
// then adding items are affecting that shared list rather than a copy.   This was causing aliasing of
// recentDataPackets with messages.value in the GUI.  So if the current list is empty we are careful to make a new list
 2020-06-04 08:53:37 -07:00
geeksville
ef61c9acff add note about https://github.com/meshtastic/Meshtastic-Android/issues/32 2020-06-04 08:02:36 -07:00
geeksville
9254a90774 add a min appVersion check, so devices can tell user when android app needs 
update
 2020-06-03 16:16:51 -07:00
geeksville
0b66d813ef message status icons approximately work - still a problem on first send though 2020-05-31 11:23:25 -07:00
geeksville
7506d712ff message status updates are coded but not yet tested. 2020-05-30 19:58:36 -07:00
geeksville
b2d8b30d5b add packetid assignment to the phone side 2020-05-30 17:28:00 -07:00
geeksville
ed4236d8e3 only use the new api now, old device loads have been out a while 2020-05-30 16:23:42 -07:00
geeksville
6031b5eaa0 clean up message API to/from mesh service, to allow clients to get 
updates on message status
 2020-05-30 15:55:47 -07:00
geeksville
67d95039bf begin support for message status 2020-05-30 14:38:16 -07:00
geeksville
38e7e8a783 oops - fix build - default channel name should never be localized 2020-05-29 14:16:16 -07:00
geeksville
05776c2593 fix warnings 2020-05-29 14:00:50 -07:00
geeksville
afedd47258 1 one minute boot delay is probably sufficient 2020-05-24 11:42:22 -07:00
geeksville
4d6ca25caf autobug, prevent redundant notifcations from onConnectChanged 2020-05-24 11:38:33 -07:00
geeksville
238ae9a06c fix autobug, if we don't have a gatt currently, treat as a BLEException 2020-05-24 11:15:13 -07:00
geeksville
38f45a9413 fix autobug that showed on a MIX2 (whatever that is), ignore BLE state changes 
when we don't have a gatt
 2020-05-24 11:07:15 -07:00
geeksville
e6abd9d1a5 autobugs - some phones send bougs onMtuChanged when we are not setting mtu 2020-05-24 11:01:13 -07:00
geeksville
8b3817964e make sync BLE operations timeout a bit shorter 2020-05-24 10:47:02 -07:00
geeksville
6d463334a5 fix autobug racecondition that could occur with non gps devices 2020-05-24 10:46:50 -07:00
geeksville
74449be999 don't spam with autobugs if we just fail because the device is off 2020-05-24 10:46:27 -07:00
geeksville
a191dac0f4 stay with old api for now, because too much change hurts reliaiblity ;-) 2020-05-24 10:12:12 -07:00
geeksville
ae72081917 possible for #30: native mapbox crash 2020-05-24 10:11:48 -07:00
geeksville
4efd25d009 Possible fix #26. It seems some phones don't quite have the services 
list populated at the time they say service discovery has completed.
Make the nasty 500ms delay a 1000ms delay instead
 2020-05-24 09:51:25 -07:00
geeksville
774ab65ece treat radio not connected exception like a remote exception 2020-05-24 09:45:52 -07:00
geeksville
28023b8f42 Fix 27: add timeouts for BLE operations, to protect against buggy drivers 2020-05-24 09:45:39 -07:00
geeksville
bba9def20e it has been a couple of weeks since new API rolled out, now just 
always use it
 2020-05-24 08:47:36 -07:00
geeksville
501ca3df9d mark that we want our text transmissions to be reliable 2020-05-21 17:25:04 -07:00
geeksville
6e261fa35e don't let the user send empty messages 2020-05-15 11:55:32 -07:00
geeksville
c06f5f1c39 set aside ble sw update for now 2020-05-15 10:18:15 -07:00
geeksville
3c338aec61 firmware update progress bar kinda works 2020-05-14 11:47:24 -07:00
geeksville
5044c5393f firmware update wip 2020-05-13 17:34:15 -07:00
geeksville
c1388d6bad firmware update button is kinda in 2020-05-13 17:00:23 -07:00
geeksville
6576f5eab5 backend updated to reneable firmware update 2020-05-13 14:47:55 -07:00
geeksville
b4da48beb5 after boot wait even longer - 2 min, we are in no rush anyways 
the phone should be quite less busy by then
 2020-05-11 15:27:53 -07:00
geeksville
407a38594f workaround for slow booting Samsung phones 2020-05-11 13:12:44 -07:00
geeksville
33265c7c2e fix autobug - if someone runs really old device code with buggy bluetooth 
just wait for them to fix their device...

https://console.firebase.google.com/u/0/project/meshutil/crashlytics/app/android:com.geeksville.mesh/issues/1948d9ea376e223f34d7065d1aba39df?time=last-seven-days&sessionId=5EB4DF6800B900016F5DA5AAC26367BE_DNE_1_v2
 2020-05-11 11:44:24 -07:00
geeksville
0b7f853abc fix an autobug - race condition on some phones BLE reconnect 2020-05-10 21:39:49 -07:00
geeksville
877006f26b temp code for testing failures 2020-05-10 21:39:23 -07:00
geeksville
de4cb68930 update to latest protobufs 2020-05-09 21:20:17 -07:00
geeksville
12f7e9a8ce support int based lat/long 
for https://github.com/meshtastic/Meshtastic-device/issues/124
 2020-05-04 08:05:59 -07:00
geeksville
913a0b56fd don't show progress animation once we have a node listed, re #25 2020-05-03 17:58:11 -07:00
geeksville
ee34a7a370 fix missing strings reported by @Mango-sauce 2020-05-01 13:43:57 -07:00
geeksville
f4e96b936f fix an autobug that occurred on a Droid Turbo (whatever that is) 2020-04-29 11:04:15 -07:00
geeksville
d669a06ed7 update protobufs 2020-04-28 18:02:01 -07:00
geeksville
5822dddc6c Fix #23: autobug, if we get mystery BLE error 133 while reading messages 
drop the BLE link and reconnect and try again.
 2020-04-26 13:03:35 -07:00
geeksville
bdda0c031d mark our service as very important. If the service can't run, the gui can't either 2020-04-26 12:26:08 -07:00
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
975c7d41db Rather than waiting for crashlytics to send on next launch, send reports 
immediately.
(related to #20)
 2020-04-24 18:42:57 -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