MIUI 12’s Video toolbox feature is causing some background audio problems on YouTube according to some users. This feature has been active since previous versions of MIUI, but after the new version people seem to report some bugs.
MIUI 12’s Video toolbox is causing some problems
MIUI 12 integrated a lot of renovations into this feature, such as a completely revamped UI experience and smart functionalities that Xiaomi users have long been waiting for. This box remains on the left or right side of the screen and allows us to quickly access many video-centric controls with a simple swipe.
You can take a screenshot, record a video, create a note in a floating window and, best of all, play video sound with the screen off. Unfortunately, this new bug on MIUI 12 is preventing people to play video sound when the screen is off.
No background audio on YouTube
What makes this feature really cool is the option to play video audio with the screen off, identified in the tool by an ear icon. This little utility does exactly what its name suggests and allows, among other things, listening to YouTube with the screen off, bypassing YouTube’s background playback restriction imposed on free users.
Obviously, the use of the feature is not limited only to YouTube, as it can also be used in other applications, to play voice messages on Instagram with the screen off, or to play podcasts for example. Unfortunately in the last few hours, there are several complaints on Xiaomi forums claiming that the background audio playback feature in MIUI 12’s video toolbox does not work with YouTube.
MIUI 12 bug or YouTube’s fault?
Some users have said that, since the bug only happens with the Google app, YouTube has put measures to prevent Xiaomi users from bypassing the limitation.
Fortunately, a moderator of the support center indicates that the problem is not universal and occurs from time to time only on certain devices, such as the Redmi Note 8. Probably the origin of this failure is an update but, unfortunately, a solution has not yet been provided to affected users. We’ll have to wait for a hotfix it seems.
