startLeScan with 128 bit UUIDs doesn't work on native Android BLE implementation

Question

I am having trouble using startLeScan( new UUID[]{ MY_DESIRED_128_BIT_SERVICE_UUID }, callback ) on the new introduced BLE API of Android 4.3 on my Nexus 4.

The cal

Answer 1

This is a reported bug at least in Android 4.3 JWR66Y:

• Filtering works, if I provide my 16bit UUID
• Filtering doesn't return any scan results, if I provide my 128bit UUID or if I provide both UUIDs

My setting: My device offers 2 UUIDs on advertising (1 16bit and 1 128bit) and 4 UUIDs on service discovery (1 128bit and 3 16bit).

Even if it gets fixed, I warn everybody against using the filter option provided by Android. For backward compatibility and since it's broken on Samsung Galaxy S3 with Android 4.3