PM4 Ergdata Connection to Android

[MPx]

Does anyone have a link to the old version of the app that I can use with my PM4?

If no one has a link Jonathan try emailing C2 direct on info at concept2.com - they're usually very helpful and will answer in 2 or 3 days.

[Sakly]

Does anyone have a link to the old version of the app that I can use with my PM4?

Found this:

It seems Concept2 have removed ErgData For PM3 PM4 from the app stores.
The Android version ErgData For PM3 PM4 (version 1.01) can still be downloaded from https://apkpure.com/ergdata-for-pm3-pm4 ... 4/versions

To install, download it on your device (or copy it to device), open a files app, then click on the .apk file.
Android may ask for approval to install an "unknown" application, as it is not coming from the regular app store.
You may have to enable "install unknown applications" in Developer Options.
You may have to enable Developer Options in Settings/About/Click multiple (7) times on the build version.
(See YouTube videos on Android Developer Options)

In this thread:
viewtopic.php?f=8&t=207463

[Tsnor]

Does anyone have a link to the old version of the app that I can use with my PM4?

Found this:

It seems Concept2 have removed ErgData For PM3 PM4 from the app stores.
The Android version ErgData For PM3 PM4 (version 1.01) can still be downloaded from https://apkpure.com/ergdata-for-pm3-pm4 ... 4/versions

To install, download it on your device (or copy it to device), open a files app, then click on the .apk file.
Android may ask for approval to install an "unknown" application, as it is not coming from the regular app store.
You may have to enable "install unknown applications" in Developer Options.
You may have to enable Developer Options in Settings/About/Click multiple (7) times on the build version.
(See YouTube videos on Android Developer Options)

In this thread:
viewtopic.php?f=8&t=207463

just be aware you may hit problems. I was seeing bad stroke counts on C2 log with the older ergdata. C2 support said <my translation> yep, broken, no fix. you gotta move forward if you want accurate data. To be clear honest accurate support like C2 is the best support.

[Sakly]

Does anyone have a link to the old version of the app that I can use with my PM4?

Found this:

It seems Concept2 have removed ErgData For PM3 PM4 from the app stores.
The Android version ErgData For PM3 PM4 (version 1.01) can still be downloaded from https://apkpure.com/ergdata-for-pm3-pm4 ... 4/versions

To install, download it on your device (or copy it to device), open a files app, then click on the .apk file.
Android may ask for approval to install an "unknown" application, as it is not coming from the regular app store.
You may have to enable "install unknown applications" in Developer Options.
You may have to enable Developer Options in Settings/About/Click multiple (7) times on the build version.
(See YouTube videos on Android Developer Options)

In this thread:
viewtopic.php?f=8&t=207463

just be aware you may hit problems. I was seeing bad stroke counts on C2 log with the older ergdata. C2 support said <my translation> yep, broken, no fix. you gotta move forward if you want accurate data. To be clear honest accurate support like C2 is the best support.

I saw bad stroke counts with new Ergata as well, several times. Informed support about this, but got no feedback with a reason for it.
I cannot remember exactly for what kind of sessions I saw this, but very sure it was for timed sessions as well as distance based sessions. In every occurrence the sessions were long, at least 60mins, so stroke count minimum 4 digits long.

As I moved to ergzone several weeks ago, due to some instabilities in BT connection using ergdata, I don't know if that still happens.
After the weeks of ergzone usage, I still like ergdata more, but a stable connection is the basic feature needed.

[Tsnor]

I saw bad stroke counts with new Ergata as well, several times. Informed support about this, but got no feedback with a reason for it.
I cannot remember exactly for what kind of sessions I saw this, but very sure it was for timed sessions as well as distance based sessions. In every occurrence the sessions were long, at least 60mins, so stroke count minimum 4 digits long.

As I moved to ergzone several weeks ago, due to some instabilities in BT connection using ergdata, I don't know if that still happens.
After the weeks of ergzone usage, I still like ergdata more, but a stable connection is the basic feature needed.

this is what I saw (11/28/2023)

Hi,

I've noticed the stroke count is bad in my last three log entries. Bad entries start Nov 23. Entries were good on Nov 22 and prior.

Example below is from Nov 28. A 70 minute "just row" with a stroke rate of 18-20 should give about 1200 to 1400 strokes. That is what ERGDATA displayed during the row. Downloading the CSV data shows 1329 strokes. But my log entry shows 750 strokes.


Agree stability is king. With old ergdata and old kindle bluetooth stability was bad, same hardware connected via USB OTG cable was perfect. After migration to new ergdata and phone rather than kindle bluetooth has been stable with just a few initial connection hiccups. Good luck with ergzone.

[Sakly]

I saw bad stroke counts with new Ergata as well, several times. Informed support about this, but got no feedback with a reason for it.
I cannot remember exactly for what kind of sessions I saw this, but very sure it was for timed sessions as well as distance based sessions. In every occurrence the sessions were long, at least 60mins, so stroke count minimum 4 digits long.

As I moved to ergzone several weeks ago, due to some instabilities in BT connection using ergdata, I don't know if that still happens.
After the weeks of ergzone usage, I still like ergdata more, but a stable connection is the basic feature needed.

this is what I saw (11/28/2023)

Hi,

I've noticed the stroke count is bad in my last three log entries. Bad entries start Nov 23. Entries were good on Nov 22 and prior.

Example below is from Nov 28. A 70 minute "just row" with a stroke rate of 18-20 should give about 1200 to 1400 strokes. That is what ERGDATA displayed during the row. Downloading the CSV data shows 1329 strokes. But my log entry shows 750 strokes.


Agree stability is king. With old ergdata and old kindle bluetooth stability was bad, same hardware connected via USB OTG cable was perfect. After migration to new ergdata and phone rather than kindle bluetooth has been stable with just a few initial connection hiccups. Good luck with ergzone.

Ah yes, I remember I had this issue with just row as well.
I have no data/comparison for the old ergdata version and BT <-> cable, as I used it directly with a cable and OTG adapter. I recognized it only with new Ergata version.

I don't mind about the counter reported in the workout, but I do mind about the overall stroke data, heartrate. And even if ergdata reconnects during the row, this data is lost until the point of reconnect. Another thing is, even if the app reconnects, it only shows white screens, no data anymore, but records them in the background.
It's kind of sad, as I think the ergdata app has a better user interface and data organisation than ergzone. With ergdata I had several connection losses during a HM, with ergzone not a single one since I use it. Same device, same rower, same environment.