YouTube ReVanced for Android 6-7

📣 Patches Update
v5.4.1-dev.4.1 [HOTFIX]
https://github.com/kitadai31/revanced-patches-android6-7/releases/tag/v5.4.1-dev.4.1

[This is a hotfix release]
Fixed an issue where the ReVanced Extended settings page is blank on Android 6.0
Please patch again if you are facing this issue.

📣 ReVanced Manager for Android 5-7 is back!

Sorry for the wait!
I just released an update of "ReVanced Manager for Android 5-7" fork.
Now Patches v5.x.x is supported.
You can use ReVanced Manager on use Android 6-7 devices again!
https://github.com/kitadai31/revanced-manager-android5-7/releases

📣 Patches Update
v5.4.1-dev.4
https://github.com/kitadai31/revanced-patches-android6-7/releases/tag/v5.4.1-dev.4

📣 Patches Update
v5.4.1-dev.3
https://github.com/kitadai31/revanced-patches-android6-7/releases/tag/v5.4.1-dev.3

Casting crash is fixed.
I can't release Manager update today, sorry.
Manager is still not ready yet. Please use other patching methods!

[How to patch]

I will release patches update today
Manager update also may be released (If I have time)

This workaround will work for several months.
After a few months, Google will completely block access from these older clients.
After that, the app will be completely unavailable with [400] error, even if the update screen is disabled.

For reference, this is the schedule for when Google ended support for 16.01-17.32:
- October 2023: The force update screen started to appear for 16.01-17.32.
- March 2024: Access from 16.01-17.32 was completely blocked with [400] error.

From this example, it can be inferred that 17.34.36 will be usable until July.
There are only 5 months left. Enjoy!

Google started to show the force update screen ("Update your app" / "Switch to YouTube.com") to old clients less than 19.01.xx. (Including 17.34.36)

This means that the stock YouTube app is no longer available on Android 6-7.

However, RVX have a patch to disable the update screen! 🥳
In v5.2.1: "Hide layout components" patch
In v2.160.12: "disable-update-screen" patch

So, you can continue to use YouTube ReVanced on Android 6-7 for now! 👍

Note: Disabling the update screen is just a temporary workaround.
See also the next message.

📣 Patches Update
v5.2.1
Full changelogs:
https://github.com/kitadai31/revanced-patches-android6-7/releases/tag/v5.2.1

This is the biggest update ever for ReVanced Android 6-7! 🥳
Until now, this project was based on RVX v2.160.1 (released in February 2023).
After this update, this project is based on the latest version of RVX.
A ton of new features have been added, and many bugs have been fixed. (e.g. Livestream ads, Default video speed)

[How to patch]

As previously announced, ReVanced Manager for Android 5-7 fork is currently unavailable.

Clean install is recommended.
There is some known isssues, please read the full changelogs.

The new patches was already completed 5 days ago...
And I wanted to prepare the update of Manager for A5-7.

However, I'm busy this week and don't have time to touch the Manager.
In addition, yesterday, it turned out that to get the Manager to work on A5-7, it requires more work than before.
But I want to release the patches quickly.

So, I will release it before the Manager is finished.
Until the Manager A5-7 update is released, the following patching methods will be available:

- Revancify
- RVX Builder
- ReVanced CLI
- Official ReVanced/RVX Manager on Android 8.0+ devices (Change source to kitadai31, and patch, then save the patched apk and move it to the Android 6-7 device)

I'm going to release the patches update (recreated based on the latest RVX) tomorrow!

I am currently working on rewriting this "YouTube ReVanced for Android 6-7" based on the latest RVX Patches.
(This is an approach of adding minimal fixes to the latest RVX Patches)
This work started two days ago.
I haven't started on fixing the important huge patches such as RYD and SB yet, but fortunately the work is progressing well.

Currently, “YouTube ReVanced for Android 6-7” is based on RVX Patches v2.160.1 with minimal changes some additional features.
RVX v2.160.1 is a very old version released on February 13, 2023, and its internal structure was significantly different from the current one, making maintenance difficult.
For example, the current RVX Patches contains a lot of new features that should also be available in 17.34.36, but I left it alone because it would take too long to backport.

However, the approach of adding minimal fixes for 17.34.36 to the latest RVX will keep the our patches up-to-date.
In fact, new features like Alternate Thumbnails (Dearrow) and keyword filtering are already available.
Surprisingly, these patches worked without any modification on 17.34.36.
The only thing holding them back was the hassle of porting to v2.160.1.
Live stream ads is fixed too.

