Good point! A reboot does "reset" your currently activated keyboard (maybe this should be part of a separate bug?).

The keyboard layout groups was confusing for me too, and it indeed complicated everything. From the user point of view I also agree that you don't need a dozen keyboards enabled for only using the `fr` one. If the design decision would be to remove the keyboard groups I would be up to doing that :) -- again I suppose this should be a separate bug that will block this one.

Regarding your suggestion about a new setting that points to the active keyboard, there already is a `keyboard.current` setting, but it doesn't seem to be that widely used (only everything.me has an observer for it: [DoATAPI.js#L87](https://github.com/mozilla-b2g/gaia/blob/master/apps/homescreen/everything.me/js/api/DoATAPI.js#L87)). I can try to build on that and integrate this setting better in the keyboard app. What do you think about this?