Timezone problem BC between Windows and Android

[Aaron]

Thanks. Always great to get up to date app/software recommendations.

[buelensc]

Problems solved. I promised to say how.

1. The App "FTP Server Pro" does support preserving timestamps when copying files. It was my mistake telling it did not work when testing with Filezilla: Filezilla has an option to preserve timestamps, it was set OFF in my case (might be the default)
2. BC copies with timestamp preservation. Great.
3. BC setup to use FTP is easy,
4. Setting up "FTP Server Pro" is easy too. But giving this app the rights to access to root map on an external SD card is a bit hidden. In its settings panel, do NOT select "Ext.SdCard", even though it looks the ideal selection. It makes that the home folder for FTP connections becomes Android/data/com.olivetree.ftpserverpro/files not what one wants to sync photo's for example.
   You must select "Custom folder", that starts Android's file manager. There you have to find the "external SD card" and select that. Android will then permit the FTP App to access this card, and if you like even all folders from the top.

[Aaron]

Oh, we think timestamps are important.

If you do find anything up to date, any follow up would be appreciated.

[buelensc]

Good news coming from the Android side?
https://www.mobileread.com/forums/sh....php?p=4113033
After your recent changes to the drivers for 5.17, I can confirm timestamps started working on all my Android devices. Date/Times are set properly when sending files to device (verified in file manager)
Dated 30 April 2021, so I guess it won't ever get onto my Samsung A40, too long ago already.

From a website that mentioned it in a discussion about syncing Windows with Android, I got nice words about the "Ftp server" app. So I installed it; used Filezilla to copy a file to Andoid, and the timestamp was NOT preserved. So my fears that surely not all FTP servers maintain timestamps are confirmed. Makes me think about another, non-FTP based, file transfer method commonly used to transfer files between mainframes and workstations (IND$FILE not to name it, slower than FTP but requires no setup): it doesn't preserve timestamps. I'm specialized in z/VM, and IBM had an "internal use only" IND$FILE like tool, ALMCOPY, that preserved timestamps, I was so happy with it. But, that one stopped working with Windows 7, and was never fixed. I just don't understand why apparently so few people find these timestamps important. Grrr.

I'll keep searching, and when I find a solution, I'll tell you here.

[buelensc]

Assigning a drive letter to my Android: I've been looking around a long time to find tricks. Because with a drive letter, ToalCommander or even my self written Photo database management program could to sync.
USB Tethering: when I activate that, my Android becomes a kind of router router and via Android's G4 phone network my laptop connect to the Internet. I can't miss that on locations where I want to use my laptop, but without access to a Wifi network.

[Aaron]

I'm afraid I'm not familiar with a specific Android FTP app; they shift a bit frequently and the one I was familiar with isn't one I'd recommend anymore. I also say "FTP" since BC4 Std supports FTP, but if you have Pro, I'd recommend SFTP.

What does "usb tethering" do? I don't have an Android device handy, but I think that might be presenting as a drive letter? Or is that only for acting as a network hotspot?

We do support the MTP protocol, and many devices work well with it (including making optional support to better handle file timestamps) as do transfers From the device as the Source. We could try to add some kind of 'supported' language or emphasize trying the Trial with your device, but it would be difficult to phrase as a warning and we heavily encourage trying the Trial first in all scenarios. I have a lot of experience troubleshooting these types of devices, but that's because I also see all of the support requests. That doesn't mean it is prevalent, just that I have a lot of experience.

[buelensc]

I can change the USB connection type indeed. But, the setting page is made for dumb users, and allows me to select (I translate, my Android speaks Dutch)

• transfer files
• USB tethering
• MIDI
• transfer photos
• only charge battery

The first one will be MTP, the 4th PTP. I don't have other choices. (I've got Android 11)

You convinced me BC is not to blame here, BC is just misinforming me (just like Explorer). And that's again not a blame for BC. But, teh BC website should have a warning that one should check if with an MTP connection if the timestamps are preserved after breaking the connection.

Yesterday evening I restarted the Old APP that can fix dates for photos: "Image & Video Date Fixer". I also digged up the problem I had with it: the problem was indeed that it didn't work for subfolder, I'd have to do it folder by folder. It appear the bug was fixed now: yesterday thus the App had to scan of my 40K photos took 2 hours to find which filesystem dates didn't match with the Exif date. This morning I let it fix all mismatched dates (I didn't time it)

Now, for the future. BC supports FTP you say. I'm a retired IT man (worked on mainframes since 1978). From my past, I know that at least some FTP servers do no support maintaining the file timestamps. Do you happen know an Android FTP server App that does preserve file timestamps? (I already googled a bit, but I didn't find a single App yet that speaks about timestamps).

In the meantime: thanks for your quick help.

[Aaron]

