You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 6, 2019. It is now read-only.
Steps to reproduce:
set up a "spoof" google ID through xprivacy
Deny com.google.android.providers.gsf.permission.READ_G SERVICES to both Google Play and Google Service Framework
Purge data of Google play AND google play service.
Result:
Google play can no longer connect.
However, it can connect again if com.google.android.providers.gsf.permission.READ_G SERVICES is re-enabled for google play.
linked:
logcats with debug enabled in xprivacy
good.txt - the one where google play connects (com.google.android.providers.gsf.permission.READ_G SERVICES is allowed)
here: https://infotomb.com/aigia.txt
bad.txt - the one where it fails ( com.google.android.providers.gsf.permission.READ_G SERVICES is denied)
if I chose "randomize at startup" for Google Play, Google Services Framework, and "Global", then purge google play and google play service data, and after that finally reboot, the issue does not arise (but my country gets also randomized which is not something I want :( )
Platform:
Android 4.1
Steps to reproduce:
set up a "spoof" google ID through xprivacy
Deny com.google.android.providers.gsf.permission.READ_G SERVICES to both Google Play and Google Service Framework
Purge data of Google play AND google play service.
Result:
Google play can no longer connect.
However, it can connect again if com.google.android.providers.gsf.permission.READ_G SERVICES is re-enabled for google play.
linked:
logcats with debug enabled in xprivacy
good.txt - the one where google play connects (com.google.android.providers.gsf.permission.READ_G SERVICES is allowed)
here:
https://infotomb.com/aigia.txt
bad.txt - the one where it fails ( com.google.android.providers.gsf.permission.READ_G SERVICES is denied)
here:
https://infotomb.com/w2t22.txt
I can upload full Xprivacy databases for both cases, so that reproducing the issue will be easier.
The text was updated successfully, but these errors were encountered: