* commit 'c74e41973a74aa416e16aeadaa2f491153da26bc':
Restoring provider behavior for reloading app on old devices > For older devices, launcher will only reload in case of inserts with specific query parameters > For older devices, launcehr will notify content observers of any internal inserts > Chaning TAG for Launcher provider as max logging tag is only 23 characters
> For older devices, launcher will only reload in case of inserts with specific query parameters
> For older devices, launcehr will notify content observers of any internal inserts
> Chaning TAG for Launcher provider as max logging tag is only 23 characters
Bug: 23821706
Change-Id: I32891387612d967c41ddae848c43dc4b1de1b0e9
Since power save mode (introduced in Lollipop, also known as battery saver)
disables animations, the ReorderPreviewAnimation looks bad - instead of
displaced folders subtly and smoothly moving up and down, they violently jump
between up and down positions in rapid succession. Setting the animation to not
repeat in this case avoids this issue.
Bug: 23675090
Change-Id: I8149610af75e7023dca28a942b3447228083cd33
When "Wallpapers" is selected from the overlay, the current wallpaper parallax
offset is sent to the WallpaperPickerActivity as an Intent extra. The CropView
then uses that offset when previewing new wallpapers to ensure the preview looks
exactly the same as the actual wallpaper will when set.
Note that this fix doesn't seem to work for DefaultWallpaperInfo - that will
come in a future CL.
Bug: 23568800
Change-Id: I41c5bbbfdabfeb4e20d77e9b5804842a03211edf
- The regression was introduced in scroll bar changes ag/751628, but
unlike AllApps, the WidgetsRecyclerView can have an unbound model.
Bug: 23689784
Change-Id: Ibd3d5bcbafab0ada9a372fa00acaa45809ce720d
Using itemId instead of generating a new id for each item. This is because
if the process gets killed, View.generateId will get reset but we will still
receive the generated item id map in onRestoreInstance. This will cause
conflicts with newly generated item ids.
We wrap all the generated homescreen views inside a single sparse array. This
ensures that we do not cause any conflict with dynamically generated views in
other parts of the UI.
Change-Id: I6fe69c2e1dd463402f51222715fae31b9d4dd240
- This was due to us not re-attaching the thumb to the scrollbar after
we scroll the view to the top explicitly without the user scrolling.
Bug: 23562489
Change-Id: I5932b9b3b9358e23c0ec23aa235644b4f27c43ea
- This would happen when you scroll near the thumb and pass through the
area where the scrollbar was when the gesture started, and this CL
prevents gestures that move beyond a fixed distance from the original
touch position that is not already a fastscroll.
Bug: 23561678
Change-Id: I66226777671456a8919503dae4e92164ee10dd6d
Previous patch Ia4ccc59ca27e560e470122d1b2c6c1eccb4caf9a was
reverted due to a weird behavior around folder name editing
with virtual keyboard.
Also, requestFocus() on doneEditingFolderName() did nothing
because the folder itself didn't get the focus at that point.
This CL addresses these issues:
- no change on the descendant focusability. Folder itself is
focusable before its descendants.
- customize Folder.focusSearch(), so once the folder is focused,
further focus cycle moves among its descendants.
- Folder requests its focus when it appears. Without this,
the first arrow-key after opening a folder by touch moves
the focus to the folder itself, which looks like nothing happened.
Bug: 22562679
Change-Id: I04375bd4cb69d463b9a95bebafa9c60142e95daa
Sunny Goyal
Ivan Lee
Tony Wickham
Winson Chung
Jun Mukai