Bug 453350

Summary:	Part of exif tags are being deleted when copying photo's from Android to pc
Product:	[Applications] kdeconnect	Reporter:	dutchkind
Component:	android-application	Assignee:	Albert Vaca Cintora <albertvaka>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	cwo.kde, jgdlyst
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Other
OS:	Android 11.x
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description dutchkind 2022-05-03 16:35:10 UTC

SUMMARY
When I copy photo's from my phone to my pc with kdeconnect the geolocation tags are deleted somehow. When however I copy from pc to phone the geolocation tags are kept intact. I think it is preferable to always keep the full exif information intact.


STEPS TO REPRODUCE
1. Send photo's from android to pc with kdeconnect
2. 
3. 

OBSERVED RESULT
All tags containing latitude, longitude and altitude have disappeared

EXPECTED RESULT
Photo's should be copied without any modification

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
Operating System: openSUSE Tumbleweed 20220501
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.93.0
Qt Version: 5.15.2

Android 11
kdeconnect 1.19.1

ADDITIONAL INFORMATION

Comment 1 jan etc 2022-09-20 19:02:38 UTC

Transferred a bunch of images with kdeconnect

Android 12 (on OPPO Find X3 Lite) kdeconnect 1.19.1

Steps to reproduce:

1. Take an image and make sure that location data is in it directly on the device
2. Transfer image 
3. Examine exif data in an appropriate PC app (commandline : exiftool, Gwenview, Digikam or the like)
4. Check location data : Location data wiped / set to zero in my case
5. Transfer same image via USB
6. Repeat step 4 : location data present

After a bit research, i stumbled upon
https://developer.android.com/training/data-storage/shared/media#media-location-permission

Comment 2 cwo 2024-08-08 18:19:21 UTC

Thank you for the bug report! This issue has already been filed; please follow the linked bug report for updates on a fix.

*** This bug has been marked as a duplicate of bug 421613 ***