Dispatcher Lite expansion
Role-gated incident assignment, release actions, assignment candidates, and compact team accountability stay inside the existing server-authorized organization boundary.
Link'd DMR 0.2.65 Public Beta fixes the withdrawn Code67 startup crash by restoring database schema 12 and the proven Code66 all-features baseline. Install it directly over Code66 or Code67; do not uninstall the app or clear storage. Accounts, channels, contacts, settings, Business data, and user-created Enhanced Privacy keys remain in place. No privacy key is created or shown as saved unless the customer explicitly saves one.
Preserved from the original app
Code68 deliberately preserves the proven Code66 feature set while repairing the Code67 upgrade path. Scanner V2 and the home-screen widget are not in this emergency recovery; they will return only after a correct rebase and live CJ-1 testing.
Role-gated incident assignment, release actions, assignment candidates, and compact team accountability stay inside the existing server-authorized organization boundary.
Operators can deliberately select a path, with a keyed-call interlock. Automatic is included but stays unavailable unless a reviewed production adapter is configured.
Bounded canned status, check-ins, assignments, expiry, deduplication, authorization re-checks, and receipts are included. Nearby stays unavailable without its production transport adapter; no multi-hop delivery is claimed.
Debounced action routing and supported CJ-1 mappings are included. Unknown or unvalidated secondary-key mappings remain unavailable.
Approved accessory profiles expose visible route and keying state, and release transmit fail-closed if the active accessory disconnects.
Audience-bound, expiring, replay-safe plans require local review and use durable receipts, backup, verification, and rollback. There is no silent remote programming.
Support data can include coarse thermal, reconnect, transport, and module state while excluding audio, transcripts, precise location, credentials, tokens, and private keys.
CJ-1 RF users only
Regular Android users do not need this check for cellular PTT. Before enabling CJ-1 RF, the compatibility tool must run because the app sees the same V012 module identifier for selector 05 and selector 01, so it cannot prove that setting by itself. It must confirm all three exact values:
Artifact integrity
The public download is the same signed 72.3 MiB artifact identified below. If the checksum differs, do not install it.