Split of microG core

hi,

i want to stop google from running privileged code on my device. however, i'm ok with running google code if sandboxed. in fact, i need to. i can't have a phone that cannot run hangouts for instance, because i need voip support to be able to work. (i've talked about sandboxed google before: https://github.com/microg/android_packages_apps_GmsCore/issues/253 )

i've posted on the hangouts issue (which looks simple enough, apparently a missing SSL provider), but the microG project does not seem to be prioritizing this: https://github.com/microg/android_packages_apps_GmsCore/issues/72

microG reimplements the google account. but in my view, the google account can be considered part of the google client apps that i am willing to run (as long as they are sandboxed). if i am using google client apps (gmail, hangouts, etc) i might as well also use google's implementation of their account. in fact, issues with microG's version of the google account might crop up later with client app updates, and using google's code instead is probably safer in this regard.

but for many reasons, microG is doing the right thing in reimplementing the google account; i won't argue this. my position is that not everybody using microG is interested in this functionality.

because of the hangouts issue, that has been open for a year without progress, i'll have to abandon microG unfortunately.

fortunately, google's own account manager seems to work with just one privileged permission. see:
http://kindlefireforkid.com/how-to-setup-a-google-account-on-amazon-fire-tablet/

i'd like to install google's account manager, at least for the time being, side by side with microG replacing other google services. but unfortunately i think this is not possible because microG and its implementation of the google account is monolithic, and i suspect both account managers can't coexist in the same device.

is this suspicion true?

i'd suggest breaking app microG core in two apps to separate the account manager and handle this issue. this would also add the benefit of not installing a google account manager (even if free software) for those who don't want any google service.

No files, tests, or entry points are named. Start by reviewing the GmsCore app structure and its existing account-manager implementation to assess whether the components can be separated and coexist with Google's manager. Done would require a maintainer-approved design and a clearly scoped split, rather than a small standalone edit.