Muhammad Usama
I build and maintain Fix My Speaker — the tool itself, the pages around it, and the source list everything is checked against. This page exists so you know who stands behind the advice, and equally, what I am not claiming to be.
What I am not. I am not an audio engineer, an acoustician, or a phone repair technician, and this site does not pretend otherwise. If a page here tells you something is true, it is because it traces to a manufacturer's own documentation, a published standard, or an established physical constant — not because I am asserting authority. Every one of those sources is listed on the sources page so you can check the claim without taking my word for it.
What I actually did here
Concretely, and all of it verifiable by looking at the site:
- Built the tone engine. Every cleaning mode is synthesised in your browser with the Web Audio API — no audio files, no server. The exact frequencies, sweep periods, modulation and durations are published on the methodology page rather than kept vague, so anyone can reproduce or criticise them.
- Made the audio schedule reliable. The sweep and the
stop are scheduled on the audio clock rather than driven by a
JavaScript timer, because
requestAnimationFrameis paused in background tabs — a timer-driven version can leave a tone playing indefinitely if you switch apps. This is the sort of detail nobody notices when it works. - Compiled and verified the sources. Each cited URL was checked live and read to confirm it says what we claim it says. Where a claim could not be sourced, it is labelled in the text as convention or estimate instead of being stated as fact.
- Wrote the limits sections. Every tool page says what the method cannot fix — torn diaphragms, corrosion, failed amplifiers, sticky residue. That is the part most sites in this category leave out, and it is the part I consider most useful.
- Handle corrections. Reports come to me directly, and the process is described in the editorial policy.
Where the practical knowledge comes from
I build and run web tools in the phone-audio space, and have done for a while. That is not a credential in acoustics — it is something more specific and more useful for a site like this: repeated exposure to what people actually type into a search box when their phone is wet, which answers help them, and which ones waste their time.
That experience is why the pages are structured the way they are. The instruction to point the speaker down is first because forgetting it is the most common reason the tool appears not to work. The Bluetooth warning is prominent because more people are defeated by audio routing to a forgotten car stereo than by any hardware fault. The iPhone page leads with which of the two bottom grilles is actually the speaker, because most people clean the microphone by mistake.
How to hold me to it
The site takes no advertising, no sponsorship and no affiliate commission, and runs no analytics or tracking — you can confirm that last part yourself by opening your browser's network tab and seeing that nothing is requested from any other host.
If something here is wrong, I would rather know than be right. Email [email protected] with the page and the sentence. Reports that something did not work on a specific device are more useful to me than reports that it did, because those are what expose gaps in the guidance.