The difference might be that Playstore is not automatically RUNNING on my device and I never have installed TCAnd from Playstore to begin with, only from the direct download-page.īut to completely remove Playstore from my device I would need to have that device rooted, at least that is the information I've got from experts.Īs far as the "Google requirement you cannot change" is concerned - what authority does Google have to enforce that? As I understand that this would only be true for a TCAnd-version that is distributed via Google in some way. I don't know, until now I CAN install updated TCAnd-apks (like all other apks) from within TCAnd - while I have Playstore installed from the get-go as usual. Ghisler(Author) wrote: ↑, 09:00 UTCThis is a Google requirement, not something I can change. Is, for example, x-plore file-manager affected by this latest "hostile-takeover-assault" by Google in the same way?Īnyhow - if such sinister Google activity to further deprive Android-users of their proprietary devices and their unrestricted usage is on its march - then I would strongly second the above proposal for such an unrestricted "freedom-version" of TCAnd, even if payed like the PC-version, which could be distributed via ghisler.ch and would need to be completely independent from those Playstore-vultures. Having that said and described my usual MO it is kind of unacceptable for me to no longer being able to install apks directly by calling them from within TCAnd. And of course it is TCAnd (what else?) from which I then load them to an Apk-folder on each device-associated SD-card and install from there via TCAnd. So only after inspection for a possibly wrong version-number and the like I will transfer that apk to my WiFi-NAS and from there transfer it further to the Android-devices that are supposed to run them. Even a quick look into the apk with the wdx-content-plugin (which is not available on Android) would usually give them away as fraud. My experience is that fake-apks do not bother to mask the fraud at all. There I also have the tools to inspect that apk first and look into it. I usually download apks not from an android-device at all but would rather download them to a PC first. I usually refuse to use google-Playstore - for good reasons as it turns out. Well, then this does sound like a severe setback to me that I've been unaware of so far. The only difference is how you install the apk: Instead of clicking on the apk in Total Commander, you need to download it with a browser and then install it directly from that browser. In summary, there shouldn't be any need to release a separate version without these restrictions. Again this will not affect devices without the play store like Huawei or custom ROMs. There is a clause that apps from the play store are not allowed to update themselves via any other ways than the play store. The internal apk installer will refuse to install an apk of Total Commander itself (class ) when the play store is installed on the same system. The help file viewer opens links to and other sites also in an external browserĤ. The internal browser will refuse to download apk files when the play store is installed on the same system. It only used the internal (help file) browser when there was no other browser installed, so this change is irrelevant for most usersĢ. It will now always open an external browser to download plugins. 3.31 introduces the following limitations, otherwise it would have been removed from Google Play:ġ.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |