The platform currently supports the notion of default carrier apps.
These apps are set to DISABLED_UNTIL_USED until a SIM is inserted
which grants them carrier privileges, at which point they are enabled.
Apps are not touched if they have been updated from the version on
/system or if their state has been modified externally (e.g. by the
user).
This CL extends this notion to associated apps, which may not have
carrier privileges themselves, but should be enabled/disabled
alongside a particular carrier app. This should include helper apps
that should not be visible to users who don't use the given carrier
unless the user explicitly enables the app.
As additional protection, we add a check to ensure that we never
disable apps after the first time we've run. Since we need to store
this information in secure settings, we also move the call site from
PackageManagerService#main() to PackageManagerService#systemReady(),
which enables use of secure settings but still occurs before
third-party apps can be started.
Bug: 30141427
Change-Id: Iee72ba4e70e5ca97999c9147a65af82c670a23e8
Before when extreme alert is disabled, severe alert will be disabled
by default because we assume users won't be interested in severe
alert if he is even not interested in extreme (higher level) alert.
Now carriers are allowed to turn this feature off by carrier config.
bug: 29369591
Change-Id: I3eb8a0c3e2df420ea75a77ec01cc447013434219
Adds a Carrier Config key to specify whether an IMS call supports
holding. If not, the CAPABILITY_HOLD and CAPABILITY_SUPPORT_HOLD are
not added to the Connection.
Bug: 30195356
Change-Id: I9b16b385a2b90118453d484be5af4f173b199ab1
Some modems use a lowercase version of this extra, which is not correct.
Adding an alternate definition so ImsCall can still determine the radio
type.
Bug: 28933314
Change-Id: I61d13a2aa447877e1c89c3ae474a8614c29492a1
Disable VT when users turn off data or hit data limit. If
there are ongoing VT calls, we'll need to downgrade them
to VoLTE calls.
bug: 27316521
Change-Id: I89fe42f6cf6c419c21c4f2006e9cb43cf7e13503
1) Finish plumbing of PULLING_CALL state.
2) Add new disconnect cause used when maximum number of calls across
all devices has been reached.
3) Add PII mask for toString of ImsExternalCallState.
Bug: 29522023
Change-Id: I78a0a9f3c3d846cfc58a1c5bcc6f105027602cbc
Used to be DISABLE_ADD_CALL_DURING_VIDEO_CALL, now just
DISABLE_ADD_CALL. The meaning has also changed -- having the extra set
means that adding calls should be disabled no matter what.
Bug: 29047863
Change-Id: Icd8966492b264a9c64dc4880080a706032f0759c
Adding new carrier config, defaulted to false, which allows a carrier to
promote the use of WFC when the device is connected to WIFI and WIFI
calling is disabled.
Bug: 27970317
Change-Id: I4904b7f006bae9f834816c1964025acf36b4ba84
Used to inform listeners when a connection can or cannot be part of a
conference. Used to inform the conference controller so that it can
recalculate the conferencable connections.
Adding carrier config for carrier requirement.
Bug: 29059073
Change-Id: Iab028fd44d87c8dc2bbbe8bba7ba9ccdc223fe51
Adding two new carrier config options:
1. treat_downgraded_video_calls_as_video_calls_bool - when there is an ongoing
call which was previously a video call (or is currently video call), some
carriers require that this is treated as if it is a video call for
telephony logic such as in (2).
2. drop_video_call_when_answering_audio_call_bool - if the user is in an
active video call (see (1)) over wifi, and an incoming audio call comes in,
when this carrier config option is "TRUE", the video call will be dropped
when the audio call is answered.
Adding new connection extra to indicate to the dialer app that answering
a ringing call will cause the current active video call to drop.
Bug: 29275420
Change-Id: Ied5dbabc8ff09045ba41c5eba2136adad10db80e
Note this may be redesigned in O to better handle the
various bitrate/channel combinations in a sane way.
bug:27360321
Change-Id: If6ffbd02e3a7f170cc041747e32bb624234c3e09
Provide persistable state for cell radio
to handle airplane mode similar to any
other radio in the system.
Change-Id: I87398fe84de3f6a10b0e1002e9e5bf7e61f9441f
Only reports transitions to higher RATs within a given family.
Reset when we move to a new cell.
Avoids costly propogation of RAT flapping within the family,
for example every outgoing data pops us into a higher RAT and
idle time pops us back down.
bug:27360321
Change-Id: I549d79c1c74325981bee284cef452bd096184d86
A few disconnect cause mappings were missing for the multi-endpoint
disconnect causes. Adding them here.
Bug: 29236416
Change-Id: I669bd72290c0e823c54eb6062ebd658743882852
There's more data that needs to make it out to the carrier app.
Add the extras and correct some (it's a byte array, not an int, etc).
bug:28567303
Change-Id: I97ed41d9329ccc14851b8e171e8fa07919c8e38b
- add a new field: provisioningNotificationEnabled from NetworkMisc. set
to false if we want to hide "sign in" notification and placed
carrier-specific notification instead. it is set on connect, once set,
it is carrier-app's responsibility to post new UI to users
- rework on the interaction between carrier app and framework
- code cleanup
- unit test support
Bug: 28567303
Change-Id: Ic84db7ffbb920d15344717f104496d3cb82e1a85
PCO is a container in data-call responses with a range
of optional fields devoted to carrier-proprietary signalling.
This change includes a class to contain this opaque info on
its way to carrier apps.
bug:28961371
bug:28567303
Change-Id: Ibfc304800bb3d5b8706d56c08400c1d0b4453a55
