Tapping button while screen is touched may drop button event
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 42/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 停滞
- 技术栈
- cpp
- 领域
- embedded-iot
调研方向
从 src/systemtask/SystemTask.cpp 中第 155 行附近的 pinConfig.hi_accuracy 设置开始，然后阅读链接的 nRF5 SDK GPIOTE 中断文档。通过按住屏幕并点击侧边按钮来重现问题，并在考虑文档所述功耗权衡的同时比较中断配置。完成标准是按钮事件不会丢失，也不会残留为虚假的按下状态，同时不会对功耗造成不可接受的影响。
由索引模型根据 Issue 内容生成。
描述
Verification
- I searched for similar bug reports (including closed issues) and found none was relevant.
What happened?
Tapping the side button while the screen is touched may drop button toggle events.
What should happen instead?
Tapping the side button while the screen is touched does not drop any events.
Reproduction steps
- Open any app (not necessary but useful for demonstration)
- Hold touch on the screen
- Tap the side button
Possible outcomes:
- The screen goes back to the apps list. This is when the bug fails to trigger. Try again.
- The button press does not go through.
- The screen goes directly to the watch face. At this point you can release the screen touch and wait. It will further go to the watch info page, as though the button was still pressed.
Reproducing this bug should take around 5-10 tries, it's not extremely rare.
More details?
In the third outcome listed where there is still a phantom held button press, the watch will not reset like it normally does if the button is held for a very long time.
I believe the bug is caused by the interrupt mode used for the screen and button. The low accuracy mode used cannot handle more than one active pin at a time (source). Changing the interrupts to use high accuracy mode by changing pinConfig.hi_accuracy on line 155 of src/systemtask/SystemTask.cpp to true does indeed seem to fix this issue, but mark9084 in the Pine64 discord informed me that this could increase power draw by 60uA if the high frequency clock is not already running (they provided this link to relevant documentation) so this may not be a desirable fix.
Version
e03414c
Companion app
No response
- 主要语言
- C
- 星标
- 3.4k
- 派生
- 1.1k
- 平均合并
- 23 小时 18 分钟
- 30 天内合并 PR
- 1
环境准备
在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
InfiniTimeOrg/InfiniTime 的其他 Issue
-
BLE handlers use length fields from the packet without checking how much data arrived可能已有人在做 @DustinHab 于 37 天前认领。 未关闭
难度 4/5 3-5 天 新手友好度 56/100
InfiniTimeOrg/InfiniTime#2485 ·
-
Unexpected jump back to watch face when button pressed可能已有人在做 @SteveAmor 于 80 天前认领。 未关闭bug
难度 4/5 3-5 天 新手友好度 50/100
InfiniTimeOrg/InfiniTime#2461 · 2 条评论 ·
-
Screen doesn't go to sleep after reset countdown app可能已有人在做 @SteveAmor 于 78 天前认领。 未关闭bug
难度 4/5 3-5 天 新手友好度 45/100
InfiniTimeOrg/InfiniTime#2419 · 4 条评论 ·
-
难度 4/5 3-5 天 新手友好度 25/100
InfiniTimeOrg/InfiniTime#2410 ·
-
难度 4/5 3-5 天 新手友好度 45/100
InfiniTimeOrg/InfiniTime#2407 · 4 条评论 ·
查看 InfiniTimeOrg/InfiniTime 的全部 Issue
相似的 Issue
-
bug
难度 1/5 1 小时以内 新手友好度 84/100
VirusTotal/yara#2255 ·
-
bug
难度 2/5 1-3 小时 新手友好度 76/100
neutralinojs/neutralinojs#1861 ·
维护者通常 1 天内回复
-
[BUG] Filename sequence expansion (`+`) panics on numeric values exceeding `i32::MAX`可能已有人在做 @muntasir-396 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 82/100
CCExtractor/ccextractor#2402 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
FujiNetWIFI/fujinet-lib#204 ·
维护者通常 1 天内回复
-
os:linux
难度 2/5 1-3 小时 新手友好度 66/100
mpv-player/mpv#18649 ·
维护者通常 1 天内回复