this post was submitted on 01 Apr 2024
27 points (96.6% liked)

Android

27883 readers
22 users here now

DROID DOES

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:

Rules


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:

!android@lemmy.ml


founded 1 year ago
MODERATORS
 

Any idea why? I've been using it for months. I probably had to grant permission when I first installed it, but haven't had to again since then, until just now.

Also, some of the time, when F-droid updates an app, the update just goes through. But other times I get a dialogue asking "do you want to update this app?". It seems random. Any idea?

Phone is a Moto G5 Stylus 2023 and it recently got a security update from Motorola, but I think I've done some F-droid updates since then. However, this may be related.

The other possibility is that something might have happened to F-droid's code signing credentials, e.g. someone messed with them? That thought is basically why I'm asking here.

top 6 comments
sorted by: hot top controversial new old
[–] TraubeNuss@discuss.tchncs.de 27 points 7 months ago (1 children)

I’m not an android dev nor am I affiliated with the f droid project so this might be wrong: As far as I know f droid started using an Android built in mechanism for updating. It has to request permissions to install and update apps at all and then it has to ask once for each individual app.

So you allow it to update apps and install X. Then once X gets an update you will be asked whether f droid is allowed to install ist. When the next update for X comes f droid will be silently allowed to install it.

As far as I understand it’s just how this kind of permission works on android.

[–] Pantherina@feddit.de 1 points 7 months ago

"Session Installer"

[–] lemmyreader@lemmy.ml 16 points 7 months ago

Maybe it has to do with the new feature https://f-droid.org/en/2024/02/01/twif.html

[–] justJanne@startrek.website 12 points 7 months ago

Fdroid only gained the ability to auto update apps a while ago, so that's why you got that prompt.

Also, if the permissions an app requests change, fdroid can't always auto-update it.

[–] shortwavesurfer@monero.town 6 points 7 months ago

You have to grant permission to update each app one single time and then after that it will no longer ask you to manually update that app anymore as it will just be able to do it. For apps that are very commonly updated you will see this once and then not again. Some apps are rarely updated and when everything else has been updated automatically you'll still get this one app that has not been and needs permission.

[–] j4k3@lemmy.world 2 points 7 months ago

Look at the notes about the update. It will say what permissions have been changed. It is provably just the base android permissions have changed by adding a feature that has altered what your previous permissions were set at