</ul>
<p class="toc-title">Content</p>
<ul class="toc">
- <li><a href="#manager">Connection Manager</a></li>
- <li><a href="#con_profile">Connection Profile</a></li>
- <li><a href="#statistics">Connection Statistics</a></li>
+ <li><a href="#socket">IP Sockets</a></li>
<li><a href="#prerequisites">Prerequisites</a></li>
<li><a href="#detail">Getting Network Connection Details</a></li>
<li><a href="#info">Getting Connection Information</a></li>
<div id="container"><div id="contents"><div class="content">
<h1>Connection Management</h1>
-<p>The connection features enable you to create a network connection and perform various operations over the connection. The application can access connection details, such as the IP address, proxy information, gateway information, and connection statistics.</p>
+<p>You can create a network connection in your application, and use it to perform various operations. The application can access connection details, such as the IP address, proxy information, gateway information, and connection statistics. It can also manage <a href="#socket">IP sockets</a>.</p>
<p>The main features of the Connection API include:</p>
<ul>
<li>Managing connections
- <p>You can <a href="#manager">establish and manage various data connections</a>. You can also retrieve the connection state and monitor property changes in the connection.</p></li>
+ <p>You can establish and manage various data connections using a connection handle, which is created with the <code>connection_create()</code> function of the Connection Manager API (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__NETWORK__CONNECTION__MANAGER__MODULE.html">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__NETWORK__CONNECTION__MANAGER__MODULE.html">wearable</a> applications). You can use the handle to:</p>
+ <ul>
+ <li><a href="#detail">Get a state of the connection interface</a>.
+ <p>You can access the state of the Bluetooth, cellular, and Wi-Fi connections only. Use the <code>connection_get_[interface]_state()</code> function to retrieve the state as the <code>connection_bt_state_e</code> (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__NETWORK__CONNECTION__MANAGER__MODULE.html#gaf4abc0a653145fb9dec7e885c9081395">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__NETWORK__CONNECTION__MANAGER__MODULE.html#gaf4abc0a653145fb9dec7e885c9081395">wearable</a> applications), <code>connection_cellular_state_e</code> (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__NETWORK__CONNECTION__MANAGER__MODULE.html#ga9ca508e61d795be15ee1795581a66396">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__NETWORK__CONNECTION__MANAGER__MODULE.html#ga9ca508e61d795be15ee1795581a66396">wearable</a> applications), or <code>connection_wifi_state_e</code> (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__NETWORK__CONNECTION__MANAGER__MODULE.html#gab3ad7fdb200354b3c34878d88fc97dcd">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__NETWORK__CONNECTION__MANAGER__MODULE.html#gab3ad7fdb200354b3c34878d88fc97dcd">wearable</a> applications) enumerator.</p></li>
+ <li>Access various network details, such as the IP address, proxy, and gateway information.
+ <p>You can use the <code>connection_address_family_e</code> enumerator in (<a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__NETWORK__CONNECTION__PROFILE__MODULE.html#ga5910989495b39e8c4dbbd05ec9482d19">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__NETWORK__CONNECTION__PROFILE__MODULE.html#ga5910989495b39e8c4dbbd05ec9482d19">wearable</a> applications) to get the IPv4 or IPv6 address family. You can use it as a parameter when you retrieve the IP address of the current connection or proxy.</p></li>
+ <li><a href="#register">Register property change callbacks</a>.</li>
+ <li>Create a <code>connection_profile_h</code> profile handle, which provides information according to the connection type.</li>
+ </ul>
+ </li>
<li>Mapping connection profiles
- <p>You can <a href="#con_profile">map a connection profile</a> to retrieve details about specific connections.</p></li>
+ <p>You can map a connection profile to retrieve details about specific connections, using the Connection Profile API (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__NETWORK__CONNECTION__PROFILE__MODULE.html">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__NETWORK__CONNECTION__PROFILE__MODULE.html">wearable</a> applications).</p>
+ <p>Each connection profile is defined by a set of configuration information defined in the <code>connection_profile_h</code> handle. The profile provides different information according to the connection type (such as Bluetooth, cellular, Ethernet, and Wi-Fi). You can access various profile details, such as the state, type, and name with the <code>connection_profile_get_XXX()</code> functions.</p>
+ <p>The Connection Profile API has child APIs for cellular and Wi-Fi profiles:</p>
+ <ul>
+ <li>To manage a cellular profile, use the Cellular Profile API (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__NETWORK__CONNECTION__CELLULAR__PROFILE__MODULE.html">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__NETWORK__CONNECTION__CELLULAR__PROFILE__MODULE.html">wearable</a> applications). You can access and modify various cellular connection details.</li>
+ <li>To manage a Wi-Fi profile, use the Wi-Fi Profile API (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__NETWORK__CONNECTION__WIFI__PROFILE__MODULE.html">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__NETWORK__CONNECTION__WIFI__PROFILE__MODULE.html">wearable</a> applications). You can access various Wi-Fi connection details, and set a passphrase for the WPA (Wi-Fi Protected Access).</li>
+ </ul></li>
+
<li>Gathering statistics
- <p>You can <a href="#statistics">gather various statistics on the network usage</a>, such as the amounts of sent and received data.</p></li>
+ <p>You can <a href="#info">gather various statistics on the network usage</a>, such as the amounts of sent and received data, using the Connection Statistics API (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__NETWORK__CONNECTION__STATISTICS__MODULE.html">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__NETWORK__CONNECTION__STATISTICS__MODULE.html">wearable</a> applications). You can also retrieve the cumulative size of packets sent or received since the last reset based on the operation mode, such as packet switching (PS). To define the specific type of statistics information you want, use the <code>connection_statistics_type_e</code> enumerator (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__NETWORK__CONNECTION__STATISTICS__MODULE.html#ga24b29d70490e8cd9ee34f45615ea1c63">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__NETWORK__CONNECTION__STATISTICS__MODULE.html#ga24b29d70490e8cd9ee34f45615ea1c63">wearable</a> applications).</p>
+
+ <div class="note">
+ <strong>Note</strong>
+ Statistics are supported for Wi-Fi and cellular connections only.
+ </div>
+
+ <p>You can re-initialize the statistics with the <code>connection_reset_statistics()</code> function.</p>
+ </li>
</ul>
-<h2 id="manager" name="manager">Connection Manager</h2>
-<p>The Connection Manager API (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__NETWORK__CONNECTION__MANAGER__MODULE.html">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__NETWORK__CONNECTION__MANAGER__MODULE.html">wearable</a> applications) allows you to manage data connections using a connection handle. First you create the handle with the <code>connection_create()</code> function, and then you can use it to:</p>
-<ul><li><a href="#detail">Get a state of the connection interface</a>.
-<p>You can access the state of the Bluetooth, cellular, and Wi-Fi connections only. Use the <code>connection_get_[interface]_state()</code> function to retrieve the state as the <code>connection_bt_state_e</code> (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__NETWORK__CONNECTION__MANAGER__MODULE.html#gaf4abc0a653145fb9dec7e885c9081395">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__NETWORK__CONNECTION__MANAGER__MODULE.html#gaf4abc0a653145fb9dec7e885c9081395">wearable</a> applications), <code>connection_cellular_state_e</code> (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__NETWORK__CONNECTION__MANAGER__MODULE.html#ga9ca508e61d795be15ee1795581a66396">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__NETWORK__CONNECTION__MANAGER__MODULE.html#ga9ca508e61d795be15ee1795581a66396">wearable</a> applications), or <code>connection_wifi_state_e</code> (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__NETWORK__CONNECTION__MANAGER__MODULE.html#gab3ad7fdb200354b3c34878d88fc97dcd">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__NETWORK__CONNECTION__MANAGER__MODULE.html#gab3ad7fdb200354b3c34878d88fc97dcd">wearable</a> applications) enumerator.</p></li>
-<li>Access various network details, such as the IP address, proxy, and gateway information.
-<p>You can use the <code>connection_address_family_e</code> enumerator in (<a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__NETWORK__CONNECTION__PROFILE__MODULE.html#ga5910989495b39e8c4dbbd05ec9482d19">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__NETWORK__CONNECTION__PROFILE__MODULE.html#ga5910989495b39e8c4dbbd05ec9482d19">wearable</a> applications) to get the IPv4 or IPv6 address family. You can use it as a parameter when you retrieve the IP address of the current connection or proxy.</p></li>
-<li><a href="#register">Register property change callbacks</a>.</li>
-<li>Create a <code>connection_profile_h</code> profile handle, which provides information according to the connection type.</li></ul>
+<h2 id="socket" name="socket">IP Sockets</h2>
-<p>The Connection Manager API is related to <a href="http://curl.haxx.se/libcurl/" target="_blank">libcurl</a> (see the <a href="curl_n.htm">Curl</a> guide) and sockets. After a network connection is established, you can create a socket on the kernel Linux stack to be used directly or by libcurl or any other network library. If you want to create a socket directly without libcurl, you must check whether you are using the IPv4 or IPv6 environment, and create an applicable IP socket.</p>
+<p>The Connection Manager API
(in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__NETWORK__CONNECTION__MANAGER__MODULE.html">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__NETWORK__CONNECTION__MANAGER__MODULE.html">wearable</a> applications) is related to <a href="http://curl.haxx.se/libcurl/" target="_blank">libcurl</a> (see the <a href="curl_n.htm">Curl</a> guide) and sockets. After a network connection is established, you can create a socket on the kernel Linux stack to be used directly or by libcurl or any other network library. If you want to create a socket directly without libcurl, you must check whether you are using the IPv4 or IPv6 environment, and create an applicable IP socket.</p>
<p>To manage IP sockets, you can:</p>
<ol>
<p>For libcurl, you can <a href="curl_n.htm#manage">use the <code>CURLOPT_PROXY</code> option</a>.</p>
</div>
-
-<h2 id="con_profile" name="con_profile">Connection Profile</h2>
-<p>The Connection Profile API (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__NETWORK__CONNECTION__PROFILE__MODULE.html">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__NETWORK__CONNECTION__PROFILE__MODULE.html">wearable</a> applications) provides functions for mapping a connection profile. It allows you to use a <code>connection_profile_h</code> handle for getting details about the connection.</p>
-
-<p>Each profile is defined by a set of configuration information defined in the <code>connection_profile_h</code> handle. The profile provides different information according to the connection type (such as Bluetooth, cellular, ethernet, and Wi-Fi).</p>
-
-<p>The following table defines the available profile information, which you can get using the <code>connection_profile_get_XXX()</code> function.</p>
-
- <p align="center" class="Table"><strong>Table: Common information</strong></p>
-<table>
- <tbody>
- <tr>
- <th colspan="2">Information</th>
- <th>Description</th>
- </tr>
- <tr>
- <th rowspan="12">Common</th>
- <td>DNS address</td>
- <td>DNS address; you can get the first and second DNS address</td>
- </tr>
- <tr>
- <td>Gateway address</td>
- <td>Gateway address</td>
- </tr>
- <tr>
- <td>IP address</td>
- <td>IP address</td>
- </tr>
- <tr>
- <td>IP configuration type</td>
- <td>IP address configuration type, such as static, dynamic, auto, or fixed</td>
- </tr>
- <tr>
- <td>Network interface name</td>
- <td>Name of the network interface, such as eth0 or pdp0</td>
- </tr>
- <tr>
- <td>Profile ID</td>
- <td>Unique profile ID; when you create a new profile, this value is determined</td>
- </tr>
- <tr>
- <td>Profile name</td>
- <td>Profile name associated with the profile ID</td>
- </tr>
- <tr>
- <td>Profile state</td>
- <td>Profile state, such as disconnected, association, configuration, or connected</td>
- </tr>
- <tr>
- <td>Profile type</td>
- <td>Profile type indicating the network connection type</td>
- </tr>
- <tr>
- <td>Proxy address</td>
- <td>Proxy address</td>
- </tr>
- <tr>
- <td>Proxy type</td>
- <td>Proxy method, such as direct or auto</td>
- </tr>
- <tr>
- <td>Subnet mask</td>
- <td>Subnet mask</td>
- </tr>
- <tr>
- <th rowspan="9">Wi-Fi-specific</th>
- <td>BSSID</td>
- <td>Basic service set identifier</td>
- </tr>
- <tr>
- <td>ESSID</td>
- <td>Extended service set identifier</td>
- </tr>
- <tr>
- <td>Encryption type</td>
- <td>Type for encryption modes, such as WEP, TKIP, AES or TKIP/AES mixed</td>
- </tr>
- <tr>
- <td>Frequency</td>
- <td>Frequency (in MHz)</td>
- </tr>
- <tr>
- <td>Max speed</td>
- <td>Maximum speed (in Mbps)</td>
- </tr>
- <tr>
- <td>Passphrase required</td>
- <td>Passphrase compulsion</td>
- </tr>
- <tr>
- <td>RSSI</td>
- <td>Received signal strength indication</td>
- </tr>
- <tr>
- <td>Security type</td>
- <td>Wi-Fi security type; supports WEP, WPA-PSK, WPA2-PSK, and EAP</td>
- </tr>
- <tr>
- <td>WPS supported</td>
- <td>Whether WPS (Wi-Fi Protected Setup) is supported</td>
- </tr>
- <tr>
- <th rowspan="10">Cellular-specific</th>
- <td>APN</td>
- <td>Access Point Name</td>
- </tr>
- <tr>
- <td>Cellular authentication info</td>
- <td>Authentication information, including user name and password</td>
- </tr>
- <tr>
- <td>Cellular home URL</td>
- <td>Home URL</td>
- </tr>
- <tr>
- <td>Default</td>
- <td>Whether the profile is default</td>
- </tr>
- <tr>
- <td>Editable</td>
- <td>Whether the profile is editable</td>
- </tr>
- <tr>
- <td>Hidden</td>
- <td>Whether the profile is hidden</td>
- </tr>
- <tr>
- <td>PDN type</td>
- <td>Cellular PDN type</td>
- </tr>
- <tr>
- <td>Roaming PDN type</td>
- <td>Cellular roaming PDN type</td>
- </tr>
- <tr>
- <td>Roaming</td>
- <td>Roaming state</td>
- </tr>
- <tr>
- <td>Service type</td>
- <td>Cellular service type</td>
- </tr>
- </tbody>
- </table>
-
-
-<h2 id="statistics" name="statistics">Connection Statistics</h2>
-
-<p>You can use the Connection Statistics API (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__NETWORK__CONNECTION__STATISTICS__MODULE.html">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__NETWORK__CONNECTION__STATISTICS__MODULE.html">wearable</a> applications) to <a href="#info">gather statistics on the network usage</a>, such as the amount of sent or received data. You can also retrieve the cumulative size of packets sent or received since the last reset based on the operation mode, such as packet switching (PS). To define the specific type of statistics information you want, use the <code>connection_statistics_type_e</code> enumerator (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__NETWORK__CONNECTION__STATISTICS__MODULE.html#ga24b29d70490e8cd9ee34f45615ea1c63">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__NETWORK__CONNECTION__STATISTICS__MODULE.html#ga24b29d70490e8cd9ee34f45615ea1c63">wearable</a> applications).</p>
-
-
- <div class="note">
- <strong>Note</strong>
- Statistics are supported for Wi-Fi and cellular connections only.
- </div>
-
-<p>You can re-initialize the statistics with the <code>connection_reset_statistics()</code> function.</p>
-
<h2 id="prerequisites">Prerequisites</h2>
<p>To enable your application to use the connection functionality:</p>
<div class="note">
<strong>Note</strong>
- In a proxy environment, the libcurl library does not know the proxy address. To handle HTTP and HTTPS requests in a proxy environment, first get the proxy address using the <a href="connection_n.htm#manager">connection manager</a>, and then set the proxy address using the Curl API.
+ In a proxy environment, the libcurl library does not know the proxy address. To handle HTTP and HTTPS requests in a proxy environment, first get the proxy address using the <a href="connection_n.htm">connection manager</a>, and then set the proxy address using the Curl API.
</div>
</li>
</ul>
<p class="toc-title">Content</p>
<ul class="toc">
- <li><a href="#call">Call Information</a></li>
- <li><a href="#sim">SIM Information</a></li>
- <li><a href="#net">Network Information</a></li>
- <li><a href="#modem">Modem Information</a></li>
<li><a href="#prerequisites">Prerequisites</a></li>
- <li><a href="#call_use">Getting Call Information</a></li>
- <li><a href="#sim_use">Getting SIM Card Information</a></li>
- <li><a href="#network_use">Getting Network Information</a></li>
- <li><a href="#modem_use">Getting Modem Information</a></li>
+ <li><a href="#call_use">Retrieving Call Information</a></li>
+ <li><a href="#sim_use">Retrieving SIM Card Information</a></li>
+ <li><a href="#network_use">Retrieving Network Information</a></li>
+ <li><a href="#modem_use">Retrieving Modem Information</a></li>
</ul>
<p class="toc-title">Related Info</p>
<ul class="toc">
<div id="container"><div id="contents"><div class="content">
<h1>Telephony Information</h1>
- <p>Telephony information features include call, SIM, network, and modem information using the Telephony Service.</p>
+ <p>Through the telephony service, you can access various telephony features, such as call, SIM, network, and modem information.</p>
<p>The main Telephony Information API features are:</p>
<ul>
<li>Call information
-<p>Using the <a href="#call">Call API functions</a>, you can <a href="#call_use">get the voice and video call states</a>. You can use this information in call-related actions.</p></li>
+<p>You can <a href="#call_use">retrieve information about the current call</a> by using the Call API (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__TELEPHONY__INFORMATION__CALL.html">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__TELEPHONY__INFORMATION__CALL.html">wearable</a> applications) to retrieve a list of current call handles. You can also access voice and video call states, and use the state information in call-related actions.</p>
+<p>You can access the number, type, and status of the call. You can also determine the call direction (mobile-originated or mobile-terminated) and whether the call is a conference call.</p>
+</li>
<li>SIM information
-<p>Using the <a href="#sim">SIM API functions</a>, you can <a href="#sim_use">extract information stored on a SIM card</a> without changing the information.</p></li>
+<p>You can <a href="#sim_use">extract information stored on a SIM card</a> using the SIM API (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__TELEPHONY__INFORMATION__SIM.html">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__TELEPHONY__INFORMATION__SIM.html">wearable</a> applications). You can get, for example, the ICC-ID (Integrated Circuit Card Identification), operator, and SPN (Service Provider Name) information.</p>
+</li>
<li>Network information
-<p>Using the <a href="#net">Network API functions</a>, you can <a href="#network_use">access (without changing) information about the current cellular network</a> and telephony service.</p></li>
+<p>You can <a href="#network_use">retrieve information about the current cellular network and telephony service</a> using the Network API (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__TELEPHONY__INFORMATION__NETWORK.html">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__TELEPHONY__INFORMATION__NETWORK.html">wearable</a> applications). You can get, for example, the cell ID, LAC (Location Area Code), network type, and network name of the current cellular network and telephony service.</p>
+</li>
<li>Modem information
-<p>Using the <a href="#modem">Modem API functions</a>, you can <a href="#modem_use">access (without changing) IMEI information</a>.</p></li>
-</ul>
-
-<p>The following figure illustrates the Telephony Service and APIs.</p>
-
- <p align="center"><strong>Figure: Telephony APIs and Telephony Service</strong></p>
- <p align="center"><img alt="Telephony APIs and Telephony Service" src="../../images/telephony.png" /></p>
-
-<h2 id="call" name="call">Call Information</h2>
+<p>You can <a href="#modem_use">access information about the modem</a> using the Modem API (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__TELEPHONY__INFORMATION__MODEM.html">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__TELEPHONY__INFORMATION__MODEM.html">wearable</a> applications). You can get the IMEI (International Mobile Station Equipment Identity), MEID (Mobile Equipment Identifier), and power status of the modem.</p></li>
-<p>The Call API (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__TELEPHONY__INFORMATION__CALL.html">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__TELEPHONY__INFORMATION__CALL.html">wearable</a> applications) provides the following functions:</p>
-
-<ul>
-<li><code>telephony_call_get_preferred_voice_subscription()</code>
-<p>Gets the current value for the preferred voice call subscription. It returns one of the <code>telephony_call_preferred_voice_subs_e</code> values (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__TELEPHONY__INFORMATION__CALL.html#gafbb8572dabc68ea7cdb93a4eb8f9c719">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__TELEPHONY__INFORMATION__CALL.html#gafbb8572dabc68ea7cdb93a4eb8f9c719">wearable</a> applications).</p></li>
-<li><code>telephony_call_get_call_list()</code>
-<p>Gets the list of the current call. It returns the current call count and the call handle.</p></li>
-<li><code>telephony_call_release_call_list()</code>
-<p>Releases the list allocated to the call handle. When the call handle is no longer needed, this function must be called to free the handle.</p></li>
-<li><code>telephony_call_get_handle_id()</code>
-<p>Gets the call handle ID.</p></li>
-<li><code>telephony_call_get_number()</code>
-<p>Gets the call number.</p></li>
-<li><code>telephony_call_get_type()</code>
-<p>Gets the call type. It returns one of the <code>telephony_call_type_e</code> values (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__TELEPHONY__INFORMATION__CALL.html#ga7fd22fc9506f04744c0672a3bb2d6197">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__TELEPHONY__INFORMATION__CALL.html#ga7fd22fc9506f04744c0672a3bb2d6197">wearable</a> applications).</p></li>
-<li><code>telephony_call_get_status()</code>
-<p>Gets the call status. It returns one of the <code>telephony_call_status_e</code> values (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__TELEPHONY__INFORMATION__CALL.html#ga57063fd38cbd104003151f511847e8ba">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__TELEPHONY__INFORMATION__CALL.html#ga57063fd38cbd104003151f511847e8ba">wearable</a> applications).</p></li>
-<li><code>telephony_call_get_direction()</code>
-<p>Gets the call direction: MO (Mobile Originated) or MT (Mobile Terminated). It returns one of the <code>telephony_call_direction_e</code> values (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__TELEPHONY__INFORMATION__CALL.html#ga821d2e9727a0cdab601f55f2e286af90">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__TELEPHONY__INFORMATION__CALL.html#ga821d2e9727a0cdab601f55f2e286af90">wearable</a> applications).</p></li>
-<li><code>telephony_call_get_conference_status()</code>
-<p>Determines whether the call is conference call. It returns <code>true</code> for a conference call or <code>false</code> for a single call.</p></li></ul>
-
-<p>To get call state change notifications, the application must register for the notifications with the <code>telephony_set_noti_cb()</code> function, by specifying the notification ID.</p>
-
-<p>The following table defines the available notification IDs.</p>
-
- <p align="center" class="Table"><strong>Table: Call information notification IDs</strong></p>
-<table>
- <tbody>
- <tr>
- <th>Change in state</th>
- <th>Notification ID</th>
- </tr>
- <tr>
- <td>Voice status idle</td>
- <td><code>TELEPHONY_NOTI_VOICE_CALL_STATUS_IDLE</code></td>
- </tr>
- <tr>
- <td>Voice status active</td>
- <td><code>TELEPHONY_NOTI_VOICE_CALL_STATUS_ACTIVE</code></td>
- </tr>
- <tr>
- <td>Voice status held</td>
- <td><code>TELEPHONY_NOTI_VOICE_CALL_STATUS_HELD</code></td>
- </tr>
- <tr>
- <td>Voice status dialing</td>
- <td><code>TELEPHONY_NOTI_VOICE_CALL_STATUS_DIALING</code></td>
- </tr>
- <tr>
- <td>Voice status alerting</td>
- <td><code>TELEPHONY_NOTI_VOICE_CALL_STATUS_ALERTING</code></td>
- </tr>
- <tr>
- <td>Voice status incoming</td>
- <td><code>TELEPHONY_NOTI_VOICE_CALL_STATUS_INCOMING</code></td>
- </tr>
- <tr>
- <td>Video status idle</td>
- <td><code>TELEPHONY_NOTI_VIDEO_CALL_STATUS_IDLE</code></td>
- </tr>
- <tr>
- <td>Video status active</td>
- <td><code>TELEPHONY_NOTI_VIDEO_CALL_STATUS_ACTIVE</code></td>
- </tr>
- <tr>
- <td>Video status dialing</td>
- <td><code>TELEPHONY_NOTI_VIDEO_CALL_STATUS_DIALING</code></td>
- </tr>
- <tr>
- <td>Video status alerting</td>
- <td><code>TELEPHONY_NOTI_VIDEO_CALL_STATUS_ALERTING</code></td>
- </tr>
- <tr>
- <td>Video status incoming</td>
- <td><code>TELEPHONY_NOTI_VIDEO_CALL_STATUS_INCOMING</code></td>
- </tr>
- <tr>
- <td>Preferred voice subscription</td>
- <td><code>TELEPHONY_NOTI_CALL_PREFERRED_VOICE_SUBSCRIPTION</code></td>
- </tr>
- </tbody>
- </table>
-
-
-<h2 id="sim" name="sim">SIM Information</h2>
-
-<p>The SIM API (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__TELEPHONY__INFORMATION__SIM.html">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__TELEPHONY__INFORMATION__SIM.html">wearable</a> applications) provides the following functions:</p>
-<ul><li><code>telephony_sim_get_icc_id()</code>
-<p>Gets the Integrated Circuit Card IDentification (ICC-ID). You get the ICC-ID as a string, which needs to be freed by the application.</p></li>
-<li><code>telephony_sim_get_operator()</code>
-<p>Gets the SIM operator (MCC + MNC). You get the operator information as a string, which needs to be freed by the application.</p></li>
-<li><code>telephony_sim_get_msin()</code>
-<p>Gets the Mobile Subscription Identification Number (MSIN) of the SIM provider. You get the MSIN as a string, which needs to be freed by the application.</p></li>
-<li><code>telephony_sim_get_spn()</code>
-<p>Gets the Service Provider Name (SPN) of the SIM card. You get the SPN as a string, which needs to be freed by the application.</p></li>
-<li><code>telephony_sim_get_cphs_operator_name()</code>
-<p>Gets the Operator Name String (ONS) of the Common PCN Handset Specification (CPHS) in the SIM card. You get the CPHS as a string, which needs to be freed by the application.</p></li>
-<li><code>telephony_sim_get_subscriber_number()</code>
-<p>Gets the subscriber number embedded in the SIM card. This value contains the MSISDN related to the subscriber. You get the subscriber number as a string, which needs to be freed by the application.</p></li>
-<li><code>telephony_sim_get_state()</code>
-<p>Gets the state of the SIM. It returns one of the <code>telephony_sim_state_e</code> values (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__TELEPHONY__INFORMATION__SIM.html#ga08448f4cfaf7c59cd585008d3bf32b70">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__TELEPHONY__INFORMATION__SIM.html#ga08448f4cfaf7c59cd585008d3bf32b70">wearable</a> applications).</p></li>
-<li><code>telephony_sim_is_changed()</code>
-<p>Checks whether the current SIM card differs from the previous SIM card.</p></li>
-<li><code>telephony_sim_get_application_list()</code>
-<p>Gets the application list on the UICC. It returns one of the masking values (<code>telephony_sim_application_type_e</code> in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__TELEPHONY__INFORMATION__SIM.html#ga9b13e5521ca5578a377455a16e721c86">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__TELEPHONY__INFORMATION__SIM.html#ga9b13e5521ca5578a377455a16e721c86">wearable</a> applications).</p></li>
-<li><code>telephony_sim_get_subscriber_id()</code>
-<p>Gets the subscriber ID as a string, which needs to be freed by the application.</p></li>
-<li><code>telephony_sim_get_lock_state()</code>
-<p>Gets the SIM card lock state. If the SIM card is locked, you can use this function to retrieve the lock state.</p></li>
-<li><code>telephony_sim_get_group_id1()</code>
-<p>Gets the Group Identifier Level 1 (GID1) embedded in the SIM card.</p></li>
-<li><code>telephony_sim_get_call_forwarding_indicator_state()</code>
-<p>Gets the call forwarding indicator state of the SIM. If the state is <code>true</code>, incoming call is forwarded to the selected number.</p></li>
+<li>State changes
+<p>You can receive notifications for various information change events related to call, SIM card, and network information. To monitor state change events, register state change callbacks with the <code>telephony_set_noti_cb()</code> function, by specifying the notification ID. The available notification IDs are defined in the <code>telephony_noti_e</code> enumeration (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__TELEPHONY__INFORMATION.html#ga3f9d407deee8c7c7f1f7ed946bc60b4d">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__TELEPHONY__INFORMATION.html#ga3f9d407deee8c7c7f1f7ed946bc60b4d">wearable</a> applications).</p></li>
</ul>
-<p>To get SIM state change notifications, the application must register for the notifications with the <code>telephony_set_noti_cb()</code> function, by specifying the notification ID.</p>
-
-<p>The following table defines the available notification IDs.</p>
-
- <p align="center" class="Table"><strong>Table: SIM information notification IDs</strong></p>
-<table>
- <tbody>
- <tr>
- <th>Change in state</th>
- <th>Notification ID</th>
- </tr>
- <tr>
- <td>SIM state</td>
- <td><code>TELEPHONY_NOTI_SIM_STATUS</code></td>
- </tr>
- </tbody>
- </table>
-
-
- <div class="note">
- <strong>Note</strong>
- Before retrieving information from the SIM card, you must retrieve the state of the SIM card. You can get SIM-related information only if the SIM state is <code>TELEPHONY_SIM_STATE_AVAILABLE</code>.
- </div>
-
+<p>The following figure illustrates the telephony service and APIs.</p>
-<h2 id="net" name="net">Network Information</h2>
-
-<p>The Network API (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__TELEPHONY__INFORMATION__NETWORK.html">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__TELEPHONY__INFORMATION__NETWORK.html">wearable</a> applications) provides the following functions:</p>
-<ul><li><code>telephony_network_get_lac()</code>
-<p>Gets the LAC (Location Area Code) of the current location.</p></li>
-<li><code>telephony_network_get_cell_id()</code>
-<p>Gets the cell ID of the current location.</p></li>
-<li><code>telephony_network_get_rssi()</code>
-<p>Gets the RSSI (Received Signal Strength Indicator).</p></li>
-<li><code>telephony_network_get_roaming_status()</code>
-<p>Gets the roaming state (<code>true</code> = roaming and <code>false</code> = not roaming).</p></li>
-<li><code>telephony_network_get_mcc()</code>
-<p>Gets the MCC (Mobile Country Code) of the current registered network. You get the MCC as a string, which needs to be freed by the application.</p></li>
-<li><code>telephony_network_get_mnc()</code>
-<p>Gets the MNC (Mobile Network Code) of the current registered network. You get the MNC as a string, which needs to be freed by the application.</p></li>
-<li><code>telephony_network_get_network_name()</code>
-<p>Gets the name of the current registered network. You get the network name as a string, which needs to be freed by the application.</p></li>
-<li><code>telephony_network_get_type()</code>
-<p>Gets the network service type of the current registered network. It returns one of the <code>telephony_network_type_e</code> values (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__TELEPHONY__INFORMATION__NETWORK.html#ga250d1e41f6ab9b949c46c842a7959329">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__TELEPHONY__INFORMATION__NETWORK.html#ga250d1e41f6ab9b949c46c842a7959329">wearable</a> applications). </p></li>
-<li><code>telephony_network_get_service_state()</code>
-<p>Gets the current network state of the telephony service. It returns one of the <code>telephony_network_service_state_e</code> values (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__TELEPHONY__INFORMATION__NETWORK.html#gae9f3b6e54a1086b8734f4acc71fd001b">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__TELEPHONY__INFORMATION__NETWORK.html#gae9f3b6e54a1086b8734f4acc71fd001b">wearable</a> applications).</p></li>
-<li><code>telephony_network_get_ps_type()</code>
-<p>Gets the packet service type of the currently registered network. It returns one of the <code>telephony_network_ps_type_e</code> values (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__TELEPHONY__INFORMATION__NETWORK.html#gac98431df26c117a457f4fbde5d4b1f3c">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__TELEPHONY__INFORMATION__NETWORK.html#gac98431df26c117a457f4fbde5d4b1f3c">wearable</a> applications).</p></li>
-<li><code>telephony_network_get_network_name_option()</code>
-<p>Gets the network name option of the currently registered network. It returns one of the <code>telephony_network_name_option_e</code> values (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__TELEPHONY__INFORMATION__NETWORK.html#gae2ffe560f05c886539f5f7d2d32f2870">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__TELEPHONY__INFORMATION__NETWORK.html#gae2ffe560f05c886539f5f7d2d32f2870">wearable</a> applications).</p></li>
-<li><code>telephony_network_get_default_data_subscription()</code>
-<p>Gets the current default subscription for the data service (packet-switched). It returns one of the <code>telephony_network_default_data_subs_e</code> values (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__TELEPHONY__INFORMATION__NETWORK.html#ga6c9c05c55d8059a64cc4d666cf7dabef">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__TELEPHONY__INFORMATION__NETWORK.html#ga6c9c05c55d8059a64cc4d666cf7dabef">wearable</a> applications).</p></li>
-<li><code>telephony_network_get_default_subscription()</code>
-<p>Gets the current default subscription for the voice service (circuit-switched). It returns one of the <code>telephony_network_default_subs_e</code> values (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__TELEPHONY__INFORMATION__NETWORK.html#ga8aecec279bb07cc0a6251f4210edf2dd">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__TELEPHONY__INFORMATION__NETWORK.html#ga8aecec279bb07cc0a6251f4210edf2dd">wearable</a> applications).</p></li>
-<li><code>telephony_network_get_selection_mode()</code>
-<p>Gets the network selection mode. It returns one of the <code>telephony_network_selection_mode_e</code> values (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__TELEPHONY__INFORMATION__NETWORK.html#gad5ec5e1e6b610f7ce7f03f75d710b548">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__TELEPHONY__INFORMATION__NETWORK.html#gad5ec5e1e6b610f7ce7f03f75d710b548">wearable</a> applications).</p></li>
-<li><code>telephony_network_get_tac()</code>
-<p>Gets the TAC (Tracking Area Code) of the current location.</p></li>
-<li><code>telephony_network_get_system_id()</code>
-<p>Gets the system ID of the current location.</p></li>
-<li><code>telephony_network_get_network_id()</code>
-<p>Gets the network ID of the current location.</p></li>
-<li><code>telephony_network_get_base_station_id()</code>
-<p>Gets the base station ID of the current location.</p></li>
-<li><code>telephony_network_get_base_station_latitude()</code>
-<p>Gets the base station latitude of the current location.</p></li>
-<li><code>telephony_network_get_base_station_longitude()</code>
-<p>Gets the base station longitude of the current location.</p></li>
-
-</ul>
-
-<p>To get network-related information change notifications, the application must register for the notifications with the <code>telephony_set_noti_cb()</code> function, by specifying the notification ID.</p>
-
-<p>The following table defines the available notification IDs.</p>
- <p align="center" class="Table"><strong>Table: Network information notification IDs</strong></p>
-<table>
- <tbody>
- <tr>
- <th>Change in state</th>
- <th>Notification ID</th>
- </tr>
- <tr>
- <td>Network service state</td>
- <td><code>TELEPHONY_NOTI_NETWORK_SERVICE_STATE</code></td>
- </tr>
- <tr>
- <td>Cell ID</td>
- <td><code>TELEPHONY_NOTI_NETWORK_CELLID</code></td>
- </tr>
- <tr>
- <td>Roaming status</td>
- <td><code>TELEPHONY_NOTI_NETWORK_ROAMING_STATUS</code></td>
- </tr>
- <tr>
- <td>Signal strength</td>
- <td><code>TELEPHONY_NOTI_NETWORK_SIGNALSTRENGTH_LEVEL</code></td>
- </tr>
- <tr>
- <td>Network name</td>
- <td><code>TELEPHONY_NOTI_NETWORK_NETWORK_NAME</code></td>
- </tr>
- <tr>
- <td>Packet-switched type</td>
- <td><code>TELEPHONY_NOTI_NETWORK_PS_TYPE</code></td>
- </tr>
- <tr>
- <td>Default data subscription</td>
- <td><code>TELEPHONY_NOTI_NETWORK_DEFAULT_DATA_SUBSCRIPTION</code></td>
- </tr>
- <tr>
- <td>Default subscription</td>
- <td><code>TELEPHONY_NOTI_NETWORK_DEFAULT_SUBSCRIPTION</code></td>
- </tr>
- <tr>
- <td>Location Area Code</td>
- <td><code>TELEPHONY_NOTI_NETWORK_LAC</code></td>
- </tr>
- <tr>
- <td>Tracking Area Code</td>
- <td><code>TELEPHONY_NOTI_NETWORK_TAC</code></td>
- </tr>
- <tr>
- <td>System ID</td>
- <td><code>TELEPHONY_NOTI_NETWORK_SYSTEM_ID</code></td>
- </tr>
- <tr>
- <td>Network ID</td>
- <td><code>TELEPHONY_NOTI_NETWORK_NETWORK_ID</code></td>
- </tr>
- <tr>
- <td>Base station ID</td>
- <td><code>TELEPHONY_NOTI_NETWORK_BS_ID</code></td>
- </tr>
- <tr>
- <td>Base station latitude</td>
- <td><code>TELEPHONY_NOTI_NETWORK_BS_LATITUDE</code></td>
- </tr>
- <tr>
- <td>Base station longitude</td>
- <td><code>TELEPHONY_NOTI_NETWORK_BS_LONGITUDE</code></td>
- </tr>
- </tbody>
- </table>
-
-
-<h2 id="modem" name="modem">Modem Information</h2>
-
-<p>The Modem API (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__TELEPHONY__INFORMATION__MODEM.html">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__TELEPHONY__INFORMATION__MODEM.html">wearable</a> applications) provides the following functions:</p>
-<ul><li><code>telephony_modem_get_imei()</code>
-<p>Gets the IMEI (International Mobile Station Equipment Identity) of the mobile phone. You get the IMEI as a string, which needs to be freed by the application.</p></li>
-<li><code>telephony_modem_get_power_status()</code>
-<p>Gets the power status of the modem. It returns one of the <code>telephony_modem_power_status_e</code> values (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__TELEPHONY__INFORMATION__MODEM.html#gabbd5f448dbe923fd92b994378cdee4b5">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__TELEPHONY__INFORMATION__MODEM.html#gabbd5f448dbe923fd92b994378cdee4b5">wearable</a> applications).</p></li>
-<li><code>telephony_modem_get_meid()</code>
-<p>Gets the MEID (Mobile Equipment Identifier) of a mobile phone. You get the MEID as a string, which needs to be freed by the application.</p></li>
-</ul>
+ <p align="center"><strong>Figure: Telephony APIs and telephony service</strong></p>
+ <p align="center"><img alt="Telephony APIs and telephony service" src="../../images/telephony.png" /></p>
<h2 id="prerequisites" name="prerequisites">Prerequisites</h2>
}
</pre></li></ol>
- <h2 id="call_use" name="call_use">Getting Call Information</h2>
+ <h2 id="call_use" name="call_use">Retrieving Call Information</h2>
<p>To get the voice and video call state and be notified when the user makes a voice or video call or hangs up the phone, use the Call API (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__TELEPHONY__INFORMATION__CALL.html">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__TELEPHONY__INFORMATION__CALL.html">wearable</a> applications).</p>
<p>Getting call information involves:</p>
- <h2 id="sim_use" name="sim_use">Getting SIM Card Information</h2>
+ <h2 id="sim_use" name="sim_use">Retrieving SIM Card Information</h2>
<p>To extract information stored on a SIM card, use the SIM API (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__TELEPHONY__INFORMATION__SIM.html">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__TELEPHONY__INFORMATION__SIM.html">wearable</a> applications).</p>
<p>Getting SIM information involves:</p>
<li><a href="#sim_info">Getting SIM card details</a></li>
</ul>
-
+<div class="note">
+ <strong>Note</strong>
+ Before retrieving information from the SIM card, you must retrieve the state of the SIM card. You can get SIM-related information only if the SIM state is <code>TELEPHONY_SIM_STATE_AVAILABLE</code>.
+</div>
<h3 name="sim_state" id="sim_state">Getting the SIM Card State</h3>
-<p>Before retrieving information from the SIM card, retrieve the card state. You can get SIM-related information only if the card state is <code>TELEPHONY_SIM_STATE_AVAILABLE</code>.</p>
+
<p>To get the state, call the <code>telephony_sim_get_state()</code> function. It returns the SIM card state in its second parameter, using the values of the <code>telephony_sim_state_e</code> enumerator (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__TELEPHONY__INFORMATION__SIM.html#ga08448f4cfaf7c59cd585008d3bf32b70">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__TELEPHONY__INFORMATION__SIM.html#ga08448f4cfaf7c59cd585008d3bf32b70">wearable</a> applications).</p>
<h3 name="sim_info" id="sim_info">Getting SIM Card Details</h3>
-<p>If the current SIM card state is <code>SIM_STATE_AVAILABLE</code>, you can call various <code>telephony_sim_get_XXX()</code> functions to retrieve the SIM card details: ICC-ID, operator (MCC+MNC), MSIN, SPN, subscriber number, subscriber ID, and application list.</p>
+<p>You can call various <code>telephony_sim_get_XXX()</code> functions to retrieve the SIM card details: ICC-ID, operator (MCC+MNC), MSIN, SPN, subscriber number, subscriber ID, and application list.</p>
<p>If the functions return <code>SIM_ERROR_NONE</code>, the requested SIM information is received and stored in an output parameter. Free all returned variables when they are no longer needed.</p>
}
</pre>
- <h2 id="network_use" name="network_use">Getting Network Information</h2>
+ <h2 id="network_use" name="network_use">Retrieving Network Information</h2>
<p>To access information about the current cellular network and telephony service, use the Network API (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__TELEPHONY__INFORMATION__NETWORK.html">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__TELEPHONY__INFORMATION__NETWORK.html">wearable</a> applications).</p>
<p>Getting network information involves:</p>
<li><a href="#network_info">Getting network details</a></li>
</ul>
-
-
+<div class="note">
+ <strong>Note</strong>
+ Before retrieving information about the current cellular network and telephony service, you must retrieve the network service state. You can get network-related information only if the network state is <code>TELEPHONY_NETWORK_SERVICE_STATE_IN_SERVICE</code>.
+</div>
<h3 name="network_state" id="network_state">Getting the Network Service State</h3>
-<p>Before retrieving information about the current cellular network and telephony service, retrieve the network service state. You can get the related information only if the service state is <code>TELEPHONY_NETWORK_SERVICE_STATE_IN_SERVICE</code>.</p>
+
<p>To get the state, call the <code>telephony_network_get_service_state()</code> function. It returns the network service state in its second parameter, using the values of the <code>telephony_network_service_state_e</code> enumeration (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__TELEPHONY__INFORMATION__NETWORK.html#gae9f3b6e54a1086b8734f4acc71fd001b">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__TELEPHONY__INFORMATION__NETWORK.html#gae9f3b6e54a1086b8734f4acc71fd001b">wearable</a> applications).</p>
<h3 name="network_info" id="network_info">Getting Network Details</h3>
-<p>If the current network service state is <code>NETWORK_INFO_SERVICE_STATE_IN_SERVICE</code>, you can call various <code>telephony_network_get_XXX()</code> functions to retrieve the network details: LAC, Cell ID, RSSI, roaming state, MCC, MNC, network provider name, PS type, and network type.</p>
+<p>You can call various <code>telephony_network_get_XXX()</code> functions to retrieve the network details: LAC, Cell ID, RSSI, roaming state, MCC, MNC, network provider name, PS type, and network type.</p>
<p>If the functions return <code>TELEPHONY_ERROR_NONE</code>, the requested network information is received and stored in an output parameter. Free all returned variables when they are no longer needed.</p>
<p>For example, to get the cell ID and MNC information:</p>
}
</pre>
- <h2 id="modem_use" name="modem_use">Getting Modem Information</h2>
+ <h2 id="modem_use" name="modem_use">Retrieving Modem Information</h2>
<p>To access information about the modem, use the Modem API (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__TELEPHONY__INFORMATION__MODEM.html">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__TELEPHONY__INFORMATION__MODEM.html">wearable</a> applications).</p>
<p>You can call various <code>telephony_modem_get_XXX()</code> functions to retrieve the modem details: IMEI and power status.</p>
<div id="container"><div id="contents"><div class="content">
<h1>Wi-Fi Direct®</h1>
-<p>Wi-Fi Direct® (synonym for Wi-Fi P2P (Peer-to-Peer)) is a technology that allows you to find nearby Wi-Fi Direct devices and form a Wi-Fi Direct group to communicate over a peer-to-peer link without wireless access points (base stations) in the infrastructure mode.</p>
+<p>Wi-Fi Direct® is a technology that allows you to find nearby Wi-Fi Direct devices and form a Wi-Fi Direct group to communicate over a peer-to-peer link without wireless access points (base stations) in the infrastructure mode. Wi-Fi Direct is a synonym for Wi-Fi P2P (Peer-to-Peer).</p>
<p>This feature is supported in mobile applications only.</p>
<li>Getting the Wi-Fi Direct peer device information
<p>You can <a href="#getting_device_info">discover Wi-Fi Direct peer devices</a> and show Wi-Fi Direct peer device information.</p></li>
<li>Connecting to a specific Wi-Fi Direct peer device
-<p>You can <a href="#connecting_device">connect to a specific Wi-Fi Direct device</a> and disconnect from a specific Wi-Fi Direct device.</p></li>
+<p>You can <a href="#connecting_device">connect to a specific Wi-Fi Direct device</a>. When the connection is no longer needed, you can end it.</p></li>
<li>Managing Wi-Fi Direct groups
<p>You can <a href="#creating_group">create a Wi-Fi Direct group</a> and manage the group.</p></li>
</ul>
<div class="note">
<strong>Note</strong>
- You can test the Wi-Fi Direct functionality only on target devices. The <a href="../../../../org.tizen.studio/html/common_tools/emulator.htm">emulator</a> does not support this feature currently.
+ You can test the Wi-Fi Direct functionality on a target device only. The <a href="../../../../org.tizen.studio/html/common_tools/emulator.htm">emulator</a> does not support this feature.
</div>
<h2 id="prerequisites">Prerequisites</h2>
}
</pre></li>
-<li>Connect with a Wi-Fi Direct peer device.
+<li>Connect to a Wi-Fi Direct peer device.
<p>Check whether Wi-Fi Direct is activated using the <code>wifi_direct_get_state()</code> function, and then get the specific device address.</p>
<p>You can obtain the address directly from the user (as in the following example), or by calling the <code>wifi_direct_foreach_discovered_peers()</code> function to the address through the device discovery process.</p>
</ul>
<p class="toc-title">Content</p>
<ul class="toc">
- <li><a href="#wifi_manager">Wi-Fi Manager</a></li>
- <li><a href="#ap">Access Point</a></li>
- <li><a href="#wifi_monitor">Wi-Fi Monitor</a></li>
<li><a href="#prerequisites">Prerequisites</a></li>
<li><a href="#activate">Activating a Wi-Fi Device</a></li>
<li><a href="#scan">Scanning for Access Points</a></li>
<div id="container"><div id="contents"><div class="content">
<h1>Wi-Fi</h1>
-<p>Tizen allows your application to connect to a Wireless Local Area Network (WLAN) and transfer data over the network. The Wi-Fi Manager enables your application to activate and deactivate a local Wi-Fi device, and to connect to a WLAN network in the infrastructure mode.</p>
+<p>You can connect to a Wireless Local Area Network (WLAN) and transfer data over the network. The Wi-Fi Manager enables your application to activate and deactivate a local Wi-Fi device, and to connect to a WLAN network in the infrastructure mode.</p>
<p>The main features of the Wi-Fi Manager API include:</p>
<ul><li>Wi-Fi device and connection management
-<p> You can use the <a href="#wifi_manager">Wi-Fi Manager</a> to implement and manage Wi-Fi connection features.</p></li>
-<li>Access point management
-<p>You can <a href="#ap">manage the Wi-Fi account and security information</a>.</p>
-<p>The infrastructure mode is used to connect to a wireless local area network (WLAN). The infrastructure mode requires a wireless access point. To connect to a WLAN, a client must be configured to use the same service set identifier (SSID) as the access point.</p></li>
+<p> You can to implement and manage Wi-Fi connections with the Wi-Fi Manager API (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__NETWORK__WIFI__MANAGER__MODULE.html">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__NETWORK__WIFI__MANAGER__MODULE.html">wearable</a> applications). For example, you can <a href="#activate">activate or deactivate</a> a local Wi-Fi device, <a href="#connect">connect to an access point</a> asynchronously, and <a href="#scan">scan for available access points</a> and retrieve information from the found access points.</p>
+</li>
+<li id="ap">Access point management
+<p>You can connect to a specific access point (AP) with the Access Point API (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__NETWORK__WIFI__MANAGER__AP__MODULE.html">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__NETWORK__WIFI__MANAGER__AP__MODULE.html">wearable</a> applications). The infrastructure mode is used to connect to a wireless local area network (WLAN). The infrastructure mode requires a wireless AP. To connect to a WLAN, a client must be configured to use the same service set identifier (SSID) as the AP.</p>
+<p>To manage APs, you must create an AP handle (<code>wifi_manager_ap_h</code>), which allows you to retrieve Wi-Fi network and security information:</p>
+ <ul>
+ <li>Network information details, such as the SSID, frequency band, and maximum speed of the access point, are available through the Network Information API (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__NETWORK__WIFI__MANAGER__AP__NETWORK__MODULE.html">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__NETWORK__WIFI__MANAGER__AP__NETWORK__MODULE.html">wearable</a> applications).</li>
+ <li>Security information details, such as the used encryption type and whether WPS is supported, are available through the Security Information API (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__NETWORK__WIFI__MANAGER__AP__SECURITY__MODULE.html">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__NETWORK__WIFI__MANAGER__AP__SECURITY__MODULE.html">wearable</a> applications).
+ <p>You can also obtain EAP information through the EAP API (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__NETWORK__WIFI__MANAGER__AP__SECURITY__EAP__MODULE.html">mobile</a> and <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__NETWORK__WIFI__MANAGER__AP__SECURITY__EAP__MODULE.html">wearable</a> applications).</p></li>
+ </ul>
+</li>
<li>Wi-Fi state monitoring
-<p>You can use the <a href="#wifi_monitor">Wi-Fi Monitor</a> to monitor the Wi-Fi connection state.</p></li>
-</ul>
-
+<p>You can register a callback with the Wi-Fi Monitor API (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__NETWORK__WIFI__MANAGER__MONITOR__MODULE.html">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__NETWORK__WIFI__MANAGER__MONITOR__MODULE.html">wearable</a> applications) to monitor the Wi-Fi connection state changes. The supported states are defined in the <code>wifi_manager_connection_state_e</code> enumerator (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__NETWORK__WIFI__MANAGER__MONITOR__MODULE.html#gafa0bc807592532fbd1fa3a4df82b24b2">mobile</a> and <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__NETWORK__WIFI__MANAGER__MONITOR__MODULE.html#gafa0bc807592532fbd1fa3a4df82b24b2">wearable</a> applications).</p>
+<p>You can also register callbacks for monitoring changes in the Wi-Fi device state (whether Wi-Fi is activated) and the RSSI level of the Wi-Fi connection.</p>
+</li></ul>
<div class="note">
<strong>Note</strong>
You can test the Wi-Fi functionality only on a target device. The emulator does not support this feature.
</div>
-
-<h2 id="wifi_manager" name="wifi_manager">Wi-Fi Manager</h2>
-
-<p>The Tizen Wi-Fi Manager API (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__NETWORK__WIFI__MANAGER__MODULE.html">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__NETWORK__WIFI__MANAGER__MODULE.html">wearable</a> applications) provides functions for using a Wi-Fi connection. </p>
-<p>Using the Wi-Fi Manager, you can implement features that allow the users of your application to:</p>
-
-<ul><li>Activate and deactivate a Wi-Fi device
-<p>You can <a href="#activate">activate and deactivate a local Wi-Fi device</a> using the <code>wifi_manager_activate()</code> and <code>wifi_manager_deactivate()</code> functions. Both functions have a callback function as the first parameter. The callback function is called after the activation or deactivation is completed. You can use the <code>NULL</code> value, if you want no notifications.</p>
-</li>
-<li>Connect to an access point
-<p>You can <a href="#connect">connect to an access point</a> asynchronously using the <code>wifi_manager_connect()</code> function.</p>
-</li>
-<li>Scan the access points
-<p>To <a href="#scan">scan access points</a>, use the <code>wifi_manager_scan()</code> and <code>wifi_manager_foreach_found_ap()</code> functions.</p>
-<p>The <code>wifi_manager_scan()</code> function starts the scan asynchronously. When the scan is finished, a callback function is called. The <code>wifi_manager_foreach_found_ap()</code> function allows you to get the result of the scan. It also invokes a callback function.</p></li></ul>
-
-<h2 id="ap" name="ap">Access Point</h2>
-
-<p>The Access Point API (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__NETWORK__WIFI__MANAGER__AP__MODULE.html">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__NETWORK__WIFI__MANAGER__AP__MODULE.html">wearable</a> applications) provides functions for managing access points (AP). You need to create an AP handle (<code>wifi_manager_ap_h</code>) for using the API functions. </p>
-
-<p>The Access Point API supports the following main features:</p>
-<ul><li>Creating and destroying an AP handle</li>
-<li>Getting the network information</li>
-<li>Getting the security information</li></ul>
-
-<p>The following table lists the network information details you can access with the Network Information API (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__NETWORK__WIFI__MANAGER__AP__NETWORK__MODULE.html">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__NETWORK__WIFI__MANAGER__AP__NETWORK__MODULE.html">wearable</a> applications).</p>
-
-<p align="center" class="Table"><strong>Table: Network information details</strong></p>
- <table>
- <tbody>
- <tr>
- <th>Information</th>
- <th>Description</th>
- </tr>
- <tr>
- <td>Bssid</td>
- <td>Basic service set identifier</td>
- </tr>
- <tr>
- <td>Connection state</td>
- <td>Connection state</td>
- </tr>
- <tr>
- <td>DNS address</td>
- <td>DNS address</td>
- </tr>
- <tr>
- <td>Essid</td>
- <td>Extended service set identifier</td>
- </tr>
- <tr>
- <td>Frequency</td>
- <td>Frequency (in MHz)</td>
- </tr>
- <tr>
- <td>IP address</td>
- <td>IP address</td>
- </tr>
- <tr>
- <td>IP config type</td>
- <td>Net IP configuration type</td>
- </tr>
- <tr>
- <td>Max speed</td>
- <td>Maximum speed (in Mbps)</td>
- </tr>
- <tr>
- <td>Proxy address</td>
- <td>Proxy address</td>
- </tr>
- <tr>
- <td>Proxy type</td>
- <td>Proxy method type</td>
- </tr>
- <tr>
- <td>Rssi</td>
- <td>Received signal strength indication</td>
- </tr>
- <tr>
- <td>Subnet mask</td>
- <td>Subnet mask</td>
- </tr>
- </tbody>
- </table>
-
-
-<p>The following table lists the security information details you can access with the Security Information API (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__NETWORK__WIFI__MANAGER__AP__SECURITY__MODULE.html">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__NETWORK__WIFI__MANAGER__AP__SECURITY__MODULE.html">wearable</a> applications).</p>
-<p align="center" class="Table"><strong>Table: Security information details</strong></p>
- <table>
- <tbody>
- <tr>
- <th>Information</th>
- <th>Description</th>
- </tr>
- <tr>
- <td>Encryption type</td>
- <td>Wi-Fi encryption type, used in the infrastructure and ad-hoc mode</td>
- </tr>
- <tr>
- <td>Security type</td>
- <td>Wi-Fi security type</td>
- </tr>
- <tr>
- <td>Passphrase required</td>
- <td>Whether the passphrase is required</td>
- </tr>
- <tr>
- <td>WPS supported</td>
- <td>Whether the WPS (Wi-Fi Protected Setup) is supported</td>
- </tr>
- </tbody>
- </table>
-
-<p>You can also obtain the EAP information listed in the following table.</p>
-<p align="center" class="Table"><strong>Table: EAP information details</strong></p>
- <table>
- <tbody>
- <tr>
- <th>Information</th>
- <th>Description</th>
- </tr>
- <tr>
- <td>Authentication type</td>
- <td>Type of EAP phase2 authentication of Wi-Fi</td>
- </tr>
- <tr>
- <td>CA certificate</td>
- <td>EAP CA certificate (valid only if the EAP type is TLS)</td>
- </tr>
- <tr>
- <td>Client Certificate</td>
- <td>EAP client certificate (valid only if the EAP type is TLS)</td>
- </tr>
- <tr>
- <td>Passphrase</td>
- <td>EAP passphrase (valid if the EAP type is PEAP or TTLS)</td>
- </tr>
- <tr>
- <td>Private key file</td>
- <td>EAP private key file (valid only if the EAP type is TLS)</td>
- </tr>
- <tr>
- <td>EAP type</td>
- <td>EAP type of Wi-Fi</td>
- </tr>
- </tbody>
- </table>
-
-<h2 id="wifi_monitor" name="wifi_monitor">Wi-Fi Monitor</h2>
-
-<p>The Wi-Fi Monitor API (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__NETWORK__WIFI__MANAGER__MONITOR__MODULE.html">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__NETWORK__WIFI__MANAGER__MONITOR__MODULE.html">wearable</a> applications) provides functions for monitoring the Wi-Fi connection state.</p>
-
-<p>The Wi-Fi Monitor allows you to get the state of the Wi-Fi connection. The state can be:</p>
-
-<ul><li><code>WIFI_CONNECTION_STATE_FAILURE</code>
-<p>Connection failed.</p></li>
-<li><code>WIFI_CONNECTION_STATE_DISCONNECTED</code>
-<p>Disconnected.</p></li>
-<li><code>WIFI_CONNECTION_STATE_ASSOCIATION</code>
-<p>Association.</p></li>
-<li><code>WIFI_CONNECTION_STATE_CONFIGURATION</code>
-<p>Configuration.</p></li>
-<li><code>WIFI_CONNECTION_STATE_CONNECTED</code>
-<p>Connected.</p></li></ul>
-
-<p>The Wi-Fi Monitor also allows monitoring the changes in Wi-Fi. With the Wi-Fi Monitor, you can register callback functions, which notify you when Wi-Fi properties change. The property changes resulting in notifications are listed in the following table.</p>
-
-<p align="center" class="Table"><strong>Table: Property changes</strong></p>
-<table>
- <tbody>
- <tr>
- <th>Change in</th>
- <th>Description</th>
- </tr>
- <tr>
- <td>Connection state</td>
- <td>The callback is called when the connection state is changed.</td>
- </tr>
- <tr>
- <td>Device state</td>
- <td>The callback is called when the device state changes.</td>
- </tr>
- <tr>
- <td>RSSI level</td>
- <td>The callback is called when the RSSI of the connected Wi-Fi changes.</td>
- </tr>
- </tbody>
- </table>
-
<h2 id="prerequisites">Prerequisites</h2>
<p>To enable your application to use the Wi-Fi functionality:</p>
}
</pre>
-<p>You can get other information, including frequency, IP address, and security type. For more information, see the <a href="#ap">Access Point</a>.</p></li></ol>
+<p>You can get other information, including frequency, IP address, and security type. For more information, see <a href="#ap">access point management</a>.</p></li></ol>
<h2 id="connect" name="connect">Connecting to a Specific Access Point</h2>
<li><a href="#storage">Retrieving Storage Information</a></li>
<li><a href="#state">Monitoring Storage State Changes</a></li>
<li><a href="#space">Retrieving Storage Space Information</a></li>
+ <li><a href="#virtualroots">Virtual Roots</a></li>
</ul>
<p class="toc-title">Related Info</p>
<ul class="toc">
<div id="container"><div id="contents"><div class="content">
<h1>Data Storages</h1>
- <p>Tizen enables you to get storage information and manage directories.</p>
- <p>The Storage API provides access to accessible parts of the file system, which are represented as virtual root locations. The virtual roots form a collection of locations that function as a single virtual device file system. The following table lists the supported virtual roots.</p>
-<p align="center" class="Table"><strong>Table: Filesystem virtual roots</strong></p>
- <table border="1" style="width: 100%">
- <tbody>
- <tr>
- <th>Virtual root</th>
- <th>Description</th>
- </tr>
- <tr>
- <td><code>images</code></td>
- <td>Location for storing images.</td>
- </tr>
- <tr>
- <td><code>sounds</code></td>
- <td>Location for storing sound files.</td>
- </tr>
- <tr>
- <td><code>videos</code></td>
- <td>Location for storing video files.</td>
- </tr>
- <tr>
- <td><code>camera</code></td>
- <td>Location for storing photos.</td>
- </tr>
- <tr>
- <td><code>downloads</code></td>
- <td>Location for storing downloaded items.</td>
- </tr>
- <tr>
- <td><code>music</code></td>
- <td>Location for storing audio files.</td>
- </tr>
- <tr>
- <td><code>documents</code></td>
- <td>Location for storing documents.</td>
- </tr>
- <tr>
- <td><code>others</code></td>
- <td>Location for storing other files.</td>
- </tr>
- <tr>
- <td><code>ringtones</code></td>
- <td>Location for ringtones (read-only location).</td>
- </tr>
- </tbody>
- </table>
+ <p>You can access storage information and manage directories within certain parts of the file system, represented as <a href="#virtualroots">virtual root locations</a>. These virtual roots form a collection of locations that function as a single virtual device file system.</p>
<p>The main features of the Storage API include:</p>
<ul>
- <li>Storage management <p>You can manage different storages on the device with the Storage APIs.</p> <p>You can <a href="#storage">retrieve additional information about the storages</a>, including which storage is supported on the device using the <code>storage_foreach_device_supported()</code> function. The callback function returns the storage type, mount state, and virtual root path. You can also <a href="#memory">retrieve memory sizes</a> and <a href="#state">monitor storage state changes</a>.</p>
+ <li>Storage management
+ <p>You can manage different storage locations on the device.</p>
+ <p>You can <a href="#storage">retrieve additional information about the storage locations</a>, including which storage is supported on the device, by using the <code>storage_foreach_device_supported()</code> function. The callback function returns the storage type, mount state, and virtual root path. You can also <a href="#memory">retrieve memory sizes</a> and <a href="#state">monitor storage state changes</a>.</p>
</li>
<li>Storage space management
- <p>You can <a href="#space">get the available and total space</a> size of the storage.</p></li></ul>
+ <p>You can <a href="#space">get the available and total size</a> of the storage.</p></li></ul>
<h2 id="prerequisites">Prerequisites</h2>
<p>To use the functions and data types of the Storage API (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__SYSTEM__STORAGE__MODULE.html">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__SYSTEM__STORAGE__MODULE.html">wearable</a> applications), include the <code><storage.h></code> header file in your application:</p>
<p>To retrieve storage information:</p>
<ul>
-<li>Retrieve all storages on a device using the <code>storage_foreach_device_supported()</code> function.
+<li>Retrieve all storages on a device by using the <code>storage_foreach_device_supported()</code> function.
<p>The function triggers a separate callback for each storage. As long as the callback returns <code>true</code>, the foreach function continues to loop over the storages.</p>
<p>Within the callback, you can get information about the individual storage type, state, location, and ID.</p>
</pre>
</li>
-<li>Get the root directory of a specific storage using the <code>storage_get_root_directory()</code> function.
+<li>Get the root directory of a specific storage by using the <code>storage_get_root_directory()</code> function.
<p>The function retrieves the absolute path to the root directory.</p>
<pre class="prettyprint">
</pre>
</li>
-<li>Get the directory of a specific type within a specific storage using the <code>storage_get_directory()</code> function.
+<li>Get the directory path for a storage of a specific type by using the <code>storage_get_directory()</code> function.
<p>The function retrieves the absolute path to the directory.</p>
<p>The second parameter defines the directory type based on the <code>storage_directory_e</code> enumerator (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__SYSTEM__STORAGE__MODULE.html#gaacf2209a06b947c1cee4ba223679383a">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__SYSTEM__STORAGE__MODULE.html#gaacf2209a06b947c1cee4ba223679383a">wearable</a> applications).</p>
</pre>
</li>
-<li>Get the storage type of a specified storage using the <code>storage_get_type()</code> function.
+<li>Get the storage type of a specific storage by using the <code>storage_get_type()</code> function.
<p>The <code>storage_type_e</code> enumerator (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__SYSTEM__STORAGE__MODULE.html#gabdf32571260b6c253da5bfcdecaa2f1f">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__SYSTEM__STORAGE__MODULE.html#gabdf32571260b6c253da5bfcdecaa2f1f">wearable</a> applications) defines the available storage types.</p>
</pre>
</li>
-<li>Get the storage mount state of a specific storage using the <code>storage_get_state()</code> function.
+<li>Get the mount state of a specific storage by using the <code>storage_get_state()</code> function.
<p>The <code>storage_state_e</code> enumerator (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__SYSTEM__STORAGE__MODULE.html#gac72d0e57e790d888dfd7bd57d52fbfee">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__SYSTEM__STORAGE__MODULE.html#gac72d0e57e790d888dfd7bd57d52fbfee">wearable</a> applications) defines the available storage states.</p>
<p>To retrieve storage space information:</p>
<ul>
-<li>Get the total space of the storage using the <code>storage_get_total_space()</code> function.
+<li>Get the total space of the storage by using the <code>storage_get_total_space()</code> function.
<p>The function returns the total space of the given storage in bytes. It invokes the <code>storage_get_internal_memory_size()</code> or <code>storage_get_external_memory_size()</code> function internally.</p>
<pre class="prettyprint">
</pre>
</li>
-<li>Get the available space of the storage using the <code>storage_get_available_space()</code> function.
+<li>Get the available space of the storage by using the <code>storage_get_available_space()</code> function.
<p>The function returns the available space of the given storage in bytes. It invokes the <code>storage_get_internal_memory_size()</code> or <code>storage_get_external_memory_size()</code> function internally.</p>
<pre class="prettyprint">
</pre></li>
</ul>
+
+<h2 id="virtualroots">Virtual Roots</h2>
+
+<p>The following table lists the supported virtual roots.<p>
+
+<p align="center" class="Table"><strong>Table: Filesystem virtual roots</strong></p>
+ <table border="1" style="width: 100%">
+ <tbody>
+ <tr>
+ <th>Virtual root</th>
+ <th>Description</th>
+ </tr>
+ <tr>
+ <td><code>images</code></td>
+ <td>Location for storing images.</td>
+ </tr>
+ <tr>
+ <td><code>sounds</code></td>
+ <td>Location for storing sound files.</td>
+ </tr>
+ <tr>
+ <td><code>videos</code></td>
+ <td>Location for storing video files.</td>
+ </tr>
+ <tr>
+ <td><code>camera</code></td>
+ <td>Location for storing photos.</td>
+ </tr>
+ <tr>
+ <td><code>downloads</code></td>
+ <td>Location for storing downloaded items.</td>
+ </tr>
+ <tr>
+ <td><code>music</code></td>
+ <td>Location for storing audio files.</td>
+ </tr>
+ <tr>
+ <td><code>documents</code></td>
+ <td>Location for storing documents.</td>
+ </tr>
+ <tr>
+ <td><code>others</code></td>
+ <td>Location for storing other files.</td>
+ </tr>
+ <tr>
+ <td><code>ringtones</code></td>
+ <td>Location for ringtones (read-only location).</td>
+ </tr>
+ </tbody>
+ </table>
+
<script type="text/javascript" src="../../scripts/jquery.zclip.min.js"></script>
<script type="text/javascript" src="../../scripts/showhide.js"></script>
</div></div></div>
<div id="container"><div id="contents"><div class="content">
<h1>Attached Devices</h1>
- <p>The attached device features provide functions to control attached devices and monitor device changes.</p>
+ <p>You can control attached devices and monitor device changes in your application.</p>
<p>The main features of the Device API include:</p>
<ul><li>Battery information
<li>Display
<p>You can <a href="#display">get and set display details</a>, such as the number of displays, the maximum brightness of the display, the current brightness, and the display state, using the Display API (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__SYSTEM__DEVICE__DISPLAY__MODULE.html">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__SYSTEM__DEVICE__DISPLAY__MODULE.html">wearable</a> applications).</p></li>
<li>Haptic
- <p>You can <a href="#haptic">manage
the haptic devices</a> by, for example, getting the number of haptic devices, opening or closing the haptic handle, and requesting the vibration effects to play or stop, with the Haptic API (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__SYSTEM__DEVICE__HAPTIC__MODULE.html">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__SYSTEM__DEVICE__HAPTIC__MODULE.html">wearable</a> applications).</p></li>
+ <p>You can <a href="#haptic">manage
haptic devices</a> by, for example, getting the number of haptic devices, opening or closing the haptic handle, and requesting vibration effect playback, with the Haptic API (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__SYSTEM__DEVICE__HAPTIC__MODULE.html">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__SYSTEM__DEVICE__HAPTIC__MODULE.html">wearable</a> applications).</p></li>
<li>IR
- <p>You can <a href="#ir">manage
the IR devices</a> by, for example, determining whether an IR device is available and transmitting an IR pattern, using the IR API (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__SYSTEM__DEVICE__IR__MODULE.html">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__SYSTEM__DEVICE__IR__MODULE.html">wearable</a> applications).</p></li>
+ <p>You can <a href="#ir">manage IR devices</a> by, for example, determining whether an IR device is available and transmitting an IR pattern, using the IR API (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__SYSTEM__DEVICE__IR__MODULE.html">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__SYSTEM__DEVICE__IR__MODULE.html">wearable</a> applications).</p></li>
<li>LED
- <p>You can <a href="#led">manage the camera flash LED</a> by, for example, getting the maximum and current brightness of the LED. You can also change the current brightness of the camera flash LED, and request the service LED to play
or stop effects using the Led API (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__SYSTEM__DEVICE__LED__MODULE.html">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__SYSTEM__DEVICE__LED__MODULE.html">wearable</a> applications).</p></li>
+ <p>You can <a href="#led">manage the camera flash LED</a> by, for example, getting the maximum and current brightness of the LED. You can also change the current brightness of the camera flash LED, and request the service LED to play effects using the Led API (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__SYSTEM__DEVICE__LED__MODULE.html">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__SYSTEM__DEVICE__LED__MODULE.html">wearable</a> applications).</p></li>
<li>Power
<p>You can <a href="#power">request the power state</a> to be locked or unlocked using the Power API (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__SYSTEM__DEVICE__POWER__MODULE.html">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__SYSTEM__DEVICE__POWER__MODULE.html">wearable</a> applications).</p></li>
</ul></li>
<p>To retrieve battery information:</p>
<ul>
- <li>Get the battery percentage with the <code>device_battery_get_percent()</code> function.
+ <li>Get the battery charge percentage with the <code>device_battery_get_percent()</code> function.
<p>The function returns the current battery percentage as an integer value from 0 to 100 that indicates the remaining battery charge as a percentage of the maximum level.</p>
<pre class="prettyprint">
error = device_battery_get_percent(&pct);
</pre></li>
- <li>Get the current charging battery state with the <code>device_battery_is_charging()</code> function:
+ <li>Get the current battery charging state with the <code>device_battery_is_charging()</code> function:
<pre class="prettyprint">
int error;
</pre>
</li>
- <li>Get the current battery level state with the <code>device_battery_get_level_status()</code> function.
+ <li>Get the current battery level with the <code>device_battery_get_level_status()</code> function.
<p>The <code>device_battery_level_e</code> enumerator (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__SYSTEM__DEVICE__BATTERY__MODULE.html#ga63913a4983cc34e35dcdd670e8fe99e4">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__SYSTEM__DEVICE__BATTERY__MODULE.html#ga63913a4983cc34e35dcdd670e8fe99e4">wearable</a> applications) defines the available battery levels.</p>
<pre class="prettyprint">
int error;
</pre>
</li>
- <li>Get the maximum brightness with the <code>device_display_get_max_brightness()</code> function.
+ <li>Get the maximum possible brightness with the <code>device_display_get_max_brightness()</code> function.
<p>The function returns the maximum brightness value that can be set.</p>
<pre class="prettyprint">
</li>
<li>Play and stop an effect on the device with the <code>device_haptic_vibrate()</code> and <code>device_haptic_stop()</code> functions.
-<p>The device vibrates during specified time with a constant intensity. The effect handle can be 0.</p>
+<p>The device vibrates for a specified time with a constant intensity. The effect handle can be 0.</p>
<pre class="prettyprint">
int error;
haptic_effect_h effect_handle;
</pre>
</li>
-<li>Play and stop a custom effect of the service LED with the <code>device_led_play_custom()</code> and <code>device_led_stop_custom()</code> functions.
+<li>Play and stop a custom effect on the service LED with the <code>device_led_play_custom()</code> and <code>device_led_stop_custom()</code> functions.
<p>The <code>led_custom_flags</code> enumerator (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__SYSTEM__DEVICE__LED__MODULE.html#ga2065bc82e5ecf7e2acba8629c0d75e3b">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__SYSTEM__DEVICE__LED__MODULE.html#ga2065bc82e5ecf7e2acba8629c0d75e3b">wearable</a> applications) defines the available custom effects.</p>
<p>The custom effect plays on the service LED that is located on the front of the device.</p>
<p class="toc-title">Content</p>
<ul class="toc">
<li><a href="#prerequisites">Prerequisites</a></li>
- <li><a href="#play">Playing Feedback for a Specific Pattern</a></li>
- <li><a href="#playtype">Playing Feedback for a Specific Type and Pattern</a></li>
+ <li><a href="#play">Playing Feedback with a Specific Pattern</a></li>
+ <li><a href="#playtype">Playing Feedback with a Specific Type and Pattern</a></li>
<li><a href="#support">Checking for Pattern Support</a></li>
</ul>
<p class="toc-title">Related Info</p>
<div id="container"><div id="contents"><div class="content">
<h1>Sound and Vibration Feedback</h1>
- <p>You can play feedback for a specific pattern or play it for a specific type and pattern. You can also check whether a specific pattern is supported.</p>
+ <p>You can play feedback with a specific pattern or play it with a specific type and pattern. You can also check whether a specific pattern is supported.</p>
<p>The main features of the Feedback API include:</p>
<ul>
- <li>Playing feedback for a specific pattern
- <p>You can <a href="#play">play a sound and vibrate for a specific pattern</a>.</p></li>
+ <li>Playing a specific feedback pattern
+ <p>You can <a href="#play">play a sound or vibrate with a specific pattern, or both</a>.</p></li>
<li>Playing feedback for a specific type and pattern
- <p>You can <a href="#playtype">play a sound and vibrate for a specific type and pattern</a>.</p></li>
+ <p>You can <a href="#playtype">play a sound and vibrate with a specific type and pattern</a>.</p></li>
<li>Checking for pattern support
<p>You can <a href="#support">determine whether a specific pattern is supported</a>.</p></li>
</ul>
#include <feedback.h>
</pre>
-<h2 id="play" name="play">Playing Feedback for a Specific Pattern</h2>
+<h2 id="play" name="play">Playing Feedback with a Specific Pattern</h2>
-<p>To play a sound and vibrate for a specific pattern, use the <code>feedback_play()</code> function.</p>
+<p>To play a sound and vibrate with a specific pattern, use the <code>feedback_play()</code> function.</p>
<p>Internally, the function invokes the <code>sound_play</code> or <code>vibrator_play</code> feedback type. It returns success when the pattern enum is valid.</p>
<pre class="prettyprint">
int ret;
</pre>
<p>The return value defines whether playing the feedback was successful.</p>
-<h2 id="playtype" name="playtype">Playing Feedback for a Specific Type and Pattern</h2>
+<h2 id="playtype" name="playtype">Playing Feedback with a Specific Type and Pattern</h2>
-<p>To play a sound and vibrate for a specific type and pattern, use the <code>feedback_play_type()</code> function.</p>
+<p>To play a sound and vibrate with a specific type and pattern, use the <code>feedback_play_type()</code> function.</p>
<p>Internally, the function invokes the <code>sound_play</code> or <code>vibrator_play</code> feedback type. It returns success when the pattern enum is valid.</p>
<pre class="prettyprint">
static int ret;
-ret = feedback_play(type, pattern);
+ret = feedback_play_type(type, pattern);
</pre>
<p>The return value defines whether playing the feedback was successful.</p>
<div id="container"><div id="contents"><div class="content">
<h1>Runtime Information</h1>
- <p>Tizen provides various runtime information and enables your application to access it and monitor changes in it.</p>
+ <p>You can access various runtime information and monitor changes in it.</p>
<p>The main features of the Runtime Information API include:</p>
<ul>
<li>Getting runtime information with a key-value pair
<div id="container"><div id="contents"><div class="content">
<h1>System Information</h1>
- <p>System information features enable your application to retrieve information about fixed platform features or device capabilities by querying system information keys. You can also check for supported features.</p>
+ <p>You can access various information about fixed platform features or device capabilities by querying system information keys. You can also check for supported features.</p>
<p>The main features of the System Information API include:</p>
<ul>
<li><a href="#settings">Geofence Management through My Places</a></li>
<li><a href="#prerequisites">Prerequisites</a></li>
<li><a href="#start">Starting the Geofence Service</a></li>
- <li><a href="#status">Getting the Geofence Event State</a></li>
- <li><a href="#track">Tracking the User for Geofence Alerts</a></li>
+ <li><a href="#status">Monitoring Geofence State Changes</a></li>
+ <li><a href="#track">Tracking the User for Geofence Crossing Alerts</a></li>
<li><a href="#proximity">Tracking the User for Proximity Alerts</a></li>
<li><a href="#info">Retrieving Geofence Information</a></li>
</ul>
<div id="container"><div id="contents"><div class="content">
<h1>Geofences</h1>
-<p>A geofence is a virtual perimeter for a real-world geographic area. A geofence is defined by either a geopoint with a radius for geopoint geofences, or a MAC address for Wi-Fi and Bluetooth geofences. The geofence feature alerts the user when the geofence state changes (the user crosses the perimeter).</p>
+<p>A geofence is a virtual perimeter for a real-world geographic area. A geofence is defined by either a geopoint and radius for geopoint geofences, or by a MAC address for Wi-Fi and Bluetooth geofences. The geofence feature alerts the user when the geofence state changes (the user crosses the perimeter).</p>
<p>This feature is supported in mobile applications only.</p>
<li><a href="#start">Create different types of geofences</a></li>
<li><a href="#status">Get the current state</a></li>
<li>Get <a href="#track">in and out alerts</a> and <a href="#proximity">proximity alerts</a>
- <p>You can get notifications about the in or out state and the proximity state based on the geofence defined by the user.</p></li>
+ <p>You can get notifications when the user approaches or crosses any geofences they have defined.</p></li>
<li><a href="#info">Retrieve information about created geofences</a></li>
</ul>
<p>The geofence manager is set to <code>GEOFENCE_MANAGER_ERROR_NONE</code> if it is working correctly. The device can receive alerts about the geofence when a particular geofence service is started using the <code>geofence_manager_start_geofence()</code> function.</p>
-<p>If the user revokes a permission to use the location information, the geofence manager state is set to <code>GEOFENCE_MANAGER_PERMISSION_DENIED</code> and the same error is returned back to the application invoking the geofence service.</p>
+<p>If the user revokes permission to use the location information, the geofence manager state is set to <code>GEOFENCE_MANAGER_PERMISSION_DENIED</code> and the same error is returned to the application attempting to use the geofence service.</p>
-<p>Asynchronous geofence-related alerts (in or out) and event callbacks (a fence added or removed) are implemented with callback interfaces.
The alerts are received using the <code>GEOFENCE_STATE_UNCERTAIN</code>, <code>GEOFENCE_STATE_IN</code>, and <code>GEOFENCE_STATE_OUT</code> values of the <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__GEOFENCE__MANAGER__MODULE.html#ga266085fcc5f8fa9af62e54efe08cd912">geofence_state_e</a> enumerator.</p>
+<p>Asynchronous geofence-related alerts (in or out) and event callbacks (a fence added or removed) are implemented with callback interfaces.
Geofence alerts are received using the <code>GEOFENCE_STATE_UNCERTAIN</code>, <code>GEOFENCE_STATE_IN</code>, and <code>GEOFENCE_STATE_OUT</code> values of the <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__GEOFENCE__MANAGER__MODULE.html#ga266085fcc5f8fa9af62e54efe08cd912">geofence_state_e</a> enumerator.</p>
<h2 id="definition" name ="definition">Geofence Definition</h2>
-<p>The geofence definition defines the parameters of a geofence.</p>
-<p>The 3 types of available geofences are geopoint, Wi-Fi, and Bluetooth. When creating the geofence,
the type can be defined using the <code>GEOFENCE_TYPE_GEOPOINT</code>, <code>GEOFENCE_TYPE_WIFI</code>, and <code>GEOFENCE_TYPE_BT</code> values of the <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__GEOFENCE__MANAGER__MODULE.html#ga15a724d2959e78b49b78b877e964f513">geofence_type_e</a> enumerator.</p>
-<p>The geopoint geofences require a geopoint and a radius, and the Wi-Fi and Bluetooth geofences require a MAC address. Based on the defined geofence type, the geofence manager creates the fence for the particular application.</p>
+<p>Geofence definition defines the parameters of a geofence.</p>
+<p>The 3 types of available geofences are geopoint, Wi-Fi, and Bluetooth. When creating the geofence,
define the type using the <code>GEOFENCE_TYPE_GEOPOINT</code>, <code>GEOFENCE_TYPE_WIFI</code>, and <code>GEOFENCE_TYPE_BT</code> values of the <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__GEOFENCE__MANAGER__MODULE.html#ga15a724d2959e78b49b78b877e964f513">geofence_type_e</a> enumerator.</p>
+<p>Creating a geopoint geofence requires a geopoint and a radius, whereas Wi-Fi and Bluetooth geofences require a MAC address. Based on the defined geofence type, the geofence manager creates the fence for the particular application.</p>
<h2 id="settings" name="settings">Geofence Management through My Places</h2>
- <p>Tizen provides the user a way of managing the geofence places and fences through the My places application. The following figure shows the default places and supported fences.</p>
+ <p>Tizen provides the user a way of managing geofence places and fences through the My places application. The following figure shows the default places and supported fences.</p>
<p align="center"><strong>Figure: My places</strong></p>
<p align="center"><img alt="My places" src="../../images/geofence_setting.png" style="display: block; text-align: center; margin-left: auto; margin-right: auto" /></p>
- <p>My places controls the adding, removing, and updating of places and fences. <strong>Home</strong>, <strong>Office</strong>, and <strong>Car</strong> are the default places, and <strong>Map</strong>, <strong>Wi-Fi</strong>, and <strong>Bluetooth</strong> are the supported fence methods. <strong>Car</strong> supports only Wi-Fi and Bluetooth for a fence method.</p>
+ <p>My places controls the adding, removing, and updating of places and fences. <strong>Home</strong>, <strong>Office</strong>, and <strong>Car</strong> are the default places, and <strong>Map</strong>, <strong>Wi-Fi</strong>, and <strong>Bluetooth</strong> are the supported fence methods. <strong>Car</strong> supports only Wi-Fi and Bluetooth as fence methods.</p>
<h2 id="prerequisites">Prerequisites</h2>
geofence_manager_start(manager, geofence_id);
</pre></li>
-<li><p>Using the geofence service for geopoints is power consuming, so if the service is not used, stop the status alerts using the <code>geofence_manager_stop()</code> function. Call the <code>geofence_manager_start()</code> function again if the alerts are needed.</p>
+<li><p>Using the geofence service for geopoints adds to power consumption, so if the service is not used, stop the status alerts using the <code>geofence_manager_stop()</code> function. Call the <code>geofence_manager_start()</code> function again if the alerts are needed.</p>
<pre class="prettyprint">
geofence_manager_stop(manager, geofence_id);
</pre></li>
</pre>
<p>If you destroy the handle, there is no need to call the <code>geofence_manager_stop()</code> function to stop the service as the service is automatically stopped. Also, you do not have to unset the previously set callbacks.</p></li></ol>
- <h2 id="status" name="status">Getting the Geofence Event State</h2>
+<h2 id="status">Monitoring Geofence State Changes</h2>
-<p>To get the state of all geofence events, use the geofence event callback. The geofence event callback is invoked whenever there is a request from the user, for example, to add a geofence or to start a geofence service.</p>
+<p>To track the state of the geofence, use the geofence event callback. The geofence event callback is invoked whenever there is a request from the user, such as to add a geofence or to start a geofence service.</p>
<ol>
<li><p>Register the callback using the <code>geofence_manager_set_geofence_event_cb()</code> function:</p>
<div class="note">
<strong>Note</strong>
- This event callback is used to let the user know whether the request is successful on the server side. This event callback is invoked only in the case of an asynchronous API. For a synchronous API, an error is immediately returned.
+ The geofence change event callback is used to let the user know whether the request is successful on the server side. This event callback is invoked only in the case of an asynchronous API. For a synchronous API, an error is immediately returned.
</div>
</li></ol>
- <h2 id="track" name="track">Tracking the User for Geofence Alerts</h2>
+<h2 id="track">Tracking the User for Geofence Crossing Alerts</h2>
-<p>To get information about the in or out state for the geofence:</p>
-<ol>
-<li>Receive event-based notifications:
-<ol type="a"><li><p> You can get notifications about the in or out state updates using the state update callback. The callback is invoked on an event, receiving the current state of the user with respect to geofences with each call.</p>
+<p>To get information about whether the user has crossed the boundary of the geofence:</p>
+<ul>
+<li>Receive event-based notifications with a callback:
+<ol><li><p>You can be notified when the user crosses a particular fence. The callback receives the current state of the user (whether the user is in or out of the virtual boundaries of a geofence) with each call.</p>
<p>Register the geofence state update callback using the <code>geofence_manager_set_geofence_state_changed_cb()</code> function.</p>
<pre class="prettyprint">
geofence_manager_set_geofence_state_changed_cb(manager, geofence_state_changed, NULL);
</pre></li></ol>
</li>
<li><p>Receive the current state on request.</p>
- <p>You can get the current state of the user with respect to a fence, such as the in or out state and the duration of the current state.</p>
-<ol
type="a"><li><p>To access the state or the duration, first create a status handle:</p>
+ <p>You can get the current state of the user with respect to a geofence, such as their in or out state and the duration of the current state.</p>
+<ol><li><p>To access the state or the duration, first create a status handle:</p>
<pre class="prettyprint">
int geofence_id = 1;
geofence_status_h status_h;
geofence_status_destroy(status_h);
</pre>
</li></ol></li>
-</ol>
+</ul>
<h2 id="proximity" name="proximity">Tracking the User for Proximity Alerts</h2>
-<p>To get information about the proximity state:</p>
+<p>To get information about the user's proximity to a geofence:</p>
<ol>
-<li><p>You can get notifications about the proximity state updates using the state update callback. The callback is invoked on an event, receiving the current state of the user with respect to proximity with each call.</p>
+<li><p>You can get notifications about the proximity state updates using the state update callback. The callback receives the current state of the user with respect to proximity with each call.</p>
<p>Register the proximity state update callback using the <code>geofence_manager_set_geofence_proximity_state_changed_cb()</code> function.</p>
<pre class="prettyprint">
geofence_manager_set_geofence_proximity_state_changed_cb(manager, proximity_state_changed, NULL);
<h2 id="info" name="info">Retrieving Geofence Information</h2>
-<p>To get information about the geofence:</p>
+<p>To get information about a geofence:</p>
<ul><li><p>Get common information (such as the type and place) about the geofences:</p>
<pre class="prettyprint">
geofence_type_e type;
geofence_get_type(fence_h, &type);
geofence_get_place_id(fence_h, &place_id);
</pre></li>
-<li><p>Retrieve the geopoint geofence information:</p>
+<li><p>Get information specific to a geopoint geofence:</p>
<pre class="prettyprint">
double latitude;
double longitude;
/* Release the resource after use */
free(address);
</pre></li>
-<li>Retrieve the Wi-Fi or Bluetooth geofence information:
+<li>Get information specific to a Wi-Fi or Bluetooth geofence:
<pre class="prettyprint">
char *bssid;
char *ssid;
<div id="container"><div id="contents"><div class="content">\r
<h1>Messages</h1>\r
\r
- <p>Tizen provides you with access to the device messaging capabilities, including sending SMS and MMS messages.</p>\r
+<p>You can access the device messaging capabilities, including sending SMS and MMS messages.</p>\r
\r
<p>The main messaging features include:</p>\r
<ul><li>Text messaging (SMS)\r
<li>Messaging notifications\r
<p>You can register and deregister callback functions to be notified when an outgoing message is successfully sent or an incoming message has been received.</p></li></ul>\r
\r
-<p>The sent status of SMS and MMS can be checked asynchronously. You receive a separate status report for each SMS recipient, and one status report regardless of the number of MMS recipients.</p>\r
+<p>The sent status of the SMS and MMS messages can be checked asynchronously. You receive a separate status report for each SMS recipient, and one status report for each MMS message regardless of the number of recipients.</p>\r
\r
<h2 id="prerequisites">Prerequisites</h2>\r
\r
-<p>To enable your application to use the messages functionality:</p>\r
+<p>To enable your application to use the messaging functionality:</p>\r
<ol>\r
<li>\r
<p>To use the Messages API (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__MESSAGING__MESSAGES__MODULE.html">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__MESSAGING__MESSAGES__MODULE.html">wearable</a> applications), the application has to request permission by adding the following privileges to the <code>tizen-manifest.xml</code> file:</p>\r
\r
<h2 id="sending" name="sending">Sending SMS or MMS Messages</h2>\r
\r
-<p>The Messaging API supports SMS (Short Message Service) messages and MMS (Multimedia Message Service) messages with attachments (image or video files).</p>\r
+<p>You can send SMS (Short Message Service) messages and MMS (Multimedia Message Service) messages with attachments (image or video files).</p>\r
<p>To send a message:</p>\r
<ol><li>Create a message.\r
<p>To create an SMS or an MMS message, use the <code>messages_create_message()</code> function. Specify the message type (<code>MESSAGES_TYPE_SMS</code> or <code>MESSAGES_TYPE_MMS</code>) when creating the message. The following example creates an SMS message.</p>\r
<div id="container"><div id="contents"><div class="content">
<h1>Push</h1>
-<p>You can to push events from an application server to your application on a Tizen device.</p>
+<p>You can push events from an application server to your application on a Tizen device.</p>
<p>The Push API is optional for the Tizen wearable profile, which means that it may not be supported on all wearable devices.</p>
<p>The FIDO (Fast IDentity Online) Alliance is a organization formed to address the lack of interoperability among strong authentication devices as well as the problems users face with creating and remembering multiple usernames and passwords.</p>
- <p>FIDO covers both password-less authentications (through <a href="#fido_uaf_components">FIDO UAF components</a>), such as fingerprint, iris, and voice, and multi-factor authentication, such as OTP and USB dongle. Tizen currently does not support multi-factor authentication.</p>
+ <p>FIDO covers both password-less authentications (through <a href="#fido_uaf_components">FIDO UAF components</a>), such as fingerprint, iris, voice, and multi-factor authentication, such as OTP and USB dongle. Tizen currently does not support multi-factor authentication.</p>
<p>FIDO Alliance provides certification for FIDO-compliant products through FIDO Ready™.</p>
<h2 id="fido_uaf_components" name="fido_uaf_components">FIDO UAF Components</h2>
<p>The FIDO UAF authenticator is a secure entity, connected to or housed within the FIDO user devices, that can create key material associated with a relying party. The key can then be used to participate in FIDO UAF strong authentication protocols.</p>
</li>
<li><p><strong>FIDO UAF authenticator metadata validation</strong></p>
- <p>In the FIDO UAF context, attestation is how authenticators make claims to a relying party during registration that the keys they generate, and certain measurements they report, originate from genuine devices with certified characteristics. An attestation signature, carried in a FIDO UAF registration protocol message, is validated by the FIDO UAF server.</p>
+ <p>In the FIDO UAF context, attestation is how authenticators make claims to a relying party during registration. They claim that the keys they generate, and certain measurements they report, originate from genuine devices with certified characteristics. An attestation signature, carried in a FIDO UAF registration protocol message, is validated by the FIDO UAF server.</p>
</li></ul>
<h2 id="prerequisites">Prerequisites</h2>
<p>To use the FIDO Client API (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__FIDO__MODULE.html">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__FIDO__MODULE.html">wearable</a> applications), the application has to request permission by adding the following privilege to the <code>tizen-manifest.xml</code> file:</p>
<p>The main features of the Voice control API include:</p>
<ul>
<li>Managing commands
- <p>You can use the Voice control service to register commands as foreground or background type. When the user speaks a registered command, the callback function returns the recognition result.</p></li>
+ <p>You can use the Voice control service to register commands as foreground or background type. When the user speaks a registered command, the callback returns the recognition result.</p></li>
<li>Retrieving information
<p>You can <a href="#info">get various information</a> from the voice control:</p>
<ul><li>Voice control state
<p>The user controls the state by starting and stopping command recognition.</p></li>
<li>Current language
<p>A command is valid only when the command language is the same as the current language. The current language can be changed by changing the application or display language on the device.</p>
-<p>You can get a notification of the language change in a callback. If the display language is changed to a non-supported one, the voice control language changed to English.</p></li>
+<p>You can get a notification of the language change in a callback. If the display language is changed to a non-supported one, the voice control language changes to English.</p></li>
<li>Supported language
<p>You can retrieve a list of supported languages to check whether the language that you want is supported.</p></li></ul>
</li>
</ul>
<p>To use the voice control:</p>
-<ol><li>Set up the voice control and <a href="#callback">register callback functions</a>.
+<ol><li>Set up the voice control and <a href="#callback">register callbacks</a>.
<p>The initialization allows the voice control to distinguish your application from any other applications also using voice control. The registered callbacks allow you to receive notifications about changes in the service state, language, and recognition result, and about any errors.</p></li>
<li>Prepare the voice control.
<p>The preparation connects the Voice control service for background work, such as recording and recognizing the user voice.</p>
<li>Set commands.
<p>You can <a href="#commands">create a command list</a>, and add or remove individual commands in the list. When creating an individual command, set the command text and type for each command handle. When all commands are created and added to the command list, set the command list to the voice control for recognition.</p></li>
<li>Get the recognition result.
-<p>The recognition result is sent through a registered callback function.</p>
+<p>The recognition result is sent through a registered callback.</p>
<p>If the registered command is duplicated or the user speaks multiple commands, the recognition result can contain multiple results. If you set duplicated commands, the Voice control service can reject the command. The rejection is shown in the result event.</p></li>
<li>When no longer needed, unprepare and deinitialize the voice control.
<p>You must disconnect the voice control service and deinitialize the voice control using the <code>vc_unprepare()</code> and <code>vc_deinitialize()</code> functions.</p></li></ol>
<div class="note">
<strong>Note</strong>
- The detailed implementation of the preloaded voice application (how to trigger and recognize the user speaking) can vary according to the device (mobile, wearable, or TV).
+ The detailed implementation of the preloaded voice application (how to trigger and recognize the user speaking) can vary depending on the device (mobile, wearable, or TV).
</div>
<div class="note">
<strong>Note</strong>
- If the recognition result produces a reject event, the Voice control service has rejected the recognized command. Make sure that the command does not conflict with other commands and there are not duplicated commands.
+ If the recognition result produces a reject event, the Voice control service has rejected the recognized command. Make sure that the command does not conflict with other commands and there are no duplicated commands.
</div>
-<p>To get the command, use the Voice control APIs with the <code>vc_cmd_list</code> parameter, which is a list of recognized commands. The <code>result</code> parameter contains the recognized text.</p>
+<p>To get the command, use the Voice control APIs with the <code>vc_cmd_list</code> parameter, which represents a list of recognized commands. The <code>result</code> parameter contains the recognized text.</p>
<pre class="prettyprint">
/* Callback */
<ol>
<li>Create a command list with a command list handle.
-<p>The command list can include many commands, which have a command text and type. The list can have both the <code>VC_COMMAND_TYPE_FOREGROUND</code> and <code>VC_COMMAND_TYPE_BACKGROUND</code> type commands. The foreground commands are valid when the application is in a visible state and the background commands are valid when the application is in a visible or invisible state.</p>
+<p>The command list can include many commands, which each have a command text and type. The list can have both the <code>VC_COMMAND_TYPE_FOREGROUND</code> and <code>VC_COMMAND_TYPE_BACKGROUND</code> type commands. The foreground commands are valid when the application is in a visible state and the background commands are valid when the application is in a visible or invisible state.</p>
<p>You can access the command list after you set it to the voice control and when you get the recognition result. </p>
<pre class="prettyprint">
projects / sdk / online-doc.git / commitdiff