Google Maps doesn't update location in real time on Versa 4

[InfiniteSleep]

I wonder if any of my settings need to change? Location, Bluetooth, Google Maps and Fitbit apps are all turned on on my phone (OnePlus 11). The app on Versa 4 auto starts, but then it does not update turn by turn directions as I walk the path. Background data usage for the Fitbit app is on on my phone. Is there a fix?

[LokeAa]

You have set battery to "Not optimize" for Fitbit App? 

[InfiniteSleep]

The Fitbit app was set to optimize battery usage. After changing the setting to "not optimize," I continue to have the same issue. 

I would appreciate any other suggestions. Thank you.

[LokeAa]

It must be permission related. The app for Sense has its own permission settings. Go to the gallery in the Fitbit app. Scroll to "Maps" Tap the "Sense 2" tab - Scroll down to "Google Maps" Tap "Permissions", Toggle "Select all" to "On"

[InfiniteSleep]

Thank you, @LokeAa . But all permissions are granted to share with Google Maps already, so that's not the fix.

[LokeAa]

@InfiniteSleep are you sure we are talking about same settings? Google Maps permissions must be granted both on your phone AND your Fitbit. I am talking about the latter.. Looks like this:

[Triletics]

@InfiniteSleep what do you mean by "real-time"? Does it update late or not at all? Do you see any directions? I'm asking because I know one case that could reproduce the issue. If you use Always-On display it may not update instantly (I experienced that with Sense 2) but when I woke up watch (tilting or tapping) then it refreshed. Is it a possibility that you look at directions in Always-On mode?

[InfiniteSleep]

@TrileticsAlways on Display is off.  The watch starts giving directions, sometimes it updates one or two turns but usually not, then it freezes without any updates.

[Triletics]

Ok, so it's neither permissions (because then you'd not get into any navigation) nor AOD. The way app works is through getting GM notifications from the phone so could be something may be not right there. Make sure the power saving mode (for the phone or just for phone GM app) is off. Reset BT connection (off/on), reboot phone and watch (probably you already did that). Maybe do all the pairing again. Make sure nothing CPU heavy runs in the background on your phone either (try to close everything but maps). Unfortunately, I don't have many more ideas. I would also tried to test it with another phone just to have an idea where source of problem may be.

[InfiniteSleep]

Thanks everyone and also to Fitbit support. The fix was to restart my Versa 4. After the restart, Google Maps worked fine on my tracker.