The SDK needs to be loaded to your app when you package the app. The SDK starts to run in the app process when a user launches the app and is stopped immediately after the user closes the app.
Appropriate permissions are required to call different capabilities.
Capture permissions
API | Permission Name | Permission Request |
getBehavior | Behavior detection |
|
getBeaconStatus | Bluetooth | android.permission.BLUETOOTH |
| Location | android.permission.ACCESS_FINE_LOCATION | |
getHeadsetStatus | Bluetooth | android.permission.BLUETOOTH |
getLocation/getCurrentLocation | Location | android.permission.ACCESS_FINE_LOCATION |
| getWeatherByDevice/getWeatherByUser | Location |
|
getTimeCategories | Location |
|
| getBluetoothStatus | Bluetooth | android.permission.BLUETOOTH |
Barrier permissions
API | Permission Name | Permission Request |
BehaviorBarrier | Behavior detection |
|
BeaconBarrier | Bluetooth | android.permission.BLUETOOTH |
| Location | android.permission.ACCESS_FINE_LOCATION | |
HeadsetBarrier | Bluetooth | android.permission.BLUETOOTH |
LocationBarrier | Location |
|
TimeBarrier | Location | android.permission.ACCESS_FINE_LOCATION |
| BluetoothBarrier | Bluetooth | android.permission.BLUETOOTH |
To call the beacon capability, ensure that the permission requirements of HUAWEI Nearby Service are met. For details, please refer to Adding Permissions.
The HMS Core Awareness SDK does not store any personal data or disclose personal data to any third parties. The HMS Core Awareness SDK provides only capability APIs. The service capabilities can be called on demand through the APIs.
The HMS Core Awareness SDK and on-device service exchange data with each other using Binder. The security mechanism of Android ensures secure data transmission based on Binder.