Nexus4
Constructors
Properties
A callback that will be called when the app requests to advertise. The callback should return the TX power level used for mock advertising.
The Android SDK version.
Whether the BLUETOOTH_ADVERTISE permission is granted.
Whether the BLUETOOTH_CONNECT permission is granted.
Whether the BLUETOOTH_SCAN permission is granted.
Whether LE 2M PHY is supported on the device.
Whether LE Coded PHY is supported on the device.
Whether LE Extended Advertising feature is supported.
Whether location service is enabled on the device.
Whether the fine location permission is granted.
Whether location is required to scan for Bluetooth devices.
Whether multi advertisement is supported by the chipset.
Whether the device can scan for Bluetooth LE devices advertising on LE Coded PHY as Primary PHY.
Some Android devices claim they can only transmit 27-byte long packets on L2CAP in the LLCP Data Length Update procedure, while later trying to send 251 bytes. This causes the peripheral to terminate the connection. This flag simulates this issue. It was encountered e.g. on Samsung A8 and Samsung A8 Tab.
Some early Android devices were sending only one Scan Request message for a single device per scan. Non-connectable devices were reported continuously, but connectable devices were reported only once. The client had to stop and start scanning again to receive further advertisements. This flag simulates this issue. It was encountered e.g. on Nexus 4.
The maximum LE advertising data length in bytes, if LE Extended Advertising feature is supported.
Whether the device requires runtime permissions to use Bluetooth.
A callback that will be called when the mock central manager requests to scan for devices. It returns whether the scan was successful, secretly failed, or returned an error.