tslocum / aafm

!!! Use https://gitlab.com/tslocum/adbfm instead !!! Android ADB file manager
Other
27 stars 4 forks source link

[CLOSED] Can't see any files on the android device #44

Closed tslocum closed 10 years ago

tslocum commented 10 years ago

Issue by ds9 Tuesday Oct 02, 2012 at 04:18 GMT Originally opened as https://github.com/sole/aafm/issues/44


On my PC I'm running Ubuntu 10.01 (lucid), kernel 2.6.32-43-generic-pae.

Android device: Toshiba tablet, model AT-300, Android version 4.0.3, kernel version 2.6.39.4-00013-g7d9fd87, build number IML74K.01.000041114.

When I start aafm, the right panel for the tablet is blank. Running the Android SDK tool ddms I am able to explore the file system on the tablet. In case it matters, this is the entry I have in the 51-android.rules file:

SUBSYSTEM==”usb”, ATTR{idVendor}==”0930”, ATTR{idProduct}==”0963”, MODE=”0666″

Can you tell me why I can't see any file on the tablet using aafm?

Thanks.

tslocum commented 10 years ago

Comment by sole Tuesday Oct 02, 2012 at 07:49 GMT


No.

I can't tell you anything if you don't provide the logs that aafm generates. You know those texts that show up at the command line window where you launched it.

Paste them here and we'll try to find it out :-)

tslocum commented 10 years ago

Comment by ds9 Tuesday Oct 02, 2012 at 12:54 GMT


Ok, here is what is in the terminal window when I start aafm:

main1@system1:~$ /home/main1/applications/aafm/src/aafm-gui.py EXECUTE= adb shell ls --help /bin/sh: adb: not found EXECUTE= adb shell ls -l -a /mnt/sdcard/ /bin/sh: adb: not found

And, when I manually execute adb, I get this:

main1@system1:~$ /home/main1/applications/asdk/android-sdk-linux/platform-tools/adb Android Debug Bridge version 1.0.29

-d - directs command to the only connected USB device returns an error if more than one USB device is present. -e - directs command to the only running emulator. returns an error if more than one emulator is running. -s - directs command to the USB device or emulator with the given serial number. Overrides ANDROID_SERIAL environment variable. -p - simple product name like 'sooner', or a relative/absolute path to a product out directory like 'out/target/product/sooner'. If -p is not specified, the ANDROID_PRODUCT_OUT environment variable is used, which must be an absolute path. devices - list all connected devices connect [:] - connect to a device via TCP/IP Port 5555 is used by default if no port number is specified. disconnect [[:]] - disconnect from a TCP/IP device. Port 5555 is used by default if no port number is specified. Using this command with no additional arguments will disconnect from all connected TCP/IP devices.

device commands: adb push - copy file/dir to device adb pull [] - copy file/dir from device adb sync [ ] - copy host->device only if changed (-l means list but don't copy) (see 'adb help all') adb shell - run remote shell interactively adb shell - run remote shell command adb emu - run emulator console command adb logcat [ ] - View device log adb forward - forward socket connections forward specs are one of: tcp: localabstract: localreserved: localfilesystem: dev: jdwp: (remote only) adb jdwp - list PIDs of processes hosting a JDWP transport adb install [-l] [-r] [-s] [--algo --key --iv ]

scripting: adb wait-for-device - block until device is online adb start-server - ensure that there is a server running adb kill-server - kill the server if it is running adb get-state - prints: offline | bootloader | device adb get-serialno - prints: adb status-window - continuously print device status for a specified device adb remount - remounts the /system partition on the device read-write adb reboot [bootloader|recovery] - reboots the device, optionally into the bootloader or recovery program adb reboot-bootloader - reboots the device into the bootloader adb root - restarts the adbd daemon with root permissions adb usb - restarts the adbd daemon listening on USB adb tcpip - restarts the adbd daemon listening on TCP on the specified port networking: adb ppp [parameters] - Run PPP over USB. Note: you should not automatically start a PPP connection.

refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1 [parameters] - Eg. defaultroute debug dump local notty usepeerdns adb sync notes: adb sync [ ] can be interpreted in several ways: - If is not specified, both /system and /data partitions will be updated. - If it is "system" or "data", only the corresponding partition is updated. environmental variables: ADB_TRACE - Print debug information. A comma separated list of the following values 1 or all, adb, sockets, packets, rwx, usb, sync, sysdeps, transport, jdwp ANDROID_SERIAL - The serial number to connect to. -s takes priority over this if given. ANDROID_LOG_TAGS - When used with the logcat option, only these debug tags are printed. Finally, when I manually run the adb devices command, I get this: main1@system1:~$ /home/main1/applications/asdk/android-sdk-linux/platform-tools/adb devices - daemon not running. starting it now on port 5037 * - daemon started successfully * List of devices attached 015d13ab6d17f80e device
tslocum commented 10 years ago

Comment by sole Tuesday Oct 02, 2012 at 13:08 GMT


Doesn't this ring a bell?

EXECUTE= adb shell ls --help /bin/sh: adb: not found

If not, then maybe you didn't read and follow the instructions on the project page regarding setting adb in $PATH: https://github.com/sole/aafm