NTsocial MeshLink Android operation manual

Android · Meshtastic / LoRa

NTsocial MeshLink operation manual

Connect an Android phone to Meshtastic radios, exchange off-grid text, manage as many as four radio endpoints, and optionally let selected NTsocial channels reach LoRa.

Manual revision · 2026-10-20 Google Play · 1.0.9 Android · 8.0+ Radio connection · Bluetooth

Android screens · 2026-10-20 · MeshLink 1.0.9 and NTsocial 1.7.1. Tap a screenshot to enlarge it. Private content is obscured; radio names and settings are examples.

Fastest safe start: turn on the radio → open Connection → select the radio → wait for synchronization → set the correct LoRa region → open Channels. A region is a radio-law setting, not a language choice.

Chapter 01

What MeshLink does

MeshLink is an independent Meshtastic controller for Android and an optional local gateway for NTsocial. NTsocial is not required for ordinary Meshtastic use.

Two ways to use it

Standalone Meshtastic app

Connect to a compatible radio, send channel or direct text, inspect nearby nodes, and configure LoRa, channels, security, device settings and supported modules.

NTsocial radio gateway

Keep MeshLink connected to the radio while NTsocial sends explicitly bound text and supported state through MeshLink to a Meshtastic channel.

The five tabs, from left to right. Choose a name to jump to its chapter.
  1. Channels
  2. Nodes
  3. MeshCore
  4. Settings
  5. Connection
The five tabs, from left to right. Choose a name to jump to its chapter.

The five main destinations

  • Channels: Channel Hub, channel conversations and direct messages, with an all-radio view and per-radio tabs.
  • Nodes: Devices learned from the mesh and their status, position and telemetry when available.
  • MeshCore: A separate feature path. It is not the Meshtastic radio connection used by the NTsocial gateway.
  • Settings: Radio, device, channel, security, modules, backup, maintenance and app preferences.
  • Connection: Scan for Bluetooth radios, connect, and manage the saved radio fleet.

Current Android boundaries

  • The Android connection screen exposes Bluetooth radios. Do not expect a USB or TCP connection button in this release.
  • LoRa is a low-bandwidth text and state path. MeshLink does not send NTsocial images, voice clips, PTT audio or general files over LoRa.
  • Native Meshtastic radio messaging does not need the internet. Internet can still be used by optional features you explicitly configure, such as MQTT or obtaining firmware.
  • This Android release has no map view. Position values and position-related metrics can still appear in node details.

Chapter 02

Meshtastic essentials

Understanding the two wireless links prevents most setup mistakes: Bluetooth connects the phone to one nearby radio; LoRa connects that radio to other Meshtastic radios.

How one message travels

  1. Android phoneMeshLink creates or displays the text
  2. BluetoothShort-range control link to your radio
  3. Your radioEncodes and transmits a Meshtastic packet
  4. LoRa meshOther nodes receive and may rebroadcast it
Bluetooth range is not LoRa range. Keep the phone close enough to its own radio. The radio—not the phone—provides the long-range LoRa link.

Core terms

Node
One Meshtastic radio. It has a node ID, long and short names, and may report battery, position and telemetry.
Mesh and hop
Nodes can rebroadcast packets. Each relay is a hop. More hops can extend reach but also consume shared airtime.
Region
The legal frequency plan for where the radio is physically used. Set it correctly before transmitting.
Modem preset
A bundle of LoRa speed/range parameters. Radios must use compatible radio settings to hear each other.
Primary / secondary channel
A radio stores channel slots. The primary channel also carries important mesh behavior; secondary channels provide additional conversations.
PSK
The shared channel key. Matching name alone is not enough—peers need compatible radio settings and the same channel key.
Role
Controls node behavior such as ordinary client or routing-focused use. Choose a role for the device's real job.
Airtime
LoRa capacity is limited and shared. Short, infrequent text is healthier for the mesh than rapid or bulky traffic.

