I have a strange error. Sometimes, when I copy some files, their names are truncated. Fortunately, when it happens on a file, it is consistent, I can recreate the issue as many times as I want. I tried to find some special characters in the name to see if it the cause of the issue but it is not! I can' find a consistent reason.
How can I provide useful information for you to analyse the issue?
Best regards.
The_Steph
Hi Steph,
please, send me the logs (when the file has been put to the device and the list of files). It could be utf8 vs busybox related. That's all that comes to my mind
OK, as soon as I will find a file that create the issue, I will tick the box to generate debug log and send you the result so you'll be able to find the issue cause.
I just checked and I was using version 4.6 (I would have sworn I used 4.9) on my home PC and you probably corrected the issue I faced in your 4.8 version. I think it is a non problem.
However I faced another issue today, I file that always make the ADB plugin crash (that is the reason I checked my plugin version) when I copy it to my device whatever the location (internal memory, internal sd card, or external sd card). How can I send this file to you to analyse it?
I just checked and I was using version 4.6 (I would have sworn I used 4.9) on my home PC and you probably corrected the issue I faced in your 4.8 version. I think it is a non problem.
However I faced another issue today, I file that always make the ADB plugin crash (that is the reason I checked my plugin version) when I copy it to my device whatever the location (internal memory, internal sd card, or external sd card). How can I send this file to you to analyse it?
The_Steph
Hi Steph,
depends on the file size. If it is less then 5MB you can send it to me by email:
jakub at icewarp dot com
Otherwise we need to think of something else
Also send me the logs of the problem
Finally had some time to test the file upload with the debug log activated )
The only point here is that when I activate the logs in ADB options, the transfer is fine and when I disable it I got a crash message (did not took a screen capture though).
Last important point, it only happens when I am using Windows 7 64 bits and not on Windows XP SP3 32 bits.
I will pm you all the info so you can have a look at it.
Last point, are you aware of a file size limit to transfer via ADB? Each time I want to transfer a file larger than 2GB I end with a 0 byte file on my device while I can copy it when mounting my sdcard as an USB drive.
Finally had some time to test the file upload with the debug log activated )
The only point here is that when I activate the logs in ADB options, the transfer is fine and when I disable it I got a crash message (did not took a screen capture though).
Last important point, it only happens when I am using Windows 7 64 bits and not on Windows XP SP3 32 bits.
I will pm you all the info so you can have a look at it.
Last point, are you aware of a file size limit to transfer via ADB? Each time I want to transfer a file larger than 2GB I end with a 0 byte file on my device while I can copy it when mounting my sdcard as an USB drive.
Thanks.
The_Steph
Hi Steph,
ok please send me the details when you have them. x64 was not tested that much as I personally still use x32. I will figure it out
The 2GB limit I was not aware of it. Does it even start copying the file? Is it the same for pull and push?
I am using a portable 32bits TC version on a win 7 64 bits OS. Therefore your 32bits module is in action.
File copy does not start it just a one second operation and a 0 byte file created on the device (internal sdcard or 64GB exFAT formatted external sdcard).
At work I use a Win XP and everything works differently as said earlier. Blocked file transfer under windows 7 works fine.
I tried to pull 2.5gb file from device to pc and it worked but in a weird way. I got a immediate 100% done displayed, but the file is transferring like it was being done in the background without updating the display.
I'll do the same tests on my Windows 7 at home tonight.
icfu wrote:Nice plugin, but: Where are the hidden files and directories? Those starting with a dot? Any way to enable these?
Can't see .android_secure.vfat.tar from CWM and stuff like that...
I can see such files correctly on my sdcard. You can turn on debugging and see the result of the ls command. Maybe there should be more parameters to reveal these? Let me know
# ls -l -a /sdcard/clockworkmod/backup/2013-01-02.09.30.30
ls -l -a /sdcard/clockworkmod/backup/2013-01-02.09.30.30
-rwxrwxr-x system sdcard_rw 5242880 2013-01-02 10:30 boot.img
-rwxrwxr-x system sdcard_rw 5242880 2013-01-02 10:30 recovery.img
-rwxrwxr-x system sdcard_rw 199600896 2013-01-02 10:32 system.yaffs2.img
-rwxrwxr-x system sdcard_rw 121152768 2013-01-02 10:34 data.yaffs2.img
-rwxrwxr-x system sdcard_rw 203145216 2013-01-02 10:35 .android_secure.vfat.tar
-rwxrwxr-x system sdcard_rw 23232 2013-01-02 10:35 cache.yaffs2.img
-rwxrwxr-x system sdcard_rw 302 2013-01-02 10:36 nandroid.md5
Actually, the answer is pretty simple
You do not have busybox installed (or enabled) and that is why only the simple ls is used.
busybox:
If Not adb.Command('shell:su -c "busybox ls -lp -a -e --color=never "' + Path + '""', S) Then Exit;
native:
If Not adb.Command('shell:ls -l "' + Path + '"', S) Then NoList := True;
The reason is that the native ls might not have the -a parameter implemented. At least that's what I always thought so. In such cases it would not return anything. I have just checked the 4.2.1 emulator and it works with both -l and -a. So that would work but what about some old Android versions?
Actually, the answer is pretty simple
You do not have busybox installed (or enabled) and that is why only the simple ls is used.
busybox IS installed AND enabled. The problem is that in default installation mode busybox does NOT replace the ls command.
You have to explicitly enable ls replacement in the busybox "smart install".
These commands are NOT replaced in default installation mode:
)
