No CIQ_LOG.TXT

My watch has stopped creating the CIQ_LOG.TXT file on app crashes, which makes it very hard to debug crashes that happen on the device but not in the simulator. I've searched the forums and haven't found other people mentioning this. Is there some setting that I could have changed that caused this?

I'm debugging a sideloaded app, and can get an app log.

thanks,
alex

jim_m_58 over 7 years ago

What kind of app (watchface, DF, etc), what watch, and what FW version? When does it crash?
Have you tried turning your watch and back on? (the hard "off", where you hold the light button until watch turns itself off - maybe 20 seconds)

alexphredorg over 7 years ago

It is a full app and crashes at startup if the device was left with glonass turned on. I've done a lot of full power cycles and I'm using the latest SDK.

jim_m_58 over 7 years ago

What device? How big is your app? (peak memory in the sim)

Are you using GPS in the app? When do you start it? When the app firsts starts?

alexphredorg over 7 years ago

vaHR.

The app runs fine in GPS mode, this is only an issue in GLONASS mode. This isn't a peak memory issue, I'm used to those from a year of working on a fairly complex CIQ app.

It doesn't happen in the sim regardless of GPS simulated data modes.

Alan.raceQs over 7 years ago

FWIW, I'm running on a VA-HR with GLONASS on and not getting a crash. I suspect the GLONASS setting is a "red herring"

jim_m_58 over 7 years ago

I suspect that based on timing/quality of data you're taking a different code path. Where in your code are you staring positioning?

Try this app in both cases you mention. If one fails I can track it own in my code. If both work it will help to narrow down what you see.

https://apps.garmin.com/en-US/apps/116a5b59-29ae-4397-a70e-907d7e5f8e44

alexphredorg over 7 years ago

It could be a red herring, but it is the only thing that is different between the app not crashing and crashing. If I go into Bike mode and turn on GLONASS then I crash. If I go in and switch it back to GPS or reboot then the app doesn't crash. If CIQ_LOG worked then I'd be able to see why. It used to work on my device, but doesn't appear to be anymore.

I turn on position updates in the initialize method of my behavior delegate. You can see the code here:
https://github.com/alexphredorg/ConnectIqSailingApp/tree/master/source

Look at the initialize method in SailingAppDelegate.mc

alex

alexphredorg over 7 years ago

Sorry, raceQs is right and GLONASS is a red herring. If I start the bike app and wait for a GPS lock (GLONASS or not), then start my app, my app will crash. If I reboot the watchthen my app starts up just fine. I don't have the same problem with the run app. I do have a custom datafield loaded for the bike app and not the run app.

alexphredorg over 7 years ago

This appears to be a device issue with my device. It affects all CIQ apps, not just my own. I also tested with Connect IQ Benchmark and RaceQs. There must be something about the state that the device is left in after running the custom datafield in the bike app.

The installed datafield is "SmartCycle". I uninstalled it and the issue went away. It's still probably worth having someone on the ConnectIQ team investigate.

Brandon.ConnectIQ over 7 years ago

alexphredorg We'll investigate the SmartCycle app and see if there's a reproducible issue. I'm concerned about your device not providing any CIQ_LOG files on app crash. I'm not sure whether you're aware, but you can create a text file in /GARMIN/APPS/LOGS that matches a PRG name, and it will capture any System.println() output.That can be useful for pinning down where a problem is occurring.