Google Play ↗What to know
- Android 9 or newer is necessary but not sufficient: the phone must expose Bluetooth HID Device support.
- Connected describes the link, not proof that the focused computer app accepted a shortcut or click.
- Use the built-in Fix connection sequence and preserve your deck before broader changes.
Before you start
Keep the phone near an awake computer with Bluetooth enabled. Check that the computer permits Bluetooth keyboards, particularly on managed work devices.
Save work on the computer and open a temporary document for input tests. Keep a conventional keyboard or mouse available while changing Bluetooth settings. Do not clear app data or uninstall it just to retry a connection.
How to do it
Read the status before changing settings
Open Connect computer. If it says Bluetooth off, use Turn on Bluetooth. If Android requests Nearby devices permission, allow it for pairing. For Not supported on this phone, Try again can retry registration, but persistently missing HID support cannot be added with a Pro purchase.
Check the target and discoverability
Check that the intended computer is awake and nearby. For a new connection, choose Make discoverable and accept both pairing prompts. If already paired, try the existing computer entry before creating another pairing.
Use the guided recovery sequence
Choose Trouble connecting? Fix it step by step to open Fix connection. Follow the shown step, then use Try connecting now. If it still fails, This didn’t help — next step advances the guide. Later steps include toggling Bluetooth, restarting the app or phone, and re-pairing.
Separate delivery from shortcut behaviour
Once connected, focus an empty document on the computer and send ordinary letters from Keyboard. If letters arrive but a shortcut does not work, check Shortcut keys, the focused application and its own shortcut settings. Use Change beside Shortcut keys; switching the Pairing guide chip alone does not change the keys.
Re-pair only when the guide calls for it
A stale pairing may need removal on both sides, particularly after a keyboard/mouse-profile update. Follow the guide’s instructions for the selected computer: remove the phone from the host’s Bluetooth list, forget the matching host on the phone when requested, then make the phone discoverable and pair again.
Match the symptom to the next check
| Symptom | Check first |
|---|---|
| Not supported on this phone | Phone HID Device capability and the app’s Try again registration control. |
| Computer cannot find the phone | Make discoverable, Android permissions, host Bluetooth settings and device policy. |
| Paired but not connected | The existing host entry and Fix connection sequence. |
| Connected but letters do not arrive | The selected host, focused text field and a plain-letter Keyboard test. |
| Wrong punctuation or characters | US-layout mapping and the computer’s active input method. |
| Keyboard works but a newer pointer input fails | The update notice about cached keyboard/mouse profiles and guided re-pairing. |
Avoid changing several things at once
Try one step and inspect the result before moving on. Keyboard-layout problems differ from unsupported HID hardware or a failed connection attempt. Note the status and the simplest action that fails.
The recovery guide keeps progress through its app and phone restart steps. Closing it does not require deleting your deck. After Connected!, still test harmless input: the link does not confirm a macro’s outcome.
Know the remaining boundaries
Phone firmware, the computer’s Bluetooth stack and workplace policy can prevent operation. A host that refuses Bluetooth input is not something this app bypasses. If ordinary Mouse works but Air Mouse is unavailable, check the separate rotation-sensor requirement and Pro access rather than re-pairing repeatedly.
For a macro failure, test one key or short supported text. Focus, shortcut mapping and timing still matter. Do not repeatedly run a partial sequence and duplicate input. Export important decks before experimenting.
Limits to keep in mind
- These steps are source-based product guidance, not proof of a diagnosis or compatibility test for your individual phone and computer.
- Do not bypass organisational restrictions, install unknown drivers or erase saved decks to make a connection appear successful.
Questions and answers
Should I clear app data to fix pairing?
No. Start with the built-in connection recovery controls. Clearing data can remove your setup and is not part of this guide.
Does a Connected label prove my macro worked?
No. Inspect the result in the intended computer application. The Bluetooth link cannot confirm application focus or the effect of a shortcut.
Why did newer controls stop after an update?
A computer can remember the older keyboard/mouse profile. If the app shows Paired before this update?, follow its re-pairing instructions for the affected host.