How to Use an External NFC or RFID Reader on Android (USB-C OTG Checklist)

Android phones and tablets can read some RFID cards with built-in NFC, but not every card, not on every device and not without an app. An external reader, such as one of our USB-C RFID readers for Android, fills those gaps. It plugs into the charging port, takes power from the device and types each card number into the field that has the cursor, like a keyboard.

This guide explains when an external reader makes sense, how it works on Android and what to check before a rollout: OTG support, power, keyboard settings, output format and range. It closes with a troubleshooting table for the most common faults.

When an external reader beats built-in NFC

The external reader wins when the card is not 13.56 MHz, when the device has no NFC, or when the software already exists and only needs a number in a field. Built-in NFC wins when an app must read data stored on NFC tags. For the frequency background, see NFC reader vs RFID reader.

How a USB-C reader works on Android

Three pieces of standard technology do the work:

1. USB host mode. Normally a phone is a USB device that a PC talks to. With a reader attached, the phone must act as the host and supply power. This is what “USB OTG” means on a phone; the USB-IF defines the host role for portable devices in its On-The-Go and Embedded Host supplements. On a USB-C port, the phone detects the attached peripheral through the port’s configuration (CC) lines and switches on its 5 V output.
2. USB HID keyboard. The reader presents itself as a keyboard in the standard USB Human Interface Device (HID) class, so Android uses its built-in keyboard support. There is no driver, no app and no permission dialog.
3. Text input. When a card is read, the reader sends one key press per character. Android delivers the keys to whichever text field has focus, as it would for any USB or Bluetooth keyboard.

Our USB-C readers draw 100 mA at 5 V from the phone, well below the 500 mA limit for a USB 2.0 device, and have no battery to charge. They measure 35 × 35 × 7 mm without the plug and weigh about 20 g.

Choose the reader by card frequency

All four are read-only and share one housing. Apart from the A220-C, which reads both kinds of animal tag, each model reads one card technology, so a site with both EM4100 and MIFARE cards needs two readers. The U220-C is listed for 902–928 MHz only; check your country in UHF RFID frequency bands by country.

iOS is not a listed host for these readers. For iPhone and iPad, the H510-B Bluetooth NFC pocket reader (13.56 MHz, with a 125 kHz L510-B version) and the U510-B Bluetooth UHF pocket reader list iOS. The USB-C readers are also listed for Windows 7 and 10 PCs through an OTG adapter, but a desktop reader such as the H110-U 13.56MHz USB NFC card reader suits a fixed desk better.

The OTG checklist

1. Confirm USB host (OTG) support on the exact device model. Look for “USB OTG” in the specification, not just “USB-C”. A quick field test is a USB keyboard or flash drive on a USB-C adapter. App developers can check the Android system feature android.hardware.usb.host.
2. Switch OTG on if the device has a setting for it. Some phones and tablets ship with OTG off, and some switch it off again after a period without use. Check every device model in the fleet.
3. Check the port and the case. The plug must seat fully. Thick rugged cases and some port covers prevent that, so try the reader with the case removed before deciding a device does not work.
4. Watch the LED. The blue LED lights when the reader has power. No LED means no power from the port: OTG is off, the device does not support host mode, or the plug is not fully in.
5. Set the physical keyboard layout. Android applies a layout to each hardware keyboard. On a French or Belgian (AZERTY) layout, the digit keys type symbols such as & and é unless Shift is held, so a reader that sends 0–9 produces symbols. Open Settings > System > Languages & input (or Keyboard) > Physical keyboard and set the reader to English (US) so digits arrive unchanged. Menu names vary by brand.
6. Decide about the on-screen keyboard. While a hardware keyboard is connected, Android may hide the on-screen keyboard. If staff also type by hand, turn on the on-screen keyboard option in the same menu.
7. Put the cursor where the number belongs. The number goes to the focused field. Test in your real app, web form or spreadsheet, not only in a notes app.
8. Agree the output string. The H220-C, L220-C and A220-C type a 10-digit decimal by default; the U220-C types the EPC and Enter. If your app needs hex, a different length, the full 15-digit animal ID or a specific terminator, state it when you order; the output format is confirmed in your quotation. RFID card number formats explains the options.
9. Mind the phone’s own NFC. If phone NFC is on and a 13.56 MHz card comes near the phone’s antenna, Android may react as well, showing a tag message or opening another app and taking focus from your field. At a dedicated reading station, switch phone NFC off or keep cards away from the phone body.
10. Test with your real cards on every device model. Card and fob construction changes range. Order samples, pilot them with a small group, then confirm the volume order.

Receiving the number in your own app

To your app, the reader is a keyboard, so there is no SDK to integrate. A few habits make keyboard input reliable:

• Give reads a dedicated field. Use a single-line EditText that has focus when the screen opens, and validate what arrives, for example exactly 10 digits.
• Treat Enter as the end of a read. A hardware Enter reaches a single-line EditText through its OnEditorActionListener, or you can watch for KEYCODE_ENTER in onKeyUp(). If your reader sends no Enter, trigger on length or a short pause instead.
• Capture without a visible field. Override dispatchKeyEvent() in the Activity to see key events before the focused view does, and buffer characters until Enter.
• Tell the reader from a real keyboard. KeyEvent.getDevice() returns the input device, and its getVendorId() and getProductId() identify the reader, so your app can handle its key events separately.
• Web apps work too. A browser-based system receives the same key events. Read KeyboardEvent.code so the keyboard layout does not matter; the keyboard wedge explainer has a JavaScript example.
• Keep staff on the input screen. On a shared tablet, Android’s app pinning or your device-management kiosk mode stops users leaving the page that receives reads.

No command set or SDK is listed for the USB-C readers: they only type the ID. Your app cannot change their settings, read card memory or write to cards through them. If a project needs that, describe it in your RFQ.

Troubleshooting

If a card reads but the number does not match your records, the cause is usually the output format, not the reader or the card. Compare both numbers in the card number converter.

Before a volume order

• List every phone and tablet model that will host a reader, and test each one.
• Write down the output string your app expects: digits, base, length and terminator.
• Confirm the card technology with a sample, especially at sites with mixed 125 kHz and 13.56 MHz cards.
• For a private-label version, see OEM and ODM options; terms are confirmed in your quotation.

Compare the models on the Type-C OTG RFID reader page, or send your device model and a sample card with your inquiry and we will confirm the reader and output format before you order.