What affects range

  • Antenna quality, frequency match, antenna height, terrain, buildings, radio power and modem preset all matter.
  • Line of sight usually matters more than raw transmitter power. Move a node higher and away from metal before chasing aggressive settings.
  • A repeater is not automatically beneficial. Use rebroadcast-oriented roles only when the placement and local airtime plan justify them.
Do not silently set Rebroadcast mode = ALL. It can increase network load and should be a deliberate, team-wide decision.

What delivery indicators mean

Statuses such as queued, sent or acknowledged describe different milestones. A packet admitted to the local database or radio queue is not proof that a remote person read it. In difficult terrain, confirm important messages by a reply or another agreed procedure.

Chapter 03

Install and first launch

MeshLink 1.0.9 supports Android 8.0 or later. A compatible Meshtastic radio should normally run firmware 2.5.14 or later; older firmware can hide features or behave differently.

First-launch flow

  1. Choose English, 繁體中文 or 日本語. You can change the app language later in Settings.
  2. Read the introduction, then grant Nearby devices / Bluetooth so the app can discover and connect to the radio.
  3. On Android 12 or later, Nearby devices permissions cover Bluetooth discovery. Android 11 or earlier also needs Location permission and system Location enabled for scanning. Sharing the phone’s location is a separate opt-in; the app does not request background location.
  4. Allow notifications if you want new-message, new-node or low-battery alerts. Critical alerts are optional.

01 · Choose the app language

First launch with English, Traditional Chinese and Japanese language choices
Choose English, 繁體中文 or 日本語. Later, use Settings → App language to change it.

02 · Allow radio discovery

MeshLink introduction with the Configure Bluetooth button
Continue through the introduction and allow the Bluetooth / Nearby devices request when Android asks. On Android 11 or earlier, scanning also needs Location permission and system Location enabled.

Before the first connection

  • Charge the phone and radio, and attach the correct antenna before transmitting.
  • Enable Bluetooth on the phone and wake the radio.
  • Keep the radio near the phone during pairing and initial synchronization.
  • Stop another controller app from holding the same radio connection.
  • Know the permitted frequency region for your physical location.

Chapter 04

Connect the first radio

Use Connection for discovery and fleet management. Scanning is bounded rather than permanent, which saves power and avoids stale results.

Scan and connect

Bottom navigation→Connection→Bluetooth devices
  1. Power on the radio, place it nearby, and open Connection.
  2. Wait for the scan window. If the device does not appear, restart the scan after confirming Bluetooth permission and radio advertising.
  3. Tap the correct device name/address. Complete the Android pairing prompt or radio PIN if one appears.
  4. Wait until the connection state is ready and the app finishes reading radio configuration, node data and channels.

01 · Find your radio

Connection screen with the Bluetooth scan and Meshtastic_1407 result
Open Connection, then Scan for Bluetooth devices. Match the radio name or last four characters and tap the result. Complete the system pairing prompt if it appears.

02 · Wait for synchronization

Connection screen showing a connected Meshtastic radio and the active node count
Wait for Connected and the radio information. The 1 / 4 count refers to occupied connection slots; a saved device alone does not occupy one.

After the first synchronization

Open Settings → LoRa and set the correct region if the app warns that it is unset. Then verify the owner name and radio channel. Some setting changes make the radio reboot and reconnect.

Region is a legal setting. Select the region where the radio is being operated. Do not copy a teammate's region merely because the channel QR came from them.

Disconnect, reconnect and forget

  • Disconnect releases the active connection slot and keeps the saved endpoint and local history. It also stops automatic reconnect for that radio until you choose Connect again.
  • Connect resumes a saved endpoint. Keep the device awake and in Bluetooth range.
  • Remove forgets a non-primary saved endpoint from the fleet. It is not the same as erasing the physical radio.
  • The compatibility primary endpoint is marked Gateway primary. Its Remove action is hidden, but Disconnect still releases its connection slot and keeps its binding.

