title: Android

Get Started

This document describes how to develop application based on Feitian Mobile SDK, including the development interfaces supported by mobile readers and how to develop applications based on these interfaces. This chapter covers the following topics:

  • Application development interfaces and library of Feitian mobile readers

  • Development of applications using PC/SC interfaces

  • Development of applications using private interfaces

The Feitian combo SDK supported below readers:

IR301, BR301, BR301BLE, BR500, more information, please go our website see more details:


Below is the interface support by Android:

Reader name IR301 BR301 BR301BLE BR500
Bluetooth 3.0
Bluetooth 4.0

Above showed the interface be supported by these readers, all readers had Micro USB interface, so you can using OTG cable with reader on Android platform. Alternatively, you can choose the Bluetooth 3.0 or 4.0 as communication channel work with reader.


We provide two interfaces and libraries to access the mobile reader, the simplest private API based on java language and PC/SC compatible API based on C language. We prefer using private API for your new project, and the PC/SC compatible API for exist project which you already using on PC platform.

JAR Library - private API definition

Related file Private API related files
JAR Library ftsafe.jar This jar include communication API and private API, also include the service, you can include this jar into your project and using private API directly, without load.h and.a files)

Static Library – PC/SC API definition, all related files need include to your project

ft_pcsc.h The define of PCSC API
ft_socket.h The define of socket API
ft_tools.h The define of string exchange
ftsafe.jar Based on above, the ftsafe.jar is service side, it will running as PCSC service to handle the request from.a. so in your project, you will include this file too.
Libftpcsc_arm_0.1.a The.a is PCSC client side, it send request to ftsafe.jar, for example, when user call ScardConnect, then.a will send request to ftsafe.jar to connect the reader, then the ftsafe.jar will call USB or Bluetooth framework do connect the reader and get data back

Private API


Download from https://github.com/FeitianSmartcardReader/FEITIAN_MOBILE_READERS/archive/master.zip

Build & Test

The project is developed based on eclipse, please using eclipse + NDK + Android on your PC. Import the whole project into your eclipse, build and run.

Make sure all related files already in the project which listed in figure 2.

We provide demo source code for integration, you can check the code and make your own code.

Private API

Authority the permission

Our SDK need access the USB and Bluetooth device, so before start development, we need open the authority. You can copy below code into your AndroidManifest.xml file.

<uses-feature android:name=”android.hardware.usb.host” />
<uses-permission android:name=”android.permission.USB_PERMISSION” />
<uses-permission android:name=”android.permission.MOUNT_UNMOUNT_FILESYSTEMS”/>
<uses-permission android:name=”android.permission.INTERNET” />
<uses-feature android:name=”android.hardware.bluetooth_le” android:required=”true”/>
<uses-permission android:name=”android.permission.BLUETOOTH_ADMIN” />
<uses-permission android:name=”android.permission.BLUETOOTH” />


Feitian private API, support Bluetooth, OTG and Bluetooth smart interface reader from Feitian.

We suggestion customer using private API, because it is easy to use and without complex configuration, all API wrote by Java, so you can copy the ftsafe.jar into your project and using the private API directly

Function Description
FTReader Constructor API
readerFind Find the reader, this API will scan Bluetooth and USB, to list the reader found
readerOpen Connect the reader
readerClose Disconnect the reader
readerPowerOn Do power on to the card
readerPowerOff Do power off the card
readerXfr Transfer APDU to card and get return data back
readerEscape Transfer escape APDU to card
readerAutoTurnOff Using to disable auto saving battery feature
readerGetSlotStatus Get slot status, for example, card absent or present
readerGetType Get reader type, the SDK support all Feitian mobile reader, so call this API can get specific reader type
readerGetSerialNumber Get reader serial number
readerGetFirmwareVersion Get reader firmware number
readerGetUID Get reader UID
readerGetLibVersion Get reader lib version

FTReader class

The private API has definition in “com.ftsafe.readerScheme” package, the class name call FTReader

The FTReader constructor is defined as follows:

