I restarted the emulated device from AVD Manager and this time logcat was able to detect the emulated device. The solution to this problem is, revert back any changes made to this file. When I installed OpenStack few months back, I made some changes (commented a few lines) to that file. All the solutions were pointing to “/etc/hosts” file. I copied the error message from Event Log window and searched for it in Google. I think Android Studio was trying to connect to the emulated device on the local machine (localhost or 127.0.0.1) on some random port. I opened it and it was showing error messages like “ Unable to open connection to: localhost:5037 due to : Connection refused“. □Īfter a few hours, I noticed a small tab in the Android Studio at the very bottom (right corner) named Event Log and it was showing a very small (very very small) red icon (generally, red means error). I applied five to six different solutions mentioned in various forums like StackOverflow, etc. It seems that there are lot of problems associated with emulated devices and Android Studio. Now, like everyone else, I too googled for a solution to my problem. To my surprise, when the run button was clicked and the “ Select Deployment Target” dialog box displayed, there are no emulators listed in it, even though the emulated device was running. I was able to start the emulator from AVD manager and see the emulated device on the desktop screen. For this step, I installed an emulator using the Android Studio’s AVD Manager.ĭownload and installation of the emulator went fine. Now, it was time to run the project and see the output. Installation went smoothly after following these installation instructions.Īfter the installation is completed, a new project was created with a basic activity containing a “Hello Wold” label. After a long time I was trying out Android Studio on my Ubuntu 16.04 LTS desktop.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |