Universal diagnostic library
Consumer-product troubleshooting by exact model, symptom and code
Error codes, symptoms, indicators and components converge on the same safe diagnostic path.
Browse by platform
13,225 complete records in this directory2.4 GHz Wi-Fi behaves incorrectly or produces the wrong result
A wrong result requires checking inputs, mode, calibration and output separately; a working control path can still be configured for the wrong state. This record isolates 2.4 GHz Wi-Fi through radio coverage versus channel congestion, security compatibility and interference.
Open record Home networking · 2.4 GHz2.4 GHz Wi-Fi fails only on one device, band, room or service
When a network feature works elsewhere, isolate the client, radio band, location or service path before touching router-wide settings. This record isolates 2.4 GHz Wi-Fi through radio coverage versus channel congestion, security compatibility and interference.
Open record Home networking · 2.4 GHz2.4 GHz Wi-Fi is not working
A complete failure should be separated into power or eligibility, the external path, and the component itself before any reset. This record isolates 2.4 GHz Wi-Fi through radio coverage versus channel congestion, security compatibility and interference.
Open record Home networking · 2.4 GHz2.4 GHz Wi-Fi is unusually slow or delayed
A delay can come from capacity, weak signal, background work, protection or a service wait; measuring the exact stage prevents the wrong repair. This record isolates 2.4 GHz Wi-Fi through radio coverage versus channel congestion, security compatibility and interference.
Open record Home networking · 2.4 GHz2.4 GHz Wi-Fi keeps disconnecting or working intermittently
Intermittent behavior is diagnosed by the trigger—movement, heat, load, sleep, distance or time—not by repeating broad resets. This record isolates 2.4 GHz Wi-Fi through radio coverage versus channel congestion, security compatibility and interference.
Open record Home networking · 2.4 GHz2.4 GHz Wi-Fi stopped working after an update, outage or hardware change
A failure immediately after a known change should be checked for new defaults, stale pairing, power sequencing or compatibility before factory recovery. This record isolates 2.4 GHz Wi-Fi through radio coverage versus channel congestion, security compatibility and interference.
Open record Home networking · 5 GHz5 GHz Wi-Fi behaves incorrectly or produces the wrong result
A wrong result requires checking inputs, mode, calibration and output separately; a working control path can still be configured for the wrong state. This record isolates 5 GHz Wi-Fi through range/walls versus DFS channel support, width and client capability.
Open record Home networking · 5 GHz5 GHz Wi-Fi fails only on one device, band, room or service
When a network feature works elsewhere, isolate the client, radio band, location or service path before touching router-wide settings. This record isolates 5 GHz Wi-Fi through range/walls versus DFS channel support, width and client capability.
Open record Home networking · 5 GHz5 GHz Wi-Fi is not working
A complete failure should be separated into power or eligibility, the external path, and the component itself before any reset. This record isolates 5 GHz Wi-Fi through range/walls versus DFS channel support, width and client capability.
Open record Home networking · 5 GHz5 GHz Wi-Fi is unusually slow or delayed
A delay can come from capacity, weak signal, background work, protection or a service wait; measuring the exact stage prevents the wrong repair. This record isolates 5 GHz Wi-Fi through range/walls versus DFS channel support, width and client capability.
Open record Home networking · 5 GHz5 GHz Wi-Fi keeps disconnecting or working intermittently
Intermittent behavior is diagnosed by the trigger—movement, heat, load, sleep, distance or time—not by repeating broad resets. This record isolates 5 GHz Wi-Fi through range/walls versus DFS channel support, width and client capability.
Open record Home networking · 5 GHz5 GHz Wi-Fi stopped working after an update, outage or hardware change
A failure immediately after a known change should be checked for new defaults, stale pairing, power sequencing or compatibility before factory recovery. This record isolates 5 GHz Wi-Fi through range/walls versus DFS channel support, width and client capability.
Open record Home networking · 6 GHz6 GHz Wi-Fi behaves incorrectly or produces the wrong result
A wrong result requires checking inputs, mode, calibration and output separately; a working control path can still be configured for the wrong state. This record isolates 6 GHz Wi-Fi through client/radio eligibility versus WPA3, band visibility and range.
Open record Home networking · 6 GHz6 GHz Wi-Fi fails only on one device, band, room or service
When a network feature works elsewhere, isolate the client, radio band, location or service path before touching router-wide settings. This record isolates 6 GHz Wi-Fi through client/radio eligibility versus WPA3, band visibility and range.
Open record Home networking · 6 GHz6 GHz Wi-Fi is not working
A complete failure should be separated into power or eligibility, the external path, and the component itself before any reset. This record isolates 6 GHz Wi-Fi through client/radio eligibility versus WPA3, band visibility and range.
Open record Home networking · 6 GHz6 GHz Wi-Fi is unusually slow or delayed
A delay can come from capacity, weak signal, background work, protection or a service wait; measuring the exact stage prevents the wrong repair. This record isolates 6 GHz Wi-Fi through client/radio eligibility versus WPA3, band visibility and range.
Open record Home networking · 6 GHz6 GHz Wi-Fi keeps disconnecting or working intermittently
Intermittent behavior is diagnosed by the trigger—movement, heat, load, sleep, distance or time—not by repeating broad resets. This record isolates 6 GHz Wi-Fi through client/radio eligibility versus WPA3, band visibility and range.
Open record Home networking · 6 GHz6 GHz Wi-Fi stopped working after an update, outage or hardware change
A failure immediately after a known change should be checked for new defaults, stale pairing, power sequencing or compatibility before factory recovery. This record isolates 6 GHz Wi-Fi through client/radio eligibility versus WPA3, band visibility and range.
Open record Roku · Streaming appA Roku app will not open, loads black or keeps crashing
Check whether other apps work, update Roku software, restart the device, then remove and reinstall only the affected app. Reinstalling may require that service’s sign-in credentials.
Open record Headphones · ANCActive noise cancellation behaves incorrectly or produces the wrong result
A wrong result requires checking inputs, mode, calibration and output separately; a working control path can still be configured for the wrong state. This record isolates active noise cancellation through ear-tip seal and mode versus wind, microphone obstruction and hardware.
Open record Headphones · ANCActive noise cancellation fails with one app, game, host or connection
When audio, console or wearable behavior changes with one app, game, host or connection, the working context proves the entire device has not failed. This record isolates active noise cancellation through ear-tip seal and mode versus wind, microphone obstruction and hardware.
Open record Headphones · ANCActive noise cancellation is not working
A complete failure should be separated into power or eligibility, the external path, and the component itself before any reset. This record isolates active noise cancellation through ear-tip seal and mode versus wind, microphone obstruction and hardware.
Open record Headphones · ANCActive noise cancellation is unusually slow or delayed
A delay can come from capacity, weak signal, background work, protection or a service wait; measuring the exact stage prevents the wrong repair. This record isolates active noise cancellation through ear-tip seal and mode versus wind, microphone obstruction and hardware.
Open record Headphones · ANCActive noise cancellation keeps disconnecting or working intermittently
Intermittent behavior is diagnosed by the trigger—movement, heat, load, sleep, distance or time—not by repeating broad resets. This record isolates active noise cancellation through ear-tip seal and mode versus wind, microphone obstruction and hardware.
Open record Headphones · ANCActive noise cancellation stopped working after an update, outage or hardware change
A failure immediately after a known change should be checked for new defaults, stale pairing, power sequencing or compatibility before factory recovery. This record isolates active noise cancellation through ear-tip seal and mode versus wind, microphone obstruction and hardware.
Open record Component diagnostic recordAir-conditioner contactor: function, symptoms, testing boundary and repair difficulty
Air-conditioner contactor switches high-voltage power to compressor and fan. Related symptoms include outdoor unit silent, buzzing, chattering or running while off. Those symptoms do not prove the component failed: confirm thermostat demand and external disconnect/breaker state.
Open record iPhone · AirDropAirDrop cannot find the other device
Turn on Wi-Fi and Bluetooth on both Apple devices, move them nearby, set the receiver to Contacts Only or Everyone for 10 Minutes, and restart both devices. Personal Hotspot can interfere with the local discovery path.
Open record Mac · AirDropAirDrop is not working between a Mac and iPhone
Enable Wi-Fi and Bluetooth on both devices, put them nearby, open AirDrop on the Mac and make the receiver discoverable, then restart both devices. Confirm Contacts Only has matching Apple Account contact details.
Open record Samsung TV · AirPlayAirPlay is not working on a Samsung TV
Confirm the TV model supports AirPlay, put the Apple device and TV on the same Wi-Fi, enable Apple AirPlay Settings on the TV, then update and restart both devices. Reset paired AirPlay devices only after basic discovery checks fail.
Open record AirPods · charging caseAirPods case will not charge
A case can fail to charge because of cable/adapter, port debris, wireless alignment, temperature or battery damage. Test wired charging from known power before resetting AirPods.
Open record Printers · mobile printingAirPrint or Mopria discovery behaves incorrectly or produces the wrong result
A wrong result requires checking inputs, mode, calibration and output separately; a working control path can still be configured for the wrong state. This record isolates AirPrint or Mopria discovery through printer service versus guest isolation, VPN, multicast and stale IP.
Open record Printers · mobile printingAirPrint or Mopria discovery fails for one device, job or paper type
A printer problem limited to one sender, document, tray or media type should be repaired at that boundary, not with a factory reset. This record isolates AirPrint or Mopria discovery through printer service versus guest isolation, VPN, multicast and stale IP.
Open record Printers · mobile printingAirPrint or Mopria discovery is not working
A complete failure should be separated into power or eligibility, the external path, and the component itself before any reset. This record isolates AirPrint or Mopria discovery through printer service versus guest isolation, VPN, multicast and stale IP.
Open record Printers · mobile printingAirPrint or Mopria discovery is unusually slow or delayed
A delay can come from capacity, weak signal, background work, protection or a service wait; measuring the exact stage prevents the wrong repair. This record isolates AirPrint or Mopria discovery through printer service versus guest isolation, VPN, multicast and stale IP.
Open record Printers · mobile printingAirPrint or Mopria discovery keeps disconnecting or working intermittently
Intermittent behavior is diagnosed by the trigger—movement, heat, load, sleep, distance or time—not by repeating broad resets. This record isolates AirPrint or Mopria discovery through printer service versus guest isolation, VPN, multicast and stale IP.
Open record Printers · mobile printingAirPrint or Mopria discovery stopped working after an update, outage or hardware change
A failure immediately after a known change should be checked for new defaults, stale pairing, power sequencing or compatibility before factory recovery. This record isolates AirPrint or Mopria discovery through printer service versus guest isolation, VPN, multicast and stale IP.
Open record Smart home · routinesAlexa routine runs only sometimes
Intermittent routines usually fail at the trigger, one action, device reachability or timing condition. The activity history shows where the chain stopped.
Open record Android · AppsAn Android app keeps crashing or will not open
Force stop the app, restart the device, update the app and Android, then clear the app cache. Clear storage or uninstall only with credentials and synced data available because either can remove local app state.
Open record Apple TV · AppsAn Apple TV app is frozen or will not open
Force-quit only the affected app, reopen it, restart Apple TV, then update the app and tvOS. Delete or reset the app last because local app data and sign-in state may be removed.
Open record iPhone · AppsAn iPhone app keeps closing, freezing or will not open
Close and reopen the app, restart iPhone, update the app and iOS, then delete and redownload the app last. Deletion can remove data stored only inside that app.
Open record Chromebook · Android appsAndroid apps on Chromebook behaves incorrectly or produces the wrong result
A wrong result requires checking inputs, mode, calibration and output separately; a working control path can still be configured for the wrong state. This record isolates Android apps on Chromebook through app compatibility versus Play Store availability, storage and managed restrictions.
Open record Chromebook · Android appsAndroid apps on Chromebook is not working
A complete failure should be separated into power or eligibility, the external path, and the component itself before any reset. This record isolates Android apps on Chromebook through app compatibility versus Play Store availability, storage and managed restrictions.
Open record Chromebook · Android appsAndroid apps on Chromebook is unusually slow or delayed
A delay can come from capacity, weak signal, background work, protection or a service wait; measuring the exact stage prevents the wrong repair. This record isolates Android apps on Chromebook through app compatibility versus Play Store availability, storage and managed restrictions.
Open record Chromebook · Android appsAndroid apps on Chromebook keeps disconnecting or working intermittently
Intermittent behavior is diagnosed by the trigger—movement, heat, load, sleep, distance or time—not by repeating broad resets. This record isolates Android apps on Chromebook through app compatibility versus Play Store availability, storage and managed restrictions.
Open record Chromebook · Android appsAndroid apps on Chromebook stopped working after an update, outage or hardware change
A failure immediately after a known change should be checked for new defaults, stale pairing, power sequencing or compatibility before factory recovery. This record isolates Android apps on Chromebook through app compatibility versus Play Store availability, storage and managed restrictions.
Open record Chromebook · Android appsAndroid apps on Chromebook works in one app, account or port but not another
When a computer function works in another app, user account or port, keep the repair inside the failing context. This record isolates Android apps on Chromebook through app compatibility versus Play Store availability, storage and managed restrictions.
Open record Android · defaultsAndroid default-app routing behaves incorrectly or produces the wrong result
A wrong result requires checking inputs, mode, calibration and output separately; a working control path can still be configured for the wrong state. This record isolates Android default-app routing through system default versus in-app browser and domain-specific verified links.
Open record Android · defaultsAndroid default-app routing is not working
A complete failure should be separated into power or eligibility, the external path, and the component itself before any reset. This record isolates Android default-app routing through system default versus in-app browser and domain-specific verified links.
Open record Android · defaultsAndroid default-app routing is unusually slow or delayed
A delay can come from capacity, weak signal, background work, protection or a service wait; measuring the exact stage prevents the wrong repair. This record isolates Android default-app routing through system default versus in-app browser and domain-specific verified links.
Open record Android · defaultsAndroid default-app routing keeps disconnecting or working intermittently
Intermittent behavior is diagnosed by the trigger—movement, heat, load, sleep, distance or time—not by repeating broad resets. This record isolates Android default-app routing through system default versus in-app browser and domain-specific verified links.
Open record Android · defaultsAndroid default-app routing stopped working after an update, outage or hardware change
A failure immediately after a known change should be checked for new defaults, stale pairing, power sequencing or compatibility before factory recovery. This record isolates Android default-app routing through system default versus in-app browser and domain-specific verified links.
Open record Android · defaultsAndroid default-app routing works only on one app, network, account or location
When a phone or tablet function changes with the app, network, account or location, that context is the first repair boundary. This record isolates Android default-app routing through system default versus in-app browser and domain-specific verified links.
Open record Android · Wi-FiAndroid is connected to Wi-Fi but has no internet
Compare Wi-Fi with mobile data, test another device on the same network, restart the phone and router, then forget and reconnect to the network. Reset Wi-Fi, mobile and Bluetooth settings only after noting that it removes saved connections.
Open record Android · keyboardAndroid keyboard disappeared or will not open
If no keyboard appears in any app, the input method may be disabled, crashed or not selected. If one app is affected, treat it as that app’s layout problem.
Open record Android · hotspotAndroid mobile hotspot behaves incorrectly or produces the wrong result
A wrong result requires checking inputs, mode, calibration and output separately; a working control path can still be configured for the wrong state. This record isolates Android mobile hotspot through carrier/tethering plan versus cellular data, VPN, band and client compatibility.
Open record Android · hotspotAndroid mobile hotspot is not working
A complete failure should be separated into power or eligibility, the external path, and the component itself before any reset. This record isolates Android mobile hotspot through carrier/tethering plan versus cellular data, VPN, band and client compatibility.
Open record Android · hotspotAndroid mobile hotspot is unusually slow or delayed
A delay can come from capacity, weak signal, background work, protection or a service wait; measuring the exact stage prevents the wrong repair. This record isolates Android mobile hotspot through carrier/tethering plan versus cellular data, VPN, band and client compatibility.
Open record Android · hotspotAndroid mobile hotspot keeps disconnecting or working intermittently
Intermittent behavior is diagnosed by the trigger—movement, heat, load, sleep, distance or time—not by repeating broad resets. This record isolates Android mobile hotspot through carrier/tethering plan versus cellular data, VPN, band and client compatibility.
Open record Android · hotspotAndroid mobile hotspot stopped working after an update, outage or hardware change
A failure immediately after a known change should be checked for new defaults, stale pairing, power sequencing or compatibility before factory recovery. This record isolates Android mobile hotspot through carrier/tethering plan versus cellular data, VPN, band and client compatibility.
Open record Android · hotspotAndroid mobile hotspot works only on one app, network, account or location
When a phone or tablet function changes with the app, network, account or location, that context is the first repair boundary. This record isolates Android mobile hotspot through carrier/tethering plan versus cellular data, VPN, band and client compatibility.
Open recordStructured depth, not empty permutations
Every published record carries a direct answer, scope, ordered fixes, risk notes and sources.
Device and manufacturer hubs share a consistent record system, but each answer carries the relevant controls, fault boundaries, consequences and official support entry point for that platform.
See the publication gate