iPhone 18 Pro Owners Report a Crackling Speaker, and iOS 27.0.1 Did Not Fix It

Owners of Apple's newest flagship phones say the device makes a crackling sound from its speaker, and the software update Apple shipped this week did not stop it. The reports, covered by MacRumors on September 29, 2026, describe a fault that shows up on both iPhone 18 Pro sizes during ordinary use, including while running an app or scrolling a website.

Related reading: Apple Puts Touch on the Mac at $2,899, Reversing a Long Resistance · Apple's New iPad Mini Starts at $699, $200 Above the Model It Replaces.

To be clear, this is a user-reported issue. Apple had not publicly acknowledged it or commented on it as of the reporting, and no teardown or service bulletin has established a cause. The complaints surfaced on the MacRumors forums and Reddit before the outlets picked them up, which is the usual path for launch-week faults: owners find each other first, and coverage follows. What follows is what owners say they hear, what Apple has and has not done, and what usually determines whether a launch-week defect becomes a footnote or a repair program.

What owners say they hear and when

The sound is described in several ways: a crackle, a faint tick or pop, or random clicking. It comes mostly from the earpiece speaker, the driver at the top of the phone that handles calls and some media playback. Android Headlines collected the same range of descriptions from owners, and MacObserver reported similar accounts.

The reported triggers are broad. Owners say the noise appears during app use, while scrolling websites, when a notification arrives, when the keyboard pops up, and during calls on a cellular connection. Toggling Airplane Mode on and off reportedly triggers it, and so does quickly adjusting screen brightness. Mashable Middle East summarised the same complaints on September 30.

That list matters for diagnosis. A single bad speaker usually fails in a narrow band of conditions, such as loud playback. These reports cluster around events that wake or reconfigure the audio path: a call connecting, a notification firing, a keyboard opening, a radio state change. Those are moments when software hands work to the speaker, which is why some owners suspect the problem sits in audio processing rather than in a dead driver.

The earpiece detail narrows the story further. The top speaker is the one people hold to their ear during a call, so a crackle there is harder to ignore than one from the bottom-firing media speaker, and it lands in the one use case where the phone is held still and close. Both Pro sizes appear in the reports, which points away from a single assembly line and toward something shared across the line, whether a component batch or a piece of firmware.

What Apple has and has not done

Apple released iOS 27.0.1 on September 28, 2026. Its stated purpose was to fix a bug that could cause iPhone 18 Pro models to restart when Face ID authentication fails. The release notes did not mention a speaker fix, and Macworld reported on September 30 that early feedback from users said the update did not help. Owners in the MacRumors thread reached the same conclusion.

So there are two distinct bugs here, and only one has an official fix. The restart-when-Face-ID-fails flaw was acknowledged and patched. The speaker noise has not been acknowledged at all. For a phone that has been on sale for roughly twelve days, per Macworld's September 30 report, the absence of a statement is itself the story for owners trying to decide whether to keep the phone, return it, or wait.

The timing is awkward. The patch arrived one day before MacRumors published the speaker reports, so owners who installed it were already looking for a fix when the coverage landed. Apple's release notes are the only official description of what 27.0.1 changes, and they are specific about the Face ID restart and silent on audio. That silence is not evidence of anything by itself; a company does not list every change, and an intermittent fault may not have been reproduced in time to make the build. It does mean owners have no official timeline to plan around.

Replacements that arrived with the same flaw

A detail from the MacRumors forum thread sharpens the concern. Some owners who returned their phones for a replacement said the second unit made the same sound. If accurate, that narrows the possibilities. A one-off manufacturing slip would not travel with a new unit. Either a run of devices shares a hardware fault, or the source is something a swap cannot remove, such as firmware or a calibration step applied to every unit.

Neither conclusion is established. Replacement anecdotes are among the least reliable forms of evidence, because people who receive a working replacement rarely post about it. Still, the pattern is the kind that turns a quiet forum thread into a support queue, and it is why the next few weeks of owner data will matter more than the first few days.

Replacement data is also the hardest thing for a company to argue with. If a meaningful share of swapped units repeat the fault, the fix cannot be a swap, and the options narrow to a firmware patch or a component change on the line. That is the scenario that produces a repair program, and it is what Apple would want to rule out before saying anything.

