What can an AI assistant do with no signal?

What still works with the radio off

More than most people expect. Anything the phone computes for itself keeps running: alarms, timers, notes, the calendar, the calculator, downloaded music, photos and the index built over them, text recognition inside images, autocorrect and next-word prediction. Recent phones also run speech-to-text on the device for common languages, which is why dictation often keeps working when nothing else does.

Satellite positioning can work without cellular or Wi-Fi on many phones because the receiver listens for satellite signals. Navigation still depends on the device and app, and maps, place search, traffic, or other data may need to be downloaded in advance.

Translation works if the language pack was downloaded. A language model works if its weights are sitting in storage. The rule underneath both is the same. The asset has to already be on the device, and it usually arrived over a network you had at the time, which is the part people forget until the first time they need it.

What cannot work, however good the model is

The line runs between computing and fetching. A model can reason over what it holds. It cannot know today’s weather, a live price, a departure gate, or the message someone sent you an hour ago, because none of that is inside it. No amount of local capability closes that gap, and no honest assistant should imply otherwise.

Sending is the same problem in reverse. Mail, messages, calls, shared documents and anything with another person on the far end need a working link by definition. So does anything that checks a license or an account on a server, which is why some apps that do their real work locally still refuse to open when they cannot reach one.

The failures that look like successes

This is the category worth learning to spot. Ask an assistant something with no signal and a refusal is a good outcome. It tells you the truth immediately, and you go and solve the problem another way. The bad outcome is the interface that accepts the request, shows it in a list as though it were done, and holds it in a queue until the radio comes back.

Queued work then arrives out of context. The message sends three hours late. The reminder lands after the thing it was for. Cached answers are the same fault wearing different clothes: a stale figure shown without a timestamp reads exactly like a fresh one. The useful question is what the screen would look like if the request had failed, and whether you could tell the difference.

One bar is worse than none

A dead connection often fails differently from a weak one. Depending on client timeouts and retry behavior, a fading or congested link can add waits before the app reports a failure. That is the version of no signal that feels broken rather than offline: spinners, half-drawn screens, and an assistant that takes far longer to say it cannot help than it would have taken to say so at once.

Airplane mode, no cell service and no Wi-Fi are three different states, and in-flight Wi-Fi is not offline at all. If you want to know what your phone does without a network, switch off everything, including the Wi-Fi that airplane mode lets you turn back on.

Test it on your next flight

Ten minutes with every radio off tells you more than any specification sheet. Run the handful of requests you actually make in a normal day, and watch the failures at least as closely as the successes. What you are measuring is not how much still works. It is whether the phone tells you the truth about the part that does not.

• Ask for current information that is not stored locally, such as a live departure update. The assistant should explain that it cannot fetch it.
• Set a timer, an alarm and a reminder, then check that all three exist on the device rather than waiting to sync.
• Dictate a long paragraph and see whether the words appear as you speak or never arrive at all.
• Translate a sentence into a language you have never used on that phone. That is the test of whether the pack is local.
• Send a message, then look at what the interface claims. Whether it admits the failure is the whole test.
• Open the map and find yourself on it without searching for anything.