I have used 'shutdown.exe /r /o' to restart windows 11 in advanced mode. The screen opens where I can see the Troubleshooting menu. I wish to click on the Troubleshooting menu after startup. Is there a way to do this?
I am trying to reboot a virtual device, which is currently running. If I choose Cold Boot Now
it swears "AVD .... is already running", which is true.
How to reboot then?
By pressing "X" icon of the emulator tab, you can terminate your emulator.
Alternatively, you can "emulate" reboot by long pressing "Power" icon in the emulator menu (1st icon)
The emulator in my android studio keeps showing "shutting down". I try closing it and run again, restarting my mac, but nothing worked, each time I run it, it shows "shutting down" again. even though I can see actions running below (very blur)
Click on Tools
Click on AVD Manager
Click on the dropdown arrow next to the AVD which is stuck
Click on cold boot now
This issue occurs when we forcibly exit an unresponsive/stuck AVD. AVD manager saves the state before it is forcibly exited and on the next start it continues from the unresponsive/stuck state. This is useful when we need the AVD to boot up quickly, however if you want to disable this feature entirely then follow the steps below:
In the AVD manager, click on the pencil icon
A new window will pop up. Click on show advanced settings
Scroll down to the emulated performance section
Next to boot option, select cold boot
open AVD Manager Dialog from top right corner
go to your emulator
click on the last icon on the right which is a drop down button
Click wipe data
Important Note: this will delete all data on that emulator and give it a fresh install again and might solve your problem
If that didn't work then check that you have enough rams to run both the emulator and the android studio.
I run my emulator with cold boot by command line
cd C:\Users\<your_user_name>\AppData\Local\Android\Sdk\emulator
emulator -list-avds
emulator -avd <your_adb_name> -no-snapshot-load
If the cold boot or wipe data does not work, you can try deleting the lock file. Then quit the emulator, and restart it.
In my case, AVD Manager prompted me to delete the following files, I did it, and the problem was solved.
If it shows "AVD *** is already running etc." then just connect any mobile device that after enabling debugging mode and run your app in a physical device instead of an emulator then
Click on Tools
Click on AVD Manager
Click on the dropdown arrow next to the AVD which is stuck
Click on cold boot now
First of all:
You have to close the window, or tab of your Virtual Appliance.
With this you get Android Studio to standby the Device and unlock the ADV (Android Virtual Device) files, so you can manipulate the virtualization.
Maybe you have to wait until Android Studio kill the process. If Android doesn't do this automatic, you will have to close Android Studio and delete C:\Users{YOUR_USER}.android\avd{YOUR_DEVICE_NAME}.avd and within this folder delete all files and folders with extension .lock to stay secure before start again Android Studio.
After that:
Just open the Device Manager, and click on the down arrow in the Actions section for your device, and select Cold Boot Now. This reload the Virtual Device without start or open any program.
Finally:
If Cold Boot Now worked fine, now you can run or debug your application to check that it functions perfectly. Without the device continuing with the problem that the system is still stuck/frozen.
And also you do not need to do a Wipe Data, so you do not delete the data of your application, since you can have any internal database in SQLite, which has the changes and advances that you have been implementing or creating during the development of your application for its operation.
For some reason, I can't get mouse support to work under CMDer.
It works normally under the regular CMD. I can click all I want all day. But I use CMDer as my development environment. It has temporary settings for my installation of CLang to use.
I went into the settings and enabled "Send Mouse Events to Console" but that does not appear to be doing anything. I even made sure to try
:set mouse=a
Which is on by default when ever I use the regular windows Command Prompt.
I solved this by going to: settings -> Mouse -> Mouse options: enable send mouse events to console -> save settings. Then close the cmder and open again. You should be able to navigate into a vim script using the mouse left click.
With the new update of Android Studio, whenever I rebuild my app, it always launches it on the same emulator/device. In order for me to switch devices, I have to shutdown the emulator/disconnect the device, so that it brings up the device selection screen.
Is there any way around this?
For me I had to press the red stop button in order to stop the "instant run" mode which automatically runs your app on the same device.
Once I press the stop button I can run the app again and it will bring up the device chooser dialog.
Just do this:
Select this menu:
And then uncheck the "Use the same device.." option:
Uncheck thi option: