I am raising this to high as Android devices are increasingly common and many replace hand-held cameras now. This problem essentially makes Shotwell import (and others depending on gphoto, I presume) unusable for practical purposes. Shotwell being a core application and given Android devices increasing penetration, this issue will only affect an increasing number of users.
Although there is a proposed fix in Android's code, it won't make it in a practical timeframe (or at all) for most Android phones/devices users (unless perhaps those using CyanogenMod or other modified code). Perhaps Shotwell could implement a configurable preference to only scan certain directories and exclude Thumbnails. I'll comment on that upstream @Shotwell.
It seems this is a gphoto bug + Android DCIM spec implementation being wrong, if I read upstream's report comments right.
Upstream @gphoto: sourceforge. net/tracker/ ?func=detail& aid=3000202& group_id= 8874&atid= 108874
http://
Android issue 2960: Camera / DCIM compliance problem: code.google. com/p/android/ issues/ detail? id=2960
http://
I am raising this to high as Android devices are increasingly common and many replace hand-held cameras now. This problem essentially makes Shotwell import (and others depending on gphoto, I presume) unusable for practical purposes. Shotwell being a core application and given Android devices increasing penetration, this issue will only affect an increasing number of users.
Although there is a proposed fix in Android's code, it won't make it in a practical timeframe (or at all) for most Android phones/devices users (unless perhaps those using CyanogenMod or other modified code). Perhaps Shotwell could implement a configurable preference to only scan certain directories and exclude Thumbnails. I'll comment on that upstream @Shotwell.