Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Sendig different BLE characteristics

Abierto
#24 14 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
25/100
Tipo de issue
Error
Claridad
Necesita aclaración
Estado de actividad
Estancado
Stack tecnológico
android, kotlin
Área
mobile

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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?

Lenguaje dominante
Kotlin
Estrellas
99
Forks
49
Sin PR fusionados en 30 d

Guía de contribución

Abrir la guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de STMicroelectronics/BlueSTSDK_Android

Todos los issues de STMicroelectronics/BlueSTSDK_Android

Issues similares

Más issues de Kotlin

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.