Add a keylayout mapping to support gamepad buttons and axes on the
Amazon Luna controller.
Buttons and axes are mapped according to
https://www.kernel.org/doc/Documentation/input/gamepad.txt except for
the Alexa Push-To-Talk button which is mapped to MEDIA_RECORD.
Bug: 183990549
Test: used the "Gamepad Tester" app and https://gamepad-tester.com in
Chrome to verify all mappings work.
Change-Id: I1921e501eea0ce398b79a32809efa63456074ed5
- Create a new XML tag for the new format. The new format should
persist the arrays of values without assuming they necessarily
have different bits.
- Upon reading, if the new tag is present, use that. If the new
tag is not present but the old tag is present, then limit the
contents to the capabilities/transports that existed in R.
- Catch all exceptions and ignore the requests if they can't be
re-read from disk. This is a measure to avoid any mistake where
the device couldn't boot when JS tries to restore state.
Bug: 183071974
Test: atest JobStoreTest
Change-Id: I56cde50d2adab81134c8be4f6996d68018f4212a
When apps try to call factoryReset to do networking reset, it
will result in updating the setting in SettingsProvider.
ContentProvider will verify if the package name of the caller
that initiated the request being processed on the current thread.
The package should belong to the calling UID. The setting update
started from the ConnectivityService context, so the package will
be android but the calling UID will be the calling app. It will
cause a SecurityException. The behavior is fine previously as its
known caller(Settings) shares system UID. But it will be a
problem for other callers, such as CTS. Thus, clear the identity
since the necessary permission check should be examined at the
top of the method. The following actions should be fine to be
proceed from the system itself. Also replace the user restriction
check via hasUserRestrictionForUser with the UserHandle created
from the calling uid to ensure it's verified with correct user.
Bug: 186061922
Test: Factory reset from Settings
Change-Id: If2dd69f702a1eafff331f9e71f6b92aeadfb715d
This grants the shell app the SUGGEST_EXTERNAL_TIME permission needed
for the TimeManagerTest (CTS) to invoke the
TimeManager.suggestExternalTime() method during tests.
Bug: 184947690
Bug: 177079827
Test: See associated cts change
Merged-In: Ia1995ec9503dbd2b12e0b5b5f92a96e02f85beec
Change-Id: Ia1995ec9503dbd2b12e0b5b5f92a96e02f85beec
The txt was previously referencing VcnGatewayConnectionConfig.MIN_MTU_V6
which isn't part of the API. The API txt should be complete on its own,
so inline the value instead.
Bug: 188527836
Test: m checkapi
Merged-In: Ideb34ab78c9a8fc4d589e58e810316b6f36b7a43
Change-Id: Ideb34ab78c9a8fc4d589e58e810316b6f36b7a43
Adds some clarifications for how UCE operates
in Android 12.
Bug: 188580687
Test: docs only change
Merged-In: I139455c286378ccfac876014656f8d3177bdba9d
Change-Id: I139455c286378ccfac876014656f8d3177bdba9d
1. Declare the constant events for loading and updating SIM contacts.
2. Introduce radio HAL capability to control the SIM phonebook feature.
Bug: 23044962
Change-Id: Ice0cc1cddc832b5ae0f272348503e28842fccbb6
Merged-In: Ice0cc1cddc832b5ae0f272348503e28842fccbb6
If someone is trying to cherry-pick back to aosp, don't force them
to use --no-verify, allow it.
Right now, the only form of cherry-pick allowed is:
cherry picked from
Test: Ran on a commit with the message and without and observed that
Test: with the cherry pick message, no error, without, error message.
Change-Id: I27581f782cdc1a1c4fa207a3aae392c0d434eb5a
In device booting, PackageParser2 uses a thread
local ParseTypeImpl obj as shared result and reset
it before parsing everty time. But it doesn't reset
the target sdk version, which could make deferError
returned unexpected error, cause apk scaned failed
and deleted by the system.
Test: atest com.android.server.pm.parsing
Change-Id: Ie6fbc4b79e94943c9282206b1ef6d20b4129fa0b
Signed-off-by: liulvping <liulvping@xiaomi.com>
This CL updates ConnectivityService to check location permissions for
ConnectivityDiagnostics callbacks last in the permission check process.
This minimizes misattribution of location access for networks that an
app is not administering.
This CL also updates ConnectivityDiagnosticsManager documentation to
clearly state that location permissions are required in order to receive
callbacks.
Bug: 187310575
Test: atest ConnectivityDiagnosticsManagerTest
Test: atest ConnectivityServiceTest
Change-Id: I2dbeddac6273e2392ccaeae51a1c7776d6d3da75