Manual to Compile Android for PINE46

[lvcargnini]

And what is tulip_chiphd?


Sent from my iPhone using Tapatalk

Don't know.

@lvcargnini: I suggest you to downgrade to java 7, Android 6 isn't ready yet to be compiled with java 8 by default.
AFAIK there isn't any official github tree.

I'm on a Mac OSX, in fact there is some changes to be made on Mac side, the most important one is adding teh following into your android_profile file for bash variables:
export ANDROID_JAVA_HOME=`/System/Library/Frameworks/JavaVM.framework/Versions/Current/Commands/java_home`
Of course there is a new error after this:
Starting build with ninja
ninja: Entering directory `.'
ninja: error: 'out/target/product/tulip-p1/obj_arm/SHARED_LIBRARIES/libMemAdapter_intermediates/export_includes', needed by 'out/target/product/tulip-p1/obj_arm/SHARED_LIBRARIES/camera.tulip_intermediates/import_includes', missing and no known rule to make it
make: *** [ninja_wrapper] Error 1

---

What do I need to copy over form the A64**.zip file into the main AOSP repository ?
I'm trying to compile with the new code of Android., since the tools seem a bit more polished to work with.

You can't copy nothing.
I will try to explain as better as I can. (my english isn't so good)

The first BIG problem; The SDK it's a zip file and the zip does not store unix file permissions so we need to restore the execution bit to all *.sh, *.py, bash files with no .sh extension and all the 32 and 64 bit binary files after the unzip.

But that's not all, for unknow reason they (who?!) removed all the git repository of AOSP source code from all the projects, ~500 projects, so if you want to get newest build you must add back all the AOSP git by hand.

But that's not all, for unknow reason they (who?!) removed the whole git commit log from all the projects so we don't know what they have modified.

My point of view is that if a team member can provide us a proper SDK, ok, otherwise I think I will sell my PINE64 because it's pretty useless to work on it without a proper Android SDK.

Maybe I'm wrong but I think that your problems are related with the execution bit of some files.

@NGC6691  So why don't we start the git tree in the best possible way for the  community  ?

Look there is this github.com/pine64 repository that is empty, we can push over there my AOSP tree, it seems to have some bug during final stages of compilation ( I closed all my stuff before finishing checking the messages). But I copied some devices files from the A64-*blah*.zip, over the master AOSP tree, and everything is fine the biggest annoyance is set the :
device/softwinner/tulip-common/BoardConfigCommon.mk 
or in the
device/softwinner/tulip-p1/BoardConfig.mk 

So I set in the tulip-p1 that is the variable BOARD_WIDEVINE_OEMCRYPTO_LEVEL in my initial test I set to 3, can be 1 or 3, since I didn't checked if it finished OK or in errors I have to re-run the compilation, luckily I have CCACHE in place, to speed-up stuff, if this works I'll have a compiled image of AOSP. 
Currently it is compiling my AOSP, with the necessary structure for tulip_p1 on latest master.