How to Find Nordic Beacon Using BLE onLeScan() for Android

[RaQ]

I'm an Android developer and I bought the NRF51822-Beacon kit. All I want to do is be able to "see" the beacon using Android's onLeScan() bluetooth call. However, the beacon doesn't register at all. I can see other BLE devices, but not the Nordic beacon. I have the battery installed and the purple light is flashing which should mean it's beaconing. I don't want to use the Nordic app to "see" the beacon---the whole point is to be able to do it in a generic Android app. Do you know why I can't see the beacon? Is it even possible?

[RaQ]

/* DEVICE DISCOVERY */

private BluetoothAdapter.LeScanCallback mLeScanCallback = new BluetoothAdapter.LeScanCallback() {

    @Override
    public void onLeScan(final BluetoothDevice device, final int rssi, byte[] scanRecord) {
        runOnUiThread(new Runnable() {

            @Override
            public void run() {

                Log.e("Main: LeScanCallback()", "rssi " + rssi + " device " + device.getName() +
                        "  " + device.getAddress());

                btn_name.setText(device.getName());
                btn_address.setText(device.getAddress());
                btn_rssi.setText(""+rssi);
            }
        });
    }
};

[Aleksander Nowakowski]

Thanks. This code is OK and should work. The scanner-compat library does not limit you to any nordic devices. It just wraps the standard API with some other classes and gives you parsing, batch scanning etc. Those features were added in Android Lollipop or later. Does your app find other BLE devices but does not find your beacon? Remember, that the beacons name is null. Could you also post the code how do you start scanning?

[RaQ]

Here is the whole code. It should show the device name, rssi, and bluetooth address. Even if the name is null, the latter two elements should still show. I don't have access to Lollipop, only KitKat. Yes, my app finds other BLE devices but not my beacon.

public class MainActivity extends Activity {

// VARIABLES - FOR FINDING BLE DEVICE

BluetoothAdapter btAdapter;
final int REQUEST_ENABLE_BT = 1;	// A value > 0 which ensures the corresponding activity is
                                    // launched as a sub-activity

Button btn_name, btn_address, btn_rssi;


/* TURNS ON BLUETOOTH */
@Override
protected void onCreate(Bundle savedInstanceState) {
    super.onCreate(savedInstanceState);

    // GENERAL SETUP

    requestWindowFeature(Window.FEATURE_NO_TITLE);
    getWindow().setFlags(WindowManager.LayoutParams.FLAG_FULLSCREEN, WindowManager.LayoutParams.FLAG_FULLSCREEN);
    getWindow().addFlags(WindowManager.LayoutParams.FLAG_KEEP_SCREEN_ON);

    setContentView(R.layout.activity_main);

    Log.e("Main: onCreate()", "Starting");

    // GET STATUS

    btn_name = (Button) findViewById(R.id.name);
    btn_address = (Button) findViewById(R.id.address);
    btn_rssi = (Button) findViewById(R.id.rssi);

    // GET BLUETOOTH ADAPTER --- NECESSARY FOR DEVICE DISCOVERY
    //
    // Also check that the Android device has Bluetooth enabled. Will request the user enable
    // Bluetooth if it is currently disabled

    final BluetoothManager btManager = (BluetoothManager)getSystemService(Context.BLUETOOTH_SERVICE);
    btAdapter = btManager.getAdapter();	// The phone's Bluetooth radio

    if (btAdapter != null && !btAdapter.isEnabled()) {
        Intent enableIntent = new Intent(BluetoothAdapter.ACTION_REQUEST_ENABLE);
        enableIntent.putExtra(BluetoothAdapter.EXTRA_DISCOVERABLE_DURATION,0);
        startActivityForResult(enableIntent, REQUEST_ENABLE_BT);	// Enables Bluetooth if disabled
    }
    else
        btAdapter.startLeScan(mLeScanCallback);
}


/* QUIT IF THEY DIDN'T ENABLE BLUETOOTH */

@Override
protected void onActivityResult(int requestCode, int resultCode, Intent data) {
    // User didn't enable Bluetooth
    if ((requestCode == REQUEST_ENABLE_BT) && (resultCode == Activity.RESULT_CANCELED)) {
        finish();
        return;
    }
    super.onActivityResult(requestCode, resultCode, data);

    btAdapter.startLeScan(mLeScanCallback);
}


/* DEVICE DISCOVERY */

private BluetoothAdapter.LeScanCallback mLeScanCallback = new BluetoothAdapter.LeScanCallback() {

    @Override
    public void onLeScan(final BluetoothDevice device, final int rssi, byte[] scanRecord) {
        runOnUiThread(new Runnable() {

            @Override
            public void run() {

                Log.e("Main: LeScanCallback()", "rssi " + rssi + " device " + device.getName() +
                        "  " + device.getAddress());

                btn_name.setText(device.getName());
                btn_address.setText(device.getAddress());
                btn_rssi.setText(""+rssi);
            }
        });
    }
};

}

[Aleksander Nowakowski]

Your code is very good should work. So I guess the problem is with a beacon. Give your app some more time to find it. By default the nordic beacon advertises every 760ms which is quite rare. This makes it hard to be found. You may also press the SW2 button on the beacon (this will start the Config Mode with different adv interval) or SW1 - enables the DFU mode. In the DFU mode the beacon advertises very often so your app should easily find it.

You may also change the setting of the beacon and make it advertise more often. Press the SW2 button (it it's in DFU mode you need to take the battery out and in again and press SW2), connect to it using nRF Beacon app (the UPDATE tab) and change the advertising interval to 100ms. I would also recommend to disable the LED as it drains the most of the battery. After that you can check if your app can find it.

[RaQ]

Yes, it is very odd. I ran it in purple (normal beaconing), yellow (config) Sw2, and even blue (Sw1) mode. Nothing. My app is designed to show information (even if very brief) anytime it grabs a signal. I left it running for almost an hour and it never picked up the beacon. I turned on another BLE that I know only beacons once every 1-2 seconds, and my app saw it just fine. It never once saw the Nordic beacon. I will try changing the advertising rate later, though at the default 760ms, it's still faster than the other beacon that definitely works, and should have been seen without fault at least once.