-
-
Notifications
You must be signed in to change notification settings - Fork 315
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: Android VR client not working in Spoof Video Stream patch. #3737
Comments
The manager logs are not useful for this. The app logs are needed. You need to use a laptop and use command prompt with adb. |
Additionally, you can try patching using the latest dev release. Integrations dev release has a fix that might resolve this. But to patch dev release you still need to setup adb. |
I did it, still the same result.
no? it patched successfully with adb, tried the latest dev release of the RV manager |
I have a desktop, but with linux and not windows, any alternative way? |
Yes Linux works just fine for adb and collecting the logs. Search for instructions on how to setup adb on whatever Linux flavor you use. Just to confirm, you are using ReVanced Manager and patching a APK you provided? There is a scam app from a .net site called "ReVanced Manager" and it's not official nor is it safe to use. |
Lol, yes, I am using the RV manager which i downloaded from the GitHub page by the same account by which this repo is made and I got the YT apk from apk mirror. I'll try to do the abd method when I get home. |
He mean to patch the apk with dev patches and Integrations with adb, not patched with dev manager |
oh, sorry. |
Closing in favor of #3759 |
Bug description
When the default client is selected to 'Android VR', no kind of video play, but with IOS as the default client, it works but the side effects of the IOS client got me crazy (stream opening from the very start).
Android Version: 14 (with Realme UI 5.0)
ReVanced Manager Version: 1.22.0
Youtube Version: 19.16.39 (as recommended by the RV manager)
Error logs
No response
Solution
No response
Additional context
No response
Acknowledgements
The text was updated successfully, but these errors were encountered: