Hi, I am using a Motorola Edge 2022 packed with Android 15 and a Motorola G20 with Android 14.
We recently went on vacation to Turkey and set up on both Android phones QFile-Pro to mirror into my NAS the new files (pictures taken) during the trip, using the Wifi of the hotels.
Many issues arise; the connection did not re-establish automatically after connecting to WiFi at the hotels.
So many times I needed to suspend the uploading task and resume it after a successful connection to the NAS.
SUPRPRISE :S
The worst of all was that after returning home, when I tried to see my remotely downloaded files at the local NAS I got many “bad image” on *.JPG files.
:idea: Sniffing around, I noticed they were too big for a *.JPG file, so I renamed them to *.mp4 and suddenly they showed as a full MP4 video file.
:!: Digging deeper, I noticed that only some of the .JPG files were renamed as .MP4, so I took the SD card out of the phone, and compared them with the uploaded files. And here came the ugly surprise: "all files were renamed and badly stored as the former file name, independent of the type or file. All of my files were suddenly changed (the content was the former file content, and the name was the next file name), making it impossible to make corrections with any file manager.
I currently have more than 4000 files “auto-renamed” with the former file time-stamp and name.
This is dangerous and a HUGE PROBLEM :twisted:
I no longer trust the auto-upload of the QFile pro…!!! :evil:
QNAP should be ashamed of such a huge mistake on a supposedly trustworthy remote-uploading backup system!
I’m not sure of what’s going on as it looks like you didn’t take a lot of pictures but instead videos. Generally if you take “live” pictures, there is both a picture and a video file for each. I’m not sure how Android handles it but this is how it works on the iPhone.
You have to leave QFile running and in the foreground to sync all images in your library initially. After that, it does do a pretty good job of keeping new images sync’d to the NAS. Perhaps that’s part of the issue here.
But beyond that, unlesss you are using a VPN or have your NAS exposed to the internet (bad idea), if you are accessing the NAS via QFile and going through MyQNAPCloud, then you are effectively running through the QNAP servers in Taiwan. It’s not the fastest connection so it’s likely that it was taking a long time to do it and if you have a lot of files, you have to keep QFile running in the foreground.
Now, you can also change settings in QFile to keep the original file name. The default is that it changes it to the date the picture was taken instead of IMG001, etc. Perhaps something got messed up in this process. I would recommend setting QFile to not change the file name. I would also open a support ticket about this. You may have found a legitimate bug.
Thanks!
I know what you’ve said, but this is not the case, the QFile was instructed not to change the picture name, and overwrite any on the NAS (if duplicated)
I confirmed that the QFile filename change was an obvious programming internal error, just because the filenames are “shifted” in the list by one, every file was renamed to the former file name, including the extension. I noticed this because the internal date stamp did not coincide with the filename-stamped date not with the file-date stamp. I am programmer and some time ago wrote a small program to rename any *.jpg (JFIF formatted files) to the internal JFIF date+time taken information. This was because some programs to download pictures of some cameras wrongly stamp the file’s datestamp (as the copy-datetime) and do not copy the original date time stamp, so you get a mess in your picture directory.
The program failure I am talking about here is surely an internal failure during the uploading protocol, maybe when retrying, or so, the program QFile gets desynced with the NAS service.