I have followed all the necessary installation and setup steps for Eclipse 3.4 + ADT + Android SDK on Windows 7.
I followed the Hello, Android tutorial in Eclipse and code-completion also works like a charm. No errors shown.
unfortunately the emulator never shows up.
When I run the project. I have fullfilled the same steps in a virtual Windows XP machine and - though very slow - it does work there.
I have not found anything about known problems with Windows 7. What can I do?
Try launching the emulator from the command line with the -verbose option as this may help determine why it is failing:
emulator -verbose -avd <avd name>
To a get a list with the names of AVDs you've set up enter:
android list avd
(If nothing shows up when you list your AVDs that's your problem.)
Ensure you are running the app as an android app and as Dave Webb suggest ensure you have an emulator "profile" created. I created one to meet my HTC Hero and I use Windows 7 (x64).
NOTE: You might also want to unplug your HTC device, if its connected to the PC. I've noticed that if its plugged in the apps will download and run directly on the real device. Thats probably by design and intentional. ;-)
HTH
Philip
I am developing on Windows 7 Pro with no issues. Eclipe and Emulator are all working OK.
Related
i'm using android studio in windows server 2016 and have next problem: for work task i need to start android device emulation. On windows 10 emulator works fine, but same steps on windows server cause problem -"the emulator process for AVD_Pixel3A was killed". What should i do?
p.s: hyper-V components not installed, virtualization is accessable.
You will need to to have the H-visuals turned on.. Also check to see that you have HAX installed. Also be sure to turn on developer mode within the computer... I would also run the program on a physical android device to see if you get the same issue.
Also if none of these work you might have to check to see if the server runs the minimum requirements. If it does you may have to reinstall Android Studio. I had this happened to me the other day. I uninstalled and reinstalled Android Studio and it fixed the issue.
Today I downloaded Android Studio for my Debian Testing system. I wanted to run a HelloWorld application but weren't able to run it. With adb I can install it without having any problems.
However, if I try to do it with Android Studio, it gets stuck on 'Installing APKs'. The same happens when I try to start it in an emulator (gets stuck on 'Waiting for target device to come online').
My device is a Samsung Galaxy S3 with LineageOS (Android 7.1.2) and root permissions. Android Studio recognizes my phone properly.
What I've already done:
installed openjdk
set android_home
installed all the SDK-platforms since Android 4.3 and Android Emulator from SDK tools
enabled USB-debugging
tried with MTP and PTP
tried another emulated phone
installed lib32stdc++6
restarted my computer
and probably much more
I tried to do it the whole evening and couldn't find a solution. Is there something Debian-specific because I can only find instructions for Ubuntu? I have never experienced anything close to this on other systems.
Thank you in advance.
EDIT: I am now able to use my phone to run the android application by using USB 2.0 instead of USB 3.0! Is that a normal behavior since it works with native adb? I mean, if I buy a new PC after some years which has got only USB 3.0 ports, will I not be able to use phone debugging with Android Studio or is this just an issue? It is still known since 2014 (https://stackoverflow.com/a/9548311/8292104).
However, I still cannot get the app running on an AVD. I changed graphics to software, now it shows the phone but the screen remains black and the phone won't start. What can I do to fix it?
Try to completely delete and install Android Studio again, I think that it will solve the problem
Another possible solution that worked for me is to, in the application, go to
app - build - intermediates - split-apk - debug - slices
and then delete all of the contents within this folder. Then again, this only worked for me, so I would duplicate the document in case of corruption.
I am facing this problem when i am starting my emulator from android studio avd manager. it shows the list of my virtual devices. now when i start the emulator. it shows progress to opens and disappeared in a second without throwing/showing any error.
i am using latest android studio version.
system config : Intel core 2 duo
ram : 6 GB
is this problem cause of system config? Please write your answer and feel free to ask.
I had similar issues (the simulator progress would open then disappear) on my Mac El Capital. Downloading the latest HAXM and RE-INSTALLING it fixed.
Download link: https://software.intel.com/en-us/android/articles/intel-hardware-accelerated-execution-manager
I have updated the video drivers and solved :
1. emulator problem
2. genymotion "player.exe stopped working" problem.
You should use Genymotion replace for default Android Emulator.
There are some various ways to solve this kind of problems:
-> after restarting android studio, if u are facing same problem then try below ones.
kill the adb server through adb shell and then start adb and then launch your emulator.
2.First uncheck Enable ADB Integration and launch emulator and then check Enable ADB Integration.
3.launch your adb and emulator by Debug app from run .
4.maintain the targetSdkVersion corresponding to your emulator
5.uninstall existing emulators and create new one.
delete your adb application and and download new one.
I had this problem because I had many (20) devices saved in my AVD with lots of memory allocated to each (1GB) and my laptop was lower than normal on memory itself.
I cleared out the devices in AVD and started over and it began to work normally again.
I have followed following tut to install messaging-simulator.apk on my Nexus 7 emulator of adt sdk...
http://www.orhancanceylan.com/installing-and-testing-apk-files-to-the-android-emulator-on-mac/
But, after the device (virtual) is launched (which is annoyingly slow), no further action could be performed from terminal as it gets stuck or no progress is shown. (Basically, I am stuck after ./android command. Nothing can be entered in terminal after that. How do i resolve this?
If you can't type a thing in the terminal - just open a new Terminal window and type it there.
A few tips that will speed up your emulator
Make your emulator as intel x86. and check Use host GPU
Install HAXM from the sdk manager
make the settings like this:
I use mac to develop Android.
Thanks a ton to #Uriel Frankel. Yet, all those tips and tricks given by him did not work out for me due to low memory in my macbook.
So I have used Genymotion emulator(http://techapple.net/2014/05/3-best-android-emulators-for-mac-os-macbook-run-and-install-android-app-on-your-mac-os-x-macbook-airpro/) instead of default android emulator and successfully launched the app by installing it.
You can all try above solution first and if it did not work out, use Genymotion, it's cool :)
I wanted to try my hand at programming android devices, so I followed the directions from the android website, installed the sdk, the java sdk, and eclipse. My computer is Windows 7 64-Bit, but I have the 32-bit Java SDK and Eclipse installed since hearing that there are issues with the 64-bit versions.
I am running the most recent version of the Android sdk, 4.0 R15.
I believe followed all of the instructions for installation, but when I load up a sample (Lunar Lander in this case), it loads the emulator, but will not install the app to it. ADB does not show the emulator listed when I use "adb devices", the DDMS perspective in eclipse does not detect any device either. In the emulator I have activated the USB debug setting in the developer area.
I have tried restarting the adb server, and have reinstalled a few times.
I even copied what one guy did on a youtube tutorial for a hello world program, and it still would not load to the device.
Does anybody have any idea how to get the emulator and eclipse talking so I can actually run and debug programs?
Try to adb kill-server and then do adb command like adb devices which will start adb again.
It helps in my case.
Best solution I found is this:
Open DDMS(Window->Open Perspective->DDMS)
In DDMS in the left side there is a Devices tab, a little below there is a list of items, choose little triangle called View Menu, under it find Reset adb and launch it.
After that I get my emulator detected.
Create new AVD following Window->AVD Manager->New (Give a name to your device & select the target) -> Create AVD.
Select the AVD that you created and Click Start to launch the devie.
Only on launching, the device is displayed under adb devices.
For starters, I think you can try the 64 bit versions of Java and Eclipse for Windows. I've Windows 7 64-bit edition, 64-bit java and eclipse versions and all work very well, without any glitches. I however have a question. Where exactly have you installed Android? I mean, using the installer that's available in the Android Developer website. If you've installed it in C:\Program Files, then try re-installing it in C:\ directly instead of Program Files directory. I had faced issues when the directory was C:\Program Files and then I changed it to C:\ .
I noticed that if you allocate a lot of memory to the device it can "freeze" when starting, if frozen for a sufficient period it disappears from the adb devices list. Try reduce the memory footprint of the application?