@aw found this bug in the screen device, I'll try to fix it today.