search

jonasoreland / runnerup

A open source run tracker
GNU General Public License v3.0
742 stars 274 forks source link

using step sensor #668

Open humarf opened 6 years ago

humarf commented 6 years ago

I am new to RunnerUp and use it for about 4 weeks now - it's great.

In RunnerUp settings I found that the step sensor of the phone can be used. I tried this and in the work out files step information is included when performing simple or advanced workout. It is not included when performing interval training. Is there something I can do about it? Is there a setting I did not see so far?

Thanks and best regards humarf

gerhardol commented 6 years ago

The cadence should be recorded in every mode, there is no specific setting.

humarf commented 6 years ago

Thanks. I guess it's a bug then. Can someone confirm, please?

gerhardol commented 6 years ago

I can see this too. There should be nothing special about Intervals

step sensor cadence is not activated for Biking

gerhardol commented 6 years ago

I tested to quickly (probably without moving the phone). Cadence is recorded and exported in the same way in all modes. I see no difference when testing.

humarf commented 6 years ago

I can test it again. Maybe it's a version problem(?) I use RunnerUp from Google Play store. If there is a newer version available somewhere else I can try that.

gerhardol commented 6 years ago

A 2.0 alpha can be built from the repo, but there are no precompiled packages yet.

humarf commented 6 years ago

Did you do your checks with v2.0 or with v1.58?

gerhardol commented 6 years ago

I think I tested with 1.58, but 2.0 definitely works

humarf commented 6 years ago

Sorry that this took so long. I have tested it again. Here are snippets from standard training:

`<?xml version="1.0" encoding="UTF-8"?>

2018-09-30T12:22:03Z 317 1002.0 0 Active Manual 52.43844 13.68282 -5 0.0 52.438446 13.682834 -6 1.2430383 62 52.438465 13.682858 -6 3.953755 73 ` and from interval training: ` 2018-10-02T05:27:19Z 201 543.0 0 Active Manual 52.43838 13.682603 -11 0.0 52.438393 13.68263 -11 2.217946 52.43841 13.682663 -11 5.3255434 52.438435 13.6827 -12 8.915002 52.43847 13.682776 -12 15.358157 ` Cadence is missing in interval training file. Is there anything you could do about it?
gerhardol commented 6 years ago

This is working in master. I do not know a reason for it to not work in latest official, but it will be available in next release.

humarf commented 6 years ago

Ok, will wait for next release.

humarf commented 5 years ago

I have seen there is 2.0 available here. I installed the app and now cadence is recorded in standard training and in interval mode but only as long as the display is active. Maybe this is a phone related issue but I have checked all battery saving options and disabled everything for runnerUp. With runnerup 1.x version cadence was recorded when display switched off.

Do you have any advice what I could do?

gerhardol commented 5 years ago

What phone and what Android?

The cadence counter has some tweaks for the smoothing, but not much else what I can recall. The Android target version is updated to Pie/9.0, that has some changes to background but from what I know this should work the same in RU1.x

humarf commented 5 years ago

It's a Huawei p20lite running Android 8.0.

gerhardol commented 5 years ago

Huawei has a very customized version of Android. Have you tried the suggestions here? https://dontkillmyapp.com/huawei

Have you tried 1.x recently, i.e. this is not caused by an update?

I cannot see how this is caused by changes. When I look around I find no hints for developers, only for users.

humarf commented 5 years ago

I know that apps running in background on a huawei is a mess. I made similar customizing for runnerUp 1.x and 2.x. Today I cross checked doing a training with new version directly followed by a training with old version. In 1.x cadence is reported properly while in 2.x it's not. Maybe you could double check for any changes in 2.x code base as well?

gerhardol commented 5 years ago

There are changes to smoothing, pause handling etc. However the registration is the same and cannot be done in many ways. As I wrote earlier, the only I can think of is targeting Android 9 instead of Android 7. The support libraries etc are updated. At least Android 8 is required to publish in Play (Android 9 will be in the fall).

To go forward, it seems like debugging on the device. Can you debug? At least a logcat could help.

humarf commented 5 years ago

I am happy to help. Just tell me what to do to retrieve the logs or whatever is needed.

gerhardol commented 5 years ago

The first step is getting a logcat when the problem occurs. I do not what knowledge you have, where to start. One guide here: https://logmatic.io/blog/a-how-to-guide-to-debugging-with-android-logcat/

The log should contain the complete sequence from where RU is started to where where RU is stopped. If you do not have GPS coverage at the PC, you may need to increase the log buffer (should be in the Developers settings, close to where adb is enabled.

The log may contain sensitive information like passwords (I have not really seen it), not from RU though. You may want to share it privately.

The second styep is to debug with Android Studio.