:extendedCode - Inconsistent Implementation in SDK / Devices

Hi,

recently we bumped into unexpected memory issues on certain devices. We are using the extendedCode annotation for certain parts of an app's (watch face) code, what requires "System8" as of the announcement from beginning of this year. This works fine for most devices we support (Epix2, EpixPro Series, Fenix8 Series, Venu3). But there are some odd things I'd like to bring up:

A. Some "special focus" devices don't support System8, although they are based on models that are supported:

approachs7042mm
approachs7047mm (based on Venu3)
descentmk343mm
descentmk351mm (based on EpixPro)

It would be great if Garmin will support these devices and make them System8 compatible

B. On some System8 devices :extendedCode does not work:

d2mach1

fr570

fr970

On these the app crashes with an "out of memory" error, both on the simulator and on the real device. That's especially bad in the case of the new Forerunners! This needs to be fixed asap.

I'm interested in your experience on this topic. Did you observe something similar? I'd like to cross-check before raising a bug report.

Best,

RoboleoApps-Team

jim_m_58 10 days ago

There are a number of things that aren't available on all devices even at the same System level, probably determined by the resources like available memory and maybe specific HW available like the GPU.

This looks to be just another case of that. Something you need to account for in your app.

Roboleo-Apps 10 days ago in reply to jim_m_58

The resources on app level are the same for the Approach compared to the Venu3. It seems more like Garmin missed to implement that feature in certain firmwares. Forerunner 570 / 970: Certainly no resource / hardware issue!

jim_m_58 10 days ago in reply to Roboleo-Apps

Over-all resources you can't see like total available memory on the watch....Even if the HW is almost the same, the firmware may not be and hasn't been in the past.

the side of the common graphics pool could also be different for example.

jim_m_58 10 days ago in reply to jim_m_58

See https://forums.garmin.com/developer/connect-iq/i/bug-reports/extended-code-space-extendedcode-is-not-supported-for-some-of-the-newest-devices

Roboleo-Apps 10 days ago in reply to jim_m_58

OK, thanks. Anybody supporting that bug-report please vote up.

jim_m_58 10 days ago in reply to Roboleo-Apps

Understand that even if Garmin decides to change this today, it would be a FW change and may not roll out until the Q3 FW,

Roboleo-Apps 6 days ago

Kyle.ConnectIQ Hi Kyle, you've been very helpful on the FR165 firmware issue (drawRadialText etc) earlier this year. Could you raise this issue at the right places within Garmin, please? As Jim mentioned, there is already a bug report on this.

Thanks!