After started android emulator and run an example app. I run the UI Automator Viewer and click button Device Screenshoot and it shows message:
I've tried to run as administrator but it not successfully!
Looks to an issue with emulator configuration and not specific to your application, try to play with configuration of your emulator
Related
I can't start the Dart Dev Tools in VS Code, when I launch in debugging mode it opens a chrome window says Connect to a running app
Enter a port or URL to a running Dart or Flutter application.
When I hover over the Dart DevTools button, it shows a port but I still can't connect to it.
Any ideas?
Start your flutter app with --observatory-port option. For example,
flutter run --observatory-port=9200
Once the app starts, you’ll see a message in your terminal that looks like:
An Observatory debugger and profiler on Android SDK built for x86 is available at: http://127.0.0.1:9200/Swm0bjIe0ks=/
Paste the URL you got from running your app (http://127.0.0.1:9200/Swm0bjIe0ks=/) into the connect dialog to connect your app to DevTools.
Hope this helps.
On Visual Studio Code: click the letter (v) while the app is running. that's it!
In Run flutter in Terminal with port you want. It can 9200 or 9300 or 9301 etc
flutter run --observatory-port=9200
On the logcat you will see message look like
"An Observatory debugger and profiler on Android SDK built for x86 is available at: http://127.0.0.1:9200/Swm0bjIe0ks=/"
After that copy and past url (http://127.0.0.1:9200/Swm0bjIe0ks=/) to dialog connect your app to DevTools
Hi run your app on emulator or real device.
On bottom of android studio you will find a run tab
on run tab there will be a message like below:
Debug service listening on ws://127.0.0.1:54675/CPu_ErpGRaw=/ws
copy (ws://127.0.0.1:54675/CPu_ErpGRaw=/ws) and paste it on Dart DevTools input field.
It will be connected to your running device or emulator
In my case the above answers did not work due I had another problem: PATH: the enviroment variables. This was because I couldn't execute flutter command in the terminal at my folder app project , so enviroment variables at system level it's necessary and I was doing this at user level for Windows. So I run flutter doctor o whatever to see if alredy the path was working and then I used the answer of #Hayeong Choi.
I am trying to launch a simple application with some labels and images on the content page, but when the android emulator starts it opens the application and shows only a white page with nothing on it. However, if I run the iOS simulator it shows the label and images. So I wonder if there is something that is preventing the page from loading? I am using Xamarin Forms in Studio on Mac.
Can you try it in a fisical device ?
Just to know if your emulator has an error...
Are you sure you have an StackLayout or another container for the label and entry ?
Hope you solve it...
I cannot get appcelrator to work with Genymotion.
Everytime i "run" - that is, hit the green run button in the top-left - i get [ERROR] : Failed to install apk on "192.168.25.101:5555"
[ERROR] : Error: device not found
This isn't useful nor is it helpful.
I can manually drag the created .apk file into genymotion and it will run it (although, irritatinly, it immediately crashes as I'm upgrading an old app to whatever new style appcelerator have decided on).
All the posts on this are from 2014 and not very useful - I also cannot get appcelerator running genymotion on a blank new project.
I installed genymotion to a different directory, but appcelerator seems to find it and start it - i can see genymotion start up.
What am i missing?
Sometimes I have seen the Appcelerator emulator wait startup timeout before Appcelerator can send the APK. What I have done is start the emulator first independent of the 'run' command in Appcelerator, then select the emulator from Appcelerator and then Run. If the emulator has started, then it will send it without having to drag/drop the apk manually.
I'm trying to run the wearable-preview-support.jar from terminal and I get the error
java -jar wearable-preview-support.jar
Failed to load Main-Class manifest attribute from
wearable-preview-support.jar
Also just trying to open the jar by double clicking gives the error:
The Java JAR file "wearable-preview-support.jar" could not be launched. Check the Console for possible error messages.
No error messages were displayed in Console.
Anyone else having this problem?
The JAR isn't a self contained executable, it is a library to build the wearable apps off of. See this page for more information about how to use it. You have to reference it as a library in your Android application in order to run it, and you will have to run it in the Android virtual machine.
Here are some steps to get Android Wear working in a virtual machine. Keep in mind it might be a little underwhelming using it with a mouse since it'll be less responsive than the actual device will be (hopefully).
The jar file should be included in your Android application, you do not run it directly.
The "Android Wear Preview app" is an application you download from the Google Play Store which runs on your real device. You can only download this application if google have enabled you do. For this to happen you need to sign up at the Google wear preview signup - once you have downloaded the application, you then grant it notification access.
This is pretty simple: I'm using NetBeans on Linux with Android emulator 1.6. I have Logcat on my android phone, but the process of getting the messages to somewhere readable isn't smooth at all.
Can someone tell me how to get Logcat running on the emulator? Is there anything I can do to see debug messages other then having to copy the apk to my phone and testing it?
Thanks in advance!
You have a few options for viewing the debug log output, assuming you have the SDK installed and your command path set up correctly:
Type adb logcat. The log output from the connected device or running emulator will appear. I usually prefer adb logcat -v time to see the time stamps.
Type ddms. This launches the stand-alone version of DDMS. It has a logcat display at the bottom.
Install the ADT extension for Eclipse, and open the logcat view. (Since you're using NetBeans I assume this isn't what you want to do, but I'm mentioning it for completeness.)
In all cases, the interaction is the same whether you're using a physical device or software emulator, because the ADB daemon conceals the details. Whatever you're doing for the device is also expected to work for the emulator.
If you have a device and emulator connected simultaneously, you can use adb -e logcat for the emulator and adb -d logcat for the device. From stand-alone DDMS or Eclipse, just pick the device or emulator from the pop-up menu.
If you have setup nbandroid you can find the adb logcat viewer in netbeans under:
Window -> Output -> ADB Log
--edit
Just followed up on the post above and started using C:\Program Files (x86)\Android\android-sdk-windows\tools\ddms which is alot better then the one in netbeans.
The SDK comes with a handy tool called ddms it should be in the tools folder of the SDK.
At the moment an Emulator is running, or a mobile phone is connected to your machine it should show up in ddms and you can see all the log output in ddms.