We have a new MicroG

[ghost]

Deprecated

[oSumAtrIX]

ReVanced does not use MicroG.

[ghost]

And what use to login on non-root?

[oSumAtrIX]

YouTube is not ReVanced.

[oSumAtrIX]

Additionally, your repo does not contain any history from the original MicroG. One would have to go through the entire source files to be sure it is safe.

[ghost]

Additionally, your repo does not contain any history from the original MicroG. One would have to go through the entire source files to be sure it is safe.

Well...I'll re-push it tomorrow with a fork from Vanced.

[ghost]

Additionally, your repo does not contain any history from the original MicroG. One would have to go through the entire source files to be sure it is safe.

Done!

[nyxiereal]

When you would add support for other arcs? Then i night add support for uMicroG to my repo

[ghost]

Which arcs are you interested in?

[nyxiereal]

universal / nodpi

[ghost]

I created 2 branches on repo. Give it a look.

[ghost]

@xemulat Why don't make a release (like previous Vanced)? This will help to deprecate current (and bloated) Vanced MicroG.

[pascua28]

The ideal scenario would be to somehow get the necessary changes to MicroG by Vanced merged to MicroG upstream as this way people who use regular MicroG do not have to use Vanced MicroG. Forking the fork is making matters worse.

Unless you are talking about the root variant of ReVanced YouTube, this is just not possible. The reason is that the original MicroG uses com.google.android.gms as its package name, which means, it's meant as a Google Play Services replacement for custom ROMs that do not have Google Play Services. Therefore, it's not possible to install it on non-root users. That's why Vanced team renamed the package name, along with some of the methods from com.google.* to com.mgoogle.*. That way, non-root users will be able to install the modified MicroG and allow it to co-exist with Google Play Services
As for the Vanced YouTube app, it's not possible to install it using the same package name for non-root users, that's why we have to rename it to something like revanced.app.android.youtube. The resulting problem, however, of renaming the YouTube package name is that we are not allowed to use it alongside Google Play Services so it has to use a modified MicroG.
By using root variant, on the other hand, we can just replace the original YouTube app with the modified app while retaining the same package name, and so, Vanced MicroG is not needed anymore as it can use Google Play Services. But not everyone would want to root their phones

[oSumAtrIX]

The reason is that the original MicroG uses com.google.android.gms as its package name

I was referring to all mods which are not necessary such as removing code, making small changes to support devices by different vendors or fixing broken code by unsupported means. These are changes which branch off the development of MicroG and thus are out of the question to get merged. Necessary changes such as the renaming of the packages are certain patches you'd do on top of upstream along upstream, but small changes, if done properly, are ideally subject for a PR to upstream.

[pascua28]

The reason is that the original MicroG uses com.google.android.gms as its package name

I was referring to all mods which are not necessary such as removing code, making small changes to support devices by different vendors or fixing broken code by unsupported means. These are changes which branch off the development of MicroG and thus are out of the question to get merged.

If you have MicroG installed and working, that means you already have root. Vanced root variant will just work even without Vanced MicroG. It just needs Google Services, whether from vanilla MicroG or Google Play Services
For a non-root method, there's no other way to get vanilla MicroG and Vanced YouTube work other than to make a fork of MicroG

Necessary changes such as the renaming of the packages are certain patches you'd do on top of upstream along upstream, but small changes, if done properly, are ideally subject for a PR to upstream.

For a non-rooted device, renaming of packages is necessary. Let's say you have managed to rename the package and some methods to com.mgoogle.*, installed and got MicroG working, all other apps that use Google Services will not recognize MicroG anymore and won't have Google Services functionality which defeats the purpose of MicroG.

[oSumAtrIX]

Yes, either non-root + Vanced MicroG or root & (Vanced) MicroG. Still, bug fixes concern MicroG and are not just related to Vanced. So if you have to make changes to MicroG for Vanced which are applicable to MicroG you should PR it so it is available in upstream and you do not have to maintain it anymore. Only changes that concern Vanced now have to stay in sync with upstream.

[pascua28]

Yes, either non-root + Vanced MicroG or root & (Vanced) MicroG. Still, bug fixes concern MicroG and are not just related to Vanced. So if you have to make changes to MicroG for Vanced which are applicable to MicroG you should PR it so it is available in upstream and you do not have to maintain it anymore. Only changes that concern Vanced now have to stay in sync with upstream.

Yeah that would be good. It's why I also forked microG and added some minimal changes needed for Vanced so in the future, it would be easier for me to merge microG changes: https://github.com/pascua28/VancedGmsCore

[pascua28]

Vanced microG causes unusual battery drain on my device so I made my own personal build for Vanced. This is a work in progress and there are still services/components that I will remove in the future. Feel free to check it out here: https://github.com/pascua28/VancedMicroG

[pascua28]

I just decided to compile my own also because the git history of VancedMicroG is somewhat messy and I have some trust issues

[TheJeterLP]

I just decided to compile my own also because the git history of VancedMicroG is somewhat messy and I have some trust issues

Trust issues? What makes you get these?

[pascua28]

I just decided to compile my own also because the git history of VancedMicroG is somewhat messy and I have some trust issues

Trust issues? What makes you get these?

I don't know, lol

[TheJeterLP]

I just decided to compile my own also because the git history of VancedMicroG is somewhat messy and I have some trust issues

Trust issues? What makes you get these?

I don't know, lol

Err, okay I guess? Vanced MicroG is a fork of MicroG. So you can see all the changes they made. No trust issues here at all with them

[pascua28]

I just decided to compile my own also because the git history of VancedMicroG is somewhat messy and I have some trust issues

Trust issues? What makes you get these?

I don't know, lol

Err, okay I guess? Vanced MicroG is a fork of MicroG. So you can see all the changes they made. No trust issues here at all with them

As this is a personal project, I would prefer to keep a cleaner history so I could pull updates and build on my own