- Mar 17, 2015
- 402
- 0
- 16
Lately, I've noticed where application access to notifications (like Pebble or Android Auto) keeps getting reset on a restart or an "undock" like a car app. With each use, I have to go into Settings > Sound and Notification > Notification access and manually check all the apps that need notification access.
This is common mostly on Galaxy S4 phones running Lollipop. In that specific case it seems to be related to a bug with the GlanceViewMK process.
However, this process doesn't seem to exist with the Galaxy S5.
Has anyone (who might be using a Gear device or Android Wear) with a Galaxy S5 experienced this?
Here are the details of my set up:
VZW Galaxy S5 (SM-G900V)
Android 5.0 (OC4 revision)
SELinux security policy - May 11 2015
This is common mostly on Galaxy S4 phones running Lollipop. In that specific case it seems to be related to a bug with the GlanceViewMK process.
However, this process doesn't seem to exist with the Galaxy S5.
Has anyone (who might be using a Gear device or Android Wear) with a Galaxy S5 experienced this?
Here are the details of my set up:
VZW Galaxy S5 (SM-G900V)
Android 5.0 (OC4 revision)
SELinux security policy - May 11 2015