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

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

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.

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

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)

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