Support

Getting in touch

Email support.napalarm@gmail.com. To get a useful answer on the first reply, it helps enormously to include:

• Your phone model and Android version.
• What you expected to happen and what actually happened — "the alarm never sounded" and "the alarm sounded three stops late" have completely different causes.
• The route, and whether any of it runs underground or through a long tunnel.
• Roughly what your proximity buffer was set to.

Before you email: common fixes

The alarm didn't fire at all

This is almost always Android stopping the app in the background rather than the alarm logic itself. Several manufacturers apply battery restrictions well beyond stock Android, and they will kill a foreground service that has been running for a while.

The fix is to exempt Nap Alarm from battery optimisation in your system settings — the exact path varies by manufacturer, but it is usually under Settings → Apps → Nap Alarm → Battery. Setting it to "Unrestricted" or the equivalent is what you are looking for.

The alarm fired at the wrong time

Usually a buffer that doesn't suit the journey. A trigger distance that works on an intercity train will fire several stops early on a city bus route, because bus stops sit a few hundred metres apart. The train alarm and bus stop alarm pages go into the numbers for each. If your route goes underground, the subway alarm page explains what the app does when there is no satellite fix, and why a wider buffer helps there.

The alarm fired but made no sound

Check the notification permission first. Android 13 and later require you to grant it explicitly, and if it was declined the alarm can run without ever surfacing anything you would notice. It lives under Settings → Apps → Nap Alarm → Notifications. If headphones were connected, also check that the audio actually routed to them rather than to a device that had dropped its Bluetooth connection.

The position on the map isn't updating

Usually one of three things, in the order worth checking:

• Location permission is set to "While using the app".That is enough while the app is on screen and not enough once it is not. The alarm needs the "Allow all the time" setting to keep tracking with the phone locked.
• Precise location is off. With approximate location only, the reported position can be off by enough to make a few hundred metres of buffer meaningless.
• There is genuinely no fix. Underground, in a deep cutting, or between tall buildings, the phone may report nothing at all. What the app does in that case is on the subway alarm page.

Trip Buddy pairing or alerts aren't working

Pairing needs the six-digit code entered while it is still valid — generate a fresh one from the Trip Buddy Hub if it has been sitting for a while. Note that the escalation only arms during an active trip and only fires if the arrival alarm goes unanswered, so it will correctly do nothing on a trip you ended normally. On the receiving side, your buddy needs notification permission granted for the siren to reach them. The full sequence is on the Trip Buddy page.

Deleting your account and data

Two routes, depending on whether you still have the app installed:

• In the app. Settings → Delete Account. This erases your cloud data from the server.
• By email. If you have already uninstalled, email support.napalarm@gmail.comwith the subject "Account Deletion Request" and the Google email address attached to your account. It is done manually within 7 days.

Uninstalling the app on its own stops any further data collection, even if you don't request deletion.

Other pages worth knowing about

• FAQ — how the alarm behaves with the screen locked, underground, and on battery.
• Privacy policy — what is collected, which third-party services are involved, and your data rights.
• About Nap Alarm — who builds it, and what the app does with the permissions it asks for.
• Google Play listing — current version and release notes.

Bug reports and feature requests are genuinely welcome at the same address.