Symptoms
Switch scanning moves focus yet cannot enter a selected letter.
The useful clue here is what still works: Switch scanning moves focus yet cannot enter a selected letter. That narrows the test to the point where the two paths diverge.
- The failing path: Switch scanning moves focus yet cannot enter a selected letter.
- Control test: Test the same switch action in a simple settings screen and in the keyboard.
- A successful outcome: A disposable note accepts three chosen letters via switch input.
Why It Happens
Assistive devices can expose separate settings for calls, media, captions and accessibility scanning. Distinguish the communication path from the hearing or input aid itself.
There are three genuinely different layers worth checking; use the observation in the table to decide which one is implicated. None of these is proven merely by the symptoms.
- Selection action unassigned. This explanation predicts a different result in the comparison test or the more advanced inspection.
- Keyboard scanning mode mismatch. This explanation predicts a different result in the comparison test or the more advanced inspection.
- Focus trapped in one app. This explanation predicts a different result in the comparison test or the more advanced inspection.
Before Making Changes
Keep a backup input method available before changing switch mappings.
Save the current configuration or capture screenshots of the exact option values; where a file or recording is involved, work on a disposable duplicate. If this is shared equipment, ask the owner or administrator before changing it. Prefer a safe test item over real customers, medical decisions, paid transactions or irreplaceable data.
Write down the device model, platform, observed time of failure, and which action still works. These details will distinguish an unsupported feature from a malfunction and will be useful if escalation is required.
Problem-Specific Diagnosis
Use the following route rather than guessing based on a product name. The expected differences are designed for this particular failure.
| Action or observation | Meaning of the result | Decision |
|---|---|---|
| Test the same switch action in a simple settings screen and in the keyboard. | Does the failure follow the affected file, profile, connection or location? | Keep this result as the baseline; do not alter two systems at once. |
| Check select/confirm switch assignment and scanning mode within accessibility settings. | Does the low-impact correction restore the exact failure without altering the control case? | Re-test; reverse the change if the original symptom is unchanged. |
| Distinguish keyboard focus traps from switch hardware debounce and app-specific keyboard accessibility. | Does this separate keyboard scanning mode mismatch from focus trapped in one app? | Use documented diagnostic views rather than blind replacement. |
| A disposable note accepts three chosen letters via switch input. | Is the same original symptom gone after a normal repeat? | Record the pass condition and preserve the working settings. |
If the control case fails as well, the fault may be broader than this guide. Stop at that point and check the shared power, account, access or media path before applying the narrow fix.
Beginner and Advanced Paths
Start with the reversible Beginner path. The Advanced path examines a different layer when the first route fails; it is not a repetition of the same restart or setting.
Step-by-Step Troubleshooting
Choose the simple reversible checks first, then investigate the deeper system layer only if necessary.
Record the exact failure
Confirm the behavior without guessing: Switch scanning moves focus yet cannot enter a selected letter. Note the affected account, file, connection or physical control and record the current settings. Keep a backup input method available before changing switch mappings.
Run the passing comparison
Test the same switch action in a simple settings screen and in the keyboard. Keep the working and failing cases separate. If both fail, stop and investigate the common path instead of forcing a narrow repair.
Apply the least disruptive correction
Check select/confirm switch assignment and scanning mode within accessibility settings. Change only this setting or route; do not reset unrelated profiles, storage or pairing records. Save the previous value so it can be restored.
Retest and keep the result
A disposable note accepts three chosen letters via switch input. Repeat after a normal reopening or reconnect. If the control case gets worse, undo the last change and write down the difference.
Separate the three underlying layers
Test the hypotheses independently: selection action unassigned; keyboard scanning mode mismatch; focus trapped in one app. A green status indicator does not distinguish them. Use the recorded control case as evidence.
Inspect the deeper component
Distinguish keyboard focus traps from switch hardware debounce and app-specific keyboard accessibility. Use only read-only diagnostics or documented configuration screens first. Capture logs and timestamps rather than removing the component or reinstalling software blindly.
Cross-check with an independent path
Where possible, repeat “Test the same switch action in a simple settings screen and in the keyboard.” using a second supported account, safe sample file, physical input, known-good cable or alternate compatible application. Change only one variable and note which outcome follows it.
Choose a reversible targeted escalation
If the deeper check isolates a fault, use a vendor-supported fix or authorized service for that layer; otherwise restore original values. Finish only when: A disposable note accepts three chosen letters via switch input. Keep a backup input method available before changing switch mappings.
Solution Checklist
Solution Checklist
Common Mistakes to Avoid
- Treating selection action unassigned as certain just because the behavior looks familiar.
- Changing several independent settings together, which makes the result impossible to interpret.
- Skipping the safety boundary: Keep a backup input method available before changing switch mappings.
- Calling the issue fixed after one status indicator changes but before repeating the original operation.
- Discarding the working configuration or the only original file before a replacement has been verified.
How to Verify the Fix
A disposable note accepts three chosen letters via switch input.
Use the same baseline case: Test the same switch action in a simple settings screen and in the keyboard. Then repeat the previously failing operation after a normal close-and-open, reconnect or next scheduled cycle, whichever matches the scenario. Confirm the part of the system that was already working is still unaffected.
Where a result can be measured, retain the test timestamp, file name, screenshot or device state. A temporary success that cannot be repeated is not yet a confirmed repair.
If the Problem Continues
Escalate from the surface symptom to the narrower mechanism: Distinguish keyboard focus traps from switch hardware debounce and app-specific keyboard accessibility. If this identifies a hardware, account-policy or service limitation, use the manufacturer’s authorized support route rather than bypassing controls.
When opening a support case, supply the model, software/firmware version actually installed, the failing operation, the successful comparison, the three possible explanations checked, and the final observed result. Redact account identifiers, access codes, serial-number photos and personal information from public posts.
Prevent Recurrence
Keep a short note of the confirmed working configuration, particularly the setting implicated by selection action unassigned. Repeat the disposable comparison after an app update, device replacement, major account change or new connection only when that change plausibly affects this issue.
Retain a recovery path: spare test material, a saved profile, a restore point, a backup copy or official service information, as appropriate for the device. Do not schedule risky resets as routine maintenance.
Official Resources
Android Accessibility Help — Set up Switch Access — manufacturer documentation relevant to this feature or compatibility pathway.
FAQ
Is selection action unassigned definitely the reason this happens?
No. The same symptom can come from keyboard scanning mode mismatch or focus trapped in one app. First compare the affected and unaffected paths: Test the same switch action in a simple settings screen and in the keyboard. Do not assume any cause without a different outcome.
How can I safely rule out keyboard scanning mode mismatch?
Try the reversible correction only after documenting the control: Check select/confirm switch assignment and scanning mode within accessibility settings. If the behavior does not change, restore the old value and use the deeper observation: Distinguish keyboard focus traps from switch hardware debounce and app-specific keyboard accessibility.
What if focus trapped in one app turns out to be responsible?
Do not force an unsupported setting or a factory reset. Keep the evidence and ask the manufacturer or responsible administrator to investigate the isolated layer. The measurable pass condition remains: A disposable note accepts three chosen letters via switch input.