Bug: 6405276
- Make thumbnails bigger
- Make thumbnails higher-res
- In landscape, start the thumbnails on the right
- Fix issue where you'd sometimes see "No recent
apps" flash before the thumbnails appeared
- Fix issue where the first time recents was run
you'd see double the amount of thumbnails
Change-Id: I878caf57a955cb6a0c1b4f0a72b5b993609047f2
In rewriteSingle(), catch Throwable to rollback to backup file,
instead of just IOException. Also add dumpAll() to pack up contents
for later debugging, and use it when encountering bad stats.
Bug: 6467868
Change-Id: Ic8e287cf5a235706811a304a88d71d11d3a79cd4
- Remove the notion of channel from an application perspective
- Remove the use of DnsSd as part of API and add a protocol type to allow
future extensions
- Use the listener object as a handler for stop and unregister operations. Also,
we now allow multiple active discovery operations.
- Remove init/deinit operations in favour of setting up construction
Bug:6434844
Change-Id: Id15521d571aac9c4053d81184ad66dfc54f636de
If the layout goes through more than one pass after detecting a window
movement but before animation begins then the later pass overwrites
the animation offsets. The incorrect values are large leading to an
animation starting location in the bottom right corner.
Fixes bug 6450310.
Change-Id: I0f74e67b3e9a15a9246151abf6d47384509340e9
Instead of throwing NullPointerException when getMountService() returns
null, simply throw RemoteException so the code calling getMountService()
can fail gracefully.
Bug: 6461657
Change-Id: Ibefc17de3e0024eb73bbd24914759c0a404f538e
There are three functions in FaceUnlock.java that have the requirement
that they are to be called on the UI thread. I added checks to log
an error if they are ever called off of the UI thread.
Change-Id: I581968e8138b7561b7ad75a1ac6945bf218e2bcf
It appears sometimes the Choreographer will call you with an
old frame (i.e. an animation time in the past).
Bug: 6457615
Change-Id: I7135e2f4f524c14fe4f58f9a367f764b66d68edc
It has been several hours since my last commit.
Fix an obscure bug that could cause call ordering problems while
updating ListAdapter-based MenuPresenters. This would trigger an
inconsistent return value from the adapter's getCount method that
didn't take the expanded menu item into account, resulting in the
infamous ListView "you didn't call notifyDataSetChanged" exception.
Bug 6412318
Change-Id: I6262846d9c2acdb87ff99116ad78ca4a388efa6d
