I really like what you got there. That servicemenu looks very useful. I’ll have to look into those, thank you for all that, I really appreciate it!
What I’m doing now is using exiftool to strip the orientation data, and that seems to do the trick. But I have to run it before anything else (opening and saving), because if I strip the orientation data while the image is incorrectly oriented after opening and saving, it will just stay that way — broken.
Attached below is a ‘broken’ file, the thumbnail is not in the same orientation as the image: The properties menu says, "Image Orientation: 180° rotated (as does exiftool). The image when you open it is indeed upside down, but the thumbnail is rotated 90° CW in Dolphin only and not in Gwenview.
Maybe you can take a look and see how it works on your system.
But yeah, just running exiftool to remove orientation data works, provided I run the command before doing anything else.
I would rather not strip everything from EXIF.
BTW, exiftool keeps or writes an original copy but without the original file extension, for the .jpg, it uses .jpq_original.
I was having trouble with exiftool, besides: Only the 1 and 8 values worked for the image so I couldn’t really do anything useful — especially because neither of those values executed correctly. For example, the command below rotates the image 180, and rewrites the EXIF field accordingly — but it wasn’t supposed to do that:
exiftool -Orientation=1 20250112_002150_original.v1.jpg
Below is the FUBAR file that I was working with (shown here upside down), and I can’t UNFUBAR it because only 1 and 6 work on exiftool, etc. Honestly, I just laugh. It’s just so weird. And this only happens with photos taken using the Samsung Pro mode. And a Samsung “Memories” video I just uploaded, OMG. Maybe I should get with Samsung lol
