精华内容
下载资源
问答
  • Android Studio 3.0找不到Android Device Monitor

    万次阅读 多人点赞 2018-05-29 12:52:20
    什么Android Studio 3.0中找不到Android Device Monitor? 因为自Android Studio 3.0开始弃用Android Device Monitor,Android Developers官网上的原话: Android Device Monitor is a standalone tool that...

    为什么Android Studio 3.0中找不到Android Device Monitor?

    因为自Android Studio 3.0开始弃用Android Device Monitor,Android Developers官网上的原话是:

    Android Device Monitor is a standalone tool that provides a UI for several Android app debugging and analysis tools.
    However, most components of the Android Device Monitor are deprecated in favor of updated tools available in Android Studio 3.0 and higher. The table below helps you decide which developer tools you should use.

    译文:

    Android设备监视器是一个独立的工具,为几个Android应用调试和分析工具提供了一个UI。
    但是,大多数Android设备监视器组件已弃用,以支持Android Studio 3.0和更高版本中提供的更新工具。下表帮助您决定应该使用哪些开发人员工具。

    这里写图片描述

    图1.Android Developers关于Android Device Monitor的说明页

    如何在Android Studio 3.0中使用Android Device Monitor?

    虽然说被“弃用”,但是不代表不支持,我们还是可以通过其他方式来使用Android Device Monitor,具体使用方式如下:

    android-sdk/tools/目录的命令行中输入以下内容:

    monitor

    如果你不知道你的Android SDK安装在哪个目录,可以在Android Studio的设置1中查看:

    这里写图片描述

    图2.Android Studio设置界面

    进入CMD窗口2,cd到目标文件夹tools下,然后输入命令montior
    这里写图片描述

    图3.cmd界面

    接下来,我们就可以看到期待已久的Android Device Monitor界面了3
    这里写图片描述

    图4.Android Device Monitor界面


    1. Android Studio的设置界面快捷键:Ctrl+Alt+S
    2. Windows键+R进入CMD窗口
    3. 进入Android Device Monitor的前提是已经打开了Android设备模拟器
    展开全文
  • Ø 简介 什么是 Android Device Monitor,中文意思就是安卓设备监视器,用于管理安装设备(手机、模拟器)用的。下面列出 Android Device Monitor 常见的一些问题。 1. 打开 Android Device Monitor 没有任何内容 1)...

    Ø  简介

    什么是 Android Device Monitor,中文意思就是安卓设备监视器,用于管理安装设备(手机、模拟器)用的。下面列出 Android Device Monitor 常见的一些问题。

     

    1.   打开 Android Device Monitor 没有任何内容

    1)   无任何内容

    clip_image002[1]

    2)   这是因为没有监视到一台以上的 Android 设备,运行一个项目启动模拟器即可,如图:

    clip_image004[1]

     

    2.   无法访问 File Explorer 中的内容(比如 data

    clip_image005[1]

    1)   这是因为没有权限,data 的访问权限为 drwxrwx—xx,一共10个字符。

    1.   1个字符(d):表示是文件夹还是目录,d 表示文件夹。

    2.   后面9个字符(rwxrwx--x)分为三组:

    1)   第一组(rwx):表示所有者(user)对文件的访问权限,r 表示可读(read)w 表示可写(write)x 表示可执行

    2)   第二组(rwx):组群(group)对文件的访问权限。

    3)   第三组(--x):表示其他人(other)对文件的访问权限,- 表示没有该权限,也就是说其他人没有读/写权限。

     

    2)   那是不是修改相应的权限即可呢,没错。

    1.   修改权限使用 adb shell 命令,可参考:http://www.cnblogs.com/abeam/p/8908225.html

    2.   在命令行输入以下命令:

    clip_image007[1]

    1)   adb shell, 打开 adb 外壳程序。

    2)   # 表示超级管理器;$ 表示普通管理员。

    3)   su, 表示切换至超级管理员。

    4)   chmod 777, 表示设置指定的文件/文件夹权限,777 表示3个二进制(7=111),所以合起来就是(777=111111111),设置所有全的权限都为1,即 rwxrwxrwx

     

    3.   无法提取文件

    clip_image008[1]

    clip_image010[1]

    1)   在当前用户命令行输入 adb root 命令

    clip_image011[1]

    2)   返回 Android Device Monitor,选择模拟器,再次提取就 OK

    clip_image013[1]

    转载于:https://www.cnblogs.com/abeam/p/8900922.html

    展开全文
  • Android-Android Studio 3.0如何调出...为什么Android Studio 3.0中tools中找不到Android Device Monitor? 因为自Android Studio 3.0开始弃用Android Device Monitor,Android Developers官网上的原话: ...

    Android-Android Studio 3.0如何调出Android Device Monitor测试查看logcat

     

    为什么Android Studio 3.0中tools中找不到Android Device Monitor?

    因为自Android Studio 3.0开始弃用Android Device Monitor,Android Developers官网上的原话是:


      Android Device Monitor is a standalone tool that provides a UI for several Android app debugging and analysis tools. 
      However, most components of the Android Device Monitor are deprecated in favor of updated tools available in Android Studio 3.0 and higher. The table below helps you decide which developer tools you should use.


    译文:


      Android设备监视器是一个独立的工具,为几个Android应用调试和分析工具提供了一个UI。 
      但是,大多数Android设备监视器组件已弃用,以支持Android Studio 3.0和更高版本中提供的更新工具。下表帮助您决定应该使用哪些开发人员工具。

     

    如何在Android Studio 3.0中使用Android Device Monitor?

    虽然说被“弃用”,但是不代表不支持,我们还是可以通过其他方式来使用Android Device Monitor,具体使用方式如下:

     

    如果你不知道你的Android SDK安装在哪个目录,可以在Android Studio的设置1中查看:

    Android Studio的设置界面快捷键:Ctrl+Alt+S,找到Android SDK的目录,双击即可执行。

     

    然后开启使用模式:

    1.打开AS的AndroidDeviceMonitor

    2.连接真机,然后在AS里run对应的文件。

    3.在AndroidDeviceMonitor里就可以看到run出来的进程。

    4.点击StartMethodProfiling

    5.点击ok

    6.这时已经进入了分析模式,然后在手机上进行想要测量的操作,AndroidDeviceMonitor会记录我们操作时对应进程消耗的内存。

    7.点击StopMethodProfiling(和开始录制相同的按钮),停止录制。

    8.这时分析结果就出来了。

    9.分析操作

     

    参考链接:

    https://www.cnblogs.com/hustcser/p/9782664.html

    https://blog.csdn.net/QPC908694753/article/details/78816818

    展开全文
  • 什么Android Studio 3.0中找不到Android Device Monitor? 因为自Android Studio 3.0开始弃用Android Device Monitor,Android Developers官网上的原话: Android Device Monitor is a standalone tool that ...

     

    为什么Android Studio 3.0中找不到Android Device Monitor?


    因为自Android Studio 3.0开始弃用Android Device Monitor,Android Developers官网上的原话是:

    Android Device Monitor is a standalone tool that provides a UI for several Android app debugging and analysis tools. 
    However, most components of the Android Device Monitor are deprecated in favor of updated tools available in Android Studio 3.0 and higher. The table below helps you decide which developer tools you should use.

    译文:

    Android设备监视器是一个独立的工具,为几个Android应用调试和分析工具提供了一个UI。 
    但是,大多数Android设备监视器组件已弃用,以支持Android Studio 3.0和更高版本中提供的更新工具。下表帮助您决定应该使用哪些开发人员工具。

    图1.Android Developers关于Android Device Monitor的说明页
    如何在Android Studio 3.0中使用Android Device Monitor?
    虽然说被“弃用”,但是不代表不支持,我们还是可以通过其他方式来使用Android Device Monitor,具体使用方式如下:

    在android-sdk/tools/目录的命令行中输入以下内容:

    monitor

    找到SDK的路径后,打开AS的CMD,输入如下命令

    1、定位到SDK目录

    D:\DIDI\GovCar>cd D:\Android\sdk

    2、定位到tools目录

    D:\Android\sdk>cd tools

    3、打开monitor

    D:\Android\sdk\tools>monitor

    这样就可以了。

     

    但是!!!有的同学可能会报错!!!

    我们打开日志看看是什么

    !SESSION 2018-11-07 10:09:32.608 -----------------------------------------------
    eclipse.buildId=unknown
    java.version=1.8.0_131
    java.vendor=Oracle Corporation
    BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=zh_CN
    Command-line arguments:  -os win32 -ws win32 -arch x86 -data @noDefault
    
    !ENTRY org.eclipse.osgi 4 0 2018-11-07 10:09:34.673
    !MESSAGE Bundle reference:file:org.apache.ant_1.8.3.v201301120609/@4 not found.
    
    !ENTRY org.eclipse.osgi 4 0 2018-11-07 10:09:34.679
    !MESSAGE Bundle reference:file:org.apache.jasper.glassfish_2.2.2.v201205150955.jar@4 not found.
    
    !ENTRY org.eclipse.osgi 4 0 2018-11-07 10:09:34.681
    !MESSAGE Bundle reference:file:org.apache.lucene.core_2.9.1.v201101211721.jar@4 not found.
    
    !ENTRY org.eclipse.osgi 4 0 2018-11-07 10:09:34.727
    !MESSAGE Bundle reference:file:org.eclipse.help.base_3.6.101.v201302041200.jar@4 not found.
    
    !ENTRY org.eclipse.osgi 4 0 2018-11-07 10:09:34.729
    !MESSAGE Bundle reference:file:org.eclipse.help.ui_3.5.201.v20130108-092756.jar@4 not found.
    
    !ENTRY org.eclipse.osgi 4 0 2018-11-07 10:09:34.730
    !MESSAGE Bundle reference:file:org.eclipse.help.webapp_3.6.101.v20130116-182509.jar@4 not found.
    
    !ENTRY org.eclipse.osgi 4 0 2018-11-07 10:09:34.732
    !MESSAGE Bundle reference:file:org.eclipse.jetty.server_8.1.3.v20120522.jar@4 not found.
    
    !ENTRY org.eclipse.osgi 4 0 2018-11-07 10:09:34.738
    !MESSAGE Bundle reference:file:org.eclipse.platform.doc.user_4.2.2.v20130121-200410.jar@4 not found.
    
    !ENTRY org.eclipse.osgi 4 0 2018-11-07 10:09:34.742
    !MESSAGE Bundle reference:file:org.eclipse.team.core_3.6.100.v20120524-0627.jar@4 not found.
    
    !ENTRY org.eclipse.osgi 4 0 2018-11-07 10:09:34.743
    !MESSAGE Bundle reference:file:org.eclipse.team.ui_3.6.201.v20130125-135424.jar@4 not found.
    
    !ENTRY org.eclipse.osgi 4 0 2018-11-07 10:09:34.746
    !MESSAGE Bundle reference:file:org.eclipse.ui.cheatsheets_3.4.200.v20120521-2344.jar@4 not found.
    
    !ENTRY org.eclipse.osgi 4 0 2018-11-07 10:09:34.749
    !MESSAGE Bundle reference:file:org.eclipse.ui.intro_3.4.200.v20120521-2344.jar@4 not found.
    
    !ENTRY org.eclipse.osgi 2 0 2018-11-07 10:09:36.028
    !MESSAGE One or more bundles are not resolved because the following root constraints are not resolved:
    !SUBENTRY 1 org.eclipse.osgi 2 0 2018-11-07 10:09:36.029
    !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 2018-11-07 10:09:36.029
    !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 2018-11-07 10:09:36.029
    !MESSAGE Bundle initial@reference:file:plugins/org.apache.lucene_2.9.1.v201101211721.jar was not resolved.
    !SUBENTRY 2 org.apache.lucene 2 0 2018-11-07 10:09:36.029
    !MESSAGE Missing required bundle org.apache.lucene.core_[2.9.1,3.0.0).
    !SUBENTRY 1 org.eclipse.osgi 2 0 2018-11-07 10:09:36.029
    !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 2018-11-07 10:09:36.029
    !MESSAGE Missing imported package org.apache.jasper.servlet_[0.0.0,6.0.0).
    !SUBENTRY 2 org.eclipse.equinox.jsp.jasper 2 0 2018-11-07 10:09:36.029
    !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 2018-11-07 10:09:36.029
    !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 2018-11-07 10:09:36.029
    !MESSAGE Missing imported package org.eclipse.jetty.server_[8.1.0,9.0.0).
    !SUBENTRY 2 org.eclipse.jetty.security 2 0 2018-11-07 10:09:36.029
    !MESSAGE Missing imported package org.eclipse.jetty.server.handler_[8.1.0,9.0.0).
    !SUBENTRY 1 org.eclipse.osgi 2 0 2018-11-07 10:09:36.029
    !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 2018-11-07 10:09:36.029
    !MESSAGE Missing imported package org.eclipse.jetty.server.session_[8.0.0,9.0.0).
    !SUBENTRY 2 org.eclipse.equinox.http.jetty 2 0 2018-11-07 10:09:36.029
    !MESSAGE Missing imported package org.eclipse.jetty.server_[8.0.0,9.0.0).
    !SUBENTRY 2 org.eclipse.equinox.http.jetty 2 0 2018-11-07 10:09:36.029
    !MESSAGE Missing imported package org.eclipse.jetty.server.bio_[8.0.0,9.0.0).
    !SUBENTRY 2 org.eclipse.equinox.http.jetty 2 0 2018-11-07 10:09:36.029
    !MESSAGE Missing imported package org.eclipse.jetty.server.handler_[8.0.0,9.0.0).
    !SUBENTRY 2 org.eclipse.equinox.http.jetty 2 0 2018-11-07 10:09:36.029
    !MESSAGE Missing imported package org.eclipse.jetty.server.nio_[8.0.0,9.0.0).
    !SUBENTRY 2 org.eclipse.equinox.http.jetty 2 0 2018-11-07 10:09:36.029
    !MESSAGE Missing imported package org.eclipse.jetty.server.ssl_[8.0.0,9.0.0).
    !SUBENTRY 1 org.eclipse.osgi 2 0 2018-11-07 10:09:36.029
    !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 2018-11-07 10:09:36.029
    !MESSAGE Missing required bundle org.eclipse.team.ui_[3.4.100,4.0.0).
    !SUBENTRY 2 org.eclipse.ltk.ui.refactoring 2 0 2018-11-07 10:09:36.029
    !MESSAGE Missing required bundle org.eclipse.team.core_[3.4.100,4.0.0).
    !SUBENTRY 1 org.eclipse.osgi 2 0 2018-11-07 10:09:36.030
    !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 2018-11-07 10:09:36.030
    !MESSAGE Missing required bundle org.apache.lucene.core_[2.9.1,3.0.0).
    !SUBENTRY 1 org.eclipse.osgi 2 0 2018-11-07 10:09:36.030
    !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 2018-11-07 10:09:36.030
    !MESSAGE Missing imported package org.eclipse.jetty.server_[8.1.0,9.0.0).
    !SUBENTRY 2 org.eclipse.jetty.servlet 2 0 2018-11-07 10:09:36.030
    !MESSAGE Missing imported package org.eclipse.jetty.server.ssl_[8.1.0,9.0.0).
    !SUBENTRY 2 org.eclipse.jetty.servlet 2 0 2018-11-07 10:09:36.030
    !MESSAGE Missing imported package org.eclipse.jetty.server.session_[8.1.0,9.0.0).
    !SUBENTRY 2 org.eclipse.jetty.servlet 2 0 2018-11-07 10:09:36.030
    !MESSAGE Missing imported package org.eclipse.jetty.server.handler_[8.1.0,9.0.0).
    !SUBENTRY 2 org.eclipse.jetty.servlet 2 0 2018-11-07 10:09:36.030
    !MESSAGE Missing imported package org.eclipse.jetty.server.nio_[8.1.0,9.0.0).
    !SUBENTRY 1 org.eclipse.osgi 2 0 2018-11-07 10:09:36.030
    !MESSAGE Bundle initial@reference:file:plugins/org.eclipse.platform_4.2.2.v201302041200/ was not resolved.
    !SUBENTRY 2 org.eclipse.platform 2 0 2018-11-07 10:09:36.030
    !MESSAGE Missing required bundle org.eclipse.ui.intro_[3.2.0,4.0.0).
    !SUBENTRY 2 org.eclipse.platform 2 0 2018-11-07 10:09:36.030
    !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 2018-11-07 10:09:36.030
    !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 2018-11-07 10:09:36.030
    !MESSAGE Missing required bundle org.eclipse.ui.intro_[3.4.0,4.0.0).
    
    !ENTRY org.eclipse.osgi 2 0 2018-11-07 10:09:36.062
    !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 2018-11-07 10:09:36.062
    !MESSAGE Bundle org.apache.lucene_2.9.1.v201101211721 [25] was not resolved.
    !SUBENTRY 2 org.apache.lucene 2 0 2018-11-07 10:09:36.062
    !MESSAGE Missing required bundle org.apache.lucene.core_[2.9.1,3.0.0).
    !SUBENTRY 2 org.apache.lucene 2 0 2018-11-07 10:09:36.062
    !MESSAGE Missing optionally required bundle org.apache.lucene.analysis_[2.9.1,3.0.0).
    !SUBENTRY 2 org.apache.lucene 2 0 2018-11-07 10:09:36.062
    !MESSAGE Missing optionally required bundle org.apache.lucene.highlighter_[2.9.1,3.0.0).
    !SUBENTRY 2 org.apache.lucene 2 0 2018-11-07 10:09:36.062
    !MESSAGE Missing optionally required bundle org.apache.lucene.memory_[2.9.1,3.0.0).
    !SUBENTRY 2 org.apache.lucene 2 0 2018-11-07 10:09:36.062
    !MESSAGE Missing optionally required bundle org.apache.lucene.queries_[2.9.1,3.0.0).
    !SUBENTRY 2 org.apache.lucene 2 0 2018-11-07 10:09:36.062
    !MESSAGE Missing optionally required bundle org.apache.lucene.snowball_[2.9.1,3.0.0).
    !SUBENTRY 2 org.apache.lucene 2 0 2018-11-07 10:09:36.062
    !MESSAGE Missing optionally required bundle org.apache.lucene.spellchecker_[2.9.1,3.0.0).
    !SUBENTRY 2 org.apache.lucene 2 0 2018-11-07 10:09:36.062
    !MESSAGE Missing optionally required bundle org.apache.lucene.misc_[2.9.1,3.0.0).
    !SUBENTRY 1 org.eclipse.osgi 2 0 2018-11-07 10:09:36.062
    !MESSAGE Bundle org.apache.lucene.analysis_2.9.1.v201101211721 [26] was not resolved.
    !SUBENTRY 2 org.apache.lucene.analysis 2 0 2018-11-07 10:09:36.062
    !MESSAGE Missing required bundle org.apache.lucene.core_[2.9.1,3.0.0).
    !SUBENTRY 1 org.eclipse.osgi 2 0 2018-11-07 10:09:36.062
    !MESSAGE Bundle org.eclipse.equinox.http.jetty_3.0.1.v20121109-203239 [91] was not resolved.
    !SUBENTRY 2 org.eclipse.equinox.http.jetty 2 0 2018-11-07 10:09:36.062
    !MESSAGE Missing imported package org.eclipse.jetty.server_[8.0.0,9.0.0).
    !SUBENTRY 2 org.eclipse.equinox.http.jetty 2 0 2018-11-07 10:09:36.063
    !MESSAGE Missing imported package org.eclipse.jetty.server.bio_[8.0.0,9.0.0).
    !SUBENTRY 2 org.eclipse.equinox.http.jetty 2 0 2018-11-07 10:09:36.063
    !MESSAGE Missing imported package org.eclipse.jetty.server.handler_[8.0.0,9.0.0).
    !SUBENTRY 2 org.eclipse.equinox.http.jetty 2 0 2018-11-07 10:09:36.063
    !MESSAGE Missing imported package org.eclipse.jetty.server.nio_[8.0.0,9.0.0).
    !SUBENTRY 2 org.eclipse.equinox.http.jetty 2 0 2018-11-07 10:09:36.063
    !MESSAGE Missing imported package org.eclipse.jetty.server.session_[8.0.0,9.0.0).
    !SUBENTRY 2 org.eclipse.equinox.http.jetty 2 0 2018-11-07 10:09:36.063
    !MESSAGE Missing imported package org.eclipse.jetty.server.ssl_[8.0.0,9.0.0).
    !SUBENTRY 2 org.eclipse.equinox.http.jetty 2 0 2018-11-07 10:09:36.063
    !MESSAGE Missing imported package org.eclipse.jetty.servlet_[8.0.0,9.0.0).
    !SUBENTRY 1 org.eclipse.osgi 2 0 2018-11-07 10:09:36.063
    !MESSAGE Bundle org.eclipse.equinox.jsp.jasper_1.0.400.v20120912-130548 [94] was not resolved.
    !SUBENTRY 2 org.eclipse.equinox.jsp.jasper 2 0 2018-11-07 10:09:36.063
    !MESSAGE Missing imported package org.apache.jasper.servlet_[0.0.0,6.0.0).
    !SUBENTRY 2 org.eclipse.equinox.jsp.jasper 2 0 2018-11-07 10:09:36.063
    !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 2018-11-07 10:09:36.063
    !MESSAGE Bundle org.eclipse.equinox.jsp.jasper.registry_1.0.300.v20120912-130548 [95] was not resolved.
    !SUBENTRY 2 org.eclipse.equinox.jsp.jasper.registry 2 0 2018-11-07 10:09:36.063
    !MESSAGE Missing imported package org.eclipse.equinox.jsp.jasper_0.0.0.
    !SUBENTRY 2 org.eclipse.equinox.jsp.jasper.registry 2 0 2018-11-07 10:09:36.063
    !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 2018-11-07 10:09:36.063
    !MESSAGE Bundle org.eclipse.jetty.security_8.1.3.v20120522 [138] was not resolved.
    !SUBENTRY 2 org.eclipse.jetty.security 2 0 2018-11-07 10:09:36.063
    !MESSAGE Missing imported package org.eclipse.jetty.server_[8.1.0,9.0.0).
    !SUBENTRY 2 org.eclipse.jetty.security 2 0 2018-11-07 10:09:36.063
    !MESSAGE Missing imported package org.eclipse.jetty.server.handler_[8.1.0,9.0.0).
    !SUBENTRY 1 org.eclipse.osgi 2 0 2018-11-07 10:09:36.063
    !MESSAGE Bundle org.eclipse.jetty.servlet_8.1.3.v20120522 [139] was not resolved.
    !SUBENTRY 2 org.eclipse.jetty.servlet 2 0 2018-11-07 10:09:36.063
    !MESSAGE Missing optionally imported package org.eclipse.jetty.jmx_8.0.0.
    !SUBENTRY 2 org.eclipse.jetty.servlet 2 0 2018-11-07 10:09:36.063
    !MESSAGE Missing imported package org.eclipse.jetty.security_[8.1.0,9.0.0).
    !SUBENTRY 2 org.eclipse.jetty.servlet 2 0 2018-11-07 10:09:36.063
    !MESSAGE Missing imported package org.eclipse.jetty.server_[8.1.0,9.0.0).
    !SUBENTRY 2 org.eclipse.jetty.servlet 2 0 2018-11-07 10:09:36.063
    !MESSAGE Missing imported package org.eclipse.jetty.server.handler_[8.1.0,9.0.0).
    !SUBENTRY 2 org.eclipse.jetty.servlet 2 0 2018-11-07 10:09:36.064
    !MESSAGE Missing imported package org.eclipse.jetty.server.nio_[8.1.0,9.0.0).
    !SUBENTRY 2 org.eclipse.jetty.servlet 2 0 2018-11-07 10:09:36.064
    !MESSAGE Missing imported package org.eclipse.jetty.server.session_[8.1.0,9.0.0).
    !SUBENTRY 2 org.eclipse.jetty.servlet 2 0 2018-11-07 10:09:36.064
    !MESSAGE Missing imported package org.eclipse.jetty.server.ssl_[8.1.0,9.0.0).
    !SUBENTRY 1 org.eclipse.osgi 2 0 2018-11-07 10:09:36.064
    !MESSAGE Bundle org.eclipse.ltk.ui.refactoring_3.7.0.v20120523-1543 [147] was not resolved.
    !SUBENTRY 2 org.eclipse.ltk.ui.refactoring 2 0 2018-11-07 10:09:36.064
    !MESSAGE Missing required bundle org.eclipse.team.core_[3.4.100,4.0.0).
    !SUBENTRY 2 org.eclipse.ltk.ui.refactoring 2 0 2018-11-07 10:09:36.064
    !MESSAGE Missing required bundle org.eclipse.team.ui_[3.4.100,4.0.0).
    !SUBENTRY 1 org.eclipse.osgi 2 0 2018-11-07 10:09:36.064
    !MESSAGE Bundle org.eclipse.platform_4.2.2.v201302041200 [150] was not resolved.
    !SUBENTRY 2 org.eclipse.platform 2 0 2018-11-07 10:09:36.064
    !MESSAGE Missing required bundle org.eclipse.ui.intro_[3.2.0,4.0.0).
    !SUBENTRY 2 org.eclipse.platform 2 0 2018-11-07 10:09:36.064
    !MESSAGE Missing optionally required bundle org.eclipse.ui.cheatsheets_[3.2.0,4.0.0).
    !SUBENTRY 2 org.eclipse.platform 2 0 2018-11-07 10:09:36.064
    !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 2018-11-07 10:09:36.064
    !MESSAGE Bundle org.eclipse.search_3.8.0.v20120523-1540 [152] was not resolved.
    !SUBENTRY 2 org.eclipse.search 2 0 2018-11-07 10:09:36.064
    !MESSAGE Missing required bundle org.eclipse.ltk.ui.refactoring_[3.5.0,4.0.0).
    !SUBENTRY 1 org.eclipse.osgi 2 0 2018-11-07 10:09:36.064
    !MESSAGE Bundle org.eclipse.ui.intro.universal_3.2.600.v20120912-155524 [164] was not resolved.
    !SUBENTRY 2 org.eclipse.ui.intro.universal 2 0 2018-11-07 10:09:36.064
    !MESSAGE Missing required bundle org.eclipse.ui.intro_[3.4.0,4.0.0).
    !SUBENTRY 1 org.eclipse.osgi 2 0 2018-11-07 10:09:36.064
    !MESSAGE Bundle org.eclipse.ui.navigator.resources_3.4.400.v20120705-114010 [166] was not resolved.
    !SUBENTRY 2 org.eclipse.ui.navigator.resources 2 0 2018-11-07 10:09:36.064
    !MESSAGE Missing required bundle org.eclipse.ltk.ui.refactoring_[3.5.0,4.0.0).
    
    !ENTRY org.eclipse.osgi 4 0 2018-11-07 10:09:36.066
    !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(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)
    

    居然有这么多,然后百度查一查原因是:

    java.lang.NullPointerException at org.eclipse.core.runtime.URIUtil.toURI(URIUtil.java:280)

    怎么解决呢?

    找遍国内网站都没有这个问题的解决,后来在国外网站找到了。

    Ensure you have no other monitor.exe (if on Windows) or monitor (if 
    OS X / Linux) process running. If you do, kill it.

    Run rm -rf $HOME/.android/monitor-workspace or remove the directory 
    manually

    就是先在任务管理器进程里面关掉所有 monitor.exe 进程。 
    再去删除monitor-workspace整个目录,我的在C:\Users\Administrator.android里面,删除完重新打开成功。

    传送门: 
    https://tutel.me/c/programming/questions/26052849/unexpected+error+while+parsing+input+invalid+uiautomator+hierarchy+file
     

    解决。可以打开MMDS了~

     

    展开全文
  • Android性能测试——Allocation Tracker(Device Monitor) Allocation Tracker 能做什么? 追踪内存分配信息,按顺序排列,这样我们就能清晰看出来某一个操作的内存如何一步一步分配出来的。比如在有内存...
  • HHD 出品的 Device Monitor 一款功能非常强大又好用的数据传输监视软件,包含 Serial Monitor 和 USB Monitor 等模块。只可惜网上没有破解版。流传的Serial Monitor 3.21 破解版也只是表面破解了,并不能超过30次...
  • 学习Java开发,在mac上装了一个AS,想试一下Android Device Monitor,结果启动失败,一直报error,让查看日志什么的。 试遍了国内的技术网站与Stackoverflow各种类似问题的解决方案,都不能成功.....后来想到自己...
  • HHD 出品的 Device Monitor 5.24 一款功能非常强大又好用的数据传输监视软件,包含 Serial Monitor 和 USB Monitor 等模块。只可惜网上没有破解版。流传的Serial Monitor 3.21 破解版也只是表面破解了,并不能超过...
  • 什么是内存 Android系统为我们APP分配的内存大小有限的,不同的手机型号、不同的ROM分配的内存大小不一定一样,这里所提到的内存一般指Android手机的RAM,RAM包含寄存器、堆、栈、静态存储区域、常量池。通常...
  • Android Studio 找不到Android Device Monitor

    千次阅读 2018-12-01 18:25:49
    当学习到《第一行代码》的第六章第二“文件存储”时,按要求点击Android Studio导航栏中的Tools却找不到Android选项。 于是就上百度查询,...(保持模拟器处于运行状态,一篇博客里这么要求的,虽然不知道什么...
  • Allocation Tracker 能做什么?追踪内存分配信息,按顺序排列,这样我们就能清晰看出来某一个操作的内存如何一步一步分配出来的。Allocation Tracker面板各名称的含义如下: 名称 意义 Alloc Order 分配序列 ...
  • HHD 出品的 Device Monitor 一款功能非常强大又好用的数据传输监视软件,包含 Serial Monitor 和 USB Monitor 等模块。只可惜网上没有破解版。流传的Serial Monitor 3.21 破解版也只是表面破解了,并不能超过30次...
  • Android Studio Version(2.2.2 || 2.2.3) Android Version(7.1.1 || 7.0) 以前写过SQLite的文章,那时候好像用Android 6.0,DDMS打开很正常。...就在今天调试SQLite的时候发现,打开DDMS里面什么都没有???
  • 我做OAD升级,板子已经下载了BIM和Image-A,用BLE Device Monitor软件搜索广播设备,出现这种错,什么情况这[img=https://img-bbs.csdn.net/upload/201509/01/1441076372_133649.jpg][/img]
  • 服务器message文件中,fail to add monitor on‘/dev/tty5 :No space left on device 是什么情况??
  • [2016-03-25 15:15:05 - DeviceMonitor] Adb connection Error:远程主机强迫关闭了一个现有的连接。 [2016-03-25 15:15:06 - DeviceMonitor] Connection attempts: 1 [2016-03-25 15:15:08 - ...
  • HHD 出品的 Device Monitor 5.24 一款功能非常强大又好用的数据传输监视软件,包含 Serial Monitor 和 USB Monitor 等模块。只可惜网上没有破解版。流传的Serial Monitor 3.21 破解版也只是表面破解了,并不能超过...
  • 环境:操作系统Mac,模拟器问题:AndroidStudio中AndroidDeviceMonitor中的FileExplore不显示文件本人在...问一下,这什么?本人换成真机后,可以在FileExplore看到文件列表了,能看到“data”目录,但是...
  • 问题:error running 'app':no target device found在进行真机调试的时候找不到设备,明明开发者模式什么usb都都设置了,但还是找不到,这个问题容易出现在重新打开Android Studio的时候,原因Android Monitor程序...
  • 有没有大佬看看这是什么问题啊,用荣耀9调试的时候日志显示[ThreadDexHotfixMonitor]Bind hotfix monitor service fail! 手机上打开了开发者模式,android studio也能连上,就想发条通知,但怎么点击按钮都没用。...
  • "What is an input device?", "Keyboard", "Monitor", "Printer", "Motherboard", "Keyboard" ), array( // [0] is the question, [1]-[4] are the answer choices, [5] is the correct chioce "What is ...
  •  at com.android.ddmlib.DeviceMonitor.processIncomingJdwpData(DeviceMonitor.java:548)  at com.android.ddmlib.DeviceMonitor.deviceClientMonitorLoop(DeviceMonitor.java:436)  at ...
  • 一个最普通的 HelloWorld app运行以后,总共会开启多少线程,这些线程分别是什么作用,线程的status是什么? 二 分析 helloworld app运行以后,打开Android Studio — Tools — Android — Android Device ...
  • mBusEventBus.getDefault的一个实例,有解绑,这个页面没有使用stickyPost,但是还是有内存泄漏,各位有什么想法 mBus使用到的代码 ``` public EventBus mBus; @Override protected void ...
  • 线程基础

    2019-08-07 22:33:02
    1.什么是进程 先了解一下什么是进程。进 程操作系统结构的基础,程序在一个数据集合上运行的过程,系 统进行资源分配和调度的基本单位。...再举一个例子,如图4-2所示,这Android Device Monitor中 的...
  • 写这篇博客的主要目的给大家提供一种解决办法,笔者的使用情境这样:先用自带模拟器运行应用,然后打开Android Device Monitor,运行HierarchyView发现提示:查网上先有的解决办法,有的说是:使用root权限执行...
  • view的测量,布局,绘制

    2016-10-02 22:31:16
    Android原生桌面上的那些应用图标其实 textview, 可以再 Android Device Monitor 中看(dump view). View只能有一个父View, 为什么? 这样设计, 系统底层只需跟最顶层的View交互. View是否必须有父View, 不是, ...

空空如也

空空如也

1 2 3 4
收藏数 71
精华内容 28
关键字:

devicemonitor是什么