iOS 6/6.0.1 Sound Issues?

By ZakO
in iPhone - iOS/tvOS/watchOS

 Share

Recommended Posts

Veteran

ZakO

Posted
Posted

Hi all,

Since upgrading to iOS 6.0 (and 6.0.1) both my iPhone 4S and my fiances iPhone 4 have had sound issues. Randomly sound will stop working.. it still rings and you can speak to a person both on and off loudspeaker, but all other sounds stop working. Clicking the volume up/down buttons does nothing either (no volume bar). I've tried restoring to factory defaults but it makes no difference.

I went to a local certified Apple repair store (not an official Apple store because there aren't any near here), they tried to tell me it was a hardware issue and the phone and/or dock needs replacing, but for it to happen on two different phones after iOS 5.1 worked fine for over a year makes be believe it's a iOS 6 software issue.

There's a thread about it on the Apple forum: https://discussions....tart=0&tstart=0 but no working fixes. Is anyone else experiencing this, is so have you found any workarounds?

Link to comment
https://www.neowin.net/forum/topic/1117721-ios-6601-sound-issues/
Share on other sites
Contributor

bugsbungee

Posted
Posted

Had a similar thing earlier today (4S), basically button clicks and text messages had no sound but calls worked ok. A hard reset fixed it for me (holding both buttons until the screen goes black, then letting go of the bottom one and then the top when the apple symbol appears).

Sounds like a software issue as you say if both phones of different models are affected at the same time.

Grand Master

RadishTM Veteran

Posted
  • Veteran
Posted

A work buddy of mine had the same fault on his 4S + not being able to hear a person they called, he was on 6.0 but updating to 6.0.1 fixed the issue.

As you have no Apple stores, I'd give AppleCare a call.

Apprentice

Gavotril

Posted
Posted

It is due some dirt on the headphones or dock ports. It happened to me once and I fixed it by sucking on the ports (DO NOT blow on them, never); if it is not fixed that way, clean them with cotton and alcohol, with the iPhone off.

This topic is now closed to further replies.
 Share
Go to topic listing

  • Posts

    • Microsoft finally admits its default Windows 11 25H2, 24H2 action broke key legacy component

      By hellowalkman · Posted

      Microsoft finally admits its default Windows 11 25H2, 24H2 action broke key legacy component by Sayan Sen Microsoft last week released Windows 11 KB5094126 and KB5093998 as the latest Patch Tuesday updates. Following that the company also published the accompanying dynamic updates under KB5094149, KB5095971, and KB5094156. So far the company has acknowledged two known issues that have popped up after the release which include bugged-out Office apps as well as the Recycle Bin; though there could be more at play too. Speaking of bugs and issues, Microsoft seems to have finally acknowledged a problem that probably has been around for close to a year. That's because back in July of 2025 the company made a default change to the latest Windows 11 versions, wherein it switched to JScript9Legacy on Windows 11 24H2 and later releases. Hence following the release of version 25H2 in October 2025, JScript9Legacy also remained default-enabled. As a result there has been a compatibility issue ever since then. For those wondering, by switching to JScript9Legacy Microsoft intended to improve the security of modern Windows PCs by reducing vulnerabilities tied to legacy scripting like cross-site scripting (XSS), among others. XSS exploits can allow cyber-attackers to attach malicious code onto legitimate websites and use them to execute the code when a potential victim loads such a website. Hence the new JScript9Legacy engine enforced stricter execution policies and improved object handling, which should help mitigate such attacks. Microsoft today has published a new support article detailing the problem. Neowin spotted it while browsing. The company says that JScript global definitions and execution context may fail to persist across scripts, potentially breaking older dependent apps and web-based components that relied on this legacy behavior. In the article Microsoft has confirmed that the issue stems from its move away from the older jscript9.dll engine in favor of jscript9legacy.dll. As mentioned above, while the newer engine was designed to address vulnerabilities and strengthen security it also changes how JScript handles execution context. As a result functions and definitions loaded by one script could no longer remain available to subsequent scripts once execution ended. The company notes that some applications worked correctly on earlier Windows versions because the older JScript engine automatically retained global definitions and execution state between scripts. Under the newer model though that behavior is disabled by default causing certain legacy workloads and polyfill-dependent scripts to fail. Microsoft says it addressed the problem via the KB5077241 update though the fix had not been enabled automatically in the following updates. As such admins must explicitly turn on persistent JScript execution context using a Registry setting that the tech giant shared today. The configuration can be applied to individual processes or system-wide through the FEATURE_ENABLE_PERSISTENCE registry key. The steps have been outlined below: Run the following command to create the feature control registry key: reg add "HKLM\Software\Policies\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_ENABLE_PERSISTENCE" Under this key, create a new DWORD (32-bit) value. Configure the value as follows: To enable persistence for specific processes only: Set the value to 1 for each target process name. To enable persistence for all processes: Add * as the key name and set its value to 1. You can find the official support article here on Microsoft's website.
    • The quantum search for Time's origin had an equally mind-boggling conclusion

      By cleverclogs · Posted

      The possibility that milk gathers back into a glass implies that gravity can be 'reversed'.
    • VidCoder 12.20

      By Copernic · Posted

      VidCoder 12.20 by Razvan Serea  VidCoder is a DVD/Blu-ray ripping and video transcoding application for Windows. It uses HandBrake as its encoding engine. Calling directly into the HandBrake library gives it a more rich UI than the official HandBrake Windows GUI. VidCoder can rip DVDs but does not defeat the CSS encryption found in most commercial DVDs. You’ll need the NET 8 Desktop Runtime. If you don’t have it, VidCoder will prompt you to download and install it. The Portable version is self-contained and does not require any .NET Runtime to be installed. You do not need to install HandBrake for VidCoder to work. Feature list: Multi-threaded MP4, MKV containers Completely integrated encoding pipeline: everything is in one process and no huge intermediate temporary files H.264, H.265, MPEG-4, MPEG-2, VP8, Theora video Hardware-accelerated encoding with AMD VCE, Nvidia NVENC and Intel QuickSync AAC, MP3, Vorbis, AC3, FLAC audio encoding and AAC/AC3/MP3/DTS/DTS-HD passthrough Target bitrate, size or quality for video 2-pass encoding Decomb, detelecine, deinterlace, rotate, reflect, chroma smooth, colorspace filters Powerful batch encoding with simultaneous encodes Customizable Pickers to automatically pick audio and subtitle tracks, destination, titles and more Instant source previews Creates small encoded preview clips Pause, resume encoding VidCoder 12.20 changes: Updated HandBrake core to 1.11.2. Download: VidCoder 12.20 | 47.0 MB (Open Source) Download: Portable VidCoder 12.19 | 89.3 MB Link: VidCoder Home Page | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • This is how much iPhone 18 Pro could cost after Apple's price hike confirmed

      By +Nik Louch · Posted

      They will
    • Politically funny images of the World

      By +Nik Louch · Posted

      Too soon, I'm still not over this death!

  • Recent Achievements

    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done

  • Popular Contributors

    1. 1
      +primortal
      593
    2. 2
      +Edouard
      185
    3. 3
      PsYcHoKiLLa
      77
    4. 4
      Michael Scrip
      73
    5. 5
      Steven P.
      66
    Show More

  • Tell a friend

    Love Neowin? Tell a friend!