Android Device Monitor File Explorer does not work with emulator working with API 24+

So, just like a question. The Android device monitor does not show anything in the Explorer view. This only happens on virtual devices running the Android API level 24+.

Any solution?

enter image description here

+44
android android-studio
Jul 30 '16 at 1:54 on
source share
9 answers

Prior to Android Lollypop emulators, we can access the file explorer folders. If the emulator is created with marshmallows or higher, we cannot access the file explorer. Perhaps this is a bug from API level 24+.

+11
Jan 20 '17 at 8:58
source share

This is a bug in Android Device Monitor and is reported by Google.

According to the Message, this thread will be updated after the patch is released.

+8
Feb 27 '17 at 7:46
source share

A temporary solution that worked for at least my needs was to install the .apk file manager (I used the Astro.apk file manager) - just drag and drop .apk into the emulator window. Another very useful utility - ImDisk - which allows you to mount a sdcard.img virtual device. If you mount it as a downloadable device, you can access the virtual file system in real time.

+6
Mar 11 '17 at 14:03
source share

Workaround with adb command line tool:

 root@mypc ~ $ adb kill-server root@mypc ~ $ adb start-server root@mypc ~ $ adb root 

Now you can browse the file system with the linux ls :

 root@mypc ~ $ adb shell ls -all / total 3688 drwxr-xr-x 15 root root 0 2017-04-21 11:11 . drwxr-xr-x 15 root root 0 2017-04-21 11:11 .. drwxr-xr-x 29 root root 0 2017-04-21 11:11 acct drwxrwx--- 6 system cache 4096 2017-01-06 12:11 cache lrwxrwxrwx 1 root root 13 1970-01-01 01:00 charger -> /sbin/healthd ... -rw-r--r-- 1 root root 4853 1970-01-01 01:00 ueventd.rc lrwxrwxrwx 1 root root 14 1970-01-01 01:00 vendor -> /system/vendor 
+5
Apr 21 '17 at 10:41 on
source share

Another workaround is to use adb shell

First copy the database to sdcard

 ./adb shell run-as com.yourapplication cp /data/data/com.yourapplication/databases/yourFileName.db /sdcard 

Then pull the database file to the computer

 ./adb pull /sdcard/yourFileName.db /Users/yourUserName/Desktop 
+3
Mar 29 '17 at 15:11
source share

This is probably due to permissions for the new folder for Android. As indicated in another answer , you can use:

 root@mypc ~ $ adb root 

to gain root access to your emulator (no need to restart adb). Then you can see all the folders on the device using the DDMS file or through the shell. Another option is to wait for the new file explorer that was promised in version 2.4 of Android Studio.

If you need to update the gallery after this, like me, you can use:

 root@mypc ~ $ adb shell "am broadcast -a android.intent.action.MEDIA_MOUNTED -d file:///mnt/sdcard" 

This will simulate the installation of an SD card, which will lead to a rescan of the media.

+2
04 Sep '17 at 2:04 on
source share

Its an alternative way.

Create a bat file to configure APP_NAME Example (com.example.com)

DESTINATION_FOLDER (myProjectFiles)

 cd "C:\Users\USERNAME\AppData\Local\Android\sdk\platform-tools\" adb shell run-as APP_NAME rm -R /sdcard/DESTINATION_FOLDER adb shell run-as APP_NAME cp -R cache/ /sdcard/DESTINATION_FOLDER rmdir C:\Users\USERNAME\Documents\DESTINATION_FOLDER /s /q adb pull /sdcard/DESTINATION_FOLDER C:\Users\USERNAME\Documents\ timeout 5 

After setting up your bat file, double-click it. he will do the rest

+2
Oct 14 '17 at 4:24 on
source share

I also ran into the same issue in Android Device Monitor.

The emulator we use is very tall, like the Marshmallow 25, so for this to happen, we just need to run the emulator at the level level, i.e. Lollipop 22

+1
Jun 01 '17 at 7:41
source share

Try a few methods:

  • Click the triangle icon in the device window, then select "reset adb."
  • Turn off the emulator and turn it on again.
  • Now you can use Genymotion, the best simulator.
-one
Jul 30 '16 at 3:00
source share



All Articles