Q&A (Questions & Answers) - EN


Q1. What is this project?

A1. "Vanced Extended" - an unofficial continuation of the YouTube Vanced project development.

The official YouTube Vanced project has been discontinued. There are several follow-up projects that use the source of the YouTube Vanced project. Among them, "YouTube ReVanced" is well-known to the public.

"Vanced Extended" is also one of the follow-up projects, focusing on putting the features of the original YouTube Vanced and it's own features into the latest version of official YouTube app.

Also, this project is not done as a team, but only by myself.
Therefore, the update cycle of this project is not constant (the update cycle may be fast or it may be delayed).
Also, it may be discontinued at any time due to my personal circumstances.


Q2. I changed "Enable RYD (ALPHA)" to ON in "Return YouTube Dislike settings". Why is RYD not working though?

A2. You will see the Return YouTube Dislike dialog that appears when you first install the app.
You may have seen the phrase "WARNING: CURRENTLY IN ALPHA. If the YouTube API changes, dislikes button may not appear".
With that said, since YouTube v17.09.xx, the YouTube API has changed.
Therefore, in the latest version of YouTube Vanced@inotia00, simply enabling "Enable RYD (ALPHA)" does not display the number of Dislikes.
(More precisely, it is associated with the change of the button container to Litho)

If you change "Settings > Vanced settings > Layout settings > Old Layout (Not Recommend)" to ON, YouTube Vanced@inotia00 app will go back to v17.08.35 version, and RYD will work normally.

There is currently no way to make RYD work other than this method, and that's why KNOWN ISSUE says "RYD does not work".


Q3. Is it possible to run YouTube Vanced@inotia00 without installing MicroG in the NON-ROOT version?

A3. From YouTube v17.26.xx and later, the app has been changed to run only after receiving a specific token from MicroG. Since this is a YouTube source change, MicroG is required to run the app in YouTube Vanced@inotia00 v17.26.xx and later.
If you want to run the NON-ROOT version of YouTube Vanced@inotia00 without installing MicroG, please install YouTube Vanced@inotia00 v17.25.34.


Q4. Some YouTube Vanced@inotia00 settings are not applied properly (example: There is no download button inside the player).

A4. If you are installing YouTube Vanced@inotia00 for the first time, there is a problem that preset settings are not applied.
Change "Settings > Vanced settings > Layout settings > Shorts button" to ON, refresh and restart. All settings will work normally.


Q5. An error occurs when downloading and installing YouTube Vanced@inotia00 from Vanced Manager.

A5. Try uninstalling Vanced Manager and reinstalling it.


Q6. Is it possible to update from official YouTube Vanced v17.03.38 to YouTube Vanced@inotia00 v17.2x.xx?

A6. Unfortunately, the official version of YouTube Vanced and the YouTube Vanced@inotia00 are not compatible.
To move from the official version of YouTube Vanced v17.03.38 to YouTube Vanced@inotia00, you must uninstall the previously installed official version of YouTube Vanced and install YouTube Vanced@inotia00.

This applies to YouTube Vanced@inotia00 as well as YouTube Music Vanced and Vanced Manager.

Q&A (Вопросы и Ответы) - RU


В1. Что это за проект?

О1. "Vanced Extended" - неофициальное продолжение развития проекта YouTube Vanced.

Разработка официального проекта YouTube Vanced была прекращена. Есть несколько проектов, использующих исходный код проекта YouTube Vanced. Среди них в данный момент наиболее известен "YouTube ReVanced".

"Vanced Extended" также является одним из таких проектов, нацеленным на добавление функций оригинального YouTube Vanced и своих собственных в последнюю официальную версию приложения YouTube.

Кроме того, этот проект разрабатывается не командой, а одним человеком - мною.
Поэтому цикл обновления этого проекта не является постоянным (обновления могут выходить быстро и стабильно, но также возможны и задержки).
Разработка данного проекта может быть прекращена в любое время из-за моих личных обстоятельств.


В2. Я активировал "Включить RYD (ALPHA)" в "Настройки Return YouTube Dislike". Почему счётчик дизлайков не работает?

