mirror
/
meshtastic-android
kopia lustrzana https://github.com/meshtastic/Meshtastic-Android
1
0
Forkuj 1
Kod Zgłoszenia Packages Projekty Wydania Wiki Aktywność
576 Commity
6 Gałęzie
233 Tagi
85 MiB
Wykres commitów

576 Commity (0.7.5)

Autor SHA1 Wiadomość Data
geeksville 7529bbcfb6 0.6.4 2020-05-11 13:18:18 -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 d811fc6ac4 0.6.3 2020-05-10 21:39:59 -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 8a35f9a856 update google libs 2020-05-09 21:20:02 -07:00
geeksville 1d65542505 add one more string for the visually impared 2020-05-05 11:00:24 -07:00
geeksville cc471530da 0.6.2 2020-05-05 11:00:06 -07:00
geeksville bc5b6dad6d 0.6.2 2020-05-04 20:14:01 -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 45a5d47d21 update protos 2020-05-01 13:43:05 -07:00
geeksville ad707f4a13 New Chinese translations from @Mango-sauce 2020-04-30 19:39:36 -07:00
geeksville 52c47af364 fix some accessiblity warnings 2020-04-29 12:08:13 -07:00
geeksville 3a8ed8bf20 0.6.0 (and update to latest libs) 2020-04-29 11:39:43 -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 56cf723b93 0.5.9 2020-04-26 13:11:26 -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 d28eb97497 fix nokia8 autobug? 2020-04-26 12:26:19 -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 2bd0bc5020 0.5.8 2020-04-26 08:39:36 -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 dd2b6041ac 0.5.7 2020-04-24 16:59:44 -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 4c39d9e3f9 don't let users edit their name when not connected to radio 2020-04-23 11:24:10 -07:00
geeksville 5e57fd69e1 also show failure to bond in the GUI 2020-04-23 09:03:44 -07:00
geeksville 56534f0b89 0.5.4 2020-04-23 08:52:35 -07:00
geeksville ca2cae7003 Don't claim we have bluetooth access until the user grants location 
permissions.  This fixes an ugly behavior when for when the user does
a from scratch install and first runs the app (and the dialog comes up
to grant access).

Previously we were starting our BLE scan for devices before that dialog
has been approved by the user, which Android doesn't return an error for
it instead just silently refuses to show devices.  If the user switched
away from the app and came back, we'd restart our scan and they could see
their device.

This fixes things so that the user doesn't have to switch away from our
app once before the devices appear.
 2020-04-23 08:52:25 -07:00
geeksville 7d76f99731 wait for bonding complete before telling service to connect 2020-04-23 08:22:54 -07:00
geeksville 8220e1210f 0.5.3 2020-04-23 08:03:19 -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 a201de649c 0.5.2 a better fix for the messages send startup condition 2020-04-21 20:59:28 -07:00
geeksville 5abb56ec3f a better fix for the problem of sending messages while device is asleep 
Better just to Observe myId and wait for it to be !null
 2020-04-21 20:48:44 -07:00
geeksville 1558675cc7 0.5.1 fix a crash when sending messages when app hasn't yet connected to the device 
during this boot of android.

Thanks to @b3hr3ns  for the report
 2020-04-21 20:39:35 -07:00
geeksville 2dd37e791d don't let users try to send texts if we haven't received our node ID 
I wanted an and not an or ;-)

Based on the autobug and the great report inhttps://github.com/meshtastic/Meshtastic-esp32/issues/102

I think this should fix the crash described in the messages screen.
 2020-04-21 20:29:34 -07:00
geeksville 322db5ac25 add more Italian from @ohcdh 2020-04-21 15:41:49 -07:00