Update: Android 13 Beta 2 includes Vo5G for T-Mobile, Metro, and Assurance.
The file you want to edit will look similar to this:
Your carrier will likely have a different xml file name. Vo5G should also work for Metro and T-Mobile MVNOs like Mint. Not sure if any other carriers support it. When in doubt,
Root file explorers and editors might not see this file but give it a try. Probably easier to just do this on the device.
You can also do this from command line or do a weird sequence of copies, pulls, edits, pushes with adb and your favorite text editor. You need root.
Example:
Add or edit these items before the </bundle> at the end. You can combine.
For Vo5G:
For VoLTE (experimental):
For VoWiFi (experimental):
For VT carrier video calling (experimental, seems to set the toggle with my AT&T sim):
Reboot. Enjoy.
Experimental means experimental. Try at your own risk. Additional flags to properly config your carrier or use when roaming are likely needed.
To test Vo5G, the best way is to set NR-only in *#*#4636#*#* and then try to dial your voicemail. I have not tested ViNR/Vi5G (Video over 5G). Your phone will typically only use Vo5G as a last resort otherwise. Be sure to set back to NR/LTE/GSM/WCDMA when done.
And no, I don't know how to enable 5G for your phone in an unsupported country/carrier. I have a few leads on where the xml files may control 5G but again, untested. Or it's deep in the modem package's config files and not something I want to mess with. I'm just laying out my research. Your carrier may block or whitelist these features by IMEI or plan. At least that's the case for my AT&T sim.
Background:
This phone launched without Vo5G support. Or did it? When Android 13 DP1 came out, this was left enabled, among other goodies in the carrier settings and modem. When subsequent builds came out, Vo5G was gone regardless of modem or carrier config pb file overrides. Turns out I was looking in the wrong place. Credit to @foobar66 for laying a great foundation in the original VoLTE thread and ideas on how these kinds of edits can be Magisk modules. For the VoLTE item, when I set to false in the xml, I could no longer place calls in 4G or 5G modes on T-Mobile. It didn't shift down to HSPA+ though as a fallback. And yes, I know that T-Mobile is actually using an VoLTE/EPS core for Vo5G, but it's still Vo5G as far as the phone cares.
The file you want to edit will look similar to this:
/data/user_de/0/com.android.phone/files/carrierconfig-com.google.android.carrier-8901260570715066153-1.xml
Your carrier will likely have a different xml file name. Vo5G should also work for Metro and T-Mobile MVNOs like Mint. Not sure if any other carriers support it. When in doubt,
ls
the folder. If you are dual-sim, pick the right one.Root file explorers and editors might not see this file but give it a try. Probably easier to just do this on the device.
You can also do this from command line or do a weird sequence of copies, pulls, edits, pushes with adb and your favorite text editor. You need root.
Example:
adb shell
su
cp /data/user_de/0/com.android.phone/files/carrierconfig-com.google.android.carrier-8901260570715066153-1.xml /sdcard/
exit
exit
adb pull /sdcard/carrierconfig-com.google.android.carrier-8901260570715066153-1.xml
*edit file*
adb push carrierconfig-com.google.android.carrier-8901260570715066153-1.xml /sdcard/
adb shell
su
cp /sdcard/carrierconfig-com.google.android.carrier-8901260570715066153-1.xml /data/user_de/0/com.android.phone/files/
reboot
Add or edit these items before the </bundle> at the end. You can combine.
For Vo5G:
<boolean name="vonr_enabled_bool" value="true" />
For VoLTE (experimental):
<boolean name="carrier_volte_available_bool" value="true" />
For VoWiFi (experimental):
<boolean name="carrier_default_wfc_ims_enabled_bool" value="true" />
<boolean name="carrier_wfc_ims_available_bool" value="true" />
For VT carrier video calling (experimental, seems to set the toggle with my AT&T sim):
<boolean name="carrier_vt_available_bool" value="true" />
Reboot. Enjoy.
Experimental means experimental. Try at your own risk. Additional flags to properly config your carrier or use when roaming are likely needed.
To test Vo5G, the best way is to set NR-only in *#*#4636#*#* and then try to dial your voicemail. I have not tested ViNR/Vi5G (Video over 5G). Your phone will typically only use Vo5G as a last resort otherwise. Be sure to set back to NR/LTE/GSM/WCDMA when done.
And no, I don't know how to enable 5G for your phone in an unsupported country/carrier. I have a few leads on where the xml files may control 5G but again, untested. Or it's deep in the modem package's config files and not something I want to mess with. I'm just laying out my research. Your carrier may block or whitelist these features by IMEI or plan. At least that's the case for my AT&T sim.
Background:
This phone launched without Vo5G support. Or did it? When Android 13 DP1 came out, this was left enabled, among other goodies in the carrier settings and modem. When subsequent builds came out, Vo5G was gone regardless of modem or carrier config pb file overrides. Turns out I was looking in the wrong place. Credit to @foobar66 for laying a great foundation in the original VoLTE thread and ideas on how these kinds of edits can be Magisk modules. For the VoLTE item, when I set to false in the xml, I could no longer place calls in 4G or 5G modes on T-Mobile. It didn't shift down to HSPA+ though as a fallback. And yes, I know that T-Mobile is actually using an VoLTE/EPS core for Vo5G, but it's still Vo5G as far as the phone cares.
oriole:/ # logcat | grep -i vonr
04-28 23:55:50.668 2473 2473 D VoNrSettings: init:
04-28 23:55:50.668 2473 2473 D VoNrSettings: mHas5gCapability: true,mIsNrEnabledFromCarrierConfig: true,mIsVonrEnabledFromCarrierConfig: true,mIsVonrVisibleFromCarrierConfig: true
Attachments
Last edited: