History log of /frameworks/base/packages/SystemUI/src/com/android/systemui/statusbar/ServiceMonitor.java
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
4db614dbed10e74285eaa6d0e56c3e79a4afecc0 27-Jun-2013 John Spurlock <jspurlock@google.com> Add sanity check inside ServiceMonitor's setting observer.

When registering for a specific setting key uri, the observer
can also be called back for "parent uri" updates. e.g.
adb shell content update --uri content://settings/secure will
trigger onChange with uri=content://settings/secure.

Add a quick setting value recheck, and avoid restarting if
the setting value change will have no impact.

Bug: 9595731
Change-Id: I4c71f6a4be3b655b31d2535e809bb42edd931cd6
/frameworks/base/packages/SystemUI/src/com/android/systemui/statusbar/ServiceMonitor.java
5c4541246c6a70f53552423dc35940386788bd5f 17-Jun-2013 John Spurlock <jspurlock@google.com> Introduce SystemUI-managed alternative system bars.

If a service component is defined in a new secure setting,
SystemUI will attempt to use that service as the status bar
provider.

Falls back to the existing in-process implementation configured
in the product config if the setting is missing or invalid.

Nothing changes yet from a permission point of view. Alternative
system bar implementations still require the status bar permission.

Also nothing changes from an api point of view. Alternative
system bar implementations use the existing IStatusBar interface.

This simply enables testing alternative system bar implementations
installed from other trusted, platform-signed packages.

Known caveat: the setting is stored per user, multi-user changes
will be handled in a future CL.

Change-Id: I0413df185f7e75f77ad2ae1bc3689306d5e6e0fb
/frameworks/base/packages/SystemUI/src/com/android/systemui/statusbar/ServiceMonitor.java