Kuri

Rating: 
5
Your rating: None Average: 5 (22 votes)

Kuri is a sport tracking application for Sailfish OS. Kuri means "run" in Esperanto. Funnily it also means "discipline" in Finnish.

Notes:

  • On SFOS 4.5 some user have problems to start or install Kuri. This is related to the deprecation and removal of QtBluetooth. For user which are affected by this issue qtconnectivity-bluetooth from OpenRepos can be installed. A proper fix is not yet available
  • You need to enable the chum repo to resolve the Mapbox GL Native QML dependency for map display
    • download the chum rpm for your architecture
    • install the rpm, e.g. via the file browser
    • install Kuri (if installation still does not work, perform a `devel-su pkcon refresh`)
  • All strings should now be translatable, so please start translating
  • Not everyting from the new Record Page is working, yet
  • With v0.5 the location of the config file and recorded activities changed as preparation for a future Sailjail activation
    • config is now stored in '.config/org.kuri/kuri/kuri.toml'
    • activities are now stored in '.local/share/org.kuri/kuri'
    • activities are migrated on first start, config is not migrated

Kuri takes inspirations from MeeRun, but it will take some time until all of MeeRuns features are implemented.

This application is a fork of Laufhelden by jdrescher. The reason for the fork is that it isn't maintained anymore.

Thanks to translators!

  • Swedish - eson
  • Polish - kormil

License: GPLv3

Source code: https://gitlab.com/elBoberido/kuri

Icons: https://icons8.com

Bugs: https://gitlab.com/elBoberido/kuri/-/issues

Screenshots: 
Application versions: 
AttachmentSizeDate
File harbour-kuri-0.1.0-1.armv7hl.rpm718.17 KB09/03/2020 - 02:21
File harbour-kuri-0.2.0-1.armv7hl.rpm725.91 KB08/04/2020 - 23:19
File harbour-kuri-0.2.1-1.armv7hl.rpm726.74 KB11/04/2020 - 17:50
File harbour-kuri-0.3.0-1.armv7hl.rpm723.05 KB16/04/2020 - 22:55
File harbour-kuri-0.3.1-1.armv7hl.rpm722.58 KB20/07/2020 - 21:56
File harbour-kuri-0.3.1-2.armv7hl.rpm722.74 KB20/07/2020 - 22:32
File harbour-kuri-0.3.2-1.armv7hl.rpm723.26 KB24/07/2020 - 12:52
File harbour-kuri-0.3.3-1.armv7hl.rpm723.66 KB19/10/2020 - 22:58
File harbour-kuri-0.3.4-1.armv7hl.rpm682.89 KB22/05/2021 - 00:04
File harbour-kuri-0.3.4-1.aarch64.rpm697.28 KB22/05/2021 - 00:04
File harbour-kuri-0.3.5-1.armv7hl.rpm732.01 KB22/05/2021 - 20:32
File harbour-kuri-0.3.5-1.aarch64.rpm746.79 KB22/05/2021 - 20:32
File harbour-kuri-0.3.7-1.armv7hl.rpm725.84 KB31/05/2021 - 23:33
File harbour-kuri-0.3.7-1.aarch64.rpm737.19 KB31/05/2021 - 23:33
File harbour-kuri-0.4.0-1.armv7hl.rpm2.14 MB03/07/2021 - 00:15
File harbour-kuri-0.4.0-1.aarch64.rpm484.16 KB03/07/2021 - 00:15
File harbour-kuri-0.4.1-1.armv7hl.rpm2.14 MB04/07/2021 - 21:25
File harbour-kuri-0.4.1-1.aarch64.rpm483.45 KB04/07/2021 - 21:25
File harbour-kuri-0.4.2-1.armv7hl.rpm2.14 MB10/07/2021 - 00:05
File harbour-kuri-0.4.2-1.aarch64.rpm484.21 KB10/07/2021 - 00:05
File harbour-kuri-0.4.3-1.armv7hl.rpm2.14 MB18/07/2021 - 23:14
File harbour-kuri-0.4.3-1.aarch64.rpm483.86 KB18/07/2021 - 23:14
File harbour-kuri-0.4.4-1.armv7hl.rpm2.14 MB18/03/2022 - 23:55
File harbour-kuri-0.4.4-1.aarch64.rpm484.16 KB18/03/2022 - 23:55
File harbour-kuri-0.4.5-1.armv7hl.rpm2.14 MB17/09/2022 - 19:16
File harbour-kuri-0.4.5-1.aarch64.rpm484.2 KB17/09/2022 - 19:16
File harbour-kuri-0.5.0-1.armv7hl.rpm1017.67 KB29/07/2023 - 17:32
File harbour-kuri-0.5.0-1.aarch64.rpm1003.49 KB29/07/2023 - 17:32
File harbour-kuri-0.5.1-1.armv7hl.rpm1018.45 KB01/08/2023 - 17:36
File harbour-kuri-0.5.1-1.aarch64.rpm1003.79 KB01/08/2023 - 17:36
File harbour-kuri-0.5.2-1.armv7hl.rpm1 MB23/08/2023 - 01:44
File harbour-kuri-0.5.2-1.aarch64.rpm1008.75 KB23/08/2023 - 01:44
File harbour-kuri-0.5.3-1.armv7hl.rpm1022.2 KB03/10/2023 - 02:24
File harbour-kuri-0.5.3-1.aarch64.rpm1005.82 KB03/10/2023 - 02:24
Changelog: 

