XPost: comp.mobile.android, alt.privacy
From: ehj46PkBWfBAng9C@VW28LtWn6wknpUMV.invalid
Erholt Rhein writes:
> On Wed, 02 Nov 2022 17:54:06 +0800, 5GyYap52yQ1UGMWD wrote:
>
>>> Why would an app REQUIRE Google Play Store spyware to be running?
>>
>> Because most apps use Google Firebase for the analytics and push
>> notifications and because of that almost all Play Store apps require the
>> "Play Store Services" as a soft dependency. You can technically run
>> those apps without the "Play Store Services" but you will have a
>> neutered experience.
>
> You need to be very clear whether you're talking Google Play Store or
> Google Play Services because they're completely different on Android.
>
Oh yeah. I was just going with what I remembered at that moment. Yes,
I'm referring to the Google Play Services app.
> Specifically I disabled & forcestopped only the Google Play Store module
> and not the Google Play Services module for the test initially described.
>
This wouldn't do anything significant since the whole thing relies on
the "Services" app anyway.
> Checking again, this is the initial test condition:
> ENABLED/RUNNING Google Play Services 22.42.12
> DISABLED/FORCESTOPPED Google Play Store 32.9.14-21
>
> In checking my tests I forgot to mention in the original post that a reboot
> is required even if the app was both disabled and forcestopped in Android.
>
> Apparently pressing "Force stop" doesn't do what anyone would think it does
> since a reboot is required as can be shown when I tested your suggestion.
>
> Based on your suggestion, I tested this reverse scenario:
> DISABLED/FORCESTOPPED Google Play Services 22.42.12
> ENABLED/RUNNING Google Play Store 32.9.14-21
>
> In that test, the app still worked but that's when I realized things are
> DIFFERENT once you reboot after disabling and force stopping programs.
>
> Even turning off both and testing, the app still worked!
> DISABLED/FORCESTOPPED Google Play Services 22.42.12
> DISABLED/FORCESTOPPED Google Play Store 32.9.14-21
>
> Yet rebooting after the test condition above, the app crashed as before.
>
> Unfortunately, too many other errors resulted from Google Play Services
> disabled/forcestopped/rebooted as shown by notifictions after reboot.
> ERROR https://i.postimg.cc/qvMpkZrg/Clipboard01.jpg
> Enable Google Play Services
> [Name-of-app] won't work unless you enable Google Play Services
>
Yes, that's the issue. A lot of apps from the Play Store requires the
"Services" app to be even functional.
> If someone else can confirm the following, that would help all.
> (1) Install the app and make sure it pops up when tapped
> (2) Disable & force stop Google Play Store in Android settings
> (3) Reboot (this is the part I had forgotten I had done many times)
> (4) Try to run the app
>
> In my case, the app crashes if Google Play Store is not running.
> If that happens for others, the important question to ask is why.
As I said, it's because they're using Google's own push notifications
and analytics system. A lot of app developers don't really care that
much about user privacy and would rather use a proprietary
implementation that's easy to include in their project.
The only way out of it is to either use F-Droid apps which doesn't not
rely on Google's Firebase code or use a "Play Services Emulator" like
microG. The latter, however, requires you to fully wipe and reinstall
your phone's system ROM. That might not be possible depending on the
phone that you are currently using.
--
Pointless meanderings in a bleak and lonely world.
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)
|
