10-11-2020 10:08
10-11-2020 10:08
I've noticed that the Sense usually doesn't display notifications from Google Maps correctly when paired with an iPhone. If there are no notifications from Google Maps, then any new notification will appear on the watch correctly. However if there is already a notification from Google Maps in the notification centre on the phone, and a new notification comes in, then the new notification is not pulled to the watch. The watch keeps displaying the old notification indefinitely, no matter how many new notifications arrive. As you can imagine this makes using my watch for walking directions a bit difficult!*
I suspect that what's happening is that Google Maps is not actually generating a new notification each time - it's using one notification and modifying it with new information. Presumably the Fitbit app only checks for new notifications, not modified ones. However it should be possible for the Fitbit to detect the change and pass the updated notification to the watch, assuming it's using ANCS.
*There is a work-around of manually deleting the notification after looking at it but that is not exactly convenient.
10-11-2020 20:35
10-11-2020 20:35
What kind of notifications does Google maps send?
10-12-2020 00:19
10-12-2020 00:19
In this case it’s the notifications for navigation directions.
10-12-2020 00:25
10-12-2020 00:25
I didn't even realise Google Maps would send notifications to the Sense when navigating. I tried it the other day and didn't receive anything during my 30 minute walk. Have notifications for maps turned on in the Fitbit app.
I used to get directions on Android Wear smart watches. Android user here by the way.
10-12-2020 10:35
10-12-2020 10:35
Ah, this is just with an iPhone. I wonder if Google Maps doesn't use notifications for the directions on Android. (Apple Maps doesn't use notifications for the directions on the iPhone!)