Select version of android for hikey

Hi,

How do i select an older version (ie android-6.0.1_r62) for hikey? The directions here are only for the master.

these are the directions I was following:

https://source.android.com/source/devices.html

Try repo init -u platform/manifest - Git at Google -b android-6.0.1_r62.

yeah I did that and it downloaded the branch but when I went to build it…using lunch…there was no “hikey” option. The “hikey” lunch was option was only available via running -b master

In that case, that version might be a branch where hikey support wasn’t added. You can maybe try adding hikey to default.xml like below, but not sure if it’ll work or not.


diff --git a/default.xml b/default.xml
index 8f7c459..cb9c5ed 100644
--- a/default.xml
+++ b/default.xml
@@ -58,6 +58,8 @@
   <project path="device/lge/bullhead-kernel" name="device/lge/bullhead-kernel" groups="device,bullhead" clone-depth="1" />
   <project path="device/lge/hammerhead" name="device/lge/hammerhead" groups="device,hammerhead,broadcom_pdk,generic_fs" />
   <project path="device/lge/hammerhead-kernel" name="device/lge/hammerhead-kernel" groups="device,hammerhead,broadcom_pdk,generic_fs" clone-depth="1" />
+  <project path="device/linaro/hikey" name="device/linaro/hikey" />
+  <project path="device/linaro/hikey-kernel" name="device/linaro/hikey-kernel" clone-depth="1" />
   <project path="device/moto/shamu" name="device/moto/shamu" groups="device,shamu,broadcom_pdk" />
   <project path="device/moto/shamu-kernel" name="device/moto/shamu-kernel" groups="device,shamu,broadcom_pdk" clone-depth="1" />
   <project path="device/sample" name="device/sample" groups="pdk" />

