Android Mobile Devices
We provide a native development library in binary form for Android mobile devices under EVVA License (currently closed source).
The dependency can be acquired directly as Maven dependency com.evva.xesar:abrevva-sdk-android
:
Abrevva SDK @ Maven Central
<dependency> <groupId>com.evva.xesar</groupId> <artifactId>abrevva-sdk-android</artifactId> <version>${abrevva-sdk-version}</version></dependency>
Notes for your mobile application
Section titled “Notes for your mobile application”Features that may be required
Section titled “Features that may be required”- BLE related
<uses-featureandroid:name="android.hardware.bluetooth_le"android:required="true" />
Permissions that may be required
Section titled “Permissions that may be required”- BLE related
<uses-permission android:name="android.permission.NFC" /><uses-permission android:name="android.permission.INTERNET" /><uses-permissionandroid:maxSdkVersion="30"android:name="android.permission.ACCESS_COARSE_LOCATION" /><uses-permissionandroid:maxSdkVersion="30"android:name="android.permission.ACCESS_FINE_LOCATION" /><uses-permissionandroid:maxSdkVersion="30"android:name="android.permission.BLUETOOTH" /><uses-permissionandroid:maxSdkVersion="30"android:name="android.permission.BLUETOOTH_ADMIN" /><uses-permissionandroid:name="android.permission.BLUETOOTH_SCAN"android:usesPermissionFlags="neverForLocation"tools:targetApi="s" />
- NFC related
<uses-permissionandroid:maxSdkVersion="30"android:name="android.permission.NFC" />
Compliance
Section titled “Compliance”Dependencies
Section titled “Dependencies”- Nordic Kotlin BLE Library]
- Scanner
no.nordicsemi.android.kotlin.ble:scanner
- Client
no.nordicsemi.android.kotlin.ble:client
- Scanner
- Bouncycastle For Java
- Provider
org.bouncycastle:bcprov-jdk15to18
- Provider
- secure-random
org.kotlincrypto:secure-random
- kotlinx-serialization
- JSON
org.jetbrains.kotlinx:kotlinx-serialization-json
- JSON
- HiveMQ MQTT Client
com.hivemq:hivemq-mqtt-client
Use of cryptography
Section titled “Use of cryptography”- Communication with Services uses standard TLS encryption based on what the OS provides
- Communication with EVVA Components uses AES-CCM-256 encryption based on the Bouncycastle implementation