О2. Вы увидите диалоговое окно «Вернуть счётчик дизлайков YouTube», которое появляется при первой установке приложения.
Возможно, вы заметите сообщение - "ВНИМАНИЕ: В настоящее время в ALPHA. Если YouTube API изменится, кнопка «дизлайков» может не появиться".
С учетом сказанного, начиная с YouTube версии 17.09.xx, API YouTube изменился.
Следовательно, в последней версии YouTube Vanced@inotia00 активация функции "Включить RYD (ALPHA)" не отображает количество дизлайков.
(Точнее, это связано с изменением контейнера кнопки на Litho)

Если вы активируете функцию "Cтарый интерфейс (Не рекомендую)" в "Настройки > Настройки Vanced > Настройки внешнего вида", приложение YouTube Vanced@inotia00 условно вернется к версии v17.08.35, и счётчик дизлайков будет работать нормально.

В настоящее время нет другого способа заставить работать счётчик дизлайков кроме этого метода, и поэтому в ИЗВЕСТНЫХ ПРОБЛЕМАХ указано, что "RYD (счётчик дизлайков) не работает".


В3. Можно ли запустить YouTube Vanced@inotia00 без установки MicroG в версии без ROOT?

О3. Начиная с YouTube версии 17.26.xx и более поздних, приложение было изменено, чтобы запускаться только после получения определённого токена от MicroG. Поскольку эти изменения на стороне исходного кода YouTube, для запуска приложения YouTube Vanced@inotia00 17.26.xx и более поздних версий требуется MicroG. Если вы всё таки хотите запустить версию YouTube Vanced@inotia00 без root и без MicroG, то установите YouTube Vanced@inotia00 версии 17.25.34.


В4. Некоторые настройки YouTube Vanced@inotia00 не применяются должным образом (например, внутри проигрывателя нет кнопки загрузки).

О4. Если вы устанавливаете YouTube Vanced@inotia00 в первый раз, то может возникнуть проблема, что предустановленные настройки не применяются.
Для решения этой проблемы необходимо зайти в "Настройки > Настройки Vanced > Настройки внешнего вида >, активировать переключатель кнопки "Shorts", обновить и перезапустить приложение . После чего все настройки будут работать нормально.


В5. Возникают ошибки при скачивании/установке YouTube Vanced@inotia00 из Vanced Manager.

О5. Попробуйте переустановить Vanced Manager, предварительно удалив предыдущую версию.


В6. Можно ли обновиться с официального YouTube Vanced v17.03.38 до YouTube Vanced@inotia00 v17.2x.xx?

О6. К сожалению, официальная версия YouTube Vanced и версия YouTube Vanced@inotia00 несовместимы.
Чтобы перейти с официальной версии YouTube Vanced v17.03.38 на YouTube Vanced@inotia00, вы должны удалить ранее установленную официальную версию YouTube Vanced и установить YouTube Vanced@inotia00.

Это относится к YouTube Vanced@inotia00, а также к YouTube Music Vanced и Vanced Manager.

From now on, I would like to provide additional guidance on the parts that have not been given to you separately.

The "Vanced Extended" channel, unlike the present, in the past was simply a channel for backing up the YouTube Vanced that I modified for my own use.
Those of you who have been on this channel for a long time will remember that in the past the channel was called "Vanced Mod Archives for me".

However, the channel became bigger than I had expected, and I found that this channel was quite lacking in several ways.

Many people made suggestions for the development of this channel,
I accepted the suggestions.

One of them is to open-source the Vanced Manager I modified.
Because the Original Vanced Manager is open source, I thought it was right to switch to open source the Vanced Manager I modified as well.

Currently, I am preparing to upload the modified Vanced Manager source code to github.
When I finish this preparation process, I will notify the participants of the channel once again.

Thank you to everyone who is interested in Vanced Extended 🥰

By chance, while checking logcat, I discovered that one important source was missing from the v17.27.35 version of vanced-integration.

Those who ran into issues with YouTube Vanced v17.27.35 were no coincidence 😅

