http://sourceforge.net/p/necessitas/home/
Welcome on the home of the android lighthouse project.
What is Necessitas ?
Necessitas is the codename for the port of Qt on the Android Operating System and of the user-friendly Qt Creator Integration with Android,
This project provides you Qt for the Android Operating System, and a first-class citizen IDE letting you manage, develop, deploy, run & debug your Qt Applications on Android Devices.
How does the AOSP and the Android SDK relate?
If I repo the AOSP do I by default now have the SDK?
Do I have to download it separately?
Or can I/Should I compile it from the AOSP?
I ask because after following the instructions up until: source.android.com/source/building.html. I successfully compiled full-eng and ran the emulator and everything works just fine. It also seems like adb is installed which from what I understand is a part of the SDK. I can't seem to find an answer to this.
So I am going to do my best at answering my own questions and posting for the benefit of anyone else who may be confused; if any of the statements I make are wrong feel free to correct me. This is just from my experience. There seems to be little information regarding how the two relate excepting the build/core/build-system.html, and sdk/docs/howto_build_SDK.txt included with AOSP and airtower.wordpress.com/2010/07/25/building-the-android-sdk/ and of course, trial and error.
NB: jindroid.com/2009/06/08/howto-build-sdk-from-android-source-code/ points to documentation that has since moved to the above location it seems. At least it wasn't there for me as of the most recent repo sync against master.
rpowell8 said:
How does the AOSP and the Android SDK relate?
Click to expand...
Click to collapse
The android SDK is a subset of the ADT (Android Developer Toolkit). The SDK as you download it today is basically just a few binarys for getting the actual content SDK.
I think the best way to describe the SDK is that it is divided into to parts tools, and libraries. The tools are for managing the sdk (tools/android) and misc tools to build apk's, align them, emulate an api etc, and then there are the tools in platform-tools which allow you to perform operations on your device (adb fastboot etc). The "libraries" are a set of API's , system images (file for running an android virtual device (emulator)), and documentation for each release of Android. These seem to reside under platform/
You can either download the above components from the command line, or from eclipse. Eclipse is actually included in the ADT as well with the plugin for android apps preloaded. If you don't have the plugin, you can get it vie Help/Install New Software. This launches what seems to be a front end for the android SDK Manager which allows you to graphically choose which platforms you want to support and emulate.
Now, how does the SDK (the tools and libraries) relate to the AOSP as you repo init/sync from the master repository? It seems you can't build apps from the code downloaded from the AOSP git repo (I'm not sure about this but doesn't seem like it). Instead, what you do, is you use the AOSP to build the SDK (NB: when you use the SDK Manager as mentioned above, you are getting prebuild SDKs, if you want to build the SDK yourself you use the AOSP code) as described in the above mentioned howto. Once the build for the Android SDK is complete it is located in out/host/linux-x86/sdk or similar directory. You can actually point the eclipse plugin to this directory as the location for the SDK...but I recommend using the .zip file that is in that directory and putting it somewhere other than the out directory. Reason being if you decide to do a lunch full-eng after you did the lunch sdk-eng, and then proceed to make, it will force a make cleaninstall and that will basically do a rm -rf on the out directory, deleting all of your SDK and any other platforms you downloaded through the sdk manager.
After you've built the sdk, you now have the necessary tools and API's to build for the platform you repo'd. A word of warning is that it seems if you repo the master branch, it is labeled as "AOSP" for the version indicating to Eclipse that the minimum platform required is the one you just built and so if you want to run it on your device you'll need the full platform loaded onto it or it will show you are running a version earlier than AOSP (also called 'Preview'). Example, as of this writing the version of AOSP is 4.2.1 and the API level is 17 (An API level is just a set of functions/datastructures available for a particular release of Android OS, so for Level 17 it corresponds to 4.2, You can use a higher API than your target (accept in the case of AOSP Preview) and still make sure you are compatible, but you can't use a lower API and expect to have functions/datastructures that were only implemented in later versions of Android). If you have downloaded the Android SDK for API level 17 it will be 4.2, not 4.2.1. You will not be able to run your app that you built using the API level 17 "Preview" based on 4.2.1...on your 4.2 emulator (or device for that matter). You will need to use the emulator based on the AOSP Preview build.
So in short the AOSP contains the sources to build the SDK, but you can also get prebuilt SDK's if you don't want to go through and build each API level.
rpowell8 said:
If I repo the AOSP do I by default now have the SDK?
Click to expand...
Click to collapse
No, you have the components to /build/ the SDK
rpowell8 said:
Do I have to download it separately?
Click to expand...
Click to collapse
No, you can either build it from the AOSP, or you can download it separately.
rpowell8 said:
Or can I/Should I compile it from the AOSP?
Click to expand...
Click to collapse
Probably should if you're building against the latest android development, but I don't see the need if you are building apps for already released API levels.
I'm looking for a Android studio emulator engineering GSI build so I can develop (debug) system apps that use android:sharedUserId="android.uid.system" on the manifest. Where can I download them and how do I create a AVD to be used in android studio ? I'm looking for Android 8 or 9.
xjpmauricio said:
I'm looking for a Android studio emulator engineering GSI build.........
Click to expand...
Click to collapse
All I did was Google "Android studio emulator engineering GSI" as reflected on the following link...
https://www.google.com/search?q=Android+studio+emulator+engineering+GSI
... and the very first result was to the following link...
https://source.android.com/setup/build/gsi
... and if you go to that link, and scroll down a bit, you'll see the category "Downloading GSIs" that provides you with what your looking for.
If it's not on that page, then it's not available (yet) but, It looks like it is available.
Good Luck!
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Enigma Machine {aenigma = Latin for "Riddle" AND Nickname for "My Ex-Wife"}.
I had already looked at that page but the information is confusing. There's a page containing various userdebug builds for download for android pie:
https://ci.android.com/builds/branches/aosp-pie-gsi/grid?
There are three types of builds: eng, userdebug, and user; I'm looking for the eng type, which uses the platform test keys.
The other problem, is that if you follow one of the links you'll land on a artifacts page containing many files that can only be downloaded one by one: https://ci.android.com/builds/submitted/5467499/aosp_arm64-userdebug/latest/
I haven't found an engineering build, only userdebug and I have no ideia on how to download all the files in the artifacts page, but the main problem is that I found no instructions on how to setup an AVD that can be used on Android Studio and Windows 10.
xjpmauricio said:
I had already looked at that page but the information is confusing.........
Click to expand...
Click to collapse
Hmm... I've never, personally, looked into this using this type/specific avenue before myself.
I'm just thinking that, maybe/possibly, either @Qui Peccavit, @Droidriven or even @osm0sis may be able to provide a better answer/guidance to help you out with this.
I do wish you the best of luck with this!
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Enigma Machine {aenigma = Latin for "Riddle" AND Nickname for "My Ex-Wife"}.
Out of my wheelhouse, unfortunately. @phhusson is the GSI master.
I think that userdebug builds built by ci.android.com are signed with AOSP test keys, so that's good enough for you?
I don't really know how to plug in Android Studio with it though, but I heard it's quite easy
@phhusson, I just confirmed that a userdebug build uses the platform test keys; I unpacked a system.img from a userdebug build, checked the SystemUI.apk certificate, using keytool -printcert and the SHA1 is: 27:19:6E:38:6B:87:5E:76:AD:F7:00:E7:EA:84:E4:C6:EE:E3:3D:FA (the sha1 from the google platform test keys)
So...all I need to know is, using these files: https://ci.android.com/builds/submitted/5467499/aosp_arm64-userdebug/latest/
How do I create a AVD that I can use on Android Studio in Windows ? Any ideias?
@phhusson, you were right: its easy to get a userdebug build signed with AOSP test keys, they are available for download on Android Studio in the AVD manager section:
Go to Tools > AVD Manager > + Create Virtual Device > Select Phone, Nexus 5X > Next > Select X86 Images > Select Pie, Api Level 28, ABI x86_64, Target Android 9.0. > Next, etc, download and install.
All builds signed with AOSP test keys are identified by having a target name of Android 9.0, Android 8.1, etc. If you select an image, look at the panel on the right; it should say Android Open Source Project, etc.
All of the other builds of target user are identified with Target "Android 9.0 (Google APi's)" or "Android 9.0 (Google Play)", etc, and those are signed with dev keys, not test keys.
Thanks.
I am trying to debug one of the AOSP service, with Android studio 4.0. Most of the steps I found online are using ddms which is no longer present in android sutdio. Is there any alternative to set up the debug environment for the new version of Android studio ?
I am looking for an Android Studio Client/Server USB Sample/Example code. I have gotten a basic Java Based Android Studio App built successfully running through Android Studio and debugged by representing it on a physical Samsung Android device through a USB port. What I would like to do now is the following:
Build a small Java example code to run separately on Ubuntu that is not necessarily build on Android Studio but some other development platform that can communicate through USB to software build on the first program mentioned here.
Build an APK based on the code from the first project mentioned here and deploy it to an Android device.
Test the communication between these two programs.