The problem I am having is that when I try to run my application onto my android emulator I get the error of: There is not enough storage space on the device to store package:/data/local/tmp/Mono.Android.DebugRuntime-debug.apk. Free up some space and try again.
The emulator runs fine, its when I try and deploy the app that it gives me the message. I know that it has something to do with space on the enumlator. I have tried to see what I could find on here but none of it seems to work in this case. I have looked up some of the same questions on here but so far they have not been effective. I have tried to uninstall apps, clear data, change the size of the sd card and ram, also I have tried to make the java heap bigger. At this point I do not know where to go from here.
I am pretty much asking what can I do from here to try and fix this issue? I will provide pictures of the setting and the exact output messages since there where no error messages technically. I am using visual studio enterprise 2017 and using Xamarin Forms.
Pictures here:
This is a picture of the settings for the emulator
This is the second picture of the settings for the emulator
This is the picture of the Output window where I get the message
I had a similar issue (not Xamarin forms, just Xamarin app in general)
After resetting the device in Android Device Manger I set the DataPartition via the GUI to 2GB. Restarted the device but the dataPartition was still 200mb. (seen in the hardware-qemu.ini).
I noticed the Device Manager wrote to the config.ini the line
disk.dataPartition.size=2 GB
So what I found worked for me was.
Factory Reset the device
Manually edit the config.ini to read 2000m not (not 2 G)
disk.dataPartition.size=2000m
Restart the device
Here is a screen shot of my emulator on a Mac.
Stupid question your pc does have enough ram and local storage right ??
part1:
part2:
What also helped was factory reset (too many test apps installed)
Related
I am trying to install app on a Nexus 4 virtual android 5.1 on Xamarin Virtual machine. If i want to install an app, I mostly get this error: App not installed (don't get this during some installations but 95% get this error).
I did ofcourse lots of research and testing.
Install Android studio their VM. Same error.
found some potential solution here
*Reboot the phone: In times like this, first thing to do is to reboot your device. Or just shut down, remove and reinsert your battery. Done and no luck
*Make sure to uninstall any apps you don’t use to free up space, also uninstall previous versions of the same app currently installed on your device.
I download them all for the first time via APKpure.com
*Double check the apk files you download and be sure they were completely copied or downloaded. App are released by companies their self and are fully downloaded
*Try resetting app permissions by going to Settings >Apps>All>Menu key >Reset application permissions or Reset app preferences. Done and no luck
*Change app installation location to Automatic or Let system decide. don't know how this is possible without a root
*Make sure your SD card is not mounted or connected to a PC or elsewhere. no Sd card
*For worst case scenarios, format your SD card – copy it’s contents somewhere else for backup and format. no Sd card
*The last solution would be to totally wipe your device. Either by doing a factory reset under Settings or by doing a full wipe in recovery mode. I even reinstalled Xamarin
Downloaded an android 4 version, no luck.
I found lots of post where they were talking about signing. I did not change the APK files and I never managed to install them before.
downloaded never Nexus device with A5.1 and still same error.
Help is much appriciated.
I've always had problems with Xamarin Android Emulator.
Please use the Android Emulator (AVD) instead which contains less bugs than the Xamarin one.
Click here for a guide on using the Android AVD.
And in the meanwhile, you can report the bug here to Xamarin with any relevant information such as logs and errors seen during app deployment.
The problem seemed to be an compatibility issue with lots of apps. I was able to retrieve the Logcat and after looking at the logcat, that was our only conclusion.
I have a mid 2013 Macbook Air (so I should have the resources to make the emulator work) and I'm trying to get the Android Emulator working. It's been half an hour and the color pinwheel continues to spin. In the meantime I looked up and downloaded Andy and BlueStacks Android emulators but Andy was nothing more than a clock with no buttons and BlueStacks, while it had a number of options there was nothing that seemed evident that I could get 'Hello World' running from the basic tutorial.
http://developer.android.com/training/basics/firstapp/running-app.html
I want to progress but I'm stuck. Thanks.
I would look into Genymotion. They have a great android emulator that can spin up vms for different phones. Its free for personal use and easy to use. The VM image is download directly from their server so when it gets corrupted you can delete it and add it again.
It is also recognized by Eclipse and Android Studio.
There should be two downloads, one that includes Oracle VM and one that doesn't. I recommend the one that does so you do not need to install Oracle VM by its self.
If that doesn't work post a comment and ill see what I can do.
try restarting your computer..
When you start an emulator you should "Store a snapshot for faster performance" in the Android Virtual Device (AVD) configuration or the emulator won't start at all. After too much time troubleshooting, it was as simple as that.
I'm using IntelliJ Idea 13 to develop Android applications on Ubuntu 12.04 64-bit. But my virtual device never starts despite there is no error.. its screen always stays like this:
My Android target level is 4.4 (API 19). How can I solve this issue?
Edit: Here is my AVD details:
I Recommend you look at this post to a similar question.
https://stackoverflow.com/a/5535532/2978914
they are using eclipse but you should be able to view the logcat, other posts say first load can be ridiculously long.
the spec of your PC may come into play as this post https://superuser.com/a/347298 explains the way the emulator converts to arm opcode: direct quote:
To use emulator more effectively, this is my experience:
Don't close emulator everytime you run your application.
Scale the emulator screen smaller.
Disable snapshot (Yes, it's useful but it takes time to close the emulator).
Specify a file path for SD card image file. I use only one SD card for many AVDs.
If you got any problems in adb, just reset adb, don't close emulator.
Open few programs in your operating sytem.
If you are using Windows, don't ever close emulator. Do it combined with Hibernate of Windows.
My AVD has started after I check "Use Host GPU" option from "Emulation Options".
I have a problem with the Android Emulator and its SD card. I am developing an application that writes files to /sdcard. Everything works fine, until I exit the emulator by clicking its close button. After restart the files are empty (size 0), but still in the directory. Of course, they have not been empty as long as the emulator runs.
This looks like a failed sdcard unplug, like with usb stick. But I am not sure, how the emulator treats the card exactly. I am starting the emulator from Eclipse, and get an error at exit, when I close the emulator.
The problem did not exist before I updated my Android plugin. I could use all my files after restarting the emulator. Moreover, the problem does not occur on the real thing. I am using the most recent Android stuff, and Eclipse 3.5.
I already tried deleting my emulators and creating a new one. I also tried shutting the emulator down with the red telephone button, but that did never complete. Of course, my app is not a service and has no threads pending at shutdown.
Any ideas, you friendly people out there?
I am currently seeing the same problem on mine using an API 4 emulator, but putting the apk on my actual android device it works fine. It only happens if I close the emulator and restart using "Debug As" or "Run As". My current workaround is to start the emulator before running / debugging my app... not shutting down the emulator prevents this from happening, although I wish I had a real fix.
The problem went away by itself. I have no idea, what caused the healing. I did not do anything particular. I just continued working.
Thanks for your attention.
my problem : the app I have uploaded into my cellular device is shown without the pictures I have insert to it .
steps I have done in order to install:
I have inserted the xxx.apk file into the device via usb
I downloaded an apps installer via the Market
I opened the app using the installer and instead of picture an white background appeared
when I opened the xxx.apk file using file system I found the pictures.
note: even an application icon weren't appearing.
Apparently the res libary having problem to be bined to application.
I might ness to add something to my appliction manifest?
I might need to change something on my device ? (I already made a change and enabled user's not Market application )
I would be very grateful for some life saving answer I need to show my work in a few days in this is the first time i tested her on a real devise.
I also tried an example as shown in hello android book the same example worked perfectly on the emulator where on my android device (Motorola milestone ) the picture and icon weren't shown
Please tell me what I might be doing wrong guys I need to apply my project back at uni(I was the only one in uni who did it on android and in my country most of pep don't even know what android is so getting help outside of forum's like this is not an option ) so please please help me .
I don't know what app installer you downloaded from the Market, but you shouldn't need it. You should be installing the app to your phone using the same SDK tools you used to install it to the emulator. Ie, using Eclipse or the commandline "adb install" commmand.
I'm assuming you used the SDK tools to install the app to the emulators? In which case, start there. Start with looking at what you're doing different between when you installed unsuccessfully to your phone and when you installed to successfully to the SDK.
In my experiences so far, there should be very few differences between working with the emulator and working with the phone.
Well, something is wrong, but what is hard to tell from your question. What pictures are you talking about? Your drawable resources? My guess would be that your application works in the emulator (you have tested it?), but that it doesn't on the phone you're testing with. Have you checked the logcat output?
If you're developing from Eclipse, why not try a debugging session using the phone rather than the emulator?
Hard to narrow down without more details, but a few notes:
Pontus has a point - what's your logcat output? You can use logcat on a real device. Maybe not yours unless it's rooted, but with many phones you can.
Do you link the drawable to your app in the manifest file?
How do you test on emulator vs. device? Do you right-click the app and choose "Run As -> Android Application"? Do you do that for both emulator and device?
When you run on the device, do you first sign it? If so, can you verify the jar/apk and see the contents? Is the drawable under res/drawable?