Checklist
Affected app version
1.13.1
Affected Android/Custom ROM version
Android 16/OxygenOS 16
Affected device model
Oneplus Nord 5
How did you install the app?
F-Droid / IzzyOnDroid
Steps to reproduce the bug
-
Have a very large photo collection on your phone (mine has 30 000 photos, 1200px wide webp pics, average file size maybe 90kB) somewhere where Fossify Gallery can access it (e.g. sdcard/Pictures/COLLECTION or sdcard/Pictures2/COLLECTION2), that have been divided to subfolder tree structure of hundreds of folders.
-
Open fossify gallery
-
Tap any visible folder to open it
Expected behavior
Folder opens
Actual behavior
Most of time there is no response to tap. Sometimes there is response with 5 sec delay, sometimes with over 20 sec delay. Sometimes but much more rarely it opens near instantly.
Screenshots/Screen recordings
No response
Additional information
I have replicated this behaviour with at least 2 different devices (Oneplus Nord 5, android 16 and Samsung Galaxy S21FE android 14).
I suspect reason being that devs have maybe? not thought about users having this large collections and have not optimized the UI with the thought that there could be so large amount of pics and possibly assume that whole UI (instead of just the visible portion) should be rendered to some degree before it can accept taps.
Nevertheless having minor versions of images of your whole photo collection on your phone is very useful if/whenever you feel sharing some memories from past.
Whatever is the case the app is currently pretty unusable for me as virtually any time I open it (unless I open an individual file from file manager app which I sometimes also do) it does not respond properly before a long delay.
A related issue could be that if I swipe down to refresh UI (sometimes I also do it half accidentally). It pretty much freezes the app as it starts the whole rendering process from scratch and seems to go through whole photo collection again. So also this feature should have some mechanism that taps / some sort of usage is already possible for viewable area before the whole thing is re-rendered again.
Checklist
Affected app version
1.13.1
Affected Android/Custom ROM version
Android 16/OxygenOS 16
Affected device model
Oneplus Nord 5
How did you install the app?
F-Droid / IzzyOnDroid
Steps to reproduce the bug
Have a very large photo collection on your phone (mine has 30 000 photos, 1200px wide webp pics, average file size maybe 90kB) somewhere where Fossify Gallery can access it (e.g. sdcard/Pictures/COLLECTION or sdcard/Pictures2/COLLECTION2), that have been divided to subfolder tree structure of hundreds of folders.
Open fossify gallery
Tap any visible folder to open it
Expected behavior
Folder opens
Actual behavior
Most of time there is no response to tap. Sometimes there is response with 5 sec delay, sometimes with over 20 sec delay. Sometimes but much more rarely it opens near instantly.
Screenshots/Screen recordings
No response
Additional information
I have replicated this behaviour with at least 2 different devices (Oneplus Nord 5, android 16 and Samsung Galaxy S21FE android 14).
I suspect reason being that devs have maybe? not thought about users having this large collections and have not optimized the UI with the thought that there could be so large amount of pics and possibly assume that whole UI (instead of just the visible portion) should be rendered to some degree before it can accept taps.
Nevertheless having minor versions of images of your whole photo collection on your phone is very useful if/whenever you feel sharing some memories from past.
Whatever is the case the app is currently pretty unusable for me as virtually any time I open it (unless I open an individual file from file manager app which I sometimes also do) it does not respond properly before a long delay.
A related issue could be that if I swipe down to refresh UI (sometimes I also do it half accidentally). It pretty much freezes the app as it starts the whole rendering process from scratch and seems to go through whole photo collection again. So also this feature should have some mechanism that taps / some sort of usage is already possible for viewable area before the whole thing is re-rendered again.