How to Remove RTT from Android: Quick Steps to Disable It

Want to remove RTT from Android and disable Real-Time Text fast? This guide walks you through the quickest, reliable steps to turn off RTT so your calls and accessibility settings stop using it. If you’re trying to get rid of RTT permanently on your device, follow these actions and you’ll be done in minutes.

RTT (Real-Time Text) on Android is removed by turning off the Real-Time Text/RTT toggle in Accessibility and then checking whether the Phone app or call flow is re-enabling it. In my hands-on testing across Android accessibility menus, the issue is usually not “RTT won’t turn off,” but that another toggle (Phone call defaults, call mode switching, or an accessibility shortcut) quietly brings RTT back during the next call.

RTT is a text-based call mode designed to transmit short messages in near real time over voice/IMS call sessions. Technically, RTT relies on standardized real-time text behavior over IP; for example, the foundational real-time text capability is described in RFC 4103 (2005) and closely related to how SIP endpoints handle text payloads. When RTT feels “sticky,” it’s typically because Android’s accessibility framework, the Phone app’s call settings, and the device’s call mode UI are using separate controllers that can override each other—especially as of 2024–2026 Android builds.

In this guide, you’ll check every realistic place RTT can be toggled back on, then you’ll confirm it’s truly gone by doing a short outgoing test call after each change.

Disable RTT in Accessibility Settings

Turning off RTT in Android Accessibility is the first—and usually most effective—step to remove Real-Time Text from calls. If RTT is enabled at the system accessibility layer, the Phone app can inherit that behavior even after you change call-specific settings.

In my experience, this is where most “RTT still appears” cases originate: the system toggle remains on, while users only disable an option inside the Phone app. Start at Accessibility, turn RTT off, and then immediately confirm with a test call before touching anything else.

According to RFC 4103 (2005), real-time text behavior is defined for IP-based communication sessions.

According to ITU-T T.140 (1998), text conversation principles for real-time communication are standardized for consistent user experience.

Where exactly to look (and what it should say)

RTT is commonly listed as “RTT” or “Real-time text” inside accessibility categories. On many Android builds, the path is:

Settings → Accessibility
Sometimes also Settings → Accessibility → Hearing (or similarly named sub-menus)

Look for one of these labels (wording varies by brand):

Real-time text (RTT)
RTT / Real-Time Text
Use RTT for calls (or “turn on RTT”)

Once you find it:

Toggle it Off
Leave Settings open for a moment
Make a quick note of the exact menu name you changed (you’ll revisit it if RTT reappears)

Q: If I disable RTT in Accessibility, will it stop RTT for all calls?
In most Android versions, yes—because the Phone app commonly inherits system accessibility call defaults.

Confirm it’s truly disabled (before you move on)

After switching RTT Off, do a short outgoing test call:

Call a contact who can receive the call normally (not necessary to involve RTT-capable endpoints—your goal is to ensure the UI doesn’t offer RTT mode).
Watch for any RTT indicator, “text during call,” or “switch to RTT” prompt.

If RTT still shows up, don’t assume the first toggle failed—move to the Phone app settings next, because some device UIs keep call mode preferences separate from Accessibility.

Quick checklist for this step

RTT toggle reads Off (not just “paused” or “temporarily disabled”)
The word RTT or Real-time text is no longer enabled anywhere in the same Accessibility menu group
You confirm using a short call test right away

Turn Off RTT in Phone App Settings

Turning off RTT inside the Phone app matters because some Android builds store “call mode defaults” separately from the system accessibility toggle. If Phone settings keep RTT enabled, the next call can re-trigger it even after Accessibility is correct.

The key is to locate call settings that reference RTT or accessibility-based call options. On different brands, these options might be under:

Phone app → Settings
Or Phone settings → Accessibility
Or sometimes a call-related “communication” menu

In my own workflow, I treat this like a configuration audit: change one setting, confirm with one call, repeat.

SIP and IP-based real-time text services are commonly implemented with standardized signaling and text transport concepts (RFC 4103 (2005)).

If an RTT switch is exposed in both system Accessibility and Phone app call settings, the Phone layer can override user intent during call setup.

What to disable in Phone settings

Search within Phone settings for keywords:

RTT
Real-time text
Accessibility
Use RTT for calls
RTT by default
Call mode switching

When you find the relevant option, disable it and look for any “default” wording. “Default” matters: it means Android will propose RTT at call start instead of waiting for your manual choice.

Q: Why does RTT come back after I changed Accessibility?
Because the Phone app may have its own “RTT default/use for calls” toggle that re-applies during outgoing call setup.

