Add flag for showing data usage chart on detail fragment
Bug: 128569047
Bug: 124700353
Test: manual
Change-Id: Ib150c4d72224b5707c16916d4e134aa5221a481f
Removed feature flag and change to check global flag as framework MAC
randomization api does.
Bug: 127817791
Bug: 120743100
Test: atest WifiPrivacyPreferenceControllerTest
Change-Id: Iefe0d442326ca6a9461af8724a1632fd238d8d2b
This reverts commit c9a5c72ab8.
Reason for revert: The underlying problem for the *original* revert is fixed in ag/6671099, so now we can revert the revert (after ag/6671099 lands).
Change-Id: I01e5ebac8140b253bee9d19981eff53365d3bccd
This reverts commit 1b386491c5.
Reason for revert: Reverting temporarily because of a few bugs that were uncovered: b/127524919 and b/127394263
Change-Id: I47de22c89b680d08c62fb008f97953d0586ab0a3
This change adds a new plugin API surface inside of Global Actions,
where a plugin can provide a View to be rendered alongside the Global
Actions menu.
When the GlobalActionsDialog.ActionDialog is created, the plugin can
produce a GlobalActionsPanelPlugin.PanelViewController instance, which
is used to provide the View to be rendered, and respond to Global
Actions events (right now, only dismissal). At this time, the plugin
is given an instance of GlobalActionsPanelPlugin.Callbacks, allowing
the plugin to interact with the GlobalActionsDialog (right now, only
to request dismissal).
When there is a Panel present, a darker scrim is used that is *not*
based on the colors underneath.
In order to provide maximum flexibility, the View comprising the Panel
is rendered above (z-ordering) the existing Global Actions menu, and
can take up the entire screen if desired. In practice, plugins should
take care to not block access to the GlobalActions menu.
Change-Id: I9d6eea80f7eb49e9adbc1a634f7d9c1ab720cddb
Test: manual
*Array classes will now throw an IndexOutOfBoundsException if a caller
tries to get or set a value for an index that's invalid based on the
current size.
Bug: 118339123
Test: atest CtsUtilTestCases
Change-Id: Iddc9a0c7c89e0ac743b0380049527a1b2dfb434f
Appops can be peformed by an app on its behalf and also on
behalf of another app, i.e. an app can perform a proxy op
and blame the work on another app. The proxy mechanims is
for apps doing work on behalf of other apps where GCore is
one example since the app doing the work needs to check if
the caller has access to the functionality - specifically
the app op backing a runtime permission in case the calling
app does not support runtime permissions.
Apps being able to blame work on other apps is a problem now
that we would be using historical op data to show permission
usage in the UI as apps can start blaming each other to gain
a competitive advantage.
To address the issue we are adding APIs for querying portions
of the app op data - last and historical. One can now get
the ops for work the app did for itself, work the app blamed
on other apps if the app is trusted, work the app blamed on
other apps if the app is not trusted, work other trusted apps
blamed on the app, work other untrusted apps blamed on the app.
A trusted app is one holding the permisison to update app op
stats which is privileged.
The data slicing API allow us to show in the UI only the trusted
poriton of the data which is work the app did for itself, work
trusted apps balmed on the app, and work the app if untrusted
blamed on other apps.
Test: atest CtsAppOpsTestCases
bug:111061782
Change-Id: I9a2bcaea272cb06f38ba742cf601a6dc3b287d5e
If they were null, then the Parcelable would fail to work.
Bug: 126726802
Test: manual
Change-Id: I7929ffa2f20e5de1c8e68e8263cca99496e9d014
Exempt-From-Owner-Approval: Trivial API annotations
Also migrate MediaProvider logging to more general-purpose location
on the ContentProvider.Transport, where we can log exact input/output
values to aid debugging.
Bug: 124347872
Test: manual
Change-Id: I6aba60879ded4e0892d2d1cdd717c23cebaaabd8
Both dump() and reverseDump() only need a single PrintWriter parameter.
This patch adds overloaded versions of these methods with that single
parameter. Callers can slowly migrate to these simpler methods over
time.
Test: Compiled.
Change-Id: I503df2af1d8115f715238f94551343fda1e951cb
The design of aod image wallpaper has changed and we don't need this
implementation any more so we remove it from feature flags.
Bug: 118470430
Bug: 123617158
Test: Manually
Change-Id: I4d48a8b6b8146b754c1d1f48c35855190219d8a9
The target source to send the event will be mainline module
which unable to access @hide classes/functions. And current
design of StatsLog.write only allows a specific id. Thus, add
more case to support mainline module usage.
Bug: 120452078
Test: ./out/host/linux-x86/bin/statsd_testdrive 121
against data stall event sent from NetworkStack
Change-Id: I5a68e7e093e63cc87eae753068183215a97e022d
Symptom:
To update APK Signature Scheme v1 signed system priv-app to new v1
signed version fails if apk verity is enabled.
Root cause:
The package manager gets the verity root hash from apk for apk verity.
But, the getting prosess does not consider v1 signed apk.
The getting prosess fails if the apk is v1 signed.
It causes the update failure.
Solution:
Always skip apk verity if the apk is v1 signed.
Because v1 signed apk always does not have the verity root hash,
and apk verity has been skipped in case of that the apk is v2 or v3
signed and the apk does not have the verity root hash.
Bug: 124354537
Change-Id: Ieb19ed9a3277bfad09dc67a1abf1d9039c44709f
This api is to log BinaryPushStateChanged.
Experiment id is added as a binary blob that is not expected to be
accessed on device side.
This cl is mainly for API.
Will add follow up cls for persisting train info on disk and make puller
for it.
Will address sepolicy in follow up cls.
Bug: 119633962
Bug: 119685453
Test: will add gts
Change-Id: I68b4246cf7e8079155e16121ca37a312b35a5328