Chapter 05

Use up to four radios

MeshLink supports up to four active Bluetooth radio connection slots. Remembered devices do not use a slot. Each radio keeps separate radio data and conversation history; language and theme stay shared.

Register another endpoint

  1. Open Connection and confirm the fleet capacity shown near the radio cards.
  2. Disconnect the current radio if necessary, wake the next radio, then scan and select it.
  3. Let synchronization finish before adding another device. Use the name and address suffix to distinguish similar radios.

Select and inspect a radio

For an active radio, use its Select action to make it current. For a remembered radio, choose Connect first. Switching radios reloads the corresponding local Settings page or Channels root; unsaved edits are discarded with a notice, so save or cancel them before switching.

In Channels and endpoint-aware settings, tabs can show the final four address characters. All aggregates conversations from the fleet. A disconnected radio can still show cached information, but that view is read-only until the endpoint is connected.

Read the radio card

Connected nodes card with selection and disconnect actions
Each card identifies one radio. Disconnect releases its slot and keeps its profile/history under Remembered devices. Tap Connect there when you want to use it again.

What is separate and what is shared

Per endpoint

Radio connection, node database, channels, radio configuration, message history and cached Channel Hub state.

App-wide

Language, theme and other application preferences that do not belong to one physical radio.

Gateway eligibility is explicit. Saving a secondary radio does not automatically make every one of its channels available to NTsocial. Bind only endpoints and routes that NTsocial currently lists as ready.

Chapter 06

Channels and messages

The Channel Hub combines channel and direct conversations. Use the All view for fleet awareness or an endpoint tab to focus on one radio.

Read the Channel Hub

  • Cards can show the endpoint, channel role, lock/security state, latest text, time, unread count and channel appearance.
  • A connected endpoint can open a live conversation. A disconnected endpoint may show cached history as read-only.
  • Channel conversations broadcast to members using the same channel configuration. Direct messages target a node ID.

Send a channel or direct message

  1. Open Channels and choose the intended endpoint or All.
  2. Open a channel card, or choose a node/contact for a direct conversation.
  3. Enter a short text message and send. Keep LoRa messages concise.
  4. Watch the status indicator, but request a reply for operationally important information.

Message tools

Depending on message state and context, the conversation screen supports search, reply, reactions, copy, local deletion, selection, delivery details, resend and reusable Quick Chat text. Deleting a local record does not recall a packet already transmitted over the mesh.

Text path only. Do not paste huge text blocks or expect images, voice, PTT or files to cross the radio mesh. LoRa airtime is scarce.

01 · Choose a radio and channel

Channels hub with the All tab, a radio card and its configured channels
Use All for the overview, or the radio tab to focus on one endpoint. Tap a channel row to open its radio conversation. An offline card marked Cached · read only cannot send.

02 · Write a short text

Radio channel conversation with Hello, MeshLink! entered as an unsent draft
Type in Message and tap the send arrow when ready. The counter is 200 UTF-8 bytes, not 200 characters. This screenshot is an unsent draft. Ask the other person to reply for a receipt check.

Interpreting status

Status familyPractical meaningWhat it does not prove
Queued / pendingThe app or radio path accepted work for later handling.That a LoRa transmission occurred.
Sent / en routeThe packet progressed into the radio network.That the intended person received or read it.
Acknowledged / deliveredA protocol acknowledgement was observed where supported.Human comprehension or action.
FailedThe local path could not complete the send.That no other earlier copy ever left the radio.

Chapter 07

Nodes and radio diagnostics

The Nodes page is the radio's learned mesh directory. Entries age as packets are heard; an old entry is not evidence that a device is online now.

Use the node list

Search and filter the list to find a node, then check its long/short name, ID, last-heard time, hop information and available signal or battery data. Values appear only when the node and firmware report them.

Read last-heard information

Nodes list with radio names, last-heard time, battery and signal information
Open Nodes, search/filter the list and tap the intended node. Check last heard before treating old signal, battery or position data as current. Sensitive IDs and location details are obscured here.

