No You don't get to touch those
Right?
That's like asking the fuckin' cops for shrooms.
Google Play already does this, though. Well, it used to, but now it's throwing errors when I try to update apps.
I think this just changes the installer package stored by the package manager API so they can skip a permission prompt somewhere. Without that, you'd need to hit "OK" for every update you receive, like on older alternative app stores that don't have the Android 12 API enabled yet (F-Droid, for instance).
Unless Google is willing to risk a DMA fine, other app stores should be able to do the same.
i do not trust this at all. just let me disable it.
Just don't update the app from Play Store, it's not automatic, you have to chose to change its source to the Play store
how about no
On the app listing, you’ll also see a new “Update from Play” button that will switch the update ownership from the original source to the Play Store.
It's not automatic, you have to chose to update the side loaded app from Play store, if available.
I nixed the Play store and its related gpservices. Google doesn't own my phone, and they can stay the hell away from from my ~~sideloaded~~ manually installed apps.
Really wish there was a real third OS choice. Hilarious that Apple (by force) is having to open up their platform to third-party stores. Meanwhile Google is continuing their enshittification of the entire platform full steam ahead. At this point, Samsung, bring back Tizen, or....someone do anything.
I really wonder how this is going to work, there are odd scenarios like the offline Wiki app Kiwix. If you install it from the Play Store, it can't see your filesystem and you can only download wiki images in the app itself and they live in the container directory with their own user:group assigned by the app. (One is also not even allowed to modify the user:group on files even via ADB anymore without root, so copying a sideload into the app container directory still won't work, as the app won't "see" it.)
If you sideload from the Kiwix web site, the app is then allowed to have access to what remnants of the filesystem apps are still allowed to see, and you can just copy the 100GB wiki file to your phone over USB and access it in the app.
If the app is then updated in the Play Store, will it inherit the neutered permissions of the Play Store variant and suddenly not see your wiki images?
Did you not see the news about Autoblocker being enabled by default on Oneui 6.1.1 blocking sideloading of apk files by default.
Only on new phones that ship with 6.1.1, so your existing phone won't change this setting with the update. There's also a page during the OOBE setup with a toggle for this block where you can simply tap to disable it before proceeding.
But, the precedent is there. Samsung is not pro sideloading or custom ROMs. In fact tizenOS was more locked down than android.
Can we allow unintended installation for third party AppStore’s like fdroid and aurora tho
If you mean unattended, they already do since Android 12.
Apps do need to implement the functionality manually, but it seems pretty simple.
Looks like Aurora already has, it just updated Discord for me while my phone was off.
It's already a feature since android 12 like the other user said. Try droidify if fdroid doesn't do background updates for you.
I think it's already available. I was able to update a sideloaded app via the play store just the other day. (Blackmagic camera, since officially the play store says it's incompatible with my device. It wouldn't let me install it, but it was happy to update it.)
Is this an effect of Epic winning that lawsuit against Google and wanting them to provide access from third-party app stores? Or is just typical Google fuckery?
Welcome to the droidymcdroidface-iest, Lemmyest (Lemmiest), test, bestest, phoniest, pluckiest, snarkiest, and spiciest Android community on Lemmy (Do not respond)! Here you can participate in amazing discussions and events relating to all things Android.
The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:
1. All posts must be relevant to Android devices/operating system.
2. Posts cannot be illegal or NSFW material.
3. No spam, self promotion, or upvote farming. Sources engaging in these behavior will be added to the Blacklist.
4. Non-whitelisted bots will be banned.
5. Engage respectfully: Harassment, flamebaiting, bad faith engagement, or agenda posting will result in your posts being removed. Excessive violations will result in temporary or permanent ban, depending on severity.
6. Memes are not allowed to be posts, but are allowed in the comments.
7. Posts from clickbait sources are heavily discouraged. Please de-clickbait titles if it needs to be submitted.
8. Submission statements of any length composed of your own thoughts inside the post text field are mandatory for any microblog posts, and are optional but recommended for article/image/video posts.
Community Resources:
We are Android girls*,
In our Lemmy.world.
The back is plastic,
It's fantastic.
*Well, not just girls: people of all gender identities are welcomed here.
Our Partner Communities: