NTsocial Application User Guide

2. Profile Settings

2.1 Getting to know your Profile page

Your Profile page is a one-stop hub with three types of settings: public identity information that others can see, local preferences that affect only your phone, and optional BLE, LoRa, and high-speed history controls.

• After editing fields like Tagline, Bio, Location, Website, Email, or social links, press Publish to make the new version the official profile state others can sync.
• Changing your Nickname often updates your own UI and future outgoing messages first, but that still doesn't mean the full profile has been formally republished.
• Change Avatar follows its own flow. Once you pick an image, NTsocial usually processes and sends it directly, so avatar-only changes typically don't need another tap on Publish.
• Language, Long Range Mode, High-speed Wi-Fi sync, the LoRa gateway, and UTFind are local controls, not public profile fields.
• Long Range Mode (LE Coded PHY S=8) is BLE long range, not LoRa.
• Meshtastic / LoRa gateway lets you choose NTsocial MeshLink (recommended) or the official Meshtastic app. Only one is active at a time; enabling it doesn't make every chat use LoRa or auto-bind channels.

2.2 Page layout & access

Open the app and tap Profile on the bottom navigation bar. You'll usually see the following blocks from top to bottom:

1. The title and avatar area.
2. Node Contribution.
3. MESH Pet.
4. Nickname.
5. Basic Info.
6. Social Links.
7. Language.
8. Publish.
9. Long Range Mode (LE Coded PHY S=8).
10. High-speed Wi-Fi sync.
11. Meshtastic / LoRa gateway and gateway-app selector.
12. Community tag finding (UTFind).
13. About NTsocial.

2.3 Identity, avatar, and visibility

At the top of the page you'll usually see two different identity visuals side by side.

• Identity image: a stable image generated from your fingerprint or key material — handy for recognizing someone even if they change their nickname.
• Custom avatar: the picture you want others to associate with you.
• Change Avatar: opens the system image picker, processes the selected image, and normally sends the avatar change directly.
• Transport limit: text-based profile data usually syncs more easily than the avatar image itself. A far-away node might learn that your profile text changed before it receives the new avatar file.

2.4 Editing your public profile text

The fields under Nickname, Basic Info, and Social Links are the main public text parts of your profile.

2.4.1 Nickname

• Each edit is saved locally right away.
• New outgoing messages may start showing the new nickname before the rest of the profile is formally republished.
• If you want member cards, author cards, and profile sync to all converge on the same newest version, go ahead and press Publish after you finish editing.

2.4.2 Basic info

The Basic Info block usually contains Tagline, Bio, and Location.

• Tagline: a short one-line summary.
• Bio: a fuller self-introduction.
• Location: manually entered text like a city or region — it's not live GPS.
• Privacy rule: leave anything blank if you don't want to reveal it.

2.4.3 Social links

The Social Links area usually contains Website, Email, GitHub, Twitter / X, and Instagram.

• These are raw user-entered identifiers or URLs.
• Displaying a website, email, or social handle here doesn't mean NTsocial has verified it.
• Only enter the links or IDs you actually want others to see.

2.5 Local-only controls

These controls affect only your own phone and are not public profile fields.

2.5.1 Language selector

The language block switches only the UI on your own phone.

• English
• 繁體中文
• 日本語
• Changing language doesn’t require Publish.
• Changing your UI language doesn’t change anyone else’s app language.

2.5.2 Node contribution

• This value reflects how much your node has helped relay or backfill text for others.
• It's closer to a relay contribution score than a social reputation level.
• Text synchronization is what mainly counts here, not image delivery.

2.5.3 MESH Pet

• MESH Pet is a fun optional visual that responds to your node contribution state.
• You can collapse it, and it doesn't affect ordinary communications. It's not part of your public profile.

2.6 Connectivity and optional services

The lower part of Profile now presents the current controls in this order: BLE Long Range, unified high-speed Wi-Fi, the selected LoRa gateway, and UTFind. BLE remains the communication baseline when every optional control is off.

2.6.1 Long Range Mode (LE Coded PHY S=8)

• This is BLE long range — it's not LoRa.
• Both devices need Coded PHY plus extended-advertising support and both users need to enable the mode.
• Mutual opt-in requests bidirectional Coded PHY with S=8 immediately; standard discovery remains active in parallel.
• If a device doesn't support it, NTsocial will show an unsupported message and keep the switch disabled.
• Think of it as “stretch BLE farther,” not “turn the phone into a LoRa radio.”

2.6.2 MeshLink / Meshtastic gateway

• Under Gateway app, choose NTsocial MeshLink (recommended) or the Official Meshtastic app. Only one provider is active at a time.
• MeshLink is the default managed option. Open it to pair and configure radio endpoints; NTsocial then reads the prepared radio-channel catalog. With the official app, that app owns the current radio connection and exposes its channels through the compatibility service.
• In Channels, MeshLink radio channels may be grouped by node. Bind each joined NTsocial channel to the intended radio endpoint and radio channel; several NTsocial channels may intentionally share one radio route.
• If a radio entry appears expired or a binding no longer resolves after the radio catalog changes, open the route dialog and select the current endpoint again.

2.6.3 High-speed Wi-Fi sync

• The single High-speed Wi-Fi sync switch replaces the older separate Aware and Direct controls. NTsocial automatically uses the fastest compatible implemented bearer.
• Wi-Fi Aware can serve compatible Android peers; Wi-Fi Direct can serve compatible Android or Windows paths when supported. Hardware, Android version, Nearby Wi-Fi permission, and sometimes Location services determine availability.
• The layer accelerates authenticated exact-history and eligible attachment work. It is not the discovery baseline and does not replace BLE live messaging.
• Read the card status: Off, standing by, connecting or syncing, finishing synchronization, or temporarily unavailable. When unavailable, BLE remains usable.

2.6.4 Private Wi-Fi file links

• Large-file controls appear only inside a one-to-one private chat. Tap the connection pill or choose files and then use Connect & send.
• The peer receives a named incoming-link request and must accept it. The ready pill shows whether the link is using Wi-Fi Aware or Wi-Fi Direct.
• Select one or more files, review the count and total size, add or remove items, then send. The receiver separately accepts or declines each offered file.
• This is a direct device link with no server or internet path. See Chapter 10 for transfer states, verification, and security boundaries.

2.6.5 UTFind community finding

• UTFind is off until you explicitly agree and provide a per-install service key. It is not required for NTsocial messaging.
• When enabled and NTsocial is on duty, it scans nearby FT/UT Bluetooth tags and reports the tag identifier, this phone's location, and time to UTFind (UTTEC).
• Failed reports are encrypted locally, up to 5,000 pending records, and retried later. Turning UTFind off stops scanning and deletes records that have not been uploaded.

2.7 Publish, sync, and common situations

2.7.1 What Publish changes

• Publish packages the current profile text as the newest official version and pushes that state outward.
• It matters most for Tagline, Bio, Location, Website, Email, and social links.
• Nickname may already look updated locally before you publish, but publishing is still the cleanest way to keep everyone on the same newest profile state.
• Avatar-only changes, language, Long Range, high-speed Wi-Fi, gateway, and UTFind changes don't require Publish to take effect locally.
• Published text can later travel over any usable sync path, including LoRa-backed background sync. Avatar image files still depend much more on BLE behavior.

2.7.2 Where others see your profile

