Ingress Wiki
Advertisement
Prime-COMM-Button withText
This article or section contains information that is out-of-date.
  • Please replace the old information with up to date information.
  • This may include rewriting sections to ensure they are clear and concise, and wikifying.
  • Reason: Update for Prime, add news tab etc.
Scanner COMM Button

The COMM button is in the lower right corner in Scanner.

COMM is a feature in the Scanner and Intel Map for browsing notifications and chatting between Agents. There are tabs (filters) under COMM: "All", "Faction" and "Alerts".

To disable or enable push notifications for in-Scanner events, use the "Device" tab in the OPS screen. See Device#Notifications.

In-Scanner Chat[]

Mentioned in COMM

Notification for an @mention.

In-Scanner chat is available from two COMM tabs; messages under the "All" tab are public: Agents of both Factions can see them.

Messages sent from the "Faction" tab can only be seen by the same faction. These messages are prepended with [secure] in the "All" tab. However, experienced agents typically do not trust the Faction COMM for any operations chat, since it is easily possible for enemies to see the messages using Double Accounts. Most communities have adopted other means of communication, such as Telegram or Google Hangouts.

Other Agents can be "pinged" by typing @username. This means they will see the message even if the sender is outside their chosen COMM Range. Additionally, they will receive a push notification (if they did not disable it in settings). This can be used to check any Agent's stats, as long-pressing on the @'-mention can be used to open their profile. In the "Faction" tab, this only works for friendly Agents.

COMM-Messages are limited to 256 characters and 10 mentioned Agents.

Notifications[]

Notifications about nearby Agents' actions appear in the "Activities" tab and personalized notifications in the "Alerts" tab. Sometimes remaining stealthy by avoiding notifications can be a tactical advantage, such as for taking down a well-guarded Portal. Notably, Portal Mods can be destroyed without triggering any notifications (e.g. using low-enough Ultra Strikes Ultra Strike that do not reach the Resonators Resonator).

Note that different sets of notifications appear in the Scanner and the Intel Map version of the Activities tab:

Event Activities
(Scanner)
Activities
(Intel Map)
Alerts
Portal Mod destroyed No No No
Resonator Resonator damaged No No Yes
Resonator Resonator destroyed No Yes No
Portal neutralized Yes Yes Yes
Portal captured (1st Resonator Resonator) Yes Yes No
Resonator Resonator deployed No Yes No
Resonator Resonator upgraded No No No
Link/Control Field Δ created Yes Yes No
Portal Mod deployed No No No
Fracker deployed Yes Yes No
Beacon deployed Yes Yes No
Firework deployed Yes Yes No
Battle Beacon Battle Beacon deployed Yes Yes Yes (if Agent owns Portal, its Resonators Resonator or Mods)
Battle Beacon Battle Beacon Conclusion Yes Yes Yes (if Agent participated)
Drone returned Yes Yes Yes (if own was returned)
Scout Controller gained No No Yes
Scout Controller lost No No Yes
Mentioned in Chat No No Yes
Advertisement