u/NativeJim

Notification Problem fixed

So I wanted to share something that's been bugging me for a while in case anyone else has dealt with it.

I was running my Bip 6 on a Samsung Galaxy (stock One UI / Android) and the connection was just constantly janky. The watch would randomly stop showing notifications, and every time I dug into it, Android had revoked the notification access permissions for Zepp. I'd go back in, re-grant everything, it'd work for a min or two, then same thing. Super annoying when you're relying on it for texts and calls.

I assumed it was a Zepp/Amazfit issue and honestly came close to just ditching the watch.

Anyway, I recently upgraded to a Pixel 7 Pro running GrapheneOS, and I haven't had the problem once since switching. Not a single permission revocation, connection has been solid. I don't know if it was Samsung's aggressive battery optimization killing background processes, something with One UI's permission handling, or a combination of both, but whatever it was, it's gone now.

Not saying everyone needs to switch phones, but if you're on Samsung and dealing with constant notification permission resets, it might be worth knowing the issue could be on the OS side, not the watch.

---

And before anyone says anything, I'll give credit to Claude helping me rewrite what I said so it wasn't all over the place because my writing is ass.

reddit.com
u/NativeJim — 12 hours ago