CMSettingsProvider: remove per-user cursor observation
We don't need it because we don't support using the returned cursor directly, and it can cause deadlocks when being called from platform code. Change-Id: I2f85be1152569ba27e4622d310d867e20965faa3
This commit is contained in:
parent
c50ddc2104
commit
9382b6a75f
@ -470,17 +470,6 @@ public class CMSettingsProvider extends ContentProvider {
|
|||||||
null, sortOrder);
|
null, sortOrder);
|
||||||
}
|
}
|
||||||
|
|
||||||
// the default Cursor interface does not support per-user observation
|
|
||||||
try {
|
|
||||||
AbstractCursor abstractCursor = (AbstractCursor) returnCursor;
|
|
||||||
abstractCursor.setNotificationUri(getContext().getContentResolver(), uri, userId);
|
|
||||||
} catch (ClassCastException e) {
|
|
||||||
// details of the concrete Cursor implementation have changed and this code has
|
|
||||||
// not been updated to match -- complain and fail hard.
|
|
||||||
Log.wtf(TAG, "Incompatible cursor derivation");
|
|
||||||
throw e;
|
|
||||||
}
|
|
||||||
|
|
||||||
return returnCursor;
|
return returnCursor;
|
||||||
}
|
}
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user