For what it's worth, while Mobile Screen Size pulls from user agent and
is wrongly getting lumped into 320x480... "monitor resolution" still
pulls from the "s" param in beacons, which comes from javascript objects
in the browser, and seems to still be correct. I believe this only works
for javascript solutions (mobile web) and not app, though.