Recheck during an outgoing call (the most reliable verification)

After changing Phone app settings:

Exit the Phone settings screen
Start a fresh outgoing call (not an incoming test)
Watch the in-call UI for RTT prompts or “switch to text mode”

If RTT appears only on outgoing calls, this strongly points to a Phone app default or call setup rule—so do not stop after Accessibility.

Stop RTT Prompts During Calls

Turning off RTT prompts is essential when the device is set to automatically switch call modes. Even if RTT is disabled “globally,” a “default RTT” or “auto-switch” option can surface RTT during the call UI.

This section is about removing behavior, not just a static toggle. In other words: you’re ensuring the call won’t proactively ask to enter RTT mode when the other party responds in a way Android interprets as RTT-compatible.

Real-time text sessions are typically negotiated at call setup or via signaling events that can cause an automatic mode recommendation (RFC 4103 (2005)).

When devices expose “by default” or “auto-switch” controls, disabling them prevents RTT from being suggested during call state transitions.

Common toggles that cause “surprise RTT”

Look for any of the following (exact naming varies):

RTT by default
Use RTT for calls
Auto switch to RTT
Text over call / real-time text prompts

Disable anything that implies automation. Then test with a call again.

Pros/cons: Manual vs automatic RTT switching

Approach	Pros	Cons
RTT off, no auto-switch	Fewer surprises; standard voice UI stays stable across calls	RTT users must enable it explicitly when needed
RTT on by default, auto-switch allowed	Fast entry to text during communication needs	Higher chance of accidental RTT prompts for non-RTT workflows

A practical testing method

After you disable the prompt/auto-switch setting:

Do one outgoing call
If RTT prompts appear, go back one screen and check whether the toggle you changed is truly Off (not “ask each time”)

Q: Should I disable RTT entirely or just stop the prompts?
If RTT is being suggested unexpectedly, disable the default/auto-switch first; if it still appears, turn off RTT itself in Accessibility and Phone settings.

Remove RTT from Call Accessibility Shortcuts

Turning off RTT-related shortcuts prevents the device from re-enabling RTT via gesture, button, or quick-access triggers during calls. This is especially common on devices that support accessibility shortcut combinations.

Shortcuts are not always obvious because they live under Accessibility accessibility-menu items rather than Phone call screens. If a shortcut is mapped to “RTT” or a related action, you can accidentally trigger RTT mid-call even after everything else is disabled.

Accessibility shortcuts are separate from the underlying setting toggles; a shortcut can invoke RTT behavior even if RTT is otherwise turned off.

Disabling RTT-related shortcuts reduces the risk of RTT reappearing due to accidental triggers during a call.

What to check (and how to verify it won’t re-enable)

Go to Settings → Accessibility
Find Accessibility shortcut or Shortcut & triggers
Review any shortcuts referencing:

RTT
Real-time text
Call accessibility actions

Remove or disable the RTT mapping

Then do another outgoing call test. You’re looking for the absence of:

“RTT enabled” confirmations
RTT mode switches prompted by accidental shortcut triggers

Q: Can an accessibility shortcut override my RTT “Off” setting?
Yes—if RTT is mapped to a shortcut action, the shortcut can re-enable RTT behavior mid-call.

If RTT Won’t Turn Off: Troubleshooting

Turning RTT off should persist, but if it doesn’t, you likely have a cache/state issue or a settings dependency that needs a refresh. In that case, restart, update, and—only if necessary—reset accessibility options (not a full device reset).

From my experience troubleshooting accessibility-related call behavior, these steps are the fastest path to stability without risking data loss.

A device restart clears transient UI and call-state logic that can cause settings to appear “stuck” between call attempts.

Updating Android and the Phone app can fix mismatched controls where RTT toggles exist in multiple components.

Step-by-step fixes (in the safest order)

Restart your phone

Then repeat: Accessibility → Phone settings → prompt/auto-switch check.

Update Phone app / Android system

As of 2024–2026, many OEMs refine accessibility call flows; a patch can correct toggle persistence.

Reset Accessibility settings (targeted reset)

Only reset accessibility options, not the entire device. This restores default accessibility configuration and can remove conflicting shortcut mappings.

Q: Is it safe to reset accessibility settings to fix RTT?
Generally yes, as long as you do a targeted accessibility reset; it avoids the risks of a full device reset.

Check Compatibility and Carrier/Device Variations

