New procedure for building Android from source

[jonsmirl]

https://gitlab.com/pine64-android/manifest/wikis/home

This procedure is new so it may have issues. The key feature is that all of Android and lichee are in git. That means you can clone the repos (look in the manifest files), make changes, and then send pull requests.  Then use 'repo sync' to get everyone's changes.

Anyone up for getting this working on the longsleep kernel so that we can get rid of lichee?

You need 100GB free disk space, it uses 96GB.
This takes around nine hours to run depending on network and CPU speeds.
$ mkdir ~/bin
$ PATH=~/bin:$PATH
Download the Repo tool and ensure that it is executable:
$ curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
$ chmod a+x ~/bin/repo
$ mkdir android
$ cd android
$ repo init -u https://github.com/pine64-android/manifest.git -b master
$ repo sync
$ . ./build/envsetup.sh
$ lunch (tulip_chiphd-user, Baomi/db1000)
$ make -j 5
$ cd ..
$ mkdir lichee
$ cd lichee
$ repo init -u https://gitlab.com/pine64-android/manifest.git -b master
$ repo sync
$ ./build.sh config (choose '0' for all)
$ ./build.sh
$ cd brandy
$ ARCH=aarch64 ./build.sh
$ cd ../../android
$ extract-bsp
$ pack
image in:
../lichee/tools/pack/sun50iw1p1_android_Baomi-db1000_uart0.img
This makes a Phoenix card image.
Lot's of tools for installing here: lichee/tools/tools_win
To get a 'dd' image, install it to an SD Card. Boot it. Then use 'dd' to copy the image off from the SD Card.

---

Google Play login seems to be working in this build.

---

Also note that by adding items to the manifest apps like Kodi can be included in the build.

[jonsmirl]

This build will run into several issues on Ubuntu 16.04. You can Google for work arounds. Ubuntu 14.04 works without problems.
If 'repo sync' for lichee hangs it is a gnutls issue on Ubuntu 16.04.

After you do the final pack, cd ../lichee and do './build.sh pack'. that will make a pack file without Chinese characters in the name.

[MarkHaysHarris777]

Thanks for your work on this jonsmirl.

[xalius]

I followed the steps outlined in the top post, and got a working Android image, thanks a lot jonsmirl! I used Ubuntu 14.04 after running into to many issues with 16.04 and that worked like a charm, make sure you have things like git, build-essential and https://source.android.com/source/initia...buntu-1404 installed before starting. Running the build in a Virtualbox VM took about 4h with 4 out of 8 cores (i7-975EE@3.4Ghz) and 8GB RAM assigned to the VM, disk image was on a SSD.

[MarkHaysHarris777]

Sweet... thanks for the post Xalius, and thanks again for the nice work jonsmirl.

[jonsmirl]

First update...

cd lichee
repo sync
./build.sh config

You can now choose the Longsleep kernel...
All available kernel:
0. linux-3.10
1. linux-pine64
Choice: 1

I have checked, it compiles and boots Android. I have not done much testing on it.

[Terra854]

Is it possible to tweak the default.xml file without breaking things so that we can compile Android Marshmallow/Nougat and don't get stuck on Lollipop?

[jonsmirl]

Is it possible to tweak the default.xml file without breaking things so that we can compile Android Marshmallow/Nougat and don't get stuck on Lollipop?

Allwinner has already ported A64 Android on to Marshmallow, I just don't have a copy. The repositories you are downloading from Google have the master branch in then so you already have all of the base code (they contain every branch of Android). Just need a copy of the Allwinner changes.

It might be possible to port yourself, but it is simpler just to wait until someone provides the Allwinner code.

Now that the Allwinner code is in repo form, it is not too hard to bring Cyanogenmod up on it. Maybe someone with give it a try....

[NGC6691]

Allwinner has already ported A64 Android on to Marshmallow, I just don't have a copy.

http://wiki.pine64.org/index.php/Pine_A6...ow_ver_6.0

[jonsmirl]

Allwinner has already ported A64 Android on to Marshmallow, I just don't have a copy.

http://wiki.pine64.org/index.php/Pine_A6...ow_ver_6.0

That file is very old and it was not zipped correctly. We need a new dump from them.