ATAK-CIV quickstart: install, callsign, basic map

Materials

• Android phone or tablet with enough free storage and a working GPS
• Network access to reach the official ATAK-CIV distribution (see tak.gov conceptually)
• Optional: offline map tiles / data package if you will go off-grid later

Steps

1. Confirm device basics. Enable location services. Note Android version and free space. ATAK is map-heavy — clear room before install.
2. Obtain ATAK-CIV from the official channel. Use the Civilian / public path described on tak.gov (or the current official CivTAK distribution site). Prefer signed packages from the official source. Do not sideload random APKs from forums.
3. Install and grant permissions. Allow location, storage/files (for maps and data packages), and network as prompted. Deny anything you do not need for a basic map session.
4. First launch — callsign. When prompted for callsign / self marker identity, pick a short, unique label your team will recognize (e.g. MF-1). Avoid personally identifying full names if OPSEC matters for your use case.
5. Self marker / team role. Set role/affiliation if offered (friendly / other). Keep defaults if you are only checking the map.
6. Map check. Confirm a basemap tiles in. Pan/zoom. Verify your self marker sits near your GPS fix (outdoors is more reliable than indoors).
7. Optional: drop a point. Long-press or use the point tool to place a test marker. Rename it. Confirm it stays after app backgrounding.
8. Stop here for day one. Networking (TAK server, multicast, data packages) is a separate instructable. Do not join untrusted servers.

Notes / gotchas

• Spelling: ATAK = Android Team Awareness Kit. Not “ATAC”.
• Indoor GPS is noisy — validate outdoors before blaming the install.
• Accounts, EULAs, and export rules change; always follow the current official docs on tak.gov rather than third-party mirrors.
• Battery: continuous GPS + maps drains fast. Bring a pack or dim the screen in the field.