MockAndroidEnvironment
A mock environment that can be used to test the behavior of the Central Manager.
Inheritors
Types
A mock environment for Android 5.0 (Lollipop).
A mock environment for Android 6.0 (Marshmallow).
A mock environment for Android 8.0 (Oreo).
A mock environment for Android 12 (S).
A mock environment for the Nexus 4.
A mock environment for the Samsung A8 with Android 14.
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.
Whether the BLUETOOTH_ADVERTISE permission is granted. The permission can be set to true to emulate it being granted in runtime.
Whether the BLUETOOTH_CONNECT permission is granted. The permission can be set to true to emulate it being granted in runtime.
Whether the BLUETOOTH_SCAN permission is granted. The permission can be set to true to emulate it being granted in runtime.
Whether the fine location permission is granted. The permission can be set to true to emulate it being granted in runtime.
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.
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.