When we tried CL[1] to fix Gboard Translation UI dialog dismissed that
keeping the served view when focused to the next window,
although we can skip starting new input when the window focused back as
the behavior of Q,
However, we overlooked in R, IME insets will rely on IMS#reportStartInput
to get the updated IME input target, which will out of sync for the above
case.
To fix this regression, we report the next window focus gain
to IMMS with WINDOW_FOCUS_GAIN_REPORT_ONLY when the next focused view is
same as current served view and the served input connection remains.
so that in IMMS side won't get StartInputFlags.INITIAL_CONNECTION flags
to set restarting as false when calling IInputMethod#startInput to IMS,
and in IMS side will still call reportStartInput to WMS for updating
IME input target without additional onFinishInputView callback to
client.
[1]: I8d4fff94ba9313b773bc27fcbd019cc88580d3e9
Fix: 152373385
Bug: 155781821
Test: atest CtsInputMethodTestCases
Test: manual, make sure Bug 155781821 comment #10 works:
1) Launch video call in Hangouts.
2) End call.
3) Click on the text box.
4) Expect Soft-Keyboard shown
Test: make sure not break Bug 148489857 and Bug 148788569, following
auto / manual test to verify:
- Auto: atest FocusHandlingTest#testKeyboardStateAfterImeFocusableFlagChanged
- Manual:
1) Build / install EditTextVariations
2) Select menu -> Direct-Reply, make sure Notification comes up.
3) Tap EditText on Notification, verify soft-keyboard is visible.
Change-Id: I45a9814d812ad906f417c24200fd4219959e2423
The offset was computed based off the offset represented by
the most recent historical file while we have to use the time
this file was written.
Also now we persist the history on reboot and shutdown,
significantly minimizing the possibility of data loss.
Added test API to emulate reboot of the history to allow for
precise and tightly controlled test to prevent flakes due to
boot time deviations.
Test: atest android.app.appops.cts.HistoricalAppopsTest#testRebootHistory
Fixes:156853195
Change-Id: I4142371f8bc2b1d710cc8c300e7e79cb03764c04
This revealed that we weren't initializing the nearby intent
from the original intent, so that's fixed too. This should
ensure that flags and extras from the original intent make
their way to the available and installed nearby component.
Test: Share (an image and a non-image) from DocumentsUI
Fixes: 155487375
Fixes: 155676993
Change-Id: If0c0b754a066b0ec439a866de3eae84caca7b793
Make sure the first and last Uids are valid exist in the sparse array
before removing the array range of which they are the boundaries.
If they are valid, but not exist, create fake elements to make sure all
the elemens in the range are deleted.
Bug: 157887803
Test: build
Signed-off-by: Alessio Balsini <balsini@google.com>
Change-Id: I3b5ddc499178163cb9b0e9cabbe4f3457ae34dad
It will be used by Automotive when the display is off.
Test: adb shell cmd voiceinteraction disable true && \
adb shell cmd voiceinteraction show
Test: atest CtsVoiceInteractionTestCases CtsAssistTestCases
Bug: 154011437
Change-Id: Ia87b0544b242c356c4f9180e250e2df54279803f
Currently, we show a "Couldn't take screenshot" error any time the
screenshot process disconnects. However, if the screenshot process
remains up, this can result in strange superfluous notifications,
where hours later the screenshot process gets frozen/killed due to
memory pressure, and we show the notification despite the user not
trying to take a screenshot at that point.
This change adds a check so that we only show the error notification
if the screenshot process is disconnected within the timeout period
(10 seconds).
Bug: 156064134
Fix: 156064134
Test: manual -- killed the process with 'adb shell ps | grep screenshot'
and then 'adb shell kill <pid>' to verify that the error notification
appeared, then made sure it did not appear post-change.
Change-Id: I2419634ad888300abc8b50aadab5888ce653e363
Otherwise we don't add the padding if we show the empty state
on the current profile. This caused a slight height jump when
swiping to the other profile.
Fixes: 158174328
Test: manual
Test: atest ChooserActivityTest
Test: atest ResolverActivityTest
Change-Id: I08c3f30716a8fb9a15e30088be6d274dc0869cac
