Google will enable DSDS support with 5G in a future update for the Pixel 5 and Pixel 4a 5G

One of the more under-appreciated features of the Pixel 5 and Pixel 4a 5G is support for Dual SIM Dual Standby (DSDS). The feature allow users to use two SIMs (one physical and one eSIM) to make calls and texts through one carrier and use data-only on the other. Unfortunately, the devices are limited to 4G networks when both SIMs are enabled, but that is apparently about to change.

Google’s own support page explains that the Pixel 4a 5G and Pixel 5 only supports 4G networks on DSDS.

Important: Pixel 5 and Pixel 4a (5G) phones with two SIMs in use will fall back to 4G networks. To connect to 5G networks, temporarily turn off the SIM that isn’t set to use data.

However, a code change posted to the Android Open Source Project (AOSP) suggests Google is configuring both devices to support DSDS and 5G networks. AOSP is open source and allows contributions from all developers, but the change allegedly came from Google’s internal Android code, suggesting it’s the real deal.

The code change specifically refers to “Bramble,” which is the codename for the Pixel 4a 5G. However, there are also references to “Redbull,” which is the codename for the shared device tree for the Pixel 5 (codename “Redfin”) and Pixel 4a 5G. So, it’s likely both devices will support DSDS and 5G networks whenever the changes go into effect.

This commit was just merged, so we don’t know when exactly this will be enabled on the Pixel 5 and Pixel 4a 5G. But it could happen when Google rolls out a security update in December.

Pixel 4a 5G Forums || Pixel 5 Forums

DSDS capabilities have been supported by Google devices since the Pixel 3a. But supporting DSDS and 5G networks simultaneously would be new territory for the company.

Thanks to XDA Recognized Developer luca020400 for the tip!

The post Google will enable DSDS support with 5G in a future update for the Pixel 5 and Pixel 4a 5G appeared first on xda-developers.

from xda-developers https://ift.tt/38wHjPe
via IFTTT