148 commits

Author	SHA1	Message	Date
geeksville	cecc369598	split out common code for USB and BLE links	2020-06-04 12:34:34 -07:00
geeksville	fd100d4492	fix duplicate scan table entries when pairing state changes	2020-06-04 09:58:29 -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	67d95039bf	begin support for message status	2020-05-30 14:38:16 -07:00
geeksville	05776c2593	fix warnings	2020-05-29 14:00:50 -07:00
geeksville	ae72081917	possible for #30: native mapbox crash	2020-05-24 10:11:48 -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	913a0b56fd	don't show progress animation once we have a node listed, re #25	2020-05-03 17:58:11 -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	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	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	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	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	671bafa05f	don't leak macaddrs into logs - could be possibly personally identifying	2020-04-21 08:21:42 -07:00
geeksville	99b66b3396	0.4.9 make app not crash when people try to run this on an emulator ;-)	2020-04-20 21:06:58 -07:00
geeksville	34aa4cde05	if bluetooth was disabled when we started, reattempt device connect later	2020-04-20 09:56:38 -07:00
geeksville	848fcbe53b	Fix #16: Show currently selected radio even if it is sleeping	2020-04-20 08:12:51 -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	fdd3b48364	don't let users try to send texts if we don't have a node id	2020-04-19 12:31:27 -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	840dbd491e	#14: WIP split out the bonding code so it can be shared with new impl	2020-04-18 11:45:11 -07:00
geeksville	18248bd86a	add a "report a bug" button	2020-04-15 14:10:40 -07:00
geeksville	2baa42d963	Finding the activity via the application might return null? (autobug) ... instead capture it in a closure when we know it is guaranteed valid.	2020-04-15 13:21:29 -07:00
geeksville	7fa168ab2c	0.3.9 - fix channel setting autobug and update to latest google libs	2020-04-15 07:52:00 -07:00
geeksville	ba4291f4fd	remove dead code	2020-04-13 17:01:39 -07:00
geeksville	069c0646f4	fix autobug with setting channels - for now allow only while device is awake	2020-04-13 16:00:48 -07:00
geeksville	e4363d04d5	fix autobug - it seems someone out there is running some really old device code	2020-04-12 08:58:09 -07:00
geeksville	042e8d6ebb	map analytics optional	2020-04-11 13:20:30 -07:00
geeksville	eba6fef9fa	handling received channel URLs now works okayish	2020-04-09 17:06:41 -07:00
geeksville	2b588ac7e7	editing and saving channels kinda works	2020-04-09 16:33:42 -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	468e43afc4	fixes after testing on real hardware	2020-04-09 12:22:41 -07:00
geeksville	8c70d5f67d	a few more strings	2020-04-09 11:27:42 -07:00
geeksville	5a90a06580	get ready for translations	2020-04-09 11:03:17 -07:00
geeksville	e4bbdf1d1e	remove old files	2020-04-09 08:24:56 -07:00
geeksville	e7705c83ed	bt scan kinda works again	2020-04-08 21:34:57 -07:00
geeksville	fb06046796	bt scan kinda works	2020-04-08 21:17:23 -07:00
geeksville	c286c56067	add beginnings of settings fragment	2020-04-08 19:20:43 -07:00
geeksville	749103cd09	message sending kinda works again	2020-04-08 17:50:23 -07:00
geeksville	29f0435f18	message fragment kinda works	2020-04-08 17:12:39 -07:00
geeksville	e157bb0140	add beginnings of new messages tab	2020-04-08 16:49:27 -07:00