Menu
I have been developing my app for around two months, in the last week i have started getting the following error when trying to compile and run the app from Eclipse:
java.io.IOException: Unable to upload file: No space left on device
The APK comes out at 3.6Mb and the emulator is a recently created fresh one with 512Mb SD card and other specs identical to the G1.
Can anyone suggest a reason this might be happening?
426
On Android StudioClick Edit Icon to edit the AVD. Click Show Advanced settings. Change the Internal Storage, Ram, SD Card size as necessary. Click Finish.
Click Tools -> AVD Manager. Click the edit icon for the emulator. Click the Show Advanced Settings. Under Memory and Storage, reduce the Internal Storage, specify something like 2048MB for an emulator that comes with Google Play store or less for emulators without the Google Play Store.
In Android N emulator you can easily get access Internal Memory. Then a pop up will open. Click on explore . Then you will get access of Internal Storage.
Deleting an emulator In Android Studio, open the AVD Manager from “Tools” → “AVD Manager”, where you'd normally launch an emulator. In the “Actions” column, click the arrow pointing down to open the menu for the emulator you want to delete. Select “Delete” and confirm in the dialog.
The apps are installed in /data/apps. Make sure that your data partition size is big enough to support your app. The command for running the emulator will be
emulator.exe -avd <AvdName> -partition-size 512 -no-snapshot-load
Partition size will set size of system and data images in MB. You can change 512 to a greater value depending on your needs. -no-snapshot-load ensures that you are not booting from a snapshot and thus you see the new partition size.
143
I've had that happen before, and I solved it by creating a new virtual device as Mr. Hedlund suggests. I didn't spend time trying to figure out why it happened, but creating the new device allowed my app to upload. My application is nearly twice as big as yours, and it uploads fine most of the time. Try deleting and re-creating the emulator as Mr. Hedlund suggests. It's worked for me on several occasions... Being new at Android development, I'm suspicious that I've been running into that issue due to resource leaks, but I haven't chased the problem down yet because I'm still concentrating on getting my app to work correctly... Hope this helps!
31
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
