Root Cause

The firmware has a limited node database size that varies by hardware:

• nRF52: 80 nodes
• ESP32 (basic): 100 nodes
• ESP32-S3 (16MB flash): 250 nodes
• STM32WL: 10 nodes

When the firmware's nodeDB fills up and needs to add a new node, it evicts the oldest non-favorite node. When the evicted node is later re-encountered, the firmware creates a fresh entry with default placeholder values (memset to zero except node number):

• longName: "Meshtastic XXXX" (where XXXX = last 4 hex digits of node ID)
• shortName: "XXXX"
• hwModel: UNSET
• All other fields zeroed

The bug was in MeshService.kt:installNodeInfo() - it unconditionally overwrote the app's stored node information whenever the firmware sent NodeInfo with user data, even when that data was just firmware's default placeholder. This caused users to see nodes lose their real names and revert to generic "Meshtastic XXXX" names after the firmware's nodeDB cycled through enough nodes.

Fix

Modified installNodeInfo() to detect when firmware sends placeholder data by checking both:

1. Name matches pattern ^Meshtastic [0-9a-fA-F]{4}$
2. Hardware model is UNSET

When both conditions are true AND the app has existing valid user data, we preserve all existing user information instead of overwriting it with the placeholder.

This ensures:

• Real user names/data are preserved even when firmware evicts and re-creates nodes
• Legitimate updates (actual name changes, hwModel updates) are still applied
• All other node fields (position, lastHeard, metrics, etc.) continue to update normally
• Message routing works correctly (uses node numbers, not user data)

Draft because it'll take a bit for my nodedb to repopulate to confirm, but after reading firmwawre/app I'm 99.9% sure this will fix