tree 9c8e66d9a930518f2216b1947b0a53fe7a905881
parent a5697c41c49de0ffc8b1a150f4dce17b55d45635
author Bjorn Bringert <bringert@android.com> 1251459547 +0100
committer Bjorn Bringert <bringert@android.com> 1251469563 +0100

Use existing respond hack to close GlobalSearch cursor

Before, when using Quick Search Box, this showed up in the log:

W/SuggestionCursor( 1013): received unexpectd respond: no DialogCursorProtocol.METHOD specified.

And a while later, this:

W/SuggestionCursor( 1013): SuggestionCursor finalized without being closed. Someone is leaking.

This latter warning is because of http://b/issue?id=2015069, where cross-process Cursor.close()
doesn't actually close the target cursor. The first warning is because
GlobalSearch.SuggestionCursor does not handle EXTRA_CURSOR_RESPOND_CLOSE_CURSOR
as sent by SuggestionsAdapter, which is a work-around for http://b/issue?id=2015069.

This change modified GlobalSearch.SuggestionCursor to close itself when
it receives EXTRA_CURSOR_RESPOND_CLOSE_CURSOR.
This will reduce some memory and thread life drag in GlobalSearch.

Fixes http://b/issue?id=2085248

Change-Id: If9cf3482dcacf245bd18cda5bb2871ff825ccf65