I'm still working on linking Vanced Manager to github, so I can't edit YouTube Vanced right now.

I recommend that you temporarily use YouTube Vanced v17.26.34

Temporarily, I rolled back to download YouTube Vanced v17.26.34 from Vanced Manager.
In Vanced Manager, the latest version will be displayed as v17.26.34, not v17.27.35

If Vanced Manager still shows that the latest version is v17.27.35, try uninstalling and reinstalling Vanced Manager.

[UNOFFICIAL] Vanced Manager v2.6.3

Build Date: 220712
Status: Stable

Changelog
- The first version that migrated Custom Vanced Manager to GitHub
- Apply latest commit from TeamVanced/VancedManager
- Firebase Removed
- Update some strings
- Use the latest build tools
- App optimization
- Add Github Pages to Social Media
- Change versionCode (262 → 220712)

Description
- Support to download YouTube Vanced@inotia00
- Support to download YouTube Music Vanced@inotia00

[UNOFFICIAL] Vanced Manager Origin v2.6.3

Build Date: 220712
Status: Stable

App Name: Vanced Manager v2
Package Name: com.vanced.manager.origin

Changelog
- The first version that migrated Custom Vanced Manager to GitHub
- Apply latest commit from TeamVanced/VancedManager
- Firebase Removed
- Update some strings
- Use the latest build tools
- App optimization
- Add Github Pages to Social Media
- Change versionCode (262 → 220712)

Description
- Support to download YouTube Vanced@inotia00 with Original Icon & Name
- Support to download YouTube Music Vanced@inotia00 with Original Icon & Name
- Support to download Vanced Microg with Original Icon & Name

YouTube Vanced v17.27.xx seems to have a problem with RYD not working properly.

Looking at the code, I decided that it wasn't a problem I could fix right away.
I'm just guessing maybe the YouTube API has changed (or changed to litho)

Accordingly, I changed the status of v17.27.xx from Beta to WIP(Work In Progress)

Vanced Manager recognizes that the latest version of YouTube Vanced is v17.26.34(The next most stable version), but v17.27.xx is also available for download.

Vanced Manager api change notice

- (NON-ROOT) Fixed installation failure on armeabi_v7a architecture in YouTube Vanced v17.26.34.
- (ROOT) Added 74 language packs in YouTube Vanced v17.26.34. (Previously only 16 languages were supported)

The reason the old quality layout doesn't work anymore for some people after 17.26.xx is that Google is testing a different layout with some users.

As with the button container, it is a problem that occurs in the process of moving code to litho, and another patch is required to solve it.

This doesn't happen to everyone, and I'll treat it as a KNOWN ISSUE.

[UNOFFICIAL] Vanced Manager v2.6.3

Build Date: 220714
Status: Stable

Changelog
- Gradle update
- Fix the problem that VirusTotal detects Trojan when building with BuildType set to 'release'
- Change app signature

Description
- Support to download YouTube Vanced@inotia00
- Support to download YouTube Music Vanced@inotia00

※ For ROOT version, Original YouTube Icon and name are used

※ Since the app signature has been changed, you need to uninstall the previously installed Vanced Manager and then install the new Vanced Manager.

Edited: Rollback to previous signature scheme

[UNOFFICIAL] Vanced Manager Origin v2.6.3

Build Date: 220714
Status: Stable

App Name: Vanced Manager v2
Package Name: com.vanced.manager.origin

Changelog
- Gradle update
- Fix the problem that VirusTotal detects Trojan when building with BuildType set to 'release'
- Change app signature

Description
- Support to download YouTube Vanced@inotia00 with Original Icon & Name
- Support to download YouTube Music Vanced@inotia00 with Original Icon & Name
- Support to download Vanced Microg with Original Icon & Name

※ Since the app signature has been changed, you need to uninstall the previously installed Vanced Manager and then install the new Vanced Manager.

Edited: Rollback to previous signature

This signature is a signature issued through Android Studio. However, I do not know why the error persists despite applying the signature scheme v2.

Temporarily, I rolled back to previous signature.

To avoid confusion, I will delete my previous posts.