jranaraki / steps Goto Github PK

Hi.
I am currently working on porting my current apps to focal. Is it correct that you are not working on this project anymore? If so I could fork the app and republish them on the openstore.
If my assumption is wrong, please comment on my pull request and if possible port the app to focal.
Here are a few instructions how this might work.
Greetings

This is a Halium 9 device. The app doesn't seem to work here. Thank you for your work. Matteo
This is the log with some errors:
Creating a QMirClientScreen now [PERFORMANCE]: Last frame took 46 ms to render. error calling result "An AppArmor policy prevents this sender from sending this message to this recipient; type=\"method_call\", sender=\":1.103\" (uid=32011 pid=7205 comm=\"/usr/lib/qt5/bin/qmlscene qml/Main.qml \") interface=\"com.canonical.libertine.Service.Operations\" member=\"list\" error name=\"(unset)\" requested_reply=\"0\" destination=\"com.canonical.libertine.Service\" (uid=32011 pid=4974 comm=\"/usr/bin/python3 /usr/bin/libertined \")" error calling result "An AppArmor policy prevents this sender from sending this message to this recipient; type=\"method_call\", sender=\":1.103\" (uid=32011 pid=7205 comm=\"/usr/lib/qt5/bin/qmlscene qml/Main.qml \") interface=\"com.canonical.libertine.Service.OperationsMonitor\" member=\"running\" error name=\"(unset)\" requested_reply=\"0\" destination=\"com.canonical.libertine.Service\" (uid=32011 pid=4974 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:///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:///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.

Setup

• Phone: Xiaomi Mi A2
• OS: Ubuntu Touch 16.04 OTA-19/stable
• Steps version: 1.0.8 (updating to 1.0.9 as I type ;-) )

Symptoms

On two occasions already, I started the Steps app at the beginning of a walk and put the phone in my pocket. By the time I returned to the car, the phone wouldn't let me unlock it. Pushing on the power button turned the screen on and off, but sliding horizontally to unlock produced no effect. Sliding down from the top also got no reaction.

In both cases, I ended up forcing a restart of the phone, and checking the stats in Steps afterwards, I noticed that it recorded only the first 9 steps in the first case, none at all in the second.

And yes, I did use the "UT Tweak Tool" to prevent app suspension.

By the way, in "UT Tweak Tool", if I open the page for "Steps" and I take the "Hooks" tab, I see the following message:

"Can access the device sensors"

so everything looks fine there.

Data counter reset button, maybe to the right of the step count and distance display.

Hi,

Thanks for this great app! I just wanted to let you know that it works great on the Poco F1 too after disabling app suspension in UT Tweak Tool. So if you want, you could add the Poco F1 to the test case section as well. 🙂

Today I did some tests regarding sensitivity and stride length.

1. the result depends on the kind of walk you are doing: slow/normal walking/strolling, walking quickly.
2. sensitivity and stride length need to be adjusted depending of the type of walk to provide good results

I was using two Xperia X devices and a normal step counter, all kept in the same pocket.
Because I was walking on my own, the walk type was mainly walking quickly. I take the step counter as reference.

Here my results for walking quickly:
sensitivity 7.0 steps counted: 50 % less
sensitivity 7.3 steps counted: almost equal
sensitivity 7.5 steps counted: 25 % more
sensitivity 8.0 steps counted: 25 % more
stride length: short by 50%

Walking slowly/strolling:
sensitivity 7.3 steps counted: 65 % less
sensitivity 7.5 steps counted: 50 % less
sensitivity 8.0 steps counted: 30 % less
sensitivity 8.5 steps counted: 15 % less
stride length: good match

Shopping:
sensitivity 8.5 steps counted: 40 % less
sensitivity 9.0 steps counted: 20 % less

So I think for accurate results we almost need two profiles: slow walking - quick walking.
Normal walking
Your stride calculation is fine. The default value for sensitivity should not be below 8.5, better higher (?).
Quick walking
Stride length needs to be increased. Sensitivity should be about 7.3.

Note: all numbers may depend on where exactly the device is carried. They may also vary depending on the device.

On the Volla, with SuruDark mode, the configurable data are no longer visible (they were in v1).
SuruDark

Ambiance

The change for the range of sensitivity value in this PR does reduce the sensitivity value to a level too low for the app to register any steps at all.
Currently the app is unusable. Either the value should be reverted to a working range or an correcting offset needs to be applied elsewhere.