Skip to main content
Fix My Speaker

Trust

How we write and check our guides

Where the advice in our speaker guides comes from, how we check it, what happens when we get something wrong, and who pays for the site.

Reviewed · Fix My Speaker team

Two things are published here: explanations of our own cleaning tools, and practical guides for looking after a phone speaker. Below is the process behind each, and the quickest way to flag an error.

Claims about our tools

Because we built the cleaner and the speaker test, we can describe them precisely instead of guessing:

  • Figures come straight from the code. The 165 Hz tone, the sweep range, the run lengths and the test duration printed on our pages are pulled from the same settings file the audio engine reads. Change one and the text updates with it.
  • We never quote a fix rate. There is no reliable way for us to know how many speakers a tone has rescued, so you will not see "works 99% of the time" here.
  • Limitations get equal space. Every guide spells out that a tone clears the grille only, and cannot dry a device or mend a damaged driver.

Sourcing the guides

  • Device makers come first. Drying and cleaning steps follow published manufacturer advice, mostly Apple's support documents, and each guide links its references at the bottom.
  • Popular myths are called out. When common advice clashes with what a manufacturer says — the rice trick is the classic example — we explain the conflict rather than repeat the myth.
  • Dates are always visible. Each guide shows when it was first written and when it was last reviewed, so you can weigh how current it is.
  • Numbers need a home. A statistic appears only if it comes from our own tool or from a source we link.

Authorship

Guides carry the Fix My Speaker name rather than a personal byline, and the project as a whole stands behind them. A made-up expert persona would make the pages look grander but less honest, so we do not use one.

The guides section holds 2 guides at the moment. Every one shows its dates and references and links back here.

Fixing mistakes

Errors are easiest to fix when we know exactly where they are. Send the page address and the sentence in question to hello@fixmyspeaker.dev.

What happens next:

  • Wrong facts are corrected on the page and the "Reviewed" date moves forward to match.
  • Important changes get a visible note whenever the old text might have led a reader to do something harmful or pointless.
  • Minor refreshes stay quiet. If a phone maker renames a setting, we update the step and the date, nothing more.

How we are funded

You can confirm each of these by looking at the site:

  • No adverts. There are no ad slots and no ad scripts.
  • No commissions. Links to repair services or products, where they appear, earn us nothing.
  • No paid mentions. Nobody has bought a place on any page, and we do not offer that.
  • No premium version. All the tools are open to everyone at no cost.
  • No user data. We run no accounts and no analytics — the privacy policy lists the two settings stored on your device.

Should adverts, affiliate links or sponsorship ever arrive, we will announce it here and in the privacy policy first, and label it clearly wherever it shows up.

Boundaries

  • We do not speak for phone makers. Our pages are independent advice. If your manufacturer's instructions differ, theirs win.
  • We cannot assess your particular phone. After a submersion or a hard knock, a hands-on inspection by the maker or a repair shop is the right step.
See also
The about page explains what each tool does. The privacy policy lists what is stored, and the terms cover safe use.