Hi,
Blindasabat: I agree, the ReX button click noise is a bit loud for some uses. I suspect mechanism with half this volume might keep heads from turning toward the sound of a ReX click in a theater, but would still provide enough tactile/audio feedback for, say, gloved-hand use in a reasonably-loud wind.
Some ReX observations/questions:
A) Auto-dim: My ReX seems to spontaneously transition from constant-on to PWM-dim mode when batteries are low.
Details -- When batteries are low enough to dim the light, and starting from Constant mode: click button to turn on light, swing light around a bit to ensure PWM is not operating (i.e. observe solid streaks along light path), wait a minute or two (perhaps notice light abruptly dims), swing light around a bit more (keeping clear of button to be positive you are not causing a mode change), note that light is now dimmed via PWM mode (i.e. observe dotted streaks).
Do others see this (and, like me, _not_ see this behavior on their Photon Freedom)? I'm not complaining, this looks like a good idea for the Rex, since it's a light that can be usefully employed at such a wide range of brightnesses.
B) Countdown: There seems to be a kind of 'countdown' displayed as battery charging approaches completion. The blinking changes from simple, evenly spaced flashes (roughly 1 second apart) to clusters of flashes (still ~1 second apart) separated by a pause (of, say, four seconds). When recharging a more-than-slightly depleted ReX (i.e. more than a minute or two of full-brightness since last full charge), goes from simple periodic flashing, to a cluster length starts somewhere between 12 and 10, and over many minutes, changes cluster-length towards 1, and soon after reaching 1, changes to to 'no more flashes; charging done'. There is some jitter, the number of flashes in an example series of flash-clusters might be something like:
(simple periodic)...,12,12,...,11,12,11,...,8,8,8,7,8,8,7,7,7,.....7,6,7,7,6,......1, 1, 1, (no more flashes; charging done).
I mostly charge with AA NiMHs, don't know if this happens for other battery types/voltage ranges/internal resistance values.
I'm not quite sure in either A) or B) is if the behavior was carefully chosen by the firmware authors, or if I'm seeing some unintentional result of software / device-property interaction. Photon/LRI folks: any insight here?
Cheers,
Bazzers