ErgData Testing With Samsung Galaxy A51

[mlyon]

I'm the firmware developer for the Performance Monitors. I'm looking for someone who uses ErgData with a Samsung Galaxy A51 phone. I would like them to update to the current public firmware release v169, and confirm that connecting to the PM5 and completing a workout goes as expected.

Update me on your findings.

I appreciate the help.

[CJOttawa]

I'm the firmware developer for the Performance Monitors. I'm looking for someone who uses ErgData with a Samsung Galaxy A51 phone. I would like them to update to the current public firmware release v169, and confirm that connecting to the PM5 and completing a workout goes as expected.

Update me on your findings.

I appreciate the help.

Does it need to be an A51? I have an A11 I could try.

[winniewinser]

I'm the firmware developer for the Performance Monitors. I'm looking for someone who uses ErgData with a Samsung Galaxy A51 phone. I would like them to update to the current public firmware release v169, and confirm that connecting to the PM5 and completing a workout goes as expected.

Update me on your findings.

I appreciate the help.

Is the latest release stable? I've read a few things where is has hung and caused issues?

My wife has an A51 but I neither wanted to brick that or the PM5

[mlyon]

Yes, it needs to be an A51 since this has a newer Bluetooth stack implementation (v5.x versus v4.2). We have one report from an A51 owner saying he is unable to connect to the PM5 v169 firmware where he was able to connect to v168.

We have many other Android and iOS phone users that haven't experienced any issues with v169. On some Android phones clearing the Bluetooth phone data has been required because we introduced some additional Bluetooth information for future Concept2 mobile apps. The instructions are simple:

1. Go to Settings
2. Select “Apps”
3. Display “System Apps” (you may need to either swipe left/right or choose from the menu in the top right corner...3 vertical dots)
4. Select “Bluetooth” from the list of applications
5. Select “Storage”
6. Select “Clear Data”
7. Go Back (or some phones may require restarting, but try it first before doing this)

If necessary, I can provide access to v168 firmware in the unlikely event you experience issues with v169.

Thanks.

[mlyon]

I now also have a report from someone with a Samsung Galaxy Note 9 have troubled completing the connection to ErgData. Can anyone verify that they have success with this device?

[Carl Watts]

Strange I'm running the even older Samsung Galaxy A3(2017) and no issues whatsoever.

It would be great if Concept 2 could make a list of phones that DO work with ErgData with no problems because when I replace my current phone it would be a consideration because of how much I use ErgData.

Probably wouldn't go as high as the A51 when the A21s outperforms my current A3 in every way.

[CJOttawa]

Strange I'm running the even older Samsung Galaxy A3(2017) and no issues whatsoever.

It would be great if Concept 2 could make a list of phones that DO work with ErgData with no problems because when I replace my current phone it would be a consideration because of how much I use ErgData.

Probably wouldn't go as high as the A51 when the A21s outperforms my current A3 in every way.

We could crowd-source that here, if there isn't a post for it already. Maybe a sticky in the "Ergdata, Online Racing, Rowpro & RowIt" section?

FWIW, I've had no problems with any app on a Galaxy S7, Google Pixel 2XL, or Pixel 4, via BTLE or wired (USB-OTG as well as a powered USB-C hub) connection.

A cheap, used Pixel XL or 2XL makes a good dedicated erg screen. My 2XL lives on the erg 24/7, solely populated with erg-related apps.

[Citroen]

It would be great if Concept 2 could make a list of phones that DO work with ErgData with no problems

This isn't useful. A list of currently broken phones and an option to beta test Ergdata is better. Which is exactly how it works today as everyone can report a bug to info@concept2.com.

You can never maintain a list of working phones when a new phone is launched every day. Concept2 are not a cellphone company, how could they possibly test every unit in every variation in every territory?

[mlyon]

To be clear, prior to the v169 release, to my knowledge, all Android phones were compatible with ErgData. In the v169 release there are several additional Bluetooth characteristics which changed the ordering compared to any previous connection the phone had made. This ordering is "cached" by the phone to shorten the connection process on succeeding connections. Recognizing that we added these characteristics, we also added a "service changed" characteristic which is supposed to force the phone to refresh its cached ordering. Apparently, not all Bluetooth implementations comply with the Bluetooth specification (not surprising). In response to customer reports, we have provided the following instructions to clear the Bluetooth cache:

Go to Settings (on your phone)
Select 'Apps'
Select 'System Apps' (you may need to choose from the menu in the top right corner)
Select 'Bluetooth' from the list of applications
Select 'Storage'
Select 'Clear Data'
Go Back (some phones may require restarting)

For most Android phones this has not been necessary, but for the few this solution has worked as expected. The customer with an A51 and the customer with a Note 9 have not had success.

[Carl Watts]

Thanks for the clarification.

I will therefore stick with V168 for the time being with my older phone.

As Samsung and Apple have over 75% market share in the USA and most over western countries a compatible phone list wouldn't be that long. If you think it's still to long then a list of the current phones that are a problem would be great so we can avoid buying one.

[mlyon]

As previously stated, the Samsung Galaxy A51 and the Samsung Note 9 (both Android phones) are the only two phones so far that have not worked with v169. I was able to provide a downgrade for those customers to revert back to v168 until we can figure out why. No iPhone users have experienced any difficulty.

[neil262]

I've had no issues with my Galaxy note 10+.

[castlewalls]

I had the same problem with my Galaxy S8.
problem is now solved.

My sequence.
deleted the Bluetooth data per the noted work around. no phone reboot.
same problem.
rebooted the phone.
same problem.
unpaired the PM5. no phone reboot.
problem solved.

i was surprised I was still paired after I did the Bluetooth data purge, but i was just assuming the pair data was part of what would get purged.

[mlyon]

Updated instructions for Android phones experiencing difficult connecting with ErgData to PM5 v169:

1. Go to Settings (on your phone)
2. Select Connections
3. Turn Bluetooth off
4. Return to Settings
5. Select 'Apps'
6. Select 'System Apps' (you may need to choose from the menu in the top right corner)
7. Select 'Bluetooth' from the list of applications
8. Select 'Storage'
9. Select 'Clear Data'
10. Go Back
11. Restart the phone
12. Go to Settings (on your phone)
13. Select Connections
14. Turn Bluetooth on

Restart the Ergdata app and attempt to connect again

If the above fails to resolve the connection issue:

1. Close the ErgData app
2. Put the PM5 into Connect screen
3. Use the Bluetooth phone settings to pair with the PM5
4. Unpair the PM5 from my Bluetooth phone settings

Restart the Ergdata app and attempt to connect again

Apparently some phones don't clear the Bluetooth data as expected, and the pairing/unpairing process does.

[bepah]

I have a Samsung Galaxy 9+ that ran well on the ergdata 168 version.

I have tried all of the suggestions to make it connect. It detects the PMS but will not go any further and immediate sends a message to connect the PM5 once again.

I am wondering if there are any other solutions.

For the record, the heart monitor I use does work. When I do not enable it, I get same result trying to connect the ergdata app to the PM5.

Updating...........the key to making it work is the physical unpairing. If you do not actually unpair, it seems to 'remember' the connection. Doing the unpair was the key.

Many thanks,

John Case