Is there a bug tracking the jb issues / do we still enable it on jb devices, even with the known issues? Do we intend to get it working on jb, or is that out of scope?
I tried enabling it on my jb Open C and indeed, I did see the occasional hard-lock (screen froze, buttons stop working, current song plays to the end, but doesn't continue to the next). --Chris On Mon, Jan 26, 2015 at 7:06 PM, Mason Chang <[email protected]> wrote: > Hi all, > > Silk, which is a project to improve smoothness across Firefox OS has > started to land. There are three parts to it, which you can read more about > here (http://www.masonchang.com/blog/2015/1/22/project-silk). Today, I > just enabled the vsync compositor which should create smoother animations, > which includes scrolling. However, it is quite a big change and we expect > some problems. If you find any bugs, please file them as a dependent of bug > 1118530 (https://bugzilla.mozilla.org/show_bug.cgi?id=1118530). You can > always test the bug by disabling these two prefs: > > gfx.vsync.hw-vsync.enabled > gfx.vsync.compositor > > Note: You need a kit-kat based device. I’ve tested on a flame with v180 > base image and above. Any base image below v180 or non kit-kat based > devices have known issues. > > Thanks, > Mason > > _______________________________________________ > dev-gaia mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-gaia > >
_______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
