tree 8c21ac6e4a590b7cbebcce88b9d611506a3b296c
parent 31a0926aafc8e57aab74a2d95ccb907231036b84
author Brad Ebinger <breadley@google.com> 1555539678 -0700
committer Brad Ebinger <breadley@google.com> 1555618339 +0000

overrideConfig should use existing notification flow for CCC

When CarrierConfigManager#overrideConfig was called, we were calling
the CCC broadcast directly, instead of using the existing
pattern of calling notifySubscriptionInfoUpdater. This may become
an issue if future CTS/GTS tests depend on this happening.

Also, only allow the SHELL UID to call overrideConfig, as
it should only be used for testing.

Bug: 130372397
Test: Manual
Merged-In: Ie2cccbab3e186091515bcdaf683d6925d2cbae37
Change-Id: Ie2cccbab3e186091515bcdaf683d6925d2cbae37
(cherry picked from commit 97ce72822a2dd508cb2d59b5458ee367ddbfea29)