(05-24-2016, 06:59 AM)IlyaM Wrote: Yes, there is a symlink to ../src

It's seems to me, I fixed this problem. I removed SDK and unzipped it again using terminal (previous version I unzipped using RAR manager)
So, and now my firmware is compiling, about 20 minutes have passed and I haven't got errors.

So I have 2 more questions, is there any git repository where can I get last changes, cause I downloaded SDK from wiki.pine64.org as zip archive and there are some hidden folders (.repo in root folder and .git inside some folders), how can I sync it to get update?

And what is real correct codename of our chip tulip_t1 or tulip_p1, cause in the message above someone wrote tulip_p1, in the other thread someone wore tulip_t1

My Android device info showed:

Code:

Model number: Pine64
Processor type: QuadCore-A64
Android version: 5.1.1
Firmware version: v1.2.5

Kernel version:
3.10.65
peng@ChipHD #45
Fri Apr 29 16:58:39 CST 2016

Build number:
tulip_chiphd-eng 5.1.1 LVY48E 20160505 test-keys

(05-24-2016, 05:26 AM)NGC6691 Wrote: @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.

(05-24-2016, 08:19 AM)IlyaM Wrote: And what is tulip_chiphd?


Sent from my iPhone using Tapatalk

(05-24-2016, 11:39 AM)lvcargnini Wrote:

(05-24-2016, 05:26 AM)NGC6691 Wrote: @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.

(05-27-2016, 11:17 AM)NGC6691 Wrote:

(05-24-2016, 08:19 AM)IlyaM Wrote: And what is tulip_chiphd?


Sent from my iPhone using Tapatalk

Don't know.

(05-24-2016, 11:39 AM)lvcargnini Wrote:

(05-24-2016, 05:26 AM)NGC6691 Wrote: @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.

(05-28-2016, 02:43 AM)NGC6691 Wrote: @lvcargnini: Allwinner must do it, not us.
Well, we don't know which AOSP projects they have modified and is near impossible to set up a github tree.

(05-28-2016, 06:49 PM)tllim Wrote:

(05-28-2016, 02:43 AM)NGC6691 Wrote: @lvcargnini: Allwinner must do it, not us.
Well, we don't know which AOSP projects they have modified and is near impossible to set up a github tree.

Not sure whether this shell file help up. Disclaimer, I am not Android software engineer.

(05-28-2016, 02:43 AM)NGC6691 Wrote: @lvcargnini: Allwinner must do it, not us.
Well, we don't know which AOSP projects they have modified and is near impossible to set up a github tree.