Releases: paulmandal/atak-forwarder
She's Laughing Up At Us From Hell
- Disables Plugin Manages Device by default
- Updates to
libcotshrink
1.0.4 - Updates to Meshtastic 2.2.16
- Supports ATAK 5.0.0
Pierced Through the Heart, But Never Killed
- Updates to MT 2.2.11
- Adds copy & paste for the channel settings
- Updates to the new ATAK plugin API, supports 4.9.0+
- MT 2.2.2+ addresses the service not binding issue many were seeing on Android 13
I Should Not Be Left To My Own Devices
For now the plugin will not support ATAK versions after 4.7.0.x. The plugin API changed in 4.9.x and I don't want to maintain two versions of the plugin codebase for now, so likely we will migrate to the new plugin API in the next month or so. There is also an issue in later versions where the plugin cannot connect to the Meshtastic service that I need to sort out before supporting those versions.
Release Notes:
- Updates to use Meshtastic 2.1.14
- Fixes a bug where a new PSK would be generated each time the plugin starts if one was never set by the user
- Fixes a bug where the device settings would not fully write and the device would reboot in a loop forever
Did You Hear My Covert Narcissism
Note There is an issue on some devices where the plugin cannot establish a connection to the Meshtastic service. This does not appear to happen on all devices, if it is happening you will see the icon switch to display "SVC" in red letters.
Issue: #173
- Updates to work with Meshtastic 2.1.8
- Adds a new icon for "service disconnected" state
- Blocks writing to devices when the service is disconnected (fixes a crash)
- Fixes a bug / crash when comparing the in-plugin channel settings to the device settings (missing boundary check)
Slowly Lurching Toward Your Favorite City
- Fixes crash on some devices related to
MutableLiveData
initial value being set viasetValue()
instead of the ctor. - Add
null
handling forMeshService.connectionState()
returningnull
on some devices
Midnights Become My Afternoons
- Updates for usage with MT 2.0.21 / 2.0.22
- Fix reboot loop issue seen by some users
- Fix crash on some devices when opening the plugin
- Fix device writing issues (hopefully!)
Monster on the Hill
Bug fixes for the 2.0.2 release.
- Fixes a bug where RAK devices with a Bluetooth address ending in
1
would end up with alongName
ending in\
which would break everything. This is not an ideal fix but with no way to differentiate device types at this time it will do. - Updates to work with the latest Meshtastic app (2.0.17) and firmware (2.0.20)
MT 2.0 But For Real This Time
- Updates to the latest Meshtastic (2.0.14)
- Changes the "Disable writing to comm device" setting to "Plugin Manages Device", moves the setting up in the preferences menu
- Stops using
PreSendProcessor
- Handles
RECEIVED
message state from Meshtastic - Fixes a bug where changing the channel settings wouldn't re-write the channel
- Fixes a bug where serial communication would be disabled, which blocks debugging tools from being used on the device
- Silences all haters
2.0.1 - Bugfixes
- Fixes a bug where Meshtastic devices would not be findable in the plugin
- Allows you to disable writing to the Comm device -- if you're having issues getting your devices to communicate try disabling writing to the device at the bottom of the ATAK Forwarder settings and set up your channel in the Meshtastic app
Meshtastic 2.0 Integration
Updates the plugin to work with Meshtastic 2.0.
There are some refactors but not many major changes that are visible to the user.
New Meshtastic features will be exposed in the next release.