I followed official Google`s tutorial to build my own AOSP and succeeded in all steps: I have a “Pure AOSP version” running on a nexus emulator. https://source.android.com/source/building.html
The story is I have some rare device came with some Android version full of a pre-installed app’s obviously I don’t want. I want to port Pure AOSP to my device – without any improvements or new features (So, for example, I don`t want to know how to build CM git repo).
Is it working just add to my local above master branch correct files into
/device/vendor/modeland then under
cwdof master branch execute
$ . build/envsetup.sh?
If so, what are the files and their content I need to put under
/device/vendor/model? I found a lot of guides how to pull already existing tree of CM or something else (http://xda-university.com/as-a-developer/porting-aosp-roms-using-source-code) and including this Android device configuration for AOSP and looking on some git repo’s of several devices, I tried to figure out the minimum complete set of files & their content but I didn’t find a correlation. I think there must be the minimum complete set and there is programming reason for the existence of each file. And what I saw in existed git repo`s was this set + custom extras each developer added for his own reasons.
Aftermath How do I determine the Build name & Buildtype to execute
$ lunch <Build name>-<Buildtype >?
How to integrate
$ make otapackagein order to build the familiar one zip file to load via recovery like CWM?
This is following my previous post: Porting AOSP to specific hardware device, But here the questions are more specific.