Fix for Volte on Android 12 for rog phone 3

chaoticusrexchaoticusrex Level 1
edited September 26 in ROG Phone 3

The only solution currently for Volte on Android 12 on the rog phone 3 is to revert back to Android 11 which will wipe all of your data. When we were part of the beta we could message the mods and request a file that would allow us to reinstall Android 11. This file could not be shared with the public and it was warned you'd lose all your data. Waking up to Android 12 this morning and the same problem with volte still persists. I've kept the file handy and confirms it still works. Restarting now to get android 11 back.

I'm sorry mods but the people need to know you can provide a fix for them. It may cause them to lose data but if it's the only solution. People have to know. You also should warn people on the release notes before they upgrade. You knew this was an issue and you still pushed the update. This is on you now.

@CH_ASUS @ARP_ASUS @Falcon_ASUS @Christine_ASUS @Gustav_ASUS @fussion_ASUS @Irene2_ASUS



  • GT500GT500 Level 1

    They'll have to publish a firmware update to fix VoLTE on effected phones, and it may take them some time to do it since they at least claimed they had to add VoLTE support for each carrier separately (so they may have to fix it for each carrier separately).

    If it's something simple like a config error where VoLTE was switched off in the firmware by mistake, and all they need to do is switch it back on and publish a new firmware build, then maybe the fix will be quick. If not then expect it to take a while (as in possibly weeks to months depending on which carriers they prioritize).

    Regardless, removal of features like this when upgrading to a new major version of Android (first VoWiFi and now VoLTE) and the refusal to publish monthly security updates are pushing me to never buy another ASUS phone. At this point all good will is out the window, and ASUS has failed one too many times (the ROG Phone 3 is my third ASUS phone over the years).

    And since ASUS support will probably want to know, my carrier is Simple Mobile which uses T-Mobile's network in the USA. Both VoLTE and VoWiFi worked just fine with this service when I purchased the phone at the end of 2020. When I moved in to a new home at the end of 2021 I found the VoWiFi was no longer available (presumably killed off with the Android 11 update but I didn't need it previously and didn't use it) and now I've lost VoLTE and have no way to make phone calls at all unless I pay for a SIP account and use a SIP enabled app on my phone instead of using the phone service I already pay for...

  • marksbrasmarksbras Level 1

    The Android 12 notes indicate the eliminated SIP support. Not sure if what you are suggesting is an alternative to use SIP because I honestly don't understand it.

  • GT500GT500 Level 1

    SIP is a type of old-school VoIP account that's still used today. It has nothing to do with VoWiFi (Voice over WiFi) or VoLTE (Voice over LTE).

    Some service providers today require VoLTE in order to make or receive calls on their networks. T-Mobile's date for requiring VoLTE to make/receive calls was January 2021, and AT&T's date was February 2022.

    Considering the fact that the ROG Phone 3 doesn't seem to work with Verizon or U.S. Cellular (or at least it looks that way from a quick search), ASUS just disabled/broke voice service on their U.S. customer's phones.

  • I went to download the firmware to revert back to Android 11, but the Rog Phone 3 does not even show up anymore on their support page. The entire section with the drivers and firmware has disappeared.

    It's a bit mysterious considering it was there two days ago, but now the option of downgrading is no longer there.

  • Asus Devs just sucks. No VoLTE or VoWiFi for UK or polish networks at all. Calls quality are just simply bad and I can't use phone.

  • Are you ok? The firmware to downgrade is public since a long time, there is no need to request any files or whatnot.

    @GT500 its most likely the latter, hotfix should be out relatively soon. As you have wonderfully pointed out, in some countries VoLTE is needed to be able to call anyone which means ASUS is most likely going to hurry getting it out.

    @ClownVixen No worries, support page is still there, google has to adjust to the new url, it happens every now and then when ASUS fiddles on their site.

  • @GT500 Oh and as for security fix, honestly its irrelevant because ASUS actually is good when it comes to security fixes. It's very misleading to take the month of a security update as how well a company applies security fixes to their phones, ASUS does bigger batches than other companies and its open source, if you want to have all the security updates regularly you can use kirisakura kernel since he updates it frequently, hell because of people like kirisakura the phone is more secure than many other phones on the market. Hell its 2022 and the Rog2 still gets updated. Compare that to other phones such as the Razer phone 2 (stuck on A9), Black shark 2 (a10) and Nubia RM 3 (A10) youll find that ASUS actually provides excellent support especially for a gaming phone. The Rog2 would stay secure until its hardware is dead, software wise it won't be dead anytime soon. Also another sidenote, the software and firmware update quality on the Rog phones are is so much better than even mainstream phones like Oneplus.

    Is ASUS perfect? Hell no

    Is ASUS absolute dogsht? Hell no.

    I'd say they are upper mid tier, not as good as the top, but still notably better than the average phone manufacturer. If they would promise as much OS update as Samsung they would be top tier, the only thing holding ASUS back is being limited to "only" 2OS upgrades.

  • marksbrasmarksbras Level 1

    Still not a viable option. While it reinstalled Android 11 it immediately starts to download Android 12.

  • marksbrasmarksbras Level 1

    I paused it but it will not allow me to make any changes to include turning off auto update

  • It should, go to the firmware download section, klick on the settings wheel, and change "download wifi/mobile network" to "do not allow"

  • marksbrasmarksbras Level 1
    edited July 17

    It has greyed out the option so I am retrying but turning off wifi before the reboot hoping it will allow me to do it before allowing the phone to connect to anything. By turning wifi off and then bypassing most of the setup it did allow me to get to the system update area and turn off auto update so at least it is now on Android 11 and I can get it setup to see if functionality is back. I can say that volte is back and it looks like I am back to 5g so it now appears promising

  • Thanks for the link. I was able to downgrade to Android 11 and now have VoLTE and calling capabilities again.

    The sad thing is: it deleted my Google backup when it signed out of Google and I lost all of my messages and such. I don't believe I can restore a Google backup that is a higher version anyways.

    I did, however, copy every file from the Asus to my computer before doing maybe I can find the messages in one of those files/folders.

    If any of you do revert back: make sure you have a way to save everything you're wanting to keep. I knew it would remove everything, but I was an idiot to rely on Google backup. 😆

    Also, do not connect to WiFi or data before going to your settings and disabling automatic updates... because it will download Android 12 before your phone gets to the home screen.

    I tried to restore before it installed, but it still loaded up with Android 12. I then downloaded Android 11 again and started the process over, but this time: I did not connect to WiFi or my mobile data until I shut off automatic updates.

    At least my phone is a phone again. Still disappointed, but technology, eh?

  • GT500GT500 Level 1

    You may want to familiarize yourself with how Google does security patches for Android. I'll go ahead and explain it briefly below, but this is sort of hijacking the thread since it isn't about device security.

    The way it works is that, similar to how Microsoft does monthly updates for Windows, Google will publish security patches for Android at the beginning of every month. They will publish two patch levels, one that will be dated the 1st of the month and only contains some of the month's security patches, and the other will be dated the 5th of the month and will contain all of the security patches for the month. You can check your currently installed patch level in your phone's settings by going to "About phone" and looking for "Android security patch level" (this is clearly stated in Google's documentation for Android on their website).

    While Google has been slowly moving more and more things over to being updated via Google Play with each new version of Android, most core components of Android are still updated with the firmware, and this needs to be done by the device manufacturer every single month. ASUS has refused to do this with the ROG Phone 3, just like they refused to do it with the Zenfone 3 back in the day. Take a look at the firmware release history for the ROG Phone 3, and you will see gaps of anywhere from 3 to 6 months between firmware updates once the ROG Phone 5 was released, leaving their customers' phones vulnerability to critical security vulnerabilities for extended periods of time on a phone that is still officially supported by the manufacturer (which I consider to be unacceptable).

    You're correct that they did a better job with the ROG Phone 2, continuing to do monthly firmware updates even after the ROG Phone 3 was released. This is the reason I purchased the ROG Phone 3, because it looked like ASUS was finally taking device security seriously and giving their customers monthly security updates. Unfortunately they have failed yet again to deliver the basic security patches that Android devices require, and from a security standpoint I would have been better off with almost any other phone from any other manufacturer.

    As for the size of the updates, that's irrelevant. They can make those larger or smaller just by adding or removing bundled bloatware apps, and the size of the update doesn't necessarily have anything to do with the number of security patches or how secure the software in the firmware image is.

  • Thanks for being honest. It's a shame Asus didn't let it's customers know that the were issues with this update. Or if Asus knew there were issues... Address them BEFORE the release. Pathetic honestly... Definitely delaying my ROG phone 5 order.

  • If the solutions available via download why are the mods handing it out in Google drive and telling users not to share it? I may be an old crone in the tech world but seems a bit suss to me.

    Let me see... Send a user to a public link to get the fix or share with Google drive... Meh I'll share with Google drive... Via email... Wtf..

  • You may want to familarize yourself how manufacturers does security patches for Android. Lets take a quick example on how the security patches are misleading at best.

    One of the biggest vunurabilities which is: CVE-2020-11292 had been reported and made headlines a long time ago. It took google until its june patch to actually push this fix out. This issue has been fixed on Android 10 via kirisakura kernel 2020 december, a whole 6 months before it even came to google security patch.

    Hell google themselves had the fix in january themselves before making the security patch and even samsung:

    If youre basing your security of your phone based on what security level it runs on, then u're in for a bad surprise. If it wasnt for news sites to stir up drama about the vulnurabilty it would have been even later.

    I'm not talking size, but the amount of things they fix on the drivers and such. Not actual data size.

  • GT500GT500 Level 1

    We're talking about two different things. You're talking about how long it takes Google to patch a vulnerability, and I'm talking about how long it takes ASUS to give us those patches. The difference between Android and almost every other operating system is that Android requires device manufacturers to deliver security patches for the operating system to their customers' devices in the form of firmware updates, which ASUS is refusing to do in a timely manner for the ROG Phone 3.

    Even if Google takes a long time to fix a vulnerability, I don't think they usually publish information about it publicly until they have released the patch. Once that happens, the vulnerability is publicly known, and exploits are usually trivial to make (assuming the vulnerability isn't too difficult to exploit). Device manufacturers have a limited time to publish firmware updates with those patches before the vulnerabilities can be weaponized by malicious actors, and waiting several months in between updates to devices like ASUS has been doing leaves customers devices vulnerable to known critical vulnerabilities for extended periods of time.

    Most other device manufacturers will publish firmware updates every single month for their devices, and have been doing so for 5-10 years. Throughout most of this time ASUS has refused to do monthly security updates.

  • GT500GT500 Level 1
    edited July 18

    We appear to be talking about two different things here. You're talking about how long it takes Google to patch a vulnerability, and I'm talking about how long it takes device manufacturers like ASUS to give us those patches. With most operating systems updates like that come directly from the company that makes the operating system (Windows Updates for instance), however with Android the device manufacturer needs to deliver the updates to the customer' devices via firmware updates. Most device manufacturers have been publishing monthly firmware updates for their devices for 5-10 years now, but ASUS appears to be going back to refusing to do that just like they used to.

    Even if Google takes a while to patch a vulnerability they don't usually make information about it publicly available until they've patched it. Once a vulnerability is patched and the information about it is public knowledge, it becomes trivial to make exploits for it (unless it is difficult to exploit) and the vulnerability can be weaponized by malicious actors. It is important that device manufacturers deliver these patches to their customers' devices in a timely manner, and waiting several months to do so leaves customer devices vulnerable for an extended period of time.

    The patch level of your phone tells you which patches are installed. That's its purpose, as documented by Google (the makers of Android).

  • No we arent, because depending on manufacturer that patch has been applied way before the google patch has (as demonstrated above). This is why you can't really compare microsofts updates to googles security updates.

    Sometimes ASUS doesnt update the security patch from google because they already did before google added it inside their security package. Much like samsung added the fix for the vulnurability mentioned above long before google did.

    You cannot compare lets say a redmi phone with security patch july with a samsung with security patch july, the samsung has way more fixes and patches than the redmi. If all phones were streamlined, like windows updates are then ud have a good point, however they arent, the difference in exposure to vulnurabilies is massive.

    if you want fixes, unlock bootloader and flash kernels like kirisakura and a custom OS like lineageOS.

This discussion has been closed.