Open node details

Detail pages can contain device information, position, environment, signal, power, air-quality, host, Pax, neighbor and other telemetry. Missing panels usually mean the source node, sensor module or firmware did not provide that data—not that the app failed to draw it.

Traceroute and metrics

Use traceroute sparingly to learn the path when the network supports it. A route can change between packets. RSSI and SNR describe a received radio link, while hop count describes relaying; compare trends instead of treating one sample as a guarantee.

Remote administration

Use remote administration cautiously. It needs a connected radio and appropriate session/security data. Confirm the target node ID before rebooting or changing a remote device, and avoid high-impact changes during an active field operation.

Chapter 08

The MeshCore tab

MeshCore appears as its own top-level destination because it is a separate radio ecosystem and workflow. It should not be confused with the Meshtastic connection managed in Connection.

  • Meshtastic conversations, nodes, channels and the NTsocial gateway use the Meshtastic endpoint path documented in the rest of this guide.
  • Opening or configuring MeshCore does not bind an NTsocial channel to Meshtastic.
  • The MeshCore screen is a preview: production radio transport is not available in this release, and it does not provide an NTsocial gateway route.
Simple rule: for NTsocial + LoRa, prepare the radio in Connection, verify its Meshtastic channel, then bind it from the NTsocial app.

Chapter 09

Channels, QR codes and security

A channel is more than a displayed name. Communication depends on compatible LoRa settings, channel slot and role, and the shared key.

Primary and secondary channels

The primary channel is the radio's main channel slot and participates in mesh behavior. Secondary channels add conversations. Before changing the primary channel on a working fleet, record the existing configuration and coordinate the change with the whole team.

Clear, well-known and private keys

  • Clear / no PSK: channel traffic is not protected by a private shared key.
  • Well-known/default: convenient for public interoperability but not a secret.
  • Custom PSK: only devices with the same key can interpret that channel's protected payload.
A channel PSK is a shared group secret, not verified person-to-person encryption. Anyone who receives the channel QR/key can join that security boundary. Rotate it if exposed.

Share or import a channel set

  1. From the target radio’s card in Channels, choose Manage channels / Scan QR, or open Settings → Channels. Use the scan icon for import and the QR/share control for export.
  2. Generate a QR only for the intended team. Treat the QR like a password when it contains a private key.
  3. On the receiving phone, scan on device and review whether the action will add channels or replace the current set.
  4. Confirm the region separately. Importing a channel is not permission to use the sender's regional frequency plan.

Start from the right radio

Channels hub with per-radio channel management and radio settings controls
From the intended radio card, choose Manage channels / Scan QR. You can also use Settings → Channels. Scanning configures radio channels; it does not join an NTsocial conversation.

Apply and verify

Channel and LoRa changes may reboot the radio. The app can show a neutral pending state while the radio reconnects and configuration is read back. You may leave the page; success is established by verified readback, while an explicit rejection or mismatch is an error.

Built-in NTsocial channel

MeshLink can register its canonical NTsocial Meshtastic channel when an unused slot exists. It does not overwrite an already configured region or modem preset and must fail safely when no channel slot is available. Review the result instead of assuming the radio was reconfigured.

Chapter 10

Radio and app settings

Settings are endpoint-aware. Select the intended radio before changing radio configuration. The app hides options that the hardware, role or firmware does not support.

Radio configuration

  • User: owner long/short name and identity-related radio values.
  • LoRa: region, modem preset, hop and transmit-related options. Change only with a network plan.
  • Channels: primary/secondary channel slots, role and key.
  • Security: device and administration security controls.

01 · Check the radio name

Settings page for Meshtastic 1407 with User, LoRa, Channels and Security
Open Settings or the radio card’s Radio settings. Confirm the radio name first. User, LoRa, Channels and Security change that radio; app language and theme are farther down.

