4 Commits

Author	SHA1	Message	Date
Sunny Goyal	58530bd64b	Fixing notification dots settings not updated properly ... Also avoiding settings cache reset whenever someone registers a new listener Bug: 184200027 Test: Manual Change-Id: I0c8b7084b6b4656102e9041b779b80a98624ddd8	2021-03-31 15:57:49 -07:00
Vinit Nayak	a34af18b0e	Update System settings content observer to cache values. ... Existing ContentObserver will cache values and overwrite them when the value itself is modified or caller force updates. Bug: 149571513 Test: Wrote unit tests, mostly for caching logic. Not meant to test ContentObserver contract for registering an observer. Change-Id: I12835f6c2be27ce17f65a55c51c4ef85c63b4487	2021-02-16 20:58:53 -08:00
Pinyao Ting	4c81a9a819	fix launcher crash when accessing Notification dots in home settings ... Bug: 148815606 Test: 1. Make sure launcher doesn't have notifications permission (Settings -> search for "notification access" -> Disable access for Launcher) 2. Home settings -> Notification Dot 3. Verify Alert Dialog pops up without crash Change-Id: I399b6aad46e8a3e185199a2909adac9f75596b50	2020-02-07 12:04:46 -08:00
Tony Wickham	f34bee819c	Rename "badges" to "dots" where appropriate ... This will reduce confusion with the other "badging" concept we use for, e.g. work profiles. It is also consistent with the external name "notification dots". Change-Id: I2a2c9d96dc0d6284eb0c48adc78a856271caad4d	2018-12-04 10:46:40 -08:00