OK,
So I've been using iSmoothRun for a while now and there are a few things that bug me. Not a deal killer, but it does bother me a bit. Just wondering if anyone else is seeing these things.
I'm running an Nike S2 on wOS4.2.2. iPhone6 on iOS 11.2.x (actually I'm on 11.3 now, but haven't run since updating).
1. When running outdoors, I carry my iPhone with me. I have my AW set as AW + iPhone. Start the run using the start button on the watch. The HR sensor will turn on, but I won't get a good reading for at least a 1/4 mile or so. After that, the HR reading gets more accurate. I've tested the HR reading right before running and it's solid. Not sure what's going on. Also, as soon as I stop the run, the HR sensor turns off, therefore I miss the first 30 seconds of RecoveryHR readings. I have to open an app on the watch that will turn on the HR sensor.
2. When I run outdoors with a HR strap (Polar H7) connected via BT to the AW. Start the run the same as above. Most of the time, the HR readings are instantly accurate. The only problem is that VO2max doesn't get populated when using a HR strap. Usually, the HR strap stays on and RecoveryHR is recorded.
3. When I run on a treadmill, I run in AW only mode. I do this because if I run on the treadmill in AW + iPhone mode, autopause goes nuts and I get a messed up run. However, this messes with the shoe mileage. It'll show up correctly on the iPhone as soon as the run is complete and transferred over to the iPhone, but unless the phone contacts the AW again, I'll lose the miles on that pair of shoes. Usually takes about 5 minutes of messing about on both the AW app and the iPhone app.
That's about it, other than auto-pause taking longer than I'd like to initiate.
So I've been using iSmoothRun for a while now and there are a few things that bug me. Not a deal killer, but it does bother me a bit. Just wondering if anyone else is seeing these things.
I'm running an Nike S2 on wOS4.2.2. iPhone6 on iOS 11.2.x (actually I'm on 11.3 now, but haven't run since updating).
1. When running outdoors, I carry my iPhone with me. I have my AW set as AW + iPhone. Start the run using the start button on the watch. The HR sensor will turn on, but I won't get a good reading for at least a 1/4 mile or so. After that, the HR reading gets more accurate. I've tested the HR reading right before running and it's solid. Not sure what's going on. Also, as soon as I stop the run, the HR sensor turns off, therefore I miss the first 30 seconds of RecoveryHR readings. I have to open an app on the watch that will turn on the HR sensor.
2. When I run outdoors with a HR strap (Polar H7) connected via BT to the AW. Start the run the same as above. Most of the time, the HR readings are instantly accurate. The only problem is that VO2max doesn't get populated when using a HR strap. Usually, the HR strap stays on and RecoveryHR is recorded.
3. When I run on a treadmill, I run in AW only mode. I do this because if I run on the treadmill in AW + iPhone mode, autopause goes nuts and I get a messed up run. However, this messes with the shoe mileage. It'll show up correctly on the iPhone as soon as the run is complete and transferred over to the iPhone, but unless the phone contacts the AW again, I'll lose the miles on that pair of shoes. Usually takes about 5 minutes of messing about on both the AW app and the iPhone app.
That's about it, other than auto-pause taking longer than I'd like to initiate.