I checked that. No permissions are denied. It can use location whenever I use the app. I don’t see a way to allow it “all the time”, but since the app pretty much runs 24/7 and clearly was running at this point, I can’t see that that is a real difference.
Hey there @Makoti - really sorry to hear about this, definitely sounds like a headache. Let’s get to the bottom of it so you can enjoy your hike in peace, and see all your data after.
Since you mentioned HR is showing as “disabled” I want to test your connection. Mind following these steps to set up a fresh Bluetooth bond? Sometimes things get funky with any Bluetooth electronics so a little reset goes a long ways.
Force-close the WHOOP App.
Forget the sensor from Bluetooth settings of any phone/device that may be connected.
Turn the phone off for about 30 seconds to one minute and turn the phone back on.
Note: This step seems inconsequential, but it’s crazy how often turning on/off your phone helps in these sorts of situations with all kinds of app glitches. Highly recommend.
Put the sensor into pairing mode, re-open the app and pair within the WHOOP App.
BTW - here are those steps in more detail if needed.
Once you’ve done that - do me a favor and hit the “Health” tab from the bottom navbar of the app. Do you see your Heart Rate tracking live at the top? That tells us you’re connected.
Now let’s tackle the GPS. It’s worth noting that it does require a good wireless connection since it depends on your phone. If you aren’t getting bars and your phone’s GPS isn’t in great shape on its own, GPS data may be limited. Since you mentioned that it worked with Strava, I’m a bit less suspicious of this but something to keep in mind.
Here’s what I want to try: Go back to Settings, and try turning off “Battery Optimization” if you see that it’s on. If it was enabled, that might just do the trick for us.
Alright - I know that’s quite a lot but give this a shot when you can and let us know if it helps. If you still notice an issue, could you please shoot us a quick email at support@whoop.com? It might be that there’s something deeper going on and that’ll help us take a better look so we can get you all squared away.
I am experiencing this same issue with my Whoop 4.0 and Android (Pixel 9 Pro). This issue started a few weeks ago and happens inconsistently. I tried tracking run exercises the other day and the GPS/HR data did not track for some of those runs, but did track for others. I will note that after I hit “Start Activity” and I’m brought to the running page, but before actually starting running, my Heartrate shows up and my location is correct on the map. Then once I actually start tracking, either everything will work as usual or I will get the HR Disabled error and zero map tracking.
I have tried (1) restarting my phone, (2) deleting and reinstalling the Whoop app, (3) switching to a brand new Whoop 4.0 sensor, and (4) disabling and re-enabling location permissions. There are no battery saver or optimizer features turned on.
Well, I’ve tried it a few times since, without doing anything at all to fix it, and it works…usually. It is apparently intermittent. It works with both cycling and rucking, and then will work for one but not the other. HR is showing at the top when I go to the Health tab.
Not sure if it is related, but when this started, my Daily Journal stopped opening right after I stopped my sleep recording. It had always opened right after, then it just stopped. Now, it is back to opening after stopping my sleep. A bug that got fixed? A small update? I’m not sure, but as of this morning, my HR shows, my map records, and my journal opens. If any of that changes, I’ll let you know. Again, I didn’t DO anything to change a setting. All the ones yo mentioned to check were already set correctly.
And again, it isn’t working. Worked fine yesterday. Created a map, and had HR. Today, opened the app, chose Map the route, started recording, finished to no map and disabled HR. HR does show in health tab. All info appears to have recorded, other than the map.
Hi @Makoti and @mtf612, happy Friday. I’m really sorry to hear about the issues you’re having here.
@Makoti → I noticed that you have an active support case with us over email, so I’ve escalated that with a manager so we can get to the bottom of whatever is going on. The last thing we want is for you to go through any repeat steps you’ve already tried!
@mtf612 → I’ve gone ahead and flagged this to our support team, and one of my colleagues will reach out to you via email ASAP to get you squared away. Please keep a look out on your inbox!
Thank you. I’ve gotten a couple of emails, and although I haven’t got this squared away yet, I am pleased with the responses I’ve gotten. Thanks again.
I’m also experiencing the same issues and have been unable to restore functionality via the aforementioned steps. Any help would be greatly appreciated as the device is much less useful now.
Hi @m3ghe, thanks for the note. I just took the liberty of filing a ticket for you so that a member of the team can reach out and be in touch to help. They can look at the diagnostics of your specific device and see if its a connectivity issue or another issue. Stay tuned!
Please keep a look out on your inbox!