Acknowledged
over 1 year ago

Connect IQ app with BLE scanning crashes Epix 2 (non-Pro) watch running System 7 (16.10 BETA)

Overview

Starting a Connect IQ app (widget or datafield) that turns on BLE scanning causes the Epix 2 (non-Pro) watch to crash/reboot.

Details

I have coded a widget that scans for a specific device via BLE, and if found connects to that device. The code is not using any of the new BLE functionality and works without any problems on System 5 and System 6 on several different devices. However, when that same code is installed on an Epix 2 (non-Pro) running 16.10 BETA (and thus, CIQ System 7) the watch crashes as soon as the widget is started and scanning is requested. I tried the same code as a data field with the same results.

If helpful, I can provide a PRG to use to test/replicate this issue.

Device: Epix 2 (non-Pro)

FW: 16.10

CIQ SDK: 6.2.4

For completeness, I also tried using the BETA Connect IQ SDK 7.0.1 but the same crash occurs.

Steps to Replicate

  1. Install (via sideload) a PRG for a simple widget with BLE scanning functionality -- I can provide a simple PRG, if needed
  2. Press START to access the apps
  3. Scroll down to newly installed BLE functionality widget
  4. Press START to start the widget
  5. Widget will function up to the point where BLE scanning is requested by the app to be turned on
  6. Watch crashes

The ERR_LOG.TXT file contains this info/stacktrace following a crash:


3943 (EPIX) SW ver: 1610
Build Type: RELEASE
Commit:cf26ffd047cc3ff2a876514c8a21b94e6250511b
ESN: 3419935121
01/10/24 11:33:26
Assert
..\..\..\TVM\btf\btf_tvm.c line 908
Stack frame PC, SP: 0x10001be5, 0x3038cb08
Call Stack - SP at 0x3038cb08:
0x18050613
0x10000c7f
0x18050613
0x10001ab9
0x1934963f
0x1017a6bd
0x19349c39
0x10007255
0x193846af
0x1938453b
0x1965fa7b
0x1965faa1
0x102b3baf
0x102b4d59
0x102b4fe7
0x102b58e5
0x193adb55
0x102af5b7
0x193adb09
0x102b3baf
0x102b4d59
0x102b4fe7
0x102b58e5
0x102b5191
0x19834e19
0x19383d61
0x1939922f
0x193b7927
0x100c41cd
0x1000658d
0x100073c3
0x100022e1
Uptime: 325017

dbrobert
  • over 1 year ago in reply to jim_m_58

    Interesting. I'm not having any luck from the activity loop, but I am sideloading so that might be related. And I could maybe handle it if the app just didn't work but it's causing a hard crash of the watch. And this is supposed to be a data field so the activity loop won't even be a good workaround.

  • over 1 year ago in reply to gasteropod

    I see then on a forerunner with the System 7 beta FW.  These are apps that worked fine for years before the beta FW.

    If launch the app from the glance view, no scanning.  If I launch from the activity loop, scanning works fine and the apps run fine

  • over 1 year ago in reply to gasteropod

    It looks like you have the Epix Pro (I have an Epix 2). If you've run into this, have you reported it anywhere? Or did you do it directly with someone at Garmin? And if this has been an issue since the release of the Fenix 7/Epix 2 in 2022 then I don't think there's much hope of it being fixed anytime soon. Disappointed

  • over 1 year ago in reply to dbrobert

    OK, that makes sense. If you create a glance view, you'll probably find it does not crash when started from the glance loop, but the scanning will not work and you cannot connect. I don't get crashes all the time, depending on what I do. 

  • over 1 year ago

     Oh? I didn't see any bug reports relating to this. Are you in the know behind the scene somehow? As for crashes, I can't get anything other than a crash; this was designed as a data field and I only switched it over to a widget to see if the app type affected it at all, and because there is no glance view, I am only trying to start it from the app loop.