10061 Commits

This Branch

This Branch

All Branches

Author	SHA1	Message	Date
m1nl	0fbf7f7e4f	do not use ifdef for HAS_XYZ capability flags	2025-09-02 00:15:57 +02:00
m1nl	b2b5bc1a6d	switch heltec_v2.1 variant to esp-idf sdk with power management enabled	2025-09-02 00:15:57 +02:00
m1nl	ed27f91e94	set serial clock source to ref_tick for esp32 platform	2025-09-02 00:15:57 +02:00
m1nl	050b967d5f	keep CPU at full speed when not power saving and WiFi is enabled	2025-09-02 00:15:57 +02:00
m1nl	32cd4c0868	do not enter light-sleep when GPS is in GPS_ACTIVE state	2025-09-02 00:15:57 +02:00
m1nl	772f4eeaf2	fix failing build for rak4631_eth_gw	2025-09-02 00:15:57 +02:00
m1nl	4f8fc227b8	exit light-sleep state when bluetooth pairing is received	2025-09-02 00:15:57 +02:00
m1nl	ed0eff0a31	fix gpio reset (rtc gpios not supported with esp32c6)	2025-09-02 00:15:57 +02:00
m1nl	c3a49bc97a	another refactor to better handle variants without dynamic light sleep	2025-09-02 00:15:57 +02:00
m1nl	affc8fbeb2	make some variables static, refactor GPIO reset logic	2025-09-02 00:15:57 +02:00
m1nl	9696546458	implement lower cap on power thread interval	2025-09-02 00:15:57 +02:00
m1nl	7d695c4aae	move feature flags	2025-09-02 00:15:57 +02:00
m1nl	15483be937	remove stateNB, improve regular (non-dynamic) light-sleep handling	2025-09-02 00:15:57 +02:00
m1nl	8970cadb75	do not detach button interrupt when going into light sleep	2025-09-02 00:15:57 +02:00
m1nl	177fdd674d	prevent zero-byte read from serial causing too frequent wakeups	2025-09-02 00:15:57 +02:00
m1nl	5f3613d0e1	improve logging ... fix logging make log entry more consistent	2025-09-02 00:15:57 +02:00
m1nl	223859d28b	allow light sleep when MQTT is enabled	2025-09-02 00:15:57 +02:00
m1nl	6d241dbc33	add assertion for gpio_wakeup_enable calls	2025-09-02 00:15:57 +02:00
m1nl	41e79c9820	use events to stay in idle state	2025-09-02 00:15:57 +02:00
m1nl	d0af8168d1	move sleep wake timeout to PhoneAPI	2025-09-02 00:15:57 +02:00
m1nl	62379b7206	switch heltec_v3 variant to esp-idf sdk with power management enabled	2025-09-02 00:15:57 +02:00
m1nl	29f58421de	dynamically adjust measurement interval in power management	2025-09-02 00:15:57 +02:00
m1nl	7c63147ce7	prevent light sleep when modules are busy for more than one timer tick	2025-09-02 00:15:57 +02:00
m1nl	b5ee89cdb9	refactor sleep and PowerFSM to allow dynamic light sleep	2025-09-02 00:15:57 +02:00
Jonathan Bennett	ca79760372	Add support for the RV-3028 on native Linux (#7802)	2025-08-31 21:08:58 -05:00
Wilson	4a669032dc	Change user button to cancel button on meshtiny. (#7789)	2025-08-30 08:37:18 +08:00
github-actions[bot]	b53dd2ec90	Automated version bumps (#7790) ... Co-authored-by: thebentern <9000580+thebentern@users.noreply.github.com>	2025-08-29 19:27:14 -05:00
Ben Meadors	a0e14439cb	Merge pull request #7785 from meshtastic/master ... Backmerge	2025-08-29 13:59:19 -05:00
github-actions[bot]	ed394f5f9d	Update protobufs (#7784) ... Co-authored-by: thebentern <9000580+thebentern@users.noreply.github.com>	2025-08-29 13:58:32 -05:00
Tom Fifield	11db6d4dcc	Can't trust RTCs to tell the time. (#7779) ... Further to https://github.com/meshtastic/firmware/pull/7772 , we discovered that some RTCs have hard-coded start times well in the past. This patch gives RTCs the same treatment as GPS - if the time is earlier than BUILD_EPOCH, we don't use it. Fixes #7771 Fixes #7750	2025-08-29 13:23:14 -05:00
Tom Fifield	10c6836263	Can't trust RTCs to tell the time. (#7779) ... Further to https://github.com/meshtastic/firmware/pull/7772 , we discovered that some RTCs have hard-coded start times well in the past. This patch gives RTCs the same treatment as GPS - if the time is earlier than BUILD_EPOCH, we don't use it. Fixes #7771 Fixes #7750	2025-08-29 13:22:23 -05:00
Ben Meadors	4e03df5ea7	Fix freetext hang (#7781) ... * Fixed freetext hangs by adding canned modules back to self-sourced packets and transition to SENDING_ACTIVE state * Update meshmodule handling	2025-08-29 12:09:22 -05:00
Ben Meadors	9b41131af8	Backmerge (#7782) ... * Merge pull request #7777 from meshtastic/create-pull-request/bump-version Bump release version * Only send Neighbours if we have some to send. (#7493) * Only send Neighbours if we have some to send. The original intent of NeighborInfo was that when a NeighbourInfo was sent all of the nodes that saw it would reply with NeighbourInfo. So, NeighbourInfo was sent even if there were no hop-zero nodes in the NodeDB. Since 2023, when this was implemented, our understanding of running city-wide meshes has improved substantially. We have taken steps to reduce the impact of NeighborInfo over LoRa. This change aligns with those ideas: we will now only send NeighborInfo if we have some neighbors to contribute. The impact of this change is that a node must first see another directly connected node in another packet type before NeighborInfo is sent. This means that a node with no neighbors is no longer able to trigger other nodes to broadcast NeighborInfo. It will, however, receive the regular periodic broadcast of NeighborInfo, and will be able to send NeighborInfo if it has at least 1 neighbor. * Include all the things * AvOid memleak * We don't gotTime if time is 2019. (#7772) There are certain GPS chips that have a hard-coded time in firmware that they will return before lock. We set our own hard-coded time, BUILD_EPOCH, that should be newer and use the comparison to not set a bad time. In https://github.com/meshtastic/firmware/pull/7261 we introduced the RTCSetResult and improved it in https://github.com/meshtastic/firmware/pull/7375 . However, the original try-fix left logic in GPS.cpp that could still result in broadcasting the bad time. Further, as part of our fix we cleared the GPS buffer if we didn't get a good time. The mesh was hurting at the time, so this was a reasonable approach. However, given time tends to come in when we're trying to get early lock, this had the potential side effect of throwing away valuable information to get position lock. This change reverses the clearBuffer and changes the logic so if time is not set it will not be broadcast. Fixes https://github.com/meshtastic/firmware/issues/7771 Fixes https://github.com/meshtastic/firmware/issues/7750 --------- Co-authored-by: Tom Fifield <tom@tomfifield.net>	2025-08-29 10:31:55 -05:00
Wilson	fb34dac08d	Add On-Screen Keyboard for UpDown Encoder and Rotary Encoder. (#7762) ... * Add On-Screen Keyboard for UpDownInterrupt. Pls notice the new keyboard layout was inspired and adviced by https://github.com/csrutil * Add longPress event for RotaryEncoder Press. * Update UpdownInterrupt UP and DOWN on main UI. * Change the interrupt trigger mode from rising edge to falling edge to improve button response.	2025-08-29 23:26:27 +08:00
Tom Fifield	d3e3a91096	We don't gotTime if time is 2019. (#7772) ... There are certain GPS chips that have a hard-coded time in firmware that they will return before lock. We set our own hard-coded time, BUILD_EPOCH, that should be newer and use the comparison to not set a bad time. In https://github.com/meshtastic/firmware/pull/7261 we introduced the RTCSetResult and improved it in https://github.com/meshtastic/firmware/pull/7375 . However, the original try-fix left logic in GPS.cpp that could still result in broadcasting the bad time. Further, as part of our fix we cleared the GPS buffer if we didn't get a good time. The mesh was hurting at the time, so this was a reasonable approach. However, given time tends to come in when we're trying to get early lock, this had the potential side effect of throwing away valuable information to get position lock. This change reverses the clearBuffer and changes the logic so if time is not set it will not be broadcast. Fixes https://github.com/meshtastic/firmware/issues/7771 Fixes https://github.com/meshtastic/firmware/issues/7750	2025-08-29 09:09:13 -05:00
Tom Fifield	5f8503c62d	We don't gotTime if time is 2019. (#7772) ... There are certain GPS chips that have a hard-coded time in firmware that they will return before lock. We set our own hard-coded time, BUILD_EPOCH, that should be newer and use the comparison to not set a bad time. In https://github.com/meshtastic/firmware/pull/7261 we introduced the RTCSetResult and improved it in https://github.com/meshtastic/firmware/pull/7375 . However, the original try-fix left logic in GPS.cpp that could still result in broadcasting the bad time. Further, as part of our fix we cleared the GPS buffer if we didn't get a good time. The mesh was hurting at the time, so this was a reasonable approach. However, given time tends to come in when we're trying to get early lock, this had the potential side effect of throwing away valuable information to get position lock. This change reverses the clearBuffer and changes the logic so if time is not set it will not be broadcast. Fixes https://github.com/meshtastic/firmware/issues/7771 Fixes https://github.com/meshtastic/firmware/issues/7750	2025-08-29 09:08:33 -05:00
Tom Fifield	b0e8321514	Only send Neighbours if we have some to send. (#7493) ... * Only send Neighbours if we have some to send. The original intent of NeighborInfo was that when a NeighbourInfo was sent all of the nodes that saw it would reply with NeighbourInfo. So, NeighbourInfo was sent even if there were no hop-zero nodes in the NodeDB. Since 2023, when this was implemented, our understanding of running city-wide meshes has improved substantially. We have taken steps to reduce the impact of NeighborInfo over LoRa. This change aligns with those ideas: we will now only send NeighborInfo if we have some neighbors to contribute. The impact of this change is that a node must first see another directly connected node in another packet type before NeighborInfo is sent. This means that a node with no neighbors is no longer able to trigger other nodes to broadcast NeighborInfo. It will, however, receive the regular periodic broadcast of NeighborInfo, and will be able to send NeighborInfo if it has at least 1 neighbor. * Include all the things * AvOid memleak	2025-08-28 18:45:46 -05:00
Jason P	dd2f77ea0c	BaseUI Show/Hide Frame Functionality (#7382) ... * Rename System Frame (from Memory) in code base * Create menu options to Show/Hide frames: Node Lists, Bearings, Position, LoRa, Clock and Favorites frames * Move Region Picker into submenu * Tweak wording for Send Position vs Node Info if the device has GPS	2025-08-28 11:23:24 -05:00
Ben Meadors	6c7cff7de2	Merge pull request #7777 from meshtastic/create-pull-request/bump-version ... Bump release version	2025-08-28 06:04:37 -05:00
Ben Meadors	46f797c40d	Merge pull request #7777 from meshtastic/create-pull-request/bump-version ... Bump release version	2025-08-28 06:02:24 -05:00
thebentern	75b01e17bc	Automated version bumps	2025-08-28 10:33:30 +00:00
Ben Meadors	8685436cbb	Merge pull request #7773 from meshtastic/master ... Backmerge	2025-08-27 20:53:55 -05:00
Ben Meadors	834c3c5cc2	Add this back in	2025-08-27 16:24:57 -05:00
Ben Meadors	25a19b49ad	This one is not working yet	2025-08-27 15:18:26 -05:00
Ben Meadors	a4d96bebfb	Drop for now	2025-08-27 14:35:29 -05:00
renovate[bot]	d21d6d2085	Update meshtastic/device-ui digest to a3e0e1b (#7766) ... Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>	2025-08-27 13:53:34 -05:00
Ben Meadors	26c38ffc8e	Remove debug logging	2025-08-27 11:55:27 -05:00
Ben Meadors	237b8908f7	Chainsaw took too much off the top	2025-08-27 09:54:39 -05:00
Ben Meadors	06bccef462	Reinstitute previous streamapi readStream	2025-08-27 07:17:46 -05:00
Ben Meadors	3120bb8fd7	Fix check	2025-08-27 06:50:53 -05:00