solution: need f-droid version of play protect they could raise so much money for lawsuit to force G to allow it to be swapped in
F-Droid version of KDEConnect uninstalled by PlayProtect
161–170 of 192 posts
Re: F-Droid version of KDEConnect uninstalled by PlayProtect
#162Earlier quoted context omitted.
My phone forces me to reject "Play Protect" every single time I want to install an app. If I have to explicitly reject it more than once, it is obviously malware. Once is already arguable.
The constant nagging when you tell Google "no" shows how little respect they have for their users. Messages by Google, which is primarily an SMS app, is asking me every 1-2 weeks to enable RCS chats. The link for declining the request is small and easy to miss, while the AGREE button below it takes up 25% of the area of the popup. Dear Google UX designers, the way you present your little "decline" links is illegal in…
If there is one thing like about EU, is that it's the only one in the world standing for the user's rights keeping these companies with their antitrust pratices in check.
If it weren't for them @pple wouldn't have switched to USB-C
Re: F-Droid version of KDEConnect uninstalled by PlayProtect
#163Earlier quoted context omitted.
"I mean it's only the keys to your whole life, no big." It's a telephone, with a computer on it in your pocket with a shit load of sensors. The computer part involves components from many parts of the world, with many opaque subsystems. The OS is sort of Linux with knobs on and a lot of opaque parts - the first layer "belongs" to a prolific ad slinger hell bent on knowing everything about you. Then if it isn't a Goog…
The fact that other things like the carrier are bad, does not somehow make any other thing like graphene good. (not that it's bad exactly just that there is a problem, which is not no problem, even if it's a problem you personally have just decided to be ok with) Someone else said that the head guy isn't the head guy any more so the biggest problem may not be a problem any more. The idea, stated ideal, design, & cons…
Don't trust. Verify.
Re: F-Droid version of KDEConnect uninstalled by PlayProtect
#164Happened to me, I had to disable Play Protect scanning... interestingly, in ghe deacription in Android settings, it claims Play Protect will scan and WARN, not remove, apps. That is clearly a lie.
My phone forces me to reject "Play Protect" every single time I want to install an app. If I have to explicitly reject it more than once, it is obviously malware. Once is already arguable.
There's a timer that re-enables the Play Protect nag after a certain period of time. I can't remember how many days it is.
You can permanently disable it by running the following over ADB or a local shell. Works for me.
# This should disable Play Protect. Maybe.
# https://android.stackexchange.com/questions/187097/is-there-a-way-to-control-use-google-play-protect-together-with-microg-open-sou
settings put global package_verifier_enable 0
settings put global package_verifier_user_consent -1
settings put secure package_verifier_user_consent -1
settings put global upload_apk_enable 0
settings put global PACKAGE_VERIFIER_SETTING_VISIBLE 1
settings put global PACKAGE_VERIFIER_INCLUDE_ADB 0Re: F-Droid version of KDEConnect uninstalled by PlayProtect
#165One way to be a little less constantly violated by your phone is to run GrapheneOS, instead of iOS or ordinary Android: https://grapheneos.org/
Sadly device attestation has all but destroyed installing other OS. I couldn't use government or banking apps back in my old phone with LineageOS.
Today, I consider the inability to use government or banking apps on a device that travels in my pocket a feature, not a bug, but it was indeed a steep and sometimes unpleasant learning curve.
Re: F-Droid version of KDEConnect uninstalled by PlayProtect
#166Earlier quoted context omitted.
No it isn't, as unlike the others, grapheneOS is actually usable and dailyable.
I doubt grapheneOS requires much less effort to daily drive than others. Sent from my Librem 5.
Re: F-Droid version of KDEConnect uninstalled by PlayProtect
#167Earlier quoted context omitted.
No it isn't, as unlike the others, grapheneOS is actually usable and dailyable.
I doubt grapheneOS requires much less effort to daily drive than others. Sent from my Librem 5.
Re: F-Droid version of KDEConnect uninstalled by PlayProtect
#168Earlier quoted context omitted.
The fact that other things like the carrier are bad, does not somehow make any other thing like graphene good. (not that it's bad exactly just that there is a problem, which is not no problem, even if it's a problem you personally have just decided to be ok with) Someone else said that the head guy isn't the head guy any more so the biggest problem may not be a problem any more. The idea, stated ideal, design, & cons…
Last I checked, GrapheneOS is open source. Don't trust. Verify.
Even if there were something special about graphene that made it more desirable, the real way to deal with an open source project with something unacceptable about it's production or management, is to fork it. But I already have something else to do all day, and am happy to run lineage or calyx or or others. If I did need a fork, I'd need someone else to do it, and I'd have to trust them.
Fork it or help someone else who is forking it or work towards changing the original (which is what seems to have happened actually, so this is all a bit academic now), or just use anything else, are all more reasonable responses than "the people producing this thing with access to all my communications have shown themselves to be off the rails, so what I'll do is keep using it, but personally read all the code in an entire android os."
Re: F-Droid version of KDEConnect uninstalled by PlayProtect
#169Earlier quoted context omitted.
> This is precisely one of the perks of rooting. Rather, it's a benefit of an unlocked bootloader; you can root a device with a locked bootloader, and you can use an unlocked bootloader to install an unrooted OS (or, for that matter, you can unlock the bootloader without rooting, depending on the device). > Unless you mean as a right, without needing to root? I'd disagree (from a corporate/warranty perspective), but…
> otherwise there's no reason for modifying software to affect a warranty on hardware. I think you bring up a really good point. Except for extreme cases, such as a software that is designed to be self destructive on the physical components in which it resides, the hardware should mostly be unaffected by the software. Mostly that some components get used more or less than they were before, changing efficiency of some…