Does every error reported in ERA cause an IQ! error screen to show on the actual watch?

I see quite a number of errors in ERA that users have not reported to me. So I am wondering if every error reported in ERA cause an IQ! error screen to show on the actual watch? If not, can someone clarify which ones don't cause and IQ! error screen.

Also what does the error type "System Error" mean?

_psx_ over 2 years ago

I was wondering about that too. I'm not sure because on my watch I don't have STRANGE/IMPOSSIBLE errors but I think there are 2 cases

- error and IQ screen

- error and auto restart - so nobody see errors only ERA

jim_m_58 over 2 years ago

In general the user will see the IQ! screen for each one, but in some cases, with a DF, the user might just see the standard timer instead of a CIQ DF.

"System Error" is generally something unexpected that doesn't track back to anything you can correct in your code.

If you are seeing this on a va4/venu with 7.10, that firmware wall pulled by Garmin and has been replaced by 7.20

BobMiles over 2 years ago

I would say yes, it's a crash. @_psx_ I don't think watchfaces can auto restart. At least for me it always takes me back to a stock watchface after my watchface crashed. I'm not perfectly sure on what system error means, but I saw it a lot with outdated watch firmware (e.g. the firmware the watch is shipped with) and it seems to be something that should have worked, but didn't.

jim_m_58 over 2 years ago in reply to BobMiles

Over the years, there have been a few cases where a CIQ app can cause the devices itself to crash, but it pretty uncommon these days. If the device does crash, it's an issue in the firmware and there is an err_log file generated. The contents of that only make sense to garmin folks.

One thing about ERA reports is they aren't unique user/devices. If you see something that occurred X times, all X could be the same user if the device/FW is always the same.

_psx_ over 2 years ago in reply to BobMiles

1. When error is in background no IQ crash (anyway for some errors).

2. I think it's possible to restart:

- run WF

- go to watch menu when you select WF - WF looks very strange, it runs in strange mode "very fast" there is no every second update but faster

- run settings on watch that showing Menu2 on full screen - user doesn't see WF - now if there is a crush and you exit from Menu2 WF will probably still runs - it means restarting - I've saw this once case when in one beta SW was bug in Menu2

_psx_ over 2 years ago in reply to jim_m_58

It was enough to use buffered bitmap on venu sq to even restart watch not only a crash.

I haven't decided to use buffered bitmaps on venu sq because nobody knows if it was fixed (for long time APAC versions had this bug).

And bug was in line buffDC.setColor(...); funny

SirLancelot over 2 years ago

Although ERA is super helpful, it almost never (in my case) picks up on out of memory errors. I know because my app tries to utilize the memory on the watch to download the most map data as possible. Although I’ve released my share of memory-buggy apps, the bugs sure don’t seem to make it to ERA.

EDIT: I responded a bit too quickly, and misunderstood your question to be “does ERA log every error?”.