public FTReader(Context context, Handler handler, int FTREADER_TYPE)
    Context contextInput parameter for context from user 
    Handler handlerInput parameter for handler from user
        Using to receive the notification in SDK, include below status:
            com.ftsafe.DK.USB_INPlug in USB reader
         com.ftsafe.DK.USB_OUTPlug out USB reader
              com.ftsafe.DK.CARD_IN_MASKCard present
              com.ftsafe.DK.CARD_OUT_MASKCard absent/remove
              com.ftsafe.DK.BT3_NEWDetected the Bluetooth 3.0 reader
              com.ftsafe.DK.BT4_NEWDetected the Bluetooth 4.1/4.2 reader
              com.ftsafe.DK.BT4_ACL_DISCONNECTEDdisconnect Bluetooth 4.1/4.2 reader

        int FTREADER_TYPEInput parameter, using to tell SDK which reader will be using:
            com.ftsafe.DK.FTREADER_TYPE_USBUsing USB OTG reader
              com.ftsafe.DK.FTREADER_TYPE_BT3Using Bluetooth 3.0 reader
              com.ftsafe.DK.FTREADER_TYPE_BT4Using Bluetooth 4.1/4.2 reader

When using USB OTG, do plug out/in reader will receive the notification in Handler parameter, which is com.ftsafe.DK. USB_IN or com.ftsafe.DK.USB_OUT


The private API has definition in “com.ftsafe.readerScheme” package, the class name call FTReader

The FTReader constructor is defined as follows:

public Public void readerFind() throws FTException
For USB OTG, when detect the Feitian USB OTG reader, the handler will inform the user to apply USB permission, and after got approval by user, will through the PID (Product ID) list all Feitian USB readers.

For Bluetooth 3.0 and 4.1/4.2 reader, when call this API, the SDK will filter the Bluetooth ID which named “FT_”, and through Handler to inform user com.ftsafe.DK.BT3_NEW or com.ftsafe.DK.BT4_NEW.


The readerOpen API is defined as follows

public String[] readerOpen(Object device) throws FTException
    Object device:
        USB OTG Reader: NULL (You also can input UsbDevice object, need get by customer code)
  Bluetooth 3.0/4.1/4.2: Input BluetoothDevice object (which is get from Handler)
        USB OTG Reader: Return reader list, support multi-slots, like R502 Dual interface reader
  Bluetooth 3.0/4.1/4.2: Return reader name or Bluetooth ID


The readerClose API is defined as follows

public String[] readerClose() throws FTException
The API will close all opened reader.


The readerPowerOn API using to power on the card, below is defined as follows

public byte[] readerPowerOn(int index) throws FTException
    int index:
        USB OTG Device:Provide the card slot number, which is get from readerOpen
  Bluetooth 3.0/4.1/4.20
Return value:Card ATR


The readerPowerOff API using to power off the card, below is defined as follows:

public void readerPowerOff(int index) throws FTException
int index:
USB OTG Device:Provide the card slot number, which is get from readerOpen
Bluetooth 3.0/4.1/4.20


The readerXfr API using to send command/APDU to card, below is defined as follows:

public byte[] readerXfr(int index,byte[] send) throws FTException
int index:Card slot number
-   USB OTG is the index value of the card slot    
-   Bluetooth 3.0/4.1/4.2 set to 0

byte[] send: Data/APDU for send to card
Return value:
Response data from card


The readerEscape API using to send escape command to reader, below is defined as follows:

public byte[] readerEscape(int index, byte[] send) throws FTException

int index:Card slot number
-   USB OTG is the index value of the card slot    
-   Bluetooth 3.0/4.1/4.2 set to 0

byte[] send:Data/APDU for send to reader
Return value:
Response data from reader


The readerAutoTurnOff API using to set the power saving feature, the BLE reader was designed with auto power on, if without any data communicate with reader, it will be going to turn off automatically, the purpose is to saving battery. Customer can through call this API to turn on/off this feature, below is defined as follows:

public byte[] readerAutoTurnOff (bool Value) throws FTException


bool Value:

-   If the value = false, means the reader will switch off power saving feature, the device won’t going to turn off after 2 mins (the condition is without any data communication between reader and App)

