-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Android 10 Compatibility #12
Comments
I have also downloaded ST BLE Sensor app version 4.7.2 from the Google Play store, and I have the same issue. |
Ciao Sara,
Yes we test our application on Android 10 on a some devices (but here we
don't have a motorola moto g7 Power sorry)
But please could you make a test?
On your code running on your BVBRNG board (sorry which firmware is running
on it and which board is? BVBNRG it's only the ble advertise name)
where there are are the other callbacks coming from BLE module
Please add also this one:
void aci_gatt_indication_event(uint16_t Connection_Handle,
uint16_t Attribute_Handle,
uint8_t Attribute_Value_Length,
uint8_t Attribute_Value[])
{
aci_gatt_confirm_indication(Connection_Handle);
}
Recompile the binary and flash it on your board and please make again the
test
and let me know if the problem is solved or not
Ciao and thanks a lot
Luca
ps:
please give to me more info on your running functional pack on your board
and which board are you using
Ciao
Il giorno mar 15 set 2020 alle ore 22:48 SaraHackett13 <
[email protected]> ha scritto:
… I have also downloaded ST BLE Sensor app version 4.7.2 from the Google
Play store, and I have the same issue.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#12 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEMVJZUES6W436LYN3KVPZTSF7HLTANCNFSM4RNV4G2Q>
.
--
Luca Pezzoni
|
Hi Luca, Thanks for getting back to me. I am using the STEVAL-BLUEMIC-1. I am not sure what firmware version is on the board. I am using the board by itself, not with a larger microcontroller. The block of code callbacks I posted was from the BlueMS Java code in Android Studio. Those callbacks were coming from the app side, not the board. I haven't touched the binary code that the board runs. How can I re-flash the STEVAL-BLUEMIC-1 board? Perhaps there is something I can test on the Android Studio side? Thanks! |
Ciao Sara,
I know that your log comes from Android Studio
We have found that for some devices (for example Samnsung s10e) if the code
running on the board will not answer to that event indication...
The phone will stop speaking with the board after a while (even if longer
than a few seconds... )
I will speak with the developers of the STEVAL-BLUEMIC-1 and I will ask
them if they could create one binary with the below modification...
And I will tell you all the info for flashing the new binary on the
STEVAL-BLUEMIC-1
and test it
(I had never used that board... so I could not tell to you how flash the
new binary to it in this moment.. sorry)
Ciao
Luca
Il giorno mer 16 set 2020 alle ore 16:21 SaraHackett13 <
[email protected]> ha scritto:
… Hi Luca,
Thanks for getting back to me.
I am using the STEVAL-BLUEMIC-1. I am not sure what firmware version is on
the board. I am using the board by itself, not with a larger
microcontroller.
The block of code callbacks I posted was from the BlueMS Java code in
Android Studio. Those callbacks were coming from the app side, not the
board. I haven't touched the binary code that the board runs. How can I
re-flash the STEVAL-BLUEMIC-1 board?
Perhaps there is something I can test on the Android Studio side?
Thanks!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#12 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEMVJZQADKZGGTL3M4NKXYTSGDCVDANCNFSM4RNV4G2Q>
.
--
Luca Pezzoni
|
That'd be great, thank you! Just a side note, on a Samsung Galaxy s6 (Android 7.0) the BlueMS app works fine with the STEVAL-BLUEMIC-1 board. |
Ciao,
Attached the new binary that you could test on your board
Here you should find the instruction on how flash the board:
https://www.st.com/resource/en/user_manual/dm00411757-getting-started-with-the-stevalbluemic1-evaluation-board-ultralow-power-wireless-microphone-based-on-spbtle1s-module-stmicroelectronics.pdf
Let me know if this could resolve the problem with your phone
Ciao
Luca
Il giorno mer 16 set 2020 alle ore 16:47 SaraHackett13 <
[email protected]> ha scritto:
… That'd be great, thank you!
Just a side note, on a Samsung Galaxy s6 (Android 7.0) the BlueMS app
works fine with the STEVAL-BLUEMIC-1 board.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#12 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEMVJZXAHEABHGEMVGHBNQ3SGDFYZANCNFSM4RNV4G2Q>
.
--
Luca Pezzoni
|
Hi Luca, I don't see a binary attachment to your previous reply. Do you know why some phones don't respond to the event indication you recommended below, like the Samsung s10e you mentioned above? If the board doesn't respond to this indication, is there a way to fix it or will I not be able to use that phone?
Are there certain phones that are guaranteed to properly communicate with the STEVAL-BLUEMIC-1 board and run the BlueMS app? |
Sorry the email from gmail had the attach,,, but github don't want a .hex |
Hello,
I am running the ST BLE Sensor app V 4.7.1 on a Motorola Moto g7 Power that runs Android 10 (API 29). I am using the BVBNRG board.
I am having trouble using the BlueVoice portion of the app. After a few seconds, the audio data stops streaming and the waveform graph stops plotting. If I wait a few more seconds, the Bluetooth connection between the phone and BVBNRG board disconnects and reconnects (see log below). Upon reconnection, the audio stream resumes then stops again after a few seconds.
Is the ST BLE Sensor app compatible with Android 10? If so, what changes do I need to make to allow continuous audio stream with the BlueVoice fragment?
Thanks.
The text was updated successfully, but these errors were encountered: