I enabled the new lifestyle tracking feature in Garmin Connect and set up reminders for 09:00. and 20:00. I haven't received a single notification, despite giving Garmin Connect all the necessary permissions. Anyone else having this issue?
I enabled the new lifestyle tracking feature in Garmin Connect and set up reminders for 09:00. and 20:00. I haven't received a single notification, despite giving Garmin Connect all the necessary permissions. Anyone else having this issue?
I tried an old Pixel 4a, which does work
As I mentioned earlier also works on my old phone...
Connect ver 5.17.1. Android ver 10. Perhaps an issue with newer phones.
Now on 5.17.2 and it's still working.
It's got to be something to do with device permissions. Highest Android version on Pixel 4a is 13, which seems to be working. Notifications don't seem to work on devices running Android 15 or 16.
The Connect app has all notifications enabled on my phone (Pixel 9a/Android 16), and access to all permissions, but I've not received a single notification since Lifestyle Logging became available.
Every time you modify the time of notification it works. If the next day you don't touch it, it doesn't work.
Example: yesterday time for notification at 21:50, it didn't work. If today I change it to 21:51 it will work correctly at 21:51. Tomorrow, if I will not touch anything, it will not work at 21:51
Every time you modify the time of notification it works. If the next day you don't touch it, it doesn't work.
Example: yesterday time for notification at 21:50, it didn't work. If today I change it to 21:51 it will work correctly at 21:51. Tomorrow, if I will not touch anything, it will not work at 21:51
I confirm this behaviour: yesterday I changed the reminder's time of just 5 minutes and it worked. It's a problem with the app, not with Android version
I confirm this behaviour: yesterday I changed the reminder's time of just 5 minutes and it worked. It's a problem with the app, not with Android version
This doesn't fix it for me: still no notifications.
I'm in the process of dealing with Garmin support about this issue. Not much progress yet...