• The People page and its detail view.
• Author cards shown from posts or replies.
• Other lists or info cards that display your nickname, tagline, or short profile summary.

2.7.3 Recommended workflows

1. Update your self-introduction: edit the text fields, then press Publish.
2. Change only the avatar: press Change Avatar and wait for it to process. If you also changed text fields, press Publish afterward for those text changes.
3. Test BLE long range: confirm both devices support LE Coded PHY S=8 and enable it on both ends.
4. Use LoRa with NTsocial: install and configure the radio in NTsocial MeshLink (recommended) or the official Meshtastic app, select that gateway in Profile, then bind the intended NTsocial channel from Channels.
5. Speed up history or send a large private file: enable High-speed Wi-Fi sync; NTsocial selects the compatible Aware or Direct bearer. Keep BLE enabled because it remains the discovery and fallback baseline.

2.7.4 Misunderstandings and quick fixes

• The screen changed, so everyone already received the new profile: not necessarily. Press Publish after editing text fields.
• Changing nickname means the full profile is already synced: not necessarily. The nickname can appear locally and in new messages first.
• Long Range Mode is LoRa: it isn't — it's BLE long range.
• Turning on MeshLink makes the whole app use LoRa: it doesn't. You still have to bind the actual NTsocial channel later.
• Changing the avatar always requires Publish: usually it doesn't, unless you also changed text fields and want those text changes published too.
• Others still see your old bio or tagline: confirm that you really pressed Publish and that a real BLE or LoRa sync path exists between the devices.
• The Long Range toggle is greyed out: the device usually doesn't support LE Coded PHY S=8.
• The Meshtastic gateway isn't ready: open the gateway app selected in Profile and recheck its radio pairing, channel provisioning, permissions, and status.

3. Public Feed

3.1 What is Public?

Public is NTsocial's fully public, unencrypted message wall. Anyone nearby who uses NTsocial may eventually receive what you post there, including people you don't know.

It's open to everyone nearby — not limited to friends, not private, and not encrypted. Think of it as a way for public information to flow naturally between NTsocial devices.

3.2 Why Public matters

If private messages are one-to-one and channels are for groups, Public is NTsocial's way of letting strangers exchange information openly — no infrastructure needed.

• You don't need to add a friend, know who the other person is, or join a group first.
• You don't need a cell tower, Wi-Fi, SIM card, or cloud server.
• As long as nearby people are using NTsocial, public posts can keep moving between devices.

3.3 How Public works and the privacy rule

The core idea behind Public isn't to imitate a normal social-media feed. The point is to let public messages travel through real people carrying NTsocial devices.

• Because the content is public and unencrypted, NTsocial can synchronize, backfill, deduplicate, and relay it more efficiently.
• As you walk, ride, wait, or move through crowds, your phone can gradually collect public posts already carried by nearby users.
• Your own public posts can also keep spreading as other people carry them onward.

3.4 Opening Public and reading the layout

Open the app and switch to Public. The page has three simple layers:

1. The title and notification bell at the top.
2. The list of public top-level posts in the middle.
3. The composer at the bottom for writing and sending a new post.

3.5 Reading the post list

The main list shows top-level public posts. Replies stay attached to their own thread rather than cluttering the main wall.

• The main wall is meant to stay easy to scan.
• If a post has replies, you open that thread from the reply control or reply count.
• Message cards show the sender-captured date and time in your device's local time zone.
• To discard a local copy, long-press the card and swipe it at least halfway. This does not recall or delete the message on anyone else's device.
• This is useful when you want to quickly observe what nearby users have recently made public.

3.6 Create text and image posts

The Public page mainly supports plain text posts, image posts, and public replies.

1. Type your message in the composer.
2. If needed, choose one image and enter a nonblank caption.
3. Check again that you are not revealing private information.
4. Press Send.

• A text-only post is fine.
• A text-plus-image post is also fine, but the image cannot be sent without a caption.
• If image preparation or preview fails, use the visible retry or reselect action instead of assuming the image was attached.
• The image is public too, so faces, documents, or location clues in the image count as public disclosure.

3.7 Replies and author cards

When you reply to a public post, your reply is public too — it isn't a private message or an encrypted response.

• Use the reply control under a post to open the thread view.
• The thread view usually shows the original post, all visible replies, and your own input box.
• You can also open the author's info card to understand who posted the message.
• Opening an author card isn't the same as opening a private message.

3.8 Notifications and sync on the move

The notification bell controls whether new public posts actively notify you. The feed can keep changing as you move because NTsocial exchanges public content whenever new peer links appear.

• If you're already reading Public, extra notifications matter less.
• If you're elsewhere in the app or it's in the background, new public posts may trigger a notification.
• The unread control tracks message-level targets and jumps to the next unread item; reaching the item or the newest viewport consumes it.
• You don't need to refresh manually — public posts arrive as devices meet, synchronize, and backfill nearby content.
• This isn't cloud fetching from the internet. It depends on real NTsocial users and real device encounters nearby.

3.9 Public vs private messages vs channels

• Public: fully public, unencrypted, open to nearby strangers, best for public observations and broad local sharing.
• PRIVATE MESSAGE: one-to-one communication meant for a specific person.
• Channel: a bounded shared space for a topic, team, or workflow, often with more deliberate membership and optional encryption.

3.10 Best uses, misunderstandings, and quick fixes

A. Good use cases

• Nearby observations, activity updates, line or crowd information, street conditions, event notes, and other things you want any nearby NTsocial user to be able to read.
• Short field reports with one image.
• Open discussion with people you don't already know.

B. Common misunderstandings

• Public works like a normal cloud social feed: not really. Its key property is human-carried, device-to-device spread.
• Only friends can see Public: false. Nearby strangers may receive it.
• If the list keeps growing, the app must be pulling from the internet: not necessarily. It's likely just meeting new NTsocial devices and backfilling public content.
• Public is fine for private matters: nope. It's specifically the wrong place for secrets.

C. Quick checks

• You posted something and not everyone saw it immediately: Public spreads through real device encounters, not instant cloud broadcast.
• The Public list isn't growing: check whether there are actually other NTsocial users nearby, whether the app is running normally, and whether you're in an environment where real encounters can happen.

4. People Page

4.1 Your People page

The People page isn't just a contact list. It combines the people you can interact with in NTsocial and the wireless-state information from Meshtastic into one screen.

• The upper half is the NTsocial interaction area for finding people, checking who is online, entering private messages, and managing favorites and blocks.
• The lower half is the Meshtastic diagnostic area for watching node and gateway health.
• Tapping an identified person row in the upper half normally opens PRIVATE MESSAGE directly.
• This is a global people page, not the member list for one specific channel.

4.2 Two halves: NTsocial and Meshtastic

The easiest way to understand this page is to think of it as two layers with different purposes.

• Upper half: person-to-person interaction. It answers, "Who can I interact with right now, and who should I tap for private messages?"
• Lower half: radio and network-state observation. It answers, "Which Meshtastic nodes can the gateway currently see, and how healthy is that side of the network?"

4.3 Opening the page

Open the app and tap People on the bottom navigation bar. From top to bottom, you'll usually see:

1. The online NTsocial people list.
2. Friends.
3. Blocked.
4. Meshtastic Nodes.
5. Gateway Health.

• The top online list may not have a separate "NTsocial" title, but that's what it functionally is.
• Meshtastic Nodes and Gateway Health appear only when the selected Meshtastic gateway is enabled and exposes current state.

