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

Connect 3.9 doesn´t work with Android 6.01

Former Member
Former Member
When using my VSHR+ with connect 3.9 and Android 6.01 (my phone) the notifications doesn't work.

I try with my VSHR+ with connect 3.9 and Android 5.1.1 and the notifications WORKS.

I try with my VSHR+ with iphone and the notifications WORKS.


Is seems the when using the connect 3.9 with Android 6.01 the notifications doesn't work.

Any Help Please.

:(
  • Former Member
    0 Former Member over 8 years ago
    You have to give Garmin Connect permissions in Android 6.
    Open Settings -> Applications -> Connect -> Permissions, and select all to make notifications work correctly.
  • Former Member
    0 Former Member over 8 years ago
    You have to give Garmin Connect permissions in Android 6.
    Open Settings -> Applications -> Connect -> Permissions, and select all to make notifications work correctly.


    off course.
  • Former Member
    0 Former Member over 8 years ago
    Still Not working

    I gave the permissions and allready get No notifications, No weather and No Player contol.

    Bluetooth and gps is on. But i think the vshr doesn't sync automatically.

    I hope someone can help me fix this.

    My Smartphone is the Huawei Mate s
  • Former Member
    0 Former Member over 8 years ago
    I have the same problem. Moto G 3 with 6.0 works, Vodafone Smart Prime 7 with 6.0.1 doesn't.
  • Former Member
    0 Former Member over 8 years ago
    It seems none equipment with Android 6.x is working with connect 3.9 and nobody from garmin says anything. :(
  • Z3Compact with latest 6.0.1 doesent work with GCM 3.9 :/
  • Former Member
    0 Former Member over 8 years ago
    My LG with Android 6 works OK for notifications.
  • Former Member
    0 Former Member over 8 years ago
    I only getit to work if I enable Location on my Phone. Otherwise it won't sync and notifications won't work either. It's not what I'd prefer (location on) but it seems to be an Marshmallow requirement. Try that.