Christopher Tate 4b425712c6 Fix #29737133 : content-trigger jobs not running properly ...

When removing the ContentObserver wrapper from our internal
bookkeeping we were using the wrong key.  That led to future
re-registrations thinking they were reusing a currently-
registered observers, but instead never getting onChange()
notifications.

Change-Id: Id3111db057ae63194049d7d48d45b75be6bb0000

2016-06-27 16:12:41 -07:00

..

accessibility

Report all content changes to a11y services.

2016-06-22 12:35:26 -07:00

appwidget

Allow stopping user to access AppWidgetService API

2016-06-16 14:57:00 +01:00

backup

Fix adb backup/restore

2016-06-22 13:53:41 -07:00

core

Fix #29737133 : content-trigger jobs not running properly

2016-06-27 16:12:41 -07:00

devicepolicy

More thorough cleansing of expired users

2016-06-15 11:32:16 -07:00

java/com/android/server

More thorough cleansing of expired users

2016-06-15 11:32:16 -07:00

midi

…

net

Don't loop forever on 0-length options.

2016-06-23 15:43:34 +09:00

print

…

restrictions

…

tests

Don't loop forever on 0-length options.

2016-06-23 15:43:34 +09:00

usage

…

usb

Handle the uncommon case that a name is null

2016-05-31 10:16:30 -07:00

voiceinteraction

Properly set default voice interactor

2016-06-02 15:25:15 -07:00

Android.mk

…