-   If the value = true, means the reader switch on power saving feature, the reader will not be going to turn off by itself.

Return value:

Response data from reader, 9000 means successful


The readerGetSlotStatus API using to send get card slot status, below is defined as follows:

public int readerGetSlotStatus(int index) throws FTException


int index:Card slot number

-   USB OTG is the index value of the card slot

-   Bluetooth 3.0/4.1/4.2 set to 0

Card slot status:

com.ftsafe.CARD_PRESENT_ACTIVE:Present card and already powered

com.ftsafe.CARD_PRESENT_INACTIVE:Present card and un-power

com.ftsafe.CARD_NO_PRESENT:Card absent


The readerGetType API using to get reader type, this API only works for OTG reader, not for Bluetooth reader, below is defined as follows:

public int readerGetType() throws FTException

Return valuecom.ftsafe.READER_R301E











The readerGetSerialNumber API using to get reader serial number, below is defined as follows:

public byte[] readerGetSerialNumber() throws FTException

Return value: Reader serial number


The readerGetFirmwareVersion API using to get reader firmware version, below is defined as follows:

public String readerGetFirmwareVersion() throws FTException

Return value: Firmware version


The readerGetUID API using to get reader UID (user ID), the User ID is hex number which using to encrypted whole reader firmware and also using for reader license authorize, customer can write UID in bulk readers, and work with their application to bind the reader only can work with their App. Below is defined as follows:

public byte[] readerGetUID() throws FTException

Return value: User ID string


The readerGetManufacturer API using to get reader Manufacturer:

public byte[] readerGetManufacturer() throws FTException

Return value:Manufacturer name with hex


The readerGetHardwareInfo API using to get reader Manufacturer:

public byte[] readerGetHardwareInfo() throws FTException

Return value:Hardware info name with hex


The readerGetReaderName API using to get reader name:

public byte[] readerGetReaderName() throws FTException

Return value:Hardware info name with hex


The readerGetLibVersion API using to get lib version:

public static String readerGetLibVersion()


Step #1: apply USB and Bluetooth permission first

Step #2: Call readerFind to register reader monitor, it will start filter Bluetooth and USB device, and feedback to user

Step #3: After get the list, call readerOpen API to open/connect the reader

Step #4: through the event API to check the card slot status

Step #5: If detect the card, then call readerPowerOn, the API will return your card ATR, you can call readerXfr API to send the APDU to the card, and get response data

Step #6: If you want operate the reader, you can call readerEscape or readerGetxxxx API to check the reader information, after finish your operation with card, you need call readerPowerOff the power off the card

Step #7: after done, please call readerClose to disconnect the reader and the reader will going to turn off automatically to save battery.


Since most PC software using PC/SC API, so support on this, we do wrap PC/SC API for users, below is the API already implemented, since it is wrap, so we just implement the important API, if you want have extra of these API, contact us we will support on this.

Function Description Implementation
SCardEstablishContext Create a context handle for accessing the smart card database.
SCardReleaseContext Close the context handle for accessing the smart card database.
SCardListReaders Obtain the list of the smart card groups.
SCardConnect Connect to a smart card.
SCardStatus Provide the status of a reader.
SCardTransmit Transmit data with a smart card via T=0 or T=1 protocol.
SCardDisconnect Terminate a connection to a smart card.
SCardIsValidContext Determines whether a smart card context handle is valid.
SCardReconnect Re-establish a connection to a smart card.
SCardBeginTransaction The function waits for the completion of all other transactions before it begins. After the transaction starts, all other applications are blocked from accessing the smart card while the transaction is in progress.
SCardEndTransaction Completes a previously declared transaction, allowing other applications to resume interactions with the card.
SCardGetStatusChange Blocks execution until the current availability of the cards in a specific set of reader’s change.
SCardControl Gives you direct control of the reader. You can call it any time after a successful call to SCardConnect and before a successful call to SCardDisconnect. The effect on the state of the reader depends on the control code.
SCardListReaderGroups Provides the list of reader groups that have previously been introduced to the system.
SCardFreeMemory Releases memory that has been returned from the resource manager using the SCARD_AUTOALLOCATE length designator.
SCardCancel Terminates all outstanding actions within a specific resource manager context. The only requests that you can cancel are those that require waiting for external action by the smart card or user. Any such outstanding action requests will terminate with a status indication that the action was canceled. This is especially useful to force outstanding SCardGetStatusChange calls to terminate.
SCardGetAttrib Retrieves the current reader attributes for the given handle. It does not affect the state of the reader, driver, or card.
SCardSetAttrib The SCardGetAttrib function retrieves the current reader attributes for the given handle. It does not affect the state of the reader, driver, or card.