Ugh. I pulled down all the defaults from all branches i 6.0.0 and 6.0.1 (I just manually changed the script below for 6.0.1 and the and then grepped for “hikey” … none of the versions have hikey listed under devices.

#!/bin/bash
COUNTER=0
while [ $COUNTER -lt 70 ]; do
wget https://android.googlesource.com/platform/manifest/+/refs/heads/android-6.0.0_r$COUNTER/default.xml
cp default.xml default_00_$COUNTER.xml
let COUNTER=COUNTER+1
done

Will it even work if I manually add an entry for hikey into the default listing? How is it that hikey has not been integrated into any of the repositories for android 6 except for Master? I really need to get an older version of Android 6.0 for my work that will compile and work on my CE Edition hikey board. Any help / advice?

> Will it even work if I manually add an entry for hikey into the default listing?
As mentioned earlier, not really sure if this will work. Are you able to give it a try?

> How is it that hikey has not been integrated into any of the repositories for android 6 except for Master?
Iiuc, 6.0 branch was forked off master before hikey support was added, so all new 6.0.x releases will be based off of this fork and not master.

I’m going to try the instructions here:

Looks like there is a local manifest file available for Android 6 and Android 5. If this doesn’t work, then I will try to manually edit the manifest file to to have hikey as a device.

thanks!

Here is the manifest files:

No problem and good luck! Good job locating the old build! :slight_smile:

I keep getting compilation errors when trying to build. Any advice?

I’m on ubuntu 14.04 and using openjdk 8. I built the master branch successfully earlier.
I extracted this file: http://builds.96boards.org/snapshots/hikey/linaro/binaries/20150706/vendor.tar.bz2
into Android directory. The directions say to grab 20150607, but this is not available so I assumed a typo and grabbed the file under directory 20150706. i tried both compiling with “make droidcore -j32” and “make -j32” with the same errors.

$repo init -u platform/manifest - Git at Google -b android-6.0.1_r10 -g “default,-device,hikey”
$ cd .repo/
$ git clone https://github.com/96boards/android_manifest -b android-6.0 local_manifests
$ cd -
$ repo sync -j24
$ source build/envsetup.sh
$ lunch hikey-userdebug
$ make -j32
$ cd out/target/product/hikey


including ./vendor/build-info/Android.mk …
out/host/linux-x86/bin/acp vendor/build-info/BUILD-INFO.txt out/target/product/hikey/BUILD-INFO.txt
target Symbolic: init (out/target/product/hikey/symbols/init)
out/host/linux-x86/bin/checkpolicy: loading policy configuration from out/target/product/hikey/obj/ETC/sepolicy_intermediates/policy.conf
target Symbolic: adbd (out/target/product/hikey/symbols/sbin/adbd)
target Unpacked: healthd (out/target/product/hikey/obj/EXECUTABLES/healthd_intermediates/PACKED/healthd)
Building with Jack: out/target/common/obj/JAVA_LIBRARIES/core-junit_intermediates/with-local/classes.dex
Building with Jack: out/target/common/obj/JAVA_LIBRARIES/libphonenumber-platform_intermediates/classes.jack
Building with Jack: out/target/common/obj/JAVA_LIBRARIES/conscrypt_intermediates/with-local/classes.dex
device/linaro/hikey/sepolicy/init.te:3:ERROR ‘unknown type configfs’ at token ‘;’ on line 13742:

init.hikey.usb.rc writes to /config/* to set up USB

allow init configfs:dir { create reparent rename rmdir setattr { { open getattr read search ioctl } { open search write add_name remove_name } } };
checkpolicy: error(s) encountered while parsing configuration
make: *** [out/target/product/hikey/obj/ETC/sepolicy_intermediates/sepolicy] Error 1
make: *** Waiting for unfinished jobs…
Launching background server java -Dfile.encoding=UTF-8 -Xms2560m -XX:+TieredCompilation -jar out/host/linux-x86/framework/jack-launcher.jar -cp out/host/linux-x86/framework/jack.jar com.android.jack.server.JackSimpleServer
Launching background server java -Dfile.encoding=UTF-8 -Xms2560m -XX:+TieredCompilation -jar out/host/linux-x86/framework/jack-launcher.jar -cp out/host/linux-x86/framework/jack.jar com.android.jack.server.JackSimpleServer

make failed to build some targets (01:20 (mm:ss))

Another roadblock :(. Looks like the instructions only works for https://github.com/96boards/android_manifest -b android-5.0. https://github.com/96boards/android_manifest -b android-6.0 has updates to use hikey support from aosp (see https://github.com/96boards/android_manifest/commit/60af0696b9452e1e7986ead978adf794b45164d4), so unlike the android-5.0 one, you’re actually using device/linaro/hikey - Git at Google -b master instead of https://github.com/96boards/android_device_linaro_hikey/tree/android-6.0. The best I can think of is for you to maybe try platform/manifest - Git at Google -b android-6.0.1_r10 -g with one of the following below, but again, this is sort of like an in-between releases hack so can’t say that you won’t get another build error. Or just try editing the master branch as discussed in earlier posts.

  1. https://github.com/96boards/android_manifest -b d3709bd0dab2d7a0f83f7d9e4bcd4c11a12ff13b (the commit just before the one that uses hikey support from aosp). In this case, you will use https://github.com/96boards/android_device_linaro_hikey -b marshmallow-dev, which is ahead of https://github.com/96boards/android_device_linaro_hikey -b android-6.0.

  2. https://github.com/96boards/android_manifest -b android-5.0, but with below modification to use -b android-6.0 instead. The one above (marshmallow-dev) has kernel version 4.1, and this one is 3.18, so maybe try the one above first.


diff --git a/linaro.xml b/linaro.xml
index ebd650f..5f7d169 100644
--- a/linaro.xml
+++ b/linaro.xml
@@ -17,7 +17,7 @@
   <remote name="github" fetch="http://github.com/96boards" />
   <remote name="linaro-other" fetch="git://git.linaro.org/" />
   <!-- Linaro Device Configs -->
-  <project path="device/linaro/hikey" name="android_device_linaro_hikey" revision="android-5.0" remote="github" groups="device,hikey" />
+  <project path="device/linaro/hikey" name="android_device_linaro_hikey" revision="android-6.0" remote="github" groups="device,hikey" />
   <project path="device/linaro/build" name="device/linaro/common" revision="linaro-lollipop-experimental" remote="linaro-android" groups="default" />
   <project path="android-patchsets" name="android-patchsets" revision="master" remote="linaro-android" groups="default" /> 

I am in a requirement of running the hikey 24x7 on android for my project and for a long time(i.e. a year or something). Is it suitable for the board ?

To be honest this is pretty much the same answer as for DB410C: