-
-
Notifications
You must be signed in to change notification settings - Fork 322
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bug: Picture in Picture (PIP) not showing video, patch 5.8.1 #4287
Comments
I've seen this issue but it only happens every once in a while, and it only started maybe a week ago. Try patching with only |
Reproduced once as well, I'm sure it's a YouTube bug though, confirm with the above ^ |
Or maybe problem with |
Thank you everybody for your support
Worked once after patched then the issue came back.
Issue still present with "Exit fullscreen" disabled It is a bit of work to try every patch, could you suggest which ones are the most likely to create this issue? But I suppose the issue is exactly about "Remove background playback restrictions"... |
Since the issue occured solely with that one patch, it's an issue with the YT app. The patch itself is not the cause |
Bug description
Since patch 5.8.1 my PIP not showing video but only comments/channel title, audio is working fine.
When I patched from 5.8.0 to 5.8.1 it worked fine for a day and suddenly the issue started
Mi 9 Lite (Android 10, MIUI 12.0.10 Global) I did read that this issue with MIUI was happened in the past but was something related to "Tablet Mini Player" or something like that but that option is not present anymore.
YT Version 19.16.39 and 19.47.53 (all default patches but gms core, I tried also with only advertise patches)
Revanced Manager 1.23.2
-Mount/Root installation, no issue with 5.8.0 regular (no mount) installation. I was not able to install back 5.8.0 patch as mount (since revanced-cli seems bugged installing as root according to issue opened in its github ReVanced/revanced-cli#355
Error logs
Solution
No response
Additional context
No response
Acknowledgements
The text was updated successfully, but these errors were encountered: