GPS, Callsign, and Media Event Casting

Core Functions

• Connect to an event with a code and callsign.
• Use a callsign as the active operator identity.
• Enable AES-GCM end-to-end encryption with a shared key.
• Share live GPS location from the device.
• Enable or disable microphone publishing.
• Publish a screen share or a front/rear camera stream.
• Bridge RemoteID over ZMQ, USB serial, or Bluetooth serial.
• View active participant callsigns.
• Disconnect and return to standby when finished.

Features

• Code-and-callsign event entry
• Live participant presence
• AES-GCM toggle with optional shared key dialog
• Optional GPS publishing
• Microphone control
• Screen casting and 720p30 camera streaming (front/rear)
• RemoteID Modules: ZMQ endpoint, USB serial, Bluetooth serial
• Night color scheme toggle
• Disconnect notification when a session drops

Basic Use

1. Open TFODev - OPSx (SC) on the Android device.
2. Enter the event code and operator callsign.
3. Tap AES-GCM to enter or clear a shared key if the event requires enhanced encryption that is Fed compliant; leave blank to derive from the code.
4. Toggle Night for low-light color scheme.
5. Tap Connect.
6. Allow microphone, location, camera, or Bluetooth access when prompted.
7. Open Sources to start a camera stream or start screen sharing.
8. Open Modules to configure and start RemoteID publishing (ZMQ, USB Serial, or BT Serial).

Operator Notes

Callsign is the primary identity shown to other units. AES-GCM can be enabled per event; a key left blank derives from the event code so peers match when they use the same code. Drone-side OPSx publishers do not enter this key locally; they inherit the encryption behavior from the SC-configured session. If AES-GCM is not enabled, the session still uses TLS transport encryption, but AES-GCM is the stronger end-to-end encryption mode. GPS, camera, and RemoteID publishing are each opt-in and can run concurrently.