I
Icy_Angel
Guest
I have an Android app that is advertised as BLE Gatt Server. A Win app that is BLE Gatt Client.
I pair the Android phone to Windows OS first then launch the Win app to connect to the Android phone App.
However, sometime I observe that even if the Win app is not launched, the device is shows as 'connected' in Win Setting page, and confirmed by the Android app that it has been connected. It proves that Windows OS is connecting to the Android app to.. get information? I have no idea as the Android app is implementing custom BLE profile and service.
However, when this happen, if I launch the Win app, the Win app won' be able to connect to the Android app through BLE. Most of the time the error would be "unable to get BLE Service" or "unable to get BLE characteristic".
I had to wait for the OS to "release" the device, ie. on setting page, the status becomes 'paired' instead of 'connected', then launch the app to connect with Android device.
And on one system, OS is always connecting to the Android device and the status is always shown as 'Connected'. As such, my Win app is not able to connect to the Android app at all even if I run the app.
Any idea why Win OS always need to connect to the Android BLE app and how I can reduce (hopefully) the number of times and duration for the OS to connect to the device automatically?
And I thought Windows handles Bluetooth connection at OS level so that all the app can 'share' the connection? Is my understanding wrong?
Thank you,
Angela
Continue reading...
I pair the Android phone to Windows OS first then launch the Win app to connect to the Android phone App.
However, sometime I observe that even if the Win app is not launched, the device is shows as 'connected' in Win Setting page, and confirmed by the Android app that it has been connected. It proves that Windows OS is connecting to the Android app to.. get information? I have no idea as the Android app is implementing custom BLE profile and service.
However, when this happen, if I launch the Win app, the Win app won' be able to connect to the Android app through BLE. Most of the time the error would be "unable to get BLE Service" or "unable to get BLE characteristic".
I had to wait for the OS to "release" the device, ie. on setting page, the status becomes 'paired' instead of 'connected', then launch the app to connect with Android device.
And on one system, OS is always connecting to the Android device and the status is always shown as 'Connected'. As such, my Win app is not able to connect to the Android app at all even if I run the app.
Any idea why Win OS always need to connect to the Android BLE app and how I can reduce (hopefully) the number of times and duration for the OS to connect to the device automatically?
And I thought Windows handles Bluetooth connection at OS level so that all the app can 'share' the connection? Is my understanding wrong?
Thank you,
Angela
Continue reading...