-
Notifications
You must be signed in to change notification settings - Fork 29
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(YouTube - Spoof Client): Wrong listed spoofing side effects #2072
Comments
Even if you spoof it with Android VR, Shorts and Clips use the iOS client.
This depends on your Android version. |
I forgot about that, though it can still be made a little clearer
Might wanna add "depending on Android version" to avoid confusion, as for most people higher qualities will most likely be available |
Well, I think the sentence 'Higher quality may be missing' is enough.
This part needs to be changed.
This is an issue only for Android 8.0 (API 26) https://developer.android.com/media/media3/exoplayer/supported-formats#progressive-container |
reflected in revanced-patches-4.8.5 |
Type
Other
Tools used
RVX Manager
Application
YouTube (general)
Bug description
The following changes should be made on spoof client strings:
Watch history on brand accounts doesn't work only on iOS spoof, works fine on VR spoof. It should be removed from "revanced_spoof_client_summary_on" and instead added to "revanced_spoof_client_use_ios_summary_on".
"Higher video qualities may be missing." on iOS spoof has already been fixed. Only HDR quality isn't available, and that's already listed on general spoof summary.
Video background playback works on live streams, only audio-only background playback doesn't (when you tap headphone icon on pip mode). Also, live streams don't work at all on Android 8.0 and probably below, so something like "Live streams may not play on older devices" should probably be added. (iOS spoof)
Error logs
No response
Solution
No response
Additional context
No response
Device Environment
No response
Acknowledgements
The text was updated successfully, but these errors were encountered: