Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Sendig different BLE characteristics

未关闭
#24 14 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
25/100
Issue 类型
缺陷
描述清晰度
需要澄清
活跃度
停滞
技术栈
android, kotlin
领域
mobile

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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?

主要语言
Kotlin
星标
99
派生
49
PR 合并指标
30 天内没有已合并 PR

贡献指南

打开贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

STMicroelectronics/BlueSTSDK_Android 的其他 Issue

查看 STMicroelectronics/BlueSTSDK_Android 的全部 Issue

相似的 Issue

更多 Kotlin Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。