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:
Hiya, I'm trying to install KDE Initiary as I'll be travelling soon. Heard this was a good travel planner on the Late Night Linux Podcast, however when I try to install the app I get the message as seen in the picture. Anyone got any idea of how I could this to work?
Edit:I am on GrapheneOS, but have tried to give Fdroid all permissions, but doesn't change anything.
Thanks ๐
I tried downloading it from Droid-ify, however when downloading it from F-Droid directly it worked straight away haha, so guess problem sovled..
I've had similar problems with kde apps on fdroid. I think they are rebuilding very often and that somehow gives a decent chance they are chaning the file you are downloading. So the store is correctly identifying the apk is not matching the info of the repo, because the repo is outdated compared to the file.
I suspect droidify had outdated repo info while fdroid did not. A refresh would have probably made it work on droidify too.