I have a REALLY bad issue with my #fairphone and it's #opencamera fork: It can't seem to store GPS data in a way that it is readable outside the phoone.
-
I have a REALLY weird issue with my #fairphone running #e_os and it's #opencamera fork: It can't seem to store GPS data in a way that it is readable outside the phoone. #Fossify gallery know the location, but if I share a photo to my laptop, the gps information has vanished.
I share using kdeconnect or Nextcloud => no location data.
If I browse using kdeconnect from my laptop (using sshfs), location data is there.
I can't find out where and why this happens, or how to fix it.
-
I have a REALLY weird issue with my #fairphone running #e_os and it's #opencamera fork: It can't seem to store GPS data in a way that it is readable outside the phoone. #Fossify gallery know the location, but if I share a photo to my laptop, the gps information has vanished.
I share using kdeconnect or Nextcloud => no location data.
If I browse using kdeconnect from my laptop (using sshfs), location data is there.
I can't find out where and why this happens, or how to fix it.
@anderslund does the app you are sharing with have location premissions? Some android builds strips gps coordinates if the photo is used by a app without location permissions.
-
@anderslund does the app you are sharing with have location premissions? Some android builds strips gps coordinates if the photo is used by a app without location permissions.
@mshdk Good idea. I tested, but it did not work.
I gave Kde connect location permission, Fossify Gallery does not ask for that. But sharing with comaps on the phone works fine (that has location permission).
Thanks for answering
-
I have a REALLY weird issue with my #fairphone running #e_os and it's #opencamera fork: It can't seem to store GPS data in a way that it is readable outside the phoone. #Fossify gallery know the location, but if I share a photo to my laptop, the gps information has vanished.
I share using kdeconnect or Nextcloud => no location data.
If I browse using kdeconnect from my laptop (using sshfs), location data is there.
I can't find out where and why this happens, or how to fix it.
I got a reply from the #e_os community: https://community.e.foundation/t/exif-gps-data-stripped-during-share/76155/3
Appearently, both the @kde connect, the @panoramax app and the @nextcloud android app needs the ACCESS_MEDIA_LOCATION android permission.
Kinda weird they do no have that, as sharing media is key functionality in all of them.
-
I have a REALLY weird issue with my #fairphone running #e_os and it's #opencamera fork: It can't seem to store GPS data in a way that it is readable outside the phoone. #Fossify gallery know the location, but if I share a photo to my laptop, the gps information has vanished.
I share using kdeconnect or Nextcloud => no location data.
If I browse using kdeconnect from my laptop (using sshfs), location data is there.
I can't find out where and why this happens, or how to fix it.
Having ACCESS_MEDIA_LOCATION permission is not enough. Some of those apps has it, and it still does not work.
-
I have a REALLY weird issue with my #fairphone running #e_os and it's #opencamera fork: It can't seem to store GPS data in a way that it is readable outside the phoone. #Fossify gallery know the location, but if I share a photo to my laptop, the gps information has vanished.
I share using kdeconnect or Nextcloud => no location data.
If I browse using kdeconnect from my laptop (using sshfs), location data is there.
I can't find out where and why this happens, or how to fix it.
So, after fighting this:
#Nextcloud works, if you allow 'image anc videos' permission. It fails to ask/warn if not allowed.
I filed a bug for #kdeconnect to add that permission
The #panoramax android app does not work anyways, I haven't been able to make it upload an image. Taking photos with it is not good, you can't see what you do, at least for me, that is not in a usable state.
