So the written time is closer to when the app is launched.
Bug: 187043447
Test: Launch app and check the tid of log.
Change-Id: I2a1a067b1c92ae427bf0acfe9b574083ebeb601a
Like the jar stubs, the doc stubs need modularization to avoid depending
on module sources and instead being assembled by merging the doc stubs
of the constituent modules. This will allow generating e.g. the lint
database, annotation zips, and the documentation itself from prebuilts
(which in turn allows mixing e.g. non-updatable R with the latest
modules).
Move the defaults for the non-updatable jar stubs to the shared bp file
and reuse it for the non-updatable doc stubs, and add two targets for
the public and the system stubs.
Bug: 186197911
Test: m android-non-updatable-doc-stubs{,-system}
Merged-In: Ic2cef748c42c141ea42b8cd7b4afd7ee78a1399d
Change-Id: Ic2cef748c42c141ea42b8cd7b4afd7ee78a1399d
Like the jar stubs, the doc stubs need modularization to avoid depending
on module sources and instead being assembled by merging the doc stubs
of the constituent modules. This will allow generating e.g. the lint
database, annotation zips, and the documentation itself from prebuilts
(which in turn allows mixing e.g. non-updatable R with the latest
modules).
Move the defaults for the non-updatable jar stubs to the shared bp file
and reuse it for the non-updatable doc stubs, and add two targets for
the public and the system stubs.
Bug: 186197911
Test: m android-non-updatable-doc-stubs{,-system}
Change-Id: Ic2cef748c42c141ea42b8cd7b4afd7ee78a1399d
Had to support both old/new UX for PIN for a while. Cleanup the
unneeded code and simply the ripple.
Fixes: 187340770
Test: atest KeyguardPinBasedInputViewControllerTest and visual check
Change-Id: Ie12cd93c7aaba5a3ef172792a5dd2a41f2196447
This corrects the wording of the clipboard access notification
as per UX specification. The current wording is "<app> pasted from
clipboard". It should be "<app> pasted from your clipboard".
Bug: 179469804
Test: Build and flash, copy and paste and check wording
Change-Id: I965690515c9c1fcf92553992a5d67507d0f1b855
The crash is because when the IME switch dialog created window token
is removed, it should switch back to listen to ImeContainer.
However, previous CL use the wrong API findAreaForToken, which only
finds the DisplayArea.Token under mAreaForLayer list.
In this scenario, we cannot find one because ImeContainer is moved to
its sub-RootDisplayArea.
This CL updates the naming and add more javaDoc to prevent from
confusion.
Test: atest WindowContextListenerControllerTests
Test: manual - repro steps in b/186366728#comment1
fixes: 186366728
Change-Id: I50d3247b0a158e83d09be893d31802d673a60697
Remove @GuardedBy on a final, immutable field as it is causing
errorprone warnings on a work-in-progress commit.
ContentProviderHolder.mUri is accessed in multiple places without
holding mLock, and it is final and documented as immutable so should be
safe to access without mLock. This commit should reduce ErrorProne
warnings now and in future.
Bug: 185786624
Test: build / treehugger only
Change-Id: Ic7fbe550ff6f538f336cfb859f66daa94844ca28
- mainline module team have concern about backward compatible on
old platform.
To reduce the change, we move most of change for Android S to v31
- Rename resource name to avoid build conflict in another path.
Bug: 182179573
Test: manual
Change-Id: Ic377c8cde7794e9088dad8b066ae7a9c377f8d5f
Otherwise when entering task lock mode from split-screen, the
request from WindowManagerProxy#applyDismissSplit is ignored.
That causes launch root to remain and affect new launch tasks.
Bug: 186764983
Test: MultiWindowTests#testDisallowHierarchyOperationWhenInLockedTask
Test: 1. Enable App pinning
2. Enter split-screen mode
3. Pin the task on secondary-split
4. Unpin the task and launch other new task
The new task should fill screen bounds.
"adb shell dumpsys activity a | grep mLaunchRootTasks"
must be empty.
Change-Id: I890a9e1234b11772f4183168e085b75d31859e20
Consider the situation where there is a translucent or non-fullscreen
activity in foreground and a middle activity that is going to be
finished. The black background will show below the foreground activity
if the middle activity is in STARTED state because the activity in
STARTED state was not treated as visible.
Another case is that the task of non-fullscreen activity is different to
the middle activity. We can't find any resumed activity from the task of
the middle activity.
This CL treat both PAUSED and STARTED activities as visible and update
the visibility if current activity is opaque.
Also clean up some dead code in Task and ActivityRecord.
Bug: 172837736
Test: atest WmTests:ActivityRecordTests RootTaskTests
Test: atest ActivityVisibilityTests
Test: atest ActivityLifecycleTopResumedStateTests
Test: atest CtsWindowManagerDeviceTestCases:ActivityLifecycleTests
Test: atest MultiDisplayPolicyTests
Change-Id: I43618e34383409b4805942b1923f1281f4226b1c
During R development cycle, default entitlement check is changed from
silent to showUI(start activity) in TetheringRequest. So start hotspot
by systemui is changed from silent to trigger UI. Expcility set
entitlement back to silent check in systemui for better user experience.
Fix: 182724427
Fix: 169493230
Test: atest HotspotControllerImplTest
atest CtsTetheringTest
on/off hotspot by systemui
Change-Id: Ida1964e28a7b2d0f1a1394e5de2ec437e0bc420a
Under specific conditions, parceled list can be written in such a
way that writing of new list starts when destination parcel is
just above MAX_IPC_SIZE. In that case "0" is written to parcel to
indicate that there will be no inline items written and writing of
the list will start with extra items.
When unparcelling such list, listElementClass is not determined and
stays equal to null, because it only can be determined if there
were some inline items read first, before switching to extra.
This leads to random unparcelling failures with the following
error message:
Can't unparcel type <typename> in list of type null.
Test: manually verified
Bug: 186193371
Fix: 151481291
Bug: 156514418
Fix: 169191099
Change-Id: I849bf46158b6d9b109139b19b93a6a1ba16ecc77
this private settings can be accessed from alternative API
SubscriptionManager.getPreferredDataSubscriptionId which requires
READ_PRIVILEGED_PHONE_STATE permission. Add additional permission
check for settings access to avoid any potential security holes.
note: the alernative API from SubscriptionManager is also a hidden
one, without the public alertnative API we have to handle app-compat
properly to avoid breaking apks targeting previous SDKs.
Bug: 172670679
Test: Manual
Change-Id: If527f375da33cc6c30c6513c82bf529209da277a
Use Bundle.putAll() to take both the bundle passed in to the
startActivity(Intent, Bundle) and also the new created ActivityOptions
bundle, so no extra info will be lost.
Test: rebuild and add log to make sure all bundle info are kept
Bug: 187471344
Change-Id: I802e17893b86fd4eacb812b4a7ab20b5167790fe
- Don't show the privacy dot when the shade is expanded.
- Rework the privacy dot view controller to use a view state + resolver
so we don't miss states
- Add a way for ThreadFactory to create Executors given a Looper
Test: atest SystemUITests
Bug: 177323724
Bug: 186039244
Change-Id: I272eb3135fe6a53dfb5e7aac8a1b165bc4ad3d43
