ActivityInstrumentationTestCase2 takes care of starting and closing
the activity, which prevents flakyness.
Change-Id: I2d3908f6605a67a3c2d11e18a9c4799443828df9
MtpDocumentsProvider remembers the mapping between SAF's ID and MTP's
ID. Sometimes we need to do heuristic to restore the mapping when MTP
device is reconnected.
Previously we do the mapping files that shares the same name more
strictly. For example,
1. Found file name "test.txt". Assign document ID "1".
2. MTP device is disconnected and the MTP ID of "1" is lost.
3. Found two files that have same name "test.txt" in the same directory.
Previously we don't reuse existing document ID "1" for neither of two
"test.txt" because it's not 1-to-1 mapping and we cannot determine which
one should be mapped with existing document ID. It means we need the
complete list of files in a directory to remap IDs. It takes long time
to fetch all file names in a directory when a directory has 100+
files. It's rare that a MTP device has the two files sharing the same
name in the same directory. Also the strict rule makes the mapping code
more complex.
The CL relax the rule of mapping, and it allows to reuse existing
document ID even if it is not 1-to-1 mapping. For the previous example,
it assigns "1" for either of "test.txt".
BUG=27053734
Change-Id: I19406fafc21f13ab94ba99411ce5e7f55ce7f658
If we're restoring after a background process death, the Parcelable
creator cache is cold, and since we're handing in a null ClassLoader
the best the platform can do is try the default ClassLoader which
knows nothing about the running app.
That's why ClassLoaderCreator exists, so use it to snag the relevant
ClassLoader and pass it along.
Bug: 26075620
Change-Id: I6fd977d6178dd0f5f9c465597f5806a08097ac7c
Improved drawer management in reponse to back button presses:
- if drawer is open (and we didn't just open it), close it.
- if at top of root (and we didn't close root) open it.
- there's a timeout on this behavior such that pressing back
a second time within a 1.5 second perior will NOT initiate
the behaviors described above.
Change-Id: I5990848cd3047d9dc985ec10e57ab3a0f99ce79c
Clean up the code, introduce and use a separator, fix the
existing end-of-groups separator.
Bug: 26848253
Change-Id: I2b7723ebf257e7176f08551766c59d86d01cf6a6
MTP spec defines format code as a file type of object, but we don't have
format code for some file types like PDF. This CL adds fallback that
tries to obtain mime type from file name in such case.
BUG=27004957
Change-Id: Id61352bf4726f4e044e57edadcefbf179fe3f882
Slowly chipping away at TetherUtil to clean up this code.
This CL also adds an admin check to
ConnectivityService.isTetheringSupported to get parity with the
TetherUtil function before removing it.
Change-Id: Ibe7c5c9fb420d57e5458f77dad30e8a1e751a3e2
* changes:
Fixing issue with history icons getting clobbered.
Fallback 1 for Recents timeout behaviour
Drawing thumbnail background color for empty space in view.
Fixing issue with task animating from 0,0.
Minor tweak to enter/exit animation for the home activity.
Also, reveal the illusion that we're restoring state in Files and Downloads.
Also, define a "PairedTask" class that guards calls to task methods
with checks against isDestroyed. This also let us make all of the tasks
static, so we get much narrower scope and tasks can even be moved to
their own files.
Change-Id: I6a9e8706e1ab1d1f43301e73dd9858a115a6baaf
- When showing landscape thumbnails in portrait, the thumbnails are
aspect scaled to fit the width of the view, this change will draw
a solid color to fill the other part so that we don't see the
current edge-clamp texture effect.
Change-Id: Icf08239942f9179c66ba0f8d8ddd00f7d2a09d3c
- If the view holder is rebound before the other task is recycled, there
could be multiple callbacks attached to different tasks for the same
view holder, which can cause the wrong icon (which is loaded in the
bg, to be loaded into the wrong view holder). Now, we unbind the
callback from the old task when the new task’s callbacks are bound.
Change-Id: If0dfada24985944daf4302c4db0616a00a770f06
- When we get all the initial task transforms when swiping to dismiss,
the tasks that are not visible at the original scroll position but are
in the final position are not initialized correctly. Instead when
getting the current transforms for all tasks, always calculate their
transforms regardless of whether they are currently visible or not.
- This revealed another issue where on snap-back, a task that was
visible at the new scroll and not at the old scroll was not getting
removed until the next update (which would cause a task view to linger
if you press home for example).
Bug: 26964326
Change-Id: I4db9cd1b072d3841351c2e84b219ca224a3045f9
- Fixing issue where the animation props was not applied to the progress
and callback animations correctly
- Ensuring that all tasks animate the same distance on enter/exit, and
not just to the edge of the screen
- Removing unused styles and animation resources
Change-Id: I88bd0f79f386304373fe63b49e92f02eeb882e55
When long pressing on the recents button, we made it one pixel smaller
than fullscreen so we don't dismiss the stack immediately again.
However, this is a huge hack, and lead to problems with navigation bar
background because there we actually rely on the fact whether
the window is fullscreen or not to determine whether to draw the
navigation bar background, which lead to flickering.
Bug: 26777526
Change-Id: Ifdfcf3ad4138bc88c5164177cd20f1ff1635085f
When dragging the divider in a way such the task size goes through
the following transition
- Half size
- Full screen
- Half size
the surface wasn't clipped off anymore. This was because in full
screen configuration, computeDragResizing() == false thus when
going full screen -> half size, we reset the draw state to
DRAW_PENDING to get notified when it has finished drawn. However,
this also broke clipping.
In order to fix this, we always put the window into a resizing mode
no matter whether the bounds are fullscreen or not.
However, this introduces an ugly flickering on the navigation bar,
when going into docked mode, because the app doesn't draw navigation
bar background in resize mode.
To fix that, we calculate the presence of navigation bar whether the
window is fullscreen, and not just whether it's resizing. For that,
we need to calculate the presence in BackdropFrameRenderer, by using
the insets just sent by window manager.
Change-Id: Idf56df4ae7fefe67d068bc2eeda8dc4d83bbefb7
