I have already tried with following process:
Click Start, and then click Control Panel.
2 .On the Control Panel Home page, click Programs.
In the Programs and Features section, click Turn Windows features on or off.
If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
In the Windows Features list, select Telnet Client, and then click OK.
After successful installations, run the same telnet command.
iii). Type:
power capacity 100
After following the mentioned process, emulator stops working?
If anyone could help me in this regard, please leave a comment.
Is it only the power command that makes the emulator stop? Try running other commands on telnet and let me know
If it is only power that does not work then try this
In your avd manager check the details of your emulator. See to it that hw.battery is yes and then run your emulator again and try using the power capacity 100 command from telnet localhost. It should work
use telnet command:
power status discharging
Related
Have been trying to build and run a custom Azure IoT Edge Module, in VS Code, on macOS. When I try to Build and Run IoT Edge Solution in Simulator, the
Please setup iotedgehubdev first before starting simulator
alert pops up. Completed the setup successfully and yet, every time this very warning pops up and am unable to perform the 'build and run' process.
I had the same issue today working on a fresh linux install on my laptop.
I figured that the simulator needs 3 steps:
setup (using a real device connection string)
start (actually runs docker-compose, and if use -v, will show docker logs)
stop
I setup vscode and going through the example at
https://learn.microsoft.com/en-us/azure/iot-edge/how-to-vs-code-develop-module?view=iotedge-2020-11
then find out several things:
first vscode detects that there is a DevContainer definition, and offers to open in DevContainer - which I did but is unexpected
that means that setup for azureiothubdev on the host linux is unnecessary
and that had issues with versions of pyyaml , had to downgrade to 5.4.1
will now uninstall this
second, when I try to right click (contextual menu in Azure Iot Hub extension) on the device I choose to run the simulator as, it does 'setup IoT Edge Simulator' correctly.
third, when trying the command palette approach to 'Run IoT Edge Solution in the simulator', it does what the OP describes, with a popup at the bottom asking to choose the device, and when done with setup, just stops there.
In the end, I read the instructions related to the Azure Iot EdgeHub dev tool
https://github.com/Azure/iotedgehubdev.
Here is how I got it to work:
ran 2 actions in contextual menu for deployment.debug.template.json,
Generate IoT Edge Deployment Manifest
Build and Push IoT Edge Solution
ran 1 action in the context menu for my device in AZURE IOT HUB extension
Setup IoT Edge Simulator, which runs commands in the terminal
ran one command manually in the terminal to fill the gap
sudo "iotedgehubdev" start -d ./config/<your debug deployment file> -v
stopped on a breakpoint in the sample module (the whole point of the endeavor)
in your module, set a breakpoint, in a message handler perhaps
enter debug menu (CTRL+SHIFT+D)
select the config for your (C#) module with 'Remote Debug'
click Start Debugging (empty green triangle) or press F5
select the process matching your entrypoint in the dockerfile (mine was 'dotnet SampleModule.dll')
At this point you are attached to the program running in a container, and the breakpoint should get hit as expected.
you can't use the command palette to stop the simulator, if you have the -v option where docker-compose gives you logs. the command gets written to the terminal and does nothing in the middle of the logs.
you just have to Ctrl+C in the terminal to end the simulation, though edgehub keeps running.
You stop it with
sudo "iotedgehubdev" stop
I am assuming you have Azure IoT Hub tool extension for VSCode installed. In the explorer menu pane (on left), navigate to 'Azure IoT Hub' -> Pick your Edge device and right click. You will see option 'Setup IoT Simulator' and click.
It will automatically fetch the device connection string for the device. Then you should be able to build it.
Whenever I run code in VS Code while connected to a wireless network without internet access, using either "Start Debugging" or "Run Without Debugging" from the "Run" drop down menu, there is a delay of around 60 seconds before the code is run.
As soon as I select the option to run the code, the control bar as appears, and the progress-bar in the "Run and Debug" tab starts moving. However, nothing happens until after the delay.
Control bar:
Run and Debug progress-bar:
If I manually run the code in the terminal in VS Code, using a command like,
python3 sample_code.py
the code is run immediately. Similarly, if I connect to a network with internet access, or disconnect my WiFi entirely, the code is also run immediately.
I am running Ubuntu 18.04.5 LTS am using VS Code version 1.58.2.
Is there a way to remove this delay?
I can see the device list on VSCode in Windows.
And I can select any one.
And the emulator is opening.
But I can see a single message. "Waiting for a connection from Flutter.."
Application does not open.
It doesn't get any errors either. Waiting like this.
Make sure that your API level you're running your device on is the
same as what you have installed on Android Studio.
1.1 Click on the SDK Manager button around the top right corner of AS (The icon is a box with a down arrow next to it).
1.2 Choose the same API level as your device, (When I didn't do this I had a partial install and it took some time to compile), then
click apply and wait for it to install.
We're going to run the project to our avd or mobile device from the directory of ourproject.
2.1 Open up the Command Prompt (preferably as Admin), and chage the directoy to where your project is, the command should look something
like this:
cd Documents/flutterprojects/yourflutterproject.
2.2 Finally type the command flutter run.
Restart the Emulator by holding the power Button and Selecting restart and then try again.
if that failed to work, simply restart your computer.
For example, want to know that sample.exe creates MyDriverService and runs Start / Stop to run myDriver.sys
I tried using Process Monitor, API Monitor but there was only information from Services.exe
It's easy just on computer main screen at my computer logo click right click, then in menu select manage, you will see one new open window with computer information.
In left side menu in last you will find services and applications, click on it then click services you will find their all your computer running and stop services.
Other way you can only see the running services by right clicking on computer screen down window bar then open start task manger, one pop up window will open there will be information of your computer running application running process and many other useful information's
Hope you will find it helpful
I am really struggling to get Google Chrome Remote Debugging to work! I have the phone setup and confirmed:
Then below are what I see in chrome://inspect/#devices and also F12 (both open at the same time);
It flashes with the "Connected" for about 3 seconds, and then goes to:
Offline
ZX1G324RSV Pending authentication: please accept debugging session on the device.
It's driving me nuts, as it should be simple to do, but it just doesn't want to play ball :/ Do I need to do anything special? I've used it before on this PC and although I had some fun and games with it the first time around, it worked after that.
There seems to be a ton of posts/articles about how to fix it, but none of them are working for me. https://bugs.chromium.org/p/chromium/issues/detail?id=450492 for example.
Download Android SDK here ("SDK Tools Only" section) and unzip the content.
Run SDK Manager.exe and install Android SDK platform tools
Open up the Command prompt (simply by pressing the windows button and type in cmd.exe)
Enter the path with ex: cd c:/downloads/sdk/platform-tools
Open ADB by typing in adb.exe
Run the following command by typing it and pressing enter: adb devices
Check if you get the prompt on your device, if you still can't see your phone in Inspect Devices run the following commands one by one (excluding the ") "adb kill-server" "adb start-server" "adb devices"
Here are the things that you can try:
Try different USB cable(s)
Try different USB ports on your machine(for some people using 2.0 port worked out)
Try the same process, with unchecked 'Discover USB Devices' in chrome://inspect (then Chrome will connect through the ADB server, not directly) ==> This solution worked in my scenario.