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

Watchdog constantly reboots PineTime when bluetooth connected in version 1.15.0

未关闭
  • 哪里不对？
#2,246 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
35/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
停滞
技术栈
cpp
领域
embedded-iot

调研方向

未指定源文件或测试。首先，在 Bluetooth 正在连接时，使用之前的 XTX XT25F32 内存芯片和固件 1.15.0，在 PineTime 上通过 GadgetBridge 或 Amazfish 复现该故障。手表成功连接并保持运行，而不是进入 watchdog 重启和 rollback 循环，即表示完成。

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

描述

bug needs more info
Verification
  • I searched for similar bug reports (including closed issues) and found none was relevant.
What happened?

PineTime reboots immediately after connecting to a bluetooth device.

What should happen instead?

PineTime connects successfully to the bluetooth device and stays on after that.

Reproduction steps

Install pinetime-mcuboot-app-dfu-1.15.0.zip on PineTime with the previous memory chip (XTX XT25F32B, ref. https://github.com/InfiniTimeOrg/InfiniTime/issues/2096). For companion app I tried GadgetBridge (Android) and Amazfish (SailfishOS) with the same results. Keep the bluetooth active on the companion device, or activate it after PineTime boots with firmware 1.15.0, so the watch connects to the device.

If you want to experience several reboots without reverting to the previous firmware, you have to switch off bluetooth on the companion device right after the flashing is completed and before the PineTime completes booting, and you have to validate the firmware in the PineTime settings before switching on the bluetooth in the companion device. Otherwise, PineTime will try connecting during the first boot which will lead to rebooting and reverting to the previous firmware.

More details?

If bluetooth is disabled or not connected, the watch works as expected with all of its other functions.

If you don't validate the new firmware in the PineTime settings, reverting to the previous firmware after the first reboot leads to a fully working PineTime with the previous firmware.
But if you validate the new firmware, you have two options for reverting:

  1. Reboot PineTime while keeping the button pressed until the pine logo turns blue. After that, PineTime will revert to the previous firmware;
  2. (if the first doesn't help) Reboot PineTime while keeping the button pressed until the pine logo turns red. After that, PineTime will load some emergency firmware, which allows connecting to the companion device and you can flash some working firmware.

ATTENTION! No matter which of these two methods was used for reverting, it's not enough to clear the bluetooth problem. You have to boot PineTime with bluetooth disconnected (otherwise, PineTime will reboot again and switch to the validated new firmware), then validate the working firmware in the PineTime settings, manually reboot PineTime again (keep the button pressed while the pine logo is still white or green), and then you can switch on the bluetooth and connect to the companion device.

All the above is the same, no matter if the previous firmware is 1.14.0 or 1.14.1, or the bootloader is 1.0.0 or 1.0.1, or if you keep the added device in the companion app, or delete it after the flashing and make a new pairing after booting with 1.15.0. Clearing saved data, reinstalling and trying different versions of GadgetBridge and Amazfish doesn't help too.

It was fun to discover that PineTime keeps three firmware installations even after validating in the settings:

  1. The main firmware which it boots by default;
  2. The previous firmware that it reverts to, be it after rebooting non-validated firmware, or by going to the blue pine logo during the boot;
  3. The strange emergency firmware, which can be loaded by going to the red pine logo during the boot. It doesn't tell what it is (just the text InfiniTime with its logo), you can do nothing on the watch (even to turn off the display, you can just reboot), but allows you to connect to the companion device and even vibrates when new message arrives.
Version

v.1.15.0, now back to 1.14

Companion app

Different versions of GadgetBridge and Amazfish

主要语言
C
星标
3.4k
派生
1.1k
平均合并
23 小时 18 分钟
30 天内合并 PR
1

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

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

InfiniTimeOrg/InfiniTime 的其他 Issue

查看 InfiniTimeOrg/InfiniTime 的全部 Issue

相似的 Issue

更多 C Issue

把新 issue 发到你的邮箱

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