I Built a Water Eject Tool for a Muffled Phone Speaker—Here’s What I Refused to Promise

The first version of my phone-speaker project had an attractive shortcut: play a low sound, call it a water ejector, and let the user decide what happens next.

That shortcut was easy to code and hard to defend.

When a phone speaker sounds muffled after a splash, the browser can generate audio. It cannot inspect the grille, measure the liquid, or tell whether the speaker is damaged. I ended up building the product around that boundary. The result is a small Water Eject page, but the more interesting work was deciding what not to promise.

The implementation is deliberately boring

The tool uses the Web Audio API from a user-initiated button. It creates an AudioContext, a sine oscillator, and a gain node, then routes the signal to the device output. The current cycle is 90 seconds. The oscillator moves through a bounded 150–190 Hz range instead of holding one “magic” frequency.

Those numbers are implementation details. They are not a universal optimum, a manufacturer recommendation, or a measured success threshold. Different phones have different drivers, enclosures, meshes, equalization, volume limits, and cases. A frequency that is audible on one device says very little about what is happening on another.

The gain envelope fades in, holds a controlled level, and fades out. The user still controls device volume, so the interface asks for a comfortable level rather than presenting loudness as effectiveness.

The stop button is part of the feature

The first safety question was not “does the tone sound strong enough?” It was “what happens when the user leaves the page?”

The component keeps references to the context, oscillator, gain node, and animation frame. Stopping the cycle cancels the frame, ramps the gain down briefly, stops the oscillator, disconnects the nodes, and closes the context. When the document becomes hidden, the active cycle stops as well. Unmount cleanup follows the same release path.

That prevents a hidden tab from continuing to play audio. It also gives the user a clear model: one visible action starts a short cycle, and leaving the page ends it.

The physical claim had to get smaller

Sound can move a speaker diaphragm. That movement may help shift a small droplet close to an external grille. It does not pull water out of a phone, dry a charging connector, or repair a component damaged by liquid.

So the page begins with preparation: remove the case, disconnect cables and wireless audio, wipe the exterior, and point the speaker downward. It asks users to test familiar audio after the cycle instead of measuring success by a progress animation.

The same distinction matters for dust. Loose, light particles near an external grille are not the same as compacted debris, sticky residue, or material below the grille. A browser cannot see those differences. Repeated playback is not a diagnosis.

The content has an exit path

• If the phone is only lightly wet and otherwise behaves normally, one comfortable cycle may be worth trying.
• If a moisture or charging warning is present, drying and manufacturer guidance come first.
• If there is heat, persistent crackling, silence, power trouble, or multiple failing functions, the browser workflow ends and qualified support becomes the next step.

A product that cannot inspect hardware should not pretend that it has diagnosed hardware.

Why I kept the audio local

The tool does not need a microphone, recording, or uploaded file. The browser generates the signal locally and sends it to the selected audio output. There is no user audio to process.

The trade-off is that the browser still cannot control the phone’s physical volume, audio routing, or speaker condition. Users must disconnect Bluetooth or AirPlay themselves and check that sound is coming from the phone speaker.

The promise I kept

This is a free browser-based sound cycle for a narrow, low-severity situation. It may help move a small nearby droplet. It cannot repair internal liquid damage, replace drying time, or make every muffled speaker recover.

The Speaker Cleaner homepage links the Water Eject tool with those limitations visible. For a physical problem, the boundary is not a disclaimer added after the feature. It is part of the feature design.