The steps application "freezes" the phone about steps

[petroniusniger]

In the mean time, I've discovered that Steps created log files (thanks to the "Logviewer" app -- well done!). Unfortunately, they don't seem to shed any new light on the issue.

The first version of Steps that I used during a walk and that exhibited the problem was 1.0.7, but either that one didn't create any log, or it has already been removed by 'logrotate'.

I then used v1.0.8 during a second test walk, and a log does exist for that version, but it contains a single line:

Creating a QMirClientScreen now

(also, since the log file does not contain timestamps, I can't even determine whether that message bears any relationship to the test walk in question -- even the log file last modification time can't help, as it has since been compressed and rotated out by 'logrotate').

Then there is a (slightly longer) log file for v1.0.9, but since I only upgraded to that one today, it doesn't contain any event yet related to any walk. Since it does contain error messages though, I will copy one of each kind below:

[...]
error calling result "An AppArmor policy prevents this sender from sending this message to this recipient; type=\"method_call\", sender=\":1.119\" (uid=32011 pid=12858 comm=\"/usr/lib/qt5/bin/qmlscene qml/Main.qml \") interface=\"com.canonical.libertine.Service.OperationsMonitor\" member=\"result\" error name=\"(unset)\" requested_reply=\"0\" destination=\"com.canonical.libertine.Service\" (uid=32011 pid=5873 comm=\"/usr/bin/python3 /usr/bin/libertined \")"
lastError - no arguments?
file:///usr/lib/aarch64-linux-gnu/qt5/qml/Ubuntu/Components/1.3/ComboButton.qml:398:5: QML Scrollbar: Cannot anchor to an item that isn't a parent or sibling.
[...]
file:///opt/click.ubuntu.com/steps.jranaraki/1.0.9/qml/Setting.qml:227:13: Unable to assign [undefined] to int
[PERFORMANCE]: Last frame took 104 ms to render.
qt.qpa.mirclient: Attempted to deliver an event to a non-existent window, ignoring.
[...]

Suggestion: adding a timestamp to the log entries would make them easier to relate to real-world events, I think.

[petroniusniger]

Further troubleshooting information:
While working around another problem on the phone, I temporarily switched to the dev channel, which installed v763. So I thought it would be interesting to check whether Steps was more stable on the latest development build or not.

Regretfully, I must say that this is not the case. The behaviour is exactly the same as described above.

[jranaraki]

@petroniusniger, could you download the new version and let me know if you still have the issue?

[petroniusniger]

Hello @jranaraki
Many thanks for getting back to me, first of all.
I upgraded "Steps" to the latest released version this morning (v1.1.0).
In the mean time, my phone has been updated to OTA-22.

I just made a quick check of the new "Steps", i.e.:

• I verified that my earlier user settings were still there
• I updated one of them (the age)
• I closed and restarted the app
• checked the settings again
• I then left the app running and pressed on the power button to "lock/sleep" the phone
• I walked for a minute around the house with the phone in my trouser pocket

The good news is that the app no longer "freezes" the phone. I was able to unlock the phone at the end of the test and to interact with the "Steps" app that was still active and responsive.

The bad news is that no step was actually recorded by the app (0 step, 0,0m), although sensitivity is at the highest setting.

With earlier versions, a (random) few steps would typically be recorded before the app froze.

Also, a log has been generated for v1.1.0 of Steps, but its contents looks very similar to the extracts already posted above. I haven't seen anything new or more meaningful (to me at least) there. I can also confirm that "Prevent App Suspension" setting is still active in UT Tweak Tool for Steps.

If there's any extra info / screenshots / etc. that would help, or if you want me to run more specific tests, just let me know.

[petroniusniger]

Further test over the weekend. I wanted to check what happened if I didn't lock/sleep the phone.

Test procedure:

• unlock the phone
• start the"Steps" app
• hold the phone in hand in upright position and let it gently drop on a soft surface (foamy mousepad) in a rhythmical pattern that mimics the walk

Result:

• most "steps" are counted and distance increments accordingly
• some "steps" are not detected

As a conclusion, it's clear that the app can access the phone sensors. The failure of the previous test may have been due to the fact that the "signal" from my steps while walking around the house was not strong enough as the phone was a hip level. I'll try again as soon as possible, carrying the phone in a trouser pocket at thigh level.

[petroniusniger]

Just performed the same test ("simulated walk") but with the phone locked, and no step got registered at all.
Still no freeze, though.

So I guess the problem goes beyond the fine-tuning of the sensitivity.

[jranaraki]

Please update to 1.1.1 as it fixes the sensitivity issue