The Adhan Still Plays. You Just Stopped Hearing It.

Key takeaways

• If the adhan arrives on time and you still miss the prayer, the problem is response, not delivery. The two have different symptoms and different fixes.
• Repeated signals lose their pull. Behavioural research calls this habituation, and the same literature notes that widely spaced signals also recover between presentations, so the effect is a tendency rather than a one-way slide.
• Hospitals count the same effect. A Joint Commission alert cites an estimate that 85 to 99 percent of clinical alarm signals require no intervention, and describes staff becoming desensitised to them.
• Two levers follow from that literature: make the signal a different signal, which the app supports per prayer, and attach the signal to one action decided in advance.
• No study has measured habituation for the adhan. The mechanism is documented in other domains, and the mapping to prayer notifications is reasoning rather than evidence.

There is a version of this problem where the phone is at fault, and a version where it is not. This article is about the second one: the adhan sounds at the right minute, at a volume you can hear, and you keep doing what you were doing. If the sound is missing, late, or cut short, that is a delivery fault with its own settings, and it is covered in a separate guide to setting up reliable adhan notifications. Everything below assumes delivery already works.

What changes when a signal becomes routine

Nothing changes in the sound. What changes is the response to it. Psychology has a name for the effect and a long description of its behaviour: habituation, the progressive weakening of a reaction to a stimulus that keeps repeating.

The reference description is a 1966 paper by Thompson and Spencer, which set out nine behavioural characteristics that later work has largely held to. The first is the core of it: "Given that a particular stimulus elicits a response, repeated applications of the stimulus result in decreased response (habituation). The decrease is usually a negative exponential function of the number of stimulus presentations." The fourth adds the variable that matters here: "Other things being equal, the more rapid the frequency of stimulation, the more rapid and/or more pronounced is habituation."

A 2009 consensus review restated the first as a "progressive decrease in some parameter of a response to an asymptotic level" and then qualified the fourth in a way that matters for prayer specifically. Frequent stimulation, it says, produces "more rapid and/or more pronounced response decrement, and more rapid spontaneous recovery (if the decrement has reached asymptotic levels)." Five signals a day is roughly eighteen hundred a year from the same device, which is repetition on the scale the literature associates with response decrement. But those signals sit hours apart, and the same review says the response partly recovers in gaps like that. The honest reading is a tendency, not a ratchet, and it explains why the fade is gradual and why it can be interrupted.

The same pattern, counted in hospitals

Clinical medicine has measured this at scale, because the consequences there are fatal. The Joint Commission's 2013 Sentinel Event Alert on medical device alarm safety reports an estimate it attributes to an industry study: "It is estimated that between 85 and 99 percent of alarm signals do not require clinical intervention." The consequence it describes is the part worth borrowing: "As a result, clinicians become desensitized or immune to the sounds, and are overwhelmed by information."

What people do next is documented too. The same alert continues: "clinicians may turn down the volume of the alarm, turn it off, or adjust the alarm settings outside the limits that are safe and appropriate for the patient." A 2020 review of prescribing systems found override rates between 46.2 and 96.2 percent, though that review's own point is that a large share of those overrides were clinically appropriate, so the number measures how routine dismissal has become rather than how wrong it is. Separately, a 2026 review of how alert fatigue gets measured recommends tracking it as a significant, sustained decrease in appropriate alert response rates from an established baseline, which is a precise way of saying that the signal did not change and the person did.

How far this evidence reaches

The limit of this evidence should be stated plainly, because it is easy to overstate. All of it comes from clinical alerting, and none of it studied the adhan, prayer, or Muslim users. The closest work found is a 2026 survey of 120 prayer-reminder app users, which measured punctuality, consistency and "responsiveness to application notifications" at a single point in time, and so cannot say whether that responsiveness declines with repetition.

What carries across from the clinical literature is the mechanism, not the measurement: a frequently repeated signal tends to lose behavioural response over time. Turning it down or off is a normal reaction to that, rather than a personal failing.

Make it a different signal

The lever the literature points to is stimulus specificity: response decrement attaches to the particular stimulus that was repeated, not to sound in general. The 2009 review is exact about the vocabulary here, and worth quoting because the wrong word is common. Swapping one signal for a new one tests "stimulus generalization", while dishabituation is something narrower, "an increase in response to the original stimulus and not an increase in response to the dishabituating stimulus". The practical point survives the terminology: a recording you have not been hearing for three years is not the stimulus you habituated to.

Volume is worth a word, because the honest answer is that these sources do not settle it. Thompson and Spencer's fifth characteristic says weaker stimuli habituate faster and that "strong stimuli may yield no significant habituation", which implies intensity does something. But none of the papers cited here tests turning a signal up as a durable fix, so this article does not claim that it fails and does not recommend it as the first move.

Changing the recording costs nothing and takes about a minute. Muslim App's notification settings hold more than one option: thirteen country recordings, an adaptive adhan setting that "plays the recording suited to it, the Fajr adhan at Fajr, the Maghrib adhan at Maghrib", and three short tones named Shelter, Radar and Radial for anyone who would rather keep the full adhan for the masjid. Sounds are set per prayer, so the one you have stopped registering can be changed without touching the other four.

Attach the call to one decided action

The second lever is not about the sound. It is about what has already been decided before the sound arrives. The research term is implementation intentions, and the format is fixed: an if-then plan that names a situation and the response to run in it, rather than a general intention to do better. A named situation attached to a named first move behaves differently from a resolution.

The practical version is small: not "pray when I hear the adhan", which is the goal, but one physical first step tied to the sound, such as standing up, closing the laptop lid, or filling a glass on the way to the tap. The evidence behind if-then planning, and a worked version of it, sit in the article on why Asr keeps slipping, which is where that method belongs. This article is about the signal, not about when the prayer must be performed or what counts as praying on time; those are questions for a qualified scholar rather than for this page. The plan here covers only the seconds after the sound, which is the part habituation takes away.

What the app does, and what it does not

Beyond the sound itself, two settings are worth knowing. Notifications are configured per prayer: each one can be set to sound, silent, or off, each can carry its own advance reminder from five to sixty minutes ahead, and each can be limited to chosen days of the week. That granularity is useful here because it lets you change one prayer's signal and leave the rest as a control.

There is also a channel that is not a sound at all. Muslim App's prayer times for your city drive a home and lock screen widget, described on the site as putting "the next salah, a daily ayah and a name of Allah on your lock and home screen, without opening the app". The site separately describes a countdown to the next prayer on the same surface. Something you read is not something you have spent years learning to filter out.

Two things people ask for are not in the product. Muslim App does not offer a snooze, and it does not offer critical alerts that bypass silent mode. Neither appears anywhere in its own product documentation, and an app that implied otherwise would be answering this problem with a claim rather than a change.

One boundary is worth naming before finishing. If a single prayer is the one that keeps slipping while the other four hold, habituation is an unlikely explanation, because the signal is the same in all five cases. That pattern usually points at the shape of the working day instead.

Where to start

Change one prayer's sound first, because it takes under a minute and it tests the diagnosis directly. If the new recording catches your attention for a week and then fades, that is habituation behaving as the literature describes, and the answer is not a third sound but the if-then step underneath it. Write that step down as one sentence, in the form of a situation and a first move, and keep it small enough to survive a bad day. The settings sit under the notification icon on the prayer times screen in Muslim App on iOS and Android, and the change you are looking for is one prayer, one new sound, this week.