Fix for Volte on Android 12 for rog phone 3

[chaoticusrex]

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

[trevorjr84]

chaoticusrex

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

Fix for Volte on Android 12 for rog phone 3

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.

[chaoticusrex]

Danishblunt

https://zentalk.asus.com/en/discussion/62072/fix-for-volte-on-android-12-for-rog-phone-3

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.

https://www.asus.com/supportonly/ROG%20Phone%203%20(ZS661KS)/HelpDesk_BIOS/

View post

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..

[Danishblunt]

GT500

https://zentalk.asus.com/en/discussion/comment/219152#Comment_219152

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.

View post

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:
https://www.xda-developers.com/samsung-may-2021-security-update-protected-qualcomm-vulnerability/
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.

[GT500]

Danishblunt

https://zentalk.asus.com/en/discussion/comment/219173#Comment_219173

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:

https://www.xda-developers.com/samsung-may-2021-security-update-protected-qualcomm-vulnerability/

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.

View post

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.

[GT500]

Danishblunt

https://zentalk.asus.com/en/discussion/comment/219173#Comment_219173

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:

https://www.xda-developers.com/samsung-may-2021-security-update-protected-qualcomm-vulnerability/

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.

View post

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).