java.lang.Object | |
↳ | android.provider.Telephony |
The Telephony provider contains data related to phone operation, specifically SMS and MMS messages and access to the APN list, including the MMSC to use.
Note: 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 <uses-feature>
element in your manifest that declares the "android.hardware.telephony"
hardware
feature. Alternatively, you can check for telephony availability at runtime using either
hasSystemFeature(PackageManager.FEATURE_TELEPHONY)
or getPhoneType()
.
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 Telephony
class) and only the default SMS
app receives the SMS_DELIVER_ACTION
broadcast
when the user receives an SMS or the WAP_PUSH_DELIVER_ACTION
broadcast when the user
receives an MMS.
Any app that wants to behave as the user's default SMS app must handle the following intents:
SMS_DELIVER_ACTION
("android.provider.Telephony.SMS_DELIVER"
). The broadcast receiver must also
require the BROADCAST_SMS
permission.
This allows your app to directly receive incoming SMS messages.
WAP_PUSH_DELIVER_ACTION
} ("android.provider.Telephony.WAP_PUSH_DELIVER"
)
with the MIME type "application/vnd.wap.mms-message"
.
The broadcast receiver must also require the BROADCAST_WAP_PUSH
permission.
This allows your app to directly receive incoming MMS messages.
ACTION_SENDTO
("android.intent.action.SENDTO"
) with schemas, sms:
, smsto:
, mms:
, and
mmsto:
.
This allows your app to receive intents from other apps that want to deliver a message.
ACTION_RESPOND_VIA_MESSAGE
("android.intent.action.RESPOND_VIA_MESSAGE"
) with schemas,
sms:
, smsto:
, mms:
, and mmsto:
.
This service must also require the SEND_RESPOND_VIA_MESSAGE
permission.
This allows users to respond to incoming phone calls with an immediate text message using your app.
Other apps that are not selected as the default SMS app can only read the SMS
Provider, but may also be notified when a new SMS arrives by listening for the 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.
For more information about building SMS apps, read the blog post, Getting Your SMS Apps Ready for KitKat.
Nested Classes | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Telephony.BaseMmsColumns | Base columns for tables that contain MMSs. | ||||||||||
Telephony.CanonicalAddressesColumns | Columns for the "canonical_addresses" table used by MMS and SMS. | ||||||||||
Telephony.Carriers | Carriers class contains information about APNs, including MMSC information. | ||||||||||
Telephony.Mms | Contains all MMS messages. | ||||||||||
Telephony.MmsSms | Contains all MMS and SMS messages. | ||||||||||
Telephony.Sms | Contains all text-based SMS messages. | ||||||||||
Telephony.TextBasedSmsColumns | Base columns for tables that contain text-based SMSs. | ||||||||||
Telephony.Threads | Helper functions for the "threads" table used by MMS and SMS. | ||||||||||
Telephony.ThreadsColumns | Columns for the "threads" table used by MMS and SMS. |
[Expand]
Inherited Methods | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
From class
java.lang.Object
|