tree 59c383d796a91ffd44c2964380c8d3a44fa7cf8d
parent 01297698a13a36779b897905281e9e9b22aa995a
author Felipe Leme <felipeal@google.com> 1549331547 -0800
committer Felipe Leme <felipeal@google.com> 1549333812 -0800

Make ContentCapture calls directly from the UI thread.

Most calls are bufffered anyways, so by not using a handler we save time spent
on getting a pooled lambda and posting to the the handler.

The only "expensive" operation is flushing, but it makes a oneway binder call
so it might be fine (and if necessary, we can optimize it later).

Bug: 123307965
Test: atest CtsContentCaptureServiceTestCases
Change-Id: I7182c8e193f58fa000396fdb3003e771214bf79b