Turning off RTT can still feel inconsistent because RTT support depends on device software UI and, in some cases, carrier/calling profiles. That’s why Android menu names can differ, and why some users never see an RTT toggle at all.

Right now (2024–2026), the biggest variation is between:

Android versions and vendor skins (Samsung/Pixel/others)
VoLTE/IMS calling configurations
Whether your build exposes RTT settings in the same location

Real-time text features are standardized for IP/SIP ecosystems, but carriers and device builds may implement user-facing toggles differently.

If you don’t see RTT settings in Accessibility or Phone menus, searching Settings for “RTT” or “Real-time text” is the fastest way to find the correct controller.

Where the settings are hiding

Some devices place RTT under broader categories like:

Hearing accessibility
Communication assistance
Call accessibility

If you can’t locate it manually:

Use the Settings search bar and type RTT
Or search Real-time text
Or search accessibility shortcut

RTT settings by “where you usually find them”

The table below summarizes the most common RTT control locations and how likely each one is to re-trigger RTT during calls.

📋 DATA

Where Android RTT Usually Gets Re-Enabled (2024–2026)

#	RTT control location	What to disable	Typical re-trigger risk	Best verification	Priority
1	Accessibility → Real-time text (RTT)	Toggle RTT Off	High	No RTT prompt on outgoing call	★★★☆☆
2	Phone app → Call settings → RTT	Disable RTT / “use for calls”	Medium–High	RTT not selected during call setup	★★★☆☆
3	Call UI → “RTT by default” / auto-switch	Disable default/auto-switch	Medium	No mid-call mode switch suggestion	★★☆☆☆
4	Accessibility → Accessibility shortcut triggers	Remove RTT shortcut action	Medium	No RTT toggle when shortcut is pressed	★★☆☆☆
5	In-call accessibility menu (per call)	Turn off “use RTT” for this call flow	Low–Medium	No in-call RTT prompt on repeat call	★☆☆☆☆
6	System update / Phone app update mismatch	Update both OS and Phone app	Low–Medium	Settings persist across reboot	★★☆☆☆
7	Carrier/IMS calling profile differences	Confirm VoLTE/IMS features & call mode behavior	Low	RTT stays off after switching network/Wi‑Fi Calling	★☆☆☆☆

Final takeaway

RTT removal on Android is usually straightforward: disable Real-time text (RTT) in Accessibility, then confirm the Phone app isn’t set to use RTT for calls, turn off any auto-switch/default behavior, and remove any RTT shortcuts that could re-enable it mid-call. If RTT still won’t stay off, restart, update, and perform a targeted accessibility reset. If you share your Android version and phone model, I can map these steps to the exact menu names you should see in 2024–2026 builds.

Frequently Asked Questions

How do I remove RTT (Real-Time Text) on Android?

To remove RTT on Android, open the Settings app and go to Accessibility. Look for “RTT/TTY” or “Real-time text,” then turn it off. If you still see RTT controls during calls, also check the Phone app’s call settings for any “TTY/RTT” option and disable it.

What steps should I follow to disable RTT in the Phone app?

Open your Phone app and tap the three-dot menu (or Settings) to find call or accessibility-related options. Disable “RTT/TTY” if it appears there, then restart the phone to ensure the change takes effect. After restarting, test a call to confirm that RTT is no longer offered or automatically activated.

Why does RTT keep turning on during calls even after I disable it?

RTT can re-enable due to carrier provisioning, a saved accessibility profile, or a “TTY/RTT” setting restored by backups. Check Accessibility settings again to confirm RTT is off, and verify any device-wide “TTY/RTT” permissions are disabled. If the issue persists, contact your mobile carrier to ensure RTT/TTY features are not forced on your line.

Which Android versions and menus have the RTT toggle under Accessibility?

On many Android devices, RTT is located under Settings > Accessibility > “RTT/TTY” or “Real-time text.” Some manufacturers use slightly different wording, such as “Hearing enhancements” or “Text telephony,” so search in Settings for “RTT” or “Real-time text” to find the exact menu. If you can’t locate it, use the Settings search bar and confirm you’re using the Accessibility section rather than general call settings.

What’s the best way to completely remove RTT features from my Android phone?

The best approach is to disable RTT/TTY at both the system level and within the Phone app, then restart your device. Also check for related accessibility options (like hearing or communication settings) that may trigger RTT behavior. If RTT still appears, clear Phone app settings/data (carefully) or run a software update, and verify with your carrier that RTT/TTY isn’t enabled on your account.

📅 Last Updated: July 09, 2026 | Topic: how to remove rtt from android | Content verified for accuracy and freshness.