Venu SQ2 Stuck on NULL Values After Power Cycle

2724961 13 days ago

Hi everyone,
I'm working on an application that reads some watch parameters as input, including HR and accelerometer data. I've encountered an issue while testing the app on the Venu SQ2: the device sometimes gets stuck and doesn't read any parameter.

This seems to happen particularly after turning the watch off and on again. From the .fit file generated by the app, I can see that all parameters remain set to NULL for the entire duration of the recording.

Has anyone else experienced similar issues with the Venu SQ2? Do you have any suggestions on how to fix this?
The watch is updated to the latest firmware version.

Thanks in advance!

2724961 11 days ago in reply to jim_m_58

Thanks for all your suggestions! I used the .txt file and some println() calls to debug the issue. When the problem happens, it looks like the listener doesn’t get called.

Do you think it makes sense to re-run the constructor if I see that all sensor data stay null?
Or maybe you have a better solution?

flocsy🤠 11 days ago in reply to 2724961

You can't "re-run" a constructor. Though I see what you mean, but I don't think that would make a difference. You can test it.

2724961 9 days ago in reply to flocsy🤠

I have an update I’d like to share with you to hear your thoughts.

I tried performing several power cycles on the device, and at some point, the same application that previously wasn’t working — and seemed not to register the sensor listener — suddenly started working correctly again (just like it did initially, before a power cycle caused it to stop working and exhibit the described issue).

From the debug output, I also added a System.println() line inside the constructor to check whether the HR value is actually available. I modified the constructor as follows:

function initialize() {

me.enableSensor();

System.println("Activity.getActivityInfo(): HR " + Activity.getActivityInfo().currentHeartRate);

Sensor.unregisterSensorDataListener();

me.setSensorListener(method(:onUpdate));

System.println("onUpdate Listener REGISTERED");

var options = {

:period => SamplePeriodSeconds,

:accelerometer => {

:enabled => true, // Enable the accelerometer

:sampleRate => 25, // 25 samples

:includePower => false, // Requests that the power Array be computed

:includePitch => false, // Requests that the pitch Array be computed

:includeRoll => false // Requests that the roll Array be computed

:heartBeatIntervals => {

:enabled => true

}

};

Sensor.registerSensorDataListener(method(:onSensorData), options);

}

I also noticed that, when the listener doesn't seem to be registered, the HR value is actually available — the line

System.println("Activity.getActivityInfo(): HR " + Activity.getActivityInfo().currentHeartRate);

returns a valid value. This makes it clear that the onSensorData() listener is not being triggered. Otherwise, with the defined :period, it should be automatically called whenever new data is available, correct?

From my point of view, it seems that in some cases, right after the device boots, the registration of the listener for reading and managing sensor data simply fails silently — which in turn causes the application to malfunction. And based on what I’ve experienced so far, the only solution seems to be performing several power cycles until the problem eventually goes away — which is clearly not ideal.
That’s why I’d really like to find an alternative solution, if possible.

Please let me know if you have any ideas or recommendations.