Hello @grabar_juraj
I would like the dev team to look into this a bit closer, can you create a log recreating the issue? With a log they can see what triggers the charging instead of the audio.
When you are done feel free to send me a DM.
Please follow the below 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 cases” 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)
