Hi all, I have a problem with the "change directory" function (CTRL+D) when I try to go to a directory of my Smartphone. It was ok with an older one (with Android 6) but now, I have a Samsung S10 with Android 10 (USB debugging activated) and the CTRL+D + a letter does not change to the Samsung directory. I need to go to the drive letter box and choose "Samsung S10e", then navigate to the sub dir to reach it, big waste of time.
I haven't change anything in my TC config, the only difference is another smartphone
Here is the CD function that I see in the CTRL+D "change directory menu" for one of my smartphone subdir, you can see the samsung string in it
cd ::{20D04FE0-3AEA-1069-A2D8-08002B30309D}\\\?\usb#vid_04e8&pid_6860&ms_comp_mtp&samsung_android#7&1ece14d8&0&0000#{6ac27878-a6fa-4155-ba85-f98f491d4f33}\SID-{20002,SECZ9519043CHOHB01,31901024256}\{ED6A2119-837D-B203-1B9E-CEACABEBD3E7}
Hi all, I have a problem with the "change directory" function (CTRL+D) when I try to go to a directory of my Smartphone. It was ok with an older one (with Android 6) but now, I have a Samsung S10 with Android 10 (USB debugging activated) and the CTRL+D + a letter does not change to the Samsung directory. I need to go to the drive letter box and choose "Samsung S10e", then navigate to the sub dir to reach it, big waste of time.
I haven't change anything in my TC config, the only difference is another smartphone
Here is the CD function that I see in the CTRL+D "change directory menu" for one of my smartphone subdir, you can see the samsung string in it
cd ::{20D04FE0-3AEA-1069-A2D8-08002B30309D}\\\?\usb#vid_04e8&pid_6860&ms_comp_mtp&samsung_android#7&1ece14d8&0&0000#{6ac27878-a6fa-4155-ba85-f98f491d4f33}\SID-{20002,SECZ9519043CHOHB01,31901024256}\{ED6A2119-837D-B203-1B9E-CEACABEBD3E7}
Am I missing something ?
TC : 9.51
ADB : 8.8
TIA
Do you recreate the CP string for your new phone? The string contain also the (serial)number of phone, so you have to recreate string for new phone...
and another settings to change for new phones to work with ADB: after connecting usb you have to change the USB settings -> Use USB for -> Transferring images (and not Transfering files / Android Auto as will be expected).
Thanks for replying
The CD command has been generated by TC when I added the directory of the Samsung with CTRL+D (the other smartphone was not a Samsung).
I have changed the setting on the Samsung to "Transferring images " but the CD command does not the job.
And on TC side, I don't see the content of my Samsung directories if it's not a jpg or a png file
Hi All,
First of all, thank you for this amazing plugin! It's been a great help for me for many years now.
I'd like to report a bug I've found with an Android Oreo (8.1) device.
Repro steps:
1. Create a file on your PC called "test file.txt"
2. Copy it to somewhere in the sdcard folder on the device
Expected:
3. The file appears on the device with the name "test file.txt"
4. The file can be copied back to the PC
Actual:
3. The file appears on the device with the name " file.txt"
4. The file cannot be copied back to the PC, it fails with "Error downloading file"
The file seems to be in a proper state on the device after copying, it's just that it's not accessible properly via the plugin.
This can be reproduced with a 8.1 emulator as well.
I have a device with Android 10 (Q) and on it I immediately came across a moment incomprehensible to me:
when copying files / folders with spaces in their names, the plugin displays them somehow strangely
For instance:
on Android 4.0.3 the path looks like this - \\\ ADB \ ... \ sdcard \ ... \ xxxx \ xxxx - xxx xxx xxx xxx xxx \
the same path on a device with Android 10 looks like this - \\\ ADB \ ... \ sdcard \ ... \ xxxx \ xxxx \ - \ xxx \ xxx \ xxx \ xxx \ xxx \
he added (\) to all spaces and, accordingly, there is nothing in the folders, but the Total Commander installed on this device and the native file manager show everything in the best possible way.
Hi,
Can you give a look on the ADB properties dialog.
Select Native 8.1 ls -la this should solve issues in folder name.
Also check that you have latest ADB/Fastboot binaries from google android platform.
Hope this helps.
NsPP
