Auto-lock after 30 second without any press from off.
You can do 4 clicks to disable the auto-lock completely.
Okay.
Press and hold for 0.5s to turn on / off
Personally I’m okay with this, but I know many people really do not like hold for on.
Wait a minute, where should I put moonlight?
I prefer hold from off for moonlight. The other stuff I don’t mind.
If you want timed auto lock set timer for like 15-30 mins not secs
Hi Barry,
I am so glad you are engaging the flashlight community about the auto lock, it was driving me nuts. I suggest keeping it as simple as possible with minimal changes to your existing UI which is already one of the best non Anduril UI’s.
“Auto-lock after 30 second without any press from off.”
Muggles need the auto lock to prevent accidents, 30 seconds should work fine for them when enabled.
“You can do 4 clicks to disable the auto-lock completely.”
This should work just fine for anyone who don’t need the auto lockout.
I would like to suggest the following:
Most people won’t like the rest of the changes below unfortunately, it is also not the same as your default Sofirn UI.
Rather just implement the two changes above.
Direct access to moonlight (press and hold from off) and turbo (double click from off) are important to most users.
“Standard UI is”
“Press and hold for 0.5s to turn on / off”
“While on, click to cycle through Low-Medium-high, double lick to Turbo, another double click to Strobe.”
"While off(locked), double click to unlock and go to remembered brightness. If you do other press, such as 1 click, hold, 3 click, it fashes "“twice to indicate locked status. 4 clicks to disable the auto-lock and go to remembered brightness.”
“While off (unlocked), 1 click, the indicator shows battery status for 5 seconds.”“How about that?”
“Wait a minute, where should I put moonlight?
”
I would also like to suggest the following:
Long press from off.
Don’t put too many work into this when others have solved the problem already. Have a look at the Acebeam E70 (MINI). That’s an autolocking light done right. Get one and copy the UI.
This would be making a feature that a lot of people already dislike even more likely to come into play.
IMNSHO this, or something like it, is all that’s required.
When I pull out my SP32A, hold for off is one thing I have to re-acclimate to, realize I don’t miss, and a big reason I don’t use it any longer.
While off(locked), double click to unlock and go to remembered brightness. If you do other press, such as 1 click, hold, 3 click, it fashes twice to indicate locked status. 4 clicks to disable the auto-lock and go to remembered brightness.
While off (unlocked), 1 click, the indicator shows battery status for 5 seconds.[/quote]How about that?
Wait a minute, where should I put moonlight?
It happens a lot in tech nowadays, where schools turn out UX designers who should have been flunked out, or don’t eat their own dog food.
Disrupting a UI that has been familiarized, and pretty consistent between both Anduril and non-Andruil models, all for the sake of a polarizing “feature” is the essence of the tail wagging the dog.
I think 30s is too fast. sometimes you just turn off the light to check something and you don’t want it to be locked immediately.
2 clicks for unlock can be pressed in the pocket accidently. make it 3 or 4
Make that 3C in this config.
Do not do that.
I have IF25, do not do that…
The moon 2C from turbo is just bad, especially as there is no change in my model, from top of the ramp to turbo.
PPL will strobe by accident. Strobe should be 3C when ON or move it further, like 5C, or 3H.
And I don’t like that you are changing the whole UI.
Just add the auto-lock function to the existing one, or copy the acebeam, or anduril 2.0.
1 minute is way too short for autolockout, and in general, I’m against forcing autolockout at all - with something that divisive, it should always be optional and always configurable.
Or just put Anduril in the light, with whatever vendor-specific UI coded in place of Anduril’s “Simple” mode!
That way @Barry0892 is saved from reinventing the wheel for us enthusiasts, and the people that think Anduril is too complex (and the muggles we eventually lend our lights to) can stay in Simple mode and be happy. It would be a win-win-win for everyone…
Many users (me included) don’t like Anduril lights
Sofirn/Wurkkos already did both for same model before.
TS11 with Anduril + TS11’S’ with simplified UI. And I think a few others. Ofc this would bloat up their lineup even more, but I don’t see why we can’t have both.
That would likely help them sell even more lights.
I’m interested in figuring out how simple UI could be more usable for people who don’t as that’s often the justification for a lot of manufacturers for making lights with noncustomisable firmware - do you just not like ramping interfaces at all and want one that only cycles through preset modes (perhaps in a circular loop rather than the way anduril reverses?), or something else the issue with it? Thinking about the practicality of having an “even simpler simple UI” option for OEMs who want that vs the current “anduril with less features” simple UI that ultimately still works mostly the same as the full UI.
It is not a discussion on Anduril pros and cons so I answer shortly. It is a flaslight not a jet plan. I only need it to make some light. 3-4 levels and off. Low battarey indication is nice and also electronic lock off. That is it.
If I need to read the manual more than once it is too complicated
Thanks for your comment!
Re: “many users”, please realize anduril-hat^H^H^Hunliking folks are distinctly in the minority: even among hard-core Convoy users, and even paying more for the privilege, We the People prefer Anduril by over a 5 times margin.
Just out of curiosity: did you read and understand my proposal? The idea is:
And see, as the manufacturer will end up selling MANY more lights by making them available with Anduril than without (see the “over 5 times margin” above), gains of scale would probably make the light even cheaper, so benefiting you non-Anduril-enthusiasts too!
What’s not to like? 
It will peobably shock you, but most of the pople who buy and use flashlights don’t vote on r/flaslights. They just need simple UI. They also don’t want to pay extra for MCU with more memory needed for FW they dont use
Gotta toss it in here… one of my favorite lights is the EC50.
On/off, LMH, done.
Plus I still got and use quite a few 1-mode on/off lights.
And some lights like the Tacklife with an annoying af UI which I try to use as a 1-mode light and would happily lobotomise it if I could.
Sometimes a light is just a light.
Agreed on all three counsts [sic] !
And in my proposal, that’s what they will get right from the factory 
The AT1616 MCU (which is one of the more expensive MCUs among those capable of running Anduril) costs exactly $0.05 (yep, all of 5 pennies) more than the cheapest Anduril-incapable MCU (eg, from Sonix). This is less than 0.3% of the cost of a $20 light…
But even for the ones among us where saving $0.05 in a $20 purchase is mandatory, having Anduril is a good thing: with the added sales that having Anduril would generate (and not only among the folks that access r/flashlight, as even the folks that don’t access it but are eg feature-comparing lights for their purchase, will tend to buy a light listing “Anduril” as one of its features rather than one that does not, out of curiosity if nothing else), having Anduril on the light will probably make the light less expensive than one without.
Does it run Anduril? Lobotomizing is easy 
It’s just a matter of changing the firmware. And that’s what me and the other Anduril modders are here for!
Does that Tacklife run Anduril? If yes, please tell me the model (ie, what it blinks after clicking 15C) and I will happily provide you with a
“lobotomized” HEX (that is, one that does exactly the “On/off, LMH, done” you want).
If it doesn’t already have Anduril, then there’s nothing I can do for you – one more reason for wanting Anduril everywhere! 
It got the magical tailcap that has the driver and charger built-in. Nothing in the head but the LED.
Unscrewing the outer tailcap exposes the inner tailcap with usb port, switch, and red/green LEDs for charge status (both charging and in-use).
Seems like we’re getting a bit off-topic. The thread is about what Sofirn should do to improve their recent Auto-lockout UI.
Anduril provides one solution for how to implement that feature, but it’s not the only solution. Another really slick way to handle automatic lockout is SammysHP’s “pocket UI”. It’s the same as the regular UI, but with 1 extra click on every “from off” action. It’s a very simple and very effective solution which allows a light to be locked all the time, without being a pain to turn on.
Regardless of that though, Sofirn should probably add memory for the flag which tracks whether auto-lock is enabled. So if the user turns that on or off, the light should remember even after a battery change. When it forgets the user’s preferences, it makes for an unhappy user.