Meshtastic-Android icon indicating copy to clipboard operation
Meshtastic-Android copied to clipboard

[Bug]: Cannot send messages to devices with older FW.

Open brebtatv opened this issue 5 months ago • 10 comments

Contact Details

[email protected]

What happened?

Cannot send messages to devices with older FW.

Image

Image

App Version

2.6.30 and old

Phone

Samsung S24 Ultra, Android 15

Device

RAK4631

Firmware

2.7.3

Relevant log output


Code of Conduct

  • [x] I agree to follow this project's Code of Conduct

brebtatv avatar Jul 21 '25 17:07 brebtatv

I can't reproduce it with different hardware.

I flashed a Heltec v3 with the oldest firmware available, 2.5.20 (stable), and a Heltec Wireless Paper with firmware 2.7.3 (alpha), and both sent/received messages.

Your older firmware may be lower than v2.5.0 (https://github.com/meshtastic/firmware/releases/tag/v2.5.0.9ac0e26), which adds public-key encryption to direct messages.

Image Image Image

barbabarros avatar Jul 21 '25 20:07 barbabarros

This is interesting. I always use the latest App and FW versions. I have no way of finding out the counterparty's version, I only see a yellow lock in the node list and when I want to write a direct message, I see a green lock and the message is undeliverable. All versions of the app with the new look do this. I also tried the app on another Galaxy S10 device, same result. My HW is RAK4631.

brebtatv avatar Jul 22 '25 13:07 brebtatv

Have you enabled HAM mode on any of the nodes? HAM nodes can't communicate with normal nodes. I just noticed this.

barbabarros avatar Jul 23 '25 01:07 barbabarros

No, I don't use HAM mode on any of my devices. I really just use the standard settings.

Image

brebtatv avatar Jul 23 '25 07:07 brebtatv

Different device, same problem.

Image

Image

Image

brebtatv avatar Jul 23 '25 07:07 brebtatv

Just tested, another Android device (Galaxy S10), app deleted with data, third node RAK4631 deleted node DB. Same problem again.

brebtatv avatar Jul 23 '25 07:07 brebtatv

We figured something out, two different behaviors, across two direct message options.

https://github.com/user-attachments/assets/814a3278-5003-470c-b9bb-6d2846997f22

Image

brebtatv avatar Jul 23 '25 08:07 brebtatv

Please fix it, the screen recording video documents the error. The application handles writing a new message in two ways, depending on where the input comes from.

brebtatv avatar Aug 06 '25 11:08 brebtatv

Being demanding isn't going to get it fixed any quicker - we're all volunteers donating time.

jamesarich avatar Aug 06 '25 13:08 jamesarich

also - update your firmware.

jamesarich avatar Aug 06 '25 13:08 jamesarich