Three Methods to Pre-fill Phone Numbers in Android Dialer Using Intent Mechanism

Basic Implementation with Intent.ACTION_DIAL

In Android application development, there is often a need to open the system dialer and pre-fill a phone number without directly making a call. This can be achieved using Intent.ACTION_DIAL, an Intent action specifically designed to launch the dialer interface.

The core code example is as follows:

Intent intent = new Intent(Intent.ACTION_DIAL);
intent.setData(Uri.parse("tel:0123456789"));
startActivity(intent);

The key here is constructing the URI correctly: the "tel:" prefix must be used, followed by the phone number. Omitting the prefix will cause the system to throw a java.lang.IllegalStateException: Could not execute method of the activity exception. This is because Android's Intent resolution mechanism relies on the URI scheme to identify handlers.

The advantage of using ACTION_DIAL is that it requires no special permissions, as it only opens the dialer interface, with the actual call still initiated by the user. This aligns with Android's security design principles, preventing apps from abusing phone functionality.

Direct Calling with Intent.ACTION_CALL

If bypassing user confirmation to directly make a call is needed, Intent.ACTION_CALL can be used. However, this method requires the CALL_PHONE permission, which must be declared in AndroidManifest.xml:

<uses-permission android:name="android.permission.CALL_PHONE" />

The code implementation is similar to ACTION_DIAL:

Intent intent = new Intent(Intent.ACTION_CALL);
intent.setData(Uri.parse("tel:0123456789"));
startActivity(intent);

Note that starting from Android 6.0 (API level 23), CALL_PHONE is classified as a dangerous permission, requiring not only declaration in the manifest but also runtime user authorization. This adds complexity to direct calling, so unless necessary, ACTION_DIAL is recommended as the preferred approach.

Interactive Dialing via TextView's autoLink Property

Beyond programmatically launching Intents, phone number recognition and dialing can also be implemented through UI components. In layout XML, set the android:autoLink="phone" attribute for TextView:

<TextView
    android:id="@+id/phoneTextView"
    android:layout_width="wrap_content"
    android:layout_height="wrap_content"
    android:text="Contact: 0123456789"
    android:autoLink="phone"
    android:linksClickable="true" />

When users click the phone number in the text, the system automatically launches the dialer and fills in the number. This method requires no Intent code or permissions, making it suitable for static phone number display scenarios. Its principle relies on Android's Linkify mechanism, which automatically detects patterns in text and creates clickable links.

Technical Details and Best Practices

In practical development, handling phone number formats is crucial. Phone numbers in URIs should follow international standard formats, such as using "+" for country codes: "tel:+861234567890". This ensures correct parsing across devices in different regions.

For ACTION_DIAL, although no permission is needed, it's advisable to handle ActivityNotFoundException to account for devices without a dialer app:

try {
    startActivity(intent);
} catch (ActivityNotFoundException e) {
    // Handle absence of dialer app
    Toast.makeText(this, "No dialer app found", Toast.LENGTH_SHORT).show();
}

On Android 10 and above, due to enhanced permission restrictions, using ACTION_CALL directly may face more limitations. Developers should adjust implementation strategies based on target API levels.

Overall, the choice of method depends on specific requirements: ACTION_DIAL is the simplest and safest for merely displaying the dialer interface; ACTION_CALL and its permission management are for full automation; and autoLink provides a code-free solution for UI presentation.