01-24-2024 13:02
01-24-2024 13:02
My charge 5 broke after only a year (battery problems, as usual), and the only reason I decided to go with the charge 6 again was because of google maps support. I rely on transit and will be going on a trip to many new cities soon and thought that getting metro stop info on my watch would be very handy in areas where phones are stolen out of your hand on transit. I used to use the maps feature with wearOS and thought it was the same. Now I realize that no transit information is sent to the watch. I feel this is false advertising that "maps" is supported when it leaves out key features that many rely on. Hopefully in an update they will add transit support if enough people complain.
01-24-2024 15:21
01-24-2024 15:21
@azurexa what Fitbit offers is totally different and very basic when compared to WearOS counterpart. Fitbit's version is more like "Google Directions" rather than maps and offers only basic features.
06-06-2025 13:38
06-06-2025 13:38
I need to vent my anger too about Fitbit support and the Charge 6 in this forum because navigation with
public transport via Google Maps simply doesn't work.
My phone shows me all the important notifications:
"Turn left, turn right, you are at the station, get on the X train, 5 more stops, etc."
But not a single Fitbit product, including my Charge 6, can display this information - I wonder why.
What is the difference between navigation by car, bike, or walking and this specific combination?