Sendig different BLE characteristics
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
Research direction
Start by reviewing the BLE Sensor APP structure in this repository and the way it receives the two BLE packages. Compare the package UUIDs and the frontend sensor destinations described in the report, then determine whether the same UUID is involved. Done means identifying whether the issue is in packet identification or frontend handling and documenting a reproducible fix path.
Written by the indexing model from the issue text.
Description
Hello I'm currently trying using the BLE Sensor APP by STM and I would like to work around the BLE 20 bytes cap when sending information. Basically I want to know if the APP's structure given in this repository supports the receivement of two differente BLE packages, as in an example: first my tile sends information of a given set of sensors and then, after the APP has received it the tile sends out information related to a different set of sensors
What's happening now is that I'm alternating bewtween sending package 1 with a set of sensors and package 2 with completely different sensors but what's happening is that package1's info is getting on where I showcase package 2 sensor's info and vice versa. Could the problem be in sending these 2 information packets with the same UUID or is it something that the frontend is doing wrong? And so, how can I fix it?
- Dominant language
- Kotlin
- Stars
- 99
- Forks
- 49
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from STMicroelectronics/BlueSTSDK_Android
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 15/100
-
Difficulty 4/5 3-5 days Newbie friendliness 20/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
STMicroelectronics/BlueSTSDK_Android#29 · 2 comments ·
-
README Links Dead Open
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
All issues in STMicroelectronics/BlueSTSDK_Android
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
AAswordman/Operit#1265 · 3 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
acristescu/OnlineGo#216 ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
libre-tube/LibreTube#8803 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
status: waiting-for-triage type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
spring-projects/spring-security#19781 ·