-
-
Notifications
You must be signed in to change notification settings - Fork 393
Description
Contact Details
No response
Checklist
-
I am able to reproduce the bug with the latest version.
-
I made sure that there are no existing OPEN or CLOSED issues which I could contribute my information to.
-
I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
-
This issue contains only one bug.
-
I have read and understood the Contribution Guidelines.
-
I agree to follow this project's Code of Conduct
Affected app version
2.7.3 (29319219) google
Affected Android version
Android 15
Affected phone model
Zenfone 8
Affected node model
Heltec Wireless Tracker
Affected node firmware version
2.7.12
Steps to reproduce the bug
- Go to Radio Configuration
- Look at option for Broadcast Interval and Update Interval
Actual behavior
Minimum broadcast interval is 1 hour
Broadcast Interval cannot be selected with precision
Minimum GPS update interval is 60 seconds
GPS Update Interval cannot be selected with precision
Expected behavior
Recently the values in the position tab have been updated, and appear to focus on reducing traffic on metro meshes and improving usability.
While a noble aim, a crucial use case we must support is outdoor activities. For meshtastic users performing outdoor activities, such as hiking, the settings recently introduced do not work.
That a hiker is still in a location is highly valuable information, and these changes prevent that from being broadcast more frequently than an hour.
In addition, we have a subset of users who have powered nodes in vehicles for whom accurate position information is very important. The firmware supports them explicitly, but having different behaviour for very small GPS update intervals (<10secs).
Further, there's an important relationship between the broadcast update interval and the GPS update interval. With the new hold times, it's actually more important to consider multiples of 20 seconds than half minutes. The firmware changes break the ability to balance power usage based on knowledge of the GPS chip and firmware features.
Please refer to meshtastic/protobufs#749 for the direction we're heading in the firmware.
Please revert the recent changes until we can discuss further.
Screenshots/Screen recordings
No response
Relevant log output
Additional information
No response