• Replies 4 replies
  • Subscribers 14 subscribers
  • Views 805 views
  • Users 0 members are here
Options
Related

Watch reboots indeterministically when my app is running (tested on VA, Fenix3HR)

ArtaudAntonin / Jiri Richter
Environment:
  • Device, FW: VA (FW: 4.40), Fenix3HR (FW: 4.02)
  • Eclipse version: Not using Eclipse, building via monkeyc CLI
  • CIQ SDK v2.2.4
  • CIQ mobile Android SDK v1.3


o A detailed description of the issue
My app is supposed to be run for several hours for sleep tracking. After an indeterminate amount of time, it would often reboot the watch and produce an ERR_LOG record. Logs below.

o Steps to reproduce the issue
On phone: Sleep as Android, Sleep as Android - Garmin addon (the CIQ companion) apps installed
On watch: the CIQ app installed
Steps: Start the watch app, let it run for some time. After a while, it will reboot. Does not happen always however.

o Any applicable additional information
ERR_LOG record from VA (2 crashes). I started the app again manually after the first crash:
1907 (vívoactive) SW ver: 440
Build Type: RELEASE
ESN: 3913321567
Battery Voltage: 4.027000V
02/14/17 23:45:57
RTL
errnum: 0x002
r0: 0x2000A3A0
r1: 0x602000A2
r2: 0x000BB5CB
r3: 0x00000000
Return Address (LR): 0x000D8459:Call Stack - PSP at 0x2000A138:
0x000D8459
0x000A5265
0x000BB5CB
0x000BB5CB
0x000B6899
0x000BB5CB
0x000BB5CB
0x000BB5CB
0x000B691D
0x0001E503
0x000C9F00
0x000D1F15
0x000D3E89
0x0001E203
0x0000C000
0x0001E503
0x000D44E3
0x000D41D5
0x00094606
0x000D10DF
HWM_usb_connected = 0x00. HWM_usb_mode = 0x01.
page addr = 0x000594C5
page addr = 0x0003C489
Uptime: 1754316406

1907 (vívoactive) SW ver: 440
Build Type: RELEASE
ESN: 3913321567
Battery Voltage: 4.013000V
02/15/17 00:50:55
RTL
errnum: 0x00A
r0: 0x20012F78
r1: 0x00000088
r2: 0x0000007E
r3: 0x0000007F
Return Address (LR): 0x000D8459:Call Stack - PSP at 0x20012D28:
0x0001F335
0x000D8459
0x000A5265
0x000202CB
0x000C3C49
0x000B68C1
0x000C3C49
0x000C3C49
0x000C458F
0x0009376F
0x000B730F
0x00090C09
0x000B58C7
0x00090C4D
0x000C3EB9
0x0002024F
0x0002041F
0x0001F7EF
0x00020BBF
0x0008F399
HWM_usb_connected = 0x00. HWM_usb_mode = 0x01.
page addr = 0x000594C5
page addr = 0x0003C489
Uptime: 3892450


ERR_LOG records from Fenix3HR (2 crashes, app was restarted manually after each crash):
2413 (fenix 3 HR) SW ver: 420
Build Type: RELEASE
ESN: 3933564360
Battery Voltage: 4.158000V
02/14/17 00:03:14
RTL
errnum: 0x00a
r0: 0x20025c70
r1: 0x000000a2
r2: 0x0000007e
r3: 0x0000007f
Return Address (LR): 0x00142cc3:Call Stack - PSP at 0x20025a40:
0x00142cc3
0x0010dc73
0x000a2585
0x0010dc73
0x0010dc73
0x0010e9d3
0x000aa8bd
0x00142a05
0x00142a05
0x0010e231
0x0014f13b
0x00113483
0x00028f21
0x001636bf
0x00071979
0x00071979
0x0000ffff
0x0000ffff
0x0000ffff
0x0000ffff
HWM_usb_connected = 0x00. HWM_usb_mode = 0x01.
page addr = 0x000fab65
page addr = 0x0015dc89
Uptime: 56003007