4.4 Reading the online list

The top list isn't a permanent account directory. It's the set of NTsocial identities currently recognized as recently active and practically reachable.

• A person appearing here feels more like "recently interactive" than "saved forever."
• If someone disappears from this live list later, that doesn't mean your relationship, favorite status, or message history was deleted.
• The first line usually prefers the published profile nickname when available.
• The second line may show a tagline, bio, website, a short identifier, or a waiting-for-identity message.
• Rows with unread private messages often rise to the front. After that, stronger nearby signal usually sorts earlier than weaker signal.

4.5 Starting Private Messages and Viewing Profiles

The upper list is the main entry point for one-to-one private messaging.

• Tap once: open PRIVATE MESSAGE with that person directly.
• Long-press: open the fuller profile detail card for that identified person.
• If the row still says identity is waiting or not fully resolved, some actions may be temporarily unavailable.

4.6 Badges, Signal, Favorites, and Blocking

• Unread badge: means that private conversation currently has unread content from that person. Opening the conversation usually clears it.
• Signal and dBm: when there's no unread badge, the right side often shows nearby NTsocial / BLE reachability rather than LoRa diagnostics.
• Star: add or remove the person from Friends.
• Block: add or remove the person from Blocked.

4.7 Friends list and blocked list

Friends isn't the same as "currently online." It's your own saved list of people you want easy access to.

• People can stay there even while offline.
• Tapping a friend still opens the private message screen directly.
• The blocked list is mainly a management area, not somewhere you'd go to start a conversation.
• Blocking someone doesn't make that radio presence disappear from the physical world. A currently detected device may still appear in live observation areas.

4.8 When Nobody Is Around

If the page says there are currently no connections, it only means the live NTsocial area at the top has nobody to list right now.

• It doesn't mean your Friends list was erased.
• It doesn't mean your Blocked list was erased.
• It doesn't mean your private-message history disappeared.
• It doesn't automatically mean LoRa is broken.

4.9 Checking Meshtastic Nodes and Gateway Health

The lower half is diagnostic, not conversational. Meshtastic Nodes shows what the current Meshtastic side can hear, and Gateway Health summarizes radio-side load and health.

• A node row may show the node name, hops, SNR, RSSI, and lastHeard.
• lastHeard means when the gateway last heard that radio node. It doesn't mean that NTsocial user just spoke in private messages.
• Gateway Health often includes battery, voltage, channel utilization, and air-util-tx style indicators.
• These lower sections are for technical observation, not for opening private messages.

4.10 People vs. Profile vs. Channel Members

• People: global person interaction, private-message entry, favorites, blocked list, and Meshtastic diagnostics.
• Profile: where you edit and publish your own public identity data so other people can see the newest version.
• Channel members page: a member list for one specific channel, including that channel's reachability tools such as All Ping.

4.11 Workflows, Common Mistakes, and Quick Fixes

A. Recommended workflows

1. Open a private message: go to People, find the person in the live list or Friends, then tap the whole row.
2. Keep someone easy to find later: tap the star so that person stays in Friends even when offline.
3. Read the full profile: long-press the identified person row instead of tapping once.
4. Check LoRa-side health: scroll downward to Meshtastic Nodes and Gateway Health rather than assuming the upper half already tells you everything about the radio link.

B. Common misunderstandings

• The Meshtastic node list is my private-message contact list: nope — it's diagnostic only.
• The People page is the same as a channel member list: not quite. The People page is global.
• Friends only shows people who are online right now: actually, keeping offline people handy is one of its main purposes.
• If someone isn't in the live top list anymore, the old private conversation must be gone: not true. The live list is dynamic, but your conversation history and saved lists are a separate layer.

C. Quick fixes

• You tapped a row and nothing happened: check whether identity is still unresolved or still waiting.
• You want to see profile details instead of chatting: long-press the identified person row.
• You see no live NTsocial connections: keep scrolling and check Friends, Blocked, and, when LoRa is on, the Meshtastic diagnostics below.
• You can see Meshtastic nodes but still can't start a private message: that's normal. The radio node list isn't the NTsocial private-message entry list.

1. NTsocial Overview

Modern communications infrastructure is highly developed, but it's also surprisingly fragile. During natural disasters, regional conflicts, or sudden network outages, traditional systems that depend on cell towers and centralized servers often fail right when they're needed most. NTsocial was built for exactly these extreme conditions — a decentralized social and tactical communications platform.

NTsocial follows a core design principle: don't depend on external networks. Using Bluetooth Low Energy (BLE) as its backbone, NTsocial turns smartphones into independent communication nodes and automatically links them into a local mesh network with multi-hop relay capability — even without 4G/5G or Wi-Fi. Through this network, you can send public, channel, and encrypted text messages, share images and voice clips, and even use standalone push-to-talk (PTT) voice.

Every nearby node can help store and forward eligible messages. On supported phones, mutual Long Range opt-in requests Bluetooth Coded PHY with S=8 while standard discovery stays active. Optional MeshLink / LoRa routing can extend explicitly bound channel text and supported profile, channel, and ATaK state beyond BLE; images, voice, PTT, ordinary live media, and baseline recovery remain on BLE. The unified high-speed Wi-Fi layer creates short-lived authenticated paths for exact-history work and approved private files; it is not an internet dependency or a replacement for BLE discovery.

As a communications backup for disaster zones and field operations, NTsocial tightly integrates offline maps, map object management, location reporting, and decentralized social coordination. Our goal is to preserve a basic channel for freedom of expression and information flow in the harshest conditions, so you and your teammates can stay connected when conventional networks go silent.

The guide follows the five main tabs, then adds focused chapters for the current private-message, high-speed Wi-Fi, LoRa, and UTFind workflows:

• Profile Settings: managing your public identity, language, and network preferences.
• Public Feed: reading, writing, and replying to truly public posts that spread through nearby NTsocial users.
• People Page: opening private messages, reading profile summaries, managing favorites and blocks, and checking Meshtastic node health.
• Channels in NTsocial: creating, joining, securing, and using channels, including chat, ATaK, and PTT workflows.
• Offline Map Management System: loading and configuring map data, themes, elevation (DEM), and tracks.
• ATaK and Meshtastic Workflows: location reporting, tactical object management, LoRa Sync, and long-range routing setup.
• Private Messages and High-speed Files: protection states, shared secrets, direct-link approval, transfer progress, and SHA-256 verification.
• UTFind and App Tools: explicit consent, tag reporting, pending uploads, MESH Pet, and build information.

1.1 First launch and permissions

1. Use Android 8.0 (API 26) or later on a phone with Bluetooth Low Energy. BLE is required; Wi-Fi Aware, Wi-Fi Direct, camera, and LoRa hardware are optional.
2. Allow Nearby Devices / Bluetooth. On Android versions that require it for BLE scanning, allow location permission and turn on the system Location service. Core peer discovery does not read your GPS track merely because Android requires this switch.
3. Allow notifications and remove battery restrictions if you need the mesh foreground service to stay reliable in the background.
4. Grant optional permissions only when you use their feature: Nearby Wi-Fi for high-speed sync/files, microphone for voice/PTT, camera for QR scanning, and actual precise location for ATaK or UTFind reporting.
5. Complete your nickname and profile, press Publish for profile text, then meet another NTsocial device nearby to confirm discovery before adding Wi-Fi or LoRa layers.

