- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-19-2025 05:02 AM in
Galaxy S24- « Previous
-
- 1
- 2
- Next »
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-19-2025 05:59 AM in
Galaxy S24If the Members app feedback link is the only channel for reporting this, I’ll use it. But I expected a support conversation to engage with the actual details I raised, not deflect them.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-19-2025 06:03 AM in
Galaxy S24Because Samsung gallery is NOT Discord or any other platform and programmed by different developers. That's the answer. There is no universal search standard across apps and platforms. The other platforms may read the text on photos, but the Samsung Gallery does not. It only reads what's in the metadata/photo info.
-------------------------------------------------------------
Please mark any response that helped you as your solution.
-------------------------------------------------------------
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-19-2025 06:06 AM in
Galaxy S24So clearly, Samsung Gallery is indexing something beyond just metadata. Whether it’s OCR, AI tagging, or cached thumbnail analysis, it’s working for “ghost” and “PC”—but not for “joe,” even though the word “Joe” is clearly visible on the thumbnail of the Quick Share image.
This proves the search behavior is inconsistent. If visible text is indexed in some cases but ignored in others, that’s not a limitation of cross-platform standards. That’s a flaw in Samsung Gallery’s own indexing logic.
Also, the fact that Discord surfaces the image instantly while Gallery and Copilot bury it under July 14, 2024 shows that other apps are able to prioritize recent Quick Share media, regardless of metadata. So it’s not just about different developers—it’s about Samsung Gallery failing to apply the same indexing logic it already uses successfully in other cases.
I’m not asking for universal standards. I’m asking why Samsung Gallery’s own search behavior contradicts itself.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-19-2025 06:09 AM (Last edited 09-19-2025 06:10 AM ) in
Galaxy S24Whatever the search algorithm is in the Gallery, clearly it has a reference for "ghost" or "ghostrider" - perhaps one of the photos contains it in the title and it brings up similar images. It has no reference for "Joe". This would be a question for the developers, not here in a user forum. We don't know the answer to how Samsung does its programming, as we are not the programmers.
-------------------------------------------------------------
Please mark any response that helped you as your solution.
-------------------------------------------------------------
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-19-2025 06:28 AM in
Galaxy S24That’s why I brought the issue here—to get clarity from other users or support staff who might understand the behavior. What I’m reporting is not a vague complaint. It’s a reproducible inconsistency in Samsung Gallery’s search and indexing logic.
To be clear:
- The Ghost Rider image I tested has no metadata or filename containing the word “ghost.” The file is named images(14).jpg, and yet Gallery search still finds it when I type “ghost.”
- The Joe Rogan Quick Share image has the word “Joe” clearly visible on the thumbnail, but search fails to find it.
- Discord surfaces the image instantly in the share UI, while Gallery and Copilot bury it under July 14, 2024.
This proves that Samsung Gallery does index visible text in some cases, and that the search behavior is inconsistent. If OCR or AI tagging is applied selectively, that’s a bug. If Quick Share images are excluded from indexing, that’s a design flaw.
I’m not asking for speculation about how Samsung programs its apps. I’m documenting a specific failure in how Gallery handles search and surfacing—and I’ve already tried the official feedback route. If this forum isn’t the place for technical clarity, fine. But dismissing the issue doesn’t make it go away.
- « Previous
-
- 1
- 2
- Next »