1 page.title=Reference of Available Intents 2 @jd:body 3 4 <p>This document describes the default applications and settings that Google provides 5 in their standard Android implementation. </p> 6 <h3>Intents handled by Google Android applications<a name="googleintents" id="googleintents"></a></h3> 7 <p> Android ships with Activities that handle the following Intent URI/Action pairs. </p> 8 <table width="100%" border="1"> 9 <tr> 10 <th scope="col">Scheme</th> 11 <th scope="col">Action<br /> 12 android.intent.action.<em>value</em></th> 13 <th scope="col">Description</th> 14 </tr> 15 <tr> 16 <td>http://<em>web_address</em><br /> 17 https://<em>web_address</em></td> 18 <td>VIEW</td> 19 <td>Open a browser window to the URL specified. </td> 20 </tr> 21 <tr> 22 <td>"" (empty string) <br /> 23 http://<em>web_address</em><br /> 24 https://<em>web_address</em></td> 25 <td>WEB_SEARCH</td> 26 <td>Opens the file at the location on the device in the browser. </td> 27 </tr> 28 <tr> 29 <td height="103">tel: <em>phone_number</em></td> 30 <td>CALL</td> 31 <td><p>Calls the entered phone number. Valid telephone numbers as defined 32 in <a href="http://tools.ietf.org/html/rfc3966">the IETF RFC 3966</a> are 33 accepted. Valid examples include the following:</p> 34 <ul> 35 <li>tel:2125551212 </li> 36 <li>tel: 37 (212) 555 1212</li> 38 </ul> 39 <p>The dialer is good at normalizing some kinds of schemes: for example 40 telephone numbers, so the schema described isn't strictly required 41 in the {@link android.net.Uri#parse(java.lang.String) 42 Uri(URI string)} factory. However, if you have not tried a 43 schema or are unsure whether it can be handled, use the {@link 44 android.net.Uri#fromParts(java.lang.String, java.lang.String, 45 java.lang.String) Uri.fromParts(scheme, ssp, fragment)} factory 46 instead.</p> 47 <p><strong><em>Note:</em></strong> This requires your 48 application to request the following permission in your manifest: <code><uses-permission 49 id="android.permission.CALL_PHONE" /></code></p></td> 50 </tr> 51 <tr> 52 <td><p>tel:<em>phone_number</em><br /> 53 voicemail:</p> </td> 54 <td>DIAL</td> 55 <td><p>Dials (but does not actually initiate the call) the number given 56 (or the stored voicemail on the phone). Telephone number normalization 57 described for CALL applies to DIAL as well. </p> </td> 58 </tr> 59 <tr> 60 <td>geo:<em>latitude</em>,<em>longitude</em><br /> 61 geo:<em>latitude</em>,<em>longitude</em>?z=<em>zoom</em><br /> 62 geo:0,0?q=<em>my+street+address</em><br /> 63 geo:0,0?q=<em>business+near+city</em><br /> 64 </td> 65 <td>VIEW</td> 66 <td>Opens the Maps application to the given location or query. The Geo URI scheme 67 (not fully supported) is <a href="http://tools.ietf.org/html/draft-mayrhofer-geo-uri-00">currently under 68 development</a>.<p> 69 The <em>z</em> field specifies the zoom level. A zoom level of 1 shows the whole Earth, centered at the 70 given <em>lat</em>,<em>lng</em>. A zoom level of 2 shows a quarter of the Earth, and so on. The highest 71 zoom level is 23. A larger zoom level will be clamped to 23. 72 </td> 73 </tr> 74 <tr> 75 <td>google.streetview:cbll=<em>lat</em>,<em>lng</em>&cbp=1,<em>yaw</em>,,<em>pitch</em>,<em>zoom</em>&mz=<em>mapZoom</em> 76 </td> 77 <td>VIEW</td> 78 <td>Opens the Street View application to the given location. The URI scheme is 79 based on the syntax used for Street View panorama information in Google Maps URLs.<p> 80 The cbll field is required. The cbp and mz fields are optional.<p> 81 <table border="1"> 82 <tr><th>Parameter</th><th>Description</th></tr> 83 <tr><td>lat</td><td>latitude</td></tr> 84 <tr><td>lng</td><td>longitude</td></tr> 85 <tr><td>yaw</td><td>Panorama center-of-view in degrees clockwise from North.<br /> 86 <b>Note:</b> The two commas after the yaw parameter are required. They are present 87 for backwards-compatibility reasons.</td></tr> 88 <tr><td>pitch</td><td>Panorama center-of-view in degrees from 89 -90 (look straight up) to 90 (look straight down.)</td></tr> 90 <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 /> 91 A zoom of 1.0 is 90 degree horizontal FOV for a nominal 92 landscape mode 4 x 3 aspect ratio display. 93 Android phones in portrait mode will adjust the zoom so that 94 the vertical FOV is approximately the same as the landscape vertical 95 FOV. This means that the horizontal FOV of an Android phone in portrait 96 mode is much narrower than in landscape mode. This is done to minimize 97 the fisheye lens effect that would be present if a 90 degree horizontal 98 FOV was used in portrait mode.</td></tr> 99 <tr><td>mapZoom</td><td>The map zoom of the map location associated with this panorama. This value is passed on to the 100 Maps activity when the Street View "Go to Maps" menu item is chosen. It corresponds to the <em>z</em> parameter in 101 the geo: intent.</td></tr> 102 </table> 103 </td> 104 </tr> 105 </table> 106 <p></p> 107
