Fossify Gallery

SovereignCopper

This is sounding like a Microsoft Community forum. Instead of getting unrelated advice and "it works for me", you could just export a log via the Gallery's App Info and attach it to an issue at https://github.com/FossifyOrg/Gallery/issues.

mar

SovereignCopper

Cheers. I'll dig out my github creds and submit error log with description of what causes it.

Whatever is causing it doesn't seem likely to be permissions based, as it wouldn't work fine after a reboot before it keeps happeing.

mar

schweizer

Yeah I can rotate an image.

mar

type: crash
osVersion: google/husky/husky:16/BP3A.251105.015/2025112100:user/release-keys
package: com.android.gallery3d:40030, targetSdk 29
process: com.android.gallery3d
processUptime: 126 + 272 ms

java.lang.RuntimeException: An error occurred while executing doInBackground()
at android.os.AsyncTask$4.done(AsyncTask.java:417)
at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:434)
at java.util.concurrent.FutureTask.setException(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:322)
at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:307)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1154)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:652)
at java.lang.Thread.run(Thread.java:1365)
Caused by: java.lang.IllegalArgumentException: column '_data' does not exist. Available columns: []
at android.database.AbstractCursor.getColumnIndexOrThrow(AbstractCursor.java:372)
at android.database.CursorWrapper.getColumnIndexOrThrow(CursorWrapper.java:92)
at com.android.gallery3d.filtershow.cache.ImageLoader.getLocalPathFromUri(ImageLoader.java:90)
at com.android.gallery3d.filtershow.cache.ImageLoader.getExif(ImageLoader.java:565)
at com.android.gallery3d.filtershow.imageshow.PrimaryImage.loadBitmap(PrimaryImage.java:200)
at com.android.gallery3d.filtershow.FilterShowActivity$LoadBitmapTask.doInBackground(FilterShowActivity.java:803)
at com.android.gallery3d.filtershow.FilterShowActivity$LoadBitmapTask.doInBackground(FilterShowActivity.java:794)
at android.os.AsyncTask$3.call(AsyncTask.java:396)
at java.util.concurrent.FutureTask.run(FutureTask.java:317)
... 4 more

Dumdum

mar
package: com.android.gallery3d:40030, targetSdk 29

That's the default gallery, not Fossify.

mar

garliccheese

Same phone and same settings initially (and granting direct allow not scopes didn't help). I might bin the F-droid one and go grab the Github apk (although I doubt that will help, my version now is the same as yours).

mar

Novalissoide

I considered that, not got on anything to base it on other than gut feel, but it raised an eyebrow being near 400MB.

userofgos

Dumdum package: com.android.gallery3d:40030, targetSdk 29

That's the default gallery, not Fossify.

@mar did you by chance disable the default Gallery app or remove any permissions from it?

mar

Dumdum

I start in Fossify Gallery, and then select a photo to edit, but yeah, it's the editor that goes wrong and crashes.

mar

userofgos

I had messed with permissions previously (made a thread about it) but the defaults have been back a while - I just made the same as my other GOS Pixel. What's puzzling is the error is fine after a reboot, but then it occurs after a couple of successful edits, and then back to crashing.

Dumdum

mar
The point is that (as far as this log is telling us) you're using the default gallery to edit images, not Fossify's editor. Fossify has its own editing feature which isn't been used.

mar

I don't have my other Pixel available just now to double check permissions - but looking like a case of user error. I can't reproduce problem now after adding 'Camera' permissions to stock Gallery. The edit from Fossify gallery pic just opens editor and has worked every time so far (which hopefully continues).

Sorry to have wasted people's time, and thanks for all the help/useful suggestions!

Novalissoide

mar my permissions for stock gallery is the following;
Files, Music & audio, Photos & video, Notifications.
No scoping or limiting the reach for files.
'Modify system settings' -allowed.
Mostly I tend to disable this app, which is a system app and rarely do I disable these, but this is one of few exceptions. Reason is Adhd-mitigation in launcher visuals, only one Gallery icon.

mar

Novalissoide

I don't blame you for this, and I don't think you need Adhd for it to be bothersome. I use a different launcher than stock (YAM I found to be the best for my preferences) and can see how it would be annoying having 'Gallery' twice in default GOS launcher (if you can't change it - although I don't know about that, as I don't use it). As YAM is a minimalist text launcher, I can at least just rename the Gallery entries in the app draw/home screen.

mar

Dumdum
Yeah I get that - and I could have worded the opening post better. But the Fossify Gallery was a factor in the problem, as I could not make the GOS editor crash on its own when using the GOS gallery - it would only happen when attempting to edit photos from Fossify gallery. I have it set up as Fossify as my gallery, but GOS editor to edit photos, because I prefer the default GOS editor, as like the quick 'punch' option that improves most photos, and not having to create a new edited file with Fossify editor (creating duplicates that creates a mess) or having extra click to 'overwrite'. Problem solved now anyway.

Novalissoide

mar I don't think you need Adhd for it to be bothersome

Correct, and with ADHD, 'bothersome' gets biologically weaponised into 'ruining most things you strive to get done'. 🧘

Novalissoide

mar I just saw todays Fossify Gallery update to version 1.9.1, mentions a bugfix done about crashing when using editor.

mar

Novalissoide
Thanks. That update worked. I put permissions back to how they were in GOS gallery and now editing images with GOS editor from Fossify gallery no longer crashes GOS editor.

« Previous Page Next Page »