Age | Commit message (Collapse) | Author |
|
Change-Id: Ic2889f5eb531008340529eadc36ec8efc62b1984
|
|
Bug: 196970023
Test: presubmits passing.
Change-Id: I69f51eb2faac0cf2ee9f7a5f94f7100925f7221c
|
|
Change-Id: Ie10e9c4c48550d7f4f0c9aa87015bbc1944ac787
|
|
Bug: 195934893
Test: atest ctsLocationPrivilegedTestCases
Change-Id: I255e118cabf274811b57e88a35faf8c9e697d8ae
(cherry picked from commit e19a11cf6fdafd9e9a75bc65f6c3a498a4ff687e)
|
|
|
|
Change-Id: I5aa7cf27a3a3cc16830c9947a826e30a0da481c4
|
|
|
|
Should handle extras in a better manner.
Bug: 196075248
Test: presubmits + manual
Change-Id: I89e45c289b26ea97486c5a72feb0a805c8c1a950
|
|
Logging received locations was originally removed over fears it would be
too spammy, but it is proving too difficult to debug without at least
some logs here.
Bug: 196053011
Test: manual
Change-Id: Ie18baa26daca9ad761125ad07a734f27fabfd89e
|
|
Bug: 195934893
Test: atest ctsLocationPrivilegedTestCases
Change-Id: I255e118cabf274811b57e88a35faf8c9e697d8ae
|
|
Change-Id: I96a39cdca22771b76e89caebd53ed52416005092
|
|
Change-Id: I72d03812a8377fc014aebad8db4e68eeded2d531
|
|
ADAS applications on automotive device require a way to access GNSS
sensors even when the master location toggle is off, so that they can
provide automotive safety services.
Bug: 156688086
Test: atest LocationProviderManagerTest
Change-Id: I438a781b2202c488da97f7ea732f87403d1068e4
|
|
|
|
Change-Id: I9acdc955f698dbebb8fad19cfd5cb71fcdd27b45
|
|
|
|
Change-Id: I5200ee05285ae422d5e9c1c00f45709a5d6188be
|
|
Bug: 190846015
Test: N/A
Change-Id: Ib954ac948f7e2ac4684bcc02b553bb2a3c61e853
|
|
Bug: 190263418
Test: doc update only
Change-Id: I0bec883c5b64d3e9fb2b7e3436aef3cc58a7e53a
|
|
|
|
LocationManagerService was overwriting location source appops tag
information whenever a location provider changed state. Since multiple
location providers can correspond to the same uid/app id, this could
lead to loss of tags. This is fixed by recalculating the set of tag for
an entire app id any time a uid changes.
AppOpsPolicy had a bug where tag lists coming from different uids under
the same appid would inappropriately overwrite each other. This is fixed
by modifying the internal/external APIs to work in terms of appid rather
than uid, so that it is someone else's responsibility to ensure the
result is valid for the app id as a whole.
Also fixes a bug where LMS assumes tag listeners are added prior to any
providers. If listeners are added after some providers they will miss
updates. Fixed by always updating the listener on registration.
Bug: 190073375
Test: manual
Change-Id: Ib52d752d857b6ac3b6683186a8d1bbcb814fb798
|
|
Change eventlog behavior solely based on logging properties, not the
debug build. This allows for reduced logging even on debug builds. Minor
updates to LocationProviderBase.
Bug: 190609486
Test: manual
Change-Id: I1efb28663de7ddd4224b01afe195baf3ff78ddb0
|
|
Keeps same behavior from previous releases.
Bug: 190427917
Test: none
Change-Id: I5f80bbe202ce1137c702e90f2b54a285a7628c94
|
|
dist_group replaces owner and the default is going to change, set it
to the current default "android" for frameworks/base java_sdk_libraries.
Bug: 186723288
Test: m checkbuild
Change-Id: I1526853951bcffbe5c5aec6fbc6ba8e0dbea95ad
|
|
When APIs are refactored mid-release, they can often be left marked
as @Deprecated with the intention of eventually removing them before
the SDK is finalized.
Well, the time has come to finalize the SDK, so let's clean them up.
Bug: 189325658
Test: manual
Change-Id: I48e3e1c1306fbaf071e4acfd9e8107e6ad564ffe
|
|
|
|
Remove getFlags/setFlags, determining the flag in Java side
Bug: 188798284
Test: atest CtsLocationPrivilegedTestCases, also try setting different flags in HAL to see if CTS can be passed.
Change-Id: I231148b62404ee4873da60546eebb75d83fae9a7
|
|
Create a new DeviceConfig entry to replace the prior Settings entry on
which the location ignore settings allowlist is based. This allows us to
allowlist based on attribution tag, and eliminate holes for large
applications.
Test: manual + CTS + GTS
Bug: 187421886
Change-Id: I31e61db79b93e202bd8c66efae1bb5aaf0c88ff5
|
|
Change-Id: Ic23aece12c3bbd2b4dcf3205fdbcdd1601deabec
|
|
Bug: 187145250
Bug: 188225075
Test: atest CtsLocationPrivilegedTestCases, also try setting different flags in HAL to see if CTS can be passed.
Change-Id: Ie5e11ebd5516dffcf80373805a7b37668f7db8a0
|
|
Change-Id: Ia86f3e18206beabe334e3081cedbaf5b3274f78e
|
|
|
|
|
|
Revert "Remove dynamic location settings footer"
Revert submission 13809184-location_footer
Reason for revert: b/187211885
Reverted Changes:
Iaf14044e0:Remove dynamic location settings footer
Ifa6468b11:Remove dynamic location settings footer
If3ab49241:Remove dynamic location settings footer
Bug: 187211885
Change-Id: Ib53c42b3583fd93c87d21feb9882f3431b133d40
|
|
Bug: 183239007
Test: atest CtsLocationPrivilegedTestCases
Change-Id: I30a0ff67c2523ab08505c2761594b64f48c23a21
|
|
|
|
Three bugs were present here:
1) isLocationEnabled() will return incorrect results for USER_CURRENT
and USER_CURRENT_OR_SELF
2) Disabling the location enabled cache does not work properly in the
system process, we only disable the cache for a single instance of
LocationManager.
3) isLocationEnabled() was not respecting the user as defined by the
context used to create the LocationManager.
Bug: 185401689
Test: atest CtsLocationFineTestCases
Change-Id: I84bff02604a4b2d84494a0e099e172c4ffb400a2
|
|
Change-Id: I8d45e47c131320cac5e794fd629fdef84dd3bcfc
|
|
|
|
Bug: 162508535
Test: doc update only
Change-Id: I3267a8b02d47e780cf1124a0882a26958383dd5f
|
|
Bug: 177616061
Test: none
Change-Id: I81bcd4530fd7064ade8be00e0ad6d126cb9ab6f6
|
|
Updates various docs around location time, and also fixes up some
deprecated method usage.
Bug: 184726840
Test: presubmits
Change-Id: I79365e2a3608c8eaeba954b7c193775e98fb2a91
|
|
Change-Id: Iaad2b7cc2aeba166f003d0d460bc8ce29d1caab3
|
|
Change-Id: I1e21c5890b5b2e2f2855f09960bc8eec8aa922bf
|
|
a087245e03 am: 3dd40d172b
Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/1661581
Change-Id: I99cb5fd94c4ee02688709ad00e3ffbc3e2f388e7
|
|
a087245e03
Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/1661581
Change-Id: I70994b32bd4a68bb3d3062d349cc833ba2edf5a0
|
|
Added SPDX-license-identifier-Apache-2.0 to:
drm/java/Android.bp
graphics/java/Android.bp
identity/Android.bp
identity/java/Android.bp
keystore/java/Android.bp
location/java/Android.bp
location/tests/Android.bp
lowpan/java/Android.bp
media/mca/effect/java/Android.bp
media/mca/filterfw/java/Android.bp
media/mca/filterpacks/java/Android.bp
mime/java/Android.bp
mms/java/Android.bp
opengl/java/Android.bp
rs/java/Android.bp
sax/java/Android.bp
services/tests/servicestests/test-apps/PackageParsingTestManifests/Android.bp
telecomm/java/Android.bp
telephony/common/Android.bp
tests/FlickerTests/test-apps/Android.bp
Added SPDX-license-identifier-Apache-2.0 SPDX-license-identifier-BSD to:
telephony/java/Android.bp
Bug: 68860345
Bug: 151177513
Bug: 151953481
Test: m all
Exempt-From-Owner-Approval: janitorial work
Change-Id: I2ee0af9ce8f74de2172b359b41d2c52a8b8f7e6c
|
|
am: ec1f981309
Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/1655736
Change-Id: I5d242cf5b18c4b556105cfcfe78df2ac18a8544e
|
|
Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/1655736
Change-Id: Ib8d66e1fb8845f3b47fd6e81091c0286ca6c8c9c
|
|
All the java code used to build the framework jar and run metalava
was previously defined in the toplevel Android.bp files. Move these
into the subdirs where the source actually lives.
This simplifies the rules themselves (no path and needless prefix) and
declutters the top level Android.bp.
Test: m
Change-Id: I97086e309eacb879d16facb8497d9940fa5ddaf6
|