I am trying to build the AOSP for android Oreo,in the software requirement section it is mentioned about the following device binaries-
(1)Preview binaries (blobs)
(2)Factory images
(3)Binary hardware support files branches
(4)OTA images
Without including these binaries,I am able to build the code successfully but while running the emulator it is not started.
As per my knowledge, we do not require these binaries in case we are using an emulator,is it necessary to include them?
link followed->link for software requirements
Device binaries are mandatory for both emulator as well as hardware device,the avd in the android studio and the binaries should be of same configuration.
Related
I am able to use OpenSSL static libraries (libcrypto.a and libssl.a) in my iOS app thanks to this help. Now i can also use OpenSSL dynamic libraries (libcrypto.so and libssl.so) in my Android app version thanks to this info. I downloaded the files for Android in the OpenSSL_1.0.2g_Android.zip file from here. I just guessed and used the ARM files (armeabi-v7a folder) instead of the Intel files (x86 folder) and it worked on my Android test phone.
My question: How do I make an Android build that uses the correct library files on ARM devices AND also on Intel? I don't know how to deploy both sets of files for this. Below is snip of project window showing where i test added the second libcrytpo.so library file for x86.
But, this second libcrypto.so does not show up in the deployment window, only the first version i added (the ARM version) remains.
I was hoping i could somehow use compiler directives but maybe i just need 2 independent projects altogether? One built for Android ARM and other for Android x86? Further, all i'm needing in my code is an IdHTTP1->Get() so maybe their is a way i can use the built in BoringSSL fork? If so, how?
russ
C++Builder 10.3 Version 26.0.33219.4899
RAD Studio does not support producing Android apps for Intel, only for ARM, so don't even worry about trying to use the x86 libs on Android.
Also, Indy does not support BoringSSL at this time.
I want to deploy my first iOS App created with Xamarin Forms to the AppStore or at least to a single device. I have an Apple Developer Account and performed this task several times before using xCode and native iOS Apps.
But as a Windows guy I hoped to get this done for Xamarin using my VST for Windows.
But all guides and tutorials I found are only explaining how I can deploy iOS Apps to the store and to devices using VST for Mac ... Is this the only way? How do I get the code to the Mac? Can I use the TFS Source Control? Do I have to commit every little change to TFS, check it out at the Mac, rebuild the whole app there and deploy it from the Mac?
Or are there ways and workflows that work with Windows only having the Mac 'in the background' via network?
Take a look at https://mobile.azure.com (the best solution for continuous app development: analytics, crash reports, iOS/Android/UWP builds + deploy)
I'll address the second part of your question - the ability to deploy to a single device. I'm assuming that the single device is your own device and you want to deploy via compilation. This can certainly be done from your Windows machine but due to apple licensing requirements, you will need your Mac available to compile and deploy to your phone. Your iPhone/iPad will need to be plugged into your Mac's USB.
The guides listed on the Xamarin website outline how to set up the mac build host. https://developer.xamarin.com/guides/ios/getting_started/installation/windows/connecting-to-mac/ In short, you need some prerequisites (Remote Sharing turned on, XCode installed, etc).
Once you've connected Visual Studio to your Mac, set the iOS project as the startup project, change the config from Debug to iPhone, and press F5 to compile and deploy to your device.
When in doubt, select iPhoneSimulator instead of iPhone. The simulator isn't subjected to provisioning and signing profiles which can be daunting to setup. If you can get the simulator working, you've solved the software and connectivity prerequisites.
There's a lot to configure, but it does work. This is my primary setup for Xamarin.Forms development.
I have downloaded latest Android Studio 2.2.3 and I want to start with C examples for project Tango phone (Lenovo Phab 2 Pro) using C API. The phone itself says it's run Android 6.0.1, kernel 3.10.84 on device.
Google developer documentation for Tango Project suggest to install Android Studio with Android SDK 24.4.1, Platform tools 23.1 and NDK 11.0.0.
By installing latest Android Studio there is no offering to install those versions of tools. Is it possible to use whatever SDK for development (latest)?
Where do I find aforementioned versions?
What Android SDK & NDK version is required for phone which run Android 6.0.1?
I started using the Dev Kit which runs Android 4.4 KitKat and I just recently got the Phab 2 Pro this week and I didn't need to make any updates to my Android Studio SDK manager.
Since I am working only with the Tango and not with the underlying Android features, I have found no need to require 6.0 for I am not using any of the extra features.
Also go here and clone the repo and run the hello-world and see if you can get it to work on your phone, if so you are good to go!
the SDK Manager which is part of Android Studio offers you choices on levels of android builds like 4.4.2/5.1/6.0/6.1, etc. Platform tools package is a module within the SDK Manager which also has levels which are based on the android build. The NDK is a completely different package and depending on what you want to accomplish you might be able to not worry about it to start of with. install Android Studio and then setup the SDK Manager to cover what devices you want to build for. get the latest Platform tools package setup and you will be ready to code. once you start setting up your environment things will fall in place. for the most part the installer does the work. pay attention to the things needed prior to installing Android Studio. i think you need to install a jdk and set paths and variables.
I have a Xamarin.Android application that is being built through a build server. The application is targeting API Level 23 and Min Android Version 4.1 (API 16). During debug the application works fine, but when the build server compiles the application, packages it, signs, and aligns it, it crashes on load with the error:
Unable to get provider mono.MonoRuntimeProvider: java.lang.RuntimeException: Unable to find application Mono.Android.Platform.ApiLevel_23 or Xamarin.Android.Platform
Most phones result in an immediate crash with the error mentioned above, but a handful of devices work fine. The only thing those devices have in common is they were used to deploy the application during development. This leads me to believe they have the shared run time installed and hence why it doesn't fail. The build server has the latest Xamarin.Android (just like the dev machines), latest Java, latest JDK, and latest Android libraries (per the SDK Manager). The configuration being built doesn't use the shared runtime, it is not linking (although I also tried it with linking SDK assemblies only), and it only supports armeabi-7va ABI.
What am I doing wrong?
I have finally found the problem which seems to be a bug with Xamarin (or Mono?). We have AndroidManifest.xml and AndroidManifestAlpha.xml. During the build we specify /p:AndroidManifest=Properties/AndroidManifestAlpha.xml to the MSBUILD arguments, but the compilation adds all the activity, services, and mono information to the AndroidManifest.xml file only. The build eventually uses the specified AndroidManifestAlpha.xml file and compiles the APK without the mono runtime; resulting in the error mentioned above.
Change the Target Android version. In VisualStudio on Mac, the path is Project->.Options->General->TargetFramework.
If someone finds this error check my answer in another post:
https://stackoverflow.com/a/52678522/1106547
It's for Xamarin Studio, but I guess should work for VS Xamarin extension too.
The main idea in my case was to put android-25 (or android-23 for the case of the original question) folder to the Android SDK platforms directory.
I suppose it allowed the Xamarin engine to install correct "..Platform.ApiLevel_" APK and use the shared library.
Unable to create Android Virtual Device
i follwed this link.
I installed all ARM images for each Android more than 4.0.
I installed intel & MIPs as well.
But, still my AVD Manager is saying "NO System images installed for this target".
why, so?
In order to create an Android Wear emulator you need to follow the instructions below:
If your version of Android SDK Tools is lower than 22.6, you must update
Under Android 4.4.2, select Android Wear ARM EABI v7a System Image and install it.
Under Extras, ensure that you have the latest version of the Android Support Library. If an update is available, select Android Support Library. If you're using Android Studio, also select Android Support Repository.
Below is the snapshot of what it should look like:
Then you must check the following in order to create a Wearable AVD:
For the Device, select Android Wear Square or Android Wear Round.
For the Target, select Android 4.4.2 - API Level 19 (or higher, otherwise corresponding system image will not show up.).
For the CPU/ABI, select Android Wear ARM (armeabi-v7a).
For the Skin, select AndroidWearSquare or AndroidWearRound.
Leave all other options set to their defaults and click OK.
Then you are good to go. For more information you can always refer to the developer site.
As a workaround, go to sdk installation directory and perform the following steps:
Navigate to system-images/android-19/default
Move everything in there to system-images/android-19/
The directory structure should look like this:
And it should work!
If you use Android Studio .Open the SDK-Manager, checked "Show Package Details" you will find out "Android Wear ARM EABI v7a System Image" download it , success !
I had android sdk and android studio installed separately in my system. Android studio had installed its own sdk. After I deleted the stand-alone android sdk, the issue of "“No system image installed for this Target” was gone.