Is it possible to enable the "show_touches" options on android from appium? Or via adb?
I have a appium test-script, which misbehaves. I have no Idea why, and I want to see where exactly it clicks.
adb shell settings put system show_touches 1
Related
I'm trying to learn flutter and want to run a test app I'm writing with Visual Studio Code. Although I set up an Android emulator it doesn't seem to recognise it. What am I missing?
Thanks for your help!
Run flutter doctor and flutter devices, if no devices appear to be connected (in this case, emulated) you need to kill theadb server, open the emulator and then start the adb-server.
kill server using --> adb kill-server command
Start server--> adb start-server
If the issue still persists after this, try flutter doctor --android licenses
And if it still continues, please post your flutter doctor & flutter devices output.
If above not works,
try those:
Disabled and Enabled Flutter plugin
Disabled and Enabled Dart plugin
Restarted Vscode
Restarted PC
I tried creating a new flutter project in Visual Studio Code, but for whatever reason it now has a default device of Google Chrome every time I try to run it. I don't want to run Flutter in web environments whatsoever: is there any way I can disable this?
Run the following command to disable web completely.
flutter config --no-enable-web
Then restart your editor if necessary.
First, run your emulator from the AVD manager or connect your physical device while it's on debugging mode, if it's an android device, then choose the device you want to run from the flutter device selection option
This question already has answers here:
Android Studio, Suddenly got GPU Driver Issue when running emulator
(11 answers)
Closed 10 months ago.
Good night people !!!!
I am making settings in the Flutter Framework to use Android Studio, I already did a lot of the settings but when interpreting the flutter in the command line, do not find the device, so I went to look for the settings in Android Studio and gave a stop in the AVD Manager to Virtual Devices ... the error
GPU#1
Make: 8068.
Model: Mobile Intel (R) 4 Series Express Chipset Family (Microsoft Corporation-WDD 1.1)
Device ID: 2a42
I ask for help solving the problem. Here is the error screenshot.
Try to run the emulator via command line/terminal/cmd.
first, find the emulator list:
emulator -list-avds
then run one of it:
emulator -avd avd_name -gpu mode
If you cant find the emulator command, try to look at the executable in
c:\Users\username\AppData\Local\Android\Sdk then add the path to your environment.
try running emulator from terminal, forcing it to run using hardware graphics (instead of letting emulator decide on which) using command
emulator -avd avd_name -gpu mode
where mode is host so that it will run with hardware.
example:
Using Android Studio terminal move to folder where the emulator is located. Default on Win10 is: C:\Users\userName\AppData\Local\Android\sdk\emulator
Find emulator to run by listing available ones: emulator -list-avds
Run emulator with -gpu host option: emulator -avd avd_name -gpu host
Checkout the following path.
File > Project Structure > Project SDK
If there is NO SDK selected. Then Select Appropriate Android SDK by configuring it.
Otherwise,
In your terminal, add following command
adb kill-server
adb start-server
I hope this will definitely work for you.
I have a Nativescript application that I'm developing using VS Code and have no issues when I try to run it using the Nativescript launch configurations from the Nativescript extension, when I'm using a real device connected with USB or when I use one of the android-sdk emulators.
Now I need to run Hyper-V on the machine too and those emulators cannot run when hypervisor is on. So I downloaded and installed Visual Studio Android Emulator which runs fine when I launch it manually.
Problem is that the nativescript project doesn't recognize this device either with tns device or adb devices commands and if I try to launch the application from VS Code it tries to launch one of the other emulators, which obviously fails due to the hypervisor/Intel Haax incompatibility.
Did any of you had this problem before and have any solutions you can share?
Thanks.
Microsoft MSDN say :
If the emulator is running, but it does not appear to be connected to ADB or it does not appear in Android tools that make use of ADB (for example, Android Studio or Eclipse), you may need to adjust where the emulator looks for ADB.
The emulator uses a registry key to identify the base location of your Android SDK, and looks for the \platform-tools\adb.exe file under that directory.
Here We Go!! Step By Step ;)
Copy Your ANDROID SDK PATH for me it look like this :
To modify the Android SDK path used by the emulator:
Open Registry Editor by selecting Run from the Start buttons context menu, typing regedit in the dialog box, and choosing OK.
Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Android SDK Tools in the folder tree on the left.
Note : if Android SDK Tools folder doesn't exist, Create it under WOW6432Node, And open it, And Create a String Value name it Path:)
Modify the Path registry variable to match the path to your Android SDK.
Restart the emulator and you should now be able to see the emulator connected to ADB and associated Android tools.
Now! Open Your Terminal (CMD), and Run ADB command
adb devices -l
YES YES !! The Visual Studio Emulator is running, and connected to ADB!
HERE WE GOO !!
Now We Want To Create A Demo App (for example FIRSTZAKI) ZAKI is my nickname :p
On Terminal (CMD) :
tns create FIRSTZAKI
Choose Android Platform
cd FIRSTZAKI\
tns platform add android
Check if VS EMULATOR is ready!
tns devices
YES YES ^^
Finally Step (RUN/BUILD) :
tns run android
WOW ... Great :)
AND .. Good Luck ♥ — ZAKI
I'm working on ionic App and I'm trying to run App on real Android device, But when I run ionic run android in terminal, I get the following error:
Running command: "C:\Program Files (x86)\nodejs\node.exe"
D:\wamp\www\pars-app\pars-app\hooks\after_prepare\010_add_platform_class.js
D:\wamp\www\pars-app\pars-app
add to body class: platform-android
ANDROID_HOME=D:\Sdk\android-sdk
JAVA_HOME=C:\Program Files\java\jdk1.8.0_45
No target specified, deploying to emulator
ERROR running one or more of the platforms: No emulator images (avds)
found.
1. Download desired System Image by running: "D:\Sdk\android-sdk\tools\android.bat" sdk
2. Create an AVD by running: "D:\Sdk\android-sdk\tools\android.bat" avd HINT: For a faster emulator, use an Intel System Image and install
the HAXM device driver
You may not have the required environment or OS to run this project
How to prevent run app on windows emulator? I want to run app on real device that conected to my computer.
I am using windows 8 and Huawei with Android 4.2.2
::note
I have read these questions, But I didn't got the answer!
Why not work Ionic app testing on android real device?
Ionic run android does not run app on device
ionic run android - configurations not running app on device
As a complement to #OClyde answer, you could try :
adb kill-server
adb start-server
To have infos about these commands :
adb --help
Nb : Sometimes, for a reason i do not know, the connection between my phone and the computer break. Running this fixes it.
To make sure that your app is not installed to an emulator but to your device, take the following steps:
Open up your console and run adb devices. This should give you a list of all devices available (real devices as well as running emulators) to the Android Debug Bridge. If the adb command is not recognized check that you have installed the Android SDK correctly and that you've set all the necessary environment variables accordingly.
The adb devices command might give you output similar to this:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
This indicates that the ADB wasn't ready before, so in this case just try to un- and replug your device and run adb devices again to see if the device is listed afterwards.
If your device is still not showing, check that USB Debugging is enabled on your device. Therefore you first have to enable developer settings, which you can do by tapping the build number (Settings => About Phone) 7 times (no, that's not a joke ;) ). After that, you'll have the developer options in your settings menu. Open these and check "USB Debugging"
If still your device isn't recognized by the ADB, change the USB connection mode. You can either do this in the developer options as well or tap the notification shown when the phone is connected to your PC. Try MTP as well as PTP, on of those should do the job.
After these steps, it should be nearly impossible that the device is still not recognized by your PC. As soon as there is a phone available, Ionic will install the app on the phone automatically instead of launching an emulator.