Avoid mixups between different CPSes in ZenModeConditions
A couple of places in ZenModeConditions assumed that condition id uniquely determines ConditionProviderService, which is not correct. Additionally, verify that only system zen rules can be handled by system CPSes (schedule, event, etc). Bug: 391894257 Test: atest ZenModeConditionsTest Flag: EXEMPT Bug fix Change-Id: I7bff4b04674b5f247bd3b8b6920af029ef8098f5
Loading