The display density in ARC is currently configured at build time based on the internal display. There are two consequences:

  1) Performance hit on DSF mismatch, and upscaling of low-DPI content. For example,
     when a high-DPI display is connected to a low-DPI device in docked mode (or a
     device without an internal display), Android content is scaled up by Chrome.

  2) Incorrect cursor scale. Android scales the cursor from pixels to DIPs based on
     the internal DSF. On devices without an internal display, it falls back to the
     primary DSF, which may be incorrect if the build-time density does not match.

The density should be selected at run time based on the primary DSF.

See also internal bug b/31352706.