homescreen
A shortcut can be added by any app as INSTALL_SHORTCUT is a normal
level permission. But the intent is actually launched by the launcher
app which can have other permission as well.
> When adding a shortcut from the broadcast, verify that the intent does
not require any permission
> When adding a shortcut using the two-step drop process, verify that
the source app also has the permission to create such a shortcut
Bug: 30778130
Change-Id: I33a391bc0af81248aaff4459aaa79d1adc77926b
(cherry picked from commit fb5096d07b)
- Instead of using reflection to check if N is present, we now use
Build.VERSION.SDK_INT >= Build.VERSION_CODES.N.
- Other places that used reflection to use N APIs have also been
cleaned up.
Bug: 22942492
Change-Id: Ia7b981cae375e800bcc8f0c54aec48e0c8c076da
-> When BubbleTextViews were being recycled, the RecyclerView was clearing the
AccessibilityDelegate. Ensure that this is reset by the adapter when a
BubbleTextView is reused.
issue 25948877
(cherry picked from commit 6e92f05314)
Change-Id: I5f0773333186e5ffe4600f49330b4390cd3fbaeb
-> When BubbleTextViews were being recycled, the RecyclerView was clearing the
AccessibilityDelegate. Ensure that this is reset by the adapter when a
BubbleTextView is reused.
issue 25948877
Change-Id: I95dd21bfdcd602a67925d1b8f06e6ca92d1d7203
(cherry picked from commit 6e92f05314)
The default strict mode policy in NYC cause death penalty when
when sharing file URI in intent. This causes launcher to crash
for users who have shortcuts of images and documents on their
homescreen.
Bug: 28853579
Change-Id: If84cd5ff732713aaff5d3164edf428c8b4233ea2
(cherry picked from commit 85fc55a976)
am: 0d86a8dccf
* commit '0d86a8dccf6557587eb3abae1bb3573e2c40c12c':
On some "non-standard" devices, load label can cause a security exception due to modified platform code
Change-Id: I7d65f2f39353c50a43334709f8b3bf970969a68c
> Sending unboundX to the overlay which is the total untranslated X and not just deltaX from last frame
> Handling overlay callback and translating workspace accordingly
Change-Id: I3bd8d9efac738e9ce131758f0e5ff1b9c1d6a8fc
Overlays are supposed to use their own UI and not interfere with the
Launcher UI. If the UI needs to be put inside the Launcher, use customContent
instead.
Removing some unnecessary and unused methods related to overlays
Bug: 25993953
Change-Id: I4d715cdee04eb7b0ebef673d885a4258c521ff1f
Since I62963d225e6ea5d2ec9d8ebc8a6d73099f5d6c7f, we have disabled
selection action mode in the folder-name editing mode on Launcher,
mainly because it messed up the view on phones. However that is no
longer the case in Android M and later, where floating action mode
is available.
With this CL, we start relying on the default floating action mode
in Android M and later.
Bug: 22210697
Bug: 28526978
Change-Id: Ie19e7844194acd86cdb013254a1923f0b1d78e11
(cherry picked from commit 1bd9a430ed)
b/27978139
Background: onSaveInstanceState assumes that state of the launcher
is being stored after screen is all binded. However, due to ActivityStack
bug in nyc, onCreate is called twice when the device is rotated while
the Launcher is in the background. The first onCreate fails because
our AndroidManifest is setup with nosensor field and hence doesn't support
Landscape. During this first onCreate, screen is not correctly bound
and incomplete workspace state is saved. This results in the second onCreate
to load wrong screen id.
Fix: While the workspace is still being bound, mSaveState is not reset,
which has the correct values. SaveInstance should use this state
instead of incomplete workspace state.
Change-Id: I5b80f584e55769b2a8ffa292f5daa4705c20086d
In battery saver mode, animations skip directly to the final values.
For LogDecelerateInterpolator, however, an input of 1f outputs an
interpolated 0.99999994. This meant that the FirstFrameAnimatorHelper
didn't realize that this was the last frame, and messed things up.
Since any interpolator should return 1 on an input of 1, we just
short-circuit in that case for the log interpolators.
Bug: 25666809
Change-Id: I60527e3758cea383fbcf50acb95460a7bd9ab43c
The flag we check for package suspension is reused by a hidden constant
prior to N, so the flag should only be checked on N or later system.
Bug: 28390176
Change-Id: Ia28f62991cc2cd1b5d2cc27a5f11f7edca0ba02b
change for launcher when going in/out of another app
Bug: 27600678
Change-Id: Ic873faba99c539025769d911bc7b0a4fed629cd7
(cherry picked from commit 784f9c3996)
am: d797327 -s ours
* commit 'd797327b79c5ded53f698201af5abb7d779ddfa9':
[DO NOT MERGE] Address some spacing issues in all apps related to new support library
Change-Id: I8c38d1c542f1143dd7c9f330795229b4a03c7ac8