getMessagesFromIntent with default SMS subId log is shown from
AppSmsManager for MT SMS always since an intent without subId info is
delivered to AppSmsManager first.
It might be confusing when checking MT SMS log for multi-sim devices.
Bug: 161156506
Test: MT SMS and Check log
Signed-off-by: Taesu Lee <taesu82.lee@samsung.com>
Change-Id: I66da0d5d9802c4427572cb1674be452582066450
Moved setting so we can use Tunable:
adb shell settings put secure qs_media_resumption 1
If setting is changed, removes all existing resume players
Bug: 154039093
Test: manual
Test: atest SettingsProviderTest
Test: atest com.android.systemui.media
Change-Id: Iad056fbad4520cfe762d9e9f5ed62d38ea1117b1
If a carrier-associated app is added to the system image after the
device is initially launched (e.g. Q -> R OTA), the logic to disable
apps without a corresponding SIM will not run, leaving the app in an
enabled state in more cases than there should be.
To safely account for this, we only reevaluate on SDK change for apps
whose addedInSdk value falls within the range since the last time we
evaluated carrier apps' statuses. Apps that set lower (or higher)
SDK versions are ignored. We choose *not* to use minimum or target SDK
version here because it's more likely to change with each OTA /
prebuilt, which could cause unintended disable operations (or lack
thereof).
Bug: 154872019
Test: manual, QA, atest FrameworksTelephonyTests:CarrierAppUtilsTest
Change-Id: I97ddfa03f34e7d00e66ce7cd508d6d2a5e83fbc2
ETWS primary/secondary flag needs to be saved in the
database in order to perform duplicate check later. Used the
hardcoded database column name because Android R API freezes.
Will remove the hardcode in the next Android release.
Fix: 157699377
Test: CtsTelephonyTestCases & CellBroadcastServiceTests
Change-Id: Iedec92a1f435f60ceb9f36637a1718adbbd7e2ae
This property was only used by Automotive and was added on frameworks/base
because it used be accessed by a class on frameworks/opt/services/car, but
it's now only accessed under packages/services/car (so it was moved to
CarSettings).
Test: atest SettingsBackupTest
Bug: 156567994
Change-Id: Idaff4a249600517c5250cd3821d75ce85fc9eeee
And fix a bug with toggling priority I noticed while testing
Test: atest
Fixes: 157988478
Bug: 155490513
Change-Id: I8f5a6076ed2aa6c862a187bac15f3ad9af3cd141
Exempt-From-Owner-Approval: dianne approved, but from her android.com account instead of google.com account
Test: compile
Bug: 156757711
Merged-In: I330b8cc5aeb14ebcc15fb88c605ac72770497040
Change-Id: I330b8cc5aeb14ebcc15fb88c605ac72770497040
In some situations the activity start Intent
Settings#ACTION_WEBVIEW_SETTINGS might not resolve to any launchable
activity. Make sure this is reflected in its reference documentation.
Bug: 157267574
Test: atest CtsSystemIntentTestCases
Test: atest CtsSystemIntentTestCases --user-type secondary_user
Change-Id: I59289cab764d06cb74e35722bd26986a3159e5d6
This is an experimental property on Q and doesn't need anymore.
Exempt-From-Owner-Approval: cherry-pick
Bug: 154885206
Test: N/A
Change-Id: Ibb09e17703fbc95fe41542d335311b68553502a0
Merged-In: Ibb09e17703fbc95fe41542d335311b68553502a0
(cherry picked from commit dfafe03cb4)
* changes:
Resources and strings for freezer settings
Settings option to enable/disable the app freezer
ActivityManager API to check availability of app freezer
Adding a master on/off switch for the new bucket such that when it's off,
apps aren't be put into the bucket and any apps already in it are brought
out.
Bug: 155670438
Test: atest FrameworksServicesTests:AppIdleHistoryTests
Test: atest FrameworksServicesTests:AppStandbyControllerTests
Test: atest SettingsProviderTest:SettingsBackupTest
Change-Id: Iaeabefa14cbaa2d07a13555ecbc29e6fbf11a29c
The new setting option allows for a local configuration to override the
Device Config flag. Device Config and experiments will be honored by
default.
Bug: 155465196
Change-Id: I978a7b6bd75d9daab3fafed58b7f3c6417e0adab
Test: the option is correctly read and written by the companion CLs
These were previously being suppressed by doclava but with this change,
all failures are fixed and the suppression logic has been removed.
To fix the issues, there were a few possible changes made:
- broken reference to a public API (such as incorrect parameters): fixed
- unnecessary @link inside an @see tag: fixed
- @see referring to an @hide or @SystemApi: reference removed
- broken references to inner class constructors
- worked around by fully qualifying the constructor
Bug: 6963924
Test: make doc-comment-check-docs
Exempt-From-Owner-Approval: cherry-picked from master
Change-Id: Ifbdce2de96cdffa560bd90f549fa7184d1f9af85
Merged-In: Ifbdce2de96cdffa560bd90f549fa7184d1f9af85
(cherry picked from commit e0624c7a40)
These were previously being suppressed by doclava but with this change,
all failures are fixed and the suppression logic has been removed.
To fix the issues, there were a few possible changes made:
- broken reference to a public API (such as incorrect parameters): fixed
- unnecessary @link inside an @see tag: fixed
- @see referring to an @hide or @SystemApi: reference removed
- broken references to inner class constructors
- worked around by fully qualifying the constructor
Bug: 6963924
Test: make doc-comment-check-docs
Change-Id: Ifbdce2de96cdffa560bd90f549fa7184d1f9af85
Merged-In: Ifbdce2de96cdffa560bd90f549fa7184d1f9af85
Before, CTS test used WindowManager#shouldShowSystemDecors() to set show
system decorations after overlay display launched, which wouldn't enable
system decorations without relaunching. Now, we can set those flag
before display launch similar to what VirtualDisplayHelper does.
Bug: 153624902
Bug: 154158053
Test: atest CtsWindowManagerDeviceTestCases:MultiDisplayClientTests
Test: atest CtsWindowManagerDeviceTestCases:MultiDisplaySystemDecorationTests
Change-Id: I83c21a74c722a23ac77141305a08d9f67c5bbcf0
