The old getSubId or getSubscriptionIds return multiple sub ids
per slot index, which is not possible in today's implementation
because the slot index here refers to the logical slot index,
which is also known as phone id, or the logical modem index. In
today's telephony, one logical phone can only have one
subscription at one time, so does the modem.
Bug: 239607619
Test: Manual
Change-Id: I67cb2bade2c9496a50cccd81fa8f6edc57ede967
CarrierService#onLoadConfig is called from platform to carrier service
to load carrier-specific configuration values.
In case when the multiple subscriptions are supported for the same
carrier (e.g. Fi on pSIM + Fi on eSIM case), the current API is not
able to distinguish on which subscription the carrier config should
be loaded. The subscription parameter introduced in the API can
resolve the problem.
If carrier app has no need to distinguish configs by subscriptions,
it can simply ignore overriding the new version of the API.
Bug: 131697791
Test: atest CarrierServiceTest
CTS-Coverage-Bug: 210143342
Change-Id: Id7cd75c24f01119749cb5bf31d4335c638547aaf
Current APIs does not include subId or phoneId to locate which
carrier network reported the change. A patch based on carrier
privilege were deployed in Q to temprarily fix the issue.
However, multiple subscriptions which all have the carrier
privileges will all get notified, even only one of them
has the real change.
To throughly resolve the issue, the subscription is introduced
in the API to distinguish which network actually has the change.
Bug: 131697791
Test: atest TelephonyRegistryManagerTest CarrierServiceTest
Change-Id: Ie7ee25f53da605c15e1a9228482cc8c4e7406d2a
This will allow CarrierConfigLoader to dump packages' bound carrier
services as part of bug reports when appropriate.
Bug: 146521742
Test: manual with modified CarrierConfigLoader + dumpsys carrier_config
Change-Id: Ie3aef4216e7a42e5e4cc5ba4a3978b9c4dda50dd
Merged-In: Ie3aef4216e7a42e5e4cc5ba4a3978b9c4dda50dd
(cherry picked from commit 05a57b6f5e)