5. Channels in NTsocial

In NTsocial, a channel is a shared communication space for a team, a family, a group of friends, or people nearby. It's more than a simple chat room — depending on how you set it up, a channel can carry regular conversation, encrypted messages, ATaK location data, map objects, or Meshtastic-routed text.

5.1 What Is a Channel?

You can join multiple channels at once, and each one can serve a different purpose. Some are open discussion rooms, some are password-protected, and some are dedicated to ATaK teamwork.

• Important: Two channels can show the same name and still be different channels.
• Why: Every channel has its own channel ID, creator information, and short code.
• Best practice: When joining, don't rely on the name alone. Check the creator, lock icon, and channel details so you don't enter the wrong channel.

5.2 Picking the Right Channel Type

• Public channel: Best for open discussion, local event coordination, and easy discovery by nearby users. No password is required.
• Encrypted channel: Best for a private group, team coordination, or any discussion that shouldn't be readable without the password.
• ATaK channel: Best for search and rescue, field missions, location sharing, and map-object coordination. It uses a password and a location reporting interval.
• LoRa-bound NTsocial channel: Best when you want a specific channel's text and supported state to use a MeshLink LoRa route as well as BLE. Images, voice, and PTT remain available through BLE.
• MeshLink radio-channel page: This is a read-only diagnostic view of radio-channel state. Direct LoRa text entry is intentionally rejected; send social text from a normal bound NTsocial channel.

5.3 Reading the Channels Screen

When you open the Channels tab, the screen is usually divided into three areas: channels you already joined, channels recently discovered nearby, and the Meshtastic channel list.

• Joined channels: Show the name, unread count, and markers such as encrypted, ATaK, or LoRa / Meshtastic status.
• Discovered channels: Show channels your phone has recently seen nearby through beacons or relayed channel traffic. This isn't a global public directory.
• Meshtastic radio routes: Show the current radio endpoints and their channels for diagnostics and binding. MeshLink groups routes by node and keeps expired entries separate so you can reselect a live route.
• Tap: Open the channel.
• Long-press a joined channel: View the full channel ID and short code.
• X button: Leave that channel directly from the channel list.

5.4 Creating or Joining a Channel

Tap the + button in the lower-right corner of the Channels screen to create a new channel. Channel names should be short and easy to recognize.

• Name rules: The name must be 1 to 20 characters long and cannot contain / \ : * ? " < > |.
• Public channel: Enter a name, leave encryption and ATaK off, then create it.
• Encrypted channel: Enter a name, turn on the private / encrypted option, set a password, then create it.
• ATaK channel: Enter a name, turn on the ATaK option, set a password, choose the location reporting interval, then create it.
• What happens next: After creation, NTsocial joins you to the channel immediately and opens the channel page.
• Joining a discovered channel: Tap Join. If the channel has a lock icon, you must enter the correct password before NTsocial can show the content properly.

5.5 Sending Messages, Images, Voice, and Replies

Inside a regular public or encrypted channel, you can use it as a full conversation space rather than a text-only room.

• Text: Send ordinary chat messages.
• Images: Attach pictures and show them inline in the conversation.
• Voice: Record and send voice messages from the microphone.
• Replies: Open a reply thread under a post for focused discussion.
• Author card: Open the sender information card to see the display name and related identity details.

5.6 Members, Online Status, and Push-to-Talk

Tap the member icon in the upper-right corner of a channel to open the member list.

• Search: You can look up members by display name or fingerprint-related information.
• Online / Offline: Lets you quickly see whether a member appears active.
• Signal indicator: Shows a strength estimate based on RSSI.
• PTT call: Use the phone icon to start a push-to-talk call to that member.
• How PTT works: PTT is half-duplex, like a walkie-talkie. You normally press and hold to speak, then release to listen.

PTT is especially useful for hiking teams, search and rescue crews, and other situations where short, direct voice coordination is better than typing.

5.7 Encrypted Channels and Passwords

Encrypted channels are meant for people who should be able to read the same conversation privately. The rule is simple: everyone in that channel must use the same correct password.

• Correct password: Messages can be read normally.
• No password or wrong password: You may only see a placeholder such as an encrypted-message notice instead of readable content.
• Channel-specific: The password protects only that channel. It isn't a master password for the entire app.
• Same-name warning: Two channels with the same name can still have different creators and different passwords.

5.8 ATaK Channels and Location Collaboration

ATaK channels are the most specialized channel type in NTsocial. They're designed for mission-style coordination where position updates and map data matter as much as chat.

• Best uses: Search and rescue, field coordination, disaster response, patrols, and task-based team movement.
• Setup: Create the channel as an ATaK channel, set a password, and choose a reporting interval in minutes.
• Prerequisites: Your phone needs location permission, and device location services must be turned on.
• Channel behavior: The page shows location-related actions, and you can review member location history and coordinates.
• Map objects: ATaK workflows can add, edit, and delete map objects for shared team awareness.

5.9 Meshtastic Routing and Native Channels

Binding doesn't turn an NTsocial channel into Meshtastic itself. It assigns that NTsocial channel to one current radio endpoint and radio channel supplied by your selected gateway app.

• Before binding: In Profile, select either NTsocial MeshLink (recommended) or the official Meshtastic app. Pair and configure the radio in that gateway, then wait for it to report a ready route catalog.
• How to bind: Open the NTsocial channel, tap the LoRa or Meshtastic button in the upper-right corner, then choose the intended radio endpoint and channel.
• One route per logical channel: One NTsocial channel can be bound to one Meshtastic route at a time.
• Shared radio path: Multiple NTsocial channels can point to the same radio endpoint and channel if needed.
• After binding: Text continues to work, but images and voice are disabled in that channel.

The MeshLink channel list shown on the lower part of the Channels screen is different. Those entries open a radio-channel diagnostic view; direct LoRa text entry is not supported there. Send from a normal NTsocial channel after binding it to the desired radio channel.

5.10 Notifications, leaving, and common limits

• Unread count: Joined channel cards show unread numbers so you can see where new activity happened.
• Notification toggle: Inside a channel, use the bell icon in the upper-right corner to turn notifications on or off for that channel.
• Leave from the list: Tap the X on the channel card.
• Leave from inside the channel: Use the Leave action in the upper-right corner.
• ATaK reminder: If you leave an ATaK channel, ATaK reporting and related state for that channel stop for your device.
• Discovery limit: The discovered list only shows channels your phone has actually seen nearby recently, not every channel in the world.
• Password errors: If you join but still see encrypted placeholders, check whether the password is wrong or whether you joined a same-name channel created by someone else.

6. Offline Map System

NTsocial uses a fully offline rendering engine and doesn't rely on Google Maps or other online services. It works anywhere without cellular coverage, but users must import their own map data files. NTsocial supports mainstream formats from the open-source mapping community (.map/.xml/.DEM/.GPX). In Taiwan, we recommend the open-source project “魯地圖” (MOI.OSM - Taiwan TOPO).

6.1 Opening the Map

1. For first-time use, download the latest map data files. Download the .map/.xml/.DEM files.
2. On most Android phones, files are stored in the Download folder. No manual unzip or relocation is needed; NTsocial will handle the files automatically.
3. Tap “Map” from the bottom navigation menu in the app.
4. If no map data has been imported, the app will ask you to select at least one existing map file on your device (for example, a .map file).

6.2 Importing and Switching Maps (.map)

