With version 1.3, Chinese characters in file names fail to display properly (e.g., ?????.4e.???.pdf). I remember that version 1.2 works well, but not absolutely sure. If you could provide download link for version 1.2, I'll try it again.
My environment is Galaxy S+ with Android 2.3.6, and Windows XP Pro SP3 (both Simplified Chinese edition).
[WFX] Android ADB 8.8
Moderators: Hacker, petermad, Stefan2, white
Ok the adb binary is supplied with the plugin now in 1.4 and it works fine.nsp wrote:This work fine also on Windows seven 32/64bit. Birdysync that synchronize contacts from Thunderbird to android alo use adb to communicate with device and only those 3 DLL are necessary for standard stuff.damjang wrote:I try on winXPsp2 and on win7x64 with TC8.0x32. I installed only the android usb driver and copy the files (all only 340k) from the sdk platform-tools:damjang wrote:Is it possible to copy only the requested exe/dll of adb to plugin dir and use this instead of install all the sdk?to a dir in TC. Then set the path in fsplugin.iniCode: Select all
adb.exe AdbWinApi.dll AdbWinUsbApi.dll
Work ok!
If you have any usb driver provider by your device manufacturer or standard google usb driver (plus tweak for tegra 2 tablet) you can also use usb without any trouble for all debug enabled devices !
You just have to launch adb server.
Anyhow i did not succeed to do any screenshot.
2 new functionnalities :
A) could it be possible to get meta data for installed application like it is done with android commander in order to view it with file properties?
B) could be possible to to have a dedicated script folder in local pc to execute script in remote device.
Regarding the screenshot.
This is how it is called:
Please try if it's working from command line. If yes then do you have any national characters in your TC path?java -jar " + PluginDir + 'screenshot.jar" -s ' + DeviceId + ' "' + TempFile + '"'
About the 2 FRs:
A) Could you send me a screenshot or something? Is there any tool to get metadata apart from extracting the .apk or writing an android java app?
B) How do you see this exactly? Similar to the .apps folder? So you can copy a file to it and it will actually parse the script and run it via shell? Or it will be uploaded to the device and run there? Need more details.
Anyway, probably it would be better to have the script on the device already and simply run it, right?
Are you sure the filename is in utf-8 on that device? It is 100% unicode and utf8 based so it should work. You can send me the file zipped (with utf8 encoding of course) and I will testyyang wrote:With version 1.3, Chinese characters in file names fail to display properly (e.g., ?????.4e.???.pdf). I remember that version 1.2 works well, but not absolutely sure. If you could provide download link for version 1.2, I'll try it again.
My environment is Galaxy S+ with Android 2.3.6, and Windows XP Pro SP3 (both Simplified Chinese edition).
Thanks for your prompt reply! I've uploaded a small test case here: http://www.4shared.com/zip/lYC6lQcl/adbtestcase.html.jakubklos wrote:Are you sure the filename is in utf-8 on that device? It is 100% unicode and utf8 based so it should work. You can send me the file zipped (with utf8 encoding of course) and I will test
"test.zip" contains my test file, "我的笔记.txt". From the ADB plugin, the display name is "????.txt" for me. The text file's content is "我的笔记" in UTF-8, by the way. This zip file was created by Total Commander for Android.
"test.txt" is the result of executing "ls > test.txt" in the directory of the test file ("我的笔记.txt") from an ADB shell console. Since "test.txt" is UTF-8 encoded, I think the encoding of the test file name is OK. Thank again!
Ok, I know what the problem is now. "busybox ls" corrupts the encoding somehow. Plain "ls" works fine however we lose some additional functionality. This seems like a pretty big bug of busybox to me.yyang wrote:Thanks for your prompt reply! I've uploaded a small test case here: http://www.4shared.com/zip/lYC6lQcl/adbtestcase.html.jakubklos wrote:Are you sure the filename is in utf-8 on that device? It is 100% unicode and utf8 based so it should work. You can send me the file zipped (with utf8 encoding of course) and I will test
"test.zip" contains my test file, "我的笔记.txt". From the ADB plugin, the display name is "????.txt" for me. The text file's content is "我的笔记" in UTF-8, by the way. This zip file was created by Total Commander for Android.
"test.txt" is the result of executing "ls > test.txt" in the directory of the test file ("我的笔记.txt") from an ADB shell console. Since "test.txt" is UTF-8 encoded, I think the encoding of the test file name is OK. Thank again!
Any ideas here? I use busybox for these operations (rm, mkdir, mv, ls). Of course if there is no busybox the stock tools are used but this is a different case. busybox exists but returns malformed data.
I have even found the bug:
https://dev.openwrt.org/ticket/7993
But it was not fixed
Ok I have been able to overcome the problem:jakubklos wrote:Ok, I know what the problem is now. "busybox ls" corrupts the encoding somehow. Plain "ls" works fine however we lose some additional functionality. This seems like a pretty big bug of busybox to me.yyang wrote:Thanks for your prompt reply! I've uploaded a small test case here: http://www.4shared.com/zip/lYC6lQcl/adbtestcase.html.jakubklos wrote:Are you sure the filename is in utf-8 on that device? It is 100% unicode and utf8 based so it should work. You can send me the file zipped (with utf8 encoding of course) and I will test
"test.zip" contains my test file, "我的笔记.txt". From the ADB plugin, the display name is "????.txt" for me. The text file's content is "我的笔记" in UTF-8, by the way. This zip file was created by Total Commander for Android.
"test.txt" is the result of executing "ls > test.txt" in the directory of the test file ("我的笔记.txt") from an ADB shell console. Since "test.txt" is UTF-8 encoded, I think the encoding of the test file name is OK. Thank again!
Any ideas here? I use busybox for these operations (rm, mkdir, mv, ls). Of course if there is no busybox the stock tools are used but this is a different case. busybox exists but returns malformed data.
I have even found the bug:
https://dev.openwrt.org/ticket/7993
But it was not fixed
v1.4 will cover it too"busybox ls" not used because utf8 is not supported (https://dev.openwrt.org/ticket/7993), ls syntax detection improved, new option to switch back to busybox ls in fsplugin.ini
New version 1.4
Ok guys, a new version has been released.
1.4
- adb binary included (works only with the connect feature) - no need to install Android SDK
- "busybox ls" not used because utf8 is not supported (https://dev.openwrt.org/ticket/7993), ls syntax detection improved, new option to switch back to busybox ls in fsplugin.ini
- Execution operations full unicode
- An error is displayed if Java could not be run
- Copy/Move between 2 ADB devices support added
I have tested the v1.4 and for standalone use of adb.exe there is missing the AdbWinUsbApi.dll. Without it for me connection with usb don't work.
Then I have also find some problem in dir show. In TC it is listed like:
but the ls -l sniffed with SocketSniff is:
I tested on Android 2.3.5 rooted, busybox v1.20.2 to winXP-SP2 TC8.0x32
Then I have also find some problem in dir show. In TC it is listed like:
Code: Select all
12.00 txt 1.980Code: Select all
Receive: Return Code: 0x00000000
001Fhost:transport:304D19D5A44B229E
Receive: Return Code: 0x00002733
Send: Return Code: 0x00000000
OKAY
Receive: Return Code: 0x00000000
002Bshell:ls -l "/mnt/sdcard/Android/apk/test/"
Receive: Return Code: 0x00002733
Send: Return Code: 0x00000000
OKAY
Send: Return Code: 0x00000000
-rwxrwxr-x system sdcard_rw 0 1980-01-01 01:00 prova 2012.01.01 12.00.txt
-rwxrwxr-x system sdcard_rw 522359 2012-05-07 01:05 Barcode_Scanner_v4.1.apk
-rwxrwxr-x system sdcard_rw 532395 2004-01-01 14:01 Barcode_Scanner_v4.2.apk
-rwxrwxr-x system sdcard_rw 6378112 1980-01-01 01:00 DejaOffice2_2_2_309.apkOk, I will add the usb dll too.damjang wrote:I have tested the v1.4 and for standalone use of adb.exe there is missing the AdbWinUsbApi.dll. Without it for me connection with usb don't work.
Then I have also find some problem in dir show. In TC it is listed like:but the ls -l sniffed with SocketSniff is:Code: Select all
12.00 txt 1.980I tested on Android 2.3.5 rooted, busybox v1.20.2 to winXP-SP2 TC8.0x32Code: Select all
Receive: Return Code: 0x00000000 001Fhost:transport:304D19D5A44B229E Receive: Return Code: 0x00002733 Send: Return Code: 0x00000000 OKAY Receive: Return Code: 0x00000000 002Bshell:ls -l "/mnt/sdcard/Android/apk/test/" Receive: Return Code: 0x00002733 Send: Return Code: 0x00000000 OKAY Send: Return Code: 0x00000000 -rwxrwxr-x system sdcard_rw 0 1980-01-01 01:00 prova 2012.01.01 12.00.txt -rwxrwxr-x system sdcard_rw 522359 2012-05-07 01:05 Barcode_Scanner_v4.1.apk -rwxrwxr-x system sdcard_rw 532395 2004-01-01 14:01 Barcode_Scanner_v4.2.apk -rwxrwxr-x system sdcard_rw 6378112 1980-01-01 01:00 DejaOffice2_2_2_309.apk
As for the ls issue. I will use your ls output and debug and try to fix it
Thank you
You need to use some WiFi ADB app from the market. I use "WiFi ADB" and start it. It will show you the IP and the port...Umpal wrote:Guys, how do I know what port should I use in order connect to my phone (through WiFi)? I tried 5555 and 5554 as on the posted screenshot but it didn't work. My USB Debug is on, I even turned off my PC's firewall to be sure.
Thanks for quick reply.jakubklos wrote:You need to use some WiFi ADB app from the market. I use "WiFi ADB" and start it. It will show you the IP and the port...Umpal wrote:Guys, how do I know what port should I use in order connect to my phone (through WiFi)? I tried 5555 and 5554 as on the posted screenshot but it didn't work. My USB Debug is on, I even turned off my PC's firewall to be sure.
Unfortunately WiFi ADB says that requires rooted phon. I tried with ADB WiFi (where says 'Touch the bug to switch server state'. When I click info appears: 'Can't execute ADB server state change commands'.
I went with WiFi ABD widget as well but this little fellow displays 'Please Wait' for a second and nothing happens.
Any other idea? I don't want to root this phone yet.
Both issues fixed:damjang wrote:I have tested the v1.4 and for standalone use of adb.exe there is missing the AdbWinUsbApi.dll. Without it for me connection with usb don't work.
Then I have also find some problem in dir show. In TC it is listed like:but the ls -l sniffed with SocketSniff is:Code: Select all
12.00 txt 1.980I tested on Android 2.3.5 rooted, busybox v1.20.2 to winXP-SP2 TC8.0x32Code: Select all
Receive: Return Code: 0x00000000 001Fhost:transport:304D19D5A44B229E Receive: Return Code: 0x00002733 Send: Return Code: 0x00000000 OKAY Receive: Return Code: 0x00000000 002Bshell:ls -l "/mnt/sdcard/Android/apk/test/" Receive: Return Code: 0x00002733 Send: Return Code: 0x00000000 OKAY Send: Return Code: 0x00000000 -rwxrwxr-x system sdcard_rw 0 1980-01-01 01:00 prova 2012.01.01 12.00.txt -rwxrwxr-x system sdcard_rw 522359 2012-05-07 01:05 Barcode_Scanner_v4.1.apk -rwxrwxr-x system sdcard_rw 532395 2004-01-01 14:01 Barcode_Scanner_v4.2.apk -rwxrwxr-x system sdcard_rw 6378112 1980-01-01 01:00 DejaOffice2_2_2_309.apk
Please, wait for the release1.5
- adb binary - also added AdbWinUsbApi.dll
- ls syntax detection improved
I do not think WiFi ADB can work without a rooted phone unfortunately. In that case you should try to get it working with USB instead or simply root your phone.Umpal wrote:Thanks for quick reply.jakubklos wrote:You need to use some WiFi ADB app from the market. I use "WiFi ADB" and start it. It will show you the IP and the port...Umpal wrote:Guys, how do I know what port should I use in order connect to my phone (through WiFi)? I tried 5555 and 5554 as on the posted screenshot but it didn't work. My USB Debug is on, I even turned off my PC's firewall to be sure.
Unfortunately WiFi ADB says that requires rooted phon. I tried with ADB WiFi (where says 'Touch the bug to switch server state'. When I click info appears: 'Can't execute ADB server state change commands'.
I went with WiFi ABD widget as well but this little fellow displays 'Please Wait' for a second and nothing happens.
Any other idea? I don't want to root this phone yet.
I do not have to tell you what benefit you will get when you root your phone. It's a must have
