fix #1166 by auto alignment of option name
fix #1169 and #1170
Merge pull request #1229 from chrox/fix_1166

fix #1166 by auto alignment of option name
Merge pull request #1230 from chrox/fix_1170

fix #1169 and #1170
refactor refresh

Lots of the device-related distinction wandered into
base/ffi/framebuffer_<driver>. This eases the refresh logic in
UI manager, which basically only decides what kind of refresh
to trigger. The device specific configuration in the framebuffer
driver decides how to realize that whish.

screen.lua is gone, in its place is now the framebuffer driver.
The device abstraction decides what framebuffer driver to load.
switch from scaleByDPI() to scaleBySize()
update base

pulls the needed changes in base for the refresh refactoring
fix old (pre-refactor) refresh call syntax
update base

pull in Kobo-related fix
pull in refresh waiting fix
fix refactor bug: invalidate update_regions_func
update base

pull fix for rotated rotation (well...) on Kobos
provide debug function to framebuffer ffi implementation
pass device object to input FFI module

this is needed (for now) on Android, since the FFI module triggers
screen updates.
update base

pulls changes to fix Android input/framebuffer API interaction