• Open the sidebar and scroll to the “Offline Maps” section.
• If no maps have been imported or you need to add a new one, tap “Import map file (.map/.zip).”
• The file picker will open. Select the .map file stored on your device (or a .zip containing the map).
• After import, tap the filename in the list to activate the map.

Note: The system automatically remembers the last map you used.

6.3 Visual Themes (.xml)

• Rendering themes determine the map’s visual style (road colors, contour display, and more).
• In the sidebar “Rendering Theme” section, tap “Import theme (.xml/.zip).”
• We recommend importing a .zip that includes all assets (images and icons).
• After import, select the theme you want to apply. Choosing “Default” uses the built-in rendering style.

Text scale: If map labels appear too small, adjust “Text scale” in the sidebar. Options range from Small (0.35x) to Extra large (0.85x).

6.4 Digital elevation model (DEM) & hillshading

• The system supports SRTM HGT elevation data for hillshading.
• In the sidebar “Elevation data (DEM)” section, tap “Import HGT (.hgt/.zip).”
• Select the .hgt file that matches your current map area.
• After import, the system automatically overlays hillshading during map rendering.

6.5 Managing GPX Tracks (GPX)

• In the sidebar “GPX tracks” section, tap “Import GPX.”
• After import, check the filename in the list to display the track (blue line) on the map.
• You can select multiple GPX files at the same time for overlay analysis.

6.6 Basic Map Controls

• Zoom: Use two-finger pinch gestures, or tap the + / - buttons in the top-right corner.
• Recenter: Tap the TW button in the top-right corner to reset the view to the default center point (Taiwan).
• Pan: Drag the map with one finger.

7. ATaK Tactical Channel Operations

ATaK channels are designed for outdoor team collaboration. You can create as many ATaK channels as you need, and the map can display multiple channels at once — letting you manage several teams’ geographic information simultaneously. ATaK channels include real-time member location synchronization and map object data. Each member automatically reports GPS coordinates, and each member can create map objects based on their field observations.

7.1 Activating and Showing Channels on the Map

• Tactical channels you've joined are automatically listed in the “ATaK channels” section at the bottom of the left sidebar.
• Open the left sidebar and scroll to the bottom.
• Show/Hide: Check the box to the left of a channel name to show or hide its members and objects on the map.
• Expand info: Tap the arrow to the right of a channel name to view the member list (including last report time) and the map object list.

7.2 Automatic Location Reporting (PLI - Position Location Information)

• After joining a tactical channel, the system automatically reports location in the background. The reporting interval is set by the channel creator.
• Reporting mechanism: The system uses the channel “update interval” to capture GPS coordinates and broadcast them securely.
• Freshness guard: If GPS data is too old (for example, indoors with no fix), the system pauses reporting to avoid sending incorrect coordinates.
• Privacy: Location data is only sent to tactical channels you have joined and enabled. Members can leave channels at any time.

7.3 Tracking Team Members

• Channel members are shown on the map as circular icons.
• Abbreviations: The letter or number inside the circle represents the member identifier.
• Color coding: The system assigns different colors automatically (red, purple, green, blue, and more).
• Details: Tap a member icon to view the full nickname, channel, and the time of the last location update.

7.4 Tactical objects (Map Objects) management

A. Create objects

• Long-press the desired location on the map. Zoom in first for accuracy.
• The system will show the “Create map object” dialog. Fill in the following fields:
• Publish channels: Select the channels to synchronize the object (multi-select supported).
• Name: A short label (for example, CP-1, Target-A).
• Attribute: A short note (for example, resources, food, drinking water, tents, camp, fire).
• Description: Detailed information.
• Icon: Choose a representative symbol from the grid (for example, personnel, medical, hazard, rally point).
• Tap “Create” to broadcast the object to the mesh network.

B. View & edit objects

• Tap an existing object icon on the map.
• The info panel shows the object name, coordinates, attributes, description, and the current “Alive Channels.”
• Edit: Tap “Edit” to update the name or description, or to sync the object to additional channels.
• Delete: Tap “Delete” and choose the channel(s) in which you want to remove the object.
• The system sends a delete operation (Op: Delete) to the selected channels to remove the marker from members’ maps.

8. Meshtastic / LoRa Gateways, LoRa Sync, and Channel QR

NTsocial uses one selected Meshtastic gateway app at a time: NTsocial MeshLink is recommended, while the official Meshtastic app is also supported. The selected gateway owns radio pairing, configuration, route state, and packet transport. NTsocial continues to own the social UI, logical channels, canonical history, BLE, and LoRa scheduling. LoRa is an explicit per-channel option for short text and supported state, not a replacement for the whole app.

8.1 How LoRa Works in NTsocial

Meshtastic in NTsocial is best understood as a selective long-range extension. It's used for specific channel text and tactical state, while the rest of NTsocial still keeps its normal BLE and app-level behavior.

• What LoRa is doing here: It carries very short text and tactical snapshots farther than ordinary Bluetooth links can reach.
• What it isn't: It's not a single switch that turns the whole app into a LoRa-only messenger.
• Where it helps most: Long-range group text, LoRa Sync backfill, ATaK state transfer, and channel-share coordination for teams that already operate with Meshtastic hardware.

8.2 What Uses LoRa and What Doesn't

When a channel is correctly bound to LoRa, not every content type behaves the same way. Also, don't confuse NTsocial's BLE long-range mode with Meshtastic LoRa. They're different systems.

• Main things that can use LoRa: bound NTsocial channel text posts, text replies, manually pasted share links or other text-type share content, LoRa Sync text backfill, latest channel state, member roster updates, profile JSON text updates, ATaK state snapshots, and All Ping.
• Things that don't mainly use LoRa: images, voice messages, avatar image files, PTT / call audio, and ordinary nearby BLE message sync.
• Long Range BLE mode: this is still Bluetooth Coded PHY (S=8) inside NTsocial's BLE stack.
• Meshtastic gateway: this requires either NTsocial MeshLink (recommended) or the official Meshtastic app, a working radio, and a ready compatible radio route.

8.3 Where to Find LoRa-Related Screens

Meshtastic operations are spread across several NTsocial pages. Knowing the layout first reduces a lot of confusion later.

• Profile tab: The Meshtastic / LoRa gateway card appears below the unified High-speed Wi-Fi sync card. Choose MeshLink (recommended) or the official Meshtastic app before enabling LoRa.
• Channels home: A top switch lets you move between NTsocial and Meshtastic.
• Normal NTsocial channel screen: The top-right action area contains Members, the optional ATaK icon, notifications, LoRa / LoRa ON, and Leave Channel.
• Members page: This is where All Ping lives.
• People page: When LoRa is active, it can show Meshtastic Nodes and Gateway Health.
• Map page: If you have joined ATaK channels, the map sidebar can expose ATaK members and object state.

8.4 Getting a Meshtastic Gateway Ready First

Radio setup starts in the gateway app you select in Profile. NTsocial does not pair with the radio directly, and only one gateway app can be active at a time.

1. Install NTsocial MeshLink (recommended) or the official Meshtastic app, then select the same app in NTsocial's Profile.
2. Open the selected gateway, power on the compatible LoRa node, and complete radio pairing there.
3. Set the correct radio region and create or import the physical radio channel you plan to use.
4. Make sure both radio sides use compatible channel settings. Use the selected gateway's setup and status screens to verify provisioning.
5. Return to NTsocial only after the gateway reports a ready route.

