am: d5ef1ef028
* commit 'd5ef1ef028d5d7e529746206aa72f4cd65edd55b':
Docs: Added new Whitelist feature to Data Saver for DP3 (Part 2)
Change-Id: Ic32c9e030b2a287bba161716f67788e740b78433
When animation is started with saved surfaces, app may decide to
remove one of the child windows during early animation and replace
it with a new window. This causes the app below (usually Recents)
to show through for one or more frames.
If we started animation early with a window, delay removal of
that window until the app is allDrawn in the "traditional sense"
(i.e. allDrawn without using any saved surfaces).
bug: 28742353
Change-Id: I4ef663a947b737aae96c3ccfe13a9f4c1d0567f0
Currently every focus change causes a freeform window to jump
for a few frames. The size of the jump is equal to the difference
in inset size (which is derived directly from the window elevation).
This problem goes away for most real use cases if the insets are
not allowed to decrease.
Bug: 28318973
Bug: 22668382
Change-Id: I77ca440a7d9c89cc4d45e6667bf37da94a5c8a9a
The documentation incorrectly states that, "[insertWithOnConflict
returns] the primary key of the existing row if the input param
'conflictAlgorithm' = CONFLICT_IGNORE". Unfortunately, SQLite does
not provide such functionality.
Close: https://code.google.com/p/android/issues/detail?id=13045
Signed-off-by: Steve Pomeroy <steve@staticfree.info>
(cherry picked from commit 8fc3144fa5d9fe3a6c7fb6de80cb34d5cafabc05)
Change-Id: I89e56428e612d667259744e2bc3df124e5a2aa0e
Correct and clarify the documentation for ContentValues.
Signed-off-by: Steve Pomeroy <steve@staticfree.info>
(cherry picked from commit 1276b5f29ed6f889e9691cf296fd9911958895c1)
Change-Id: Id6f4e93dcca64dd41daeb4066d804ff173f4747b
Previously, divider was adjusted for IME when IME window visibility is
changed. However, IME size can be changed without changing IME window
visibility. For example, when hardware keyboard key is pressed to show
emoji layout.
This CL checks if IME height has been changed and adjust divider position
properly.
Bug: 28389933
Change-Id: I9a561bd4796a0513c8b5c493884946883f160907
This CL is a continuation of CL 1025444.
Bug: 28143514
Change-Id: I43feb2fec6c9d57d6ebb35a388ecaea3a713876e
Original-Change-Id: I00164a740bcc19b5ba08b517023cca11f4373680
Do not post app token with the timeout message, instead put the token
in a list and post empty message only.
bug: 28744782
Change-Id: If809d8ee16bcc31067f25ae5696b62d09ea4b864
Add Bluetooth service to the interesting native processes to dump
during watchdog abort and ANRs. This may help if the process gets
wedged and cannot react normally to Java-side ANR dump requests.
Bug: 28658141
Change-Id: I788b7c299cc95748fdcddaa2be1d0e2d78f25ef1
Is some cases, the adapter is changed before the AnimationListener is
fired. Thus we need to remove the task without relying on position.
BUG: 28703989
Change-Id: If5cfe8589bbf6938c6e57e8e4c7bd54de6e3bd68
This CL fixes 2 bugs in View's addFocusables implementations.
1) addFocusables(list, dir) method was always returning focusables in
touch mode even if the device is not in touch mode.
2) addFocusables(list, dir, mode) was not respecting the provided mod.
Bug: 28745577
Change-Id: I9b9e5af27f8f5b1bb3cc601584fdad7c73e54a5d
When app has several windows and activity is relaunched + we try to preserve
main window - other windows just stayed around until removed by timeout or
replaced by app. There was a problem when one of the windows registered
broadcast receiver and set its own timer to remove it. In this case all
receivers were removed by framework because windows were considered leaked
and apps' timer caused crash when trying to remove registered receiver.
This CL removes all windows expect the main one, which we're trying to
preserve in this case.
Bug: 28337135
Change-Id: Ib8790cc8c61801f11d871ba3803bb0ebc3d3be01
Pin key files into memory to prevent having to fetch from flash
after boot. Improves system performance by preventing page cache
thrash. Retrieves files from a device-specific overlay to allow
specialization.
bug 28251566
Change-Id: I8532f52bd70271794dd7576976d13a524849ce7b
Previously the children container wasn't fading out.
In addition was the child added to the wrong overlay leading
to completely wrong animations for the children.
Change-Id: I1ae395dc02cecb8629e509dfb55870f9c79d7854
Fixes: 27719756
