Actions
Forum Thread Details
  • State Suggested Answer
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 22 subscribers
  • Views 253 views
  • Users 0 members are here
Related

Why is Android on RIoTboard Not Using the Resolution and/or Refresh Rate I Specify in bootargs?

jdmcs

According to everything I have read online, the RIoTboard is configured to a default resolution of 1280x720 at a default refresh rate of 60Hz -- what I would consider 720p. However, when I connected the RIoTboard to a TV that supports 720p, the TV told me that the input was unsupported. Sure enough, when I plugged the RIoTboard into a computer monitor, the refresh rate was 53Hz!

 

So that I can benchmark GPU performance of the BeagleBone Black, Raspberry Pi, and RIoTboard, I need to configure the resolution to several settings. The first one I tried was 1080p... but after changing the bootargs and commanding U-Boot to boot, my monitor complained that the input was unsupported. So why didn't changing "1280x720M@60" in the original bootargs to "1920x1080M@60" work... or for that matter, why isn't "1280x720M@60" outputting video at 60Hz?

 

I'd appreciate some help so I can complete my comparison. Thanks.

  • 0

    These are known problems with the Android Image.

     

    With my TV (Philips) the Android Image isn´t working at all. No matter what resolution or refresh rate.

    Linux is working fine though.

     

    With my Monitor (Samsung Syncmaster) I have no problems at all.

    720p and 1080p are working perfectly @ 60Hz.

    Also no problems with the Linux Image.

     

    I think that the Android Image has problems with the communication over HDMI, to negotiate what the TV is supporting or not.