fix strava upload when access token needs refresh

Comments

SKD's picture

My current sailfish version is 4.3.0.15. I just tried starting from terminal, here's the output (the 2 lines actually loop for quite some time at the "..."):

[nemo@XperiaXA2 ~]$ harbour-kuri

[W] unknown:0 - GStreamer; Unable to pause - "file:///home/nemoaudio/hr_toohigh_de_male.wav"

[W] unknown:0 - O2::refresh: No refresh token

[W] unknown:0 - O2::onRefreshError:  QNetworkReply::NetworkError(AuthenticationRequiredError)

[W] unknown:0 - O2::refresh: No refresh token

[W] unknown:0 - O2::onRefreshError:  QNetworkReply::NetworkError(AuthenticationRequiredError)

[W] unknown:0 - O2::refresh: No refresh token

...

[W] unknown:0 - O2::onRefreshError:  QNetworkReply::NetworkError(AuthenticationRequiredError)

Segmentation fault (core dumped)

[nemo@XperiaXA2 ~]$

 

Does this tell you anything? :)

elBoberido's picture

The good news is that kuri 0.5 will use Amber Web Authorization instead of O2, which should fix this. The bad news is that I don't know when it's ready.
I'll have a closer look at this later.

Do you use strava with Laufhelden? If yes, could you log out before starting kuri?
Did you try to rename `~/.config/harbour-kuri/harbour-kuri.conf`? Please don't delete it. If it fixes the problem it will help to fix the bug.

SKD's picture

Thank you for looking into it! I tried disabling strava in Laufhelden --> no effect. I tried to rename ~/Laufhelden --> no effect.

But the thing with the config actually worked and Kuri did start up :). This is the content of the config file:

 

[recordsettings]
thresholds="Schwellwerte Aus,true,false,0,false,0,false,0,false,0|Wettkampf 10km,false,true,183,false,133,true,5,true,4.5|Training GA 1,false,true,141,true,130,false,6.2,false,3.2"
workoutType=biking

 

elBoberido's picture

Was that the only content?
Unfortunately I cannot reproduce the issue but I'm already on 4.4.

Glad it works for you now

silta's picture

Hi @elBoberido,

 

unfortunately Kuri doesn't work under SFOS 4.4.0.58 EA. Maybe because of the Sailjail limitations.

It would be nice if you could provide an update.

 

Thanks in advance.

 

elBoberido's picture

Will publish an quick fix soon. If you have similar problems with other apps, you can disable the sandboxing by editing the destop file under /usr/share/applications and add

[X-Sailjail]
Sandboxing=Disabled
silta's picture

