Android 17 adds platform-level auto-routing for over-the-top voice and video calls to premium 5G network slices, aiming to keep calls stable in crowded areas. The feature relies on Telecom Jetpack APIs to detect when a call starts and ends, removing the need f
By the time a stadium fills in, most mobile networks start feeling it—download speeds dip, latency climbs, and video buffers become a familiar annoyance. On Android 17, Google is trying to make sure the moment you need your call to stay smooth, the network doesn’t treat it like ordinary data.
The update adds automatic support for routing over-the-top (OTT) voice and video call traffic to premium 5G network connections using 5G network slicing. In practical terms. that’s meant to keep your VoIP conversations—think WhatsApp or Zoom video calls over mobile data—less prone to lag and jitter when the network is crowded.
The mechanism is also quietly important. Android 17 uses Telecom Jetpack APIs—already used by OTT apps—to detect when a voice or video call starts and ends. During the call. the operating system identifies the app by its UID and steers that app’s traffic to the dedicated premium 5G slice if it’s available. When the call ends. the routing rule is removed. and the app’s traffic returns to the system’s default network for non-calling data such as messaging.
What makes the change stand out is what it removes. Because Android 17 handles the routing at the platform level. the system is designed to eliminate the need for app developers to explicitly request and build their own network slicing capabilities. and to handle carrier upsell flows themselves. Instead of pushing developers to interrupt users with purchase prompts to unlock prioritization. the OS can route calls automatically as long as the app uses the Telecom Jetpack API.
Still, this depends on one missing piece: carriers. For the routing to work, carriers will need to provide the dedicated 5G network slice for voice and video call traffic. The feature may also come with a cost for users, since premium slices can be offered as upsells.
To understand why that matters, it helps to know what 5G network slicing is. Network slicing allows carriers to partition a single 5G network into multiple isolated virtual networks, each with different characteristics. Instead of treating all traffic the same. carriers can allocate different resources depending on the use case—like ultra-low latency or high bandwidth—on 5G Standalone (5G SA) networks. In the US. T-Mobile has created a Video calling slice to optimize mobile apps that provide OTT video calling or conferencing features. Verizon has an Enhanced Video Calling network slice. And T-Mobile, Verizon, and AT&T also have network slices for public safety use.
Google’s work on making this more accessible has been incremental. Android 12 introduced support for 5G network slicing, but it was restricted to data routed through enterprise work profiles. Android 13 added support for per-app routing controls for IT admins, though those slicing capabilities were still limited to enterprise users. Android 14 (QPR 1) added a 5G slicing upsell feature that lets carriers offer enhanced network capabilities—mainly prioritized latency—through 5G network slicing. That approach required apps to make specific changes to offer the carrier’s upsell if the user wasn’t subscribed to the slice. and then to use it.
That extra developer work came with a user experience tradeoff: expecting a third-party app developer to interrupt the user and present the carrier’s purchase flow isn’t ideal. Android 17’s auto-routing is positioned as the fix for that friction—at least on devices and networks where the required slices are available.
Google has recently rolled out Android 17 to Pixel devices. and for Pixel owners on a supported network with a compatible mobile plan that offers these premium network slices. the call-routing feature is expected to kick in seamlessly behind the scenes. In a highly congested area—like a concert ground or a stadium—standard data might still slow down. but a VoIP call can potentially remain stable and jitter-free because it’s isolated in its own premium fast lane.
There’s also a business angle hiding in the engineering. As calls get more reliably smooth, carriers may have a clearer reason to offer—and monetize—those slices, potentially making network slicing more popular and driving a feedback loop.
Once Android 17 rolls out to more devices, the question won’t be whether the OS can steer traffic. It will be whether carriers choose to supply the slices for voice and video call traffic widely enough—and whether users will need to pay for the “fast lane” when they’re most likely to need it.
Android 17 5G network slicing premium network slices OTT voice calls OTT video calls Telecom Jetpack APIs Pixel devices VoIP WhatsApp Zoom jitter latency
So basically my phone will pay extra without me asking? Cool cool.
I don’t even know what “premium 5G slices” means but if my Zoom buffers less I’m all for it. Still, carriers are gonna charge for the slice tho right?
Wait, it says it routes “OTT calls” automatically… does that mean it’ll prioritize my regular calls too or only WhatsApp/Zoom? Also “Telecom Jetpack APIs” sounds like some developer thing I’ll never get, so how does it work on my phone then?
This is one of those things where they say they removed the upsell prompts but like… the upsell still exists just in the background. Like if it detects the call and then “steers” the traffic, who decides I’m allowed on the slice? Because last time I checked my carrier barely even gives us good 5G in my area. Stadiums? Sure. My street? not so much.