I just signed up for 'C2DM' and created an 'Appengine connected
Android Project'. After starting the Android Project, when I try to add my Account comes an error after the Server Settings: "Unable to open connection to Server". Is this
error coming up, because my C2DM account hasn't been released yet?
What target are you using? If you're using the AOSP (Android) 2.2 or above, you need to switch to using the Google API level 8 instead. This will allow you to use a (required) google account.
Edit: Let me clarify in that it's the emulator that needs to be running Google vs Android target, not the build target of the app.
Google Api 8 Emulator will give no problem. Worked for me.
in Eclipse..
Menu > Windows > Avd Manager > Create a new AVD with google api 8 .
Make sure to change the run configurations of project too...
Related
I am attempting to play around a little with xamarin within Visual Studio 2019. I built a new Xamarin Android application and just want to run the base code in the emulator, but I am getting the error in the image below. When I installed VS2019, I did so with the xamarin features including the SDK on my secondary drive and I can see the sdk file on my secondary drive, but am fairly sure that VS2019 is looking with my primary drive for some reason. Is there a way to fix this?
I don't bother with the SDK or emulator packages through the visual studio installer anymore. Install Android Studio, use the tools in that to download the SDK and setup the devices you want to emulate. Then back in Visual Studio, set the paths in the Xamarin/Android Settings in the options menu. Mine look something like this:
Android SDK Location: C:\Users\myusername\AppData\Local\Android\Sdk
Android NDK Location: C:\Users\myusername\AppData\Local\Android\Sdk\ndk-bundle
This setup seems to have much support for Android and gives you the various Google apps and services in the emulators.
Fist, you should check your android sdk path by Tools > Options > Xamarin > Android Settings to view and set the Android SDK location:
For more details, you can check here.
Meanwhile, you should check the Android SDKs and Tools by steps: Tools-> Android->
Android SDK Manager...,then you need install the platforms and Tools you need.E.g.
It seems a little bit late, but I faced this issue and I did the following to sort it out:
Be sure that the BIOS virtualization is enabled
Run the VS2019 as an administrator and run the Android device manager
Wait a for seconds it takes some times
After getting the screen of the Android device manager press the (+) plus button
If you get the menu titled New Device then cancel the creation of a new device
close VS2019 and log out the administrator account
Log in again with your account and run the Android device manager
Hope this may help
I'm keep getting the error at the bottom of the question even though I followed official emulator setup guide and sample project setup guide to the letter.
Using:
- Android Studio 3.0-Alpha7
- Pixel emulator with SDK 23
Provisioning succeeds and was able to enable instant apps in Settings > Google > Instant Apps
Side loading instant app failed: Failure when trying to read bundle. Instant App com.instantappsample requires an SDK version which is newer than the one installed on device. Please update the SDK on the device.
Error while Uploading and registering Instant App
Creating an API 26 (aka O) emulator allowed me to successfully install the Instant App, while otherwise following the guide. Hat-tip to donly from Github project android-instant-apps
Workarounds I tried unsuccessfully first:
Uninstalling "Google Play Services for Instant Apps" (from the other answer)
Downgrading to Android Studio 3.0 Canary 5
Using a physical device that can run instant apps (Galaxy S6 SM-G920V, Android 7.0)
This might be an issue on our end. Thanks for reporting. Please try the following workaround:
Settings -> Apps
Find Google Play Services for Instant Apps.
Uninstall this app.
You might get a notification when it's uninstalled, but please ignore it.
Now proceed to run your instant app again. This issue should go away.
It works for me to switch to API O X86 emulator.
I am trying to adapt a project to run on BlackBerry OS 10 using Android Studio and the BlackBerry Plugin.
When I connect the device I can use ADB to connect (something like "adb connect 172.0.0.1:57248") which connects the device and it shows its name as connected.
When I go into Studio and click the BlackBerry button the device is listed and I can click play.
When I click play in Studio I get a list of devices and the BlackBerry is there (I only have a Z10 for testing) but there is no name next to is and it says it is not able to run because minSdk(API 15) > deviceSdk(API 1).
It seems to me that the device (or something in between) is not reporting the correct API level of the device and so the default is coming back (speculation).
EDIT
Here is it showing the error.
Also, this is Android 2.0 but it does the same in 1.5.
I had the same problem. The solution is to update to the new Blackberry Android Runtime. The problem occurs with the latest OS update 10.3.2.2836.
In order to install the update, you have to click on this URL from your Blackberry browser. It will redirect you to the update on Blackberry World: http://appworld.blackberry.com/webstore/content/39879918
This URL will not work from a regular browser, you must access it from the device you want to update.
After you've installed the update, you must reboot your device and your device will be detected as an Android 4.3 API 18 device.
Additional instructions are available here: http://crackberry.com/if-youve-been-unable-download-android-runtime-update-try-now
Im a freshman of Xamarin. Pls help.
I just followed the guideline of Xamarin
https://developer.xamarin.com/guides/android/getting_started/hello,android/hello,android_quickstart/
until the step of 31
Finally, we can test our application by deploying it to an Android emulator. If you have not yet configured your emulator, please see Xamarin Android Player for setup instructions. In this example, we have installed the Nexus 4 (KitKat) (Android 4.4.2, API Level 19) virtual device and we have started it from the Xamarin Android Player Device Manager console:
I run the Xamarin Android player to test this quick start, it has a problem,
I got a message: Fail to initialize device
I google it with 0 answer
suck this account need a 10 reputation to upload a picture , how I can get the reputation?
Try to check your installed devices.
When I installed Xamarin Android Player no devices were downloaded automatically. You need download and install all you needed devices manually.
For now it's better to use Genymotion but in the future Xamarin Android Player will be a good alternative too,
if you want Xamarin Android Player for now, install the latest version and download manually a device, Make it start and try again.
The solution can be in enabling virtual technology in the bios.
I had same issue.
My solution was to enable
I had to go to My 'Network Connections' in my control panel, found the Connection named 'Virtual Box Host-Only Network', right clicked it and went to the properties and CHECKED the option 'VirtualBox NDIS6 Bridge Networking Driver' and reconnected. This fixed it for me.
I am using Google Maps on the Android emulator, but it is asking me to install Google Play Services but when I click on install it is crashing.
Thanks in advance
What you need to do is:
Install Google Play Services and Google APis from the Android SDK Manager.
Create an AVD (Android Virtual Device) with a target: Google APIs. The device should run android 4.2 or higher.
For more information check here:
http://developer.android.com/google/play-services/setup.html
Making new emulator with X86 architecture worked for me .
This is a hack from one of the posts on SO that I used and had setup on my machine. Dont have the link right now, if someone could post that please, this is just a dump from back then that I had copied.
1.) Create a new emulator
2.) For device choose "5.1'' WVGA (480 x 800: mdpi)", Target choose "Android 4.1.2 - API level 16", "CPU/ABI" choose "ARM" and The rest choose defaults
3.) Start the emulator
install com.android.vending-1.apk and com.google.android.gms-1.apk via ADB install command
Voila! It worked for me. Last I checked this was only possible otherwise officialy on devices. But that is 2012 December knowledge, I havent checked again