Android 17 Beta 3 Hearing Aid Features: New Toggles Stop Unwanted Alerts

Google has added two new controls to Android 17 Beta 3 that stop notification chimes, ringtones, and alarms from routing directly into hearing aids and cochlear implants. It's a targeted fix for a problem that ranges from mildly irritating to genuinely painful, depending on the user. Android Authority reported the addition three days ago, on March 27.

The timing matters. Android 17 entered platform stability with Beta 3, meaning features in this build are expected to carry through to the final release. What looked uncertain in Android Canary ten days earlier is now on a clear path to ship broadly.

These toggles aren't a one-off addition, either. They follow a string of hearing-device improvements across recent Android versions, from call mic switching in Android 16 to Auracast public-audio support, suggesting Google is treating hearing-device integration as sustained platform work rather than a periodic accessibility checkbox.

Android hearing aids notification alerts: what the new toggles actually do

The Accessibility > Hearing devices settings page in Android 17 Beta 3 now includes two separate toggles. One prevents notification chimes from playing through connected hearing aids. The second stops ringtones and alarms from routing there when a device is connected, per Android Authority.

The feature covers ASHA-compatible hearing aids, cochlear implants, and other medically prescribed hearing devices recognized by the Android system, not just mainstream consumer aids, per Android Authority. Compatibility requires that the device be identified by Android as a hearing device, whether via ASHA or another supported protocol.

Google hasn't confirmed exactly where blocked audio goes in Beta 3. Canary testing from March 20 suggested two possible behaviors: notification sounds shifted to the phone's speaker, while ringtones and alarms could, in some configurations, be blocked from both the phone speaker and the hearing device entirely, per Android Authority's Canary coverage. Whether the Beta 3 implementation follows the same logic isn't confirmed in current reporting.

Where to find it now:

• Open Settings > Accessibility > Hearing devices on a Pixel enrolled in the Android beta program
• Two separate toggles appear: one for notification sounds, one for ringtones and alarms
• If your aids or implants are recognized as hearing devices by Android, the new behavior applies once toggled, per FindArticles

Broader availability depends on Android 17 rollout timing and individual OEM support.

What changes in daily use

The practical shift is straightforward. With the notification toggle on, a Slack ping or email chime no longer fires directly into the ear canal during a work meeting. The alarm toggle means a 6am wake-up doesn't blast at amplified volume inside someone's aids while they're still half-asleep. For users who previously had to disconnect their hearing devices at night or during focused work just to avoid those interruptions, that's a real reduction in daily friction.

The tradeoff is worth understanding. Based on Canary behavior, notifications likely reroute to the phone's speaker when blocked from hearing aids. Ringtones and alarms may be suppressed more broadly, potentially from both the speaker and the device. Users who rely on in-ear alerts as their primary notification method should test the configuration carefully before assuming ambient sound alone will catch everything, per Android Authority.

The controls are also granular by design. Each toggle works independently, so a user can keep alarms routed into their aids for reliability while blocking notification chimes, or vice versa.

Why this matters: discomfort, disruption, and a large affected population

The core problem is physical. Sudden tones delivered directly into the ear canal and amplified by a hearing device can be uncomfortable or painful, a qualitatively different experience from a notification sound heard across a room, per FindArticles. Beyond the startle factor, abrupt audio bursts carry potential for discomfort, tinnitus, and further ear damage in users with already impaired hearing, Android Authority reported. Those claims appear in tech coverage rather than clinical literature and should be taken as plausible context rather than established medical fact.

Google's own framing is more measured: the company describes the feature as designed to reduce "unwanted interruptions" played directly inside the ear, per Android Authority. That's enough. An unexpected alarm blasting at high volume into someone's ear is a concrete daily problem, no additional framing required.

On scale: the World Health Organization estimates more than 1.5 billion people globally live with some degree of hearing loss, per FindArticles. That figure covers hearing difficulty broadly. The new Android controls apply specifically to the subset actively using hearing aids, cochlear implants, or similar devices recognized by the Android system, a narrower group, but one for whom the friction is immediate and recurring.

How this fits Android's hearing-accessibility arc

To understand where the Android 17 Beta 3 hearing aid enhancements sit, it helps to look at what the preceding versions addressed.

Android 16 focused on audio management during calls and in the surrounding environment. It added ambient volume controls letting LE Audio hearing aid users adjust how much external sound their aids pick up, and introduced the ability to switch between a hearing aid's built-in microphone and the phone's mic during voice calls. Google noted mic switching is useful in noisy environments and can also extend hearing aid battery life when the aids' own mics are running low, per Android Authority from January 2025.

Auracast addressed a different layer entirely. Google announced Android support for the Bluetooth LE Audio broadcast standard on Pixel 9 and Samsung Galaxy devices running One UI 7, per the Google Blog and The Verge in March 2025. The standard lets a single audio source broadcast to an unlimited number of connected devices, enabling hearing aid users to receive audio directly from theaters, airports, and similar public venues.

The progression has a coherent logic. Auracast addressed getting audio in. Mic switching and ambient controls addressed managing audio during calls and in the environment. Android 17's new toggles address keeping unwanted audio out. Each improvement targets a distinct layer of the hearing-device experience. Together they look less like a series of disconnected additions and more like deliberate work toward finer-grained audio control across the full day.

Bluetooth hearing aids Android 17: from Canary to Beta 3

A week made a significant difference here. When Android Authority spotted these toggles in Android Canary on March 20, the coverage explicitly cautioned they "may not necessarily make it to Android 17." Seven days later, Google moved them into Beta 3 alongside the platform stability milestone.

Platform stability is the point at which OEM partners can finalize their integration work and hearing-device manufacturers can begin validating compatibility with the new audio routing behavior, per FindArticles. Features that reach this stage are expected to carry through to the stable release, which is why the jump from Canary to Beta 3 in a single week carries more weight than it might initially suggest.

Who gets it first is straightforward: Pixel devices receiving early Android 17 updates are first in line. Broader availability follows as individual manufacturers ship their own Android 17 builds, with timing varying by OEM, per FindArticles. Which non-Pixel devices will support the feature at launch, and which specific hearing aids and implants will qualify beyond ASHA-compatible devices, isn't confirmed in current reporting.

What comes next

Two toggles in Android 17 Beta 3 give hearing aid and cochlear implant users direct control over whether alerts and ringtones reach their ears. Small settings change, concrete daily improvement, per Android Authority.

The feature is live now for Pixel owners in the Android beta program. With platform stability reached, it's on track for the stable Android 17 release. Final support for non-Pixel devices and specific hearing hardware depends on OEM and device-partner timelines, per FindArticles.

The open questions worth tracking as Android 17 approaches stable release: exactly where blocked audio goes in the final implementation, which hearing devices qualify beyond ASHA-compatible aids, and whether emergency alerts follow different routing rules. How consistently OEMs carry the feature across their Android 17 builds, and whether Android 18 extends control to additional audio categories, will determine whether this progression continues or stalls out.