Thank you for the update. Kuri is working now.

Have a nice day.

nas's picture

Hi @elBoberido ,

Do you know if  Garmin HRM-Pro (https://www.garmin.com/en-US/p/682155) which has bluetooth can work with Kuri?

Thanks

elBoberido's picture

Sorry, I can't tell you if that device works. Maybe you can ask in https://forum.sailfish.org whether someone uses that device

Alex's picture

Hey @elBoberido,
upgrading SailfishOS to 4.3.0.xx will remove Kuri because it has a dependency to a mapboxgl-qml version that requires OpenSSL 1.0. Could you please provide an updated version of Kuri (that uses the latest version of mapboxgl-qml)? :)

elBoberido's picture

That's weird. I also updated to the 4.3 EA release but did not have the problem you described. Do you have the latest mapboxgl-qml installed? It is not directly provided by Kuri but must be installed and updated manually from rinigus repo.

Alex's picture

Well I was able to install Kuri again after updating mapboxgl-qml, thanks. :)

lxmx's picture

Getting a "Could not load the page" message when trying to start a workout on an Xperia X.

elBoberido's picture

I guess this is due to a missing mapboxgl-qml dependency. Can you try to install it manually?

Juanro49's picture

It's work fine, but I can't login to strava

elBoberido's picture

What error do you get?

pasik2's picture

Can you add 64 bit support for Sony Xperia 10 II? Thanks!

elBoberido's picture

Done. Please report if there are issues.

inte's picture

It is now always crashing when trying to start. I used it some time ago and connected to strava i think. Thats all... I could try after deleting my data if that helps?

elBoberido's picture

Sorry for not replying, was hit by real life. If you still have the data, please don't delete it but just move them to a different location. It might help debugging if it's related to the data.

amaretzek's picture

On my X, SFOS3, it crashed on startup after some "uptime". In this situation I have rebooted the phone. Didn't investigate, has a taste of "out of memory"...

elBoberido's picture

I also noticed that it's getting really slow after a few hours recording. I guess I have to refactor the recording a little bit.

SKD's picture

I unfortunately have the same problem since I started using my XA2 (sometime last summer). Whenever I try to start the app the icon appears for some time and then it's just gone.

elBoberido's picture

I also had this from time to time. It's running in the background and you can kill it with e.g. Lighthouse.

Recently I found how to reproduce it, so I hope to fix it soon.

inte's picture

I get a segfault error on sfos4 while Laufhelden still works.
Don't know if its your modifications or the strava account I added...

D] unknown:0 - O0BaseAuth::setLinked: false
[D] unknown:0 - O0BaseAuth::linked: Yes
[D] unknown:0 - O2::refresh: Token: ... ""
[W] unknown:0 - O2::refresh: No refresh token
[W] unknown:0 - O2::onRefreshError: QNetworkReply::NetworkError(AuthenticationRequiredError)
[D] unknown:0 - O2::unlink
[D] unknown:0 - O0BaseAuth::setLinked: false
[D] unknown:0 - O0BaseAuth::linked: Yes
Speicherzugriffsfehler (core dumped)

elBoberido's picture

Do you have more information, like what you did before the crash? Is it reproducible?

DrYak's picture

Hello! Thanks for picking up the relay baton with this sports tracker.

I have troubles adding my BLE (random address type) HRM device to Kuri:

  • if I use the Sailfish OS Bluetooth settings and hit search device the device does show up
  • if I use the Kuri settings, preselect the correct type (BLE random address) and hit scan, the devices does not show up.
  • If I copy-paste the device config line (hrmdevice="DF:81:53:0E:F4:81,HRM508NE-0079890")  from Laufhelden's to Kuri's config file, Kuri can connect to it and receive heartrate.
elBoberido's picture

Can you still reproduce this with v0.4.0?

elBoberido's picture

I'm currently not able to fix the Bluetooth issues by myself, since I don't have an appropriate device. I will happily accecpt any patch for the issue, though. Sorry that I cannot do more at the moment.

nemishkor's picture

Looks like connection to pebble works

Pages