A little of both. MTP doesn't require timestamps, so it is up to each device to implement their own methods of support. This can shift per device or per software version of device on If or How well they handle timestamps. Does your version of Android have the dropdown control in Settings to swap how it connects when plugged into USB? While this specific device appears to have timestamp issues reproducible with Explorer (right?), that is likely limited to its MTP support, and if Drive letter is a built-in option (or installing an FTP server app), these would likely work.

If Explorer is exhibiting the same behavior with a single sample file and test, then BC4 is going to run into the same issues.

[buelensc]

> device reboot exposed at least one more facet of that disconnecting and reconnecting the device didn't expose (which, is pretty weird).
Up to now, I didn't test unplugging the phone, I only followed the suggestion of a reboot.

I copy a file both with Windows and BC to the phone's storage and to the SD-card
- Explorer and BC show timestamp as on Windows, both on Phone and SD-card
- Restart BC: timestamps still OK
- TotalCommander on Android: time = today, both on the SD-card and the Phone
Disconnect Android
- Explorer and BC show today as timestamp, both for SD-card and phone's storage

Th App that I did use once to set the timestamps of JPG's equal to the EXIF info, proves it is possible on Android to set the timestamp one wants (bu that obviously only works for files with Exif info, not for PDFs for example). So MTP is the culprit, or Android's MTP implementation?

[Aaron]

And in case it helps, one strategy I've seen for Android devices specifically with bad MTP support (if that is what is happening here), is that some offer alternate connection methods as part of the Android OS (such as binding as a drive letter) or using an app to setup an FTP server on the device, which can also be remotely accessed with BC4.

[Aaron]

BC4 is using standard copy functions to copy information to the device over the MTP protocol. The steps I'm recommending aren't specific to BC4 troubleshooting, but troubleshooting various MTP devices (including Android) I've had experience with over the years. As a next step, if you copy a single file using Explorer as one test and the Command Line as another, how does the timestamp appear on the phone before and after a phone restart? While it's possible there's something specific to BC4's copy function, it's more likely an issue with the device's MTP implementation. But first we have to narrow down exactly how the problem manifests, which the device reboot exposed at least one more facet of that disconnecting and reconnecting the device didn't expose (which, is pretty weird).

[buelensc]

I did indeed already restart BC to verify if after restart things looked fine. But I didn't reboot anything then.
Now I rebooted my Android device, and the folder that was OK before, is now all bad, BC displays the copy date.

So, is the conclusion that BC cannot be used to sync nicely between Windows and Android? So, that I spent money on BC for nothing? If so, BC's website should inform about this problem.

I just remember: I once used an App on Android to set the timestamp for JPGs to the timestamp stored in the EXIF data. But, this app didn't work very well (I forgot the details, may too much manual work? too much for 40000 photos?). But, that can maybe explain that I do have some folders with photos where the timestamps match with Windows.

[Aaron]

Hello,

MTP devices don't technically mandate timestamps, so every device can decide to tackle them a little differently. I'm not surprised Touch fails, but was hoping it could be used. It is a little surprising to see a difference in behavior for the Creation date (which, is usually set to the new creation of a file on the destination; you can test with two local files and Explorer).

One key thing to make sure of: on the initial transfer and the initial listing of the files, don't initially trust the timestamp displayed. While troubleshooting, I've seen some devices display the 'expected' value, but then lose it after a full refresh or double-checking in Explorer. It seems like you did double check in Explorer, but I can't explain why Total Commander could then differ. I might suggest throwing in a device reboot between verifications, to see if that somehow changes the timestamp value displayed in BC4, Explorer, or Total Commander.android.app.

[buelensc]

I a folder with photos that were not yet coped onto the Android (a reason why I started looking at a global resync yesterday). So, I copied that folder onto the Android, and that folder now looks fine; BC displays the expected timestamps October 7. But, when I look with TotalCommand on the Android: all files have today's date, the same with Android's explorer like App. Maybe Android's filesystem has more than one timestamp field available and BC displays another than Andoid's explorer/TotalCommander.

Before the copy


After the copy, all looks fine for this new folder


What Windows tells


And what Android's TotalCommander displays, all dates are 5'th of April, the upload instance


I had an idea: I used Windows explorer to copy 2 extra files into the folder on Android:



Remark that Windows correctly copies the "modification" timestamp, but it also sets a Creation timestamp; the files copied with BC have none. Maybe Windows is storing that information into its own Registry and not in the Android Filesystem?

[buelensc]

The reason why I thought about timezone: I noticed that it seemed to be hard to keep the timestamp when copying files from Windows to Android. I though that BC had some trick to rember what was copied, and that the trick stopped working with a timezone change.

I just tried touch, with two photos. The first one was one dated 1978 (I already wrote that on Windows -where the master copy lives- I set the timestamp to the date the photo was taken. It failed, but I thought: maybe something doesn't like a date that old.
So I went to another folder, with one JPG with a mismatch, and tried to set the date with Touch to "that of the other side". It failed too with the same error.