androidgeek2019
Newbie
My device is a Huawei Mate 9 with Oreo 8.0.
When I copy a file (locally, any file manager) or from an SSH client (my device runs SSH Droid and 'SSH server') to a folder of the internal storage (/storage/emulated/0) the copy date is always the time of the copy action (which I call 'now'), not the original file time stamp.
I know that a Linux shell cp action does the same, but when running cp -a <src> <target> it sets the timestamp of the original file. This works under Ubuntu 18.04 and macOS 14.1 and previois versions of Android (6.0 or less). When I do a copy action in a shell under Android 8.0, it issues an 'access denied' error when performing cp -a. It does copy, but sets the timestamp to 'now'.
A more clear example is this: on my previous phone running KitKat 4.4 I had FolderSync which syncs with a computer running an SSH server and worked flawlessly. However, on my Mate 9 this app is useless, because the timestamps are messed up because of this bug.
Do others have a similar problem ?
When I copy a file (locally, any file manager) or from an SSH client (my device runs SSH Droid and 'SSH server') to a folder of the internal storage (/storage/emulated/0) the copy date is always the time of the copy action (which I call 'now'), not the original file time stamp.
I know that a Linux shell cp action does the same, but when running cp -a <src> <target> it sets the timestamp of the original file. This works under Ubuntu 18.04 and macOS 14.1 and previois versions of Android (6.0 or less). When I do a copy action in a shell under Android 8.0, it issues an 'access denied' error when performing cp -a. It does copy, but sets the timestamp to 'now'.
A more clear example is this: on my previous phone running KitKat 4.4 I had FolderSync which syncs with a computer running an SSH server and worked flawlessly. However, on my Mate 9 this app is useless, because the timestamps are messed up because of this bug.
Do others have a similar problem ?