02 · Verify your local region

LoRa settings with Taiwan and MEDIUM_FAST shown as example radio values
In LoRa, check Region and the team’s modem preset. Save only intended changes and wait for reconnect/readback. Taiwan and MEDIUM_FAST are this example radio’s settings.

Device configuration

Depending on the radio, pages can include Device, Position, Power, Network, Display and Bluetooth. Phone-location sharing is opt-in and needs foreground location conditions. A setting shown for one endpoint might not appear for another model.

Module settings

Supported firmware can expose MQTT, serial, external notification, Store & Forward, range test, telemetry, canned messages, audio, remote hardware, neighbor info, ambient lighting, detection sensor, Paxcounter, status, traffic management and TAK. Enabling a module consumes radio, memory, power or airtime; enable only what the deployment uses.

MQTT changes the network boundary. Native LoRa can be completely offline, but MQTT intentionally uses IP networking and a broker you configure. Review its credentials and privacy implications.

App-local settings

Language, theme, privacy/location choices, notification behavior, filters, device links, cache and CSV export belong to the Android app. They are not broadcast as Meshtastic radio configuration. Wi-Fi provisioning may appear for supported radios even though ordinary Android radio connections remain Bluetooth-first.

Administration

Backup/restore protects configuration before risky changes. Reboot, shutdown, factory reset, node-database reset, clean local database and debug tools have different scopes—read the confirmation carefully. A factory reset of the radio is not the same operation as clearing MeshLink's local cache.

Chapter 11

Use MeshLink with NTsocial

MeshLink owns the Bluetooth radio session. NTsocial talks to MeshLink through a protected local app service and routes only channels you explicitly bind.

First time connecting the two apps?

Follow the illustrated beginner guide to prepare MeshLink, choose it in NTsocial, bind a channel and check a short test message. It also introduces the basic controls in both apps.

Connect MeshLink and NTsocial · step by step

Prepare both apps

  • Install current NTsocial and NTsocial MeshLink builds on the same Android phone.
  • Connect MeshLink to the intended radio and let synchronization finish.
  • Set the lawful region and verify the target Meshtastic channel in MeshLink.
  • Keep Bluetooth on and prevent another radio controller from taking the connection.

Choose MeshLink as the provider

NTsocial→Profile→Meshtastic / LoRa gateway→NTsocial MeshLink

Only one gateway provider is active at a time. Wait until NTsocial reports that MeshLink is ready before binding a channel. Selecting the provider does not send every NTsocial conversation over LoRa.

Bind an NTsocial channel

  1. In NTsocial, open a joined channel and tap LoRa in its header to open LoRa Route Settings.
  2. For your first binding, choose one ready radio node and one Meshtastic channel. Current NTsocial with MeshLink can bind several nodes, choosing one channel per node; these bindings are local to this phone.
  3. Save the binding, then return to the channel and send a short, non-sensitive test message.
  4. Ask the recipient to check the message in the same NTsocial channel and reply. Both phones need membership in that channel and compatible local radio bindings.

01 · Enable the gateway in NTsocial

NTsocial Profile showing the MeshLink gateway provider and enabled gateway switch
In NTsocial Profile → Meshtastic / LoRa gateway, choose NTsocial MeshLink, enable the switch and wait for the ready status.

02 · Open the conversation’s LoRa control

NTsocial channel header with the LoRa route control
Open an NTsocial channel you have joined and tap LoRa in its header. A radio channel listed automatically in NTsocial is a separate native-radio conversation.

03 · Choose a route and save

NTsocial route dialog with a Meshtastic channel selected for one radio
Choose the intended channel for each ready radio, then Save. Start with one radio/channel. Check LoRa ON afterward; the other person still needs the same NTsocial channel and their own compatible binding.

