New buffering issue
A new buffering issue has started for many users today.
🔶 Problem:
Videos start buffering at the beginning or about 10 seconds.
The buffering may continue indefinitely, or you may have to wait about 20 seconds for loading.
If the video is loaded, the quality is restricted to 360p and 720p.
(These are fallback video formats of YouTube. fmt=18 and fmt=22.)
When this fallback is happened, streaming playback doesn't work for some reason and the entire video is loaded at the beginning, so it takes a very long time to load.
🔶Progress:
There is no fix yet.
Wait for ReVanced developers to fix!
(I can't do anything about this 😢)
※ This new issue affects all ReVanced, not only my Android 6-7 fork.
※ Buffering issues are always random and has an inconsistent outcome for each users.
A new buffering issue has started for many users today.
🔶 Problem:
Videos start buffering at the beginning or about 10 seconds.
The buffering may continue indefinitely, or you may have to wait about 20 seconds for loading.
If the video is loaded, the quality is restricted to 360p and 720p.
(These are fallback video formats of YouTube. fmt=18 and fmt=22.)
🔶Progress:
There is no fix yet.
Wait for ReVanced developers to fix!
(I can't do anything about this 😢)
※ This new issue affects all ReVanced, not only my Android 6-7 fork.
※ Buffering issues are always random and has an inconsistent outcome for each users.
YouTube ReVanced for Android 6-7
New buffering issue A new buffering issue has started for many users today. 🔶 Problem: Videos start buffering at the beginning or about 10 seconds. The buffering may continue indefinitely, or you may have to wait about 20 seconds for loading. If the video…
Please open Telegram to view this post
VIEW IN TELEGRAM
Device model, Android version, YouTube version, patch developer, GmsCore version, and GmsCore developer are not related to the cause.
It's perfectly random.
Don't spread rumor!
The only workaround that might work is changing account, re-login to account, or re-install GmsCore.
However, it's unlikely to work. (It didn't work for me either!)
Buffering issues are always random.
It's perfectly random.
Don't spread rumor!
The only workaround that might work is changing account, re-login to account, or re-install GmsCore.
However, it's unlikely to work. (It didn't work for me either!)
Buffering issues are always random.
Official ReVanced Team & inotia00 released the playback fix update! 🥳
("Spoof client" patch)
So, I'm going to release an update of RVX Android 6-7 in2-3 days 4-7 days
(because I'm busy tomorrow 😭)
("Spoof client" patch)
So, I'm going to release an update of RVX Android 6-7 in
(because I'm busy tomorrow 😭)
Patches Update Released!
• revanced-patches v2.160.10
• revanced-integrations v0.96.10
🔶 The new buffering issue has been fixed! 🎉
I'm sorry to keep you waiting!
"Spoof client" patch has been added to fix video playback.
🔶 How to use the fix
1. Repatch the YouTube apk with Manager or other methods.
2. Open [Settings > ReVanced settings > Miscellaneous > Spoof client] and turn on [Spoof client] manually.
[How to patch]
full changelogs:
https://github.com/kitadai31/revanced-patches-android6-7/releases/tag/v2.160.10
• revanced-patches v2.160.10
• revanced-integrations v0.96.10
🔶 The new buffering issue has been fixed! 🎉
I'm sorry to keep you waiting!
"Spoof client" patch has been added to fix video playback.
🔶 How to use the fix
1. Repatch the YouTube apk with Manager or other methods.
2. Open [Settings > ReVanced settings > Miscellaneous > Spoof client] and turn on [Spoof client] manually.
[How to patch]
full changelogs:
https://github.com/kitadai31/revanced-patches-android6-7/releases/tag/v2.160.10
YouTube ReVanced for Android 6-7
Patches Update Released! • revanced-patches v2.160.10 • revanced-integrations v0.96.10 🔶 The new buffering issue has been fixed! 🎉 I'm sorry to keep you waiting! "Spoof client" patch has been added to fix video playback. 🔶 How to use the fix 1. Repatch the…
"Spoof client" setting is not enabled by default.
If you are facing video playback problem, open [Settings > ReVanced settings > Miscellaneous > Spoof client] and turn on [Spoof client] manually!
"Spoof client" option is a workaround, and it contains side effects.
If you are not a target user of the endless loading problem, you don't have to turn on this.
Additional updates may be released in the future to fix side effects.
If you are facing video playback problem, open [Settings > ReVanced settings > Miscellaneous > Spoof client] and turn on [Spoof client] manually!
"Spoof client" option is a workaround, and it contains side effects.
If you are not a target user of the endless loading problem, you don't have to turn on this.
Additional updates may be released in the future to fix side effects.
By the way, there are two buffering issues.
• Old buffering issue: Video stops at 30-40 seconds and never starts again
• New buffering issue: Video stops at 0-10 seconds, but sometimes video starts again after 1-3 minutes (but the video quality is restricted to 360p and 720p)
The new "Spoof client" patch fixes the latter.
If you have the former problem, you don't need to turn on "Spoof client".
To fix the old buffering issue, just force stop GmsCore. (Make sure you are using the latest patch)
• Old buffering issue: Video stops at 30-40 seconds and never starts again
• New buffering issue: Video stops at 0-10 seconds, but sometimes video starts again after 1-3 minutes (but the video quality is restricted to 360p and 720p)
The new "Spoof client" patch fixes the latter.
If you have the former problem, you don't need to turn on "Spoof client".
To fix the old buffering issue, just force stop GmsCore. (Make sure you are using the latest patch)
ReVanced Manager for Android 5-7 Update
v1.17.4 has been released
https://github.com/kitadai31/revanced-manager-android5-7/releases/tag/v1.17.4
- fix: Patched apk contains garbage files in
→ This fix reduces the patched apk size by 10MB
- feat: add ripLibs feature
- fix: Excessive requests to GitHub API
→ No more rate limit errors! (almost)
- feat: show all network errors in Toast
- feat: Allow changing patch selection by default
- apply changes from upstream v1.17.3
v1.17.4 has been released
https://github.com/kitadai31/revanced-manager-android5-7/releases/tag/v1.17.4
- fix: Patched apk contains garbage files in
res
directory→ This fix reduces the patched apk size by 10MB
- feat: add ripLibs feature
- fix: Excessive requests to GitHub API
→ No more rate limit errors! (almost)
- feat: show all network errors in Toast
- feat: Allow changing patch selection by default
- apply changes from upstream v1.17.3
GitHub
Release v1.17.4 · kitadai31/revanced-manager-android5-7
fix: Patched apk contains garbage files in "res" directory
This fix reduces the patched apk size by 10MB.
feat: add ripLibs feature
fix: Excessive requests to GitHub API
No more rate ...
This fix reduces the patched apk size by 10MB.
feat: add ripLibs feature
fix: Excessive requests to GitHub API
No more rate ...
revanced-cli fork has been released
https://github.com/kitadai31/revanced-cli
fixed some issues present in revanced-cli v3.1.1 (like patched apk contains garbage files)
Now, this is a recommended revanced-cli for our patches
https://github.com/kitadai31/revanced-cli
fixed some issues present in revanced-cli v3.1.1 (like patched apk contains garbage files)
Now, this is a recommended revanced-cli for our patches
FINISHED
1 B
Please help me with testing.
This is a ReVanced Manager A5-7 testbuild that uses
(Maximoff is developer of APKTool M)
It might fixes (exit code = 135) errors on ARMv7 devices.
This test has been finished. Thank you.
ReVanced Manager for Android 5-7 Update
v1.17.5
https://github.com/kitadai31/revanced-manager-android5-7/releases/tag/v1.17.5
- Support ARMv7 (32bit) devices
- improve patching log
ReVanced Team fixed the
(This aapt2 binary is different from the above Maximoff's one. ReVanced Team fixed not only 135 error but also 139 error.)
ARMv7 (armeabi-v7a) devices are now supported!!!
v1.17.5
https://github.com/kitadai31/revanced-manager-android5-7/releases/tag/v1.17.5
- Support ARMv7 (32bit) devices
- improve patching log
ReVanced Team fixed the
(exit code = 135 or 139)
issue on ARMv7 devices by updating aapt2 binary.(This aapt2 binary is different from the above Maximoff's one. ReVanced Team fixed not only 135 error but also 139 error.)
ARMv7 (armeabi-v7a) devices are now supported!!!
GitHub
Release v1.17.5 · kitadai31/revanced-manager-android5-7
Support ARMv7 devices
improve patching log
ReVanced Team fixed the (exit code = 135 / 139 / 7) issue on ARMv7 devices by updating aapt2 binary.
ARMv7 (armeabi-v7a, 32bit) devices are now supported!!!
improve patching log
ReVanced Team fixed the (exit code = 135 / 139 / 7) issue on ARMv7 devices by updating aapt2 binary.
ARMv7 (armeabi-v7a, 32bit) devices are now supported!!!
Patches Update
revanced-patches: v2.160.11
revanced-integrations: v0.96.11
• Spoof client: Fix some side effects of iOS spoofing:
- Higher video qualities may not be available
- Live streams not available on Android 8.0
- Not able to play live streams in background
- Watch history doesn't work with brand accounts (Experimental, Need to turn on setting manually)
• Spoof client: Change default spoofing type of live streams to iOS from Android VR
• Check watch history domain name resolution
[How to patch]
full changelogs:
https://github.com/kitadai31/revanced-patches-android6-7/releases/tag/v2.160.11
Sorry for the wait. I completely missed these fixes by the official ReVanced/RVX...
The next update may be soon, as the ReVanced team is developing a whole new strategy for Spoof client patch.
revanced-patches: v2.160.11
revanced-integrations: v0.96.11
• Spoof client: Fix some side effects of iOS spoofing:
- Higher video qualities may not be available
- Live streams not available on Android 8.0
- Not able to play live streams in background
- Watch history doesn't work with brand accounts (Experimental, Need to turn on setting manually)
• Spoof client: Change default spoofing type of live streams to iOS from Android VR
• Check watch history domain name resolution
[How to patch]
full changelogs:
https://github.com/kitadai31/revanced-patches-android6-7/releases/tag/v2.160.11
Sorry for the wait. I completely missed these fixes by the official ReVanced/RVX...
Manager Update
v1.17.6
https://github.com/kitadai31/revanced-manager-android5-7/releases/tag/v1.17.6
• Move temporary directory to filesDir from cacheDir
This arrows patching with low storage space.
Previously, when storage space was low, the patching would fail because temporary files were deleted by Android.
This problem was fixed.
v1.17.6
https://github.com/kitadai31/revanced-manager-android5-7/releases/tag/v1.17.6
• Move temporary directory to filesDir from cacheDir
This arrows patching with low storage space.
Previously, when storage space was low, the patching would fail because temporary files were deleted by Android.
This problem was fixed.
Good news: RVX Music now supports Android 5.0-6.0!
Recently, I sent a pull request that adds support for YouTube Music v6.20.51 (final version for A5 & A6) to inotia00's official RVX.
It has been merged in RVX Patches v4.14.1 (released yesterday)
Android 5.0-6.0 -> YT Music v6.20.51
Android 7.x -> YT Music v6.42.55
Patch these version of YT Music to get RVX Music for older Android versions!
Check detailed information:
https://github.com/kitadai31/revanced-patches-android6-7/wiki/About-YouTube-Music
※ You may need other Android 8.0+ devices to patch RVX Music.
See the above URL
Recently, I sent a pull request that adds support for YouTube Music v6.20.51 (final version for A5 & A6) to inotia00's official RVX.
It has been merged in RVX Patches v4.14.1 (released yesterday)
Android 5.0-6.0 -> YT Music v6.20.51
Android 7.x -> YT Music v6.42.55
Patch these version of YT Music to get RVX Music for older Android versions!
Check detailed information:
https://github.com/kitadai31/revanced-patches-android6-7/wiki/About-YouTube-Music
※ You may need other Android 8.0+ devices to patch RVX Music.
See the above URL
Since November 21st, some users have started experiencing 400 error.
This is caused by the "Spoof client" patch.
This patch is outdated and already replaced with a new better "Spoof streaming data" patch in the official ReVanced/RVX.
But our patches still using it.
I've been busy these past few months and haven't had the urge to port "Spoof streaming data".
However, the old "Spoof client" is starting to stop working anymore, so I will port it as soon as possible.
Please wait for update.
This patch is outdated and already replaced with a new better "Spoof streaming data" patch in the official ReVanced/RVX.
But our patches still using it.
I've been busy these past few months and haven't had the urge to port "Spoof streaming data".
However, the old "Spoof client" is starting to stop working anymore, so I will port it as soon as possible.
Please wait for update.
Fortunately, inotia00 had created this patch to be compatible with 17.34.36, so all I have to do is copy the code from RVX!
(So why have I not done this before? - Yes, because of my laziness)
I feel an apology for inotia00...
(So why have I not done this before? - Yes, because of my laziness)
I feel an apology for inotia00...
YouTube ReVanced for Android 6-7
Since November 21st, some users have started experiencing 400 error. This is caused by the "Spoof client" patch. This patch is outdated and already replaced with a new better "Spoof streaming data" patch in the official ReVanced/RVX. But our patches still…
Temporary workaround:
Open Settings > ReVanced settings > Miscellaneous settings > Spoof client
Change all 4 options to "Android VR"
Or, if you don't have a buffering issue now, you can turn off the entire "Spoof client" toggle.
(Only for lucky person)
Open Settings > ReVanced settings > Miscellaneous settings > Spoof client
Change all 4 options to "Android VR"
Or, if you don't have a buffering issue now, you can turn off the entire "Spoof client" toggle.
(Only for lucky person)
YouTube ReVanced for Android 6-7
Since November 21st, some users have started experiencing 400 error. This is caused by the "Spoof client" patch. This patch is outdated and already replaced with a new better "Spoof streaming data" patch in the official ReVanced/RVX. But our patches still…
This information was partially incorrect.
The 400 error is caused by the iOS client rather than the "Spoof client" patch.
Both "Spoof client" and "Spoof stream data" patch causes 400 error when spoofing to iOS client.
However, the former displays an error screen when a 400 errors occurred, whereas the latter automatically retries using the Android VR client and does not displays the error screen.
This is why I misunderstood.
The 400 error is caused by the iOS client rather than the "Spoof client" patch.
Both "Spoof client" and "Spoof stream data" patch causes 400 error when spoofing to iOS client.
However, the former displays an error screen when a 400 errors occurred, whereas the latter automatically retries using the Android VR client and does not displays the error screen.
This is why I misunderstood.