To using PC/SC API is complex than jar lib, because it using multi-language to implement, create makefile build with NDK together. To avoid the misunderstanding, we also create a demo code to explain how to setup and using PC/SC API in your application.

For example:

  1. In our demo application, we wrote our demo App by C++, file is FtReaderTest.cpp, and you can find it in our demo code.

  2. We create Android.mk using to build C++ file with ftpcsc_arm_0 static library, it will generated dynamic lib FtReaderTest.so

  3. Create Tpcsc.java file, using javah command to generate com_example_ftreadertest_Tpcsc.h

  4. Write UI and call API from jni

package com.example.ftreadertest;
import com.ftsafe.PcscServer;

final static int PORT = 0x096e; 
PcscServer pcscServer = new PcscServer(PORT,MainActivity.this, mHandler);
                ftReader = pcscServer.getFtReaderObject();
new Tpcsc().testA(PORT);


  1. Before call API in JNI, you need start pcscServer first, the API need communication with ftsat.jar by socket.

The port is constant, so please keep it as 0x096E

Control Command

The reader also provides private control command for some users, you can call SCardControl/readerEscape API to send the below command to get your needs

Turn ON/OFF auto power off feature

Bluetooth reader only:

For Feitian Bluetooth reader, to have long usage for Bluetooth reader, we add save power feature in our firmware, which is the firmware will detect the communication data, if no any data through the firmware, then the reader will be going to power off.

Function Command(HEX)
Switch off automatically power off feature A55A8031
Switch on automatically power off feature A55A8030

CardSlot Event

The SDK provide a way to check the reader and card slot event automatically. Please check source code:

private Handler mHandler = new Handler(){
        public void handleMessage(Message msg){
            TextView textView = (TextView) findViewById(R.id.textView);
            String log=null;
            switch (msg.what) {
            case -1:
            case 0:
                log = msg.obj.toString();
            case DK.USB_IN:
                textView.append("NOTICE------->USB Device In\n");
                /*try {
                } catch (Exception e) {
                    textView.append("NOTICE------->USB Device In------->this should not happend------>" + e.getMessage() + "\n");
            case DK.USB_OUT:
                textView.append("NOTICE------->USB Device Out\n");
            case DK.PCSCSERVER_LOG:
            case DK.USB_LOG:
            case DK.BT3_LOG:
            case DK.BT4_LOG:
            case DK.FTREADER_LOG:
            case DK.CCIDSCHEME_LOG:
            case DK.BT3_NEW:
                BluetoothDevice dev1 = (BluetoothDevice) msg.obj;
            case DK.BT4_NEW:
                BluetoothDevice dev2 = (BluetoothDevice) msg.obj;
            case DK.BT4_ACL_DISCONNECTED:
                BluetoothDevice dev3 = (BluetoothDevice) msg.obj;
                textView.append("[BT4_ACL_DISCONNECTED]: "+dev3.getName()+" disconnected\n");
                if((msg.what & DK.CARD_IN_MASK) == DK.CARD_IN_MASK){
                    textView.append("NOTICE------->" + "slot"+(msg.what%DK.CARD_IN_MASK)+":card in\n");
                }else if((msg.what & DK.CARD_OUT_MASK) == DK.CARD_OUT_MASK){
                    textView.append("NOTICE------->" + "slot"+(msg.what%DK.CARD_OUT_MASK)+":card out\n");