Revert "Adjust monkey to changed internal APIs"
Revert "Test featureId is correctly used in startActivity"
Revert submission 10111030-activityStarter_featureId
Reason for revert: presubmit test breakage
Reverted Changes:
Ic7056b492: Activity start: Send featureId from context->AppOp...
I8e2a07da7: Adjust monkey to changed internal APIs
I7a6af6fb1: Test featureId is correctly used in startActivity
Change-Id: I48c55a962c990b22ea49e923baa7c73b121d179b
The expected usage pattern for noteOp is to get the
Context#getOpPackageName() and Context#getFeatureId() in the calling app
and the call
noteOp(callingPackageName, Binder.getCallingUid(), callingFeatureId)
As the featureId parameter is new this parameter has to been piped all
through from the ...Manager classes running in the app all way deep into
the bowels of the system server.
There is a special featureId==null for the "default" feature. This is
used in two cases:
- In case the system server (packageName == null || packageName ==
"android") makes a call
- In the case there is no caller. In this case I left annotations in the
code to make clear that the default feature is used
Raw binder interfaces (defined in AIDL files) are not supposed to be
used by apps. Still historically this has happened and we ended up with
@UnsupportedAppUsage tags in these files. Also AIDL does not support
two methods with the same name but different parameters. I.e. in the
case when I had to add a paramater to a method tagged as UnsupportedAppUsage I
- created a new method ...WithFeature with the additional paramter
- set a maxTargetSDK for the old method and mention the public API to
use in the deprecation method
This is really not pretty. Once there is no more app using the old
internal API this hack can be removed.
Additionally this change removed all internal calls to
AppOpsService.noteOperation and AppOpsService.checkOperation and
replaces them with the public API equivalent. This sometimes means to
move the resolution of the mAppOpsManager to be lazy.
Exempt-From-Owner-Approval:: Just piping through arguments
Bug: 136595429
Test: atest --test-mapping frameworks/base/services/core/java/com/android/server/am/
atest CtsAppOpsTestCases added test to cover activity start
atest WmTests
Change-Id: Ic7056b492cb1c9a79158e6c2b4864898a0eb5b2a
Add SystemConfig parsing tests for component-override. Also fix an
issue where component-override causes the next tag to be skipped.
Bug: 148297212
Bug: 138458609
Test: atest SystemConfigTest
Change-Id: Ifc0d02f705f3f0ffe710729310779a1d41226acb
Logs notification cancel only if the notification was in fact posted.
Uses the UiEventReported framework. Tweaked that framework to handle
null InstanceIds better.
Bug: 146488473
Test: atest NotificationManagerServiceTest BuzzBeepBlinkTest RoleObserverTest
Test: statsd_testdrive 90 244
Change-Id: Ifd6946ce64c3a09f8cac436bb7087ec56521486c
Basically we configure all the lib files inside Incremental Service,
e.g., create lib dirs, make lib files, extract original
lib file data from zip and then write data to the lib files on incfs.
Test: manual with incremental installation
BUG: b/136132412 b/133435829
Change-Id: I7544d2e78bcf3bdd76ce4c0766ec31ff13fd2011
Even though the color can be changed by updating
Theme.DeviceDefault.ResolverCommon's colorControlActivated,
that also changes the background color when selecting a
list item in the resolver list. Instead, we change only
the tab-specific styling.
Fixes: 149085716
Test: manual
Change-Id: I9c3399828048ffe71db5e15d09c5cad1fd205d0d
So this can be used by other resizing not done by the framework (e.g.
PIP resizing done via SysUI).
Bug: 147361175
Test: Compile
Change-Id: I0010b292af5ea48e4303a4faaf9c0bbe49d5d64f
Root cause: can't click item to trigger function.
Goal: set clickable to true when legacy type service item is disabled status.
Bug: 148834576
Test: manual test
Change-Id: I4788711e49e507bdc50e3c29681d8461d3f5e1ef
Easier for follow up CLs to do make incremental-specific changes.
Test: atest CtsExtractNativeLibsHostTestCases
BUG: b/136132412
Change-Id: I69f05b4779fb229597fe3140bb117db28fbac938
Feature is present if ro.incremental.enable set to true.
Test: builds
Bug: b/136132412 b/133435829
Change-Id: I99ad307cbd3428e0b3964a369930658ee1c8ac0f
The public platform version no longer can be a codename, it is
always the most recently released platform. A new build property
and API provides either the offical version or the current codename
as appropriate. This will avoid breaking apps that look at the
platform version while development is under a codename.
Bug: 143175463
Test: manual
Exempt-From-Owner-Approval: Relanding change with zero delta in this project.
Change-Id: I4407df40151d884293fa9d301a401b65bedb5527
Root cause: should call corresponding function
Goal: using performAccessibilityShortcut function from AccessibilityManager
Bug: 148779579
Test: manual test
Change-Id: Ibc3fcb77e1aef54683328d1e7a71afabccffc523
Root cause: shouldn't speak "Double tap to activate" for disabled item.
Goal: set disable for the item.
Bug: 148834576
Test: manual test
Change-Id: I40a083ec4f7d18073dd46636719d6b64fb674f67
This change adds a VpnRunner superclass to the LegacyVpnRunner in
preparation for the PlatformVpnRunner
Bug: 144246767
Test: FrameworksNetTests passing
Change-Id: I1b7da86d59c34f5d8c1ac13fb621f2e5d3bf8d26
This CL adds support for a new feature flag
(notifications_allow_fgs_dismissal) that enables a user to visually
dismiss a notificationg that represents FLAG_ONGOING_EVENT or
FLAG_FOREGROUND_SERVICE into a new bottom section of the shade. Tapping
on the list items in the new section reinstantiates them back to the
shade.
In this CL:
- the new device_config flag + feature controller for it
- ForegroundServiceSectionController that can track dismissed FGS
notifications and then show them in its own decor view
- ForegroundServiceDungeonView that is optionally added at the bottom of
the shade
- Changes to the logic for NotificationEntry#isClearable to take into
account the new flag
Todo:
- Minify the dungeon view before first tap
- pin the dungeon view to the bottom of the notification shade
Test: atest SystemUITests
Test: adb shell device_config put systemui notifications_use_people_filtering false && adb shell kill $(pid com.android.systemui)
Bug: 136562823
Change-Id: I8359e8c3ad9de89cd867f5ac147d62e22b9cf816
* changes:
[NS A36] Add a test for lost trusted capability
[NS A35] Send updated scores to factories at the end.
[NS A34] Still more simplification
[NS A33] Unify changing the default network
[NS A32] More simplification
[NS A31] Simplification
[NS A30] Note linger out of the rematch loop
[NS A29] Call LOST callbacks at the end of the rematch.
[NS A28] Move setting the default network out of the rematch loop.
As part of statsd becoming a Mainline module in R, autogenerated
StatsLog.write() calls are going away and replaced by
*StatsLog.java
that is autogenerated for each module.
This CL replaces some usages of StatsLog with
FrameworkStatsLog.
Bug: 145952197
Test: m
Change-Id: Iaa2db34a7be4c3215f62cc36661ba8ac81656baa
As part of statsd becoming a Mainline module in R, autogenerated
StatsLog.write() calls are going away and replaced by *StatsLog.java
that is autogenerated for each module.
This CL replaces some usages of StatsLog with FrameworkStatsLog.
Re-landing of http://ag/10194708 .
Bug: 145952197
Test: m
Change-Id: Ie5dcc3c677c0f3667d6505a76b91c05649787fba
