Connects to the Custom Tabs warmup service, and initializes the browser.
This convenience method connects to the service, and immediately warms up the Custom Tabs
implementation. Since service connection is asynchronous, the return code is not the return
code of warmup.
This call is optional, and clients are encouraged to connect to the service, call
warmup() and create a session. In this case, calling this method is not
Context: Context to use to connect to the remote service.
String: Package name of the target implementation.
Returns the preferred package to use for Custom Tabs.
The preferred package name is the default VIEW intent handler as long as it supports Custom
Tabs. To modify this preferred behavior, set ignoreDefault to true and give a
non empty list of package names in packages.
Context: Context to use for querying the packages.
List: Ordered list of packages to test for Custom Tabs support, in
decreasing order of priority.
boolean: If set, the default VIEW handler won't get priority over other browsers.
The preferred package name for handling Custom Tabs, or null.
Creates a new session through an ICustomTabsService with the optional callback. This session
can be used to associate any related communication through the service with an intent and
then later with a Custom Tab. The client can then send later service calls or intents to
through same session-intent-Custom Tab association.
CustomTabsCallback: The callback through which the client will receive updates about the created
session. Can be null. All the callbacks will be received on the UI thread.
Warm up the browser process.
Allows the browser application to pre-initialize itself in the background. Significantly
speeds up URL opening in the browser. This is asynchronous and can be called several times.