On Fri, May 20, 2016 at 10:59 AM, NY <niruyadla@gmail.com> wrote:
> When I used pre-compiled system.img and other required images on Hikey
> board.
>
> which are shared from the below path.
> https://builds.96boards.org/releases/hikey/linaro/aosp/latest/
>
> I am using below HDMI display and could see android display comes up with
> the pre compiled images(looks like lollipop AOSP version).
>
> http://www.gechic.com/product_help_en.asp?s=10
>
>
> However when I built the latest AOSP code, with generated images.
>
> I have flashed those on Hikey board with same setup above.
>
> And could not see the display is coming up.
>
>
> It may be some issue with the display configuration on latest AOSP built,
> Got this log from logcat not sure it is expecting built in display rather
> than HDMI display?
> DisplayManagerService: Display device added: DisplayDeviceInfo{“Built-in
> Screen”: uniqueId=”local:0″, 1024 x 768, modeId 1, defaultModeId 1,
> supportedModes [{id=1, width=1024, height=768, fps=60.000004}],
> colorTransformId 1, defaultColorTransformId 1,
Can you provide dmesg output from the board? (you can capture this via
"adb shell dmesg")
The HiKey board has some limitations in generating mode clock rates
which drive displays. Some monitors could handle these limitations
better then others, so we've recently tried to limit it to some of the
common known good rates.
Its likely that the monitor you have wants one of the problematic
rates that HiKey has trouble with and possibly doesn't support any of
the known good rates. But it might be possible that the display
supports rates that HiKey can do, but I wasn't able to validate at the
time.
thanks
-john