Venu SQ2 Stuck on NULL Values After Power Cycle

Assuming this is a device app, do you call 

Yes, I did. The app at the beginning was working even on this device. 

I did like this:

What do you see if you display Sensor.getInfo().heartRate in your app?  Also try Activity.getActivityInfo().heartRate.

With println calls in your code are things being called as you expect?

Thanks for your reply!

Is there any possibility to have a sort of “USB debug” mode to run the application and see all this information in real time on the PC?

I couldn’t find anything like that in the documentation — the only option I saw was the possibility to save all the println output inside a .txt file with the same name as the .prg. However, when I tried it, it didn’t seem to work properly — maybe I did something wrong during the process.

Any suggestions on how to properly enable that kind of logging or an alternative way to debug on a real device would be really appreciated.

no, unfortunately there's no USB debug

2724961 said:

I couldn’t find anything like that in the documentation — the only option I saw was the possibility to save all the println output inside a .txt file with the same name as the .prg. However, when I tried it, it didn’t seem to work properly — maybe I did something wrong during the process.

It is possible that the filename of the PRG on the device is not the same as the original filename of the PRG that was copied over as a sideload. One example is if the same app was also installed from the store. In this case, the sideload assumes the filename of the PRG from the store iirc (which is just a "random" string of letters and numbers).

You can get the filenames of all PRGs installed from the store by looking in garmindevice.xml (you will want to beautify this file so it's human-readable). Search for the app name (as specified in manifest.xml), and you should find an entry with the corresponding PRG filename. You could also use flocsy's list-apps.py script to do this programmatically.

Unfortunately that won't help you find the name of an app that was sideloaded and not installed from the store.

The easier way to resolve this issue is to uninstall the store version of the app before sideloading it.

Another remote possibility is that the watch truncated your PRG filename to 8.3 format: 8 characters followed by ".PRG". Tbh I don't think this would happen for a watch as recent as Venu Sq 2 but who knows.

(Of course it's not possible to directly look at the watch's "filesystem" to determine the name of the PRG, as PRGs are moved to inaccessible/hidden storage after being copied over.)

One way to determine the name of your PRG (sideload or not) would be to introduce a deliberate crash.

e.g.

(:typecheck(false))
function crashme() as Null {
    var x = new [0];
    var y = x[0]; // array out of bounds
    return y;
}

If your app crashes, an entry should be written to /garmin/apps/logs/ciq_log.yml (or ciq_log.bak) with the name of the app and its filename.

If I call crashme() in my app and run it in the sim, the sim produces a ciq_log.yml entry which looks like:

Error: Array Out Of Bounds Error
Details: 'Failed invoking <symbol>'
Time: 2025-03-22T15:11:55Z
Part-Number: 006-B4024-00
Firmware-Version: '22.22'
Language-Code: eng
ConnectIQ-Version: 5.1.0
Filename: TESTDF [filename in sim folder, minus .PRG]
Appname: TestDF [appname in manifest]
[stack trace]

On a real device, I am 100% sure that the filename in the log also corresponds to the "real" filename on the device.

Or you can use this script: https://github.com/flocsy/garmin-dev-tools/blob/main/scripts/list-apps.py

flocsy🤠 said:

Or you can use this script: https://github.com/flocsy/garmin-dev-tools/blob/main/scripts/list-apps.py

oh wow for real?

The advantage of the deliberate crash suggestion is that it will also work for apps that were sideloaded and not installed from the store.

I do appreciate that you made the script. Thank you again for that.

Sorry, Leo, didn't see that on page 308 :)