I'm having issues trying to put my own apps on my phone. A bit of background information, I'm using the latest version of eclipse IDE, trying to get apps onto my galaxy s. I tried installing apps through gmail. When I go to install the app I get a parse error and it doesn't install. I have also tried using this method to install my app onto a htc wildfire s however I get the same issue. Is there a quick fix for this? Thanks for your time; any insight into what the problem is will be great.
Things I've tried:
Ok I still have a parse error when I try installing my app. The min sdkversion was set to 9 which seems right to me as that is the api level for gingerbread which galaxy s uses (i think). I haven't set a target sdkversion yet as according to the android developer guide it if not stated it defaults to the minsdkversion. I also tried setting the minsdkversion to 1 and still no luck. Any ideas?
try to check unknown source in settings==>applications if you are installing non-market application..
Related
So here's the issue:
Regardless of which Android device I choose, my emulator always looks like the screen's been scratched. When I try to run my app, the screen then becomes so distorted and scratched that it's unrecognizable. I have tried, what I think to be, everything including: deleting all android studio files and redownloading the application and wiping data of each emulator. Regardless of what I do, the screen still ends up looking like that.
Here's the details of my emulator:
I'm using a OSX Yosemite 10.10.5.
How do I fix this?
I had same issue and finally just solved it
try to install Oreo system image (API 27) and use it to create new AVD insted of API 28
I had the same issue with Pie in the emulator. I went to the AVD Manager, clicked Edit for the Pie AVD, clicked advanced settings, found the Graphics and changed it to 'Software'. Then it worked!
Well that is strange indeed. Does it happen with emulators from all API levels?
Have you updated your Android SDK tools to version 27 already? Also, check out the Android Blog post with important SDK tools release notes to help you with the emulator setup. Emulator installation is becoming more and more cumbersome in each SDK release and API level, now they even depend on your type of processor... anyway, if you follow the instructions it should eventually work fine.
I am new to mobile development, a few days ago i install Xamarin and Android SDK. I have just created a blank app and when i try to run it says built was unsuccessful and shows the above message.
But when i open the main.axml i can see Nexus one with android 7.1 is selected. I did change these option but the same error.
I did try everything mentioned here on stackoverflow and on Xamarin but none worked for me. i did update Xamarin and downgrade JDK to 8 from 9 as it was mentioned somewhere on the blog but still i am out of luck. its been more than 5 days i am trying different solutions and finally i have to put it in front of the professionals.
Its just an empty app not even a single line of code.
I can give teamviewer access if necessary.
Thanks.
You must install an emulator on which you will run the application. Or connect physical device. There is nothing to do with Xamarin or SDK versions. Your app compiles OK. You just need some device (virtual or physical) to run your application.
I'm using Xamarin Studio and Xamarin Android Player on my windows 10 PC.
I'm having trouble starting Lollipop/Marshmallow (API 21/23) devices using the XAP, but on the other hand, launching Kitkat (API 19) works prefectly.
I've downloaded the required android SDK, tried reinstalling everything again and again but nothing works.
It seems wired, because it is not a problem with Virtual Box, nor with my PC or my XAP installation (if it was, than why Kitkat works?).
I've tried every solution I could possibly find, but nothing works.
Any ideas on what could cause this problem?( If further information is required, I will be happy to add :)
EDIT
It does not matter whether I start the devices through VS/XS/XAP. It all comes down to the same problem, but for the sake of simplicity, let's say I'm running them directly through XAP. Here is a screen shot of what happens when I launch Lollipop (which is API 22, and not 21, for a strange reason) :
For like 5 minutes, the following occur:
Than, forever:
And after a few hours it says booting or something like that, and than restarts to the first position.
With Kitkat, it just starts :).
you probably missed the intel HAXM update.. may be a possible duplicate: Android 5.0 (API Level 21) AVD not launching Intel Atom x86_64
First off, it's difficult to determine the problem without more information. Please list or screenshot the build error(s) you receive when you try to debug your app on a XAP emulator.
But on a hunch... within the past week, I had a problem with similar symptoms. In my case, I had to update project packages in order for my Xamarin Forms project to run on the higher Android APIs.
Reference on how to update packages: https://developer.xamarin.com/guides/cross-platform/application_fundamentals/nuget_walkthrough/#Package_Updates
It might be that hyper-v is causing the problem: "VirtualBox and Hyper-V cannot co-exist on the same machine".
Try to disable it using bcedit as explained in the link.
For further reference, see this discussion
After launching xamarin android player, manually launch virtual box.
You should see the device listed on the left. There is a good chance it will say "stalled." If it says anything other than "Running," try reseting it or starting it.
I also had problems with XAP and my solution was to use Genymotion instead.
Did you try Genemotion
I think it is best Android emulator.
I would post a comment but my reputation is too low.
I don't know if this emulator works with Xamarin studio but if you use Visual Studio it may be an option for you.
Here is the solution:
I had the similar issue and fix the issue as follows.
delete the existing device simulator
reinstalled the simulator again
deploy the solution again.
I know that this question has been asked a lot on SO, but I tried almost every solution without success...
I have a problem when I try to upload my app to devices running on API 10 (no problems with devices on API 11 and up) with this error :
Installation failed since the device possibly has stale dexed jars that don't match the current version (dexopt error). In order to proceed, you have to uninstall the existing application.
WARNING: Uninstalling will remove the application data!
Do you want to uninstall the existing application?
If I click on "uninstall the app" (even if the app is not installed), it ends up with :
Unknown failure
It's not the problem related to 65K methods, since it works on every device except API 10. Nevertheless, I tried adding the multidex support and it didn't change anything...
It's not a problem of space either, since I deleted all the apps on my device before trying the installation. Plus the apk has a size of 12M...
I tried to install the app on the emulator and it didn't work.
I thought that it's an emulator problem, so I looked for a very old phone that I have running on Android 2.3.4 and tried to install the app on it and it didn't work.
I tried to install the apk manually by copying the apk file to the sdk directory and then install it directly on the emulator, but I have an error too.
A very important thing is that the app used to work fine before on the API 10 emulator, and stopped working one day without any significant change !
I've been struggling with this since two weeks now and it's so frustrating that I spent so much time on making my app compatible with API 10 only to be stuck with a problem like this !
Well, I found a lot of solutions to this problem but none has worked in my case.
It turned out that I've changed the targeted SDK from 22 to 23, and that was the cause of this problem.
When I changed it back to 22, it worked !
I don't know why and I'm seriously thinking about changing the minimum SDK to 11 (I've put a lot of effort to be compatible with API 10, but I think that the users still with API 10 are rare and the effort is definitely not worth it).
I build an app using these instructions: http://developer.coronalabs.com/content/build-android-devices-windows. When I connect my device with USB cable and transfer the .APK file. And when I try to install the app, I get an error message which simple says that the app has not been installed or something like that. The app(game) is working fine in the Corona Simulator but not in the real device.
This is the app - https://www.dropbox.com/s/j6jft1y81klh8gz/BlackJack.apk
(but actually I'm getting this error in my device whatever app I trying to install).
And I'm using Samsung Galaxy Y GT-S5360, android 2.3.5 (Gingerbread).
Thank you for any help.
The problems come's from the processor of the phone it uses ARMv6 processor which does not support by the new SDK Build of Corona
see this link it has the same problem as yours http://forums.coronalabs.com/topic/21994-resolved-armv6-support/
Since you mentioned that you receive the error no matter what app you are trying to install, make sure that you have enabled Unknown sources on your device in order to be able to install APK files directly. This location of this setting is usually found in the Security setting.