Comment 15 for bug 1574777

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Yes 0.6Hz sounds bad but I'm hoping we can ignore it for a couple of reasons:

1. Mir does not use that information to change its behaviour. Only prints it out. Instead Mir will sync to vblank (60Hz or whatever).

1.1. Android drivers on the other hand might use that information, which would be bad but not if #2 is proven...

2. If other M10 owners also see "0.6Hz" but can get external displays to work fine then the 0.6Hz message is benign and is a minor bug that can be ignored. In that case it's _not_ an indication of the speed Mir is trying to render at.