51
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 18 Oct 2024
51 points (94.7% liked)
Android
28005 readers
48 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:
founded 1 year ago
MODERATORS
This only because fossify hangs on my photos anymore. Black thumbnails, etc. I've cleared both cache and storage then uninstalled and reinstalled. No difference.
Shame otherwise I like fossify better.
Update it from the github. They released some bug in the version in the repos, and the fix hadn't yet made it there yet. At least that was the case a couple weeks ago. Updating from github fixed that problem for me immediately.
Thanks. I'll add it to obtanium and give it a go.
I'm on 1.2.1. Turns out F-Droid has this version as of 9/28.
This does appear to fix it. Thanks!