I understand - it's probably just some minor glitch, but w/o some debug info from libomap3camd itself it's kind a hard to figure out what's going on. My best guess is that V4L2 stuff behaves different between two kernels (I already cracked one of those bugs that prevented first usage of libomap3camd under 3.5.3 due to this, and subsequent uses worked - you can imagine debugging multithreaded lib with gdb and w/o debugging info that fails only for first use - I had to reboot about 1037 times). Fcam is probably better option in the long run.

As for the kernel itself, here is the link to it: https://github.com/filippz/kernel-adaptation-n950-n9 and instructions for building: https://wiki.merproject.org/wiki/N9_...tions_from_git. If necessary I can provide my own build (it takes tome time to set everything, ie: MerSDK, SB2...), but it would be hard to play with it w/o the ability to compile it. I've tested it using ubiboot on nemomobile, but it works under sailfish too. For preview I also had to build waylandsink (I can send compiled lib if needed)

There are guys on #nemomobile IRC channel that are better than me in setting the enviroment for compiling, so they can help with kernel building and setting up nemomobile if needed.

Anyway thanks for your app, and you taking the time to take a look at this issue!