Short answer: A paired Bluetooth scanner may still lack an active data connection or send input through a profile the application does not receive. Check connection, output mode and application focus separately. Follow one known barcode from the scanner to the application’s accepted record.
Separate pairing from receiving data
Record four observations: the host discovers the scanner, the devices are paired, the required connection is active, and a known scan reaches the receiving application. A paired-device list establishes only part of that path.
Android’s companion-device pairing documentation separates association from establishing a connection. Check the host OS version, application permissions and the scanner’s documented connection method. Retain the exact scanner model, firmware and host build.
Match the output mode at both ends
Determine whether the configured path sends keyboard input, serial data or events through a vendor interface. Both the host and application must support the selected path. Use the scanner’s configuration documentation rather than treating a successful radio pairing as proof of profile compatibility.
If the path emulates a keyboard, scan a short known value into a plain text field. Compare every character and any prefix or suffix. A decode beep without text at this checkpoint points to a different issue from correct text that the business application rejects.
Check the target field and application result
Repeat the same scan on the actual task screen. Record the focused field before and after capture, whether Enter or Tab submits the form, and the validation response. If plain text works but this screen fails, inspect field routing and the application’s input handling.
Where the application uses callbacks or a service, capture its received event and the next processing step. Check that the intended scanner is selected and that a previous input profile is not still active. Keep decode, received input and accepted transaction as separate observations.
Test reconnect and prepare a reproducible report
Repeat after the host suspends, the scanner powers down and the connection leaves range, using conditions permitted by the equipment instructions. Confirm both reconnection and input to the active task. If scans can be stored while disconnected, obtain the documented delivery and duplicate behavior before relying on it.
Send the scanner and host versions, profile, application version, known barcode, timestamps and the last successful checkpoint. For a request whose server confirmation is missing, inspect transaction status before rescanning. Duplicate-read troubleshooting helps separate repeated capture from repeated submission.
Device options for this task
If the project can combine scanning and the application on Android PDA Barcode Scanners, compare AIDC GO HX-21 and AIDC GO HX-24. Test the selected model’s barcode interface with the application before replacing an external scanner workflow.