• Ownership rule: Pairing, physical channel configuration, radio readiness, and firmware-side queue status belong to the selected gateway app.
• Delivery rule: Local gateway queue acceptance is not proof that another radio received the packet.

8.5 Selecting and Enabling the Gateway in Profile

After your gateway app reports a ready radio route, enable the integration from NTsocial's Profile page.

1. Open Profile.
2. Find the Meshtastic / LoRa gateway card and select NTsocial MeshLink (recommended) or the official Meshtastic app.
3. Turn on the switch.
4. If the selected app is missing, install it and return. If installed but not ready, open that gateway and finish radio setup there.
5. Wait for NTsocial to show that the gateway is ready, then bind the intended NTsocial channel.

• Typical status examples: gateway app missing, provisioning, ready, or unavailable.
• If setup fails: troubleshoot pairing, radio configuration, permissions, and route readiness inside the selected gateway.

8.6 Reading the MeshLink Radio-Channel List

After LoRa is enabled, open Channels and switch to Meshtastic. This is the best confirmation that NTsocial is really reading live Meshtastic data.

1. Open Channels.
2. Switch to Meshtastic.
3. Look for a status banner and a list of Meshtastic channel cards showing the index, name, and uplink / downlink state.
4. Tap one entry, such as [0] Primary or [1] LongFast, to enter the LoRa Channel #N diagnostic page.
5. Direct LoRa text entry is intentionally unsupported there. Send social text from a normal NTsocial channel after binding it.

• What LoRa Channel #N is for: a read-only viewer for MeshLink radio-channel and diagnostic summaries.
• What it isn't: it's not the same as a normal NTsocial chat page, and opening it doesn't bind a normal NTsocial channel.
• If you see APP[256] ... bytes: that usually means NTsocial traffic passed through the Meshtastic app-port path. It's a diagnostic summary, not ordinary chat text.
• Sending rule: NTsocial social text must originate in a normal bound NTsocial channel; the diagnostic page does not bypass that boundary.

8.7 Binding a Channel to LoRa

This is the step that makes a normal NTsocial channel add the MeshLink LoRa text/state path. Turning on global support isn't enough by itself, and BLE remains active.

1. Open the NTsocial channel you want to use.
2. Tap LoRa or LoRa ON at the top of the channel screen.
3. When the Meshtastic route dialog opens, choose the radio endpoint and channel you want to bind. MeshLink routes are grouped by node.
4. If a binding already exists, you can inspect the current selection, switch it, or remove it.
5. After that, the NTsocial channel remembers the mapping on your own phone.

• One route per NTsocial channel: a single NTsocial channel can bind to only one Meshtastic route at a time.
• Local flexibility: more than one NTsocial channel may still point to the same local radio endpoint and channel.
• Expired route: if a saved radio endpoint or channel is no longer in the current catalog, re-open the route dialog and select a live route.
• Local-only binding: this binding is per device. If both users want to send from NTsocial over the same LoRa path, each user must create the binding on their own device.

8.8 What Changes After Binding

A. UI and message-path changes

After binding, NTsocial still sends channel text over BLE immediately and may also hand an NTsocial envelope to MeshLink for LoRa transport. MeshLink is a radio gateway rather than the final user-facing chat format.

• Channel list change: The routed channel usually shows a LoRa marker. If the same channel is also ATaK-enabled, you may also see a location icon.
• Channel screen change: The top button changes to LoRa ON or an equivalent state label.
• Composer behavior: Text is eligible for the LoRa overlay. Images, voice clips, and PTT remain available through BLE and never enter MeshLink / LoRa.
• Receiver rule: The receiver should use NTsocial because LoRa carries an NTsocial envelope rather than raw conversational Meshtastic text.

B. Getting message length right

Each MeshLink command carries one complete NTsocial envelope of at most 180 bytes. The user's usable text is therefore shorter because the envelope also includes NTsocial headers and metadata.

• Diagnostic page: It is read-only and cannot send raw LoRa text.
• Bound NTsocial channel: The complete envelope must fit within 180 bytes, so the usable text is shorter.
• Character width matters: Chinese, Japanese, emoji, and other multibyte characters consume more space than plain Latin letters and digits.
• Practical rule: Treat bound NTsocial LoRa chat as a very short text channel rather than a place for long paragraphs.

C. How to tell whether a received message came in over LoRa

In a bound NTsocial channel, the most useful check is usually the receiving side rather than your own sent-message bubble.

• Received message: If a message arrived through Meshtastic, the sender name usually shows a LoRa marker.
• Your own outgoing message: Bound text is also sent over BLE immediately, and your own bubble doesn't prove whether MeshLink accepted the parallel LoRa copy.
• Scope reminder: Meshtastic binding doesn't switch the entire app into LoRa mode. Private chats and the regular public feed still use other paths.

8.9 LoRa Sync and Background Updates

LoRa support isn't just about live channel text. NTsocial also uses the long-range path to backfill and refresh selected state in the background.

A. LoRa Sync for missing text

• What it does: if two users share the same LoRa-bound NTsocial channel and one side missed part of the text history, NTsocial can backfill that text over LoRa in the background.
• When you feel it most: after being offline, after a weak route recovers, or after you re-encounter a node from the same channel.
• What it mainly backfills: text posts, text replies, and text-type share cards.
• What it doesn't backfill as LoRa text: images, voice, avatar image files, or PTT audio.

B. Status sync beyond chat text

• Channel state: latest channel title, summary, and related metadata can stay more current over LoRa.
• Member roster: member-list freshness is improved because roster state can sync in the background.
• Profile JSON: nickname, bio, tagline, and other text-based profile fields can sync even when avatar images don't.
• ATaK state: location and tactical state snapshots can also participate in the background sync path.

8.10 Verifying MeshLink / LoRa is actually working

The cleanest verification order is:

1. Confirm MeshLink is ready and the intended radio channel appears first.
2. Bind an NTsocial channel to the same compatible radio route.
3. Send one very short message in the bound NTsocial channel.
4. Confirm that the other side receives it in NTsocial and check whether the received message shows a LoRa marker.

• If the NTsocial envelope doesn't fit the MeshLink transport limit, the LoRa copy isn't sent; the normal BLE path remains active.
• During testing, avoid keeping both phones in a situation where direct NTsocial BLE mesh is obviously strong, or it becomes hard to tell which transport really delivered the message.
• Advanced users: If you use adb or logging tools, you can inspect diagnostic files or logcat entries for Meshtastic app-port traffic, but most users don't need this to complete setup.

8.11 Testing Reachability with All Ping

All Ping is a quick way to see which members in an NTsocial channel can currently answer you and whether the response path involved LoRa.

1. Open any NTsocial channel.
2. Tap the Members icon near the top right to enter the member page.
3. Tap All Ping at the top right of that page.
4. Review member states such as Waiting, Temporarily unreachable, xx ms / x.x s, or an extra LoRa marker.

• If the channel is LoRa-bound: All Ping can make use of both BLE and LoRa.
• If the channel isn't LoRa-bound: the feature still works, but it behaves more like a nearby BLE reachability test.
• Where results appear: Ping results stay on the member page and don't become normal chat messages.

8.12 Checking Node and Gateway Status

The bottom People tab isn't just for contacts. Once LoRa is enabled, it's also a handy place to check the health of the Meshtastic side of the network.

