On Thu, 2015-05-28 at 15:53 +0800, YongQin Liu wrote:
Hi, Tim
We only run boot test for the master juno build, but it failed to boot on our LAVA as well. One problem I can see there is about getting the value of ro.hardware. You can try with passing "androidboot.hardware=juno" as kernel parameter to check if you can boot the recent builds.
That build seems to use the kernel produced by the ARM Landing Team within Linaro. I removed the hack from that a while ago that gave the board the model name 'Juno' which Android uses to determine the hardware type. So yes, to get it working again you will need androidboot.hardware=juno on the kernel command-line. That's what our latest UEFI defaults to doing.
BTW, the latest kernel also requires the latest firmware, due to changes in SCPI interface.
Generally, the best bet to get a working Android on Juno is to use a proper monthly release and follow its instructions. Either the one done for ARM specifically [1] or the Linaro Confectionery Release (LCR). As there is a confusing and every changing plethora of builds Linaro does I would start from the main downloads page [2], that hasn't been updated yet for the release due today.
[1] http://releases.linaro.org/15.05/members/arm/android/images/armv8-android-ju... [2] https://www.linaro.org/downloads/
Since we don't have much resources before, there was not maintainer for this master juno build for a while.
So why do Linaro still create the builds? (Rhetorical question)