device eclipse如何打开android monitor_如何打开android device monitor - CSDN
  • eclipse中,启动AVD后(前提),打开File Explorer空空如也(见下图)。 2.解决方法 step1.下载ddmlib.jar ddmlib.jar的下载位置 文件大小:282KB。 或者,百度云:http://pan.baidu.com/s/1sl4KaOP提取密码...

    1.问题

    在eclipse中,启动AVD后(前提),打开File Explorer空空如也(见下图)。

    2.解决方法

    step1.下载ddmlib.jar 

    ddmlib.jar的下载位置 
    文件大小:282KB。

    或者,百度云:http://pan.baidu.com/s/1sl4KaOP 提取密码:sygc

    step2.在eclipse下搜索ddmlib.jar 

              我的路径:D:\Java\eclipse-SDK-4.2.2-win32-x86_64\configuration\org.eclipse.osgi\bundles\241\1\.cp\libs

    step3.替换ddmlib.jar

         先关闭AVD,关闭Eclipse。

         用刚刚下载的ddmlib.jar 替换刚刚step2中搜索到的ddmlib.jar 的路径。

         再次启动Eclipse和AVD,奇迹出现了。

       

     

    3.参考:

    https://blog.csdn.net/u013553529/article/details/54292956

    展开全文
  • Android Studio中打开Android Device Monitor时报以下错误时(Android-SDK\tools\lib\monitor-x86_64\configuration\1491536029820.log),请关闭Android Studio后以管理员的模式打开Android Studio后即可解决此...
    在Android Studio中打开Android Device Monitor时报以下错误时(Android-SDK\tools\lib\monitor-x86_64\configuration\1491536029820.log),请关闭Android Studio后以管理员的模式打开Android Studio后即可解决此问题。

    !SESSION 2017-04-07 11:33:49.545 -----------------------------------------------
    eclipse.buildId=unknown
    java.version=1.8.0_112-release
    java.vendor=JetBrains s.r.o
    BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=zh_CN
    Command-line arguments:  -os win32 -ws win32 -arch x86_64 -data @noDefault

    !ENTRY org.eclipse.osgi 4 0 2017-04-07 11:33:50.420
    !MESSAGE Bundle reference:file:org.apache.ant_1.8.3.v201301120609/@4 not found.

    !ENTRY org.eclipse.osgi 4 0 2017-04-07 11:33:50.438
    !MESSAGE Bundle reference:file:org.apache.jasper.glassfish_2.2.2.v201205150955.jar@4 not found.

    !ENTRY org.eclipse.osgi 4 0 2017-04-07 11:33:50.455
    !MESSAGE Bundle reference:file:org.apache.lucene.core_2.9.1.v201101211721.jar@4 not found.

    !ENTRY org.eclipse.osgi 4 0 2017-04-07 11:33:50.552
    !MESSAGE Bundle reference:file:org.eclipse.help.base_3.6.101.v201302041200.jar@4 not found.

    !ENTRY org.eclipse.osgi 4 0 2017-04-07 11:33:50.558
    !MESSAGE Bundle reference:file:org.eclipse.help.ui_3.5.201.v20130108-092756.jar@4 not found.

    !ENTRY org.eclipse.osgi 4 0 2017-04-07 11:33:50.563
    !MESSAGE Bundle reference:file:org.eclipse.help.webapp_3.6.101.v20130116-182509.jar@4 not found.

    !ENTRY org.eclipse.osgi 4 0 2017-04-07 11:33:50.571
    !MESSAGE Bundle reference:file:org.eclipse.jetty.server_8.1.3.v20120522.jar@4 not found.

    !ENTRY org.eclipse.osgi 4 0 2017-04-07 11:33:50.582
    !MESSAGE Bundle reference:file:org.eclipse.platform.doc.user_4.2.2.v20130121-200410.jar@4 not found.

    !ENTRY org.eclipse.osgi 4 0 2017-04-07 11:33:50.588
    !MESSAGE Bundle reference:file:org.eclipse.team.core_3.6.100.v20120524-0627.jar@4 not found.

    !ENTRY org.eclipse.osgi 4 0 2017-04-07 11:33:50.593
    !MESSAGE Bundle reference:file:org.eclipse.team.ui_3.6.201.v20130125-135424.jar@4 not found.

    !ENTRY org.eclipse.osgi 4 0 2017-04-07 11:33:50.600
    !MESSAGE Bundle reference:file:org.eclipse.ui.cheatsheets_3.4.200.v20120521-2344.jar@4 not found.

    !ENTRY org.eclipse.osgi 4 0 2017-04-07 11:33:50.606
    !MESSAGE Bundle reference:file:org.eclipse.ui.intro_3.4.200.v20120521-2344.jar@4 not found.

    !ENTRY org.eclipse.osgi 2 0 2017-04-07 11:33:52.114
    !MESSAGE One or more bundles are not resolved because the following root constraints are not resolved:
    !SUBENTRY 1 org.eclipse.osgi 2 0 2017-04-07 11:33:52.114
    !MESSAGE Bundle initial@reference:file:plugins/org.eclipse.platform_4.2.2.v201302041200/ was not resolved.
    !SUBENTRY 2 org.eclipse.platform 2 0 2017-04-07 11:33:52.114
    !MESSAGE Missing required bundle org.eclipse.ui.intro_[3.2.0,4.0.0).
    !SUBENTRY 2 org.eclipse.platform 2 0 2017-04-07 11:33:52.114
    !MESSAGE Missing required capability Require-Capability: osgi.ee; filter="(|(&(osgi.ee=JavaSE)(version=1.4))(&(osgi.ee=CDC/Foundation)(version=1.0))(&(osgi.ee=JavaSE)(version=1.3)))".
    !SUBENTRY 1 org.eclipse.osgi 2 0 2017-04-07 11:33:52.114
    !MESSAGE Bundle initial@reference:file:plugins/org.eclipse.equinox.http.jetty_3.0.1.v20121109-203239.jar was not resolved.
    !SUBENTRY 2 org.eclipse.equinox.http.jetty 2 0 2017-04-07 11:33:52.114
    !MESSAGE Missing imported package org.eclipse.jetty.server.handler_[8.0.0,9.0.0).
    !SUBENTRY 2 org.eclipse.equinox.http.jetty 2 0 2017-04-07 11:33:52.114
    !MESSAGE Missing imported package org.eclipse.jetty.server.session_[8.0.0,9.0.0).
    !SUBENTRY 2 org.eclipse.equinox.http.jetty 2 0 2017-04-07 11:33:52.114
    !MESSAGE Missing imported package org.eclipse.jetty.server.ssl_[8.0.0,9.0.0).
    !SUBENTRY 2 org.eclipse.equinox.http.jetty 2 0 2017-04-07 11:33:52.114
    !MESSAGE Missing imported package org.eclipse.jetty.server_[8.0.0,9.0.0).
    !SUBENTRY 2 org.eclipse.equinox.http.jetty 2 0 2017-04-07 11:33:52.114
    !MESSAGE Missing imported package org.eclipse.jetty.server.bio_[8.0.0,9.0.0).
    !SUBENTRY 2 org.eclipse.equinox.http.jetty 2 0 2017-04-07 11:33:52.114
    !MESSAGE Missing imported package org.eclipse.jetty.server.nio_[8.0.0,9.0.0).
    !SUBENTRY 1 org.eclipse.osgi 2 0 2017-04-07 11:33:52.114
    !MESSAGE Bundle initial@reference:file:plugins/org.eclipse.ltk.ui.refactoring_3.7.0.v20120523-1543.jar was not resolved.
    !SUBENTRY 2 org.eclipse.ltk.ui.refactoring 2 0 2017-04-07 11:33:52.114
    !MESSAGE Missing required bundle org.eclipse.team.ui_[3.4.100,4.0.0).
    !SUBENTRY 2 org.eclipse.ltk.ui.refactoring 2 0 2017-04-07 11:33:52.114
    !MESSAGE Missing required bundle org.eclipse.team.core_[3.4.100,4.0.0).
    !SUBENTRY 1 org.eclipse.osgi 2 0 2017-04-07 11:33:52.114
    !MESSAGE Bundle initial@reference:file:plugins/org.eclipse.equinox.jsp.jasper.registry_1.0.300.v20120912-130548.jar was not resolved.
    !SUBENTRY 2 org.eclipse.equinox.jsp.jasper.registry 2 0 2017-04-07 11:33:52.115
    !MESSAGE Missing required capability Require-Capability: osgi.ee; filter="(|(&(osgi.ee=CDC/Foundation)(version=1.0))(&(osgi.ee=JavaSE)(version=1.3)))".
    !SUBENTRY 1 org.eclipse.osgi 2 0 2017-04-07 11:33:52.115
    !MESSAGE Bundle initial@reference:file:plugins/org.eclipse.jetty.security_8.1.3.v20120522.jar was not resolved.
    !SUBENTRY 2 org.eclipse.jetty.security 2 0 2017-04-07 11:33:52.115
    !MESSAGE Missing imported package org.eclipse.jetty.server_[8.1.0,9.0.0).
    !SUBENTRY 2 org.eclipse.jetty.security 2 0 2017-04-07 11:33:52.115
    !MESSAGE Missing imported package org.eclipse.jetty.server.handler_[8.1.0,9.0.0).
    !SUBENTRY 1 org.eclipse.osgi 2 0 2017-04-07 11:33:52.115
    !MESSAGE Bundle initial@reference:file:plugins/org.eclipse.ui.intro.universal_3.2.600.v20120912-155524/ was not resolved.
    !SUBENTRY 2 org.eclipse.ui.intro.universal 2 0 2017-04-07 11:33:52.115
    !MESSAGE Missing required bundle org.eclipse.ui.intro_[3.4.0,4.0.0).
    !SUBENTRY 1 org.eclipse.osgi 2 0 2017-04-07 11:33:52.115
    !MESSAGE Bundle initial@reference:file:plugins/org.apache.lucene.analysis_2.9.1.v201101211721.jar was not resolved.
    !SUBENTRY 2 org.apache.lucene.analysis 2 0 2017-04-07 11:33:52.115
    !MESSAGE Missing required bundle org.apache.lucene.core_[2.9.1,3.0.0).
    !SUBENTRY 1 org.eclipse.osgi 2 0 2017-04-07 11:33:52.115
    !MESSAGE Bundle initial@reference:file:plugins/org.apache.lucene_2.9.1.v201101211721.jar was not resolved.
    !SUBENTRY 2 org.apache.lucene 2 0 2017-04-07 11:33:52.115
    !MESSAGE Missing required bundle org.apache.lucene.core_[2.9.1,3.0.0).
    !SUBENTRY 1 org.eclipse.osgi 2 0 2017-04-07 11:33:52.115
    !MESSAGE Bundle initial@reference:file:plugins/org.eclipse.jetty.servlet_8.1.3.v20120522.jar was not resolved.
    !SUBENTRY 2 org.eclipse.jetty.servlet 2 0 2017-04-07 11:33:52.115
    !MESSAGE Missing imported package org.eclipse.jetty.server.session_[8.1.0,9.0.0).
    !SUBENTRY 2 org.eclipse.jetty.servlet 2 0 2017-04-07 11:33:52.115
    !MESSAGE Missing imported package org.eclipse.jetty.server_[8.1.0,9.0.0).
    !SUBENTRY 2 org.eclipse.jetty.servlet 2 0 2017-04-07 11:33:52.115
    !MESSAGE Missing imported package org.eclipse.jetty.server.ssl_[8.1.0,9.0.0).
    !SUBENTRY 2 org.eclipse.jetty.servlet 2 0 2017-04-07 11:33:52.115
    !MESSAGE Missing imported package org.eclipse.jetty.server.handler_[8.1.0,9.0.0).
    !SUBENTRY 2 org.eclipse.jetty.servlet 2 0 2017-04-07 11:33:52.115
    !MESSAGE Missing imported package org.eclipse.jetty.server.nio_[8.1.0,9.0.0).
    !SUBENTRY 1 org.eclipse.osgi 2 0 2017-04-07 11:33:52.115
    !MESSAGE Bundle initial@reference:file:plugins/org.eclipse.equinox.jsp.jasper_1.0.400.v20120912-130548.jar was not resolved.
    !SUBENTRY 2 org.eclipse.equinox.jsp.jasper 2 0 2017-04-07 11:33:52.115
    !MESSAGE Missing imported package org.apache.jasper.servlet_[0.0.0,6.0.0).
    !SUBENTRY 2 org.eclipse.equinox.jsp.jasper 2 0 2017-04-07 11:33:52.115
    !MESSAGE Missing required capability Require-Capability: osgi.ee; filter="(|(&(osgi.ee=CDC/Foundation)(version=1.0))(&(osgi.ee=JavaSE)(version=1.3)))".

    !ENTRY org.eclipse.osgi 2 0 2017-04-07 11:33:52.179
    !MESSAGE The following is a complete list of bundles which are not resolved, see the prior log entry for the root cause if it exists:
    !SUBENTRY 1 org.eclipse.osgi 2 0 2017-04-07 11:33:52.180
    !MESSAGE Bundle org.apache.lucene_2.9.1.v201101211721 [24] was not resolved.
    !SUBENTRY 2 org.apache.lucene 2 0 2017-04-07 11:33:52.180
    !MESSAGE Missing required bundle org.apache.lucene.core_[2.9.1,3.0.0).
    !SUBENTRY 2 org.apache.lucene 2 0 2017-04-07 11:33:52.180
    !MESSAGE Missing optionally required bundle org.apache.lucene.analysis_[2.9.1,3.0.0).
    !SUBENTRY 2 org.apache.lucene 2 0 2017-04-07 11:33:52.180
    !MESSAGE Missing optionally required bundle org.apache.lucene.highlighter_[2.9.1,3.0.0).
    !SUBENTRY 2 org.apache.lucene 2 0 2017-04-07 11:33:52.180
    !MESSAGE Missing optionally required bundle org.apache.lucene.memory_[2.9.1,3.0.0).
    !SUBENTRY 2 org.apache.lucene 2 0 2017-04-07 11:33:52.180
    !MESSAGE Missing optionally required bundle org.apache.lucene.queries_[2.9.1,3.0.0).
    !SUBENTRY 2 org.apache.lucene 2 0 2017-04-07 11:33:52.180
    !MESSAGE Missing optionally required bundle org.apache.lucene.snowball_[2.9.1,3.0.0).
    !SUBENTRY 2 org.apache.lucene 2 0 2017-04-07 11:33:52.180
    !MESSAGE Missing optionally required bundle org.apache.lucene.spellchecker_[2.9.1,3.0.0).
    !SUBENTRY 2 org.apache.lucene 2 0 2017-04-07 11:33:52.180
    !MESSAGE Missing optionally required bundle org.apache.lucene.misc_[2.9.1,3.0.0).
    !SUBENTRY 1 org.eclipse.osgi 2 0 2017-04-07 11:33:52.180
    !MESSAGE Bundle org.apache.lucene.analysis_2.9.1.v201101211721 [25] was not resolved.
    !SUBENTRY 2 org.apache.lucene.analysis 2 0 2017-04-07 11:33:52.180
    !MESSAGE Missing required bundle org.apache.lucene.core_[2.9.1,3.0.0).
    !SUBENTRY 1 org.eclipse.osgi 2 0 2017-04-07 11:33:52.180
    !MESSAGE Bundle org.eclipse.equinox.http.jetty_3.0.1.v20121109-203239 [89] was not resolved.
    !SUBENTRY 2 org.eclipse.equinox.http.jetty 2 0 2017-04-07 11:33:52.180
    !MESSAGE Missing imported package org.eclipse.jetty.server_[8.0.0,9.0.0).
    !SUBENTRY 2 org.eclipse.equinox.http.jetty 2 0 2017-04-07 11:33:52.180
    !MESSAGE Missing imported package org.eclipse.jetty.server.bio_[8.0.0,9.0.0).
    !SUBENTRY 2 org.eclipse.equinox.http.jetty 2 0 2017-04-07 11:33:52.180
    !MESSAGE Missing imported package org.eclipse.jetty.server.handler_[8.0.0,9.0.0).
    !SUBENTRY 2 org.eclipse.equinox.http.jetty 2 0 2017-04-07 11:33:52.180
    !MESSAGE Missing imported package org.eclipse.jetty.server.nio_[8.0.0,9.0.0).
    !SUBENTRY 2 org.eclipse.equinox.http.jetty 2 0 2017-04-07 11:33:52.180
    !MESSAGE Missing imported package org.eclipse.jetty.server.session_[8.0.0,9.0.0).
    !SUBENTRY 2 org.eclipse.equinox.http.jetty 2 0 2017-04-07 11:33:52.180
    !MESSAGE Missing imported package org.eclipse.jetty.server.ssl_[8.0.0,9.0.0).
    !SUBENTRY 2 org.eclipse.equinox.http.jetty 2 0 2017-04-07 11:33:52.180
    !MESSAGE Missing imported package org.eclipse.jetty.servlet_[8.0.0,9.0.0).
    !SUBENTRY 1 org.eclipse.osgi 2 0 2017-04-07 11:33:52.180
    !MESSAGE Bundle org.eclipse.equinox.jsp.jasper_1.0.400.v20120912-130548 [92] was not resolved.
    !SUBENTRY 2 org.eclipse.equinox.jsp.jasper 2 0 2017-04-07 11:33:52.180
    !MESSAGE Missing imported package org.apache.jasper.servlet_[0.0.0,6.0.0).
    !SUBENTRY 2 org.eclipse.equinox.jsp.jasper 2 0 2017-04-07 11:33:52.180
    !MESSAGE Missing required capability Require-Capability: osgi.ee; filter="(|(&(osgi.ee=CDC/Foundation)(version=1.0))(&(osgi.ee=JavaSE)(version=1.3)))".
    !SUBENTRY 1 org.eclipse.osgi 2 0 2017-04-07 11:33:52.181
    !MESSAGE Bundle org.eclipse.equinox.jsp.jasper.registry_1.0.300.v20120912-130548 [93] was not resolved.
    !SUBENTRY 2 org.eclipse.equinox.jsp.jasper.registry 2 0 2017-04-07 11:33:52.181
    !MESSAGE Missing imported package org.eclipse.equinox.jsp.jasper_0.0.0.
    !SUBENTRY 2 org.eclipse.equinox.jsp.jasper.registry 2 0 2017-04-07 11:33:52.181
    !MESSAGE Missing required capability Require-Capability: osgi.ee; filter="(|(&(osgi.ee=CDC/Foundation)(version=1.0))(&(osgi.ee=JavaSE)(version=1.3)))".
    !SUBENTRY 1 org.eclipse.osgi 2 0 2017-04-07 11:33:52.181
    !MESSAGE Bundle org.eclipse.jetty.security_8.1.3.v20120522 [136] was not resolved.
    !SUBENTRY 2 org.eclipse.jetty.security 2 0 2017-04-07 11:33:52.181
    !MESSAGE Missing imported package org.eclipse.jetty.server_[8.1.0,9.0.0).
    !SUBENTRY 2 org.eclipse.jetty.security 2 0 2017-04-07 11:33:52.181
    !MESSAGE Missing imported package org.eclipse.jetty.server.handler_[8.1.0,9.0.0).
    !SUBENTRY 1 org.eclipse.osgi 2 0 2017-04-07 11:33:52.181
    !MESSAGE Bundle org.eclipse.jetty.servlet_8.1.3.v20120522 [137] was not resolved.
    !SUBENTRY 2 org.eclipse.jetty.servlet 2 0 2017-04-07 11:33:52.181
    !MESSAGE Missing optionally imported package org.eclipse.jetty.jmx_8.0.0.
    !SUBENTRY 2 org.eclipse.jetty.servlet 2 0 2017-04-07 11:33:52.181
    !MESSAGE Missing imported package org.eclipse.jetty.security_[8.1.0,9.0.0).
    !SUBENTRY 2 org.eclipse.jetty.servlet 2 0 2017-04-07 11:33:52.181
    !MESSAGE Missing imported package org.eclipse.jetty.server_[8.1.0,9.0.0).
    !SUBENTRY 2 org.eclipse.jetty.servlet 2 0 2017-04-07 11:33:52.181
    !MESSAGE Missing imported package org.eclipse.jetty.server.handler_[8.1.0,9.0.0).
    !SUBENTRY 2 org.eclipse.jetty.servlet 2 0 2017-04-07 11:33:52.181
    !MESSAGE Missing imported package org.eclipse.jetty.server.nio_[8.1.0,9.0.0).
    !SUBENTRY 2 org.eclipse.jetty.servlet 2 0 2017-04-07 11:33:52.181
    !MESSAGE Missing imported package org.eclipse.jetty.server.session_[8.1.0,9.0.0).
    !SUBENTRY 2 org.eclipse.jetty.servlet 2 0 2017-04-07 11:33:52.181
    !MESSAGE Missing imported package org.eclipse.jetty.server.ssl_[8.1.0,9.0.0).
    !SUBENTRY 1 org.eclipse.osgi 2 0 2017-04-07 11:33:52.181
    !MESSAGE Bundle org.eclipse.ltk.ui.refactoring_3.7.0.v20120523-1543 [145] was not resolved.
    !SUBENTRY 2 org.eclipse.ltk.ui.refactoring 2 0 2017-04-07 11:33:52.181
    !MESSAGE Missing required bundle org.eclipse.team.core_[3.4.100,4.0.0).
    !SUBENTRY 2 org.eclipse.ltk.ui.refactoring 2 0 2017-04-07 11:33:52.181
    !MESSAGE Missing required bundle org.eclipse.team.ui_[3.4.100,4.0.0).
    !SUBENTRY 1 org.eclipse.osgi 2 0 2017-04-07 11:33:52.181
    !MESSAGE Bundle org.eclipse.platform_4.2.2.v201302041200 [148] was not resolved.
    !SUBENTRY 2 org.eclipse.platform 2 0 2017-04-07 11:33:52.182
    !MESSAGE Missing required bundle org.eclipse.ui.intro_[3.2.0,4.0.0).
    !SUBENTRY 2 org.eclipse.platform 2 0 2017-04-07 11:33:52.182
    !MESSAGE Missing optionally required bundle org.eclipse.ui.cheatsheets_[3.2.0,4.0.0).
    !SUBENTRY 2 org.eclipse.platform 2 0 2017-04-07 11:33:52.182
    !MESSAGE Missing required capability Require-Capability: osgi.ee; filter="(|(&(osgi.ee=JavaSE)(version=1.4))(&(osgi.ee=CDC/Foundation)(version=1.0))(&(osgi.ee=JavaSE)(version=1.3)))".
    !SUBENTRY 1 org.eclipse.osgi 2 0 2017-04-07 11:33:52.182
    !MESSAGE Bundle org.eclipse.search_3.8.0.v20120523-1540 [150] was not resolved.
    !SUBENTRY 2 org.eclipse.search 2 0 2017-04-07 11:33:52.182
    !MESSAGE Missing required bundle org.eclipse.ltk.ui.refactoring_[3.5.0,4.0.0).
    !SUBENTRY 1 org.eclipse.osgi 2 0 2017-04-07 11:33:52.182
    !MESSAGE Bundle org.eclipse.ui.intro.universal_3.2.600.v20120912-155524 [162] was not resolved.
    !SUBENTRY 2 org.eclipse.ui.intro.universal 2 0 2017-04-07 11:33:52.182
    !MESSAGE Missing required bundle org.eclipse.ui.intro_[3.4.0,4.0.0).
    !SUBENTRY 1 org.eclipse.osgi 2 0 2017-04-07 11:33:52.182
    !MESSAGE Bundle org.eclipse.ui.navigator.resources_3.4.400.v20120705-114010 [164] was not resolved.
    !SUBENTRY 2 org.eclipse.ui.navigator.resources 2 0 2017-04-07 11:33:52.182
    !MESSAGE Missing required bundle org.eclipse.ltk.ui.refactoring_[3.5.0,4.0.0).

    !ENTRY org.eclipse.osgi 4 0 2017-04-07 11:33:52.190
    !MESSAGE Application error
    !STACK 1
    java.lang.NullPointerException
    at org.eclipse.core.runtime.URIUtil.toURI(URIUtil.java:280)
    at org.eclipse.e4.ui.internal.workbench.ResourceHandler.loadMostRecentModel(ResourceHandler.java:127)
    at org.eclipse.e4.ui.internal.workbench.swt.E4Application.loadApplicationModel(E4Application.java:370)
    at org.eclipse.e4.ui.internal.workbench.swt.E4Application.createE4Workbench(E4Application.java:220)
    at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:557)
    at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
    at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:543)
    at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
    at com.android.ide.eclipse.monitor.MonitorApplication.start(MonitorApplication.java:63)
    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(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:498)
    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)





    展开全文
  • 问题1:解决打开Android Device Monitor之后一片空白问题描述将手机升级到Android 7.0后,打开android Device Monitor(DDMS)后,File Explorer中显示一片空白。如下:Android Device Monitor (DDMS)的版本如下:不...

    问题1:解决打开Android Device Monitor之后一片空白

    问题描述

    将手机升级到Android 7.0后,打开android Device Monitor(DDMS)后,File Explorer中显示一片空白。如下:

    无法显示目录树

    Android Device Monitor (DDMS)的版本如下:

    Android Device Monitor的版本 25.1.7

    不管用monitor.bat(注ddms.bat已弃用)还是通过Android Studio中的图标启动(如下图),都是一样的问题。

    点击蓝色框中的button,启动Android Device Monitor。
    这里写图片描述

    解决方法

    情况一:通过monitor.bat或者Android Studio中图标启动时**

    • 第一步:下载ddmlib.jar

      ddmlib.jar的下载位置
      文件大小:282KB。

      或者,百度云:http://pan.baidu.com/s/1sl4KaOP 提取密码:sygc

    • 第二步:在Android SDK的tools目录中搜索ddmlib.jar

      当前目录为Android SDK的tools目录。

      $ find . -iname *ddmlib*
      ./lib/ddmlib.jar   (不用替换它)
      ./lib/monitor-x86_64/configuration/org.eclipse.osgi/bundles/2/1/.cp/libs/ddmlib.jar123123

      可能会搜出多个,我们要替换的是tools/lib/monitor-x86_64/configuration/org.eclipse.osgi/bundles/2/1/.cp/libs/ddmlib.jar

      有可能你的目录与这个不同,请以实际目录位置为准。

    • 第三步:用刚才下载到的ddmlib.jar替换刚搜到的ddmlib.jar

      需要注意的是,替换的时候,先将Android Device Monitor关掉。

    • 第四步:再次打开Android Device Monitor,就可以看到目录树了(如下)

      这里写图片描述

    情况二:在eclipse中显示File Explorer**

    前提是下载了ddmlib.jar。

    • 第一步:搜索eclipse 中的 ddmlib.jar

    例如,在我的eclipse中,ddmlib.jar在eclipse/configuration/org.eclipse.osgi/8/0/.cp/libs目录下。

    $ find . -iname ddmlib.jar
    ./configuration/org.eclipse.osgi/8/0/.cp/libs/ddmlib.jar1212

    你的ddmlib.jar所在的位置可能与我的不同,请以实际目录位置为准。

    • 第二步:用刚才下载到的ddmlib.jar替换刚搜到的ddmlib.jar

    • 第三步:重新打开eclipse,File Explorer就可以显示正常了

      这里写图片描述

    问题2:关于操作db文件导出Failed to pull selection: open failed: Permission denied问题的处理方法

    问题描述

    在遇到这个问题之前,你可能连data这个目录都打不开。。

    这里写图片描述

    解决办法

    对此,解决办法是去到安卓的adb目录/Android/sdk/platform-tools下按住Shift右键“在此处打开命令行窗口”,进入命令行窗口后:需要操作的命令有:
    1、adb shell进入shell模式

    adb shell

    2、获得所有root权限

    su

    3、先把文件夹权限全部打开

    chmod  -R 777 /data/  

    4、给里边的db文件权限设置成可读可写可操作

    chmod  777 /data/data/(项目全包名)/databases/xxx.db

    5、cd命令进入db文件所在目录:

    cat my_datbase_name.db > /sdcard/my_database_name_temp.db

    复制内容到一个temp文件中去,这一步很关键,目的是为了绕过有时候对文件直接pull的话,会找不到文件目录这一后面会出现的情况。

    6、运行两次exit直接返回到正常的终端提示符

    7、将temp文件拉出来,拉到你adb.exe存放的目录下,避免直接与数据库文件做操作,或者你也可以新建一个目录(事先新建好哟)
    adb pull /sdcard/my_database_name_temp.db (其他目录如 F:/db)


    补充上面提到的会出现的问题:
    你如果用命令 adb pull /data/data/全包名/databases/xxx.db将数据库db文件拉出来的话,会找不到目录的
    error
    提取到的数据库文件可以用SQLite打开,直接拖拽到里面就可以显示
    下面是我成功提取数据库文件sims.db的截图:
    这里写图片描述

    问题3:利用ddms查看应用的sharedprefence文件

    问题描述:

    当我使用DDMS查看file系统的时候,发现我明明有这个应用,为什么找不到这个应用呢?好神奇!

    解决办法

    没办法,既然GUI不给力,我们只能进入命令行来看了

    D:>adb shell
    zsl865:/ $ su
    zsl865:/ # chmod -R 777 data/data/

    后边基本就是linux的操作了,然后打开了data/data居然找到了之前的应用,然后进去之后发现了对应的sp文件

    展开全文
  • Android Device Monitor打开失败

    前提:因为工作电脑卡的不行,所以系统硬盘就切换为固态硬盘,就重装系统了,升级完了之后,觉得焕然一新,轻松+愉快;前几天准备用Android Device Monitor,却发现打不开直接报错了(囧哭)
    正好国庆前一天,工作不是很紧张,就把先这个问题解决了,避免影响之后的工作

    报错log(在目录sdk/tools/lib/monitor-x86_64/×××.log)

    !ENTRY org.eclipse.osgi 4 0 2017-09-30 16:23:09.769
    !MESSAGE Application error
    !STACK 1
    org.eclipse.core.runtime.CoreException: Plug-in com.android.ide.eclipse.monitor was unable to load class com.android.ide.eclipse.monitor.MonitorApplication.
        at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.throwException(RegistryStrategyOSGI.java:194)
        at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:176)
        at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:905)
        at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243)
        at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55)
        at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:191)
        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(NativeMethodAccessorImpl.java:57)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:606)
        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)
        at org.eclipse.equinox.launcher.Main.main(Main.java:1414)
    Caused by: org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter$TerminatingClassNotFoundException: An error occurred while automatically activating bundle com.android.ide.eclipse.monitor (5).
        at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:122)
        at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:469)
        at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:216)
        at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:395)
        at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:464)
        at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
        at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
        at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
        at org.eclipse.osgi.internal.loader.BundleLoader.loadClass(BundleLoader.java:340)
        at org.eclipse.osgi.framework.internal.core.BundleHost.loadClass(BundleHost.java:229)
        at org.eclipse.osgi.framework.internal.core.AbstractBundle.loadClass(AbstractBundle.java:1212)
        at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:174)
        ... 16 more
    Caused by: org.osgi.framework.BundleException: The activator com.android.ide.eclipse.monitor.MonitorPlugin for bundle com.android.ide.eclipse.monitor is invalid
        at org.eclipse.osgi.framework.internal.core.AbstractBundle.loadBundleActivator(AbstractBundle.java:172)
        at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:679)
        at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:381)
        at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:300)
        at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:440)
        at org.eclipse.osgi.internal.loader.BundleLoader.setLazyTrigger(BundleLoader.java:263)
        at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:107)
        ... 28 more
    Caused by: java.lang.UnsupportedClassVersionError: com/android/prefs/AndroidLocation$AndroidLocationException : Unsupported major.minor version 52.0
        at java.lang.ClassLoader.defineClass1(Native Method)
        at java.lang.ClassLoader.defineClass(ClassLoader.java:803)
        at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.defineClass(DefaultClassLoader.java:188)
        at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.defineClassHoldingLock(ClasspathManager.java:632)
        at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.defineClass(ClasspathManager.java:607)
        at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findClassImpl(ClasspathManager.java:568)
        at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClassImpl(ClasspathManager.java:492)
        at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:465)
        at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:216)
        at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:395)
        at org.eclipse.osgi.internal.loader.SingleSourcePackage.loadClass(SingleSourcePackage.java:35)
        at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:461)
        at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
        at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
        at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
        at com.android.ide.eclipse.monitor.MonitorPlugin.<clinit>(MonitorPlugin.java:28)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
        at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
        at java.lang.Class.newInstance(Class.java:383)
        at org.eclipse.osgi.framework.internal.core.AbstractBundle.loadBundleActivator(AbstractBundle.java:167)
        ... 34 more

    根据log google搜索解决方案

    先根据下面log关键字搜索

    Caused by: java.lang.UnsupportedClassVersionError: com/android/prefs/AndroidLocation$AndroidLocationException : Unsupported major.minor version 52.0

    https://stackoverflow.com/questions/42661578/android-device-monitor-will-not-launch-either-from-android-studio-or-from-termi
    给出的解决方式是:安装java8
    于是将本地的java7,切换为java8,但是依旧无效;

    切换关键字搜索:

    org.eclipse.core.runtime.CoreException: Plug-in com.android.ide.eclipse.monitor was unable to load class com.android.ide.eclipse.monitor.MonitorApplication.、

    https://issuetracker.google.com/issues/36970884
    给出的解决方案是下载SDK之前老的版本,文档里有给出可以老的sdk版本
    Currently the only workaround is to download the previous version of SDK separately, and replace the contents of tools/lib/monitor folder with the one from the previous version. You can get the previous version here:

    https://dl.google.com/android/android-sdk_r21.1-windows.zip
    https://dl.google.com/android/android-sdk_r21.1-macosx.zip
    https://dl.google.com/android/android-sdk_r21.1-linux.tgz

    亲证,替换sdk/tools文件夹即可成功打开Android Device Monitor

    后记

    将java8 切换至java7之后,依旧有效,看来这个问题跟java版本没有问题

    作为Android新进菜鸟一枚,多谢大神们给出的解决方案,虽只是搬运别人的想法,但整理到自己的博客是为了方便遇到此类问题能够快速找到解决方案

    展开全文
  • 启动Android Device Monitor,报错An error has occurred. See the log file xxxx. 在log file中找到error报错“Unable to acquire application service. Ensure that the org.eclipse.core.runtime bundle is ...
  • Eclipse开发Android真机调式经常遇到DeviceMonitor Connection attempts问题解决办法: 进入命令终端win+r adb kill adb restart 无用 adb devices不显示连接的设备或者没有设备连接 进入Eclipse安装...
  • 7.0后,打开Android Device Monitor(DDMS)后,File Explorer中显示一片空白。如下: Android Device Monitor (DDMS)的版本如下: 不管用monitor.bat(注ddms.bat已弃用)还是通过Android Studio中的图标...
  • 版权声明:本文为 Abracadabra(爱博客...将手机升级到Android 7.0后,打开Android Device Monitor(DDMS)后,File Explorer中显示一片空白。如下: Android Device Monitor (DDMS)的版本如下: 不管用m
  • [2016-05-27 01:06:37 - ddmlib] 你的主机中的软件中止了一个已建立的连接。 java.io.IOException: 你的主机中的软件中止了一个已建立的连接。 at sun.nio.ch.SocketDispatcher.write0(Native Method) ...
  • mac androidstudio无法打开android device monitor,生成一个出错日志,网上的解决方式没生效,我的解决方式是: mac自带的java版本是1.6,升级到1.8就解决了
  • 找不到 lib/libmonitor

    2019-10-22 11:16:18
    运行C:\Users\pradmin\AppData\Local\Android\Sdk\tools\monitor.bat,报上面的错 C:\Users\pradmin\AppData\Local\Android\Sdk\tools\bin\archquery.bat 将archquery.bat文件,回显打开 ::@if "%DEBUG%" == ...
  • Android Device Monitor 因为AS版本升级已经失效 解决办法 找到AS->File->Settings->Android SDK中的Android SDK Location路径,双击monitor.bat 可能因为我的电脑有eclipse的原因,打开eclipse并提示...
  • 1. 安装genymotion: ... 2. 设置使用adb Setting--adb--选择sdk的目录 3. apimonitor https://code.google.com/p/droidbox/wiki/APIMonitor ...4. Eclipse 安装genymotion的插件 通过update site在线安装 ...
  • 如何在Android Studio和eclipse中查看File Explorer视图 1.在eclipse中的File Explorer视图位置 window --> Show View --> Other --> Android --> ...Tools --> Android --> Android Device Monitor --> File Explorer
  • 平台: Win7x64bit运行环境: JDK9.0.1, JRE9.0.1现象:前期使用AS 2.2版本,可以正常打开android device monitor,删除低版本升级为3.0并使用原先的配置文件后,无法打开android device monitor并弹出窗口显示打印错误到...
  • 很显然,android studio提供了通过Android Monitor -> Memrory来分析app的内存使用情况,但是更多的系统级别的分析,对我们定位类存...通过android studio菜单Tool-->Android->Android Device Monitor打开Android De
  • 解决ADB启动问题--------Failed to initialize Monitor Thread:...重装了系统,再打开eclipse时就报错了,ddms初始化错误,一直在死循环里,报错-Failed to initialize Monitor Thread:unable to establish loopba
  • 1、开启设备开发者模式以及USB调试 2、打开androidSDK安装路径->tools->monitor.bat
  • 1. 问题将手机升级到Android 7.0后,打开Android Device Monitor(DDMS)后,File Explorer中显示一片空白。如下:Android Device Monitor (DDMS)的版本如下:不管用monitor.bat(注ddms.bat已弃用)还是通过Android...
1 2 3 4 5 ... 20
收藏数 5,188
精华内容 2,075
关键字:

device eclipse如何打开android monitor