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

Garmin Connect v3.2 update - did Garmin recall this version

I have users reporting that they received an update for Garmin Connect Mobile Android during the past weekend. The version is 3.2, but now seems to have disappeared from the app store. It is back on version 3.1.3

Did anybody else notice this.

This 3.2 version is causing some trouble with ConnectIQ apps.

Any way a user can downgrade GCM?
  • You could delete it from your phone then reinstall it? It'll install the newest version available on the store, which should be 3.1.3.
  • You could delete it from your phone then reinstall it? It'll install the newest version available on the store, which should be 3.1.3.


    I tried that, seems impossible.

    Apparently according to research on the web you need the apk of the older version from the developer.
    Not sure where the version is cached. Seems to be on the phone, I don't know.
  • Former Member
    0 Former Member over 9 years ago
    I updated yesterday to 3.2.0.1

    https://play.google.com/store/apps/details?id=com.garmin.android.apps.connectmobile&hl=en



    This new version forces location service to be turned on, not too happy with it.
  • I upgraded this morning. I didn't notice anything about location services being forced on.
  • This new version forces location service to be turned on, not too happy with it.


    That might be due to Android 6 - IIRC, with it, BLE requires location services to be on - it's something in Android itself (maybe a bug) and caused lots of problems with anything using BLE (other vendors too) when Android 6 came out.
  • That sounds likely. It's meant to be a feature of Android 6; apparently the reason is that BLE and WiFi can be used indirectly to infer the position of your phone.
  • Former Member
    0 Former Member over 9 years ago
    That might be due to Android 6 - IIRC, with it, BLE requires location services to be on - it's something in Android itself (maybe a bug) and caused lots of problems with anything using BLE (other vendors too) when Android 6 came out.


    I have been using Android M for a while. In the beginning, there were issues with the BL connection which requires location service on. However, after 1-2 months, the issue no longer exist, I was able to sync and get smart notifications W/O location services. Now they are forcing location to be on, which I don't think is reasonable.
  • I have been using Android M for a while. In the beginning, there were issues with the BL connection which requires location service on. However, after 1-2 months, the issue no longer exist, I was able to sync and get smart notifications W/O location services. Now they are forcing location to be on, which I don't think is reasonable.


    I think there's a good change that not all devices running Android 6 have this fix in place. Mine is only at 6.0.1 for example. and hasn't been updated in a few months.