• Meshtastic node list: You'll typically see a node name together with hops, SNR, RSSI, and lastHeard. In practical terms, fewer hops usually means a more direct path, SNR and RSSI are signal-quality references, and lastHeard tells you how recently the node was heard.
• Gateway health: This section usually shows indicators such as battery, voltage, channel utilization, and air-util-tx. It's useful when you suspect low power, a busy channel, or unstable packet delivery.

8.13 Running ATaK Over LoRa

If you need long-range tactical collaboration, LoRa binding and ATaK channel settings must work together.

1. Create or mark the NTsocial channel as an ATaK channel.
2. Set the password and location update interval required by that ATaK channel.
3. Open the same channel and bind it to the correct Meshtastic radio endpoint and channel with the LoRa button.
4. Keep NTsocial's background service active and confirm that location permission is granted.

• Why both layers matter: LoRa binding alone doesn't automatically turn a channel into an ATaK channel.
• What LoRa helps carry: position reports, ATaK settings, map objects, and related latest-state snapshots.
• Best order: first verify short-text delivery, then expand into ATaK once the base Meshtastic path is stable.

8.14 Sharing Channels via QR Codes

NTsocial can package joined channels into a shareable QR workflow. This is especially useful for field teams that need fast channel distribution.

1. Open Channels and tap the floating + button.
2. Select the action used to generate a share QR.
3. Choose one or more channels you already joined.
4. Generate the preview and confirm the bundled channel list.

• What the preview shows: selected count, a large QR image, the list of packaged channels, and notes about how importing works.
• Typical share options: save PNG, share externally, or send the share inside NTsocial as a private-message share card.
• Important behavior: the built-in “send inside NTsocial” flow is a private-message workflow. It isn't the same as dropping the share into an arbitrary channel, and it doesn't automatically inherit a channel’s LoRa route.
• Capacity: one QR currently has a practical limit of about 12 channels.
• Security note: encrypted-channel QR shares don't contain the plaintext password itself. They carry verification material so the receiver can later validate the password they enter, and generation can fail if the local device lacks the needed key material.

8.15 Importing Shared QR Codes

NTsocial supports several ways to receive a shared channel bundle.

• Direct scan: use the channel action menu to open the QR scanner.
• Import from image: pick a saved PNG or screenshot and let NTsocial detect the QR.
• Import from an NTsocial share card: if someone sent a channel-share card inside NTsocial private chat, use the card’s import action.
• External handoff: NTsocial can also handle supported share intents or an ntsocial://channels/import?... style deep link.

• Import result summary: you may see counters such as imported, updated, already existed, and failed.
• Where imported channels appear: on the NTsocial side of the channel screen, under the discoverable list rather than as auto-joined channels.
• What you still must do: join the channel yourself. If it's encrypted, enter the correct password. If you also want LoRa, bind it locally after joining.
• Important reminder: importing a QR from a LoRa-bound sender doesn't auto-bind LoRa on the receiving phone.

8.16 What Gets Cleared When You Leave

Leaving a channel clears more than just the chat membership. For LoRa and ATaK users, this matters.

• What's typically cleared: the channel's LoRa binding, ATaK settings for that channel, cached ATaK positions and map objects, member-roster cache, LoRa peer-path memory, and All Ping state tied to that channel.
• What to do after rejoining: recheck the LoRa binding and ATaK settings instead of assuming they survived the leave / rejoin cycle.

8.17 Recommended Workflow and Troubleshooting

A. Shortest correct workflow

1. Pair and configure the LoRa node in NTsocial MeshLink, then wait for its ready state.
2. Select NTsocial MeshLink or the official Meshtastic app, then enable the gateway from NTsocial Profile.
3. Confirm that the Meshtastic sub-tab shows the channel list.
4. Create or join the NTsocial channel you actually want to use.
5. Open that channel and bind it with the LoRa button.
6. Send one very short text and verify the receiver sees the LoRa marker.
7. Only after that, expand to All Ping, ATaK, QR sharing, and map-side collaboration.

B. Common misunderstandings

• Misunderstanding 1: turning on the selected Meshtastic gateway makes the whole app use LoRa. In reality, only explicitly bound channel text and supported state use LoRa; BLE still sends bound text and owns media.
• Misunderstanding 2: opening LoRa Channel #N means a normal NTsocial channel is already bound. It doesn't.
• Misunderstanding 3: importing a channel-share QR means you already joined the channel and already have LoRa. You still need to join it and then bind LoRa locally if desired.
• Misunderstanding 4: if the message arrived, LoRa definitely worked. BLE also sends bound text and may have delivered it.
• Misunderstanding 5: the share QR contains the plaintext channel password. It doesn't.
• Misunderstanding 6: sending the share inside NTsocial means it will automatically travel through whatever LoRa-bound channel you were viewing. The built-in share flow is actually a private-message card flow.

C. Frequent problems

• The Meshtastic gateway isn't ready: confirm the app selected in Profile is installed, then open it and verify radio pairing, route provisioning, permissions, and gateway status.
• The MeshLink channel list is empty: check that MeshLink has finished provisioning the radio channel and that NTsocial's LoRa switch is enabled.
• Images still don't travel far after binding: that's expected. Images aren't the main LoRa transport target.
• You imported a QR but can't find the channel: look under the discoverable section of the NTsocial channel tab, not the already-joined list.
• The QR scanner says there's nothing importable: retry with the original PNG, the image-import option, or the raw external share payload rather than a heavily compressed screenshot.
• Encrypted share-QR generation fails: confirm the device really joined the encrypted channel successfully, still has the required local key material, and isn't trying to package too many channels into one QR.
• All Ping often shows temporarily unreachable: recheck LoRa binding, Meshtastic channel compatibility on both sides, node power, and the signal indicators shown under Meshtastic Nodes and Gateway Health.

9. Private Messages & Security

9.1 Start a private conversation

1. Open People and tap an NTsocial person. A normal tap opens the one-to-one conversation; a long press opens the fuller profile view.
2. At the top of the chat, verify the display name and shortened peer identity. The same header contains Favorite, the security control, and the high-speed file-link pill.
3. Type and send text normally. Private images use the image picker; large arbitrary files use the separate Wi-Fi workflow in Chapter 10.

A private conversation is tied to the peer fingerprint, not only the nickname. Nicknames can change, so use the identity visual and security state when the conversation is sensitive.

9.2 Understand the protection states

• Shared-secret protected · higher identity assurance: both devices have derived the same private-message key from a secret you exchanged by another trusted method. This is the optional higher-assurance end-to-end mode.
• Content auto-encrypted · identity not manually verified: after a direct identity-key exchange, automatic DM2 protects the content, but you have not manually verified the other person's identity.
• Automatic identity key changed · basic app protection active: the previously observed automatic identity changed. Treat this as a warning; avoid sensitive content until you understand the change or configure a fresh shared secret.
• Basic app protection · not end-to-end encrypted: NTsocial avoids plaintext wire/history content by using a built-in app key before stronger peer protection is available. Someone who extracts that app key could decrypt or forge content, so this is not E2EE.

9.3 Set a shared secret

1. Open the private chat and tap the security icon in its header.
2. Exchange a strong secret with the other person through a separate trusted channel or face to face. Enter exactly the same value on both devices and confirm it.
3. Save. NTsocial derives an Android/iOS-compatible 256-bit key and stores the derived key inside app-private storage; the BLE hello does not transmit the secret.
4. Reopen the dialog and confirm the header reports the shared-secret state. If you clear the key, that action is local to this device.

