I'd like to test other things (like tap makes the IME move), but to do
that means replacing the mock with a proper fake. That can come later,
but this at least tests that the flagging works correctly.
The changes between this and
commit cae34b8e22 is the bouncer height is
now measured using wrap_content, so the placement can be controlled
properly by the outer View (as the position of the bouncer changes
depending on the size of the screen).
This reverts commit cae34b8e22.
Test: Included
Bug: 170858298
Change-Id: I18428a6df9abf0e8e37c1c179be6843e4eee793c
The log "Screen frozen for" is too rough to know how much time
the client windows spend. By adding the logs that are closer
to the entries of notify/response, it is easier to break down
the bottleneck of screen frozen time.
Also:
- Move log "Orientation start waiting" to after IWindow#resized.
So it is clearer to know when the redraw request is sent.
- Consolidate activityRelaunched to finishRelaunching because
the operation should belong to ActivityRecord.
Bug: 178472794
Test: Rotate device and check log "finishDrawing".
Change-Id: I07d77db1f36d653a437d9543b520522a13e12efd
For example: launch a landscape activity while device is portrait,
and then launch another portrait activity before previous transition
is done. If the landscape activity is destroyed before sending the
fixed rotation adjustment for restoration, the adjustment is always
retained by client side app. That causes the Display objects
associated with application Resources to always return rotation from
the adjustment.
This change notifies client to clear the rotated adjustments if the
the display won't be rotated by the next top activity before the
transition is done, so the app can get the correct rotation in time.
The transform will be cleared at the end of transition animation so
the closing animation won't jump cut with rotation change. E.g.
launch an activity in different orientation and press home or back
key before the launch animation is finished.
Also simply a bit for the path of clearing fixed rotation state to
avoid sending duplicated adjustments.
Bug: 161519202
Bug: 168263090
Bug: 177390830
Test: DisplayContentTests#testClearIntermediateFixedRotationAdjustments
Change-Id: Ica074604df3e74eabbdef931531abe51855103e5
Merged-In: Ica074604df3e74eabbdef931531abe51855103e5
This CL moves suggestExternalTime method from TimeDetector to
TimeManager. Eventual goal is to make suggestExternalTime a System
API. Ideally all time related system APIs live in android.app.time
hence the move.
Test: atest android.app.time
Change-Id: I464545e77fdf68c35c8a338bfe5ac8b7535bc3e6
Bug: 177079827
