blob: 8898927f240f46abae9d66e1f04fa43811710f2e [file] [log] [blame]
page.title=Reference of Available Intents
<p>This document describes the default applications and settings that Google provides
in their standard Android implementation. </p>
<h3>Intents handled by Google Android applications<a name="googleintents" id="googleintents"></a></h3>
<p> Android ships with Activities that handle the following Intent URI/Action pairs. </p>
<table width="100%" border="1">
<th scope="col">Scheme</th>
<th scope="col">Action<br />
<th scope="col">Description</th>
<td>http://<em>web_address</em><br />
<td>Open a browser window to the URL specified. </td>
<td>&quot;&quot; (empty string) <br />
http://<em>web_address</em><br />
<td>Opens the file at the location on the device in the browser. </td>
<td height="103">tel: <em>phone_number</em></td>
<td><p>Calls the entered phone number. Valid telephone numbers as defined
in <a href="">the IETF RFC 3966</a> are
accepted. Valid examples include the following:</p>
<li>tel:2125551212 </li>
(212) 555 1212</li>
<p>The dialer is good at normalizing some kinds of schemes: for example
telephone numbers, so the schema described isn't strictly required
in the {@link
Uri(URI string)} factory. However, if you have not tried a
schema or are unsure whether it can be handled, use the {@link, java.lang.String,
java.lang.String) Uri.fromParts(scheme, ssp, fragment)} factory
<p><strong><em>Note:</em></strong>&nbsp;&nbsp;&nbsp;This requires your
application to request the following permission in your manifest: <code>&lt;uses-permission
id=&quot;android.permission.CALL_PHONE&quot; /&gt;</code></p></td>
<td><p>tel:<em>phone_number</em><br />
voicemail:</p> </td>
<td><p>Dials (but does not actually initiate the call) the number given
(or the stored voicemail on the phone). Telephone number normalization
described for CALL applies to DIAL as well. </p> </td>
<td>geo:<em>latitude</em>,<em>longitude</em><br />
geo:<em>latitude</em>,<em>longitude</em>?z=<em>zoom</em><br />
geo:0,0?q=<em>my+street+address</em><br />
geo:0,0?q=<em>business+near+city</em><br />
<td>Opens the Maps application to the given location or query. The Geo URI scheme
(not fully supported) is <a href="">currently under
The <em>z</em> field specifies the zoom level. A zoom level of 1 shows the whole Earth, centered at the
given <em>lat</em>,<em>lng</em>. A zoom level of 2 shows a quarter of the Earth, and so on. The highest
zoom level is 23. A larger zoom level will be clamped to 23.
<td>Opens the Street View application to the given location. The URI scheme is
based on the syntax used for Street View panorama information in Google Maps URLs.<p>
The cbll field is required. The cbp and mz fields are optional.<p>
<table border="1">
<tr><td>yaw</td><td>Panorama center-of-view in degrees clockwise from North.<br />
<b>Note:</b> The two commas after the yaw parameter are required. They are present
for backwards-compatibility reasons.</td></tr>
<tr><td>pitch</td><td>Panorama center-of-view in degrees from
-90 (look straight up) to 90 (look straight down.)</td></tr>
<tr><td>zoom</td><td>Panorama zoom. 1.0 = normal zoom, 2.0 = zoomed in 2x, 3.0 = zoomed in 4x, and so on.<br />
A zoom of 1.0 is 90 degree horizontal FOV for a nominal
landscape mode 4 x 3 aspect ratio display.
Android phones in portrait mode will adjust the zoom so that
the vertical FOV is approximately the same as the landscape vertical
FOV. This means that the horizontal FOV of an Android phone in portrait
mode is much narrower than in landscape mode. This is done to minimize
the fisheye lens effect that would be present if a 90 degree horizontal
FOV was used in portrait mode.</td></tr>
<tr><td>mapZoom</td><td>The map zoom of the map location associated with this panorama. This value is passed on to the
Maps activity when the Street View "Go to Maps" menu item is chosen. It corresponds to the <em>z</em> parameter in
the geo: intent.</td></tr>