I run Android SDK and AVD Manager in Vista and have problems installing components. The installer downloads components successfully, but at the end of the installation it hangs for about minute and then asks to disable AV software. If I choose 'No', the installer stops with error message like: "Filed to rename directory '...' to '...' ". Thus, I have to unpack downloaded components and place them to proper folders manually.
I have no AV software. I assumed that the installer requires Administrator rights, but runing it as Administrator didn't help.
If anybody fixed the issue, please advice something.
Thanks.
Had same issue on Windows 7 32-bit. It worked eventually for me. Disabling your AV has no effect. It's probably a zombie copy of the manager.
Exit Eclipse etc...
Close most other apps, Run eclipse, run the manager (you have to click on the menu twice for some reason), I eventually got it installed OK on my 3rd attempt - just try again.
Related
I'm building an app in Android Studio (beta) 0.8.9, though I can't seem to get emulators running. I've made a Nexus 4 and 5 emulator through the options, but I can't seem to get them started. It shows this in the Run App tab.
Waiting for device.
"C:\Program Files (x86)\Android\android-studio\sdk\tools\emulator.exe" -avd smallEmulator -netspeed full -netdelay none
So either it's not starting up, or I'm just an impatient SOB.
I've also downloaded Genymotion and started up an emulator through that, but now Android Studio doesn't recognize the emulator anymore. I try to run my app and check for any running devices, but it doesn't show up, despite the fact that it actually is running.
I've added the Genymotion plug-in, to no avail. No idea what went wrong.
I also have a One Plus One, which I'm not sure how I can debug on that. They don't seem to have drivers for that and haven't immediatly found anything on Google so far.
Any help would be much appreciated.
EDIT: I fixed my problem. I used Genymotion to fix the problem. The running emulator wasn't turning up, because the android SDK's weren't linked to one another. Genymotion and Android Studio used different ones. So I edited Genymotion's settings to use the same one of AS and now it works!
First of all, update android studio. Check if the emulators run from the AVD manager outside Android Studio, I mean by starting it up manually from ur SDK installation folder (AVD Manager.exe) . Check the path of ur emulator in .ini file in C:>Users>user-name >.android>avd. U can make a system variable for ur SDK folder "ANDROID_SDK_HOME" and place the .android folder's content there (the whole .android folder). Sometimes "resetting the adb" after u run emulator may work.
There may be an easier fix than what was previously mentioned. Try opening Android Studio, go to File, Settings, plugins. Select the “Browse Repositories” button at the bottom of the page. Scroll down the displayed page to find “Genymotion”; select it and install it.
When it has installed, restart Android Studio. Again, go to File, Settings, then go to Other Settings. Genymotion should show up as an option. There will be a field that asks for the path to the Genymotion folder.
Mine was: C:\Program Files\Genymobile\Genymotion. At any rate, enter the path, click Apply or OK and Android Studio should recognize Genymotion (You may need to restart AS once again). Now you should have a small red icon on Android Studios tool bar; when you hover over it a pop up that identifies it as “Genymotion Device Manager”. Click on it, select a device to load, click start and allow the virtual device to start completely. Now run your Android Studio project; the Android Studio “Device Chooser” will pop up. You should see the Genymotion device you’d started previously, select it and you’re good.
Hope this helps…
Here is what's going on... It doesn't matter if I'm in Eclipse or manually launch SDK Manager. Once I'm in the Android SDK Manager I have packages selected and I click Install x packages... I accept the License agreement then click Install. It is then my computer restarts itself before it downloads and installs anything. It restarts before I can see any error messages. It does this every single time. I have re-downloaded everything and tried it from scratch, but I still get it. Why is it doing this and how can I prevent it?!
Since nobody on here could help me I figured it out. Here's what I did. First, I gave all permissions and took away read only attributes for the folder sdk [it may be named something different on your system] I then created a copy of the tools folder and named it tools 2. I opened a command prompt using administrator and use the command "android.bat avd manager" and i was able to update my sdk tools and all without any issues. Thank you me.
So I'm trying to create an AVD Simulator, and I keep getting the "No system images installed for this target" error when trying to create a 4.2.2 system even though the image is installed (See picture of SDK Manager).
My system is x64, does that make a difference?
After SDK Update I had the same problems with API Level 19 and
in my case restarting eclipse didn't solve it.
For some reason, in the sdk/system-images/android-19 directory, sub-folders with system images (armeabi-v7a and x86) were placed within "default" directory.
I just moved them into android-19 directory (if eclipse is running at the same time, you will have to restart it).
You just need to restart the tools. I have seen this bug before. The appropriate installed images will show up after the restart.
You can also try to refresh within the 'Packages' menu, but the easiest thing, is to restart the tools.
Goto sdk\system-images and open the folder of the current API you are using (eg.android-19 folder in your case).
Now you'll find a folder named 'default', open it and you'll see the folder named 'armeabi-v7a' or which ever system image you've installed.
Now move the folder 'armeabi-v7a' to the directory sdk\system-images...i.e simply out of the 'default' folder.
That's it.
I had the same problem and this method worked for me. :D
I restart eclipse.it worked out for me,issue is resolved.
I just had this same issue. My problem was solved by killing eclipse (Command + Q) because I'm a Mac user. So, if you're under other operative system be sure to kill the Eclipse's process and relaunch it.
Lots of potentially useful answers here, but none of them were worked for me.
On my Mac, I have both Android Studio and Visual Studio installed. One would hope that they would automatically look for an Android SDK in the same place, but no, not necessarily.
In Android Studio, go to Tools -> Android -> SDK Manager. In the window that pops up, make a note of the Android SDK Location. It should be something like
/Users/[user]/Library/Android/sdk
Next, in Visual Studio, go to Tools -> SDK Manager. In the window that pops up, the path that should be selected on the left is Projects -> SDK Location -> Android. On the right, click the Locations tab. For me, the Android SDK Location path was set to something like
/Users/[user]/Library/Developer/Xamarin/android-sdk-macosx
I changed this to the path that Android Studio was using, and that fixed the problem for me.
Very simple. I restarted Eclipse, reloaded my project and when creating a new emulator, the problem is gone
Found this thread when I did a search on Google for the same error.
So I just wanted to add that if anyone comes across this thread but you are using Android Studio. You only have to restart the Android Studio. I did and now I can see what I installed.
Make sure you have rights to all the files in the android-sdk-linux directory using:
sudo chown $USER -R ./android-sdk-linux
I have a problem with AVD. If I launch it from eclipse, load well but doesn't appear in screen. After that, I try it from terminal but I got the "Segmentation fault" message. Reading another topic I read that it is problem with 20 version of android SDK and to fix it, I should try: .../tools/emulator-arm #nameAVD. It works.
But I still have a problem, I need launch AVD from eclipse to debug applications! Can somebody help me?
Thak you a lot.
Can you tell us a bit more about your system, build, and what version of Android/Eclipse you are using?
if not, try uninstalling and re-installing eclipse, but use the Eclipse Classic version from http://www.eclipse.org/downloads/
then if it doesn't work still, try to delete and redownload the android SDK.
if that still doesn't work then chances are you have something wrong with your system settings
======================
EDIT*** here is a possible TEMPORARY solution..
only use Eclipse to clean/Build your projects, and use your terminal to install your app onto your emulator.
to build an APK without running, right click on your project, go to "Android Tools" and hit "Export Unsigned Package", which will prompt you to store the APK on to some place. Then, open up your AVD emulator and terminal. on your terminal, "cd" into the directory that you saved your APK file (like inside /...../Your Project/bin/) and then run the terminal command "adb install yourAPKfileName.apk"
this will automatically install the newest APK to your emulator and run it. since this process for building is a little slower than usual, i would recommend only building/running when you need to, and always export the APK to the same place, and have your terminal open to the same place, so that when you press "up" on the terminal, it repeats the last command you used :)
Here is how my story goes. At first, I installed the Android SDK in the default directory it selected, which was Program File (x86) (which I thought the default was supposed to be app data?!) After SUCCESSFULLY pulling the APIs I quickly realized the mistake I had made, due to spaces being in the name, so I then uninstalled it and re-installed it in my D drive under a folder called development.
That all went fine, but when I tried to pull the SDK, I received the "A folder failed to be renamed or moved" message. I then tried disabling my anti-virus (more on that later), closing all other windows, and even ending windows explorer, but nothing changed.
To disable my antivirus, I used it's control panel (Avast BTW) to turn off the shields. What I really wanted to do was end the process, but, and here is the big but, Access Denied! I even ran taskmgr.exe as admin, but no success. Can anyone explain why that is? Anyways, after getting fed up with it all, I just booted into safemode with networking, and all is well for now, but I really would hate doing this every time I need to update the SDK, so any suggestions on how to fix this would be a great help, especially how to end my antivirus process so I can see if that's the problem.
EDIT: And I also did all that while running the Android SDK manager as administrator from the folder it is installed in.
I assume that the problem happens because the upgrade program wants to upgrade itself directly while it is running. My solution is that every time before you want to install something new, make a copy of \<sdk dir>\tools dir in the \<sdk dir>\ path, and then, upgrade or install something by excecuting android.bat in the copied tools folder. This works for me.
try rename "platform-tools" folder as "_platform-tools" and create a new folder as name "platform-tools".
that's work for me!
Having eclipse open sometimes causes this.
Open the Android SDK Manager then close eclipse before you press the "install packages" button and it should be fine.