Also, Revancify will be available without forking.
The ReVanced Patcher library will also be up to date, so all tools will use the official or RVX tools instead of forks.

This has been my goal since I forked RVX.
Release will be in the new year.
Have a happy new year, everyone!

(Reference)
Left: Revancify
Right: RVX Builder

Do you want to continue using Revancify for our patches?

Recently, Revancify is updated to "Revancify v2".
It supports new .rvp format patches.
And our patches is not compatible with Revancify v2. (Because our patches will not migrate to .rvp format.)
Decipher (a developer of Revancify) suggested me to fork Revancify v1.

So, I'm considering forking Revancify v1, just for our patches.

But there is RVX Builder also.
RVX Builder is another patching tool.
It runs on Termux like Revancify, but it uses browser for UI.

I think RVX Builder is useful enough.
Also, having lots of forks makes things complicated.

Therefore, I would like to hear your opinion in a poll.
Do you want a Revancify v1 fork?

From 2024-12-01 12:09:26 UTC until 2024-12-01 15:18:25 UTC (past 3 hours), a problematic patches jar file was distributed.

If you have started the ReVanced Manager during this time, Manager will not load the patch as shown in the image.
If you are experiencing this issue, clear the cache of Manager from App Info.
Sorry for my mistake.
(I forgot to bundle classes.dex into the patches jar. Also, Java 21 was accidentally required for CLI.)

📣 Patches Update
revanced-patches: v2.160.12
revanced-integrations: v0.96.11

• Fixed playback error [400] problem
(Removed "spoof-client" patch and added new "spoof-streaming-data" patch)
• Fixed "Custom seekbar color" patch
• Fixed RVX Builder cannot select default patches by "Select All" button
• Minor improvements of shorts-seek patch and sponsorblock patch

Full changelogs:
https://github.com/kitadai31/revanced-patches-android6-7/releases/tag/v2.160.12

This update introduces a whole new strategy for "Spoof client" patch that called "Spoof streaming data".
All non-root users should update!
[How to patch]

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.

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)

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...

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.

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

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.

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 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 (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!!!

If possible, tell me also whether the (exit code = XXX) error occurs on normal ReVanced Manager A5-7.

Does anyone have ARMv7 devices?
Please help me with testing.

This is a ReVanced Manager A5-7 testbuild that uses Maximoff's aapt2 binary.
(Maximoff is developer of APKTool M)
It might fixes (exit code = 135) errors on ARMv7 devices.

This test has been finished. Thank you.

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

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 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

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)

"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.

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

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 in 2-3 days 4-7 days
(because I'm busy tomorrow 😭)

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.

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.

How to solve buffering after 30-40 sec problem after migrating to GmsCore:

1. Disable battery optimization of GmsCore

Settings > Battery > 3-dots menu > Battery optimization > All apps > microG Services > Don't optimize.
OR
microG Settings > Self check > Tap Disable battery optimization.
(not tap the checkbox, tap the text)
(Ignore other self check items. It's not related to ReVanced GmsCore)

If it doesn't work:
2. Force stop GmsCore


"Change device profile" might be false information!!!
Don't change device profile!!!

Patches Update Released!
• revanced-patches v2.160.9
• revanced-integrations v0.96.9

"The following content is not available on this app" problem was fixed

🔸Switch to ReVanced GmsCore
The official ReVanced Team released the new MicroG called "GmsCore".
It fixes "The following content..." issue.
From this patch version, old Vanced MicroG is not supported. You need the new ReVanced GmsCore.

🔸What to do
1. Install ReVanced GmsCore
2. Re-patch the YouTube apk
3. Uninstall old VancedMicroG

For details, read the changelog page.
https://github.com/kitadai31/revanced-patches-android6-7/releases/tag/v2.160.9

[How to patch]

There was an issue with RVX Builder, but it has been fixed.

Error: EISDIR: illegal operation on a directory, read

The settings had been changed but the "How to build" document were not updated.
It is corrected now.
https://github.com/kitadai31/revanced-patches-android6-7/wiki/How-to-build#method-4-using-rvx-builder-pcandroid

Watch History problem got fixed right now !!!
Please say thanks to oSumAtrlX (Revanced owner) for his work, I just copied his fix

🔸How to use the fix?
A fix for History has been released with the latest version of ReVanced Patches. Re-patch YouTube APK with the latest patches to apply the fix.
[How to patch]

🔸Will this bring back lost history?
Lost history won't come back, unless Google fixes it.
But you can see the lost history at https://myactivity.google.com/product/youtube