Do not send the shared secret inside the same private conversation it is meant to protect. If the two entries on one phone do not match, no key is activated.

9.4 Images, voice, and local controls

• Private text and images can use basic or automatic protection without setup. Private voice messages currently require the same shared secret on both devices.
• The high-speed file bubble shows End-to-end encrypted only when manual shared-secret protection is active. A generic Secured link label means the direct link is authenticated, but it is not the same security claim.
• Long-press and swipe a message halfway to discard only this phone's local copy. It does not recall the message from other nodes.
• Blocking prevents normal interaction with that person on your device; it does not erase copies that have already reached other devices.

10. High-speed Wi-Fi & Large Files

Version 1.5.8 unifies the older Aware and Direct settings into one optional high-speed layer. It uses a temporary peer-to-peer Wi-Fi path—without an internet connection or cloud server—while BLE continues to discover peers, carry live traffic, and provide fallback.

10.1 Enable the optional Wi-Fi layer

1. Open Profile and turn on High-speed Wi-Fi sync. The feature is private and off by default.
2. Grant Nearby Wi-Fi devices when Android asks. Some Android versions or Direct modes also require Location services to be on for peer discovery.
3. Wait for the status to say that Wi-Fi is standing by. If the device is unsupported or permission is missing, the card explains the reason and BLE remains available.

10.2 Exact-history acceleration

• When a compatible peer is nearby, NTsocial can use Wi-Fi Aware or Wi-Fi Direct for an authenticated exact-history session.
• The session can reconcile Public history, channels joined by both peers, the direct private pair, and eligible bounded historical attachments.
• Normal live messages do not wait for Wi-Fi. BLE stays active before, during, and after the short-lived session.
• The Profile card may show connecting/syncing, cleanup, or a last-result explanation. A failed Wi-Fi attempt does not mean BLE messaging has failed.

10.3 Send large files privately

1. Open a one-to-one private chat. Tap the high-speed connection pill, or choose the file action from the composer.
2. If high-speed Wi-Fi is off, accept the one-time enable sheet. NTsocial then asks the selected peer to open a direct link.
3. The peer must accept the incoming link request. Wait until the pill shows Wi-Fi Aware, Wi-Fi Direct, or Ready.
4. Select one or more files. The pre-send sheet shows the number of files and total size; use Add more or remove individual files before confirming.
5. Tap Send. Each file appears in the conversation with progress, throughput, estimated time remaining, and its protection label.

The picker accepts arbitrary file types and does not impose a small chat-attachment limit. Practical limits still include source-file availability, free space on the receiver, and Android's storage provider.

10.4 Receive and verify files

1. Accept the incoming high-speed link only when you recognize the named peer and expected this request.
2. For each file offer, check its name and size, then choose Accept or Decline.
3. The bubble moves through preparing, waiting, queued, transferring, and Verifying SHA-256. Completion is shown only after the received bytes match the descriptor.
4. After completion, use Open file or Share file. Treat unknown file types with the same caution you would use for any external file.

10.5 Security and interruption behavior

• With a shared-secret DM key, file chunks use the higher-assurance E2EE mode. Without it, compatible Android direct links can use authenticated link protection; that state is explicitly not labeled E2EE.
• Windows Wi-Fi Direct file transfer requires the manual shared-secret protection state.
• Files do not travel over LoRa. BLE carries the control relationship and fallback communication; the approved bytes use the temporary Wi-Fi bearer.
• Do not disconnect while a transfer is active. The app warns that an intentional disconnect fails the current transfer and offers no manual resume from that dialog. A transient transport interruption may reconnect internally, but keep the source file available and be prepared to retry.
• If progress stalls, keep both apps active, keep Wi-Fi/Bluetooth enabled, confirm free storage, and avoid switching the active peer. A batch selected for one peer is cleared when you leave or change peers.

11. UTFind & App Tools

11.1 Enable community tag finding

1. Open Profile and find Community tag finding.
2. Turn it on. Read the consent dialog, obtain a per-install revocable service key from the provider, enter the key, and choose Agree and enable.
3. Allow the Bluetooth and location capabilities required by the card, turn on Bluetooth and device Location, and let NTsocial remain on duty when background scanning is needed.

The service key is protected with Android Keystore and is not written to app logs. Use Update service key if authorization expires.

11.2 Read status and pending reports

• Normal progress includes Waiting for NTsocial duty, Getting a location fix, Scanning, Reporting this scan, and Uploading saved records.
• The card shows tags found in the current window, saved records awaiting upload, the last successful report, and the result of the latest attempt.
• If the service is offline, failed reports are encrypted on this device and queued for later upload, up to 5,000 records. Uploading requires an external network path even though BLE scanning itself does not.
• Permission, Bluetooth, Location, rate-limit, authorization, secure-storage, and protocol problems are shown as distinct states. Use the action shown by the card rather than repeatedly toggling the feature.

11.3 Disable and delete pending data

Turn the UTFind switch off and confirm Turn off and delete. Scanning and reporting stop immediately, and all locally saved records that have not yet uploaded are deleted. Data already accepted by the external service is outside this local deletion action.

11.4 MESH Pet and About NTsocial

• MESH Pet is an optional expandable Profile panel. Relay points from successful text-history backfill affect food, HP, mood, and animation; it does not change message priority or access.
• About NTsocial at the bottom of Profile shows the installed app version, project purpose, developer, website, and contact path. Check this page when confirming which build a teammate is using.
• The foreground-service notification indicates that mesh duties are being kept alive. When UTFind is enabled, the notification also identifies tag finding and location reporting.

12. Troubleshooting & Security Notes

Cannot discover nearby people

• Confirm Bluetooth is on, Nearby Devices permission is granted, and Android Location services are on when your OS requires them for BLE scanning.
• Remove battery restrictions if the mesh repeatedly disappears in the background. BLE hardware support is required; Wi-Fi and LoRa are optional.

High-speed link is unavailable or stuck

• Check the unified Profile card for hardware, Nearby Wi-Fi permission, or Location-service guidance. Both users must enable the feature and approve the named private link.
• Keep the source file available, verify receiver storage, and retry the link. A high-speed failure does not disable BLE messaging.

Private-chat identity warning

• If the automatic identity key changed, pause sensitive messaging. Confirm the other person's device state through a trusted channel and configure a new shared secret when higher assurance is required.

UTFind is waiting or not uploading

• Check service key, Bluetooth, precise location permission, device Location, network access, and whether NTsocial is on duty. The card distinguishes rate limiting from expired authorization.

Blank or grid map

• Confirm that the correct .map file is selected in the sidebar.
• Confirm that offline map data for the area has been downloaded.

Location not updating

• Ensure Android location permission is set to “Allow all the time” or “While using the app” for NTsocial.
• If Battery Saver is enabled, background location reporting may be blocked. Add NTsocial to the battery optimization whitelist.

Object sync delay

• The ATaK protocol relies on mesh network transfer. Sync delays can occur when nodes are sparse or signals are degraded.
• If an object is marked as “deleted” but the icon remains, try refreshing or restarting the app.

File compatibility

• Map files only support Mapsforge-compatible formats (OpenAndroMaps recommended).
• When importing ZIP files, ensure there are no extra macOS system files (such as __MACOSX) to avoid import failures.