On-topic for Lanterne...

I've tested it thoroughly (latest version from OP), and noticed few things:

1. Sadly, "exit on camera cover close" options doesn't work. I've tried restarting Lanterne after enabling it, to no avail. It seems, that this option is just ignored.

2. In morse code tab, text imput field is missbehaving, if one hits "return" after writing sentence to send (I did it intuitively, wanting to check if it will be same as hitting "Start transmitting" button). It seems to open new line, but there is no way to write anything in it, or delete it and get back to our string - imput field just becomes practically disabled.

Still, my text from 1st line *is* there - if I start transmitting, it goes on (that's why I think it opens new line, then goes sepuku).

3. In strobe flash experimented, input field for duty cycle time is strange, too. Using hardware keyboard, I can write max 999 ms there (three digits), but via software buttons, I can set as much as 5000 ms.

Furthermore, there is something wrong with that duty settings. On 5000 ms and 25% duty cycle, leds remain ON for same ammount of time, as with 3000 ms. Increasing it above certain level seems to only affect pause time.

BTW, UI design observation here. "new" settings, utilizing duty cycle time and duty cycle percentage are in line with wikipedia's definition, but, in real life usage, "old" way of setting ON time and pause time was *much* more convenient and intuitive. I don't know for others, but I opt for reverting it.

4. UI design suggestion - please, split "torch ON/OFF" button into two, wide in half. Then, let first one remaine "torch ON/OFF", and make another "Indicator ON/OFF". Due to buttons size, even replacing one of them with two still keeps them finger-friendly, in both landscape and portrait.

OTOH, it allow us to enable either regular or nightvision-friendly torch modes from main menu, without side trips to prefferences. Speaking about the latter, it would also allow to get rid of "use indicator led as torch" checkbox from prefferences, leaving only mA settings there. I don't see any down-sides for such solution, only gains

Speaking about details - I thinked about it carefully, including situation, when one of torch modes is already enabled, and user click "ON/OFF" button assigned to another torch mode. IMO, this should result in disabling previous torch instantly, and activating last one "clicked" (literally, toggling between normal and indicator torch).
---

Thanks for already making it almost feature-complete and UI-ideal!