Description
First, thank you to all the developers working on this project! The mesh networking capabilities are fantastic, and I really appreciate the work you're putting into MeshCore.
I'm experiencing an issue where the GPS Mode setting resets to "Disabled" every time my device reboots or powers back on. While I understand this might be intentional behavior based on the description in the UI, it creates a frustrating user experience that requires manual intervention after each reboot to restore GPS functionality.
Device Information
- Hardware: RAK WisBlock 4631
- Firmware: 1.9
- App Version: iPhone version 1.31.0. Apple MacBook Version 1.31.0
Steps to Reproduce
- Open Position Settings in the MeshCore app
- Enable "GPS Mode"
- Confirm GPS is enabled and position updates are working
- Reboot or power cycle the device
- Check Position Settings after device comes back online
Current Behavior
The GPS Mode setting reverts to "Disabled" after every device reboot. The UI even notes this behavior: "When your MeshCore device reboots, GPS will be disabled."
Expected Behavior
The GPS Mode setting should persist across reboots. If I enable GPS, it should remain enabled until I explicitly disable it. This is the expected behavior for most device configuration settings.
Impact
- Users must manually re-enable GPS after every reboot/power cycle
- Reduces the utility of GPS position broadcasting for mobile or remote deployments
- Creates potential for missed position updates if users forget to re-enable GPS
- Counterintuitive UX that differs from standard settings persistence patterns
Suggested Solution
Persist the GPS Mode preference to non-volatile storage (EEPROM/flash) so it survives reboots, similar to how other device configuration settings are handled.
Additional Context
This behavior seems inconsistent with other settings that do persist across reboots. Is there a technical reason for this current implementation, such as power consumption concerns or GPS initialization issues? If so, perhaps a compromise could be a user-configurable "GPS startup behavior" option?
Thanks again for your work on this project! Happy to provide any additional information or testing if needed.
Description
First, thank you to all the developers working on this project! The mesh networking capabilities are fantastic, and I really appreciate the work you're putting into MeshCore.
I'm experiencing an issue where the GPS Mode setting resets to "Disabled" every time my device reboots or powers back on. While I understand this might be intentional behavior based on the description in the UI, it creates a frustrating user experience that requires manual intervention after each reboot to restore GPS functionality.
Device Information
Steps to Reproduce
Current Behavior
The GPS Mode setting reverts to "Disabled" after every device reboot. The UI even notes this behavior: "When your MeshCore device reboots, GPS will be disabled."
Expected Behavior
The GPS Mode setting should persist across reboots. If I enable GPS, it should remain enabled until I explicitly disable it. This is the expected behavior for most device configuration settings.
Impact
Suggested Solution
Persist the GPS Mode preference to non-volatile storage (EEPROM/flash) so it survives reboots, similar to how other device configuration settings are handled.
Additional Context
This behavior seems inconsistent with other settings that do persist across reboots. Is there a technical reason for this current implementation, such as power consumption concerns or GPS initialization issues? If so, perhaps a compromise could be a user-configurable "GPS startup behavior" option?
Thanks again for your work on this project! Happy to provide any additional information or testing if needed.