Android ADB外壳:错误:未知命令:执行ADB外壳am显示密度时显示密度?
我正在运行LinuxMint,连接的设备是中兴HSUSB,它运行在安卓v4.1.2上 屏幕大小调整命令似乎起作用了:我执行了Android ADB外壳:错误:未知命令:执行ADB外壳am显示密度时显示密度?,android,linux,shell,usb,adb,Android,Linux,Shell,Usb,Adb,我正在运行LinuxMint,连接的设备是中兴HSUSB,它运行在安卓v4.1.2上 屏幕大小调整命令似乎起作用了:我执行了adb shell am display size 640x480,它正确地调整了屏幕大小 然而,当我试图用adb shell am display density 160调整屏幕密度时,我得到了 administrator-LenovoPC ~ # adb shell am display-density 160 usage: am [subcommand] [optio
adb shell am display size 640x480
,它正确地调整了屏幕大小
然而,当我试图用adb shell am display density 160调整屏幕密度时,我得到了
administrator-LenovoPC ~ # adb shell am display-density 160
usage: am [subcommand] [options]
usage: am start [-D] [-W] [-P <FILE>] [--start-profiler <FILE>]
[--R COUNT] [-S] [--opengl-trace] <INTENT>
am startservice <INTENT>
am force-stop <PACKAGE>
am kill <PACKAGE>
am kill-all
am broadcast <INTENT>
am instrument [-r] [-e <NAME> <VALUE>] [-p <FILE>] [-w]
[--no-window-animation] <COMPONENT>
am profile start <PROCESS> <FILE>
am profile stop [<PROCESS>]
am dumpheap [flags] <PROCESS> <FILE>
am set-debug-app [-w] [--persistent] <PACKAGE>
am clear-debug-app
am monitor [--gdb <port>]
am screen-compat [on|off] <PACKAGE>
am display-size [reset|MxN]
am to-uri [INTENT]
am to-intent-uri [INTENT]
am start: start an Activity. Options are:
-D: enable debugging
-W: wait for launch to complete
--start-profiler <FILE>: start profiler and send results to <FILE>
-P <FILE>: like above, but profiling stops when app goes idle
-R: repeat the activity launch <COUNT> times. Prior to each repeat,
the top activity will be finished.
-S: force stop the target app before starting the activity
--opengl-trace: enable tracing of OpenGL functions
am startservice: start a Service.
am force-stop: force stop everything associated with <PACKAGE>.
am kill: Kill all processes associated with <PACKAGE>. Only kills.
processes that are safe to kill -- that is, will not impact the user
experience.
am kill-all: Kill all background processes.
am broadcast: send a broadcast Intent.
am instrument: start an Instrumentation. Typically this target <COMPONENT>
is the form <TEST_PACKAGE>/<RUNNER_CLASS>. Options are:
-r: print raw results (otherwise decode REPORT_KEY_STREAMRESULT). Use with
[-e perf true] to generate raw output for performance measurements.
-e <NAME> <VALUE>: set argument <NAME> to <VALUE>. For test runners a
common form is [-e <testrunner_flag> <value>[,<value>...]].
-p <FILE>: write profiling data to <FILE>
-w: wait for instrumentation to finish before returning. Required for
test runners.
--no-window-animation: turn off window animations will running.
am profile: start and stop profiler on a process.
am dumpheap: dump the heap of a process. Options are:
-n: dump native heap instead of managed heap
am set-debug-app: set application <PACKAGE> to debug. Options are:
-w: wait for debugger when application starts
--persistent: retain this value
am clear-debug-app: clear the previously set-debug-app.
am monitor: start monitoring for crashes or ANRs.
--gdb: start gdbserv on the given port at crash/ANR
am screen-compat: control screen compatibility mode of <PACKAGE>.
am display-size: override display size.
am to-uri: print the given Intent specification as a URI.
am to-intent-uri: print the given Intent specification as an intent: URI.
<INTENT> specifications include these flags and arguments:
[-a <ACTION>] [-d <DATA_URI>] [-t <MIME_TYPE>]
[-c <CATEGORY> [-c <CATEGORY>] ...]
[-e|--es <EXTRA_KEY> <EXTRA_STRING_VALUE> ...]
[--esn <EXTRA_KEY> ...]
[--ez <EXTRA_KEY> <EXTRA_BOOLEAN_VALUE> ...]
[--ei <EXTRA_KEY> <EXTRA_INT_VALUE> ...]
[--el <EXTRA_KEY> <EXTRA_LONG_VALUE> ...]
[--ef <EXTRA_KEY> <EXTRA_FLOAT_VALUE> ...]
[--eu <EXTRA_KEY> <EXTRA_URI_VALUE> ...]
[--ecn <EXTRA_KEY> <EXTRA_COMPONENT_NAME_VALUE>]
[--eia <EXTRA_KEY> <EXTRA_INT_VALUE>[,<EXTRA_INT_VALUE...]]
[--ela <EXTRA_KEY> <EXTRA_LONG_VALUE>[,<EXTRA_LONG_VALUE...]]
[--efa <EXTRA_KEY> <EXTRA_FLOAT_VALUE>[,<EXTRA_FLOAT_VALUE...]]
[-n <COMPONENT>] [-f <FLAGS>]
[--grant-read-uri-permission] [--grant-write-uri-permission]
[--debug-log-resolution] [--exclude-stopped-packages]
[--include-stopped-packages]
[--activity-brought-to-front] [--activity-clear-top]
[--activity-clear-when-task-reset] [--activity-exclude-from-recents]
[--activity-launched-from-history] [--activity-multiple-task]
[--activity-no-animation] [--activity-no-history]
[--activity-no-user-action] [--activity-previous-is-top]
[--activity-reorder-to-front] [--activity-reset-task-if-needed]
[--activity-single-top] [--activity-clear-task]
[--activity-task-on-home]
[--receiver-registered-only] [--receiver-replace-pending]
[--selector]
[<URI> | <PACKAGE> | <COMPONENT>]
Error: Unknown command: display-density
管理员LenovoPC~#adb shell am显示密度160
用法:am[子命令][选项]
用法:am开始[-D][-W][-P][-开始探查器]
[--R计数][-S][--opengl跟踪]
am startservice
强制停车
我死了
我杀了所有人
调幅广播
调幅仪表[-r][-e][-p][-w]
[--没有窗口动画]
am配置文件开始
am配置文件停止[]
am转储堆[标志]
am设置调试应用程序[-w][--persistent]
am清除调试应用程序
am监视器[--gdb]
am屏幕兼容性[开|关]
am显示大小[重置| MxN]
am到uri[意图]
am到意向uri[意向]
am开始:开始一项活动。选项包括:
-D:启用调试
-W:等待发射完成
--启动探查器:启动探查器并将结果发送到
-P:如上所述,但当应用程序空闲时,分析停止
-R:重复活动启动时间。在每次重复之前,
顶部的活动将完成。
-S:在开始活动之前强制停止目标应用程序
--opengl跟踪:启用opengl函数的跟踪
am startservice:启动服务。
am强制停止:强制停止与之相关的一切。
am kill:终止与关联的所有进程。只会杀人。
可以安全终止的进程——也就是说,不会影响用户
经验
am kill all:杀死所有后台进程。
am广播:发送广播意图。
am仪器:启动仪器。通常是这个目标
是表格/。选项包括:
-r:打印原始结果(否则解码报告\u键\u流结果)。配合使用
[-e perf true]生成性能度量的原始输出。
-e:将参数设置为。对于测试跑步者a
常见的形式是[-e[,…]。
-p:将分析数据写入
-w:等待仪器完成后再返回。必需的
测试跑步者。
--无窗口动画:关闭将运行的窗口动画。
am profile:启动和停止进程上的探查器。
am dumpheap:转储进程的堆。选项包括:
-n:转储本机堆而不是托管堆
am设置调试应用程序:将应用程序设置为调试。选项包括:
-w:应用程序启动时等待调试器
--持久:保留此值
am清除调试应用程序:清除以前设置的调试应用程序。
am监视器:开始监测碰撞或ANR。
--gdb:在崩溃/ANR时在给定端口上启动gdbserv
am屏幕兼容:的控制屏幕兼容模式。
am显示大小:替代显示大小。
am到uri:将给定的意图规范打印为uri。
am到intent uri:将给定的intent规范打印为intent:uri。
规范包括以下标志和参数:
[a][d][t]
[-c[-c]…]
[-e|--es…]
[--esn…]
[--ez…]
[--ei…]
[--el…]
[--ef…]
[--欧盟…]
[--ecn]
[--环境影响评估[,我知道它在4.1.2中应该是这样工作的,但是你试过以防万一吗?是的,我试过了,我得到了/system/bin/sh:wm:not found
Mb,这个设备不支持这个特定的功能?嗯,但我相信应该,因为它支持重新调整大小命令。好的,am
在4.1.2中不支持ave显示密度
命令