Hi everyone,
I’m currently using the Khadas VIM1 as a BLE gateway device running a custom AOSP build. My goal is to simultaneously connect and communicate with multiple BLE peripheral devices (wearable pendants) for audio streaming and control.
When testing BLE advertising with my custom app, I found the system log shows:
mNumOfAdvertisementInstancesSupported = 1
Because of this, startAdvertising()
fails with “Too many advertisers” even if only one custom app is running.
Questions:
-
Does the AP6212 Bluetooth chip on VIM1 support multiple BLE advertising instances?
-
Is there a way to increase this instance count via firmware, driver modification, or kernel tuning?
-
Is it possible to disable the system Bluetooth stack (com.android.bluetooth) and take full control with a custom implementation?
-
Khadas Official Android Image
- Does the official Android image from Khadas (via firmware download) support:
- BLE advertising?
- BLE GATT server?
- Wi-Fi configuration via app (WifiManager)?
- I2S interface for audio output?
- Does the official Android image from Khadas (via firmware download) support:
I’m trying to decide whether I should stick with the official image or fully build AOSP from scratch.
I need to ensure that I can advertise to (and handle) multiple BLE devices simultaneously for commercial use. Any tips or confirmed limitations are appreciated.
Thanks!