[WFX] Android ADB 8.8
Moderators: Hacker, petermad, Stefan2, white
how view hidden file or dir
GoodAfternoon,
simple question how view hidden file or directoty?
I just rename a file WITH SOLID EXPLORER on device
for exsample (.myfile) the . is use for hidden file.
when i view a device with TotalCommander trough ADB plugin
I do not view a file.
simple question how view hidden file or directoty?
I just rename a file WITH SOLID EXPLORER on device
for exsample (.myfile) the . is use for hidden file.
when i view a device with TotalCommander trough ADB plugin
I do not view a file.
Re: how view hidden file or dir
You should change to busybox ls and files will be visible.giuleppe wrote:GoodAfternoon,
simple question how view hidden file or directoty?
I just rename a file WITH SOLID EXPLORER on device
for exsample (.myfile) the . is use for hidden file.
when i view a device with TotalCommander trough ADB plugin
I do not view a file.
Re: how view hidden file or dir
jakubklos wrote:You should change to busybox ls and files will be visible.giuleppe wrote:GoodAfternoon,
simple question how view hidden file or directoty?
I just rename a file WITH SOLID EXPLORER on device
for exsample (.myfile) the . is use for hidden file.
when i view a device with TotalCommander trough ADB plugin
I do not view a file.
Thank's
Hi,
I got a small feature request, if possible:
From what I could tell by the debug.log, the plugin seems to be able to automatically use su -c 'cmd', in case it fails without su.
However it does not make use of this technique for commands entered at the command line.
Could you add the same su -c '...' mode for commands entered manually, too? (Maybe as an option)
Cheers,
za222
I got a small feature request, if possible:
From what I could tell by the debug.log, the plugin seems to be able to automatically use su -c 'cmd', in case it fails without su.
However it does not make use of this technique for commands entered at the command line.
Could you add the same su -c '...' mode for commands entered manually, too? (Maybe as an option)
Cheers,
za222
Hi, good idea. I was thinking about this several times but not sure why I didn't implement it. Will put it on the list.za222 wrote:Hi,
I got a small feature request, if possible:
From what I could tell by the debug.log, the plugin seems to be able to automatically use su -c 'cmd', in case it fails without su.
However it does not make use of this technique for commands entered at the command line.
Could you add the same su -c '...' mode for commands entered manually, too? (Maybe as an option)
Cheers,
za222
Jakub
jakubklos,
Lately I experince horrible trasfer speeds. No matter what file or to what location (internal/extrenal) sd I make transfer, I get 14kb/s speeds.
The speed is almost fixed.
Image: http://i48.tinypic.com/34qmmud.jpg
Right now I am on android ADB 5.4 and using CM10.1.
Thanks for any help.
Lately I experince horrible trasfer speeds. No matter what file or to what location (internal/extrenal) sd I make transfer, I get 14kb/s speeds.
The speed is almost fixed.
Image: http://i48.tinypic.com/34qmmud.jpg
Right now I am on android ADB 5.4 and using CM10.1.
Thanks for any help.
Not related to the plugin. I have justed tested 5.5 with my Nexus 10 over WiFi ADB and the transfer from is 640kb/s and transfer to is 400kb/s. You can always try the adb command line tool to check the speed.Orochi wrote:jakubklos,
Lately I experince horrible trasfer speeds. No matter what file or to what location (internal/extrenal) sd I make transfer, I get 14kb/s speeds.
The speed is almost fixed.
Image: http://i48.tinypic.com/34qmmud.jpg
Right now I am on android ADB 5.4 and using CM10.1.
Thanks for any help.
I would suggest rebooting the device, rebooting the computer and check that you have a good WiFi signal and that there is no traffic on it.
reboot to bootloader
Hi,
On my device the roboot to bootloader option seems not to work and also there is no log entry about it.
Can you please fix it it will help instead of writing it by hand every time
thank you
On my device the roboot to bootloader option seems not to work and also there is no log entry about it.
Can you please fix it it will help instead of writing it by hand every time
thank you
Re: reboot to bootloader
Hi,gesha_s wrote:Hi,
On my device the roboot to bootloader option seems not to work and also there is no log entry about it.
Can you please fix it it will help instead of writing it by hand every time
thank you
no all ROMs support this feature. adb reboot command is used for this.
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
So you can test if it's working. If not then you can contact the ROM cook or change your ROM
Hi,tikhom wrote:Hi! My ZTE_V9 (Android 2.2.2) cannot communicate with Windows XP via Android ADB 5.6. "Enter Device IP:Port" banner pops-up... How to fill-in the empty string? Or how ti get rid of it and launch the handshaking? Thanks in advance.
I assume you have a rooted phone and WiFi ADB app installed. After enabling WiFi ADB you enter the IP of your device and it will connect.
"$" sign in path names not treated as character
Recently I tried to find the place where the map files for the "Navfree" application are stored on my device. I could NOT get to that directory using ADBD plugin. I tried also the option with and without "ls" use - no change.
Switching on debug it shows that the "ls" is not getting all characters from the original path. The directory to list is named "$com.MAP.OSM.DEU" but the "ls" issues ".com.MAP.OSM.DEU" instead.
I checked and it seems that the "$" is a legal character in filenames, so it should be treated right.
Switching on debug it shows that the "ls" is not getting all characters from the original path. The directory to list is named "$com.MAP.OSM.DEU" but the "ls" issues ".com.MAP.OSM.DEU" instead.
I checked and it seems that the "$" is a legal character in filenames, so it should be treated right.