Beacons are detetected inconsistently on different devices - Question

[Flomm]

Hello.
This is more of a question, not a bug report.
In the introduction part you write:
"The library is a simple connection with the OS APIs, the BLE stack should be standard but often has different behaviors based on the device used, the operating system and the BLE chip it connects to. Before opening an issue verify that the problem is really the library."
We are trying to detect BLE beacons (manufactured by either HPE Aruba or Kontakt.IO). Some Android devices have no problem detecting them, while others simply can't see any of them. Then, sometimes they see one type, but not the other (iOS devices consistently detect both types of beacons). The devices have a wide range of Android versions (11-15), but we were unable to establish any pattern. And it's not just your library, we tried several others, along with our own native module implementations.
Anyway, I was wondering if there is any documentation about the above referred qutoe from your introduction? How and to which extent the behaviour of the devices differ from eachother? Is it possible at all to create an app that can reliably find any kind of BLE beacon on any (relatively modern) device? We are making a POC for attendance check with BLE beacons, and would be nice to have some documentation that supports our in-house investigation.

[marcosinigaglia]

Hi @Flomm , there is no documentation about it unfortunately. Sadly it is just an empirical observation of what happens. At the technical level I think there have never been thorough controls and defined standards and controls by an entity to guarantee certain things. Even at the level of the cell phone manufacturers, there have often been weird things to reduce battery consumption. In iOS as you observed things are at least standard, in Android you can't absolutely guarantee that anything will work.

[Flomm]

@marcosinigaglia Sorry to hear that. But thanks for the quick answer!