This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Bug - Connected GPS Stopped Working with GCM Android v4.32 Update

The connected GPS feature stopped functioning when I updated the Garmin Connect Mobile for Android app to the update pushed yesterday, June 24th, 2020. My Vivosmart 4 displays the "Waiting for GPS" message until it times out with the X icon and "Unable to connect to phone GPS" message when I attempt to use Connected GPS. Data syncing to my Vivosmart 4 works perfectly, and the app displays realtime heart rate info, so the Bluetooth connection to the watch seems to be working fine. My phone gives me the system notification from Connect Mobile "Sending GPS to Vivosmart 4" when I select Connected GPS on the watch, but it does not display the location/GPS icon in the Android task bar indicating that location services on the phone are being used, and the list of recent location services requests in the phone's settings does not show any location requests from Connect Mobile. My watch is still displaying weather data.

ETA: Garmin Connect Mobile shows a version number of 4.32, nothing listed under Build Number (it's in the post title, but I thought I should add it to the post body).

The failure point appears to be Connect Mobile actually polling the phone's location service: the watch is telling the app to pass through the GPS info, as indicated by the notification, but the app is not actually requesting the data from the phone's location service, as demonstrated by the phone not showing the GPS/location icon and not logging a location services request from Connect Mobile.

Connect Mobile has all permissions enabled, and I've cleared the data store and completely reinstalled the app. I've also restarted the phone. I've connected the watch to my desktop computer by the cable and synced it manually, also, as that has sometime resolved problems before.

ETA: Garmin Connect Mobile also has full background data permissions, and background activity is allowed (can't be disabled, and Samsung's app "sleep" function is disabled for Connect Mobile). I also tried resetting all network settings, as there were previous threads indicating that some Samsung phones encountered connection issues that this resolved; resetting network settings did not resolve the problem.

Other apps are able to use the phone's location services without issue - tested with my weather app and Google Maps, for example.

My phone is a Samsung Galaxy S8 Active (Sprint/CDMA version SM-G892U) with an unmodified version of Samsung's Android distribution (One UI version 1.1, Android version 9), kernel 4.4.153-17061689, security patch level March 1, 2020.

  • Rolling back to version 4.31.1 from an APK archive fixed the issue; the phone notes the location service request in real time with the taskbar icon, and the location services request log notes Connect. It's definitely a bug related to the app's interface with the phone's location services introduced in version 4.32.

  • I also have the same problem with my vivosmart style watch and new version of Garmin Connect but I don't know how to roll back to version 4.31

  • Former Member
    0 Former Member over 5 years ago

    Exactly Same issue vivosmart style. No GPS thru connect app. Other Apps can request connected gps. In Android GPS History other Apps Listed. Garmin connect has füll Rights nur dont pulli GPS Form Samsung Galaxy a5.

  • Former Member
    0 Former Member over 5 years ago in reply to Former Member

    after ReRoll Back to 4.31.1. the connected GPS works again. 

    Thanks Johann7

  • How do you roll back to 4.31.1?

  • Google doesn't officially support downgrades through Play, but you can sideload an older version of an app from one of the several websites that archives old versions.

    I usually use APKMirror, as I did in this case - you'll need their companion installer app, which you can download from the Play Store, to install an older version of Connect because of how the app is packaged. Once you have the APKMirror installer app installed, go to the APKMirror website, search for Garmin Connect, and download version 4.31.1. Uninstall the current version of Garmin Connect (4.32). Then run the APKMirror installer, find the Garmin Connect package you downloaded, and install it.

    You'll need to make sure Play Store automatic updates are turned off, else it will just install the newest (broken) version again, and make sure you don't accidentally update Connect until the bug is fixed (hopefully next version) when you're updating other apps.

  • That said, I just checked, and there's a new version out, 4.32.1. I'm going to install it to see if the bug is resolved, and I'll update if it is.

  • Bug is still not resolved in the version 4.32.1 update; stay on version 4.31.1 if you experienced this issue.

  • It worked. Thank you

  • Rolling back worked for me, thanks for the tip. It's a great feature and Garmin proved it can work. 

    UPDATE: I have emailed Garmin the issue but not really expecting a personal response, just hoping they fix a great feature.