I'm trying to configure my FSC-BP108B tags to advertise with a non-iBeacon Manufacturer Data payload, and I'd appreciate any
pointers.
Setup
Hardware: Feasycom FSC-BP108B (×4)
App: BPMaster (latest from Play Store)
Firmware:
Test phones: Samsung Galaxy A36 (Android 16), Xiaomi (Android 14)
What I'm trying to do
Configure a slot to broadcast Manufacturer Data starting with company ID 0x0006 (or any non-Apple ID), with a fixed user-defined
identifier in the payload — basically an arbitrary raw payload, not the standard iBeacon 02 15 header.
Why
On Android 14+, the OS-level tracker-protection feature silently filters iBeacon-format advertisements before they reach
BluetoothLeScanner callbacks in third-party apps. nRF Connect (privileged) can see the tag fine, but our app never receives a
callback for it. We confirmed this on two phones across multiple OEMs; iBeacon ads from these tags simply never reach us. Microsoft
Continuity ads (06 00 …), Eddystone, and other non-iBeacon manufacturer data come through normally on the same hardware.
What I've tried
In BPMaster → Beacon Adv → I tapped the advertisement format dropdown. The only options are: iBeacon, aoaBeacon, altBeacon,
eddy-uid, eddy-url, eddy-tlm. None of them expose a raw byte field I can populate freely.
Questions
Is there a "custom" / "raw" / "user-define" advertisement mode in BPMaster I'm missing — perhaps under a different menu?
Can the FSC-BP108B accept AT commands to set arbitrary advertisement data? If so, how do I open an AT / UART session from
BPMaster (or another app) on Android?
Has anyone else hit Android's iBeacon filter and worked around it — did switching to altBeacon or Eddystone work in your tests?
