Andrew Sun

Shameless self promotion: I recently wrote a similar library, which is compatible with the `SharedPreferences` API: https://github.com/apsun/RemotePreferences This one offers granular access control to preferences (so you can deny third...

> Yeah, but the UI also has to use SharedPreferences in the same way. The good thing about the standard preferences saved in XML files is that you can easily...

> And it's hard to get a Context from the System UI (at least for me). Really? I thought you could just use [`SystemUIApplication`](https://github.com/android/platform_frameworks_base/blob/master/packages/SystemUI/src/com/android/systemui/SystemUIApplication.java) for hooks running in SystemUI (haven't...

Hmm... I don't think this is fixable at the library level. As you mentioned, one bypass would be to hook whatever in the system performs this validation and allow the...

Recently I found this undocumented property `android:forceQueryable="true"` that you can set on the `` element in your AndroidManifest.xml which seems like a way to bypass the package visibility changes. Haven't...

@RobertZenz interesting, although I'm not sure how much that would have in common with RemotePreferences (the vast majority of code in this library is just to adapt SharedPreferences to the...

I thought about this a long time ago, I believe the main reason I never implemented it was because I suck at UI and didn't want to implement rearranging list...

I do want to implement ordering, but probably won't have the time to do it myself anytime soon. Work is hard :-/

As it turns out, Android O seems to have removed the *_SMS permissions from `com.android.phone`, which means we can no longer protect our blocked messages/filters database using that permission. Using...

(2) also has the added benefit of removing a lot of ugly complexity in the app. We can finally implement verbose logging in a reasonable way (global singleton, anyone?), and...