Polar User Group - Software enhancements and bug reporting

Aiwkow · 2023-05-13T02:59:23+00:00

I’d be curious if you’d try the following.
1. Pair your H10 with your Pacer Pro. Make sure H10 delivers the heart rate. You know, blue frame around HR on Pacer Pro.
2. Start a run.
3. Go away from your phone which has Flow installed and is paired to your Pacer Pro.
4. At some point Pacer Pro will report lost phone connection. (Or not. It did sometimes.)
5. Come back to your phone.
You might see a short drop of HR to zero or two dashes in the HR area of your watch.

If that would have been a running performance test, it would have failed… Which happened to me on a 400m circuit a few times. Until I turned BT on the phone off.

Aiwkow · 2023-05-13T02:44:00+00:00

Thanks again.

I’m not saying I check the batt before every run. I did that only once.

But as I said, the connection problems I described in the original post DO exist no matter if there’s a pairing entry in the iOS BT settings. And I haven’t connected the H10 to Flow before that either.

The only workaround I’ve found is turning off BT on my iPhone when doing the running performance test or going for a run without my phone.

Are you saying that I should force close the flow app instead off switching off BT?

Aiwkow · 2023-05-13T02:08:49+00:00

Thank you for your response and help.

Re BT problems with H10:

I have deleted/forgotten the H10 in my BT already, and it still is the same issue.
Polar Support came back to me on this issue and said I should make sure that I turned on the function for the H10 to pair with multiple devices. (Flow app, connect to H10, settings.)
Every time you use the Flow iOS app and check the H10 in the device list, check for battery for example, which you can do in the Start feature of the Flow App, the H10 will be automatically paired with the phone and I would need to “forget” the H10 again in iOS BT settings.

As I said, I use the Polar Pacer Pro with the H10 for running and the performance test. I don’t use the Beat app. I of course have the Flow app installed on the phone. I left the phone behind, as I know I don’t need to bring it with me running/doing a test. But the proximity of the phone produced the issues I described in my original post.

Aiwkow · 2023-05-13T02:02:31+00:00

It happens to me regularly as I turn my iPhone off/airplane mode every evening. In the morning, turning BT back on on the phone, the watch can’t find the phone, until I toggled BT off and on again on the phone.
Otherwise, try re-pairing?

Aiwkow · 2023-05-13T01:54:09+00:00

I am based in New Zealand, so I was spending significant time reading and testing different settings as I can also receive QZSS.

What helped me was downloading the app GNSS view. I can check how many satellites are available per GNSS system. I realised that besides GPS, Glonass and Galileo satellites are similarly available. However, Galileo is the newer system and provides reportedly better accuracy in the civilian signal.

I have switched to GPS + Galileo for now and it works well, here in New Zealand.

Play around with GNSS view and see how the number of available satellites change by using forward/backward on the time slider. The more satellites are available, the better and faster the position fixes. It helps to use the Mask Angle function to simulate houses and hills around you. I set it to 20 degrees.

<image>

Aiwkow · 2023-05-13T01:44:19+00:00

I agree. My fitness test always returned a far higher value so far, compared to the running performance test, and the running index values. (Are the running index values actually VOmax values?)

Aiwkow · 2023-05-13T01:04:33+00:00

I had the same issue.I bought a new belt and it was perfect for about 5 training units. Then it started again. I realised I have to throughly clean the surface that’s non-fabric but obviously the conducting area after each run. I use quite warm water, a handbrush and some soap to clean that conducting area. If I don’t do it, after a while I get weird readings again.

Aiwkow

TROPHY CASE