Add real ACK explanationnn to Android and Apple

This commit is contained in:
GUVWAF 2023-01-12 20:38:00 +01:00 committed by Thomas Göttgens
parent 75f6357d83
commit 23d1fe125d
2 changed files with 9 additions and 7 deletions

View file

@ -23,12 +23,13 @@ Everyone contributes in a different way. Join the [Meshtastic Discord](https://d
Minimum requirement is Android 5 (Lollipop 2014, first BLE support), however at least Android 6 (Marshmallow 2015) is recommended as Bluetooth is more stable. While Android 5/6 are officially supported by Meshtastic, it is *not* recommended that you purchase devices with these versions due to their limited OS support and limited battery life due to age. Many newer models exist that are very affordable. A good resource to use when researching affordable devices is the [LineageOS Supported Devices List](https://wiki.lineageos.org/devices/).
### What is the cloud icon next to the message?
### What does the icon next to the message mean?
- Empty Cloud - Queued on the device to be sent over the mesh.
- Up Arrow - Queued on the app to be sent to your device.
- Check Mark - At least one other node on the mesh acknowledged the message.
- Cross Mark - Not acknowledged or message error.
- Cloud with an up arrow - Queued on the app to be sent to your device.
- Cloud only - Queued on the device to be sent over the mesh.
- Cloud with a check mark - At least one other node on the mesh acknowledged the message.
- Person with a check mark - The intended recipient of your direct message acknowledged the message.
- Cloud crossed out - Not acknowledged or message error.
### How can I clear the message history?
@ -56,7 +57,7 @@ Try forgetting the Bluetooth connection from the iOS/iPadOS/macOS System Setting
### Do the Apple applications provide an indication if the message was acknowledged on the mesh?
Yes, when the message is sent you will first see a `Waiting to be acknowledged...` status beneath the message. If the message is acknowledged by a node on the mesh this will update to `Acknowledged`, but if no nodes have responded it will indicate `Max Retransmission Reached`. If there is an error, the status will update to the appropriate error. Additionally, you can long press on the message and select `Message Details` to view the date/time sent, if ack was received and the time ack was received or the error (if there was one).
Yes, when the message is sent you will first see a `Waiting to be acknowledged...` status beneath the message. If the message is acknowledged by a node on the mesh this will update to `Acknowledged` in orange, which turns into grey when sending a direct message and the intended recipient acknowledged it. If no nodes have responded it will indicate `Max Retransmission Reached`. If there is an error, the status will update to the appropriate error. Additionally, you can long press on the message and select `Message Details` to view the date/time sent, if ack was received and the time ack was received or the error (if there was one).
<!-- Channels -->

View file

@ -117,11 +117,12 @@ The message window operates like most messaging apps. Note that the `(All) Prima
- Long press contacts or messages for options, like delete.
- Long press a node from the Nodes tab to send Direct Messages.
With LoRa (or any radio) there is some uncertainty that the messages has been received, so there is a confirmation built-in to the protocol. There are small cloud icons shown to the right of the messages you send:
With LoRa (or any radio) there is some uncertainty that the messages has been received, so there is a confirmation built-in to the protocol. There are small icons shown to the right of the messages you send:
- Cloud with an up arrow: the message is queued in the app, waiting to be handed to the device.
- Cloud only: the device received the message from the app, and it has been sent and transmitted via LoRa.
- Cloud with a check mark: received at least one node's acknowledgement response. Confirmations could be from any one device.
- Person with a check mark - The intended recipient of your direct message acknowledged the message.
- Cloud crossed out: the initial sender did not receive any confirmation within a certain timeout.
By default there is no long-term store-and-forward of messages, so messages not received during transmission are lost.