What's Next in ORBII: An Incident Report for the Police, Scream Detection, and a Silent SOS

The next ORBII update adds three things. None of them is a new screen for its own sake. Each one makes a specific part of the emergency pipeline work better: getting the alert out when you cannot speak, and keeping a record of what happened once it is over.

All three are coming in the next release on Google Play. This post is here so you know what they do before you see them, and what they cannot do yet.

An incident report you can take to the police

After an emergency, the question is often not “what happened” but “can you prove it”. The details are spread across a phone: a time, a place, a recording, a list of people who were told.

The incident report puts them in one document. Open any SOS in your history and tap Export incident report. ORBII makes a PDF with:

• when the SOS started and ended, and what started it
• where it started, with coordinates and a map link
• the stored location trail for that period
• whether an audio recording is saved on your phone
• who ORBII alerted, captured at the moment the SOS went out
• who responded

Every time is in India Standard Time, whatever your phone is set to. The PDF goes straight to the share sheet, so you can send it to yourself, a lawyer, or attach it to a complaint.

It is deliberately honest about what it does not have. If there is no stored trail for that period, it says so instead of showing an empty map that looks like you never moved. If a responder’s arrival time was not recorded, it lists them without inventing one. Recordings are named but not embedded, so you can share the original file with its details intact. And the report says plainly that it was generated on your phone and is not a police document.

A scream can start an SOS

ORBII’s Voice SOS already runs a small sound model on your phone, next to the speech recogniser. It listens for screaming, crying and breaking glass, with nothing sent anywhere.

Until now, a scream on its own could not fire an SOS. That was on purpose: sound models hear screams in television, music and children playing, and a safety app that cries wolf gets switched off. A scream only counted when you also said a word like “help” or “bachao”.

The next update adds a switch in Settings: Scream starts an SOS. Turn it on, and a clear scream by itself opens the countdown. It is off by default, it only works while Voice SOS is on, and it always goes through the countdown, so a scream from the next room costs you one tap to cancel.

Shake for a silent SOS

Sometimes making a sound is the dangerous part. Saying a word out loud, or a phone buzzing, can give away that you are asking for help.

The silent shake SOS is for that moment. Turn it on, then shake your phone hard, about ten times in two seconds. You feel one short buzz so you know it registered. Then:

• the screen goes dark
• a silent countdown starts, with no sound and no vibration
• when it ends, your circle is alerted with your live location
• the alert tells them it was a silent SOS, and not to call you first

The live SOS screen also stays dark. Press and hold anywhere to show it.

It needs a hard, deliberate shake on purpose. Walking, running, or a phone bouncing in a bag should not match the pattern. We have not yet tuned that pattern on a wide range of Indian phones, which is why it is off by default and, like everything that can start an SOS on a sensor alone, always goes through the countdown first.

What none of this changes

Every new trigger ends in the same countdown every other SOS uses. You can cancel it, and if you have a safety PIN set, calling off a real SOS still needs the PIN.

Nothing leaves your phone to decide whether you screamed or shook it. And in immediate danger, 112 is still the number to call. ORBII keeps it one tap away from every SOS screen, and none of this replaces it.