- Add definitions for the front bottom channels. The name
of the definitions are standardized in ITU-R BS.2051-1.
- Add definition for 13ch mask which consists of surround 5
channels, top 5 channels and bottom 3ch channels. This
channel mask is ideal speaker layout used by Sony 360
Reality Audio. Virtualizer can place individual sounds in
a 360 spherical sound field from these channels on any
headphones.
Ignoring checkstyle warning, "'|' should be on a new line",
to keep existing codestyle.
Bug: 185100731
Test: atest AudioFormatTest
Test: Play wav with 13ch mask after OUT_CHANNEL_COUNT_MAX to 24
Change-Id: I2b4deaac740a08ae3b1b8d8453650a876e2d6206
Change https://r.android.com/1667508 adds nullability annotations to
the core platform APIs which broke this code with the error:
javadoc: error - In doclet class com.google.doclava.Doclava, method
start has thrown an exception
java.lang.reflect.InvocationTargetException
com.sun.tools.javac.code.Symbol$CompletionFailure: class file for
androidx.annotation.RecentlyNonNull not found
Bug: 183938110
Bug: 185929373
Test: m checkbuild
Change-Id: I83e3071f851720a9f719cb226f0e84fd731a8f37
Merged-In: I83e3071f851720a9f719cb226f0e84fd731a8f37
- Add PowerManager.userActivity when user uses udfps to authenticate
so the screen won't turn off prematurely
- When the udfps-bouncer is showing, tapping outside the udfps view will
show the regular pin/pattern/password bouncer
Fixes: 184927116
Fixes: 182500156
Test: atest SystemUITests
Test: manual
1. enroll udfps
2. go to locked lock screen
3. double tap power button to bring up camera
4. tap on camera gallery (lock icon on image, bottom right)
Observe: udfps is highlighted; tapping outside udfps area brings up
regular bouncer
Change-Id: If01ee16647499fc2cf73afe527053cd6830a50ed
This change fixes a NPE when the VcnGatwayConnection attempts to print
for a null underlying network. Additionally, it also prints the existing
configs in order to better identify whether a VCN config is failing to
be privisoned, or failing to start.
Test: manual testing
Change-Id: I44d65633364a5f16d75519cead6729969eb1c06f
* changes:
Switch to using NetworkScore instead of legacy integer
Remove use of network scores, and provider IDs in VcnNetworkProvider
Improve dump detail
Disable INTERNET/DUN when mobile data toggled off
Remove hidden connectivity method access in FrameworksVcnTests
Pass dozeAmount values to the smartspace library to allow the lib to
make decisions regarding content on both AOD and Lockscreen
Fixes: 185598979
Test: manual, multiple smartspace cards
Change-Id: Ic7bc2ba238b22794a33e6db18c1aae0fa7c96e0b
This reverts commit ad1a153a63.
Reason for revert: Breaking 'Recently Dismissed' in notification history
Change-Id: I5393435e39bee2a41c9a48ea0f0d0bceacf45126
Fixes: 185581924
This adds background protection (and animates that background protection along with the ringer drawer), as well as updating sizes and colors to match the latest spec.
A subsequent CL will apply these changes to landscape.
Bug: 171441100
Test: manual
Change-Id: Ie14aa4477dcaf29435e3e13b07a695261a4af690
Remove references to Settings.System.DATE_FORMAT and mark it as clearly
deprecated.
It was probably made obsolete some time before kitkat. There were still
some references in view code up to lollipop (removed in change
Ib77a8e7727d027cae39d5e6f431cac1d1ff8a121). During marshmallow / nougat
there were no references, then references were added in backup code in
oreo. This change is intended to make it more obvious that this setting
is obsolete.
Bug: 185884644
Test: build only
Change-Id: I12441541bc3ca0e012cee64d4c784a0ce8233715
The check shouldCreateCompatDisplayInsets will catch any
apps that are eligible for size compat mode, and apply sandboxing
to them.
If an app is in letterbox only - and is never eligible for size
compat mode- then the app handles resizing and multiwindow mode.
We can assume, since it has explicitly declared it is resizable,
that it will use the Display size APIs correctly.
This decision is consistent with test results, as well, which only
shows apps in size compat mode benefiting from sandboxing.
Bug: 185456980
Test: atest WmTests:SizeCompatTests
Change-Id: I4b66454b3515738554c63cffe73e2f0500889cf6
Sometimes it's important that the system create PendingIntents that are
owned by their target app, rather than by the system itself. Make that
possible, and use them in the Notification auto-grouping mechanism.
This makes the auto group Notification's undering PendingIntent how has
the same capabilities as the app whose notifications it elides, rather
than having the system's own capabilities.
Along the way, build the PendingIntent mutability-check exception string
only when it's going to be used, not every time any PendingIntent is
created.
Bug: 174243774
Test: atest CtsAppTestCases:PendingIntentTest
Test: atest CtsAppTestCases:NotificationManagerTest
Test: atest NotificationManagerServiceTest
Change-Id: I5ec03706bc439d305b0093a1ee9c5d381024029c
Camera devices meeting performance class requirement will not advertise
JPEG sizes smaller than 1080p.
Test: Build doc
Bug: 184687664
Change-Id: If9a76cb7f80c01a43cd5ba9e91c1f543b81d4d54
Update SettingsProtoDumpUtil / secure.proto to reference the new (user
scoped) location_time_zone_detection_enabled setting that has been added
for S. This has been added in a "DateTime" message to reflect the
SettingsUI structure.
For consistency with secure.proto and the settings strings, global.proto
and the associated SettingsProtoDumpUtil code has updated to rename the
"Auto.time" and "Auto.time_zone" proto fields to "DateTime.auto_time"
and "DateTime.auto_time_zone". This is a binary compatible change as
the field IDs have not been changed.
Note: The "time_12_24" and "date_format" settings, which are user-scoped
settings from "Settings.System" have been left for a future release
besides some minor docs improvements. See bug 185884644.
This change also improve the docs for settings that are associated with
date and time.
Bug: 151304765
Bug: 185884644
Test: build / treehugger
Change-Id: If2daf3f530bd1add7a0a5cc3260221ea3ad8952d
This CL resolves API reviews on system APIs on MediaRouter2.
1) It checks permission when registering the MediaRoute2Manager
in system server. Therefore, app cannot bypass the permission
checks via reflection.
The system api calls will be no-op without permission.
2) It adds @RequiresPermission annotations to related APIs.
Also, this CL changes the required permission
from MODIFY_AUDIO_ROUTING to MEDIA_CONTENT_CONTROL,
as the media routing can be applied to video, not only to audio.
Note that MediaRouter2#getInstance(Context, String)
does not throw SecurityException anymore.
Bug: 183428114
Test: atest android.media.cts.MediaRouter2Test
atest android.media.cts.SystemMediaRouterTest
(MediaRouter2ManagerTest is already broken, and
that will be handled out of this CL.)
Change-Id: I55013a5b4b954ca1c8e2adb586f49f01103563db
Remove CarrierBandwidth system API. This should have been removed when
LCE system API was added.
Bug: 184396924
Bug: 180434672
Test: atest -c PhoneStateListenerTest
Change-Id: I4d3f9e6f5a62d40cdb193a0f20673a773eb3d8b0
