Hello, thanks for the awesome KDE-Connect-project! I'm running KDE-Connect 1.0 in Plasma 5.7.4 on a KDE neon 5.7 system and the Android app version 1.4 on Cyanogenmod 12.1 (Android 5.1.1). When I use Dolphin to browse files on the phone and copy a file to the PC the file on the PC shows exactly the same timestamp as the sourcefile on the phone. The same is true when I copy a file from the PC to the phone. However, when I browse files on the phone and use the share-function of Android to send a file via KDE-Connect to the PC the target file get the time and date of the moment of the transfer. The desired behaviour of all this would be to always keep the original time and date of the file transfered! Reproducible: Always
It doesn't seem super-high-priority, but I agree with you this is a bug to fix at some point.
I'm now using 20.08.0-0xneon+20.04+focal+build6 (at least that's what shown by package management) in Plasma 5.19.4 on a KDE neon 5.19 User Edition and the Android app version 1.14.2 on LineageOS 14.1 (Android 7.1.2). The bug got worse because now copying a file from PC to the phone also alters the file's timestamp.
Sorry I must correct my previous comment. The bug did not get worse, in fact the original bug this was all about seems to be gone but replaced by the behaviour mentioned in my previous comment!
So I've now tested the current behaviour using version 22.04.3-0xneon+20.04+focal+release+build42 and a smartphone running LineageOS 16.0 which is Android 9 effectively and here are the results. Sharing a file from PC to smartphone: the last edited timestamp of the target file gets changed to the moment of the transfer. Sharing a file from smartphone to PC: the last edited timestamp of the target file gets changed to the moment of the transfer. Copying a file from PC to smartphone via Dolphin: the last edited timestamp of the target file gets changed to the moment of the transfer. Copying a file from smartphone to PC: the last edited timestamp of targetfile is the same as the source file. Summary: in one out of 4 cases it works as it should. I'd be glad if someone in the know could finally tackle this issue so that the file transfer features really become useable well in day to day usage. Until then it's back to trusty old FTP-clients for me.