Some apps do not work while watch is connected to phone

Former Member over 9 years ago

Hi, guys. I have fenix 3 sapphire. Yesterday, i mentioned, that some of my Apps, installed from Connect IQ store, failed to run. When i'm trying to start an app, i just see the IQ! picture and that is all. It seems, that this happen when i'm connected with my phone via Bluetooth. When i switch off Bluetooth on phone and watch becomes not connected, these apps start working again. This kind of magic is very disappointing, because my watch is always connected to my phone.

Examples of apps are relatively popular Gym Timer (https://apps.garmin.com/en-GB/apps/93d358c4-53d3-4a9d-a7c4-e6f9a49c0e31) and Cycling App Professional (https://apps.garmin.com/en-GB/apps/9cbef7c8-9a7e-4f90-b4ef-42b11a11d8cd)

In the same time SkyWatch (https://apps.garmin.com/en-GB/apps/e531bb5d-56d1-4649-b790-adefa5adf04a) is working all time.

This happen only with Apps type of Connect IQ apps, widgets, watchfaces work properly.

watch firmware 6.50
garmin express version is the latest
connect app on Android phone - latest version

why this happen? thanks

UPDATE:
playing with this issue, i can even claim, that this kind of problem occurs randomly. sometimes apps start to work after sync with Garmin Connect App on phone, sometimes, after disabling bluetooth

geniuswrist over 9 years ago

Just an info I forgot to mention

I never had problems with my vivoactive (with firmware 3.4 or older ones) and also never had user complaints about crashs in vivoactive device.

jim_m_58 over 9 years ago

I kind of recall seeing something like this in an earlier version of the FW for a va. There's probably a thread about it here a bunch of pages back in time.

I had a CIQ widget (or maybe an app, I forget!) I was working on, and it did makeJsonRequest(). I'd side load a version of that CIQ .prg, remove it from the charger, and as soon as the phone was connected, I'd fire up what I wanted to test, and I'd get a CIQ "IQ!" some of the time. But if I waited a minute or two, it never crashed..

IIRC, it was an "out of memory" error, as the "phoneConnected" logic in the FW was still using memory at that time. What ever caused it was fixed in the next FW update - that's why I forget the details..

Former Member over 8 years ago

Any updates to this?

Hello all - I know these posts are from awhile ago, but I have been having these same issues with the Run Fields, Gym Timer, and Hike apps - what is considered a "high memory" watch face? Kind of sucks you have to choose between having more than a simple watch face and having apps run. I am using less than half of my capacity on my watch (297KB available of 512) so this just seems unreasonable to me! I have the vivoactive by the way

Brandon.ConnectIQ over 8 years ago

I don't see any updates on the case on which I reported this issue to the device team. I'll contact them and see whether they can up-prioritize the issue.

jim_m_58 over 8 years ago

Hello all - I know these posts are from awhile ago, but I have been having these same issues with the Run Fields, Gym Timer, and Hike apps...

By Hike apps, if you mean "Hike", that's me. I do lots of testing on a va, and don't see any issues. It shouldn't cause any impact on watchfaces, as it only uses memory when it actually running, and with the latest FW, it doesn't allow you to get to even the native watch while Hike is running..

That said, I have heard of issues with another app and the phone It does comm and wouldn't work most most of the time. What it turned out to be is that the user had paired the watch in their phone settings and also in Garmin Connect Mobile. Once the user removed the pairing in the phone settings (and kept the pairing in GCM) things got much better and worked consistently. Maybe something like that is going on?

The Phone settings paring is for "normal" bluetooth, but the va, etc uses "Bluetooth Smart" which is why you only want to pair from GCM.

Brandon.ConnectIQ over 8 years ago

@NIKEOW @robinsonmilani:

Have either you you experienced this issue or received recent reports of this issue on the latest device firmware? (Fenix 3 is at 7.20, and Fenix 3 HR is at 3.20). If it's still a problem, I'd like to see if anyone can collect a RAM dump from a representative device on the latest firmware. Follow this procedure immediately after a device crash:

Go to Settings > System > About
Press the Power button eight times to display a diagnostic menu
Choose Save RAM Region
Copy the [FONT=courier new]ERR_LOG.txt

[email protected]