Why a flagship launch defect matters

The iPhone Pro line is Apple's highest-margin, highest-volume flagship, and it sells to the customers most likely to notice and least likely to tolerate a flaw. A speaker problem is small in the abstract and disproportionate in practice. It affects calls, the function phones are still bought for. It is intermittent, which makes it hard to demonstrate at a service desk. And it appears on a phone whose September 18 launch already carried a price increase, which raises the emotional cost of being told to wait for a fix.

The support mechanics are mundane but expensive. A confirmed fault triggers returns inside the retailer's window, Genius Bar visits, mail-in repairs, and sometimes a replacement program. Intermittent faults are the worst case for all of those, because each owner has to reproduce the problem in front of someone else. The same dynamic explains why companies often wait for a clear reproduction and a fix in hand before saying anything publicly: an early statement can lock in a response before the cause is known.

There is also a pattern to consider. Recent iPhone cycles have opened with a run of small software regressions that are patched over the following weeks, and the Face ID restart bug fixed in iOS 27.0.1 fits that mold. The MacRumors coverage notes that the thread had drawn hundreds of comments, and that some commenters said their units are unaffected and that this launch has otherwise been smoother than past cycles. The issue is not universal, and treating it as a fleet-wide failure would overstate what the sources support.

None of this is unique to Apple, and that is the point. Every large hardware launch concentrates a year of engineering into a few weeks of public use, and the first weeks are when the widest range of devices, carriers, apps and habits meet the software. Most such reports resolve quietly after an update. A smaller number turn out to be a manufacturing defect that requires a public program. The difference is rarely visible from the outside until the company either ships a fix or starts replacing parts.

Hardware, firmware, or something else?

The honest answer is that no one outside Apple knows. The triggers point in two directions at once. Radio and brightness changes are software events, which supports a firmware or audio-processing explanation. A failing driver or a loose connection can also produce crackles under load, which supports a hardware explanation. The two are not mutually exclusive: a marginal component can be pushed over the edge by how software drives it.

The practical distinction is what happens next. If the cause is software, a point update can fix it, and owners keep their phones. If the cause is hardware, the fix is a repair or a replacement, and the evidence that replacements carry the same flaw becomes the central question. Nothing Apple has released so far settles which world this is. Both the restart bug and the speaker reports arrived on the same hardware, in the same two weeks, which is when a new device meets the widest range of conditions in public for the first time.

Caveats

Three things limit what these reports can establish. The accounts are self-selected, so owners with a faulty phone post and owners with a working one mostly do not. The number of affected units is unknown; the MacRumors thread's hundreds of comments include people saying their phones are fine. And the cause, hardware or firmware, is unproven, which makes any prediction about a fix a guess about which one it is. Apple has not disputed the reports, but it has not confirmed them either.

What to watch

The next two weeks should separate the possibilities. An update that lists an audio fix would end the speculation. A repair program, or a service document that names a serial-number range, would confirm a hardware cause. Continued silence with a growing thread would suggest Apple is still trying to reproduce the fault internally, which for an intermittent problem can take longer than owners would like.

• An official acknowledgement. A support document or a statement from Apple would turn a forum thread into a defined problem with a stated scope.
• The next point update. A later iOS 27 update, if it lists an audio fix, would confirm a software cause and give owners a date to aim for.
• Hardware evidence. A teardown, a service bulletin, or a repair program would point to a component fault and define who is covered.
• Replacement outcomes. More reports of second units with the same sound would strengthen the case that swapping hardware does not solve it.
• Return and repair data. Retailer return rates and Apple's own service numbers, if either ever surfaces, would show whether the thread reflects hundreds of phones or far more.

For now, the responsible reading is narrow. Some owners of the iPhone 18 Pro and Pro Max hear a crackling speaker under everyday conditions. Apple has fixed a different bug and said nothing about this one. Whether that silence lasts long depends on what the next update and the next wave of owner reports show.

Cover: An iPhone 18 Pro Max and an iPhone 18 Pro on display. Photo by Kyu3a via Wikimedia Commons, CC BY-SA 4.0.