* changes:
Add deviceId to Context and allow for creating Contexts with different deviceId.
Open the visibility of VirtualDeviceManager and VirtualDeviceManager#getVirtualDevices.
Add an API to get the details of all virtual devices.
Applications may create contexts associated with the default host device or with any virtual device. The only way to create a non-default device context for now is via an explcit createDeviceContext call.
Bug: 239152561
Test: atest FrameworksCoreTests:ContextTest
Change-Id: If18dc7661fb232b0bc40121c723673ba880be9d5
To deliver a "resultTo" listener for a broadcast intent, we need to
know about the ProcessRecord we're returning the result to, so that
we can potentially unfreeze them and sequence the response through
their main thread.
Also offer to lookup the "system_server" process when the caller
provides an in-process resultTo instance; this smoothly handles
dozens of situations where the system sends broadcasts without
having easy access to its own ProcessRecord.
Bug: 251486235
Test: manual
Change-Id: I1ff58a0e918b620def25a056624f093d951667a6
Migrates getDefaultVrComponents used by SettingsProvider and
adds a flag for hidden API enforcement to ApplicationInfo.
This removes any dependency on SystemConfig from core/ and
so it can be moved into services/core and exposed as a
mainline API.
This was done instead of exposing all of the methods through
SystemConfigManager, as that is designed for use across
processes, and it's more efficient to expose SystemConfig
directly for modules running in the server process.
Although VrManager is a nullable service, so getDefaultVrComponents
had to live there to simplify the logic and maintain the existing
behavior.
Bug: 236389629
Change-Id: I4c2b14e1d34aaf439ceb1a3f9c8207e5d39fa6c2
Some apps keep adding the same resources to their theme key
objects on e.g. switching dark mode. Need to be prepared to
limit the size of the arrays, otherwise theme switching gets
slower with each toggle
+ a bit more efficient native handling
Bug: 242005877
Test: manual, 10k of theme switches with no noticable slowdown
Change-Id: Icf74770bd41ebeb0a31f527ae3616de00f23b0ae
Previously two AssetFileDescriptors pointing to the same file could be
using the same underlying file descriptor and reading from both would
provide unexpected results since they would both modify the file offset
in the kernel data structure.
Test: Added testTwoFileDescriptorsWorkIndependently() to
android.content.res.cts.AssetFileDescriptor_AutoCloseInputStreamTest
Test: atest AssetFileDescriptor_AutoCloseInputStreamTest
Fix: 168310122
Change-Id: Ibf3c9ff0207544e3b227511aae93c8f4ddf52867
Override getChannel() in AssetFileDescriptor.AutoCloseInputStream
Previous fix do not have getChannel() handled which caused issues. This
is to override getChannel().
Test: Added testGetChannel() to
android.content.res.cts.AssetFileDescriptor_AutoCloseInputStreamTest
Test: atest AssetFileDescriptor_AutoCloseInputStreamTest
Bug: 168310122
Change-Id: I472655c91491fd33ef0c2631d94fc0b8d0328404
Adding OffsetCorrectFileChannel help to correct offset
Test: Added testGetChannel() to
android.content.res.cts.AssetFileDescriptor_AutoCloseInputStreamTest
Test: atest AssetFileDescriptor_AutoCloseInputStreamTest
Bug: 168310122
Change-Id: I9ed584ac795cabbed6a4e297c61c224233b9575c
This was separated out to make review easier. Applies @SystemApi
to expose a subset of PackageState and its child type APIs.
Bug: 235462722
Bug: 246609797
Bug: 244444049
Bug: 229089418
Bug: 229090204
Bug: 229090094
Test: presubmit
Change-Id: Ifc0ee3584347a79fbb0e7815d42bac6d2c2f3a4a
Move some minor changes into this smaller independent CL for better
reviewing.
Bug: 242677131
Test: atest CtsPackageInstallTestCases
Change-Id: I71db4c272c355c97251e812881f361ea32b7666f
Introduce a new mechanism to allow developers requesting the approval
from users for an install before committing the session and without
any of the APK file.
Bug: 242677131
Test: atest CtsPackageInstallTestCases
Change-Id: I38029d9dbf28f03b81e4988f1f864e552129c957
For use by static analysis, @PermissionMethod documents
the methods in the platform that perform permission "checks" (e.g.
context.enforceCallingOrSelfPermission).
@PermissionName denotes that the annoated String is a permission name.
It is typically used to annotate the argument to a @PermissionMethod
that is the permission value. This is consumed by static analysis, for
example when helper methods wrap @PermissionMethod calls to pass a hard
coded permission value e.g. "enforceAudioSettingsPermission".
See: go/enforcepermission-migration-design
Bug: 247537842
Test: Tested manually, ultimately will be tested in presubmit (atest
AndroidFrameworkLintCheckerTest, see b/240445172)
Change-Id: I811ae923de62046e782ec7b109a0f99483dab4b2
The CredentialManager module provides solution for developers to create
or get credential from a user that can be used to authenticate to the app.
It can potentially launch system level UI flows to collect user consent,
render a unified selector when more than one credential exists, and
perform anything else needed.
Check bug id for detailed design.
Note that this is still very early stage of productionizing the module
and proper test cases will be added subsequently when the service
gets more concrete business logic.
Bug: 246564035
CTS-Coverage-Bug: 246637346
Test: Local Build & Deployment
Change-Id: Ia5884a7f6a3908de3b8b4b29f154f98e25730bd7
Setup scaffold for the Health Connect system service.
This service will provide system APIs to read and write
health data.
Bug: 249321392
CTS-Coverage-Bug: 248508112
Test: atest android.healthconnect.cts
Change-Id: I503c24a039c37d09895fc4f73a1de1a13eeb72b0
Bug: 246953799
Log resource api times to statsd. Two APIs are logged:
getResourceValue() and retrieveAttributes(). Other APIs may be timed
by the runtime layer but these are not logged.
This fixes a bug in ResourceTimer.startTimer() that caused the class
to skip the first repeated publication point.
This change renames the two RecourceTimer instances in
android_util_AssetManager.cpp to "_timer" to be more explicit and to
avoid the use of the more generic "_tag".
Test: manual
Change-Id: I0c5e0906f79ff35db1e34593275b39fb7f2f179b
In order to let developers to get the install approval from users
pre-download instead of post-commit for better UX, introduce the
new data class PreapprovalDetails to encapsulate all the necessary
data for the upcoming installation.
Bug: 242677131
Test: build
Test: atest CtsContentTestCases:PreapprovalDetailsTest
Change-Id: I29a364262f980d5e30c4800fa0cfb2caae8ffa79
For use by static analysis, @PermissionMethod documents
the methods in the platform that perform permission "checks" (e.g.
context.enforceCallingOrSelfPermission).
Said methods either return in int of type @PermissionResult, or return
void and potentially throw a SecurityException.
There are currently two platform lints that care about this information.
ManualPermissionCheckDetector and PackageVisibilityDetector.
See: go/enforcepermission-migration-design
Bug: 247537842
Test: Tested manually, ultimately will be tested in presubmit (atest
AndroidFrameworkLintCheckerTest, see b/240445172)
Change-Id: Ia21ba748eab37b532b591edb2599bb78ea0c8c9d
This patch change native APIs from @FastNative to @CriticalNative.
From the benchmark, it gets 10% improvement.
The CriticalNative requires the native function can't access JNIEnv
and any jobject. nativeGetAttributeIndex can't apply CriticalNative
because it needs JNIEnv to transform Java String.
This patches move the 16 APIs from FastNative to CriticalNative.
* 11 APIs check the null document and throw NPE in native layer. They
are change to return ERROR_NULL_DOCUMENT and throw NPE in java
layer.
* 5 APIs just remove JNIEnv and jobject parameters.
* nativeGetNamespace
* nativeGetName
* nativeGetText
* nativeGetStyleAttribute
* nativeGetSourceResId
Reference: ag/19992907
Bug: 173709508
Test: # for FastNative
atest --iterations 20 \
CorePerfTests:android.content.res.XmlBlockBenchmark \
2>&1 > fn20.txt
Test: # for CriticalNative
atest --iterations 20 \
CorePerfTests:android.content.res.XmlBlockBenchmark \
2>&1 > cn20.txt
Test: http://b/issues/173709508#comment2
Change-Id: I43ccd1177fa86df5cd4d432119cbd06d370e82d8
Bug: 246953799
Collect timing information for resource acquisition methods. The
timing has nanosecond resolution and is collected inside the native
runtime code. Timing values are accumulated in the runtime and are
periodically fetched and published by the java framework. This
strategy means that normal resource methods incur a small runtime
overhead. The longer time involved in publishing the values is
handled by an independent Java thread.
A public dumpTimers() method can be called from a dumpsys command, for
debug, but the dumpsys command is not hooked up in this commit.
No APIs are actually monitored in this commit, and the ResourceTimer
loop is not started.
Test: atest
* androidfw_lib
Change-Id: I5995d3c6518ca2fa4c8ab9d3eb610167758c695d
user's actual state might have changed by the time the broadcast is
received, so added a null check.
Bug: 237413499
Test: atest HandlerThreadingDomainTest LocationTimeZoneProviderControllerTest LocationTimeZoneProviderTest ZoneInfoDbTimeZoneProviderEventPreProcessorTest
Change-Id: I79087a3e83a51b81568bdb6ff5540ee78b51b91a
Merged-In: Ieacbb35e522b35353c96de1f162a8a71388b4b04
(cherry pick from commit 799c6528f5)
This provides a sandbox-like scaled environment on client side.
- This prevents the metrics and config from being scaled multiple
times because the entry points are only called from server side,
there won't have reentrancy for applying the scale.
- App's configuration callback method can get scaled config.
- If override scale is enabled, the legacy compat mode will be
skipped. That avoids mixing different approaches of scaling.
- Legacy compat mode is to simulate a 320dp x 480dp screen
size with density 160 (the surface scale and config scale
are different).
- Override scale is to downscale the app for better performance
(the surface scale and config scale are the same).
Bug: 238416387
Bug: 240335717
Test: atest ActivityThreadTest#testOverrideScale
Test: atest CtsWindowManagerDeviceTestCases:CompatScaleTests
Test: am compat enable DOWNSCALED $pkg
am compat enable DOWNSCALE_50 $pkg
Change-Id: I0ddf333996f229063511273f8aeb3867c9ba8bda
We're defining a new compat framework change id that restricts
the other aspect ratio overrides for devices in portrait fullscreen.
Fix: 218959984
Test: As manual testing use 'adb shell am compat disable/enable OVERRIDE_MIN_ASPECT_RATIO_EXCLUDE_PORTRAIT_FULLSCREEN <package-name>'. For the unit tests run 'atest WmTests:SizeCompatTests'.
Change-Id: I84eaab4df045c93fb2c159a789852094caf9121a
Merged-In: I84eaab4df045c93fb2c159a789852094caf9121a
