Product Issues & Limitations

​
SoundPath Lab records real-world problems, limitations and compatibility risks that may matter before a customer buys. Open and unresolved records come first. Resolved records remain in a separate history and are not presented as current warnings.
​
Last editorial check: 20 September 2026 (Hong Kong time; added SPL-CAM-FH-001 and updated SPL-MIC-UAC1-001 with Microsoft's partial mitigation. Other records retain their individual evidence-review dates.)
​

Our duty is to readers. A buyer report is useful evidence, but one report is not automatically a model-wide defect. We label uncertainty, cite sources, invite manufacturer evidence and correct the record when better evidence becomes available.
​

Open and unresolved issue registry

​
These are current limitations or risks that can still affect a buying decision. “Open” does not always mean defective: some records are permanent design or compatibility limitations.
​

Active investigation queue

​
Leads may come from owners, buyer reviews, independent tests, retailer reviews, support forums, complaint records, Reddit, Head-Fi, ASR, AVS Forum, YouTube and other public sources. Each lead preserves its source, date, exact wording where permitted, product version and system conditions.
​

• E0 — single report: recorded as a lead; never generalized to the whole model.
• E1 — repeated reports: two or more apparently independent reports with matching symptoms.
• E2 — reproduced: demonstrated by SoundPath Lab or a credible independent reviewer under documented conditions.
• E3 — manufacturer acknowledged: confirmed in an official statement, manual, support record or release note.
• E4 — resolution verified: a published fix has been checked under the relevant conditions where practical.
  ​
  A queue item can be promoted, narrowed, merged, marked not reproducible or retracted. We do not hide an unresolved record merely because it is inconvenient to a manufacturer.
  ​

Brand coverage registry

​
The registry is being expanded from a small launch set into a global system. A brand appearing below means it is in the coverage queue; it does not mean that a defect has been found.
​
Priority network audio and digital sources: WiiM, Arylic, iEAST, AudioCast, EMiUZEK, Eversolo, Zidoo, FiiO, Shanling, HiBy, iBasso, Matrix Audio, Auralic, Aurender, Bluesound, NAD, Naim, Cambridge Audio, Cocktail Audio, HiFi Rose, Silent Angel, Volumio and Aiffro.
​
Priority DAC, amplifier and desktop audio: Topping, SMSL, Fosi Audio, Aiyima, Douk Audio, Nobsound, Loxjie, Sabaj, Aune, xDuoo, Gustard, Denafrips, Holo Audio, Questyle, iFi Audio, RME, Schiit Audio, Burson Audio, JDS Labs, E1DA, EarMen, Hidizs and TempoTec.
​
Priority speakers, headphones and system brands: 3M PELTOR, Teufel, Sonos, KEF, Bowers & Wilkins, Bang & Olufsen, JBL, Bose, Sony, Sennheiser, Audio-Technica, Beyerdynamic, Focal, HiFiMAN, Meze Audio, Moondrop, DALI, ELAC, Dynaudio, Genelec, Klipsch, Q Acoustics, Wharfedale, Monitor Audio, Edifier, Airpulse, SVS, Denon, Marantz, Yamaha, Onkyo and Technics.
​
Priority analogue, accessories and components: Pro-Ject, Rega, Thorens, Dual, Audio-Technica, Ortofon, Clearaudio, VPI, Cardas Audio, AudioQuest, QED, Nordost, Wireworld, Purifi, AKM, ESS Technology, ROHM, XMOS and Analog Devices.
​
Brand names, aliases and ownership changes are normalized before individual brand pages are created. Platforms, protocols, product families and component suppliers are identified separately so they are not mistaken for finished-product brands.
​

Equal-treatment rule for all brands

​
All brands receive the same evidence and status treatment. A brand’s presence in a seller list, marketplace, review-sample programme or product catalogue does not grant an exemption. Relevant problems are recorded using the same evidence and status rules, and any material relationship affecting reader judgment is disclosed on the relevant article.
​
If we receive a technical explanation or solution from a manufacturer or seller, it is added as a response. It does not replace the original record unless the evidence shows the record was wrong or the affected condition has been resolved.
​

Confirmed behaviour that is not a defect

​

Resolved issue history

​
Resolved records are history, not current warnings, unless the symptom reappears on a later version.
​

Status system

​

• Reported — unverified: useful lead, not independently supported.
• Under investigation: repeated credible reports exist, but scope or cause is uncertain.
• Open — confirmed: strong evidence supports a current problem or limitation.
• Workaround available: unresolved, but a documented mitigation exists.
• Manufacturer response received: the brand has replied; its evidence is shown separately from our finding.
• Resolved — pending verification: a fix is published but not adequately checked.
• Resolved — verified: the fix has been checked under the relevant conditions.
• Not reproducible: available evidence is insufficient after documented testing.
• Retracted: the original record was materially wrong; the correction and reason remain visible.
  ​

Required record fields

​
Every issue record should include:
​

1. Issue ID, brand, exact model and hardware revision when known.
2. Issue title, category, severity and affected scope.
3. Firmware, app and operating-system versions.
4. Region, service, network type, input/output path and connected equipment.
5. First-observed date, SoundPath Lab added date and last-checked date.
6. Expected behaviour, actual behaviour and reproduction steps.
7. Practical buyer impact and any workaround.
8. Evidence level, citations and archived supporting material where permitted.
9. Manufacturer contact date, response date and evidence supplied.
10. Resolution version, resolution date, verification result and change log.
    ​
    When an older source lacks a reliable date, we write Unknown rather than inventing one.
    ​

Record lifecycle and change log

​
Every public record follows the same lifecycle:
​
Lead received → evidence preserved → conditions normalized → editorial review → public issue ID → periodic recheck → manufacturer response → resolution claim → verification → history
​
Material edits record what changed, when it changed and why. A brand may submit evidence, but a request alone does not remove a record. Retractions remain visible with the reason under our Corrections Policy.
​

Verification update — 7 September 2026

SPL-CAM-YOYOM-001: U.S. CPSC recall 26-731 covers approximately 714 boxed pairs, records four reports involving fire, smoke or ejected battery material, reports no injuries as of the announcement, and specifies a $218 U.S. refund. Worldwide quantity remains Unknown; status remains open-confirmed.

SPL-NAI-DSP-002: Evidence remains E1 — repeated owner reports with mixed counter-evidence; not independently reproduced. Status remains Under investigation · Workaround available. Next review: 2 October 2026.

Resolved record added — 4 September 2026

Revision: 4 Sep 2026 — Added SPL-ROON-RB-001 as resolved-verified after the RoPieee 2026.08.3 maintainer release and multiple independent recovery confirmations.

SPL-ATH-TWS-002 — Audio-Technica ATH-CKS50TW2 Bluetooth security vulnerability

Status: resolved-pending-verification

Affected scope: ATH-CKS50TW2BK and ATH-CKS50TW2GR, batches before 2526, under the UK OPSS report. Scope outside that report is Unknown.

Risk and trigger: an unpatched device may allow a person in close proximity to take control through the documented Bluetooth SoC vulnerability.

Official remedy: install Audio-Technica firmware Rev1009 or later through the Audio-Technica | Connect app.

Evidence: E3 — UK OPSS plus Audio-Technica's official updater. Customer incident count and total affected population were not disclosed; no independent post-update technical retest was located.

Details: https://www.soundpathlab.com/audio-technica-ath-cks50tw2-bluetooth-security-fix/

Official sources: https://www.gov.uk/product-safety-alerts-reports-recalls/product-safety-report-audio-technica-wireless-headphones-ath-cks50tw2-2507-0028 | https://www.audio-technica.co.jp/support/atj/update/update_ATH-CKS50TW2.html

Last checked: 11 Aug 2026. Lifecycle: Active product / security modification programme.

Revision: 11 Aug 2026 — Added SPL-ATH-TWS-002; status remains resolved-pending-verification until independent retesting confirms the patch.

Open issue added — 4 September 2026

SPL-NAI-DSP-002 — Naim New Classic firmware 5.4 display-off setting may reset after power cycle

Status: Under investigation · Workaround available

Affected scope: Owner reports name NSC 222 and NSS 333 on New Classic firmware 5.4. The complete model, app-version and regional scope remain Unknown.

Buyer impact: After a full power cycle, “Turn Off Display During Playback” may remain shown as enabled in the app while the front display stays illuminated during playback.

Workaround: Switch the display preference off, leave the settings screen, return and enable it again. This restores the intended behaviour temporarily in the reports reviewed.

Evidence: E1 — repeated reports in Naim’s official community, mixed counter-evidence, not independently reproduced by SoundPath Lab.

First observed: 5 August 2026. Added: 4 September 2026. Last checked: 4 September 2026.

Manufacturer response: No formal Naim acknowledgement, support bulletin or confirmed fix located.

Details: Naim New Classic Firmware 5.4: Display-Off Setting May Reset After Power Cycle

Official community source: Firmware v5.4 for NC is now available

Revision: 4 Sep 2026 — Added SPL-NAI-DSP-002 as Under investigation / Workaround available and aligned its evidence label with the site-wide E1 definition. The record is not a claim of a universal New Classic defect.