Reputation: 1853
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:org.apache.jasper.glassfish_2.2.2.v201205150955.jar@4
not found.
>!ENTRY org.eclipse.osgi 4 0 2014-12-17 09:57:31.373 !MESSAGE Bundle reference:file:org.apache.lucene.core_2.9.1.v201101211721.jar@4 not
found.
>!ENTRY org.eclipse.osgi 4 0 2014-12-17 09:57:31.439 !MESSAGE Bundle reference:file:org.eclipse.help.base_3.6.101.v201302041200.jar@4 not
found.
>!ENTRY org.eclipse.osgi 4 0 2014-12-17 09:57:31.439 !MESSAGE Bundle reference:file:org.eclipse.help.ui_3.5.201.v20130108-092756.jar@4 not
found.
>!ENTRY org.eclipse.osgi 4 0 2014-12-17 09:57:31.440 !MESSAGE Bundle reference:file:org.eclipse.help.webapp_3.6.101.v20130116-182509.jar@4
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.
Upvotes: 32
Views: 83887
Reputation: 6891
Answer for Xamarin;
Solution is same as answer from Aman Kumar Gupta. What causes problem is;
Normally as standard Xamarin installs Android Sdk on this path C:\Program Files (x86)\Android\android-sdk
But this path is not accepted by Android Studio because of space within the path. So I had to chance the path to be like C:\Android\android-sdk
after this Android Studio and Visual Studio shares the same path. But all of a sudden Android Device Monitor stopped working. Because as Aman Kumar Gupta said Jre
location wasn't recognized somehow. You can just copy the jre folder from jdk folder and paste into the Android/Sdk/tools/lib/monitor-x86_64/
. This should solve the problem
Upvotes: 1
Reputation: 141
I used jdk-12 in Windows-10 platform, and kinda faced the same problem. This is what I did:
Upvotes: 2
Reputation: 3011
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!
Upvotes: 9
Reputation: 12021
No need to restart android-studio. Just do this:
Upvotes: 2
Reputation: 47
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.
Upvotes: 1
Reputation: 11
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
Upvotes: 1
Reputation: 361
I had the same issue with Mac OS X.
To solve it:
Good to go!
Upvotes: 6
Reputation: 41
This is the problem due to updating SDK tools Android SDK Tools
Upvotes: 4
Reputation: 1563
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
Upvotes: 39
Reputation: 3907
If you are on windows try opening your Android Studio in Administrative Mode (Run as administrator)
Upvotes: 71