When I boughg new Asus Zenfone Max Pro M2 phone there was touch issue. I requested for return on flipkart but they sent technician and he just reset the phone. Again next day touch problem occurred and technician did the same again. This return and reset process continued 5 times i.e. I put the return request on flipkart 5 times but they didn't approved the return. Meanwhile I got the next Software update on my phone and phone worked till March( When the warranty period expired). But after March update the touch problem started again. It lasted for 2 days and started working automatically. But after around 10 days the same problem occurred again. This time it didn't get resolved automatically. Then I did factory reset, no benefit of this....then I downgraded to WW_Phone_16.2017.1912.072 from WW_Phone_16.2017.1912.092 But no gain...touch is still not working ...now I installed anothet version i.e. Android 10 beta version from official Asus website. Touch still not working. I decided to downgrade it to the earlier version i.e. WW_Phone_16.2017.1912.072 But it showed error E3304: This package is for ASUS_X01BD devices. This is X01BD device. Now I changed the code where it check the Device Model. It is available in Updater script file. And installed the framework WW_Phone_16.2017.1912.072 using TWRP recovery. This time touch started working. Please tell me what is the exact problem behind this touch issue. And please fix it in new firmware update and release as soon as possible.
Let's go in phases to reach at conclusion on my phone issue is same as the piunikaweb.com article. As a layman what I understand of the article is that ASUS Zenfone OTA updates follow Block OTA method which update in same partition and their is no fallback. Newer versions???? of Android support payload based OTA via A/B partitioning, wherein update takes place in one partition and if it is non workable their still is old system to fall back upon. The article says ASUS Zenfone do not follow A/B partitioning method. As I am no expert/authority on these matters, would like to know your opinion, what I have understood is right?
You are currect, the only downside for a/b partitioning method is that it takes a lot of storage (2 to 5gb). Because of it a lot of OEM's are not implementing it in their devices (samsung have never used the a/b partitioning method). But it changes from android 11 because it does not allow any method other than a/b partitioning method for system update.
Hi mukesh_mehra1 Thank you for your reply. How can you pass SMMI test while your screen can not be touched? 😅 Besides, what is the frequency of the zero touch issue? Please reply the question above, and I may need your logs for further checking.
Oh ok, thanks veeharish2005. Well, I can hardly tell the root cause or the reason why "Root Integrity Check" (did mukesh_mehra1 access from the process here: https://www.asus.com/support/FAQ/1006346/?) failed in Android 9 because the device was re-flashed with Android 10 OTA file and I have not been in the same user behavior exactly as him. I can not know what the usage process while the device was in Android 9. However, please let me know once the issue appears again. I may need the logs for further checking.
