adb | 易学教程

ADB screenrecord command not found

阅读更多关于 ADB screenrecord command not found

问题 I am unable to run adb shell screenrecord /sdcard/my.mp4 Device specification that i am trying to run this command: Honor 5C Android 6.0 whenever i run the screenrecord command it shows command not found. D:\adb>adb shell screenrecord /systerm/bin/sh:screenrecord not found Also i have builtin screen record application is this reason for my issue? Is there any other way to capture screen except screencap? Or can i tap into builtin screen record application? Any suggestions or idea are

How to authorize and accept ADB RSA key with broken touch screen on Android [closed]

阅读更多关于 How to authorize and accept ADB RSA key with broken touch screen on Android [closed]

问题 Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers. Want to improve this question? Update the question so it's on-topic for Stack Overflow. Closed last year . My Nexus 7 2012 has a broken touch screen so I use an OTG mouse with it. I recently had to do a factory reinstall so am running v5.1 lollipop. The problem is I now have to re authorize adb with my computer so I can do work on it but cannot accept the RSA key when the dialog pops up

How to authorize and accept ADB RSA key with broken touch screen on Android [closed]

阅读更多关于 How to authorize and accept ADB RSA key with broken touch screen on Android [closed]

Where is “Activity Manager State” in Android Studio 3?

阅读更多关于 Where is “Activity Manager State” in Android Studio 3?

问题 There was a very handy feature for debugging, that was present in Android studio 2.x, but currently is not there in 3.x. It was a bit hidden in the UI: Then it will prompt with detailed activity manager state: I know, that I can acquire that output with adb shell dumpsys activity top , I'm just curious whether it is possible to get the old functionality back? 回答1: As pointed out by Wojtek Kaliciński in a tweet: A bug is opened here. Update We apologize if this was inconvenient. The old

LG G4 not recognised by Android Studio

阅读更多关于 LG G4 not recognised by Android Studio

问题 I just got the LG G4 phone, turned on developer options mode, tried running an app from Android Studio but it can't recognise my phone. I even tried switching from MTP to PTP but still it's not recognised. I tried a lot of resources out there, still nothing. Please can anyone help? 回答1: So i restarted my device, and switched USB options from MTP to PTP. and for some reason it worked. I dont know why. Thanks for answers above, much appreciated 回答2: Had the same problem and tried everything

I am trying to test android deep link urls through adb to launch my app

阅读更多关于 I am trying to test android deep link urls through adb to launch my app

问题 When I type the command in adb: ./adb shell am start -W -a android.intent.action.VIEW -d "example:gizmos" com.myapp I get this error: Starting: Intent { act=android.intent.action.VIEW dat=example://gizmos pkg=com.myapp } Error: Activity not started, unable to resolve Intent { act=android.intent.action.VIEW dat=example://gizmos flg=0x10000000 pkg=com.myapp } But when I type the command in adb: ./adb shell am start -W -a android.intent.action.VIEW -d "example:gizmos" com.myapp.activity

adb shell running multiple commands from same cmd window

阅读更多关于 adb shell running multiple commands from same cmd window

问题 I am trying to create a Perl script to run set of commands through adb shell . cmd1 cmd2 cmd3 cmd3(1) I put all the commands in a text file and ran it like this: adb shell < adb_commands.txt .(reference) However, I have this one issue where the last command cmd3(1) needs to be executed from within the previous command cmd3. So cmd3 will be executed and will wait for cmd3(1) to be entered. This is not happening coz as far as i can tell, adb shell is waiting for cmd3 to finish so it can run

Android Notifications through ADB

阅读更多关于 Android Notifications through ADB

问题 I'm writing a shell script that allows you to install an .apk on all android phones connected to a computer in parallel using Terminal . At my company we do tests on many devices and so this makes the installation part must faster. Question: I'm looking for a way to quickly identify which phones have had the .apk installed via some sort of feedback/notification. Ideally you should be able to see which phones have received the .apk just by looking at it (some sort of sound or screen flash) or

adb push 失败提示 ‘Read-only file system’

阅读更多关于 adb push 失败提示 ‘Read-only file system’

$ adb push ./xxx /xxx/ failed to copy './xxx' to '/xxx/xxx': Read-only file system 解决方法： $ adb root restarting adbd as root $ adb remount remount succeeded $ adb push ./libbacktrace.so /system/lib/ 2783 KB/s (58588 bytes in 0.020s) 已经按照上面的步骤做了，还是提示 ‘Read-only file system’怎么办 $ adb shell # mount /dev/block/by-name/android_system /system ext4 ro,seclabel,relati me,data=ordered 0 0 可以看到/system还是只读属性‘ro’，接下来我们把它remount成rw #mount -o remount -o rw /system #mount /dev/block/by-name/android_system /system ext4 rw,seclabel,relati me,data=ordered 0 0 tips：先 adb root 再adb remount 否则会出现下面的情况 $ adb

明日方舟脚本1.0（python\\adb\\cv2）

阅读更多关于明日方舟脚本1.0（python\\adb\\cv2）

一、目的《Python从入门到实践》第14章拉拉杂杂“抄”完，急于练手，便捡起以前一直想写却没写完的“鼠标键盘模拟”程序。二、思考图1.0 auto_game思考方向如图1.0，思考了两种实现方法。第一种方法是在电脑层面模拟电脑鼠标点击。使用pyautogui库实现之后，MUMU模拟器内运行游戏并未做出相应反应。更换20180111版本MUMU，仍然不成功。如果仍想采用这种思路，就需要更换模拟器软件，或者采用驱动级鼠标键盘模拟。本文对此不再进行讨论。第二种方法通过使用adb命令控制安卓手机实现。下面对第二种方法予以讨论。（一）模拟过程如图1.1所示，明日方舟1-7刷图可以分为三个部分：开始（①、②）、等待（③）、结束（④）。图1.2 1-7刷图过程 1.开始阶段（①、②）需要在两个特定位置（“开始行动”）点击两次。 2.等待阶段（③）需要等待一段时间。 3.结束阶段（④）需要在除“获得物品”之外的其他地方点击一次。（二）实现思路 1.判断当前游戏阶段使用adb命令截图，cv2判断特定图形出现在截图中的可能性，超过阈值，即为出现特定场景。 2.特定场景时发出点击命令 3.点击位置伪随机 4.点击时间间隔伪随机 5.特殊情况开始阶段的①、②两图需要点击的按钮范围存在重合部分。可以将两次独立的判断后点击合并为：判断出现场景①后，点击两次。结束阶段的④图