2

Unlike its predecessor Android versions which saves notification policy in the file /data/system/notification_policy.xml (the file which saves the package name of apps you've selected to stop giving notifications by unchecking "Show notifications" from Settings → Apps → your app name) Lollipop doesn't seem to follow that concept.

I have a Oneplus One running rooted CyanogenOS 12 (CM12). I also tested Paranoid ROM (AOSP) running Lollipop and the behavior remains same i.e. disregard for that file.

In the logcat's output the entries I see when I uncheck and later check "Shows notifications" for an app (e.g. AutomateIt) is:

[ 08-24 15:46:43.441   899: 1966 V/NotificationService ]
enabling notifications for AutomateIt.mainPackage

[ 08-24 15:47:01.361   899: 1966 V/NotificationService ]
disabling notifications for AutomateIt.mainPackage

Surprisingly, the source code of Notification Manager Service doesn't seem to disregard the said file.

So, where does Lollipop keeps notification policies which are effectively executed by system?

Edit: Compared to Android Kitkat or below, how Lollipop uses that file? Can a user simply change the content in that file and expect the notification policy for an app to be changed after a reboot. The process is very simple in Jelly Bean though.

2
+50

Since this commit notification policy settings were migrated from the separate /data/system/notification_policy.xml file to the generic AppOps subsystem. Now they are stored in /data/system/appops.xml together with other AppOps settings.

  • +1. Based on the answers here it would seem that appops is not specific to CM ROMs which answers my earlier (now deleted) comment. – Firelord Aug 27 '15 at 19:00

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.