No, it's fraud. But you can change to any name you want and it will work. Some people do it with Lucky Patcher (I've not tested). Also, you can build the app, with a different name, from sources.
ok 1 i can confirm that even ver 7.0.1614134 work as well. ..........but no any version can play unless u do the followed sequences.
I need to say that i tryed all possible options with manny attempts , and as Charlie said i did it only when i've deleted usable data in AA aplications ,ok 1 i can confirm that even ver 7.0.1614134 work as well. ..........but no any version can play unless u do the followed sequences.
1. it s very important to delete all useabe data in AA. after that. deinstal AA
2.Install fermata auto 1.8.7 with king instaler . After that start fermata it will asking for update ...press only once it will install control at first . exit app.start again it will ask again for upgrade to vers 1.8.9 ...cancell that and disable autoupdate Fermata auto in settings.
3 install AA vers for your moby, for me 7.0.1 working fine and in play store disable autoupdate app .
Fermata working fine , ive made some mistake with fermata control because it cant be good FA 1.8.7 and FC1.8.9 ....but who cares? its working . Well Andrej that means that AA, google inc ,didnt disable app in servers using names.
You are on the right track, mate.Hi guys!
Doing more tests... it seemed that only working with shared_prefs eventually did not work. I made further changes and so far (~ 3 days and multiple force closes/reboots) everything still working fine.
1. I noticed some files being created under phenotype/shared dir. This one specifically, com.google.android.libraries.consentverifier#com.google.android.projection.gearhead.pb, is not present right after clear data but gets downloaded later on.
I emptied it with "echo "" > com.google.android.libraries.consentverifier#com.google.android.projection.gearhead.pb" - if it does not exist you can use touch to create an empty file - and also changed ownership of the entire shared/ dir to root and set permissions to 400 (only root user can read them). So far everything working.
I also saw that on the shared_prefs when I made them read only AA created new files. Maybe we can let them with default permissions and settings can be changed - I left them since I set it up the way I like it and don't think will need to change anything later.
My AA release is 7.5.121304, a beta from APKmirror.
Commands to test, right after clear data:
chown -R root:root /data/data/com.google.android.projection.gearhead/files/phenotype/shared touch /data/data/com.google.android.projection.gearhead/files/phenotype/shared/com.google.android.libraries.consentverifier#com.google.android.projection.gearhead.pb chmod -R 400 /data/data/com.google.android.projection.gearhead/files/phenotype/shared/* chmod 600 /data/data/com.google.android.projection.gearhead/files/phenotype/shared
Let me know how it goes for you, I think I might be on the right track here!
Sounds really nice!I wanted to change the applications order and add some speed dial entries so I reversed the ownership and permissions of the shared_prefs dir, maintaining the changes to phenotype/shared.
So far everything still working fine! Maybe only the phenotype changes are required.
Seems like that Package renaming works, but I don't think it's a good solution. Google has many ways to block any app.