I tried to install Android Studio and it ended up taking up all of my free disk space. How do I uninstall it? The application reports it uses 400MB and /user/me/Library/Android directory reports 8GB. Can I delete these two directories? I would like to try and start fresh.
I'm on Mac OSX Mavericks.
Update:
I was following the instructions here,
This says, "Android Studio provides everything you need to start developing apps for Android".
The next page says, "By default, the Android SDK does not include everything you need to start developing." WTF? Which one is it?
So following the instructions on that page it says add these items:
I selected the items it recommended and noticed some items it mentions where already installed while others were not (the icon on the far right of it's name).
I clicked the minimal amount to install and clicked next. Half way through the download I start getting Low disk space warnings. Next I get Android out of space errors. So I cancel and look back at the application directory and that's at 400MB. I then remember from somewhere that it said something would be installed in /Library/Android. I check that directory and it's 7.4GB.
Most likely, you can just prune the sdk directories.
On Mac OSX Yosemite, my android sdk folder was taking 18 GB two minutes ago. Now, it's just 3.19 GB (not including Android Studio), after having deleted the packages I'm not currently using.
From Android Studio, select Tools > Android > SDK Manager.
Keep the tools. Keep the latest android sdk (currently at api level 21). That means, inside the folder api level 21; keep "SDK Platform", keep the "x86 emulator image for 64 bit", delete the "intel x86 emulator image for 32 bit", keep the "Samples for SDK", keep "Documentation for Android SDK", and keep "Sources for Android SDK"
For the "Google APIs", only keep that if you plan to use the google maps api, or some other google apis. Most likely, you can just delete that one as well, and download it again should you ever need it.
But do delete the package for "ARM emulator image" and all the other packages for the other api levels. Android is backwards-compatible, so targeting the latest SDK does not require additional SDKs even if your minimum SDK is very low.
From the extra folder section: Keep the "Intel x86 Accelerator (HAXM installer)", keep the "Android support repository" and keep the "Android support library". You can delete the "Google Repository" (although, I've personally kept that one, so you'll probably end up with even less than 3.19 GB once you delete it).
And if you still need even more space, I guess you could even remove the "SDK Samples" and the "Sources of Android SDK" (not that I'd recommend doing that. Do it only if you really need the space). After all, if Windows Phone and iPhone developers can survive without having access to the source code of their platforms, there is no reason most of us couldn't survive without the source code to our platform either.
I'm assuming you're using OS X here. You can simply open the applications folder and move Android Studio to the trash. Same thing goes for the SDK.
Though, I'm not sure why it says it's taking up 8 gb - it isn't nearly that big for me. My Android Studio is ~500 mb
EDIT: Also see #stkent's great find in the comments - he linked you to How to completely uninstall Android Studio?, which provides an answer that will completely remove all traces, so that if you reinstall, it is completely fresh.
Related
I have a quite big problem as accidentally removed the file, it is already removed from the bin on Mac. Now in Android Studio I cannot run emulator and I get the below message:
Can anyone help me please? What should I do now? Is there any way I can reinstall this missing file for Android studio?
Many thanks in advance!
EDIT: My problem was a missing .exe file: qemu-system-i386. I couldn't find any working solution, tried installing various images versions, was creating new emulators. I decided to uninstall Android Studio and proceed with the new installation. I used a free tool, AppCleaner, to remove the Android Studio, you can read more about this here: http://lifehacker.com/5828738/the-best-app-uninstaller-for-mac. But still had to remove manually the entire sdk tools directory. You can actually do the same from the terminal, here is the thread how to do it: How to completely uninstall Android Studio?
Anyway, the important thing it is working now! :D
1) Open the SDK manager (see the image below):
[
2) Launch the stand alone SDK manager
3) Ensure that you have downloaded and installed the SDKs and tools for Android version that you'd like to emulate. In my case I use API 25. You should also have the Intel x86 Intel Atom System images installed.
4) Then open the AVD Manager and "Create a Virtual Device"
5) Select the API level that corresponds to the one you installed in the previous steps. In the newer versions of Android Studio you can also download and install the System Image you desire in this menu.
When I go into the SDK manager in Android Studio, and I go to the tab that says SDK Update Sites, It says "unknown error" next to Google Inc. (x86 System Image). I can never update Google APIs Intel x86 Atom System Image and I think its holding me back on some features to some apps. How can I fix this?
Just go to File -> Invalidate Cache/restart -> Invalidate Restart. Once done, Android Studio will close and restart. Allow all the updates to be installed and along, Intel Atom x86 system image will also be installed.
If none of the suggested solutions works for you, try to run Android Studio as Administrator.
Also ensure there's enough disk space on the partition which you installed Android Studio on.
It takes approx. 4Gb even though it says ~930mb. Keep that in mind!
To ensure diskspace is not the problem go to:
File→Settings→Appearance & Behaviour→System Settings→Android SDK→SDK Platforms
then check [X] Show Package Details and scroll to the Android package you want to install (e g. "Android 7.1.1 (Nougat)").
Check [X] Google APIs Intel x86 Atom System Image and hit Apply. Warning will appear in case of insufficient disk space.
Delete the folder .downloadIntermediates from your SDK location. It works for me
I had same problem with android studio and performing below steps solved the problem.
Settings > Appearance & Behavior > System Settings > Updates > Canary Channel > Check Now > Stable Channel > Check Now > Android SDK > Show Package Details > Apply
No Error
Download and Install Update
I felt super stupid. I landed on this page after googling the error. I tried the Invalidate Cache thing. didn't work. Looked deeper into the error and tried doing as it said, manually removing the system image it was trying to overwrite. I couldnt. It was in use. wtf. oh, the emulator i had going slipped past me, it didn't shutdown with the android studio restart and updating.
Closed the emulator and the upgrade finished successfully instantly.
Check for instances of the system image file running, the file from folder C:\Users\NAME\AppData\Local\Android\Sdk\system-images\android-29\google_apis\x86
You need to reinstall it.
Run "SDK Manager" in stand-alone mode,
you should see the item marked as broken at the bottom, In "Extras" folder.
Delete the package, "Broken Intel x86...//"
Run the app again. It will be reinstalled.
I am developing an android app and want to test on the latest version of android, also I need to check some apps from google store, so Is there a way to run full android OS from my PC, I searched and found some telling to use virtualbox, but I tried the installation steps and it didn't work, are there any other suggestions?
You can use GenyMotion for that. It provides Android VM that are really better than the one of SDK (chosse images of Android machines that are provided with google apps for retrieving apps from Play Store).
Assuming the normal android sdk is already installed, using the Android SDK manager:
Install the Intel x86 Atom System Image of the latest api level.
Install Intel x86 Emulator Accelerator HAXM which can be found in the folder called "tools" inside the list provided by the Android SDK Manager (for those of you on Linux, you'll have to hunt around and install kvm instead).
Create an AVD using the AVD Manager
Make sure you select the x86 version when creating the AVD, the select box defaults to ARM.
And tick the checkbox Snapshot, to make sure your image keeps anything you install on it between restarts.
Fill out the rest of the parameters, create your AVD, and start it (the first time it runs will take the longest, the second time will be faster). That being said, it's still a good idea not to shutdown the emulator between tests because of the reboot time.
AVDs based on parameters alone and not actual device names will also be faster than the ones that have specific model names, but bear in mind that those with parameters will include less stuff. So it sounds like you'll want to make sure you select one with a specific phone model name.
Genymotion should work just fine as well. Just note that for the non-AOSP phones, you may have to install some of the system apks separately (because of licensing reasons, but those system apks should be very easy to find if you just google around for them)
I've just did fresh installs of the ADT bundle (20130522) and the Android Studio. (because my eclipse install got screwed up again, but that's another story.)
In either version, when I launch the SDK Manager, I don't have any system images for 2.2, only an x86 image for 2.3.3, and no images for 3.0, 3.1, and 3.2.
I couldn't find any official word as to why they've been removed. Is there now a better way to test on those platforms rather than by using the emulator images?
Check the "Obsolete" checkbox, towards the bottom of your SDK Manager window, and you should see them.
More specifically, up until Android 4.0 (or thereabouts), the ARM emulator image was not broken out into a separate download, and so you get that from the base "SDK Platform" download.
Why would people expect the ARM image to be part of the SDK platform for <4.0, when it is broken out separately for 4.0+
Well, for those of us graybeards who have been developing for Android for a while, it's second nature... :-)
More seriously, I suspect they did not want to attempt to repackage the older releases. Bear in mind that the only available platform for Android was ARM up until about 2.3, and so having a separate ARM image download would have seemed odd back in the beginning.
How can i enable my app to be moved to the sdcard?
-edited the title in order to make question more relevant to the answers given.
You have to set android:installLocation entry in AndroidManifest.xml file (preferExternal or auto values will do).
NB! For this build target should be API Level 8 (Android 2.2).
You can also set the android:installLocation and still target to Android 1.6.
In your AndroidManifest.xml you have to insert the min SDK Version like that
<uses-sdk android:minSdkVersion="4" />
This will make sure your application works only on Android 1.6 and higher. This will of course, cause an compiler error in your Eclipse project sapce. That's because the 1.6 SDK don't know about the android:installLocation. To fix this, right-click on your Project in the Eclipse Project space (assuming you're using Eclipse, don't know how it works in other IDEs or with Ant build) then go to the "Android" Option and select "Project Build Target" to Android 2.2.
This will remove the error shown above and you can compiler/export your APK file. This way the APK will work on Android 1.6-2.1 as usual and on Android 2.2 it will enable you to use SD card to install/move the app too.
However a Word of Warning:
This can be a source of incompatibility, if you're not careful. So an increased testing phase is required, because you won't notice directly if you use an 2.x feature, because Eclipse wont show it as error, because it uses the Android 2.2 SDK as reference.
So you basically have 2 choices:
1. Only do the steps above when you're exporting/signing your app (i.e. just before you're about to publish this new version) and then set it back
or
2. Extensively test your Applications on 1.6 Device or Emulator and see if it crashes at any point, because the App uses a feature only available on newer OS' than 1.6.
Depending on the compexity of your application, the first one is usually the safer one, however bears the risk that you forgot to do it once. This would have the consequence that for this one update the user won't have the possibility to install it on SD card. Choice 2 has the problem, that if you don't test everything well enough, you App may suddenly ForceClose when an Android 1.6 devices try to call features/functions only available in 2.x.
Please follow the below procedure for Android phones.
Copy the Android SDK to your system.
Connect your mobile to system and enable USB debugging option in your mobile.
Open cmd line and go to the path android sdk\platform-tools
Run the command adb shell pm setInstallLocation 2
Go to settings in your mobile and check the "Move to SD card" option is enabled or not.
This tutorial has clear instructions to move the app to SD Card
http://mobile.tutsplus.com/tutorials/android/move-to-sd-card/
Also it has pointer to when to use the SD Card feature http://developer.android.com/guide/topics/data/install-location.html#ShouldNot