Gateway data and delivery boundaries

  • Supported text and compact state/control data can use the bound LoRa route.
  • Images and ordinary files require NTsocial’s supported phone transports and do not travel over LoRa. NTsocial Android 1.7.1 currently has no usable voice-message or PTT transmission path, even if older controls remain visible.
  • “Accepted” can mean stored in local Room data, WorkManager or the radio queue. It never promises RF airtime, remote receipt or a human read.
  • NTsocial owns its canonical conversation history. The native Meshtastic radio chats in MeshLink or NTsocial carry ordinary radio text separately and do not display NTsocial overlay conversations.
  • If the radio, endpoint identity, channel key or gateway provider changes, review and revalidate the binding.

A reliable field test

  1. Disconnect mobile data/Wi-Fi if you want to prove the off-grid path, while keeping Bluetooth enabled.
  2. Use two separated Meshtastic nodes with matching region/preset/channel settings.
  3. Send a unique short phrase from the bound NTsocial channel.
  4. Confirm it in the remote phone’s same NTsocial channel, then send a reply in the reverse direction.

A reply confirms receipt, not the transport. To isolate LoRa, also rule out direct phone-to-phone Bluetooth and relay paths through other NTsocial phones.

Chapter 12

Firmware and maintenance

Firmware controls the radio's capabilities. Update only when the device, connection method and firmware package match.

Update safely

  • Charge the phone and radio, use the correct antenna and keep the devices close.
  • Back up radio configuration and channel information first.
  • Choose the exact hardware model and supported update path shown by the app.
  • Do not close the app, power off the radio or move out of range during an active transfer.
  • Expect the radio to reboot; reconnect and verify region, channels and owner data afterward.

Firmware controls appear only for compatible hardware. The app may offer Bluetooth OTA or Wi-Fi-based provisioning/update paths where supported; their presence does not add a general Wi-Fi radio connection mode to the Connection screen.

Backup, export and clean-up

Use configuration backup before experiments. CSV export is useful for inspection but is not a complete radio restore. Clean local database removes app-side data; node-database reset affects the radio's learned nodes; factory reset is broader. Confirm the scope every time.

After an interrupted change

Keep the radio powered, wait for its normal boot cycle, then reopen Connection and scan. If it advertises, reconnect and read settings before attempting another update. Follow the device maker's recovery procedure when it no longer boots or advertises.

Chapter 13

Troubleshooting

Start at the phone-to-radio Bluetooth link, then the radio configuration, then the over-air mesh. Testing in that order prevents one failure from being mistaken for another.

Radio does not appear or connect

  • Confirm the radio is awake and advertising, Bluetooth is on, and Nearby devices permission is granted.
  • Move close, stop the other controller app, restart the bounded scan, then power-cycle only the radio if needed.
  • If Android pairing is stale, forget the Bluetooth pairing in system settings and pair again.

Connected, but messages do not arrive

  • Compare region, modem preset and channel name/key on both radios; check that the intended channel is enabled.
  • Check antenna, frequency compatibility, battery, placement, last-heard time and whether the correct endpoint is selected.
  • Send one short test and wait. Rapid retries consume airtime and can make congestion worse.

Channel change remains pending

Allow the reboot/reconnect window, then revisit the channel and verify readback. If the radio reports a rejection or the values differ, treat the change as failed; do not assume a green local toast overrules the radio's actual configuration.

NTsocial cannot use the route

  • Verify MeshLink is connected and NTsocial selected MeshLink—not another gateway provider.
  • Open NTsocial's radio catalog again and bind only a currently ready entry.
  • Rebind after replacing a radio, resetting channels or changing the channel key.
  • Remember that a saved secondary radio is not automatically gateway-ready.

Battery or background reliability

Bluetooth, frequent position updates, telemetry, screen-on time and chatty modules all use power. Permit the notifications/foreground service the app explains, keep phone and radio charged, and disable modules the deployment does not need.

Last safety check

Do not rely on one off-grid path for life safety. Carry an appropriate emergency communication method, follow local spectrum rules, protect channel keys, and rehearse the exact radio plan before entering the field.