[BUG] - Volume key changes only by one level when holding it pressed

Ace2099Ace2099 Level 1
edited November 15 in ZenFone 9

Please tell us some basic information before asking for help:

  1. Model Name: Zenfone 9
  2. Firmware Version: WW_32.2040.2040.23
  3. Rooted or not: Not rooted
  4. Frequency of Occurrence: 80% of the time
  5. APP Name & APP Version (If your issue relates to the app): ZenUI


Hi, I noticed that most of the times when I want to change the volume from the volume keys, holding vol up or vol down pressed, it will only adjust it by one level. I have to press it again and hold it again to make the volume move by multiple levels.

This is really frustrating because sometimes I have the media volume set high, and when something starts playing loud I want it to quickly lower the volume, and this bug requires me to press the volume key twice to modify the volume by multiple levels, instead of instantly modifying by keeping it pressed only once.


  • Hey @Ace2099, I wasn't able to recreate the issue. Does the problem while using a specific app?

    Also, we recently released a new FW. Can you check if the problem continues to prevail even after the installation of the latest update?

  • Ace2099Ace2099 Level 1
    edited October 11

    Hey @Mansi_ASUS , no, I saw this happen no matter the opened app.

    Newer FW than WW_32.2040.2040.23 ? If so, I don't get any update, nor I can see newer one on Asus support page.

  • edited October 11

    Hey @Ace2099!

    Sorry for the confusion, I think I misread the information, the new update is meant only for the US to fix a carrier issue. However, we will look into the problem you've brought to our attention.

  • It happens to me when phone is locked only. It looks similar to https://zentalk.asus.com/en/discussion/64438/problem-with-changing-volume-during-phone-call

    @Mansi_ASUS Could you look at this issue, too?

  • I have experienced this on Z9. It was not there on Z8.

  • Hey @mumei6102, sure thing. I'll check it out.

  • Hey @Ace2099,

    In order to resolve the issue, the R&D team requires the following information from your end-

    • Has the issue occurred while using a wired (3.5mm) or Bluetooth headset?
    • Can you walk us through the events where this issue generally occurs? For example, while using specific apps or leaving the phone idle for a long time etc.

    The R&D team also requires logs or Screenshots/Screen Recordings when the issue occurred.

    Please follow the given steps to enable the built-in log tool (Bug reporter).

    1.  Open “Calculator APP”

    2.  Enter “.19595+=”

    3.  Select the Log type according to the type of issue you want to capture. “General” will work for most issues.

    4.  After your selection the log tool will exit so you can duplicate the issue or wait for it to happen. Try to use the screen recorder to show your issue when possible. If you can't screen record your issue, then please take a screenshot right after the issue has occurred (as a timestamp) so we know where to look in the log.

    5.  Navigate back to the log tool via calculator and Tap "FINISH AND SHARE".

    6. It takes several minutes for the log to generate. You can exit and do other stuff in the meantime. A silent notification will tell you once the process is done. Tap the notification and then the share button to upload the file to Google Drive and share the link with a moderator. Just make sure to change the permission first so that everyone with the link has permission to view it.

    Note: When you're no longer planning on logging your device, enter “.09595+=” in the calculator and the log tool will stop as well as deleting all stored log files. Make sure to share via calculator. The files found in internal storage -> asus_log are not the correct files (they are only 1.2kb)


  • I am having the exact same issue

  • I also experienced this bug, without using headset and the phone is leaving idle for a long time

  • Thread automatically closed due to inactivity. If the reported issue has not been resolved or you require further assistance from one of our moderators, please create a new thread and we will be with you shortly.

This discussion has been closed.