Age | Commit message (Collapse) | Author |
|
packages/Tethering/apex/manifest.json
Change-Id: I5ffb8f9d4c11897610abee96ab3ab5b008d5b4db
|
|
packages/Tethering/apex/manifest.json
Change-Id: I7214dfa832847be4f5da477b8c06467a96ce7a2f
|
|
packages/Tethering/apex/manifest.json
Change-Id: Ic2136a2147564625b5f4de3f26e265d17b00dad2
|
|
packages/Tethering/apex/manifest.json
Change-Id: Icff39ba786c63337bf367101acf4ca1ed445433f
|
|
packages/Tethering/apex/manifest.json
Change-Id: Ic2f7619ed84523229265e099a2e831c34968bd37
|
|
packages/Tethering/apex/manifest.json
Change-Id: I69f8708ff2e685e6d1e00c66c0813e60895754d1
|
|
packages/Tethering/apex/manifest.json
Change-Id: I3c056309b6ac70aa2c8f3db3d386fa65dcd8c8e2
|
|
packages/Tethering/apex/manifest.json
Change-Id: I2b5b949d067a812dab9e9bae7029d6f1fd5803fb
|
|
packages/Tethering/apex/manifest.json
Change-Id: I80c9697c75bd97b1082a627cc3b415a9815b768a
|
|
packages/Tethering/apex/manifest.json
Change-Id: I0712c2fb1d6d8255366260b6cea3eadb57d336e7
|
|
packages/Tethering/apex/manifest.json
Change-Id: Ie6dc95e2ead10672f5442cecfc2ca6bf7b194280
|
|
packages/Tethering/apex/manifest.json
Change-Id: Icf63b0d71339a738e97c08d8ad5fde20665ecd37
|
|
permission to create trusted displays""" into rvc-dev am: 8b1151e4d5
Original change: https://googleplex-android-review.googlesource.com/c/platform/frameworks/base/+/12816011
Change-Id: Ib497378a7901c19fc156d625ce3b9014b19c7757
|
|
to create trusted displays"" am: c947b10f99
Original change: https://googleplex-android-review.googlesource.com/c/platform/frameworks/base/+/12816011
Change-Id: I1c1093f14923aa7a5f2d7891912d13acd15fab66
|
|
mainline-prod
|
|
Also add MtsTetheringTest which only run if tethering mainline
module is installed.
Bug: 166057846
Bug: 170265597
Test: atest TetheringTests
Change-Id: I434dda81eb5fab700d873a8ff3429b4222f0c7e6
Merged-In: I434dda81eb5fab700d873a8ff3429b4222f0c7e6
|
|
permission to create trusted displays""" into rvc-dev
|
|
Original change: https://googleplex-android-review.googlesource.com/c/platform/frameworks/base/+/12846973
Change-Id: I36644afecbd92822cf12c20adb607b09b5766521
|
|
into mainline-prod
|
|
packages/Tethering/apex/manifest.json
Change-Id: I2c0f81f102a2bd30d7b4f2e99b1442931b14757e
|
|
mainline-prod
|
|
The downstream do not be tracked if PrivateAddressCoordinator just
return cached address. Then, PrivateAddressCoordinator would not notify
that downstream if conflict happen.
Also remove the null check in getDownstreamPrefix because:
- An IpServer is only added to mDownstreams by requestDownstreamAddress.
- That method will only add the IpServer to mDownstreams if it has an
IPv4 address.
- As soon as that method returns, the IpServer sets mIpv4Address to the
address that was returned.
- When an IpServer is torn down, mIpv4Address is set to null after
releaseDownstream is called.
So it should never be possible for this to return null.
Bug: 168169687
Test: atest CtsTetheringTest
atest TetheringTests
Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/1459887
Change-Id: I4b4d75c8a4f1de07aa7bb68b12d150d7c85c9cc1
Merged-In: Ide5206b013acdc499344e1c839a830c5b245af41
(cherry picked from commit 335c9c52d0b8d1c4ec28d52e3f994e8b827fcad6)
|
|
This test catch the regression introduced in r.android.com/1432958.
Bug: 1432958
Test: atest TetheringTest
Change-Id: Id0c1afb5563954ffee1f598a3a5de6a245d77a0e
Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/1459889
Change-Id: Ie80d4d5d535d70df493cad0a80166d779bc6ab77
Merged-In: Id0c1afb5563954ffee1f598a3a5de6a245d77a0e
(cherry picked from commit 37738b53d7810a6bea521310478bc137975d49d0)
|
|
The android.jar stubs includes the resource from framework-res. This
dependency was previously added implicitly inside the build system, but
using a java_genrule we can add it directly, which makes it easier to
make changes to this rule.
This change has the side-effect of adding the resources to some stubs
that did not previously include the resources (e.g. module-libs), which
I think is desired.
Bug: 161214753
Test: build sdk, diff out/dist before and after (shows resources added
to some stubs)
Change-Id: I1829789af207cc45c49c0c68369fc7c0c085bcb0
Merged-In: I1829789af207cc45c49c0c68369fc7c0c085bcb0
|
|
Bug: 170395679
Test: m checkapi
Change-Id: Ie81a2ef5dc6d2ba001ae87ad0cba99b4c1eede1c
|
|
Include @SystemApi APIs in the test_current stub jar, while keeping
the @TestApi and @SystemApi API txt files tracked separately.
A side-effect of this change is that string constants of @SystemApi
permissions are no longer inlined in the test api tracking, possibly
because metalava was previously incorrectly peeking at @SystemApi
whereas it is now explicitly forbidden to do so. I don't believe the
API txt change has any practical effects.
Bug: 129133308
Test: presubmit
Change-Id: I23d3c88624ee7599485c3390a0440b78bc18a0a2
Merged-In: I23d3c88624ee7599485c3390a0440b78bc18a0a2
(cherry picked from commit 84ffba267e16ca776614d6e6960ebee1e2e3122c)
|
|
|
|
Modules shouldn't have TestApis, as documented in go/android-api-types.
Additionally, nothing depends on these TestApis existing.
Bug: 170395679
Test: m checkapi
Change-Id: I6e2c8298e90b4b54f0264be974d036fa08cd5632
Merged-In: I6e2c8298e90b4b54f0264be974d036fa08cd5632
|
|
Original change: https://googleplex-android-review.googlesource.com/c/platform/frameworks/base/+/12828332
Change-Id: Iae825b842d283067aaafbc4b48a398450a46ab9c
|
|
Bug: 170764224
Change-Id: Iaef1aa4fd3143e6e9019d06834001b3bfa3d887d
Exempt-from-owner-approval: Docs-only typo fix
|
|
Currently tethering only pick prefix from 192.168.0.0/16. There is no
aviable tethering address if the upstream address is 192.168.x.y/16.
This change allow tethering to pick prefix from any private address
rnages. Now it still pick from 192.168.0.0/16 only to avoid behavior
change. Will have follow up commit to change the configuration.
Bug: 166057846
Bug: 170265597
Test: atest TetheringTests
atest CtsTetheringTest
Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/1436852
Change-Id: I008d5e5902a0fb41ac564c73f265e1c942c8dcad
Merged-In: Ib6304eb8b4788e9196d0af48e72f00a6bda73a5f
(cherry picked from commit 5a60d621055df9721b2206702d6e5f482f175fa7)
|
|
to create trusted displays""
This reverts commit ae03031efe8b751f4513b42cad68db4559a8edfd.
Reason for revert: Merge the reverted patch by accident.
Bug: 162627132
Change-Id: Ic2f072730050cb47926cec6ed24af7ef9e5e7055
|
|
|
|
936cd3b3f1
Original change: https://googleplex-android-review.googlesource.com/c/platform/frameworks/base/+/12683367
Change-Id: I4ba52f8c4af8bb9718f6ab60a295203369e35068
|
|
Original change: https://googleplex-android-review.googlesource.com/c/platform/frameworks/base/+/12683367
Change-Id: I64a3654906a73f5d8f55673dde247c12a2891084
|
|
|
|
* changes:
Make the IP subnet persistent till reboot
Make PrivateAddressCoordinator ignore vpn network
|
|
|
|
* changes:
Remove dead code for AnomalyAlarm
Remove alarm manager dependency from anomalyalarms
|
|
|
|
|
|
|
|
|
|
Anomaly alarms now rely on the flow of events into statsd's socket for
firing alarms. Remove the StatsCompanionService code path, which is
unused now.
Test: m
Bug: 161326200
Change-Id: Ife0b17c281984fc489ef46039cbf5aa7b1346bdb
Merged-In: Ife0b17c281984fc489ef46039cbf5aa7b1346bdb
|
|
Anomaly alarms, which are used for prediction-base duration metric
anomaly detection, currently use alarm manager for setting alarms. This
can result in excessive binder calls to SCS to set/cancel the alarms if
the duration metric that the alarm is based on gets stopped/started in
quick succession.
To resolve this without losing precision, we can instead rely on the
flow of events into the statsd socket for this prediction. The socket
receives events very frequently, so there should be minimal (if any)
loss of precision, and we can remove the binder call entirely.
One concern is that we used to hold a wakelock when the alarm fired
(since alarm manager would hold a wakelock), and we now lose this
ability.
Test: atest statsd_test
Test: atest AnomalyDetectionTests
Bug: 161326200
Change-Id: If37e5c6ccd8efa4e822c70a0444fa6b5a31bebca
Merged-In: If37e5c6ccd8efa4e822c70a0444fa6b5a31bebca
|
|
Original change: https://googleplex-android-review.googlesource.com/c/platform/frameworks/base/+/12794770
Change-Id: If6e12055adfbe330ef00f36d661aaccd64bfded4
|
|
Alerts were being incorrectly triggered in pulled value metrics because
a diffed value is always assumed to be over one bucket interval, which
may not be true when multiple buckets are skipped.
Bug: 159390273
Test: atest statsd_test
Change-Id: Iada3df54ebb30353572a14e0db86bed49c5515b0
Merged-In: Iada3df54ebb30353572a14e0db86bed49c5515b0
(cherry picked from commit ec72e875637eda29110cd2395e7be7f51c27ccd3)
|
|
Test: build
Change-Id: Ie639f57f86c2573cd5e06a1fa9397487f4b3f235
Merged-In: Ie639f57f86c2573cd5e06a1fa9397487f4b3f235
(cherry picked from commit fd5b18820cbea67801d4fdd1562c3cb41e4ce578)
|
|
The VERY_VERBOSE_PRINTING flag guards print-logs functionality but is
not present in the prebuilt version of the statsd module. To fix
print-logs, we remove the flag (thereby allowing print-logs to work on
user, userdebug, and eng builds), but require that the caller have root
privileges.
Test: adb shell cmd stats print-logs && adb logcat -s statsd:I (only works
once root privileges are granted)
Bug: 159982879
Change-Id: I2201fc0538876d1d6dfd6ab7abfac43cccc1102f
Merged-In: I2201fc0538876d1d6dfd6ab7abfac43cccc1102f
|
|
Bug: 169089731
Test: m -j
Change-Id: I9fb8707a5eb190b5749af84e3eb65567b87439bc
Merged-In: I9fb8707a5eb190b5749af84e3eb65567b87439bc
(cherry picked from commit 29edf77b15d381c071bdd529f854fb07133c90ad)
|