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

Delayed notifications! Is it a Garmin connect app problem?

From the first day that I've got instinct 2 solar tactical I've noticed that the notifications from my android phone are coming with five seconds delay on the watch and sometimes much more. I also have a suunto 9 baro with the notifications coming instantly. So i am guessing that the problem is on the Garmin connect app. Is anyone else facing the same problem?

  • Yes. Recently got the Venu 2 Plus and there is a few second delay between phone going off and then watch vibrating.

    My previous Garmin venu (1st gen) was almost instant. This seems to have got worse since latest update...!?

  • I have noticed about a 5 second delay. After a hard shutdown/restart of the watch it improved to a 1 second delay.

    Hold the power button down until the screen goes black (10 to 20 seconds). Then turn the watch back on.

  • Thanks for the response. I've performed hard shutdown and all other recommended actions given by garmin support but nothing happened. I have contacted with several individuals owning forerunner 45, instinct 1, instinct solar 1 and fenix 6x sapphire and they all are facing the same problems under garmin connect android app. Watches under Garmin connect ios app seems to get notifications instantly. I have opened a case with Garmin support about 15 days ago and they told me that they are still working on it.

  • Hello, I've Garmin Venu SQ, and new Motorola Egde 20 with Android 12 - which seems to be important. With old phone with Android 11, phone call notification on Venu was instant. With new Android 12 phone, notification is about 6-8 seconds delayed. I tried everything from battery settings for phone, Grain app, etc. Also tried disabling doze/idle mode on the phone through developer console, without success. System logs on the phone (through Android Studio + Logcat) shows some bluetooth stack errors. This seems to be a problem with Android 12 bluetooth stack...