The android device monitor in Android Studio is not running no matter how many times I click on it, there are no errors showing up or warnings.It's just not running, I don't know why this is happening because I used to open it with no problems whatsoever. what could the problem be?? THe android sdk path is correct and the emulator is running and there are no errors in the code. Please help
Try using ALT + 6 to open the device monitor window, or are you saying that Android Studio is not finding your device?
It takes an awfully lot of time for the ADM to finally appear. Just wait, do something else while it is opening.
Related
I've been working with PhoneGap for about two weeks now, yesterday I've build a new android app all went well except that the app starts very slow on my android device. It first shows me for three seconds just a black background except the navbar. So I want to ask how to boost it up or which files I could remove or what I've done wrong please I would be happy if you explain me also the file structure. Thanks in forward for your answers!
Your question is little bit vague. Please, give us more information about your app, about your config and what you’ve already tried.
If my app is slow on any device, I do generally the following:
Check if the same problem occurs in the browser
What’s going on at the start of the app in the browser (Chrome Dev Tools)
If nothing unusual happens, check the logs on the device
For Android, I’m using Logcat for checking what’s happening on the phone.
In order to use Logcat:
1.) Enable debugging mode on your Android phone
2.) You need Android Studio
3.) Connect your phone to your computer and start Logcat in Android Studio 3.1.2
4.) Check the logs while you are starting your app on the phone
So I open my Android Monitor Device to check the database that I have on my project and suddenly gave me this error:
Here is the error of the Android Monitor Device
So I look up if there is a way to deal with it and I ended up finding the folder of my monitor (see below).
Here is the Monitor that I found
It works perfectly but it is not showing anything. See Picture below...
Android Device Monitor with nothing on it
Here is the configuration file of the monitor if it will help.
Monitor Configuration Setting
I did not have this problem before and just happened today. There was an update that asked me last week, I don't know if that would affect my Android Studio running the Android Device Monitor. I have no idea how to fix it. I also saw that there was called Eclipse. What is the difference?
I am new to Android Studio (running the latest updated version) however I am trying to debug with Android monitor and Logcat only seems to work once then stops reporting!!!
This occurs for all my projects?!?
If i restart Logcat it just clears the messages.
I assume the emulator cannot connect to the debugger for some reason.
When I restart Android Studio logcat reports, but when I close the app running on the emulator it stops reporting.
This CANNOT be the default intentional behaviour, does this affect other people?
Many thanks for any help at all.
Simply restarting Android Studio is the best solution
By default if your close the emulator it unattaches itself from Android Studio, stops Android Monitor and logcat and doesn't reattach when starting again. If you stop it in android studio and run it again the emulator is still attached to Android monitor and logcat.
I assume the emulator cannot connect to the debugger for some reason. When I restart Android Studio logcat reports, but when I close the app running on the emulator it stops reporting. This CANNOT be the default intentional behaviour, does this affect other people? Many thanks for any help at all.
An answer to this part is that it does not sound like expected behavior of Android Studio / logcat / emulator. I am able to start and quit the app multiple times, each time logcat connects when the app begins and disconnects after. I can start the application through Android Studio or through the apps menu on the emulator. I can quit and restart the emulator.
An easy thing is double check the dropdowns along the top of the logcat display, especially the emulator, app, and filter selectors.
I once had an issue that sounded similar, with logcat not reconnecting. The issue there was my terminal and IDE were running different ADK installs and they were competing for the logcat connection. So what you describe is possible, but not the norm. Perhaps another debuggable app or connected device could cause similar confusion.
I just installed Android Studio, and I am very new with this program.
So when I run the Android Emulator it says: "To Start Android, enter your password", although I have never set a password. When I just enter a word with 4 letters it says "The Password you entered is correct, but unfortunately your data is corrupt".
After that, I have to Reset the Phone, but when I do that the same menu with "To Start Android, enter your password" appears.
Maybe it is just an easy mistake, but as I said I am new with this. I also did some research on the internet but I did not find anything useful.
this is the 2 images that it showe me:
1)
2)
and after i clicked on reset phone, nothing happened.
I would be very glad if someone has an answer for this.
This is a late response, but thought this simple fix might help anyone else who comes across this problem in the future. What worked for me is the following:
In VS2017 ==> Tools ==> Android ==> Select: Android Device Manager
In the Android Device Manager window, you'll see your Android Emulator.
Make sure the far right column contains the button "Start" (if "Stop" appears, click "Stop")
Right Click the device, and select the "Factory Reset" option in the menu.
Your emulator should now be working. Good luck.
open AVD and right click on the emulator choose ->Wipe data option.
Check that your avd folder path doesn't include national symbols (in my case it looked like C:\Users\Пользователь\.android).
After I changed this path everything is working.
See this post of how to change path:
Possible to change where Android Virtual Devices are saved?
Check out "Viewing and managing your Avds" part. Try wiping data of your emulator or create a new emulator for yourself.
https://developer.android.com/studio/run/managing-avds.html
enable GoogleAPIs and Google Play Store
Change the Android version. I was creating an emulator with Oreo 8.1 and got stuck in with the same issue.
I created another with Marshmallows 6.0 and no more asking for password.
Then if you are using Oreo 8.1 try with antoher.
I created a virtual device, and after, I had to reinstall the emulator.
When I booted the virtual device, I got this issue.
I deleted it and made a new one, and it worked fine.
Just go the AVD Manager and Wipe Data. The problem will be solved.
Here are the steps I followed after my device corrupted.
Close your emulator
Open AVD manager, right click on your device and click "Cold Boot Now" button.
Sorry for a very Late Answer. But you can't create a x64 Virtual Device on x64 System. Your device needs to be x86.
Just a warning to anyone getting this error on an emulator instance that was working and you cold booted or something. I got this error and just stopped and cold booted again and it was gone! So try that first before wiping your emulator instance unnecessarily.
Deleted the device in the Device Manager and created a new one with a higher OS version (Oreo -> Pie). The error disappeared. Did not find the real reason yet.
i'm using titanium appcelerator for developping an opp on android but i think this question can be answered by any android developper and anyone else using the android emulator.
It's already too long to wait for the emilator to be ready and for me always the first execution which makes the emulator for the first time stops on the "waiting for the emulator to be ready" step and i have to restart the app again and if the new launched app will start a new emulator instance it will be worst.. So is there a way to force always using the already created emulator instance ?
you mean emulator?
If there is an emulator, it will not start new one .
Do not close it .
I would suggest that you install Genymotion to use for emulation. Titanium Studio will see this as a device, rather than an emulator. On the flip-side, I'm not sure if debugging works with it yet. You may need to look for mods to make to get this working.
After installing Genymotion you select some emulators from their available list. You'll start the Genymotion emulator yourself, rather than Titanium Studio starting it for you. Titanium Studio's list of devices will need to be refreshed or restart Titanium Studio. Run your project. Titanium Studio sees the device more like a physical device, so it won't keep opening a new one on you and speed up the process a bit.
https://www.genymotion.com/
There my be a more official way to fix the Android interaction, rather than my idea of side stepping it.
Simple :
Goto Terminal/command prompt
Type in adb connect 127.0.0.1:5555
Now the emulator will be seen as device to Titanium studio, enjoy!