2413 (fenix 3 HR) SW ver: 420
Build Type: RELEASE
ESN: 3933564360
Battery Voltage: 4.120000V
02/14/17 02:03:11
RTL
errnum: 0x00a
r0: 0x20025c70
r1: 0x0000005d
r2: 0x0000007e
r3: 0x0000007f
Return Address (LR): 0x00142cc3:Call Stack - PSP at 0x20025a40:
0x00142cc3
0x0010dc73
0x000a2585
0x0010dc73
0x0010dc73
0x0010e9d3
0x000aa8bd
0x000243a5
0x00142a05
0x00142a05
0x0010e231
0x0014f13b
0x00113483
0x00028f21
0x001636bf
0x00071979
0x00071979
0x0000ffff
0x0000ffff
0x0000ffff
HWM_usb_connected = 0x00. HWM_usb_mode = 0x01.
page addr = 0x000fab65
page addr = 0x0011e0f9
Uptime: 7176483


o A code sample that can reproduce the issue (in email only if preferred)
Coleman already has the code for the app and also the apk for the companion app.
  • Just reproduced this again on a Vivoactive, running FW 4.40. Do you need any additional info?

    1907 (vívoactive) SW ver: 440
    Build Type: RELEASE
    ESN: 3913321567
    Battery Voltage: 3.931000V
    02/22/17 14:08:06
    RTL
    errnum: 0x002
    r0: 0x2000A3A0
    r1: 0x602000A2
    r2: 0x000BB5CB
    r3: 0x00000000
    Return Address (LR): 0x000D8459:Call Stack - PSP at 0x2000A138:
    0x000D8459
    0x000A5265
    0x000BB5CB
    0x000BB5CB
    0x000B6899
    0x000BB5CB
    0x000BB5CB
    0x000BB5CB
    0x000B691D
    0x0001D403
    0x000C9F00
    0x000D1F15
    0x000D3E89
    0x0001D103
    0x0000C000
    0x0001D403
    0x000D44E3
    0x000D41D5
    0x0009ED06
    0x000D10DF
    HWM_usb_connected = 0x00. HWM_usb_mode = 0x01.
    page addr = 0x000594C5
    page addr = 0x0003C489
    Uptime: 109184857
  • Hard crashes from a CIQ app (err_log generated) aren't really the common, but maybe it something with running out of memory? (most problems will just do an IQ! and the app will crash, but the watch won't)

    If it's something that takes a while to occur, could it be your app is increasing it's memory usage over time?

    You could do a Sys.println() every few minutes and log the Sys.getDeviceStats().usedMemory to a pre-created "<yourApp>.txt" file in the logs directory on the watch. If it's not a memory thing, you might be able to log other things to help narrow things down.
  • Thank you jim for your reply.
    I have had this reproduced again on F3HR, 27 minutes after starting the app the watch restarts. I have logged the memory usage, but there is more or less constant memory usage of around 30kB (out of 64kB).

    Do you (or someone else) have any idea what might be going on?

    I'm adding another ERR_LOG

    2413 (fenix 3 HR) SW ver: 420
    Build Type: RELEASE
    ESN: 3928437290
    Battery Voltage: 3.776000V
    02/24/17 13:36:10
    RTL
    errnum: 0x00a
    r0: 0x20025c70
    r1: 0x000000b2
    r2: 0x0000007e
    r3: 0x0000007f
    Return Address (LR): 0x00142cc3:Call Stack - PSP at 0x20025a40:
    0x00142cc3
    0x0010dc73
    0x000a2585
    0x0010dc73
    0x0010dc73
    0x0010e9d3
    0x000aa8bd
    0x00142a05
    0x00142a05
    0x0010e231
    0x0014f13b
    0x00113483
    0x00028f21
    0x001636bf
    0x00071979
    0x00071979
    0x0000ffff
    0x0000ffff
    0x0000ffff
    0x0000ffff
    HWM_usb_connected = 0x00. HWM_usb_mode = 0x01.
    page addr = 0x000fab65
    page addr = 0x0011e0f9
    Uptime: 17006447
  • Former Member
    Former Member
    Hey,

    I was able to get this log over to the device team to try and figure this out. You've been very patient.

    Thanks,
    -Coleman
Copyright © 1996-2025 Garmin Ltd. or its subsidiaries