In Android Studio when I try running Android Device Monitor, I get the following error on log file:
>!SESSION 2014-12-17 09:57:30.625 ----------------------------------------------- eclipse.buildId=unknown java.version=1.8.0_25 java.vendor=Oracle Corporation BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=pt_BR Command-line arguments: -os win32 -ws win32 -arch x86_64 -data @noDefault >!ENTRY org.eclipse.osgi 4 0 2014-12-17 09:57:31.366 !MESSAGE Bundle reference:file:org.apache.ant_1.8.3.v201301120609/@4 not found. >!ENTRY org.eclipse.osgi 4 0 2014-12-17 09:57:31.372 !MESSAGE Bundle reference:file:[email protected]not found.
>!ENTRY org.eclipse.osgi 4 0 2014-12-17 09:57:31.373 !MESSAGE Bundle reference:file:[email protected] notfound.
>!ENTRY org.eclipse.osgi 4 0 2014-12-17 09:57:31.439 !MESSAGE Bundle reference:file:[email protected] notfound.
>!ENTRY org.eclipse.osgi 4 0 2014-12-17 09:57:31.439 !MESSAGE Bundle reference:file:[email protected] notfound.
>!ENTRY org.eclipse.osgi 4 0 2014-12-17 09:57:31.440 !MESSAGE Bundle reference:file:[email protected]not found.
... >!ENTRY org.eclipse.osgi 4 0 2014-12-17 09:57:32.218 !MESSAGE Application error !STACK 1 >java.io.IOException: The folder "C:\Users\SAA%20PC\.android\monitor-workspace\.metadata" is read-only. > at org.eclipse.core.runtime.internal.adaptor.BasicLocation.lock(BasicLocation.java:206) at org.eclipse.core.runtime.internal.adaptor.BasicLocation.set(BasicLocation.java:164) at org.eclipse.core.runtime.internal.adaptor.BasicLocation.set(BasicLocation.java:137) at com.android.ide.eclipse.monitor.MonitorApplication.start(MonitorApplication.java:53) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:353) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584) at org.eclipse.equinox.launcher.Main.run(Main.java:1438)
Anyone know what could it be? Thanks for any help.
If you are on windows try opening your Android Studio in Administrative Mode (Run as administrator)
Answer：
I encounter this problem before. I fixed this issue by killing or ending “monitior.exe” running process using Taskmanager in Windows. Then click ADM (Android Device Monitor) and it works
Answer：
I had the same issue with Mac OS X.
To solve it:
- Open a terminal window
- Navigate to your SDK
- Locate the ‘tools’ folder
- cd into it
- run: sudo ./monitor
- Type in your password
Good to go!
Answer：
This is due to the error that the android device monitor not able to locate the jre so in order to solve this :
please follow the following Steps:
Step 1 : In your android studio find the jdk path, then inside jdk locate the jre and copy it. (In case of Linux jre is located inside android studio folder)
Step 2 : After copying jre paste it inside the (Android/Sdk/tools/lib/monitor-x86_64/) i.e monitor-x86_64 directory
I tried this for linux operating system, Android device monitor started well without any error.
Thanks, Hope this will help to someone!
Answer：
This is the problem due to updating SDK tools Android SDK Tools
- close the Android Studio
- open the SDK Manager.exe from SDK folder
- Now install Android SDK tool in my case tool is Rev.24.3.2
- open Android Studio it will show new tool is available install it,install that one and try to restart it.
Answer：
No need to restart android-studio. Just do this:
- Navigate to C:\Android\sdk\tools.
- Find monitor.bat
- Right-click and Run as administrator
Answer：
restart the studio and Run as administrator works for me.
Answer：
you don’t need to restart android Studio only you need to open cmd as administrator and navigate to you SDK tools directory and write monitor
in my case
C:\Android\sdk\tools\monitor
Answer：
I had the same problem with my Android Studio 2.3.1 running on Ubuntu 14.04LTS. I was using openjdk 7. I updated it to openjdk 8 and viola! problem got solved.
Answer：
I used jdk-12 in Windows-10 platform, and kinda faced the same problem. This is what I did:
- Changed the monitor.exe file’s compatibility to “Run as Administrator”– Didn’t work
- Checked if the java path (JAVA_HOME and PATH) variables are set, in the Environment Variables. –Didn’t work
- Finally uninstalled jdk-12 and installed jdk-8 and altered the path (JAVA_HOME and PATH) variables in Environment Variables. — Worked!!!!! And then the adb opened without any error.
Tags: androidandroid, file
