/**@class android.provider.Telephony
@extends java.lang.Object
The Telephony provider contains data related to phone operation, specifically SMS and MMS
messages, access to the APN list, including the MMSC to use, and the service state.
<p class="note"><strong>Note:</strong> These APIs are not available on all Android-powered
devices. If your app depends on telephony features such as for managing SMS messages, include
a <a href="{@docRoot}guide/topics/manifest/uses-feature-element.html">{@code <uses-feature>}
</a> element in your manifest that declares the {@code "android.hardware.telephony"} hardware
feature. Alternatively, you can check for telephony availability at runtime using either
{@link android.content.pm.PackageManager#hasSystemFeature
hasSystemFeature(PackageManager.FEATURE_TELEPHONY)} or {@link android.telephony.TelephonyManager#getPhoneType}.</p>
<h3>Creating an SMS app</h3>
<p>Only the default SMS app (selected by the user in system settings) is able to write to the
SMS Provider (the tables defined within the {@code Telephony} class) and only the default SMS
app receives the {@link android.provider.Telephony.Sms.Intents#SMS_DELIVER_ACTION} broadcast
when the user receives an SMS or the {@link android.provider.Telephony.Sms.Intents#WAP_PUSH_DELIVER_ACTION} broadcast when the user
receives an MMS.</p>
<p>Any app that wants to behave as the user's default SMS app must handle the following intents:
<ul>
<li>In a broadcast receiver, include an intent filter for {@link android.provider.Telephony.Sms.Intents#SMS_DELIVER_ACTION}
(<code>"android.provider.Telephony.SMS_DELIVER"</code>). The broadcast receiver must also
require the {@link android.Manifest.permission#BROADCAST_SMS} permission.
<p>This allows your app to directly receive incoming SMS messages.</p></li>
<li>In a broadcast receiver, include an intent filter for {@link android.provider.Telephony.Sms.Intents#WAP_PUSH_DELIVER_ACTION}} ({@code "android.provider.Telephony.WAP_PUSH_DELIVER"})
with the MIME type <code>"application/vnd.wap.mms-message"</code>.
The broadcast receiver must also require the {@link android.Manifest.permission#BROADCAST_WAP_PUSH} permission.
<p>This allows your app to directly receive incoming MMS messages.</p></li>
<li>In your activity that delivers new messages, include an intent filter for
{@link android.content.Intent#ACTION_SENDTO} (<code>"android.intent.action.SENDTO"
</code>) with schemas, <code>sms:</code>, <code>smsto:</code>, <code>mms:</code>, and
<code>mmsto:</code>.
<p>This allows your app to receive intents from other apps that want to deliver a
message.</p></li>
<li>In a service, include an intent filter for {@link android.telephony.TelephonyManager#ACTION_RESPOND_VIA_MESSAGE}
(<code>"android.intent.action.RESPOND_VIA_MESSAGE"</code>) with schemas,
<code>sms:</code>, <code>smsto:</code>, <code>mms:</code>, and <code>mmsto:</code>.
This service must also require the {@link android.Manifest.permission#SEND_RESPOND_VIA_MESSAGE} permission.
<p>This allows users to respond to incoming phone calls with an immediate text message
using your app.</p></li>
</ul>
<p>Other apps that are not selected as the default SMS app can only <em>read</em> the SMS
Provider, but may also be notified when a new SMS arrives by listening for the {@link android.provider.Telephony.Sms.Intents#SMS_RECEIVED_ACTION}
broadcast, which is a non-abortable broadcast that may be delivered to multiple apps. This
broadcast is intended for apps that—while not selected as the default SMS app—need to
read special incoming messages such as to perform phone number verification.</p>
<p>For more information about building SMS apps, read the blog post, <a
href="http://android-developers.blogspot.com/2013/10/getting-your-sms-apps-ready-for-kitkat.html"
>Getting Your SMS Apps Ready for KitKat</a>.</p>
*/
var Telephony = {
};