Support directory
Android issues, with manufacturer variation called out.
Begin with the exact device, symptom and connection. These records separate service outages, home-network failures, device software and app sessions before any destructive step.
An 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 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 record Android · notificationsAndroid notification channels 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 notification channels through app-wide permission versus one disabled channel, Focus and battery restriction.
Open record Android · notificationsAndroid notification channels 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 notification channels through app-wide permission versus one disabled channel, Focus and battery restriction.
Open record Android · notificationsAndroid notification channels 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 notification channels through app-wide permission versus one disabled channel, Focus and battery restriction.
Open record Android · notificationsAndroid notification channels 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 notification channels through app-wide permission versus one disabled channel, Focus and battery restriction.
Open record Android · notificationsAndroid notification channels 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 notification channels through app-wide permission versus one disabled channel, Focus and battery restriction.
Open record Android · notificationsAndroid notification channels 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 notification channels through app-wide permission versus one disabled channel, Focus and battery restriction.
Open record Android · notificationsAndroid notifications arrive late or only after unlocking
Delayed alerts usually come from per-app notification settings, battery optimization, restricted background data, Focus/Do Not Disturb or a vendor sleep list.
Open record Android · incoming callsAndroid phone rings but the incoming-call screen does not appear
A missing call screen can result from Phone app notifications, display-over-app permission, default-phone selection or a stuck call app—not the cellular connection itself.
Open record Android · storageAndroid storage is full even with few photos
Hidden storage is often app caches/downloads, offline media, messaging attachments, trash or system update files. Use the storage breakdown before deleting app data.
Open record Android · USBAndroid USB file transfer 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 USB file transfer through charge-only cable versus port, host driver, USB preference and security prompt.
Open record Android · USBAndroid USB file transfer 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 USB file transfer through charge-only cable versus port, host driver, USB preference and security prompt.
Open record Android · USBAndroid USB file transfer 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 USB file transfer through charge-only cable versus port, host driver, USB preference and security prompt.
Open record Android · USBAndroid USB file transfer 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 USB file transfer through charge-only cable versus port, host driver, USB preference and security prompt.
Open record Android · USBAndroid USB file transfer 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 USB file transfer through charge-only cable versus port, host driver, USB preference and security prompt.
Open record Android · USBAndroid USB file transfer 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 USB file transfer through charge-only cable versus port, host driver, USB preference and security prompt.
Open record Android · BluetoothAndroid will not pair with a Bluetooth device
Turn Bluetooth off and on, restart both devices, make the accessory discoverable and keep it nearby, then forget and re-pair it. Check whether the accessory is still connected to a different phone before resetting network settings.
Open record Android · system servicesGoogle Play services 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 Google Play services through one app versus system service update, account, storage and device certification.
Open record Android · system servicesGoogle Play services 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 Google Play services through one app versus system service update, account, storage and device certification.
Open record Android · system servicesGoogle Play services 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 Google Play services through one app versus system service update, account, storage and device certification.
Open record Android · system servicesGoogle Play services 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 Google Play services through one app versus system service update, account, storage and device certification.
Open record Android · system servicesGoogle Play services 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 Google Play services through one app versus system service update, account, storage and device certification.
Open record Android · system servicesGoogle Play services 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 Google Play services through one app versus system service update, account, storage and device certification.
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